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

[release-4.16] USHIFT-3273: EL94 Periodics #3434

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #3353

/assign copejon

… rpms not being available yet, so these will also need to be disabled temporarily

crel is now 4.17 with does not exist yet. this break scenarios expecting a crel image, which is not built during build phase. we will need these tests when a ec/rc 4.17 is available, so disabling the tests with a bogus extension is preferable to deleting them

moved el92-yminus@el94-src@upgrade-ok.sh to periodics (where it was intended to be). this should fix the boot failure caused by missing image, since the ostree commit isn't built in presubmits

removed rhel93-prel-with-optionals.toml as prel will be 4.15 which does not support multus

removed rhel92-prel-with-optionals as multus is not supported for 4.15

start el94-src@upgrade-fails.sh and el94-src@upgrade-fails-on-1st-boot-but-recovers-on-2nd.sh to install with 92 as a base, the immediately upgrade to 94 via ostree

Update test/scenarios/el92-yminus@el94-src@upgrade-ok.sh

Updated periodics to include tests from yminus2 and previous minor releases to el94 current release and source combinations

Signed-off-by: Jon Cope <jcope@redhat.com>

Update test/scenarios-periodics/el94-crel@el94-src@upgrade-fails.sh

Update test/image-blueprints/layer1-base/group2/rhel93-microshift-yminus2.toml

Update test/scenarios-periodics/el94-crel@el94-src@upgrade-fails.sh

add new periodic images for optionals

Co-authored-by: Patryk Matuszak <pmtk@redhat.com>
@copejon
Copy link
Contributor

copejon commented Jun 4, 2024

/retest-required

@copejon
Copy link
Contributor

copejon commented Jun 4, 2024

/test microshift-metal-tests-arm

@copejon
Copy link
Contributor

copejon commented Jun 4, 2024

USHIFT-3273

/jira-refresh

@copejon
Copy link
Contributor

copejon commented Jun 4, 2024

/test metal-periodic-test-arm

1 similar comment
@ggiguash
Copy link
Contributor

ggiguash commented Jun 5, 2024

/test metal-periodic-test-arm

@ggiguash
Copy link
Contributor

ggiguash commented Jun 5, 2024

/lgtm

@ggiguash
Copy link
Contributor

ggiguash commented Jun 5, 2024

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jun 5, 2024
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 5, 2024
Copy link
Contributor

openshift-ci bot commented Jun 5, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, openshift-cherrypick-robot

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

The pull request process is described here

Needs approval from an approver in each of these files:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 5, 2024
@ggiguash
Copy link
Contributor

ggiguash commented Jun 5, 2024

/retitle [release-4.16] USHIFT-3273: EL94 Periodics

@openshift-ci openshift-ci bot changed the title [release-4.16] [USHIFT-2971] EL94 Periodics [release-4.16] USHIFT-3273: EL94 Periodics Jun 5, 2024
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 5, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 5, 2024

@openshift-cherrypick-robot: This pull request references USHIFT-3273 which is a valid jira issue.

In response to this:

This is an automated cherry-pick of #3353

/assign copejon

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
Copy link
Contributor

ggiguash commented Jun 5, 2024

/label jira/valid-bug

@openshift-ci openshift-ci bot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jun 5, 2024
@ggiguash
Copy link
Contributor

ggiguash commented Jun 5, 2024

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jun 5, 2024
Copy link
Contributor

openshift-ci bot commented Jun 5, 2024

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

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.

@openshift-merge-bot openshift-merge-bot bot merged commit e0764a1 into openshift:release-4.16 Jun 5, 2024
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants