Description of problem: After upgrading to 6.3, promoting an old CV failed with the below errors INFO 2018-06-15 09:54:29 API] Server: https://example.com [ INFO 2018-06-15 09:54:29 API] POST /katello/api/content_views/3/publish [DEBUG 2018-06-15 09:54:29 API] Params: { "description" => "June 2018 RH Updates", "force_yum_metadata_regeneration" => true } [DEBUG 2018-06-15 09:54:29 API] Headers: {} [DEBUG 2018-06-15 09:54:29 API] Using authenticator: HammerCLIForeman::Api::InteractiveBasicAuth [ERROR 2018-06-15 09:54:33 API] 500 Internal Server Error [DEBUG 2018-06-15 09:54:33 API] { "displayMessage" => "hostname \"example.old.com\" does not match the server certificate", "errors" => [ [0] "hostname \"example.old.com\" does not match the server certificate" <---------------------------- ] } Note: the "example.old.com" is an old hostname which got renamed in 6.2 by using katello-change-hostname. Version-Release number of selected component (if applicable): 6.3.1 How reproducible: Hard Steps to Reproduce: 1. staring with satellite 6.2.14 2. changing hostname with katello-change-hostname 3. upgrading to satellite 6.3 4. hammer -d content-view publish --description 'June 2018 RH Updates' --force-yum-metadata-regeneration 1 --id 3 --organization-id 3 Actual results: 500 Internal Server Error Expected results: The CV should be promoted successfully.
A few questions: 1) Did you experience any issues during the upgrade? 2) Can you grep for your old hostname in /etc/ (and any other directories you think may be related) 3) Do you only get this error from hammer, will promoting the content view via the UI work? 4) Is there a traceback?
adding needsinfo for questions above
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.