Skip to content

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #1003

/assign wking

…s too

We've including verification-failure details for forced updates since
5ad3c14 (pkg/cvo/updatepayload: Event when forcing through a
sig-verification failure, 2022-04-07, 2022, openshift#763), but had not been
including them in logs or other output in the "we aren't forcing, so
this blocks the update's acceptance" case.  This commit adds the
detail to the Event, so it's available, but keeps only the high-level
message in the RetrievePayload status output (which feeds the
ReleaseAccepted condition in ClusterVersion), because while the
low-level are useful for debugging, they're pretty chatty for
condition consumers that are more interested in just knowing basically
why the update request isn't being accepted.

The newline-to-// replacement is because apparently Event messages
truncate at the first newline.  I have not tracked down docs or source
to back that up, but confirmed it in pre-merge testing [1].

[1]: openshift#1003 (comment)
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-25055 has been cloned as Jira Issue OCPBUGS-25664. Will retitle bug to link to clone.
/retitle [release-4.15] OCPBUGS-25664: pkg/cvo/sync_worker: Verification-failure details for unforced updates too

Details

In response to this:

This is an automated cherry-pick of #1003

/assign wking

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 changed the title [release-4.15] OCPBUGS-25055: pkg/cvo/sync_worker: Verification-failure details for unforced updates too [release-4.15] OCPBUGS-25664: pkg/cvo/sync_worker: Verification-failure details for unforced updates too Dec 19, 2023
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Dec 19, 2023
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-25664, which is valid. The bug has been moved to the POST state.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.15.0) matches configured target version for branch (4.15.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-25055 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-25055 targets the "4.16.0" version, which is one of the valid target versions: 4.16.0
  • bug has dependents

Requesting review from QA contact:
/cc @jiajliu

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This is an automated cherry-pick of #1003

/assign wking

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.

Copy link
Member

@wking wking left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@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 Dec 19, 2023
@jiajliu
Copy link
Contributor

jiajliu commented Dec 19, 2023

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Dec 19, 2023
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-25664, which is valid.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.15.0) matches configured target version for branch (4.15.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-25055 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-25055 targets the "4.16.0" version, which is one of the valid target versions: 4.16.0
  • bug has dependents

Requesting review from QA contact:
/cc @jiajliu

Details

In response to this:

This is an automated cherry-pick of #1003

/assign wking

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.

Copy link
Member

@LalatenduMohanty LalatenduMohanty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Dec 19, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 19, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: LalatenduMohanty, openshift-cherrypick-robot, wking

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:
  • OWNERS [LalatenduMohanty,wking]

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

@jiajliu
Copy link
Contributor

jiajliu commented Dec 20, 2023

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Dec 20, 2023
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 8161b06 and 2 for PR HEAD bcbeee7 in total

@petr-muller
Copy link
Member

/test unit e2e-hypershift

TestRunGraph/mid-task_cancellation_with_work_in_queue_does_not_deadlock is a known flake (https://issues.redhat.com/browse/OCPBUGS-22442)

@wking
Copy link
Member

wking commented Dec 21, 2023

Nothing does signature verification on HyperShift, at least not at the CVO level, where the HostedControlPlane controller manages the CVO Deployment.

/override ci/prow/e2e-hypershift

And the past three unit test runs have a pass, a TestRunGraph/mid-task_cancellation_with_work_in_queue_does_not_deadlock failure, and a TestOperator_upgradeableSync failure, so that doesn't seem reproducible or either. But unit tests are cheap and fairly fast:

/test unit

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 21, 2023

@wking: Overrode contexts on behalf of wking: ci/prow/e2e-hypershift

Details

In response to this:

Nothing does signature verification on HyperShift, at least not at the CVO level, where the HostedControlPlane controller manages the CVO Deployment.

/override ci/prow/e2e-hypershift

And the past three unit test runs have a pass, a TestRunGraph/mid-task_cancellation_with_work_in_queue_does_not_deadlock failure, and a TestOperator_upgradeableSync failure, so that doesn't seem reproducible or either. But unit tests are cheap and fairly fast:

/test unit

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 Dec 21, 2023

@openshift-cherrypick-robot: 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/e2e-hypershift bcbeee7 link true /test e2e-hypershift

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 1f8f3b1 into openshift:release-4.15 Dec 21, 2023
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-25664: All pull requests linked via external trackers have merged:

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

Details

In response to this:

This is an automated cherry-pick of #1003

/assign wking

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

[ART PR BUILD NOTIFIER]

This PR has been included in build cluster-version-operator-container-v4.15.0-202312210631.p0.g1f8f3b1.assembly.stream for distgit cluster-version-operator.
All builds following this will include this PR.

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.15.0-0.nightly-2023-12-21-110844

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants