Closed dkeohane closed 3 years ago
I'm confused what the actual problem is here. The oc apply
should be idempotent and should update the existing CR if it already exists or create a new one if it doesn't. What was the error you were seeing?
The issue I was encountering was when I had the existing Account CR osd-creds-mgmt-osd-staging-1
with a valid iamUserSecret
set. The oc apply
appears to wipe the iamUserSecret
and therefore when the new accountclaim see there's a 'valid' account, it claims fine but fails when attempting createIAMSecret
in the accountclaim_controller.go
Hmm, that sounds concerning. Is the iamUserSecret part of the Spec? If so, that would explain why that would happen given the oc process | oc apply
and it's not a bug. If that's not part of the spec, then this needs to be filed as a bug and we need to investigate this further.
If you can confirm that this is part of the spec that's getting overwritten, go ahead and remove the hold and we can let this merge. Otherwise, please close this PR and open a new JIRA with the bug description.
/hold /lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: dastergon, dkeohane, iamkirkbater
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Confirmed it's part of spec, removing hold
Encountered an issue today when calling
make create-accountclaim
when an account CR with a name ofosd-creds-mgmt-osd-staging-1
already exists, the call nukes the existing account and replaces it with a templated account CR.Fixed by adding a check to see if account already exists before applying new account CR.