-
Notifications
You must be signed in to change notification settings - Fork 44
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
Add the troubleshoot item for "Calling Remote API Errors" #45
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jinhli It looks like two files were included in the PR, I think you only wanted to update the troubleshooting guide.
|
||
## <a id="callingremoteapierrors"></a>Calling Remote API Errors | ||
Possible causes: | ||
- You are using the old opsid in --certification-project-id, you could find the project id in project link https://connect.redhat.com/projects/1234567890/overview |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the wording here should be consistend with the --help
output of preflight
You can see that verbiage here
@jinhli: PR needs rebase. 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/test-infra repository. |
For some old projects, the ospid and project id are different. If the older ospid is using in the preflight test, it will cause "calling remote api errors"