Bug #18270
after hostname change - publishing a content view with puppet modules in it throws ssl error
Description
1. Create a custom product
- with yum repo
- with puppet module
2. Sync the custom product
3. Create a content view - add the yum repo from step 1 and also the puppet module from step 1
4. Publish the content view, promote to multiple environments
5. Run the hostname change script
6. Republish the content view from Step 4
Actual results:
Errored. see attachment
Related issues
Associated revisions
History
#1
Updated by John Mitsch over 5 years ago
- Related to Tracker #18273: hostname change issues added
#2
Updated by Eric Helms over 5 years ago
- Project changed from Packaging to Katello
#3
Updated by Eric Helms over 5 years ago
- Category set to Tooling
- Status changed from New to Assigned
- Assignee set to John Mitsch
- Legacy Backlogs Release (now unused) set to 211
#4
Updated by John Mitsch over 5 years ago
- Target version set to 169
#5
Updated by John Mitsch over 5 years ago
- Project changed from Katello to Packaging
- Category deleted (
Tooling)
#6
Updated by John Mitsch over 5 years ago
- Blocked by Bug #18828: Can't publish a content view version with a puppet module added
#7
Updated by Brad Buckingham over 5 years ago
- Target version changed from 169 to 178
#8
Updated by The Foreman Bot over 5 years ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/Katello/katello-packaging/pull/400 added
#9
Updated by John Mitsch about 5 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset katello:katello-packaging|81c2e29a891b813c82bd1632b53337812847333c.
#10
Updated by Eric Helms about 5 years ago
- Project changed from Packaging to Katello
- Pull request deleted (
https://github.com/Katello/katello-packaging/pull/400)
Fixes #18270 - Restart puppet services after hostname change