USHIFT-6073: Add upgrade path on releases scenarios: from Z-1

[agullon]

• Add 2 new Release Testing bootc scenarios to exercise Z-1 upgrade path
• Changes brew-rpms sub dirs from X.Y-(zstream|ec|rc|nightly) format to X.Y.Z{-(ec|rc|nightly)} to support Z-1 versions
• manage_brew_rpms.sh download 4.${X} ${OUTPUT_DIR} zstream now downloads internally 4 different versions: current, Z-1, Y-2 and Y-1.
  • Example for X=19:
    • Y0_VERSION=4.19.7
    • Z1_VERSION=4.19.0
    • Y1_VERSION=4.18.26
    • Y2_VERSION=4.17.44

[openshift-ci-robot]

@agullon: This pull request references USHIFT-6073 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.21.0" version, but no target version was set.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agullon

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [agullon]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[agullon]

/retest

[openshift-ci-robot]

@agullon: This pull request references USHIFT-6073 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.21.0" version, but no target version was set.

Details

In response to this:

• Add 2 new Release Testing scenarios to exercise Z-1 upgrade path.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@agullon: This pull request references USHIFT-6073 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.21.0" version, but no target version was set.

Details

In response to this:

• Add 2 new Release Testing bootc scenarios to exercise Z-1 upgrade path
• Changes brew-rpms sub dirs from X.Y-(zstream|ec|rc|nightly) format to X.Y.Z-(ec|rc|nightly) to support Z-1 versions
  • find_package option added to manage_brew_rpms.sh to support it

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@agullon: This pull request references USHIFT-6073 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.21.0" version, but no target version was set.

Details

In response to this:

• Add 2 new Release Testing bootc scenarios to exercise Z-1 upgrade path
• Changes brew-rpms sub dirs from X.Y-(zstream|ec|rc|nightly) format to X.Y.Z-(ec|rc|nightly) to support Z-1 versions
  • find_package option added to manage_brew_rpms.sh to support it

⚠️ PR openshift/release#72367 must be merged at the same time.

• also backport this to release-4.20 and release-4.19

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@agullon: This pull request references USHIFT-6073 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.21.0" version, but no target version was set.

Details

In response to this:

• Add 2 new Release Testing bootc scenarios to exercise Z-1 upgrade path
• Changes brew-rpms sub dirs from X.Y-(zstream|ec|rc|nightly) format to X.Y.Z{-(ec|rc|nightly)} to support Z-1 versions
  • find_package option added to manage_brew_rpms.sh to support it

⚠️ PR openshift/release#72367 must be merged at the same time.

• also backport this to release-4.20 and release-4.19

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[agullon]

/test e2e-aws-tests-bootc-release-arm e2e-aws-tests-bootc-release

[openshift-ci-robot]

@agullon: This pull request references USHIFT-6073 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

• Add 2 new Release Testing bootc scenarios to exercise Z-1 upgrade path
• Changes brew-rpms sub dirs from X.Y-(zstream|ec|rc|nightly) format to X.Y.Z{-(ec|rc|nightly)} to support Z-1 versions
  • find_package option added to manage_brew_rpms.sh to support it

⚠️ PR openshift/release#72367 must be merged at the same time.

• also backport this to release-4.21, release-4.20 and release-4.19

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@agullon: This pull request references USHIFT-6073 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

• Add 2 new Release Testing bootc scenarios to exercise Z-1 upgrade path
• Changes brew-rpms sub dirs from X.Y-(zstream|ec|rc|nightly) format to X.Y.Z{-(ec|rc|nightly)} to support Z-1 versions
  • find_package option added to manage_brew_rpms.sh to support it

⚠️ PR openshift/release#72367 must be merged first to be able to download Z-1 brew RPMs.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[ggiguash]

/hold

I would like us to try implementing the same without adding extra options / dimensions to the manage_brew_rpms.sh script (i.e. 0 and 1 flags).
One idea is to always download more than one latest versions, for example the last two. This way, previous version should be handy in the cache if required.

[openshift-ci-robot]

@agullon: This pull request references USHIFT-6073 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

• Add 2 new Release Testing bootc scenarios to exercise Z-1 upgrade path
• Changes brew-rpms sub dirs from X.Y-(zstream|ec|rc|nightly) format to X.Y.Z{-(ec|rc|nightly)} to support Z-1 versions
• manage_brew_rpms.sh download 4.${X} ${OUTPUT_DIR} stream now downloads internally 4 different versions. Example for X=19:
  • Y0_VERSION=4.19.7
  • Z1_VERSION=4.19.0
  • Y1_VERSION=4.18.26
  • Y2_VERSION=4.17.44

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[agullon]

/retest

[agullon]

/retest

[agullon]

/retest

[openshift-ci-robot]

@agullon: This pull request references USHIFT-6073 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

• Add 2 new Release Testing bootc scenarios to exercise Z-1 upgrade path
• Changes brew-rpms sub dirs from X.Y-(zstream|ec|rc|nightly) format to X.Y.Z{-(ec|rc|nightly)} to support Z-1 versions
• manage_brew_rpms.sh download 4.${X} ${OUTPUT_DIR} zstream now downloads internally 4 different versions: current, Z-1, Y-2 and Y-1. Example for X=19:
  • Y0_VERSION=4.19.7
  • Z1_VERSION=4.19.0
  • Y1_VERSION=4.18.26
  • Y2_VERSION=4.17.44

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@agullon: This pull request references USHIFT-6073 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

• Add 2 new Release Testing bootc scenarios to exercise Z-1 upgrade path
• Changes brew-rpms sub dirs from X.Y-(zstream|ec|rc|nightly) format to X.Y.Z{-(ec|rc|nightly)} to support Z-1 versions
• manage_brew_rpms.sh download 4.${X} ${OUTPUT_DIR} zstream now downloads internally 4 different versions: current, Z-1, Y-2 and Y-1.
  • Example for X=19:
    • Y0_VERSION=4.19.7
    • Z1_VERSION=4.19.0
    • Y1_VERSION=4.18.26
    • Y2_VERSION=4.17.44

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[agullon]

/hold

I would like us to try implementing the same without adding extra options / dimensions to the manage_brew_rpms.sh script (i.e. 0 and 1 flags).
One idea is to always download more than one latest versions, for example the last two. This way, previous version should be handy in the cache if required.

@ggiguash can you please review this PR again please? I modified the implementation with your suggestion. See PR description.

Important, CI jobs are using custom S3 bucket to not mess up the cache: AWS_BUCKET_NAME="microshift-build-ushift-6073-cache-us-west-2"

[agullon]

/test e2e-aws-tests-bootc-release e2e-aws-tests-release e2e-aws-tests-bootc-release-arm e2e-aws-tests-release-arm

[agullon]

/test e2e-aws-tests-bootc-release

[openshift-ci]

@agullon: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-tests-bootc-release	8a0f74f	link	true	/test e2e-aws-tests-bootc-release
ci/prow/e2e-aws-tests-bootc-release-arm	8a0f74f	link	true	/test e2e-aws-tests-bootc-release-arm
ci/prow/e2e-aws-tests-release	8a0f74f	link	true	/test e2e-aws-tests-release

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.