Skip to content

Conversation

@mike-nguyen
Copy link
Member

Add test to verify that rhaos package versions match the OpenShift
version.

This is a cherry-pick of #635

Add test to verify that rhaos package versions match the OpenShift
version.
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 24, 2021

@mike-nguyen: 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:

[release-4.7] test: add test to check rhaos package versions

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
Contributor

openshift-ci bot commented Sep 24, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mike-nguyen

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:

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 requested review from cgwalters and zonggen September 24, 2021 18:13
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 24, 2021
@mike-nguyen
Copy link
Member Author

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 30, 2021

@mike-nguyen: The following test 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/build-test-qemu 0344cb5 link true /test build-test-qemu

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.

@mike-nguyen
Copy link
Member Author

Sep 30 19:52:00 qemu0 kola-runext-misc-ro.sh[1566]: ++ rpm -qa
Sep 30 19:52:01 qemu0 kola-runext-misc-ro.sh[1566]: + [[ -n runc-1.0.0-96.rhaos4.8.gitcd80260.el8.x86_64 ]]
Sep 30 19:52:01 qemu0 kola-runext-misc-ro.sh[1566]: + fatal 'Error: rhaos packages do not match OpenShift version'
Sep 30 19:52:01 qemu0 kola-runext-misc-ro.sh[1566]: + echo 'Error: rhaos packages do not match OpenShift version'

4.7 build has rhaos4.8 packages

@miabbott
Copy link
Member

miabbott commented Oct 1, 2021

4.7 build has rhaos4.8 packages

🤔 umm...I don't know how this is happening...we'll need to investigate the tagging situation with Node/ART

@miabbott
Copy link
Member

miabbott commented Oct 2, 2021

thinking umm...I don't know how this is happening...we'll need to investigate the tagging situation with Node/ART

It looks like we started using the rhaos4.6 version then started using the rhaos4.8 version around May 2021 and never looked back:

$ ./pkg_report.py --release rhcos-4.7 --package runc
47.82.202010110827-0 = runc-1.0.0-81.rhaos4.6.git5b757d4.el8.x86_64 on 2020-10-11 08:27:00
47.83.202102042048-0 = runc-1.0.0-82.rhaos4.6.git086e841.el8.x86_64 on 2021-02-04 20:48:00
47.83.202103051045-0 = runc-1.0.0-83.rhaos4.6.git8c2e7c8.el8.x86_64 on 2021-03-05 10:45:00
47.83.202104280942-0 = runc-1.0.0-95.rhaos4.8.gitcd80260.el8.x86_64 on 2021-04-28 09:42:00
47.83.202105041745-0 = runc-1.0.0-83.rhaos4.6.git8c2e7c8.el8.x86_64 on 2021-05-04 17:45:00
47.83.202105061035-0 = runc-1.0.0-95.rhaos4.8.gitcd80260.el8.x86_64 on 2021-05-06 10:35:00
47.83.202105200135-0 = runc-1.0.0-96.rhaos4.8.gitcd80260.el8.x86_64 on 2021-05-20 01:35:00

Coincides with OCP 4.7.11

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 31, 2021
@openshift-bot
Copy link

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 30, 2022
@openshift-bot
Copy link

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci bot closed this Mar 1, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 1, 2022

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.

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. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants