Skip to content
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

Open
wants to merge 4 commits into
base: development/2.10
Choose a base branch
from

Conversation

Kerkesni
Copy link
Contributor

Issue: ZENKO-4414

@bert-e
Copy link
Contributor

bert-e commented Jan 21, 2025

Hello kerkesni,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options
name description privileged authored
/after_pull_request Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval Bypass the pull request author's approval
/bypass_build_status Bypass the build and test status
/bypass_commit_size Bypass the check on the size of the changeset TBA
/bypass_incompatible_branch Bypass the check on the source branch prefix
/bypass_jira_check Bypass the Jira issue check
/bypass_peer_approval Bypass the pull request peers' approval
/bypass_leader_approval Bypass the pull request leaders' approval
/approve Instruct Bert-E that the author has approved the pull request. ✍️
/create_pull_requests Allow the creation of integration pull requests.
/create_integration_branches Allow the creation of integration branches.
/no_octopus Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity Change review acceptance criteria from one reviewer at least to all reviewers
/wait Instruct Bert-E not to run until further notice.
Available commands
name description privileged
/help Print Bert-E's manual in the pull request.
/status Print Bert-E's current status in the pull request TBA
/clear Remove all comments from Bert-E from the history TBA
/retry Re-start a fresh build TBA
/build Re-start a fresh build TBA
/force_reset Delete integration branches & pull requests, and restart merge process from the beginning.
/reset Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

@bert-e
Copy link
Contributor

bert-e commented Jan 21, 2025

Incorrect fix version

The Fix Version/s in issue ZENKO-4414 contains:

  • 2.11.0

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

  • 2.10.12

Please check the Fix Version/s of ZENKO-4414, or the target
branch of this pull request.

@Kerkesni Kerkesni force-pushed the improvement/ZENKO-4414 branch 3 times, most recently from e03ffd7 to 15d54c7 Compare January 22, 2025 11:41
@bert-e
Copy link
Contributor

bert-e commented Jan 22, 2025

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

@Kerkesni Kerkesni force-pushed the improvement/ZENKO-4414 branch 9 times, most recently from 2468755 to ac95b9c Compare January 23, 2025 17:28
@Kerkesni Kerkesni marked this pull request as ready for review January 24, 2025 15:15
@Kerkesni Kerkesni force-pushed the improvement/ZENKO-4414 branch from 7d7a397 to 9bee3e8 Compare January 24, 2025 15:16
@Kerkesni Kerkesni force-pushed the improvement/ZENKO-4414 branch from 9bee3e8 to 0efddbf Compare January 24, 2025 15:58
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
@Kerkesni Kerkesni force-pushed the improvement/ZENKO-4414 branch from 0efddbf to 9055c5f Compare January 24, 2025 16:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants