insights-vulnerability lab: Host not connected to Red Hat Insights #474
Assignees
Labels
bug
Something isn't working
Comments
|
rhc connect is already included in the lab setup, i wonder if this was a one-off issue, is this a reproducible and persistent issue? |
|
@nlager This appears to be an intermittent issue. I have run the lab about 5 times and it has happened twice now. If you run
I am running a workshop tomorrow for maybe 40 people and am concerned this won't be reliable enough to give them as an exercise to do themselves. |
|
Enabled setup-logging, so we could see what's happening as the lab provisions. Here is the output from my rhc connect during deployment. It suggests that in fact rhc connected to insights.. However rhc status confirms, it is in fact NOT connected to insights. I am going to try to clean up the subscription manager and rhc commands in setup, to see if this helps at all, it cant hurt anyway. |
|
I have cleaned up the process, and the issue persists. I believe this to be an insights or rhc bug rather than a lab issue. I am looking for a work-around. |
|
running an rhc connect after provisioning claims to register the system with insights, but in fact does not. It sits at the registering to insights step for about 10 seconds, reports success, then rhc status reports that the system is not connected. Log data: Logs from the rhc status, same log as above. |
|
This gets even worse for this host.. Running insights-client --register also runs, and reports success, but then running insights-client to get it to collect and report, tells me its not registered to insights. Also, the inventory in insights is showing me 5 entries for this host now. I think this needs to be reported to the insights team as a bug. |
|
One more test, I tried to focus on insights-client. this system ended up in my insights inventory 5 times as well. |
|
Allll right @benblasco I think this is fixed, if you have similar issues again you can mention it in #insights on slack. If they insist its not their problem let us know and I can continue troubleshooting. |
|
I updated the first step to run 'rhc connect' instead of 'rhc status'. |
|
Hi all, I do not believe the issue is any closer to being resolved. Here's what happens when I run some checks right at the start of the lab:
I have reopened the bug as a consequence, and attached the rhsm and insights logs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
Upon launching the insights-vulnerability lab, the host is not showing as being in the correctly connected status for the rest of the lab.
Work-around
Run the
rhc connectcommand to ensure the host is registered with Insights.Solution proposal
Either make sure the host is connected to Insights on launch, or add a call to either
rhc connectorinsights-client --registerto the instructions.The text was updated successfully, but these errors were encountered: