Skip to content
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

[enterprise-4.12] Issue in file installing/installing_gcp/installing-gcp-user-infra.adoc #54988

Open
linuxstudio opened this issue Jan 20, 2023 · 3 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@linuxstudio
Copy link

Which section(s) is the issue in?

Creating load balancers in GCP

What needs fixing?

The callout (1) in the "Create a 02_infra.yaml resource definition file" listing is pointing to "path: 02_lb_int.py" which is not consistent with the description of the callout "Required only when deploying an external cluster."

This seems to be present also in the same section of the documents:

installing/installing_gcp/installing-gcp-user-infra-vpc.html
installing/installing_gcp/installing-restricted-networks-gcp.html

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 21, 2023
@linuxstudio
Copy link
Author

/lifecycle frozen

@openshift-ci openshift-ci bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 21, 2023
@rolfedh
Copy link
Contributor

rolfedh commented Sep 13, 2023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

3 participants