Skip to content

[OKD] Incorrect link#105714

Open
mburke5678 wants to merge 1 commit into
openshift:mainfrom
mburke5678:okd-incorrect-link-osus-cli
Open

[OKD] Incorrect link#105714
mburke5678 wants to merge 1 commit into
openshift:mainfrom
mburke5678:okd-incorrect-link-osus-cli

Conversation

@mburke5678
Copy link
Copy Markdown
Contributor

#96704

4.17: The about-installing-oc-mirror-v2.adoc file is at: https://docs.okd.io/4.17/disconnected/mirroring/about-installing-oc-mirror-v2.html
4.18+: The about-installing-oc-mirror-v2.adoc file was moved up one level in 4.18. It is now: https://docs.okd.io/latest/disconnected/about-installing-oc-mirror-v2.html

Link to docs preview:

QE review:

  • QE has approved this change.

@mburke5678 mburke5678 force-pushed the okd-incorrect-link-osus-cli branch from 8d6f214 to 296b2ff Compare January 29, 2026 21:54
@mburke5678
Copy link
Copy Markdown
Contributor Author

@kenjpais: Dennis Gilmore suggested you can review OKD doc changes. Can you PTAL at this updated link? Thank you in advance.

@ocpdocs-previewbot
Copy link
Copy Markdown

🤖 Thu Jan 29 22:01:33 - Prow CI generated the docs preview:

https://105714--ocpdocs-pr.netlify.app/openshift-enterprise/latest/disconnected/about-installing-oc-mirror-v2.html

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Jan 29, 2026

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

@bergerhoffer
Copy link
Copy Markdown
Contributor

The branch/enterprise-4.22 label has been added to this PR.

This is because your PR targets the main branch and is labeled for enterprise-4.21. And any PR going into main must also target the latest version branch (enterprise-4.22).

If the update in your PR does NOT apply to version 4.22 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main.

@openshift-bot
Copy link
Copy Markdown

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 May 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.17 branch/enterprise-4.18 branch/enterprise-4.19 branch/enterprise-4.20 branch/enterprise-4.21 branch/enterprise-4.22 lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants