Bug 1935174: RHCOS bump for LUKS, prjquota, etc #4791

miabbott · 2021-03-25T19:12:35Z

This bumps the boot image to to include fixes for the following:

BZ#1922417 - Issue configuring nodes with VLAN and teaming
BZ#1940966 - [4.7.z] prjquota is dropped from rootflags if rootfs is reprovisioned
BZ#1941760 - [4.7.z] rootfs too small when enabling NBDE (redo)
BZ#1942706 - [4.7.z] support new AWS region ap-northeast-3

This bumps the boot image to to include fixes for the following: BZ#1922417 - Issue configuring nodes with VLAN and teaming BZ#1940966 - [4.7.z] prjquota is dropped from rootflags if rootfs is reprovisioned BZ#1941760 - [4.7.z] rootfs too small when enabling NBDE (redo) BZ#1942706 - [4.7.z] support new AWS region ap-northeast-3

openshift-ci-robot · 2021-03-25T19:12:45Z

@miabbott: This pull request references Bugzilla bug 1935174, which is invalid:

expected dependent Bugzilla bug 1922417 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 1940966 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is MODIFIED instead
expected dependent Bugzilla bug 1941760 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 1942706 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ASSIGNED instead
expected dependent Bugzilla bug 1922417 to target a release in 4.8.0, but it targets "4.7.z" instead
expected dependent Bugzilla bug 1940966 to target a release in 4.8.0, but it targets "4.7.z" instead
expected dependent Bugzilla bug 1941760 to target a release in 4.8.0, but it targets "4.7.z" instead
expected dependent Bugzilla bug 1942706 to target a release in 4.8.0, but it targets "4.7.z" instead
expected dependent Bugzilla bug 1934863 to target a release in 4.8.0, but it targets "4.7.z" instead

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

In response to this:

Bug 1935174: RHCOS bump for LUKS, prjquota, etc

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.

miabbott · 2021-03-25T19:13:21Z

/assign jlebon

jlebon · 2021-03-25T19:30:21Z

/lgtm

miabbott · 2021-03-25T21:52:24Z

e2e-metal-assisted appears to be perma-failing on https://bugzilla.redhat.com/show_bug.cgi?id=1939560

e2e-kubevirt has been perma-failing for the last 10 days; filed https://bugzilla.redhat.com/show_bug.cgi?id=1943362

e2e-openstack looks like it failed on https://bugzilla.redhat.com/show_bug.cgi?id=1926269

e2e-aws failing on [sig-api-machinery][Feature:APIServer][Late] kubelet terminates kube-apiserver gracefully [Suite:openshift/conformance/parallel] which is linked to https://bugzilla.redhat.com/show_bug.cgi?id=1926484 in VERIFIED state. So I filed a new one https://bugzilla.redhat.com/show_bug.cgi?id=1943364

Will examine other failures later.

/retest

openshift-bot · 2021-03-26T01:00:14Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2021-03-26T01:00:22Z

@openshift-bot: This pull request references Bugzilla bug 1935174, which is invalid:

expected dependent Bugzilla bug 1922417 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 1940966 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is MODIFIED instead
expected dependent Bugzilla bug 1941760 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 1942706 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 1922417 to target a release in 4.8.0, but it targets "4.7.z" instead
expected dependent Bugzilla bug 1940966 to target a release in 4.8.0, but it targets "4.7.z" instead
expected dependent Bugzilla bug 1941760 to target a release in 4.8.0, but it targets "4.7.z" instead
expected dependent Bugzilla bug 1942706 to target a release in 4.8.0, but it targets "4.7.z" instead
expected dependent Bugzilla bug 1934863 to target a release in 4.8.0, but it targets "4.7.z" instead

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

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

staebler · 2021-03-26T03:51:23Z

/approve
/override ci/prow/e2e-kubevirt
/override ci/prow/e2e-metal-assisted
/override ci/prow/e2e-openstack-ipi
/override ci/prow/e2e-vsphere-upi

openshift-ci-robot · 2021-03-26T03:51:39Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: staebler

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:

~~OWNERS~~ [staebler]

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

openshift-ci-robot · 2021-03-26T03:51:43Z

@staebler: Overrode contexts on behalf of staebler: ci/prow/e2e-kubevirt, ci/prow/e2e-metal-assisted, ci/prow/e2e-openstack-ipi, ci/prow/e2e-vsphere-upi

In response to this:

/approve
/override ci/prow/e2e-kubevirt
/override ci/prow/e2e-metal-assisted
/override ci/prow/e2e-openstack-ipi
/override ci/prow/e2e-vsphere-upi

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-bot · 2021-03-26T04:00:22Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2021-03-26T04:13:12Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2021-03-26T06:23:13Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2021-03-26T08:20:12Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2021-03-26T10:17:12Z

/retest

Please review the full test history for this PR and help us cut down flakes.

miabbott · 2021-03-26T13:06:05Z

Regarding the BZ status:

We can probably get 1922417, 1940966, 1941760 verified today or early next week.

1942706 is the support for ap-northeast-3 which is covered by this PR.

All of the referenced BZs are targeting 4.7.z as they are expected to be fixed in that release, so I don't understand why the bot complains about them.

openshift-bot · 2021-03-27T01:00:12Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2021-03-27T01:00:20Z

@openshift-bot: This pull request references Bugzilla bug 1935174, which is invalid:

expected dependent Bugzilla bug 1942706 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 1922417 to target a release in 4.8.0, but it targets "4.7.z" instead
expected dependent Bugzilla bug 1940966 to target a release in 4.8.0, but it targets "4.7.z" instead
expected dependent Bugzilla bug 1941760 to target a release in 4.8.0, but it targets "4.7.z" instead
expected dependent Bugzilla bug 1942706 to target a release in 4.8.0, but it targets "4.7.z" instead
expected dependent Bugzilla bug 1934863 to target a release in 4.8.0, but it targets "4.7.z" instead

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

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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-bot · 2021-03-28T01:00:59Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2021-03-28T01:01:08Z

@openshift-bot: This pull request references Bugzilla bug 1935174, which is invalid:

expected dependent Bugzilla bug 1942706 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 1922417 to target a release in 4.8.0, but it targets "4.7.z" instead
expected dependent Bugzilla bug 1940966 to target a release in 4.8.0, but it targets "4.7.z" instead
expected dependent Bugzilla bug 1941760 to target a release in 4.8.0, but it targets "4.7.z" instead
expected dependent Bugzilla bug 1942706 to target a release in 4.8.0, but it targets "4.7.z" instead
expected dependent Bugzilla bug 1934863 to target a release in 4.8.0, but it targets "4.7.z" instead

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

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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-bot · 2021-03-29T01:00:59Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2021-03-29T01:01:08Z

@openshift-bot: This pull request references Bugzilla bug 1935174, which is invalid:

expected dependent Bugzilla bug 1942706 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 1922417 to target a release in 4.8.0, but it targets "4.7.z" instead
expected dependent Bugzilla bug 1940966 to target a release in 4.8.0, but it targets "4.7.z" instead
expected dependent Bugzilla bug 1941760 to target a release in 4.8.0, but it targets "4.7.z" instead
expected dependent Bugzilla bug 1942706 to target a release in 4.8.0, but it targets "4.7.z" instead
expected dependent Bugzilla bug 1934863 to target a release in 4.8.0, but it targets "4.7.z" instead

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

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

miabbott · 2021-03-29T17:59:44Z

/hold

It looks like the AWS SDK needs to be bumped to support the ap-northeast-3 region

staebler · 2021-03-29T19:18:56Z

/hold
It looks like the AWS SDK needs to be bumped to support the ap-northeast-3 region

Why does this PR need to be held for the AWS SDK bump?

When building this locally, the ap-northeast-3 region isn't a selectable region when doing openshift-install create cluster

Right. But adding support in the RHCOS image is separate from the installer offering the region as a valid region.

miabbott · 2021-03-30T13:09:50Z

/hold cancel

@staebler has a different approach to support new AWS regions in #4801

We should be able to land this PR independently of #4801

miabbott · 2021-03-30T15:34:19Z

@staebler could you override the invalid bug flag? The associated BZs are fixed in RHCOS 4.7 (except for the ap-northeast-3 one) and are targeting 4.7.z

(They actually were incorrectly attached to the last 4.7.z errata that went out, so the sooner we can get this change shipped the better)

staebler · 2021-03-30T16:38:03Z

@staebler could you override the invalid bug flag? The associated BZs are fixed in RHCOS 4.7 (except for the ap-northeast-3 one) and are targeting 4.7.z

(They actually were incorrectly attached to the last 4.7.z errata that went out, so the sooner we can get this change shipped the better)

I can try. I've never done that before. Although, this needs cherry-pick approval anyway. Would it be better for the patch manager to override the invalid-bug label?

miabbott · 2021-03-30T19:59:50Z

I can try. I've never done that before. Although, this needs cherry-pick approval anyway. Would it be better for the patch manager to override the invalid-bug label?

Looks like it worked! Next time I'll be more patient and wait for the patch manager.

miabbott · 2021-03-31T15:21:26Z

/bugzilla refresh

openshift-ci-robot · 2021-03-31T15:32:53Z

@miabbott: This pull request references Bugzilla bug 1935174, which is invalid:

expected Bugzilla bug 1935174 to depend on a bug targeting a release in 4.8.0 and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but no dependents were found

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

In response to this:

/bugzilla 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.

miabbott · 2021-03-31T18:39:20Z

/bugzilla refresh

openshift-ci-robot · 2021-03-31T18:39:24Z

@miabbott: This pull request references Bugzilla bug 1935174, which is invalid:

expected the bug to target the "4.7.z" release, but it targets "---" instead

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

In response to this:

/bugzilla 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.

miabbott · 2021-03-31T18:58:09Z

/bugzilla refresh

openshift-ci-robot · 2021-03-31T18:58:16Z

@miabbott: This pull request references Bugzilla bug 1935174, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target release (4.7.z) matches configured target release for branch (4.7.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
dependent bug Bugzilla bug 1934557 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
dependent Bugzilla bug 1934557 targets the "4.8.0" release, which is one of the valid target releases: 4.8.0
bug has dependents

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

In response to this:

/bugzilla 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-bot · 2021-04-10T06:46:24Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2021-04-10T06:58:20Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2021-04-10T08:42:18Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2021-04-10T09:08:18Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2021-04-10T11:05:32Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2021-04-10T14:59:27Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-ci · 2021-04-10T16:09:22Z

@miabbott: The following test failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
ci/prow/e2e-crc	`2c06ddb`	link	`/test e2e-crc`

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

openshift-ci-robot · 2021-04-10T16:24:23Z

@miabbott: All pull requests linked via external trackers have merged:

openshift/installer#4791

Bugzilla bug 1935174 has been moved to the MODIFIED state.

In response to this:

Bug 1935174: RHCOS bump for LUKS, prjquota, etc

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 added the bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. label Mar 25, 2021

openshift-ci-robot added the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Mar 25, 2021

openshift-ci-robot requested review from jhixson74 and jstuever March 25, 2021 19:12

openshift-ci-robot assigned jlebon Mar 25, 2021

openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 25, 2021

openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 26, 2021

miabbott mentioned this pull request Mar 29, 2021

Bump the AWS SDK module to v1.37.24 openshift/terraform-provider-aws#5

Closed

openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 30, 2021

staebler removed the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Mar 30, 2021

openshift-ci-robot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Mar 31, 2021

openshift-ci-robot requested a review from mike-nguyen March 31, 2021 18:58

russellb added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Apr 9, 2021

openshift-merge-robot merged commit fae650e into openshift:release-4.7 Apr 10, 2021

Bug 1935174: RHCOS bump for LUKS, prjquota, etc #4791

Bug 1935174: RHCOS bump for LUKS, prjquota, etc #4791

Conversation

miabbott commented Mar 25, 2021

openshift-ci-robot commented Mar 25, 2021

miabbott commented Mar 25, 2021

jlebon commented Mar 25, 2021

miabbott commented Mar 25, 2021

openshift-bot commented Mar 26, 2021

openshift-ci-robot commented Mar 26, 2021

staebler commented Mar 26, 2021

openshift-ci-robot commented Mar 26, 2021

openshift-ci-robot commented Mar 26, 2021

openshift-bot commented Mar 26, 2021

openshift-bot commented Mar 26, 2021

openshift-bot commented Mar 26, 2021

openshift-bot commented Mar 26, 2021

openshift-bot commented Mar 26, 2021

miabbott commented Mar 26, 2021

openshift-bot commented Mar 27, 2021

openshift-ci-robot commented Mar 27, 2021

openshift-bot commented Mar 28, 2021

openshift-ci-robot commented Mar 28, 2021

openshift-bot commented Mar 29, 2021

openshift-ci-robot commented Mar 29, 2021

miabbott commented Mar 29, 2021

staebler commented Mar 29, 2021

miabbott commented Mar 30, 2021

miabbott commented Mar 30, 2021 • edited

staebler commented Mar 30, 2021

miabbott commented Mar 30, 2021

miabbott commented Mar 31, 2021

openshift-ci-robot commented Mar 31, 2021

miabbott commented Mar 31, 2021

openshift-ci-robot commented Mar 31, 2021

miabbott commented Mar 31, 2021

openshift-ci-robot commented Mar 31, 2021

openshift-bot commented Apr 10, 2021

openshift-bot commented Apr 10, 2021

openshift-bot commented Apr 10, 2021

openshift-bot commented Apr 10, 2021

openshift-bot commented Apr 10, 2021

openshift-bot commented Apr 10, 2021

openshift-ci bot commented Apr 10, 2021 • edited

openshift-ci-robot commented Apr 10, 2021

miabbott commented Mar 30, 2021 •

edited

openshift-ci bot commented Apr 10, 2021 •

edited