Keystone: Implement RegisteredLimit Controller#782
Conversation
|
Failed to assess the semver bump. See logs for details. |
22a08f7 to
e46ac56
Compare
e46ac56 to
4964e1d
Compare
8379469 to
027f4aa
Compare
b6de206 to
e46d4a0
Compare
e46d4a0 to
d91dcf9
Compare
$ go run ./cmd/scaffold-controller -interactive=false \
-kind=RegisteredLimit \
-gophercloud-client=NewIdentityV3 \
-gophercloud-module=github.com/gophercloud/gophercloud/v2/openstack/identity/v3/registeredlimits \
-gophercloud-type=RegisteredLimit \
-openstack-json-object=registered_limits \
-required-create-dependency=Service
On-behalf-of: SAP nils.gondermann@sap.com
Register with the resource generator On-behalf-of: SAP nils.gondermann@sap.com
Add the OpenStack client to scope On-behalf-of: SAP nils.gondermann@sap.com
Register the controller On-behalf-of: SAP nils.gondermann@sap.com
On-behalf-of: SAP nils.gondermann@sap.com
On-behalf-of: SAP nils.gondermann@sap.com
767c683 to
4c2f1fe
Compare
On-behalf-of: SAP nils.gondermann@sap.com
On-behalf-of: SAP nils.gondermann@sap.com
On-behalf-of: SAP nils.gondermann@sap.com
Generate the OLM bundle On-behalf-of: SAP nils.gondermann@sap.com
4c2f1fe to
8c90198
Compare
|
Hi, this PR is more or less good to be reviewed. I am currently running into a strange problem though: In the I have already setup a local keystone instance to test this against, and I can not reproduce the What makes this especially weird is, I have looked at the |
Hi @gndrmnn, I won't be able to look at this right away. Perhaps @eshulman2, @dlaw4608, or @winiciusallan can do a first round of reviews, and might have ideas on what could be causing the tests to fail. I'll look at this when I'm back. |
winiciusallan
left a comment
There was a problem hiding this comment.
Hi @gndrmnn, try the suggestion and let's see how the tests behave. In the meantime, I'll review the rest of your code. Thanks for working on this.
| }, | ||
| finalizer, externalObjectFieldOwner, | ||
| ) | ||
|
|
There was a problem hiding this comment.
You're missing a serviceImportDependency here. What it's maybe happening is that your service/registeredlimit-import become available at some point, but your controller are not reconciling it again due to the missing watcher here, and it waits for OpenStack forever.
You can use the endpoint controller as a reference
WIP
RegionIDas k-orc does not have that resource currentlyResourceName,RegionID, andDefaultValueleading to some interesting challengens. E.g. Declaring two yaml files with twoRegisteredLimitswith the sameRegionIDandResourceNamewill race to change the same entry.