Skip to content

Conversation

@jhadvig
Copy link
Member

@jhadvig jhadvig commented Dec 15, 2025

/assign @TheRealJon

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

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

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

Requesting review from QA contact:
/cc @yapei

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

Details

In response to this:

/assign @TheRealJon

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 added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 15, 2025
@jhadvig
Copy link
Member Author

jhadvig commented Dec 16, 2025

/retest

Copy link
Member

@TheRealJon TheRealJon 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 the lgtm Indicates that a PR is ready to be merged. label Dec 17, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 17, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jhadvig, TheRealJon

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:

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

@christoph-jerolimov
Copy link
Member

/uncc

@openshift-ci openshift-ci bot removed the request for review from christoph-jerolimov December 19, 2025 13:05
@yapei
Copy link
Contributor

yapei commented Dec 23, 2025

confirmed the missing annotations are now added

$ oc get consolequickstart trusted-artifact-signer-getting-started -o json | jq .metadata.annotations
{
  "capability.openshift.io/name": "Console",
  "include.release.openshift.io/ibm-cloud-managed": "true",
  "include.release.openshift.io/self-managed-high-availability": "true",
  "include.release.openshift.io/single-node-developer": "true"
}

$ oc get consolequickstart trusted-profile-analyzer-getting-started -o json | jq .metadata.annotations
{
  "capability.openshift.io/name": "Console",
  "include.release.openshift.io/ibm-cloud-managed": "true",
  "include.release.openshift.io/self-managed-high-availability": "true",
  "include.release.openshift.io/single-node-developer": "true"
}

/verified by @yapei

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

@yapei: This PR has been marked as verified by @yapei.

Details

In response to this:

confirmed the missing annotations are now added

$ oc get consolequickstart trusted-artifact-signer-getting-started -o json | jq .metadata.annotations
{
 "capability.openshift.io/name": "Console",
 "include.release.openshift.io/ibm-cloud-managed": "true",
 "include.release.openshift.io/self-managed-high-availability": "true",
 "include.release.openshift.io/single-node-developer": "true"
}

$ oc get consolequickstart trusted-profile-analyzer-getting-started -o json | jq .metadata.annotations
{
 "capability.openshift.io/name": "Console",
 "include.release.openshift.io/ibm-cloud-managed": "true",
 "include.release.openshift.io/self-managed-high-availability": "true",
 "include.release.openshift.io/single-node-developer": "true"
}

/verified by @yapei

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

/retest-required

Remaining retests: 0 against base HEAD e056fd6 and 2 for PR HEAD 283e085 in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 23, 2025

@jhadvig: 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/okd-scos-images 283e085 link true /test okd-scos-images

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

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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants