Description of problem: After creating a Content item with a gpgUrl and then updating the Content by unsetting the gpgUrl the redhat.repo file on disk still contains 'gpgcheck = 1'. This was found in CP: candlepin-0.9.42-1.el7.noarch API Call: Resource PUT request: /candlepin/content/1427685253045, {"id":"1427685253045","name":"1.7 Plugins","contentUrl":"/custom/Foreman/1_7_Plugins","gpgUrl":null,"type":"yum","label":"Default_Organization_Foreman_1_7_Plugins","vendor":"Custom"} Note this was done on upstream Katello that uses Candlepin.
I can see the same behavior. It is one or more bugs in subscription-manager on client side. I will raise bugs against it. For the record, the API you used has been changed. Now to update the content you must use: to get information about a content: GET /candlepin/owners/{owner}/content/{content_id} to update it: PUT /candlepin/owners/{owner}/content/{content_id} {"uuid":"ff8080815036ca63015036ca8343005f","id":"11113","type":"yum","label":"awesomeos","owner":{"id":"ff8080815036ca63015036ca7a050004","key":"snowwhite","displayName":"Snow White","href":"/owners/snowwhite"},"name":"awesomeos","vendor":"Red Hat","contentUrl":"/path/to/$basearch/$releasever/awesomeos","requiredTags":null,"releaseVer":null,"gpgUrl":null,"metadataExpire":3600,"modifiedProductIds":[],"arches":null,"created":"2015-10-05T06:57:32.995+0000","updated":"2015-10-05T06:57:32.995+0000"}
Note that possible workaround for this issue is to reattach pools that provide the content.
Eric I reproduced the issue and I am investigating it further. But because the bugreport is quite old, my question is whether you still need this fixed? Also, isn't workaround in Comment 2 good enough for you?
Closing this as this is not Candlepin bug. Created two issues on Subman to solve this: 1269147, 1269152