Project

General

Profile

Actions

Bug #26191

closed

Registering a system fails randomly (409 Conflict)

Added by Jonathon Turel almost 6 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Category:
Hosts
Target version:
Fixed in Releases:
Found in Releases:

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.


Related issues 1 (0 open1 closed)

Related to Katello - Bug #26480: registration fails if puppet fact with dmi::system::uuid exists in foremanClosedJustin SherrillActions
Actions

Also available in: Atom PDF