-
Notifications
You must be signed in to change notification settings - Fork 86
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
Deploy metadata in end to end tests #2186
base: development/2.10
Are you sure you want to change the base?
Conversation
Hello kerkesni,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Incorrect fix versionThe
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
Please check the |
e03ffd7
to
15d54c7
Compare
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
|
2468755
to
ac95b9c
Compare
7d7a397
to
9bee3e8
Compare
9bee3e8
to
0efddbf
Compare
Metadata components need to be started in the order repd -> bucketd -> cloudserver as they are not able to recover on their own when a component they depend on is not available at startup. Issue: ZENKO-4414
Configuration of the test environement is done through an image built in the build-test-image job, this image contains the list of location details used to initialize the locations. This list isn't updated when only retrying the end to end test jobs, and the bucket is create using the env var passed to the pod. So we endup creating the bucket with the updated retry count but configure the location with the old bucket name which fails as pensieve won't be able to find that bucket. Issue: ZENKO-4414
0efddbf
to
9055c5f
Compare
Issue: ZENKO-4414