Registering a system fails randomly (409 Conflict)
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.
No error message output, s-m return code 70, tracebacks, system not registered.
System registered successfully.