AGENT-1334: Examples of golden snapshot and release for OVE ISO image

[bfournie]

These are examples for the golden snapshot and release for the tested OVE ISO UI.

The purpose of the golden snapshot is to ensure that the tested snapshot is not removed from the cluster.
The release CR references the snapshot and the releasePlan. When applied to the cluster it will cause the release pipeline to run.

Both of these files should be applied to the cluster using oc apply e.g.

$ oc apply -f tools/iso_builder/releases/golden_snapshot-4-20-6.yaml -n ocp-agent-based-installer-tenant
$ oc apply -f tools/iso_builder/releases/release-4-20-6.yaml -n ocp-agent-based-installer-tenant

[openshift-ci-robot]

@bfournie: This pull request references AGENT-1334 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target either version "4.21." or "openshift-4.21.", but it targets "openshift-4.20.z" instead.

Details

In response to this:

This is the golden snapshot containing the URL for the tested
OVE ISO UI. The purpose of the golden snapshot is to ensure
that the tested snapshot is not removed from the cluster.

This snapshot has been applied to cluster kflux-prd-rh02 using:
$ oc apply -f golden_snapshot.yaml -n ocp-agent-based-installer-tenant

And verified to exist in the cluster:
$ oc get snapshots | grep golden
ove-ui-4-20-golden-4.20.z5 13m

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bfournie

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 [bfournie]

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

[bfournie]

/retest

[bfournie]

/retest

[openshift-ci-robot]

@bfournie: This pull request references AGENT-1334 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target either version "4.21." or "openshift-4.21.", but it targets "openshift-4.20.z" instead.

Details

In response to this:

This is the golden snapshot containing the URL for the tested
OVE ISO UI. The purpose of the golden snapshot is to ensure
that the tested snapshot is not removed from the cluster.

This snapshot has been applied to cluster kflux-prd-rh02.

In addition the release CR is included which references the snapshot and the releasePlan. When applied to the cluster it will cause the release pipeline to run.

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.

[bfournie]

/hold

[openshift-ci-robot]

@bfournie: This pull request references AGENT-1334 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target either version "4.22." or "openshift-4.22.", but it targets "openshift-4.20.z" instead.

Details

In response to this:

These are examples for the golden snapshot and release for the tested OVE ISO UI.

The purpose of the golden snapshot is to ensure that the tested snapshot is not removed from the cluster.
The release CR references the snapshot and the releasePlan. When applied to the cluster it will cause the release pipeline to run.

Both of these files should be applied to the cluster using oc apply e.g.

$ oc apply -f tools/iso_builder/releases/golden_snapshot-4-20-6.yaml -n ocp-agent-based-installer-tenant
$ oc apply -f tools/iso_builder/releases/release-4-20-6.yaml -n ocp-agent-based-installer-tenant

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.

[pawanpinjarkar]

/lgtm

[bfournie]

/unhold

[bfournie]

/label acknowledge-critical-fixes-only

[bfournie]

/verified bypass

[openshift-ci-robot]

@bfournie: The verified label has been added.

Details

In response to this:

/verified bypass

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 2369202 and 2 for PR HEAD 42678b5 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 86e4ffc and 1 for PR HEAD 42678b5 in total

[bfournie]

/retest

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 036a273 and 0 for PR HEAD 42678b5 in total

[openshift-ci]

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