OCPBUGS-73774-4-19: Moved Allocating Load Balancers to Specific Subne…

[dfitzmau]

The 4.19 automatic CP passed from main but failed a prow check. The reason was a link in the 4.19 release notes.

Version(s):
4.19

Issue:
OCPBUGS-73774

Link to docs preview:

• https://109127--ocpdocs-pr.netlify.app/openshift-enterprise/latest/installing/installing_aws/ipi/installing-aws-vpc.html#allocating-load-balancers_installing-aws-vpc
• https://109127--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-19-release-notes.html#ocp-4-19-networking-allocate-load-balancers-to-specific-subnets_release-notes

[openshift-ci-robot]

@dfitzmau: No Jira issue with key 4-19 exists in the tracker at https://redhat.atlassian.net.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

Details

In response to this:

Version(s):
4.19

Issue:
OCPBUGS-73774

Link to docs preview:

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]

@dfitzmau: No Jira issue with key 4-19 exists in the tracker at https://redhat.atlassian.net.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

Details

In response to this:

Not sure why but the 4.19 CP did not flag a fail on the main PR but did fail on Prow on it's own PR. I've raised a manual PR to ensure a clean backport.

Version(s):
4.19

Issue:
OCPBUGS-73774

Link to docs preview:

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]

@dfitzmau: No Jira issue with key 4-19 exists in the tracker at https://redhat.atlassian.net.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

Details

In response to this:

Not sure why but the 4.19 CP did not flag a fail on the main PR but did fail on Prow on it's own PR. I've raised a manual PR to ensure a clean backport.

Version(s):
4.16 to 4.19

Issue:
OCPBUGS-73774

Link to docs preview:

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.

[ocpdocs-previewbot]

🤖 Fri Mar 27 11:22:43 - Prow CI generated the docs preview:

https://109127--ocpdocs-pr.netlify.app/
https://109127--ocpdocs-pr.netlify.app/openshift-enterprise/latest/installing/installing_aws/ipi/installing-aws-vpc.html
https://109127--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-19-release-notes.html

[openshift-ci]

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

@dfitzmau: No Jira issue with key 4-19 exists in the tracker at https://redhat.atlassian.net.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

Details

In response to this:

The 4.19 automatic CP passed from main but failed a prow check. The reason was a link in the 4.19 release notes.

Version(s):
4.19

Issue:
OCPBUGS-73774

Link to docs preview:

• https://109127--ocpdocs-pr.netlify.app/openshift-enterprise/latest/installing/installing_aws/ipi/installing-aws-vpc.html
• https://109127--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-19-release-notes.html

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]

@dfitzmau: No Jira issue with key 4-19 exists in the tracker at https://redhat.atlassian.net.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

Details

In response to this:

The 4.19 automatic CP passed from main but failed a prow check. The reason was a link in the 4.19 release notes.

Version(s):
4.19

Issue:
OCPBUGS-73774

Link to docs preview:

• https://109127--ocpdocs-pr.netlify.app/openshift-enterprise/latest/installing/installing_aws/ipi/installing-aws-vpc.html#allocating-load-balancers_installing-aws-vpc
• https://109127--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-19-release-notes.html#ocp-4-19-networking-allocate-load-balancers-to-specific-subnets_release-notes

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.

[ShaunaDiaz]

/lgtm