Bug #26191
closedRegistering a system fails randomly (409 Conflict)
Description
Description of problem:
Sometimes, when I register a system to the server, subscription-manager fails, showing no error. The return code is 70 and new system ID and name is not shown, as opposed to a successful run.
rhsm.log on the client shows RestlibException and response status 409, see attached traceback.
production.log on the server shows "RestClient::Conflict: 409 Conflict" and a traceback, also see attached.
This seems to happen for every second attempt to register in a cycle:
1) # subscription-manager clean
2) change system hostname
3) # subscription-manager register ...
However, I don't think the bug is totally deterministic - at some times, the above doesn't happen and then starts happening again during the same script run.
Actual results:
No error message output, s-m return code 70, tracebacks, system not registered.
Expected results:
System registered successfully.
Updated by The Foreman Bot almost 6 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/katello/pull/7991 added
Updated by John Mitsch almost 6 years ago
- Subject changed from Registering a system fails randomly (409 Conflict) to Registering a system fails randomly (409 Conflict)
- Category set to Hosts
- Target version set to Katello 3.12.0
- Triaged changed from No to Yes
Updated by Jonathon Turel almost 6 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset katello|94fdc4456bffe91590be2294e90cad548f8dae24.
Updated by Justin Sherrill almost 6 years ago
- Related to Bug #26480: registration fails if puppet fact with dmi::system::uuid exists in foreman added
Updated by The Foreman Bot almost 6 years ago
- Pull request https://github.com/Katello/katello/pull/8066 added