Skip to content

Conversation

chrischdi
Copy link
Contributor

@openshift-ci-robot openshift-ci-robot added 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 Sep 1, 2025
@openshift-ci-robot
Copy link
Contributor

@chrischdi: This pull request references Jira Issue OCPBUGS-60901, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA 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:

Pulls in openshift/api#2462

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 openshift-eng/jira-lifecycle-plugin repository.

@JoelSpeed
Copy link
Contributor

/lgtm
/approve

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Sep 1, 2025
@theobarberbany
Copy link
Contributor

/lgtm
/approve

Copy link
Contributor

openshift-ci bot commented Sep 1, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed, theobarberbany

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 [JoelSpeed,theobarberbany]

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

@chrischdi
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added 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 Sep 1, 2025
@openshift-ci-robot
Copy link
Contributor

@chrischdi: This pull request references Jira Issue OCPBUGS-60901, which is valid.

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

Requesting review from QA contact:
/cc @sunzhaohua2

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested a review from sunzhaohua2 September 1, 2025 14:27
@chrischdi
Copy link
Contributor Author

/retest

@damdo
Copy link
Member

damdo commented Sep 1, 2025

/retest-required

@chrischdi
Copy link
Contributor Author

Looks like hitting rate limits:

error: unable to parse image registry.build02.ci.openshift.org/ci-op-m87t4v0i/stable@sha256:5dfbb4de009b0b2600d62606751dfe1920da923e92fcf636fd8471d100035773: cannot retrieve image configuration for manifest sha256:5dfbb4de009b0b2600d62606751dfe1920da923e92fcf636fd8471d100035773: error parsing HTTP 429 response body: invalid character '<' looking for beginning of value: "<?xml version=\"1.0\" encoding=\"UTF-8\"?><Error><Code>ServiceUnavailable</Code><Message>Reduce your rate of simultaneous reads on the same object.</Message></Error>"

Will try again later/tomorrow.

@sunzhaohua2
Copy link
Contributor

/retest-required

@sunzhaohua2
Copy link
Contributor

/retest

@sunzhaohua2
Copy link
Contributor

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Sep 2, 2025
@openshift-ci-robot openshift-ci-robot added jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. and removed jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Sep 2, 2025
@openshift-ci-robot
Copy link
Contributor

@chrischdi: This pull request references Jira Issue OCPBUGS-60901, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA 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:

Pulls in openshift/api#2462

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 openshift-eng/jira-lifecycle-plugin repository.

@chrischdi
Copy link
Contributor Author

/test help

Copy link
Contributor

openshift-ci bot commented Sep 2, 2025

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

/test e2e-aws-operator
/test e2e-aws-ovn
/test e2e-aws-ovn-upgrade
/test e2e-metal-ipi
/test e2e-metal-ipi-ovn-ipv6
/test e2e-metal-ipi-virtualmedia
/test goimports
/test golint
/test govet
/test images
/test okd-scos-images
/test security
/test unit
/test verify-crds-sync
/test verify-deps

The following commands are available to trigger optional jobs:

/test e2e-aws-operator-techpreview
/test e2e-azure-manual-oidc
/test e2e-azure-operator
/test e2e-azure-ovn
/test e2e-gcp-operator
/test e2e-gcp-ovn
/test e2e-metal-ipi-ovn-dualstack
/test e2e-metal-ipi-upgrade
/test e2e-nutanix
/test e2e-openstack
/test e2e-vsphere-host-groups-ovn
/test e2e-vsphere-operator
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-multi-vcenter
/test e2e-vsphere-ovn-serial
/test e2e-vsphere-ovn-techpreview
/test e2e-vsphere-ovn-techpreview-serial
/test e2e-vsphere-ovn-upgrade
/test e2e-vsphere-static-ovn
/test okd-scos-e2e-aws-ovn
/test regression-clusterinfra-aws-ipi-mapi

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

pull-ci-openshift-machine-api-operator-main-e2e-aws-operator
pull-ci-openshift-machine-api-operator-main-e2e-aws-operator-techpreview
pull-ci-openshift-machine-api-operator-main-e2e-aws-ovn
pull-ci-openshift-machine-api-operator-main-e2e-aws-ovn-upgrade
pull-ci-openshift-machine-api-operator-main-e2e-azure-operator
pull-ci-openshift-machine-api-operator-main-e2e-azure-ovn
pull-ci-openshift-machine-api-operator-main-e2e-gcp-operator
pull-ci-openshift-machine-api-operator-main-e2e-gcp-ovn
pull-ci-openshift-machine-api-operator-main-e2e-metal-ipi
pull-ci-openshift-machine-api-operator-main-e2e-metal-ipi-ovn-dualstack
pull-ci-openshift-machine-api-operator-main-e2e-metal-ipi-ovn-ipv6
pull-ci-openshift-machine-api-operator-main-e2e-metal-ipi-upgrade
pull-ci-openshift-machine-api-operator-main-e2e-metal-ipi-virtualmedia
pull-ci-openshift-machine-api-operator-main-e2e-nutanix
pull-ci-openshift-machine-api-operator-main-e2e-openstack
pull-ci-openshift-machine-api-operator-main-e2e-vsphere-host-groups-ovn
pull-ci-openshift-machine-api-operator-main-e2e-vsphere-operator
pull-ci-openshift-machine-api-operator-main-e2e-vsphere-ovn
pull-ci-openshift-machine-api-operator-main-e2e-vsphere-ovn-multi-vcenter
pull-ci-openshift-machine-api-operator-main-e2e-vsphere-ovn-serial
pull-ci-openshift-machine-api-operator-main-e2e-vsphere-ovn-techpreview
pull-ci-openshift-machine-api-operator-main-e2e-vsphere-ovn-techpreview-serial
pull-ci-openshift-machine-api-operator-main-e2e-vsphere-ovn-upgrade
pull-ci-openshift-machine-api-operator-main-e2e-vsphere-static-ovn
pull-ci-openshift-machine-api-operator-main-goimports
pull-ci-openshift-machine-api-operator-main-golint
pull-ci-openshift-machine-api-operator-main-govet
pull-ci-openshift-machine-api-operator-main-images
pull-ci-openshift-machine-api-operator-main-okd-scos-e2e-aws-ovn
pull-ci-openshift-machine-api-operator-main-okd-scos-images
pull-ci-openshift-machine-api-operator-main-regression-clusterinfra-aws-ipi-mapi
pull-ci-openshift-machine-api-operator-main-security
pull-ci-openshift-machine-api-operator-main-unit
pull-ci-openshift-machine-api-operator-main-verify-crds-sync
pull-ci-openshift-machine-api-operator-main-verify-deps

In response to this:

/test help

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-sigs/prow repository.

@openshift-bot
Copy link
Contributor

/jira refresh

The requirements for Jira bugs have changed (Jira issues linked to PRs on main branch need to target different OCP), recalculating validity.

@openshift-ci-robot openshift-ci-robot added jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. and removed jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Sep 2, 2025
@openshift-ci-robot
Copy link
Contributor

@openshift-bot: This pull request references Jira Issue OCPBUGS-60901, which is invalid:

  • expected the bug to target either version "4.21." or "openshift-4.21.", but it targets "4.20.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA 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

The requirements for Jira bugs have changed (Jira issues linked to PRs on main branch need to target different OCP), recalculating validity.

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 openshift-eng/jira-lifecycle-plugin repository.

@chrischdi
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added 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 Sep 2, 2025
@openshift-ci-robot
Copy link
Contributor

@chrischdi: This pull request references Jira Issue OCPBUGS-60901, which is valid.

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

Requesting review from QA contact:
/cc @sunzhaohua2

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 openshift-eng/jira-lifecycle-plugin repository.

@damdo
Copy link
Member

damdo commented Sep 2, 2025

/retest-required

@damdo
Copy link
Member

damdo commented Sep 2, 2025

/retest

@chrischdi
Copy link
Contributor Author

chrischdi commented Sep 2, 2025

/verified by @sunzhaohua2

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Sep 2, 2025
@openshift-ci-robot
Copy link
Contributor

@chrischdi: This PR has been marked as verified by sunzhaohua2.

In response to this:

/verified by sunzhaohua2

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 openshift-eng/jira-lifecycle-plugin repository.

@damdo
Copy link
Member

damdo commented Sep 2, 2025

/retest-required

1 similar comment
@chrischdi
Copy link
Contributor Author

/retest-required

@chrischdi
Copy link
Contributor Author

Waiting for lifting the acknowledge-critical-fixes-only requirement :-)

@damdo
Copy link
Member

damdo commented Sep 3, 2025

Looking at the failed jobs (even if they are optional) to try and see what's going on:

  • the e2e-aws-operator-techpreview failed on a Cluster API AWS MachineSet [It] should be able to run a machine with dedicated instance [capi, disruptive] test here, this is likely unrelated but i'd be nice to understand why it is failing
  • e2e-openstack seems to be consistently failing in the pre test phase while resolving KAS dns name (here) (cc. @stephenfin is there a known issue with this?)
  • e2e-vsphere-host-groups-ovn seems to be permafailing for a while now and it seems to be a workflow/configuration error for the job (here) (cc. @vr4manta @jcpowermac @rvanderp3 is this something you have seen already?)
  • e2e-vsphere-ovn-techpreview-serial this timed out on the 4h mark and we should increase its shard count to 2 to parallelise it
  • regression-clusterinfra-aws-ipi-mapi this has never passed from what I can tell (here) (cc. @sunzhaohua2 @huali9 @miyadav is there a known issue with it?)
  • e2e-gcp-ovn is flaking it seems like

@damdo
Copy link
Member

damdo commented Sep 3, 2025

/test e2e-gcp-ovn

@damdo
Copy link
Member

damdo commented Sep 3, 2025

/test e2e-openstack

Copy link
Contributor

openshift-ci bot commented Sep 3, 2025

@chrischdi: 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/e2e-vsphere-ovn-techpreview-serial e783f66 link false /test e2e-vsphere-ovn-techpreview-serial
ci/prow/e2e-aws-operator-techpreview e783f66 link false /test e2e-aws-operator-techpreview
ci/prow/e2e-vsphere-host-groups-ovn e783f66 link false /test e2e-vsphere-host-groups-ovn
ci/prow/regression-clusterinfra-aws-ipi-mapi e783f66 link false /test regression-clusterinfra-aws-ipi-mapi

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

@openshift-merge-bot openshift-merge-bot bot merged commit e3846e1 into openshift:main Sep 4, 2025
33 of 36 checks passed
@openshift-ci-robot
Copy link
Contributor

@chrischdi: Jira Issue OCPBUGS-60901 is in an unrecognized state (Verified) and will not be moved to the MODIFIED state.

In response to this:

Pulls in openshift/api#2462

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 openshift-eng/jira-lifecycle-plugin repository.

@damdo
Copy link
Member

damdo commented Sep 4, 2025

Should we backport this to 4.20 to enable the comment/doc fix you did in the API @chrischdi ?

@chrischdi
Copy link
Contributor Author

Yes, Imho we should backport to 4.20, because the API change is already in there.

@damdo, Question: Should we also backport to 4.19 together with openshift/api#2464 ?

@damdo
Copy link
Member

damdo commented Sep 5, 2025

@chrischdi yes I think that makes sense, TY :)

@chrischdi
Copy link
Contributor Author

/cherrypick release-4.20

@openshift-cherrypick-robot

@chrischdi: new pull request created: #1410

In response to this:

/cherrypick release-4.20

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-sigs/prow 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. 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. qe-approved Signifies that QE has signed off on this PR verified Signifies that the PR passed pre-merge verification criteria
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants