-
Notifications
You must be signed in to change notification settings - Fork 115
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
Fix katello-agent #12395
Fix katello-agent #12395
Conversation
trigger: test-robottelo |
trigger: test-robottelo |
trigger: test-robottelo |
Okay, so with |
c311e21
to
010074c
Compare
trigger: test-robottelo |
Seems reasonable to not overinvest effort into this feature that will only be run on older branches, as long as they pass consistently. |
010074c
to
1334900
Compare
trigger: test-robottelo |
1334900
to
9ecfb9d
Compare
rebased |
robottelo/hosts.py
Outdated
# Override the repos to enabled if needed | ||
if override: | ||
rhel_contenthost.execute(r'subscription-manager repos --enable \*') | ||
|
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.
Just curious, I thought custom repos will be disabled in only AK itself, or Library would contain this disabled as well? and can't we change state of this repos either in product/LCE we're using instead of doing this on host?
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.
Custom repos are disabled by default, regardless AK existence. If you register a host using this function, they are present/visible on both sides, but disabled. This enables them on both sides too, so it seems valid way to me. Unless you have some nicer way.
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.
what do you mean by both sides here? host and ?
Currently, register_host_custom_repo
uses the old registration method, instead we should be using new Global registration method which will work with AK and we could easily override the repos for host in AK, but it feels out of scope of this PR :)
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.
Both sides I mean - Host itself (in /etc/yum.repos.d
) and Satellite (in host details).
For host registration rewrite - I think it would deserve a separate PR.
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.
yes, definately, can you create an issue for this? so we don't miss this :)
9ecfb9d
to
9f027ca
Compare
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.
Ack looks good !
10dbe86
to
9a11e9e
Compare
trigger: test-robottelo |
In PRT#3833 19 tests passed, 1 failed in host registration with this errror
I guess that we hit the rare case when the same hostname was used for the second time in the same session against the same SAT. We could probably unregister the host on teardown. EDIT: Rolling back the explicit unregister, this is actually done in contenthost teardown. The intermittent issue shall be resolved by 12466 |
9a11e9e
to
6085c8a
Compare
trigger: test-robottelo |
In PRT#3847 18 passed, 2 failed with
I think we are good to go @Gauravtalreja1 |
6085c8a
to
3ae6c74
Compare
Let katello-agent run on a standard VM (cherry picked from commit f85639f)
Fix katello-agent (#12395) Let katello-agent run on a standard VM (cherry picked from commit f85639f) Co-authored-by: vsedmik <[email protected]>
Let katello-agent run on a standard VM
Let katello-agent run on a standard VM
Let katello-agent run on a standard VM
Let katello-agent run on a standard VM
Let katello-agent run on a standard VM
In this PR I propose two changes:
PRT results:
no_containers:
with containers: