-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Identities missing after 1.3 -> 1.4 upgrade #12598
Comments
thanks for the report. it looks like the computed keypath for identities in etcd was accidentally changed during the 1.4 development cycle. will be corrected to refer to the 1.3 location and a hotfix will be released. |
I already ran migration scripts to recreate all the identities, will there be a merge or will they be deleted? |
the old identities are still intact in etcd under the old key (unless you moved them with your migration scripts) with the fix in #12606, the old identities would be visible again, and any new ones you created under the new key would be inert. we'll need to think carefully about whether we could safely merge new data back into the old location. |
Thanks for the clarification. I can just recreate the identities because we already manage them externally. This should clear out the soon to be redundant identities? after #12606 is included in a released |
https://github.com/openshift/origin/releases/tag/v1.4.1 has been released which resolves the incorrect storage location for Identity and EgressNetworkPolicy objects. Identity objects created while running 1.4.0 can be copied to the correct etcd location using etcdctl to make them available in 1.4.1:
EgressNetworkPolicy objects created while running 1.4.0 can be copied to the correct etcd location using etcdctl to make them available in 1.4.1:
|
Post upgrade all user identities and mappings seem to be lost (users exist but identities missing)
Using mappingMethod=lookup
Will update
The text was updated successfully, but these errors were encountered: