Skip to content

[enterprise-4.19] OSDOCS-15477: add gwapi aws known issue #96578

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: enterprise-4.19
Choose a base branch
from

Conversation

jldohmann
Copy link
Contributor

@jldohmann jldohmann commented Jul 23, 2025

Version(s): 4.19

Issue: https://issues.redhat.com/browse/OSDOCS-15477

Link to docs preview: https://96578--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-19-release-notes.html#ocp-4-19-known-issues_release-notes (scroll a bit)

QE review:

  • QE has approved this change.

Additional information: needs change management

@jldohmann jldohmann added this to the Continuous Release milestone Jul 23, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 23, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 23, 2025

@jldohmann: This pull request references OSDOCS-15477 which is a valid jira issue.

In response to this:

Version(s): 4.19

Issue: https://issues.redhat.com/browse/OSDOCS-15477

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information: needs change management

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/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jul 23, 2025
@jldohmann
Copy link
Contributor Author

@lihongan could you PTAL at this docs PR for QE feedback? it adds the known issue about GWAPI and AWS private clusters. please lmk if there needs to be more information about the issue. thank you 🙇

@ahardin-rh
Copy link
Contributor

LGTM!

@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Jul 23, 2025

🤖 Tue Jul 29 22:54:17 - Prow CI generated the docs preview:

https://96578--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-19-release-notes.html

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 23, 2025

@jldohmann: This pull request references OSDOCS-15477 which is a valid jira issue.

In response to this:

Version(s): 4.19

Issue: https://issues.redhat.com/browse/OSDOCS-15477

Link to docs preview: https://96578--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-19-release-notes.html#ocp-4-19-known-issues_release-notes (scroll a bit)

QE review:

  • QE has approved this change.

Additional information: needs change management

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.

@jldohmann jldohmann force-pushed the OSDOCS-15477-4.19 branch from 9fcda76 to e16c5a0 Compare July 24, 2025 17:07
@openshift-ci openshift-ci bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jul 24, 2025
@jldohmann jldohmann force-pushed the OSDOCS-15477-4.19 branch 4 times, most recently from df097bb to 77cb578 Compare July 24, 2025 18:24
@jldohmann
Copy link
Contributor Author

hi, i need the following acks from you all for change management purposes:
@Miciah
@CFields651
@mcurry-rh
@kalexand-rh
and Ashley (thanks! 😄 )

thank you all

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 25, 2025

@jldohmann: This pull request references OSDOCS-15477 which is a valid jira issue.

In response to this:

Version(s): 4.19

Issue: https://issues.redhat.com/browse/OSDOCS-15477

Link to docs preview: https://96578--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-19-release-notes.html#ocp-4-19-known-issues_release-notes (scroll a bit)

QE review:

  • QE has approved this change.

Additional information: needs change management

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.

@jldohmann jldohmann added the merge-review-needed Signifies that the merge review team needs to review this PR label Jul 28, 2025
@michaelryanpeter
Copy link
Contributor

/label merge-review-in-progress

@openshift-ci openshift-ci bot added the merge-review-in-progress Signifies that the merge review team is reviewing this PR label Jul 28, 2025
@michaelryanpeter
Copy link
Contributor

LGTM!

Since you are a merge reviewer and still getting change management acks, I am going to add the ok-to-merge label for you.

/label ok-to-merge
/remove-label mergre-review-needed
/remove-label merge-review-in-progress

@openshift-ci openshift-ci bot removed the merge-review-in-progress Signifies that the merge review team is reviewing this PR label Jul 28, 2025
Copy link

openshift-ci bot commented Jul 28, 2025

@michaelryanpeter: The label(s) /label ok-to-merge , /remove-label mergre-review-needed cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, ux-approved, no-qe, downstream-change-needed, rebase/manual, cluster-config-api-changed, run-integration-tests, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, cloud-experts, cnv, dev-tools, distributed-tracing, ims, jira/valid-bug, merge-review-in-progress, merge-review-needed, mtc, multi-arch, oadp, rhacs, rhv, sd-docs, serverless, service-mesh, sme-review-done, sme-review-needed, stability-fix-approved, staff-eng-approved, telco. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

LGTM!

Since you are a merge reviewer and still getting change management acks, I am going to add the ok-to-merge label for you.

/label ok-to-merge
/remove-label mergre-review-needed
/remove-label merge-review-in-progress

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.

@michaelryanpeter michaelryanpeter added ok-to-merge and removed merge-review-needed Signifies that the merge review team needs to review this PR labels Jul 28, 2025
@kalexand-rh
Copy link
Contributor

From a CM perspective, LGTM, but I'm having trouble squaring up the relationship between the introduction to the UL and the UL contents.

@CFields651
Copy link

LGTM

@CFields651
Copy link

/label px-approved

@openshift-ci openshift-ci bot added the px-approved Signifies that Product Support has signed off on this PR label Jul 29, 2025
@jldohmann jldohmann force-pushed the OSDOCS-15477-4.19 branch from 77cb578 to 9954b50 Compare July 29, 2025 20:20
@jldohmann jldohmann force-pushed the OSDOCS-15477-4.19 branch from 9954b50 to 19afb78 Compare July 29, 2025 22:39
Copy link

openshift-ci bot commented Jul 29, 2025

@jldohmann: all tests passed!

Full PR test history. Your PR dashboard.

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
branch/enterprise-4.19 jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. ok-to-merge px-approved Signifies that Product Support has signed off on this PR 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.

10 participants