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

Bug 2047935: bump RHCOS 4.11 bootimage metadata #5729

Merged

Conversation

aaradhak
Copy link
Contributor

@aaradhak aaradhak commented Mar 19, 2022

These changes will update the RHCOS 4.11 bootimage metadata in the installer.
This change includes fixes for the following BZs:

Bug 2032717: Unable to download ignition after coreos-installer install --copy-network

Changes generated with:

plume cosa2stream --target data/data/coreos/rhcos.json --distro rhcos  x86_64=411.85.202203181601-0 s390x=411.85.202203181515-0 ppc64le=411.85.202203181612-0 --url https://rhcos-redirector.apps.art.xq1c.p1.openshiftapps.com/art/storage/releases --no-signatures

@openshift-ci openshift-ci bot added the bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. label Mar 19, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 19, 2022

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.11.0) matches configured target release for branch (4.11.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

Requesting review from QA contact:
/cc @HuijingHei

In response to this:

Bug 2032717: bump RHCOS 4.11 bootimage metadata

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 added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Mar 19, 2022
@openshift-ci openshift-ci bot requested review from HuijingHei and lucab March 19, 2022 00:29
These changes will update the RHCOS 4.11 bootimage metadata in the installer.
This change includes fixes for the following BZs:

Bug 2047935 - [4.11] Bootimage bump tracker

This change will also introduce artifacts for for Aliyun, AWS GovCloud regions,
and Nutanix.

Changes generated with:
```
plume cosa2stream --target data/data/coreos/rhcos.json --distro rhcos  x86_64=411.85.202203181601-0 s390x=411.85.202203181515-0 ppc64le=411.85.202203181612-0 --url https://rhcos-redirector.apps.art.xq1c.p1.openshiftapps.com/art/storage/releases --no-signatures

```
@aaradhak aaradhak changed the title Bug 2032717: bump RHCOS 4.11 bootimage metadata Bug 2047935: bump RHCOS 4.11 bootimage metadata Mar 19, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 19, 2022

@aaradhak: This pull request references Bugzilla bug 2047935, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.11.0) matches configured target release for branch (4.11.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

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

In response to this:

Bug 2047935: bump RHCOS 4.11 bootimage metadata

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 March 19, 2022 01:34
@aaradhak
Copy link
Contributor Author

/bugzilla refresh

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 19, 2022

@aaradhak: This pull request references Bugzilla bug 2047935, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.11.0) matches configured target release for branch (4.11.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

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.

@staebler
Copy link
Contributor

/test e2e-aws

@aaradhak
Copy link
Contributor Author

/retest

@miabbott
Copy link
Member

/test e2e-azure
/test e2e-gcp
/test e2e-vsphere
/test e2e-metal-ipi-ovn-dualstack
/test e2e-metal-ipi-ovn-ipv6
/test e2e-metal-ipi-virtualmedia

@miabbott
Copy link
Member

/retest

1 similar comment
@HuijingHei
Copy link
Contributor

/retest

@miabbott
Copy link
Member

e2e-aws-upgrade shows that the [sig-scheduling][Early] The HAProxy router pods should be scheduled on different nodes [Suite:openshift/conformance/parallel] test is failing

A search turns up there is a BZ filed for this already - https://bugzilla.redhat.com/show_bug.cgi?id=2062459

This doesn't appear to to be related to the bootimage bump; the cluster still installed successfully

@miabbott
Copy link
Member

e2e-azure-upi has been red/yellow for over a week. The failing tests on this run are:

[sig-arch][bz-etcd][Late] Alerts alert/etcdHighNumberOfFailedGRPCRequests should not be at or above info [Suite:openshift/conformance/parallel]
[sig-network-edge][Conformance][Area:Networking][Feature:Router] The HAProxy router should pass the gRPC interoperability tests [Suite:openshift/conformance/parallel/minimal]
[sig-network-edge][Conformance][Area:Networking][Feature:Router] The HAProxy router should pass the h2spec conformance tests [Suite:openshift/conformance/parallel/minimal]
[sig-network-edge][Conformance][Area:Networking][Feature:Router] The HAProxy router should pass the http2 tests [Suite:openshift/conformance/parallel/minimal]
[sig-storage] In-tree Volumes [Driver: azure-disk] [Testpattern: Dynamic PV (delayed binding)] topology should provision a volume and schedule a pod with AllowedTopologies [Suite:openshift/conformance/parallel] [Suite:k8s]

These look like the same tests that have been failing in other runs of the job and don't appear to be correlated with this PR.

@miabbott
Copy link
Member

e2e-crc has been red/yellow for over a week. The failing job can't even start successfully as the e2e-crc-openshift-e2e-gcp-crc-test step is failing:

++ curl -L https://mirror.openshift.com/pub/openshift-v4/x86_64/clients/ocp-dev-preview//candidate-4.10/release.txt
++ sed -n 's/^ *Version: *//p'
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100    52  100    52    0     0     22      0  0:00:02  0:00:02 --:--:--    22
100    52  100    52    0     0     22      0  0:00:02  0:00:02 --:--:--    22
Unable to determine an OpenShift release version.  You may want to set the OPENSHIFT_VERSION environment variable explicitly.
+ OPENSHIFT_RELEASE_VERSION=
+ test -n ''
+ echo 'Unable to determine an OpenShift release version.  You may want to set the OPENSHIFT_VERSION environment variable explicitly.'
+ exit 1
+ jobs=($(jobs -p))
++ jobs -p
+ '[' -n '' ']'
+ true
{"component":"entrypoint","error":"wrapped process failed: exit status 1","file":"k8s.io/test-infra/prow/entrypoint/run.go:80","func":"k8s.io/test-infra/prow/entrypoint.Options.Run","level":"error","msg":"Error executing test process","severity":"error","time":"2022-03-22T04:43:44Z"}
error: failed to execute wrapped command: exit status 1

This looks unrelated to this PR.

@miabbott
Copy link
Member

e2e-ibmcloud has been red/yellow for over a week. It looks like the e2e-ibmcloud-ipi-install-install is failing because it can't setup the DNS config:

level=fatal msg=failed to fetch Common Manifests: failed to fetch dependency of "Common Manifests": failed to generate asset "DNS Config": failed ot get DNS zone ID: failed to list DNS zones: Exactly one of ApiKey or RefreshToken must be specified.

This looks unrelated to this PR

@miabbott
Copy link
Member

miabbott commented Mar 23, 2022

e2e-metal-ipi-ovn-ipv6 looks like it has been mostly red for over a week. It looks like the baremetalds-devscripts-setup step is failing but I'm having a hard time sifting through the logs.

The failure modes for the past failed jobs are not consistent, either.

From what I can tell in the journal from a control plane node in the gather-extra subdir, it looks like this job is using it's own definition for boot images, because the output from the pivot to the new machine-os-content shows packages upgraded from el8_4 to el8_5.

NetworkManager 1:1.30.0-13.el8_4 -> 1:1.32.10-4.el8

So I'm not sure this is a good job to validate the new bootimage that is introduced by this change.

@miabbott
Copy link
Member

okd-e2e-aws-upgrade isn't valid for this PR since OKD uses FCOS.

@miabbott
Copy link
Member

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 23, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: miabbott

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 Mar 23, 2022
@miabbott
Copy link
Member

e2e-azure-upi has been red/yellow for over a week. The failing tests on this run are:

[sig-arch][bz-etcd][Late] Alerts alert/etcdHighNumberOfFailedGRPCRequests should not be at or above info [Suite:openshift/conformance/parallel]
[sig-network-edge][Conformance][Area:Networking][Feature:Router] The HAProxy router should pass the gRPC interoperability tests [Suite:openshift/conformance/parallel/minimal]
[sig-network-edge][Conformance][Area:Networking][Feature:Router] The HAProxy router should pass the h2spec conformance tests [Suite:openshift/conformance/parallel/minimal]
[sig-network-edge][Conformance][Area:Networking][Feature:Router] The HAProxy router should pass the http2 tests [Suite:openshift/conformance/parallel/minimal]
[sig-storage] In-tree Volumes [Driver: azure-disk] [Testpattern: Dynamic PV (delayed binding)] topology should provision a volume and schedule a pod with AllowedTopologies [Suite:openshift/conformance/parallel] [Suite:k8s]

These look like the same tests that have been failing in other runs of the job and don't appear to be correlated with this PR.

Filed https://bugzilla.redhat.com/show_bug.cgi?id=2067323 for the HAProxy failures

https://bugzilla.redhat.com/show_bug.cgi?id=2066865 exists for the Dynamic PV failure

@miabbott
Copy link
Member

e2e-ibmcloud has been red/yellow for over a week. It looks like the e2e-ibmcloud-ipi-install-install is failing because it can't setup the DNS config:

level=fatal msg=failed to fetch Common Manifests: failed to fetch dependency of "Common Manifests": failed to generate asset "DNS Config": failed ot get DNS zone ID: failed to list DNS zones: Exactly one of ApiKey or RefreshToken must be specified.

This looks unrelated to this PR

Looks like https://bugzilla.redhat.com/show_bug.cgi?id=2066463

@openshift-bot
Copy link
Contributor

/retest-required

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

5 similar comments
@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@aaradhak
Copy link
Contributor Author

/retest /override ci/prow/e2e-aws-upgrade

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 26, 2022

@aaradhak: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

  • /test e2e-aws
  • /test e2e-aws-upgrade
  • /test e2e-gcp-upgrade
  • /test e2e-metal-ipi-ovn-ipv6-required
  • /test gofmt
  • /test golint
  • /test govet
  • /test images
  • /test okd-images
  • /test okd-unit
  • /test okd-verify-codegen
  • /test openstack-manifests
  • /test shellcheck
  • /test tf-lint
  • /test unit
  • /test verify-codegen
  • /test verify-vendor
  • /test yaml-lint

The following commands are available to trigger optional jobs:

  • /test e2e-alibaba
  • /test e2e-aws-disruptive
  • /test e2e-aws-fips
  • /test e2e-aws-proxy
  • /test e2e-aws-shared-vpc
  • /test e2e-aws-single-node
  • /test e2e-aws-upi
  • /test e2e-aws-upi-proxy
  • /test e2e-aws-workers-rhel8
  • /test e2e-azure
  • /test e2e-azure-resourcegroup
  • /test e2e-azure-shared-vpc
  • /test e2e-azure-upi
  • /test e2e-azurestack
  • /test e2e-azurestack-upi
  • /test e2e-crc
  • /test e2e-gcp
  • /test e2e-gcp-shared-vpc
  • /test e2e-gcp-upi
  • /test e2e-gcp-upi-xpn
  • /test e2e-ibmcloud
  • /test e2e-libvirt
  • /test e2e-metal
  • /test e2e-metal-assisted
  • /test e2e-metal-ipi
  • /test e2e-metal-ipi-ovn-dualstack
  • /test e2e-metal-ipi-ovn-ipv6
  • /test e2e-metal-ipi-swapped-hosts
  • /test e2e-metal-ipi-virtualmedia
  • /test e2e-metal-single-node-live-iso
  • /test e2e-openstack
  • /test e2e-openstack-kuryr
  • /test e2e-openstack-parallel
  • /test e2e-openstack-proxy
  • /test e2e-openstack-upi
  • /test e2e-ovirt
  • /test e2e-vsphere
  • /test e2e-vsphere-upi
  • /test okd-e2e-aws
  • /test okd-e2e-aws-upgrade
  • /test okd-e2e-gcp
  • /test okd-e2e-gcp-upgrade
  • /test okd-e2e-vsphere
  • /test tf-fmt

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-installer-master-e2e-alibaba
  • pull-ci-openshift-installer-master-e2e-aws
  • pull-ci-openshift-installer-master-e2e-aws-disruptive
  • pull-ci-openshift-installer-master-e2e-aws-fips
  • pull-ci-openshift-installer-master-e2e-aws-proxy
  • pull-ci-openshift-installer-master-e2e-aws-shared-vpc
  • pull-ci-openshift-installer-master-e2e-aws-single-node
  • pull-ci-openshift-installer-master-e2e-aws-upgrade
  • pull-ci-openshift-installer-master-e2e-aws-workers-rhel8
  • pull-ci-openshift-installer-master-e2e-azure
  • pull-ci-openshift-installer-master-e2e-azure-resourcegroup
  • pull-ci-openshift-installer-master-e2e-azure-shared-vpc
  • pull-ci-openshift-installer-master-e2e-azurestack
  • pull-ci-openshift-installer-master-e2e-crc
  • pull-ci-openshift-installer-master-e2e-gcp
  • pull-ci-openshift-installer-master-e2e-gcp-shared-vpc
  • pull-ci-openshift-installer-master-e2e-gcp-upgrade
  • pull-ci-openshift-installer-master-e2e-gcp-upi-xpn
  • pull-ci-openshift-installer-master-e2e-ibmcloud
  • pull-ci-openshift-installer-master-e2e-libvirt
  • pull-ci-openshift-installer-master-e2e-metal-assisted
  • pull-ci-openshift-installer-master-e2e-metal-ipi-ovn-ipv6
  • pull-ci-openshift-installer-master-e2e-metal-single-node-live-iso
  • pull-ci-openshift-installer-master-e2e-openstack
  • pull-ci-openshift-installer-master-e2e-openstack-kuryr
  • pull-ci-openshift-installer-master-e2e-openstack-parallel
  • pull-ci-openshift-installer-master-e2e-openstack-proxy
  • pull-ci-openshift-installer-master-e2e-ovirt
  • pull-ci-openshift-installer-master-e2e-vsphere
  • pull-ci-openshift-installer-master-gofmt
  • pull-ci-openshift-installer-master-golint
  • pull-ci-openshift-installer-master-govet
  • pull-ci-openshift-installer-master-images
  • pull-ci-openshift-installer-master-okd-e2e-aws
  • pull-ci-openshift-installer-master-okd-e2e-aws-upgrade
  • pull-ci-openshift-installer-master-okd-images
  • pull-ci-openshift-installer-master-okd-unit
  • pull-ci-openshift-installer-master-okd-verify-codegen
  • pull-ci-openshift-installer-master-openstack-manifests
  • pull-ci-openshift-installer-master-shellcheck
  • pull-ci-openshift-installer-master-tf-fmt
  • pull-ci-openshift-installer-master-tf-lint
  • pull-ci-openshift-installer-master-unit
  • pull-ci-openshift-installer-master-verify-codegen
  • pull-ci-openshift-installer-master-verify-vendor
  • pull-ci-openshift-installer-master-yaml-lint

In response to this:

/retest /override ci/prow/e2e-aws-upgrade

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

/retest-required

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

8 similar comments
@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 27, 2022

@aaradhak: 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/okd-e2e-aws-upgrade 50892dc link false /test okd-e2e-aws-upgrade
ci/prow/e2e-ibmcloud 50892dc link false /test e2e-ibmcloud
ci/prow/e2e-metal-ipi-ovn-ipv6 50892dc link false /test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-azure-upi 50892dc link false /test e2e-azure-upi
ci/prow/e2e-crc 50892dc link false /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-bot
Copy link
Contributor

/retest-required

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

8 similar comments
@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-merge-robot openshift-merge-robot merged commit 0ef8d76 into openshift:master Mar 28, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 28, 2022

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

Bugzilla bug 2047935 has been moved to the MODIFIED state.

In response to this:

Bug 2047935: bump RHCOS 4.11 bootimage metadata

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 Apr 20, 2022

@aaradhak: Bugzilla bug 2047935 is in an unrecognized state (VERIFIED) and will not be moved to the MODIFIED state.

In response to this:

Bug 2047935: bump RHCOS 4.11 bootimage metadata

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. bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants