Skip to content

[enterprise-4.16] OCPBUGS-81524: Added a note about seed cluster usage - #119240

Open
lcavalle wants to merge 1 commit into
openshift:enterprise-4.16from
lcavalle:cherry-pick-114277-enterprise-4.16
Open

[enterprise-4.16] OCPBUGS-81524: Added a note about seed cluster usage#119240
lcavalle wants to merge 1 commit into
openshift:enterprise-4.16from
lcavalle:cherry-pick-114277-enterprise-4.16

Conversation

@lcavalle

@lcavalle lcavalle commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

This is a manual cherry-pick of #114277

Version(s):
4.16

Issue:
https://redhat.atlassian.net/browse/OCPBUGS-81524

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

  • Manual cherry-pick of OCPBUGS#81524: Added a note about seed cluster usage #114277
  • Automated cherry-pick did not apply cleanly because this version still uses a callout in the verification example, and the previous "provision a new seed cluster" sentence is before the Verification section.
  • The IMPORTANT note about not using the seed cluster after image generation replaces that sentence and is placed after verification, matching the original PR.

/assign slovern

Co-authored-by: Cursor <cursoragent@cursor.com>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 2, 2026
@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Sep 2, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@lcavalle: This pull request references Jira Issue OCPBUGS-81524, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED instead
  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-81524 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

Details

In response to this:

This is a manual cherry-pick of #114277

Version(s):
4.16

Issue:
https://redhat.atlassian.net/browse/OCPBUGS-81524

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

  • Manual cherry-pick of OCPBUGS#81524: Added a note about seed cluster usage #114277
  • Automated cherry-pick did not apply cleanly because this version still uses a callout in the verification example, and the previous "provision a new seed cluster" sentence is before the Verification section.
  • The IMPORTANT note about not using the seed cluster after image generation replaces that sentence and is placed after verification, matching the original PR.

/assign slovern

Made with Cursor

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.

@lcavalle

lcavalle commented Sep 2, 2026

Copy link
Copy Markdown
Contributor Author

/jira refresh

@openshift-ci-robot

Copy link
Copy Markdown

@lcavalle: This pull request references Jira Issue OCPBUGS-81524, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED instead
  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-81524 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

Details

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 added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Sep 2, 2026
@ocpdocs-previewbot

Copy link
Copy Markdown

@lcavalle

lcavalle commented Sep 2, 2026

Copy link
Copy Markdown
Contributor Author

/retest

@openshift-ci

openshift-ci Bot commented Sep 2, 2026

Copy link
Copy Markdown

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants