Tracker #18273: hostname change issues - Katello - Foreman

Actions

Tracker #18273

closed

hostname change issues

Added by John Mitsch over 8 years ago. Updated almost 7 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

-

Target version:

Katello Recycle Bin

% Done:

0%

Difficulty:

Triaged:

Bugzilla link:

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

These are issues that are found from running katello-change-hostname

Related issues 6 (0 open — 6 closed)

	Related to Katello - Bug #18263: Resyncing of RH kickstart repos after the hostname change - failed	Resolved	John Mitsch	01/26/2017			Actions
	Related to Katello - Bug #18266: after running the hostname change, the old hostname is still showing in the content host registration page	Resolved	John Mitsch	01/26/2017			Actions
	Related to Katello - Bug #18267: https://katello.example.com/pub shows entries for the old hostname	Closed	John Mitsch	01/26/2017			Actions
	Related to Katello - Bug #18268: Unable to pull content from katello after registering a content host after hostname change process	Closed		01/26/2017			Actions
	Related to Katello - Bug #18270: after hostname change - publishing a content view with puppet modules in it throws ssl error	Closed	John Mitsch	01/26/2017			Actions
	Related to Katello - Bug #18403: capsule sync not working after hostname change	Closed	John Mitsch	02/06/2017			Actions

Actions

#1

Updated by John Mitsch over 8 years ago

Related to Bug #18263: Resyncing of RH kickstart repos after the hostname change - failed added

Actions

#2

Updated by John Mitsch over 8 years ago

Related to Bug #18266: after running the hostname change, the old hostname is still showing in the content host registration page added

Actions

#3

Updated by John Mitsch over 8 years ago

Related to Bug #18267: https://katello.example.com/pub shows entries for the old hostname added

Actions

#4

Updated by John Mitsch over 8 years ago

Related to Bug #18268: Unable to pull content from katello after registering a content host after hostname change process added

Actions

#5

Updated by John Mitsch over 8 years ago

Related to Bug #18270: after hostname change - publishing a content view with puppet modules in it throws ssl error added

Actions

#6

Updated by John Mitsch over 8 years ago

Related to Bug #18403: capsule sync not working after hostname change added

Actions

#7

Updated by Eric Helms over 8 years ago

Project changed from Packaging to Katello

Actions

#8

Updated by John Mitsch about 8 years ago

Status changed from New to Resolved

Actions

#9

Updated by John Mitsch about 8 years ago

Status changed from Resolved to Closed

Actions

#10

Updated by John Mitsch about 8 years ago

Translation missing: en.field_release set to 166

Actions

Also available in: Atom PDF