Skip to content

OCPBUGS-8009: Revert to legacy toolbox#1203

Merged
openshift-merge-robot merged 2 commits intoopenshift:release-4.13from
travier:release-4.13-backports
Apr 5, 2023
Merged

OCPBUGS-8009: Revert to legacy toolbox#1203
openshift-merge-robot merged 2 commits intoopenshift:release-4.13from
travier:release-4.13-backports

Conversation

@travier
Copy link
Copy Markdown
Member

@travier travier commented Mar 16, 2023

Revert "manifest: Back to rhel toolbox"

We now have a legacy toolbox build in the correct repo.

This reverts commit 3c453e5.


manifest/9/2: Get conmon-rs from rhel-9.2-server-ose-4.13 repo

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 16, 2023

@travier: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

kola-denylist: re-enable luks.* test on !x86_64

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/test-infra repository.

@travier
Copy link
Copy Markdown
Member Author

travier commented Mar 16, 2023

/hold
as we might want to pick up parts of #1202 too

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 16, 2023
@openshift-ci openshift-ci Bot requested review from HuijingHei and jschintag March 16, 2023 11:09
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 16, 2023
@travier travier changed the title kola-denylist: re-enable luks.* test on !x86_64 OCPBUGS-8008: Backports and revert to legacy toolbox Mar 16, 2023
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 16, 2023

@travier: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

OCPBUGS-8008: Backports and revert to legacy toolbox

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/test-infra repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 16, 2023
@openshift-ci-robot
Copy link
Copy Markdown

@travier: This pull request references Jira Issue OCPBUGS-8008, which is invalid:

  • expected the bug to target the "4.13.0" version, but it targets "4.14" instead
  • expected Jira Issue OCPBUGS-8008 to depend on a bug targeting a version in 4.14.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

kola-denylist: re-enable luks.* test on !x86_64

See #1185

(cherry picked from commit 4c3c5d8)


ci: Disable RHCOS 8 builds & tests

(cherry picked from commit a442b06)


ci: Use RHCOS 9 for builds & tests by default

(cherry picked from commit 100d0d4)


ci: Update fetch path for 9.2 builds

(cherry picked from commit 1c662d7)


ci: Cleanup unused versions and whitespace

(cherry picked from commit 227ca9e)

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/test-infra repository.

@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Mar 16, 2023
@travier travier changed the title OCPBUGS-8008: Backports and revert to legacy toolbox OCPBUGS-8009: Backports and revert to legacy toolbox Mar 16, 2023
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 16, 2023

@travier: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

OCPBUGS-8009: Backports and revert to legacy toolbox

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/test-infra repository.

@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Mar 16, 2023

@travier: This pull request references Jira Issue OCPBUGS-8009, which is invalid:

  • bug is open, matching expected state (open)
  • bug target version (4.13.0) matches configured target version for branch (4.13.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • bug has dependents
  • dependent bug RHELBLD-12381 is not in the required OCPBUGS project

All dependent bugs must be part of the OCPBUGS project. If you are backporting a fix that was originally tracked in Bugzilla, follow these steps to handle the backport:

  1. Create a new bug in the OCPBUGS Jira project to match the original bugzilla bug. The important fields that should match are the title, description, target version, and status.
  2. Use the Jira UI to clone the Jira bug, then in the clone bug:
    a. Set the target version to the release you are cherrypicking to.
    b. Add an issue link “is blocked by”, which links to the original jira bug
  3. Use the cherrypick github command to create the cherrypicked PR. Once that new PR is created, retitle the PR and replace the BUG XXX: with OCPBUGS-XXX: to match the new Jira story.

Note that the mirrored bug in OCPBUGSM should not be involved in this process at all.

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

kola-denylist: re-enable luks.* test on !x86_64

See #1185

(cherry picked from commit 4c3c5d8)


ci: Disable RHCOS 8 builds & tests

(cherry picked from commit a442b06)


ci: Use RHCOS 9 for builds & tests by default

(cherry picked from commit 100d0d4)


ci: Update fetch path for 9.2 builds

(cherry picked from commit 1c662d7)


ci: Cleanup unused versions and whitespace

(cherry picked from commit 227ca9e)

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/test-infra repository.

@travier
Copy link
Copy Markdown
Member Author

travier commented Mar 16, 2023

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown

@travier: This pull request references Jira Issue OCPBUGS-8009, which is invalid:

  • expected dependent Jira Issue OCPBUGS-8008 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is POST instead
  • expected dependent Jira Issue OCPBUGS-8008 to target a version in 4.14.0, but it targets "4.14" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

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/test-infra repository.

@HuijingHei
Copy link
Copy Markdown
Contributor

HuijingHei commented Mar 16, 2023

There is #1200 to backport 4c3c5d8, maybe we can close it.

@HuijingHei
Copy link
Copy Markdown
Contributor

/LGTM

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Mar 16, 2023
@HuijingHei
Copy link
Copy Markdown
Contributor

Just minor question, revert to legacy toolbox is not included in this PR, maybe should remove that in the title.

@travier
Copy link
Copy Markdown
Member Author

travier commented Mar 16, 2023

See #1203 (comment). It's in #1203 and I'll add to include it here after it lands in 4.14

@mike-nguyen
Copy link
Copy Markdown
Member

/label backport-risk-assessed
/label cherry-pick-approved

@openshift-ci openshift-ci Bot added 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. labels Mar 20, 2023
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 24, 2023
@travier travier changed the title OCPBUGS-8009: Backports and revert to legacy toolbox OCPBUGS-8009: Revert to legacy toolbox Mar 29, 2023
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 29, 2023

@travier: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

OCPBUGS-8009: Revert to legacy toolbox

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/test-infra repository.

@openshift-ci-robot
Copy link
Copy Markdown

@travier: This pull request references Jira Issue OCPBUGS-8009, which is invalid:

  • expected dependent Jira Issue OCPBUGS-8008 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is POST instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Revert "manifest: Back to rhel toolbox"

This reverts commit 3c453e5.

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/test-infra repository.

@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 29, 2023
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 29, 2023
@HuijingHei
Copy link
Copy Markdown
Contributor

/retest

@HuijingHei
Copy link
Copy Markdown
Contributor

https://github.com/openshift/os/blob/release-4.13/rhcos-packages.yaml#L18 includes toolbox, they might be duplicated?

@travier
Copy link
Copy Markdown
Member Author

travier commented Mar 30, 2023

release-4.13/rhcos-packages.yaml#L18 includes toolbox, they might be duplicated?

This line above is to make sure the toolbox package is included.

This PR is to make sure it comes from the right repo so that we get the right version of it.

travier added 2 commits March 30, 2023 09:56
We now have a legacy toolbox build in the correct repo.

This reverts commit 3c453e5.
@travier travier force-pushed the release-4.13-backports branch from 9b6f697 to 493984a Compare March 30, 2023 07:57
@openshift-ci-robot
Copy link
Copy Markdown

@travier: This pull request references Jira Issue OCPBUGS-8009, which is invalid:

  • expected dependent Jira Issue OCPBUGS-8008 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is POST instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Revert "manifest: Back to rhel toolbox"

We now have a legacy toolbox build in the correct repo.

This reverts commit 3c453e5.


manifest/9/2: Get conmon-rs from rhel-9.2-server-ose-4.13 repo

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/test-infra repository.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 30, 2023

@travier: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

OCPBUGS-8009: Revert to legacy toolbox

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/test-infra repository.

@mike-nguyen
Copy link
Copy Markdown
Member

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Apr 3, 2023
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 3, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: HuijingHei, mike-nguyen, travier

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 [HuijingHei,mike-nguyen,travier]

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

@sdodson
Copy link
Copy Markdown
Member

sdodson commented Apr 4, 2023

/label bugzilla/valid-bug
/label jira/valid-bug

@openshift-ci openshift-ci Bot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Apr 4, 2023
@travier
Copy link
Copy Markdown
Member Author

travier commented Apr 5, 2023

/jira refresh

@openshift-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Apr 5, 2023
@openshift-ci-robot
Copy link
Copy Markdown

@travier: This pull request references Jira Issue OCPBUGS-8009, which is valid.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.13.0) matches configured target version for branch (4.13.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-8008 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-8008 targets the "4.14.0" version, which is one of the valid target versions: 4.14.0
  • bug has dependents

Requesting review from QA contact:
/cc @mike-nguyen

Details

In response to this:

/jira refresh

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/test-infra repository.

@openshift-ci openshift-ci Bot requested a review from mike-nguyen April 5, 2023 12:23
@travier
Copy link
Copy Markdown
Member Author

travier commented Apr 5, 2023

I've manually verified toolbox in 4.14 and that conmon-rs is there in 4.13. Everything should be ready for this one.
/unhold

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 5, 2023
@travier
Copy link
Copy Markdown
Member Author

travier commented Apr 5, 2023

CI is failure here is expected for now.
/override ci/prow/rhcos-92-build-test-metal
/override ci/prow/rhcos-92-build-test-qemu
/override ci/prow/scos-9-build-test-metal
/override ci/prow/scos-9-build-test-qemu

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 5, 2023

@travier: Overrode contexts on behalf of travier: ci/prow/rhcos-92-build-test-metal, ci/prow/rhcos-92-build-test-qemu, ci/prow/scos-9-build-test-metal, ci/prow/scos-9-build-test-qemu

Details

In response to this:

CI is failure here is expected for now.
/override ci/prow/rhcos-92-build-test-metal
/override ci/prow/rhcos-92-build-test-qemu
/override ci/prow/scos-9-build-test-metal
/override ci/prow/scos-9-build-test-qemu

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/test-infra repository.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 5, 2023

@travier: all tests passed!

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/test-infra repository. I understand the commands that are listed here.

@openshift-merge-robot openshift-merge-robot merged commit ee2b02f into openshift:release-4.13 Apr 5, 2023
@openshift-ci-robot
Copy link
Copy Markdown

@travier: Jira Issue OCPBUGS-8009: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-8009 has been moved to the MODIFIED state.

Details

In response to this:

Revert "manifest: Back to rhel toolbox"

We now have a legacy toolbox build in the correct repo.

This reverts commit 3c453e5.


manifest/9/2: Get conmon-rs from rhel-9.2-server-ose-4.13 repo

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/test-infra repository.

@travier travier deleted the release-4.13-backports branch April 5, 2023 13:30
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. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. 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.

6 participants