Project

General

Profile

Bug #7364

Katello host environment is not updated upon registration to itself

Added by Stephen Benjamin about 5 years ago. Updated about 2 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Hosts
Target version:
-
Difficulty:
medium
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

If you sub-man register the Katello server to itself, should we also update the Foreman host to be in the corresponding puppet environment?

Today it stays in 'production'.


Related issues

Related to Katello - Tracker #8161: Host UnificationRejected

History

#1 Updated by Eric Helms about 5 years ago

  • Legacy Backlogs Release (now unused) set to 14
  • Difficulty set to medium
  • Triaged changed from No to Yes

#2 Updated by Eric Helms almost 5 years ago

  • Legacy Backlogs Release (now unused) changed from 14 to 23

#3 Updated by Eric Helms over 4 years ago

  • Legacy Backlogs Release (now unused) changed from 23 to 31

#4 Updated by Eric Helms over 4 years ago

  • Legacy Backlogs Release (now unused) deleted (31)

#5 Updated by Eric Helms almost 4 years ago

  • Legacy Backlogs Release (now unused) set to 86

#6 Updated by Eric Helms almost 4 years ago

#7 Updated by Eric Helms over 3 years ago

  • Legacy Backlogs Release (now unused) changed from 86 to 143

#8 Updated by Justin Sherrill over 3 years ago

  • Legacy Backlogs Release (now unused) changed from 143 to 114

#9 Updated by John Mitsch about 2 months ago

  • Target version deleted (Katello Backlog)
  • Status changed from New to Rejected

Thanks for reporting this issue. This issue was created over 4 years ago and hasn't seen an update in 1 year. We are closing this in an effort to keep a realistic backlog. Please open up a new issue that includes a link to this issue if you feel this still needs to be addressed. We can then triage the new issue and reassess.

Also available in: Atom PDF