-
Notifications
You must be signed in to change notification settings - Fork 55
RHDHBUGS-2274: Changes to the RHOAI docs #1588
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
base: main
Are you sure you want to change the base?
Conversation
|
Updated preview: https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-1588/ @ 11/20/25 12:41:51 |
|
As part of my PR review @pabel-rh I'll use the YAML from https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-1588/ to set up the connector, and confirm we avoid the hiccups James hit. |
|
Independent of the code changes @pabel-rh I noticed this sort of duplication: perhaps rather than printing out the yaml for the WDYT? |
gabemontero
left a comment
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.
some changes wrt the message warnings in the container logs
as part of that, the image ref for the location container should be changed to
quay.io/redhat-ai-dev/model-catalog-location-service@sha256:763311530fb842a1366447e661ca22563e6ef22505d993716aea350bbbfae9a0
| + | ||
| [NOTE] | ||
| ==== | ||
| During startup, you may see non-critical log errors, such as `connection refused` or `in cluster config error: open /var/run/secrets/kubernetes.io/serviceaccount/token: no such file or directory`, in the sidecar logs (in the `location` container). These errors are expected during the initial setup and do not indicate a failure, provided the container eventually becomes healthy. |
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 this should be moved to the top of the troubleshooting section
Also, let's leave the text as is for now, but as I mentioned in slack and the Jira, if I can get rid of the connection refused error James was citing, let's then remove it from this warning
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.
yep the change to remove messages like
E1113 16:13:29.258658 1 server.go:102] Get "http://10.128.2.58:7070/list": dial tcp 10.128.2.58:7070: connect: connection refused
from the location container are now in place
7f3815c to
b335c18
Compare
|
forgot to mention here (though I did in the Jira bug) - I was able to grab the sidecar yaml from the preview server's display, insert in the backstage CR instance via this includes the normalizer's metrics port getting set to 8081 so it did not conflict with lightspeed's 8080 |
|
@pabel-rh can you let me know here when the preview server is updated with the responses to my comments (it did not appear to be when I checked just now). at this point that is the easier way for me to review at this point :-) |
IMPORTANT: Do Not Merge - To be merged by Docs Team Only
Version(s):
1.8, main
Issue:
RHDHBUGS-2274
Preview:
https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-1588/openshift-ai-connector-for-rhdh/