Bug 1962253
Summary: | Global registration succeeded but throwing error messages when auto-attach is true | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Gaurav Talreja <gtalreja> |
Component: | Registration | Assignee: | Leos Stejskal <lstejska> |
Status: | CLOSED ERRATA | QA Contact: | Gaurav Talreja <gtalreja> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.10.0 | CC: | ahumbe, lstejska, oezr, okhatavk, vijsingh |
Target Milestone: | 6.12.0 | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | foreman-3.1.1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-11-16 13:32:29 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Gaurav Talreja
2021-05-19 15:17:10 UTC
Are you sure this host wasn't reused for testing, e.g. it was properly unregistered before you tried the new registration? Is the 'attempting' really part of the output or you replaced the UUID with this? I can imagine that auto-attach modifies the stdout of the sub-man identity command we use to find out the UUID from. That's why we'd see "attempting" as a wrong UUID. Hi, I wasn't able reproduce the issue, registration with activation key auto_attach: true works fine. I'm proposing to close the issue as NOT A BUG Hi Leos/Marek, Yes, `insights-client` related errors are expected, as I didn't have rhel7-server repos for it, and using custom repos for testing. I've been trying to reproduce on Snap 19 and was able to reproduce it again. So to reproduce, I'm reusing the same host across 2 satellite boxes, after using the host on the first satellite, I properly unregister/clean before reusing this host for testing, also deleted the host from Satellite WebUI, also removed the katello-ca-consumer-* package, and while registering the same host to the second host I'm hitting this issue. I'm not sure if this host remains semi-registered as you mentioned after the first satellite sub-man clean/unsubscribe, what steps do I need to follow for complete unsubscribed? Please let me know if you need anything or am I missing something. Thanks, Gaurav Hi, sorry but I do not understand the third point: > regenerate the command without `the ignore_subman_errors` when the command contains `ignore_subman_errors=false`? Whats the value of `the ignore_subman_errors`? > So it seems parameter ignore_subman_errors is being set true if we set false in step3, is that expected? No that is not expected, i can confirm that it's a bug. Created redmine issue https://projects.theforeman.org/issues/34206 from this bug Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34206 has been resolved. Hi Gaurav, the error messages says: "Unable to find available subscriptions for all your installed products." Registration failed (correctly) due to error when installing insights-client, my guess is that you don't have correct subscriptions and repositories enabled in satellite. This is not related to the registration feature at all, it's between subscription manager and subscriptions, there is nothing I can do with it. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: Satellite 6.12 Release), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:8506 |