OCPBUGS-68367: Add missing console annotation to the quickstart

[jhadvig]

/assign @TheRealJon

[openshift-ci-robot]

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

[jhadvig]

/retest

[TheRealJon]

/lgtm

[openshift-ci]

[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:

• quickstarts/OWNERS [TheRealJon,jhadvig]

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

[christoph-jerolimov]

/uncc

[yapei]

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]

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

/retest-required

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

[openshift-bot]

/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-bot: This pull request references Jira Issue OCPBUGS-68367, which is valid.

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 POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @yapei

Details

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.

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 17c6c71 and 1 for PR HEAD 283e085 in total

[jhadvig]

/override ci/prow/okd-scos-images

[jhadvig]

/backport release-4.20

[openshift-ci]

@jhadvig: Overrode contexts on behalf of jhadvig: ci/prow/okd-scos-images

Details

In response to this:

/override ci/prow/okd-scos-images

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.

[jhadvig]

/cherry-pick release-4.20

[openshift-cherrypick-robot]

@jhadvig: once the present PR merges, I will cherry-pick it on top of release-4.20 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick 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.

[openshift-ci-robot]

/retest-required

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

[openshift-ci]

@jhadvig: all tests passed!

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.

[openshift-ci-robot]

@jhadvig: Jira Issue Verification Checks: Jira Issue OCPBUGS-68367
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-68367 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

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-cherrypick-robot]

@jhadvig: #1082 failed to apply on top of branch "release-4.20":

Applying: OCPBUGS-68367: Add missing console annotation to the quickstart
Using index info to reconstruct a base tree...
A	quickstarts/trusted-artifact-signer.yaml
A	quickstarts/trusted-profile-analyzer.yaml
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): quickstarts/trusted-profile-analyzer.yaml deleted in HEAD and modified in OCPBUGS-68367: Add missing console annotation to the quickstart. Version OCPBUGS-68367: Add missing console annotation to the quickstart of quickstarts/trusted-profile-analyzer.yaml left in tree.
CONFLICT (modify/delete): quickstarts/trusted-artifact-signer.yaml deleted in HEAD and modified in OCPBUGS-68367: Add missing console annotation to the quickstart. Version OCPBUGS-68367: Add missing console annotation to the quickstart of quickstarts/trusted-artifact-signer.yaml left in tree.
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 OCPBUGS-68367: Add missing console annotation to the quickstart

Details

In response to this:

/cherry-pick 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.

[jhadvig]

/cherry-pick release-4.21

[openshift-cherrypick-robot]

@jhadvig: new pull request created: #1089

Details

In response to this:

/cherry-pick release-4.21

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.