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.

Sign up for GitHub

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

Jump to bottom

OCPBUGS-11789: update RHCOS 4.13 bootimage metadata to 413.92.202304131328-0 #7093

Merged
merged 1 commit into from
Apr 14, 2023
Merged

OCPBUGS-11789: update RHCOS 4.13 bootimage metadata to 413.92.202304131328-0 #7093

merged 1 commit into from
Apr 14, 2023

Conversation

mike-nguyen
Copy link
Member

These changes will update the RHCOS 4.13 bootimage metadata.

This change was generated using:

plume cosa2stream --target data/data/coreos/rhcos.json --distro rhcos --no-signatures --name 4.13-9.2 --url https://rhcos.mirror.openshift.com/art/storage/prod/streams x86_64=413.92.202304131328-0 aarch64=413.92.202304131328-0 s390x=413.92.202304131328-0 ppc64le=413.92.202304131328-0

@mike-nguyen
update RHCOS 4.13 bootimage metadata to 413.92.202304131328-0
a9dffbc 
These changes will update the RHCOS 4.13 bootimage metadata.

This change was generated using:
```
plume cosa2stream --target data/data/coreos/rhcos.json --distro rhcos --no-signatures --name 4.13-9.2 --url https://rhcos.mirror.openshift.com/art/storage/prod/streams x86_64=413.92.202304131328-0 aarch64=413.92.202304131328-0 s390x=413.92.202304131328-0 ppc64le=413.92.202304131328-0
```
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Apr 13, 2023
@openshift-ci-robot
Copy link
Contributor

@mike-nguyen: This pull request references Jira Issue OCPBUGS-11789, which is invalid:

  • expected the bug to target the "4.13.0" version, but it targets "4.13.z" instead
  • expected dependent Jira Issue OCPBUGS-11788 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.

In response to this:

These changes will update the RHCOS 4.13 bootimage metadata.

This change was generated using:

plume cosa2stream --target data/data/coreos/rhcos.json --distro rhcos --no-signatures --name 4.13-9.2 --url https://rhcos.mirror.openshift.com/art/storage/prod/streams x86_64=413.92.202304131328-0 aarch64=413.92.202304131328-0 s390x=413.92.202304131328-0 ppc64le=413.92.202304131328-0

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 13, 2023

@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.

In response to this:

OCPBUGS-11789: update RHCOS 4.13 bootimage metadata to 413.92.202304131328-0

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
Member Author

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@mike-nguyen: This pull request references Jira Issue OCPBUGS-11789, which is invalid:

  • expected dependent Jira Issue OCPBUGS-11788 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.

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.

@jlebon
Copy link
Member

jlebon commented Apr 13, 2023

The build ID timestamp between the 4.14 and 4.13 PRs looked sus 🔍, but it checks out. ✔️
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 13, 2023
@stbenjam
Copy link
Member

/payload 4.13 ci blocking

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 13, 2023

@stbenjam: trigger 4 job(s) of type blocking for the ci release of OCP 4.13

  • periodic-ci-openshift-release-master-ci-4.13-e2e-aws-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.13-upgrade-from-stable-4.12-e2e-aws-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.13-upgrade-from-stable-4.12-e2e-azure-sdn-upgrade
  • periodic-ci-openshift-release-master-ci-4.13-e2e-aws-sdn-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/6b0a3c10-da38-11ed-86c5-9b0459ea062f-0

@sdodson
Copy link
Member

sdodson commented Apr 13, 2023

/test e2e-azure
/test e2e-gcp

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 13, 2023

@sdodson: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

  • /test agent-integration-tests
  • /test aro-unit
  • /test e2e-agent-compact-ipv4
  • /test e2e-aws-ovn
  • /test e2e-aws-ovn-upi
  • /test e2e-azure-ovn
  • /test e2e-azure-ovn-upi
  • /test e2e-gcp-ovn
  • /test e2e-gcp-ovn-upi
  • /test e2e-metal-ipi-ovn-ipv6
  • /test e2e-openstack-ovn
  • /test e2e-vsphere-ovn
  • /test e2e-vsphere-upi
  • /test gofmt
  • /test golint
  • /test govet
  • /test images
  • /test okd-images
  • /test okd-scos-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-agent-ha-dualstack
  • /test e2e-agent-sno-ipv6
  • /test e2e-alibaba
  • /test e2e-aws-ovn-disruptive
  • /test e2e-aws-ovn-fips
  • /test e2e-aws-ovn-imdsv2
  • /test e2e-aws-ovn-proxy
  • /test e2e-aws-ovn-shared-vpc
  • /test e2e-aws-ovn-single-node
  • /test e2e-aws-ovn-upgrade
  • /test e2e-aws-ovn-workers-rhel8
  • /test e2e-aws-upi-proxy
  • /test e2e-azure-ovn-resourcegroup
  • /test e2e-azure-ovn-shared-vpc
  • /test e2e-azurestack
  • /test e2e-azurestack-upi
  • /test e2e-crc
  • /test e2e-gcp-ovn-shared-vpc
  • /test e2e-gcp-ovn-xpn
  • /test e2e-gcp-secureboot
  • /test e2e-gcp-upgrade
  • /test e2e-gcp-upi-xpn
  • /test e2e-ibmcloud-ovn
  • /test e2e-libvirt
  • /test e2e-metal
  • /test e2e-metal-assisted
  • /test e2e-metal-ipi-ovn-dualstack
  • /test e2e-metal-ipi-sdn
  • /test e2e-metal-ipi-sdn-swapped-hosts
  • /test e2e-metal-ipi-sdn-virtualmedia
  • /test e2e-metal-single-node-live-iso
  • /test e2e-nutanix-ovn
  • /test e2e-nutanix-sdn
  • /test e2e-openstack-externallb-techpreview
  • /test e2e-openstack-kuryr
  • /test e2e-openstack-proxy
  • /test e2e-openstack-sdn-parallel
  • /test e2e-openstack-upi
  • /test e2e-ovirt-sdn
  • /test e2e-vsphere-upi-zones
  • /test e2e-vsphere-zones
  • /test okd-e2e-aws-ovn
  • /test okd-e2e-aws-ovn-upgrade
  • /test okd-e2e-gcp
  • /test okd-e2e-gcp-ovn-upgrade
  • /test okd-e2e-vsphere
  • /test okd-scos-e2e-aws-ovn
  • /test okd-scos-e2e-aws-upgrade
  • /test okd-scos-e2e-gcp
  • /test okd-scos-e2e-gcp-ovn-upgrade
  • /test okd-scos-e2e-vsphere
  • /test okd-scos-unit
  • /test okd-scos-verify-codegen
  • /test tf-fmt

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

  • pull-ci-openshift-installer-release-4.13-aro-unit
  • pull-ci-openshift-installer-release-4.13-e2e-agent-ha-dualstack
  • pull-ci-openshift-installer-release-4.13-e2e-aws-ovn
  • pull-ci-openshift-installer-release-4.13-e2e-aws-ovn-disruptive
  • pull-ci-openshift-installer-release-4.13-e2e-aws-ovn-upgrade
  • pull-ci-openshift-installer-release-4.13-e2e-aws-ovn-workers-rhel8
  • pull-ci-openshift-installer-release-4.13-e2e-openstack-ovn
  • pull-ci-openshift-installer-release-4.13-gofmt
  • pull-ci-openshift-installer-release-4.13-golint
  • pull-ci-openshift-installer-release-4.13-govet
  • pull-ci-openshift-installer-release-4.13-images
  • pull-ci-openshift-installer-release-4.13-okd-e2e-aws-ovn
  • pull-ci-openshift-installer-release-4.13-okd-e2e-aws-ovn-upgrade
  • pull-ci-openshift-installer-release-4.13-okd-images
  • pull-ci-openshift-installer-release-4.13-okd-scos-e2e-aws-ovn
  • pull-ci-openshift-installer-release-4.13-okd-scos-e2e-aws-upgrade
  • pull-ci-openshift-installer-release-4.13-okd-scos-images
  • pull-ci-openshift-installer-release-4.13-okd-scos-unit
  • pull-ci-openshift-installer-release-4.13-okd-scos-verify-codegen
  • pull-ci-openshift-installer-release-4.13-okd-unit
  • pull-ci-openshift-installer-release-4.13-okd-verify-codegen
  • pull-ci-openshift-installer-release-4.13-shellcheck
  • pull-ci-openshift-installer-release-4.13-tf-fmt
  • pull-ci-openshift-installer-release-4.13-tf-lint
  • pull-ci-openshift-installer-release-4.13-unit
  • pull-ci-openshift-installer-release-4.13-verify-codegen
  • pull-ci-openshift-installer-release-4.13-verify-vendor
  • pull-ci-openshift-installer-release-4.13-yaml-lint

In response to this:

/test e2e-azure
/test e2e-gcp

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.

@sdodson
Copy link
Member

sdodson commented Apr 13, 2023

/test e2e-azure-ovn
/test e2e-gcp-ovn

@sdodson sdodson added 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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Apr 14, 2023
@sdodson
Copy link
Member

sdodson commented Apr 14, 2023

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 14, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sdodson

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 Apr 14, 2023
@sdodson
Copy link
Member

sdodson commented Apr 14, 2023

/payload 4.13 ci blocking
Just wondering if the command is broken

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 14, 2023

@sdodson: trigger 4 job(s) of type blocking for the ci release of OCP 4.13

  • periodic-ci-openshift-release-master-ci-4.13-e2e-aws-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.13-upgrade-from-stable-4.12-e2e-aws-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.13-upgrade-from-stable-4.12-e2e-azure-sdn-upgrade
  • periodic-ci-openshift-release-master-ci-4.13-e2e-aws-sdn-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/5a08a290-da69-11ed-8e76-f19c50101a4e-0

@sdodson
Copy link
Member

sdodson commented Apr 14, 2023

/retest-required

@openshift-merge-robot openshift-merge-robot merged commit 9eac541 into openshift:release-4.13 Apr 14, 2023
@openshift-ci-robot
Copy link
Contributor

@mike-nguyen: Jira Issue OCPBUGS-11789: All pull requests linked via external trackers have merged:

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

In response to this:

These changes will update the RHCOS 4.13 bootimage metadata.

This change was generated using:

plume cosa2stream --target data/data/coreos/rhcos.json --distro rhcos --no-signatures --name 4.13-9.2 --url https://rhcos.mirror.openshift.com/art/storage/prod/streams x86_64=413.92.202304131328-0 aarch64=413.92.202304131328-0 s390x=413.92.202304131328-0 ppc64le=413.92.202304131328-0

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
Reviewers

@bgilbert bgilbert Awaiting requested review from bgilbert

@gursewak1997 gursewak1997 Awaiting requested review from gursewak1997

Assignees

@jlebon jlebon

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/severity-moderate Referenced Jira bug's severity is moderate 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. 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
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
6 participants
@mike-nguyen @openshift-ci-robot @jlebon @stbenjam @sdodson @openshift-merge-robot