-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
chore(test): add workaround for multiple groot issue in export-import #8897
Conversation
When we perform an export and import into the cluster, this ends up creating two groot users in the cluster. This PR implements a workaround so that two groot users are not created to begin with. With this workaround, now we can also run upgrade tests using ExportImport upgrade strategy.
0945f3a
to
3c7de47
Compare
What's the work around? |
it fixes the UID in the export to the UIDs in the current cluster. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a comment on -1
. Looks good to me.
When we perform an export and import into the cluster, this ends up creating two groot users in the cluster. This PR implements a workaround so that two groot users are not created to begin with. With this workaround, now we can also run upgrade tests using ExportImport.
The workaround is as follows. We find the UIDs of groot user and guardian group from the new cluster. We modify the output of the export and replace the UIDs of groot user and guardian group with the UIDs we found in the new cluster.
Closes: DGRAPHCORE-300