-
Notifications
You must be signed in to change notification settings - Fork 114
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
Update and fix RHCloud tests part one #16751
base: master
Are you sure you want to change the base?
Update and fix RHCloud tests part one #16751
Conversation
trigger: test-robottelo |
PRT Result
|
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.
LGTM, makes sense from what we talked about
trigger: test-robottelo |
PRT Result
|
trigger: test-robottelo |
|
PRT Result
|
PRT Result
|
trigger: test-robottelo |
PRT Result
|
# Register client with insights | ||
if self.execute('insights-client --register').status != 0: | ||
raise ContentHostError('Unable to register client with insights') |
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 manual install and register for insight-client would be required only when register=False, so could this move in if-else?
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.
This code is weird. Basically, we register a host in order to create the custom repos needed for insights(these base OS repos are too big to enable and sync every test). Insights client does not register during this. Its only when we install packages and manually register at the end that insights gets set up.
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.
+1 to the workflow, it's dumb but this works.
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.
@ColeHiggins2 I don't understand why are we moving the registration part at the start of the configure_insights_client
. We probably should remove yum install -y insights-client
part here as the insights-client
should get install during host registration process, we don't need to do it manually.
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.
Since its general helper which install and insights during registration process when register=True
, and when register=False
we should do these setup manually
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.
It's probably better to get rid of this helper, it's very old and it's definition and usage are now very confusing. We can keep the creating custom repo part(and rename it accordingly) and then do registration like we normally do using global registration command.
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.
@ColeHiggins2 I already suggested the same thing on your last PR #16497 (comment),
But if we consider getting rid of this helper itself, so I'd suggest using repo_data
option in global registratio, with this option while registering we could pass custom repos and it creates foreman_register repo in /etc/yum.repos.d/.
For 6.16 and stream, it does support creating multiple repos now, and it creates foreman_register1, foreman_register2 repo files in /etc/yum.repos.d/
# Register client with insights | ||
if self.execute('insights-client --register').status != 0: | ||
raise ContentHostError('Unable to register client with insights') |
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.
@ColeHiggins2 I don't understand why are we moving the registration part at the start of the configure_insights_client
. We probably should remove yum install -y insights-client
part here as the insights-client
should get install during host registration process, we don't need to do it manually.
Test fixes for RHCloud.