When uploading a manifest to a satellite/foreman server after updating it or redefining it, the manifest role appears to not automatically try to refresh the manifest and instead fails. Also, trying to write a recovery fails if the manifest has been deleted on the portal...
TASK [satellite_post : Try to upload] ******************************************************************************
fatal: [sat.example.ca]: FAILED! => {"changed": false, "msg": "Upload of the manifest failed: Owner has already imported from another subscription management application. The following conflicts were found: [ DISTRIBUTOR_CONFLICT ]"}
TASK [satellite_post : Try to refresh existing] ********************************************************************
fatal: [sat.example.ca]: FAILED! => {"changed": false, "error": {"displayMessage": "The Subscription Allocation providing the imported manifest has been removed. Please create a new Subscription Allocation and import the new manifest.", "errors": ["The Subscription Allocation providing the imported manifest has been removed. Please create a new Subscription Allocation and import the new manifest."]}, "msg": "Error while performing refresh_manifest on subscriptions: 400 Client Error: Bad Request for url: https://sat.example.ca/katello/api/organizations/1/subscriptions/refresh_manifest"}
I can understand why this may behave the way it does... avoiding the whole reattach all the subs thing. But a "force: true" parameter might be a nice add.
SUMMARY
When uploading a manifest to a satellite/foreman server after updating it or redefining it, the manifest role appears to not automatically try to refresh the manifest and instead fails. Also, trying to write a recovery fails if the manifest has been deleted on the portal...
ISSUE TYPE
ANSIBLE VERSION
COLLECTION VERSION
KATELLO/FOREMAN VERSION
STEPS TO REPRODUCE
EXPECTED RESULTS
The subscription is refreshed or replaced.
ACTUAL RESULTS
Errors below...