Skip to content

Conversation

@eliranmal
Copy link
Collaborator

@eliranmal eliranmal commented Nov 3, 2025

Summary

use "latest" in OCP doc-links, instead of hard-coding the version.

Additional information

just FYI: these were discovered during the work on this PR, and got moved to #204 for proper scoping:

  • fix path variables; installing_on_gcp got replaced with installing_on_google_cloud
  • fix occurrences of hard-coded version strings in the OSDK release-notes link URL, and update its anchor link, which was removed (was tentative, tech-writers' team decided to keep the current link as is)

Jira

addresses OCMUI-3556

How to Test

run check-links, verify there's no regression in the output.

Review process

Please review and follow the PR process.

QE Reviewer

  • Pre-merge testing : Verified change locally in a browser (downloaded and ran code using reviewx tool)
  • Updated/created Polarion test cases which were peer QE reviewed
  • Confirmed 'tc-approved' label was added by dev to the linked JIRA ticket
  • (optional) Updated/created Cypress e2e tests
  • Closed threads I started after the author made changes or added an explanation

in OCP doc links:
- use `latest` for the base link, instead of hard-coding `4.19`
- fix path variables; `installing_on_gcp` got replaced with `installing_on_google_cloud`
@sourcery-ai
Copy link

sourcery-ai bot commented Nov 3, 2025

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Replace hard-coded OCP documentation version with the 'latest' alias in installation links so that documentation URLs always point to the most recent release.

Class diagram for updated OCP documentation link constants

classDiagram
    class installLinks {
        +SHP_CLI_LATEST : string
        +OCP_DOCS_BASE : string
        +OSD_DOCS_BASE : string
        +ROSA_DOCS_BASE : string
    }
    installLinks : OCP_DOCS_BASE changed from '.../openshift_container_platform/4.20/html' to '.../openshift_container_platform/latest/html'
Loading

File-Level Changes

Change Details Files
Use 'latest' alias for OCP documentation links
  • Replaced hard-coded version in OCP_DOCS_BASE constant with 'latest' for the base URL
src/common/installLinks.mjs

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey there - I've reviewed your changes - here's some feedback:

  • Consider extracting the repeated 'installing_on_google_cloud' path segment into its own constant to reduce duplication and ease future updates.
  • Since you switched OCP docs to 'latest', review other doc bases (OSD/ROSA) for potential consistency or document why they remain versioned.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- Consider extracting the repeated 'installing_on_google_cloud' path segment into its own constant to reduce duplication and ease future updates.
- Since you switched OCP docs to 'latest', review other doc bases (OSD/ROSA) for potential consistency or document why they remain versioned.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

revert replacement of `installing_on_google_cloud` with `installing_on_gcp`
@eliranmal eliranmal marked this pull request as ready for review November 11, 2025 15:26
Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey there - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Copy link
Contributor

@zherman0 zherman0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Code change looks fine. The test instructions say to run the check-links which I did. There are several issues still reported, but none have issue with using latest tg.

Copy link
Contributor

@t-hendricks t-hendricks left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested locally. LGTM!

@jmekkatt jmekkatt requested review from apecha and shivanthi-amara and removed request for jmekkatt November 13, 2025 05:25
@shivanthi-amara
Copy link
Contributor

@eliranmal I tried to execute this PR a couple of times using the command run/check-links.mjs. Below are my results

Screenshot 2025-11-17 at 7 00 16 AM

The redirect URLs having been failing with 403 errors as shown below. Kindly take a look.

Screenshot 2025-11-17 at 7 08 32 AM Screenshot 2025-11-17 at 7 04 50 AM

@eliranmal
Copy link
Collaborator Author

eliranmal commented Nov 17, 2025

@shivanthi-amara - as noted in other PRs, these problems due to request errors are unrelated to the changes, and seem to only happen on your system.

the only thing to really verify is that there's no regression; that the same number of successes/failures are reported before and after the change (provided that the request errors you're having are deterministic. matter of fact, you should not rely on them and either fix that or use another QE member's env for this verification)

@eliranmal
Copy link
Collaborator Author

eliranmal commented Nov 17, 2025

the request errors are apparently sporadic, and we were unable to determine their origin.

after discussing it (@shivanthi-amara and myself), we agreed to try and hand the verification to another QE member, in hope they're able to run the check-links script without those sporadic errors.

@shivanthi-amara - one lead i might have, is ECONNRESET errors are sometimes caused in the context of a bad VPN connection. maybe try to run the script without VPN?

@shivanthi-amara
Copy link
Contributor

@eliranmal I tried to execute this PR a couple of times using the command run/check-links.mjs. Below are my results

Screenshot 2025-11-17 at 7 00 16 AM The redirect URLs having been failing with 403 errors as shown below. Kindly take a look.

Screenshot 2025-11-17 at 7 08 32 AM Screenshot 2025-11-17 at 7 04 50 AM

@jmekkatt Please have a try from your end as well to confirm.

@jmekkatt
Copy link
Collaborator

@eliranmal I tried to execute this PR a couple of times using the command run/check-links.mjs. Below are my results
Screenshot 2025-11-17 at 7 00 16 AM
The redirect URLs having been failing with 403 errors as shown below. Kindly take a look.
Screenshot 2025-11-17 at 7 08 32 AM Screenshot 2025-11-17 at 7 04 50 AM

@jmekkatt Please have a try from your end as well to confirm.

@shivanthi-amara

 % ./run/check-links.mjs
Checking URLs...
Found 412 URLs to check

Testing redirect destinations...

URL CHECK RESULTS

Category                           Count
---------------------------------- ------
Total URLs skipped                     0
Success                              267
Redirects                            141
Redirects errors                       1
Client errors (4xx)                    4
Server errors (5xx)                    0
Request errors                         0
---------------------------------- ------
Total URLs checked                   412

SUCCESS:                                                                267 URLs
All these URLs returned status code 200 (OK)

REDIRECTS:                                                              141 URLs

[Status 301 - Moved Permanently (Resource at new location)] -            21 URLs

   21 redirect URLs tested successfully


[Status 302 - Found (Resource temporarily at different URL)] -           83 URLs

   82 redirect URLs tested successfully
  X 1 redirect URLs had errors

  [Original URL] https://console.aws.amazon.com/route53/v2/hostedzones
  [Redirect URL] https://us-east-1.console.aws.amazon.com/route53/v2/hostedzones
  [Redirect URL Test] 405


[Status 307 - Temporary Redirect (Resource temporarily moved)] -         37 URLs

   37 redirect URLs tested successfully


CLIENT ERRORS (4xx):                                                      4 URLs

[Status 405 - Method Not Allowed (Request method not supported)] -  4 URLs

  [Original URL] https://console.aws.amazon.com/ec2/home#SecurityGroups

  [Original URL] https://console.aws.amazon.com/rosa/home

  [Original URL] https://console.aws.amazon.com/rosa/home#/get-started

  [Original URL] https://issues.redhat.com/projects/OCPBUGS/issues


SERVER ERRORS (5xx):                                                      0 URLs
No server errors (5xx) found

REQUEST ERRORS:                                                           0 URLs
No request errors found

SKIPPED:                                                                  0 URLs
No URLs were skipped

--------------------------------------------------------------------------------
Total URLs checked:                                                     412 URLs
--------------------------------------------------------------------------------

Note: Run with -v or --verbose to see URLs for successful requests and redirects
      Run with -r or --redirects to see ONLY redirected URLs with targets
      Run with -h or --help for more information

@eliranmal
Copy link
Collaborator Author

@jmekkatt , it seems that this is the expected results, can you approve? or should @shivanthi-amara take it from here?

@apecha
Copy link

apecha commented Nov 24, 2025

@eliranmal I tried run links check several times. It isn't consistent with reporting same amount of the errors. Example:
1st run:

URL CHECK RESULTS

Category                           Count
---------------------------------- ------
Total URLs skipped                     0
Success                              265
Redirects                            141
Redirects errors                      14
Client errors (4xx)                    4
Server errors (5xx)                    1
Request errors                         1
---------------------------------- ------
Total URLs checked                   412

SUCCESS:                                                                265 URLs
All these URLs returned status code 200 (OK)

REDIRECTS:                                                              141 URLs

3rd run:

URL CHECK RESULTS

Category                           Count
---------------------------------- ------
Total URLs skipped                     0
Success                              233
Redirects                             85
Redirects errors                       1
Client errors (4xx)                   70
Server errors (5xx)                    1
Request errors                        23
---------------------------------- ------
Total URLs checked                   412

SUCCESS:                                                                233 URLs
All these URLs returned status code 200 (OK)

REDIRECTS:                                                               85 URLs

cc: @jmekkatt, @shivanthi-amara
Is this blocking approval?

I will also check docs links manually as per linked test case to the Jira card

@eliranmal
Copy link
Collaborator Author

eliranmal commented Nov 27, 2025

@apecha - it shouldn't block approval cuz the links can be tested manually

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants