Project

General

Profile

Bug #6104

"Product Content" tab shows content sets not applicable to the content host

Added by Thomas McKay over 5 years ago. Updated 4 months ago.

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

Description

Having both 6Server and 5Server content sets available under a subscription means that both will show up on the content host's "Product Content" tab. The redhat.repo file, however, will only be populated with the content set that matches its version (eg. just the 6Server content will show up in the redhat.repo file on a 6Server host). Kickstart content sets also are displayed when they too will not be in the redhat.repo.

Candlepin needs to provide a mechanism to query what the redhat.repo file really looks like on the client.

History

#1 Updated by Thomas McKay over 5 years ago

  • Bugzilla link set to https://bugzilla.redhat.com/show_bug.cgi?id=1105716

#2 Updated by Eric Helms over 5 years ago

  • Triaged changed from No to Yes

#3 Updated by Eric Helms over 5 years ago

  • Target version changed from 45 to 48

#4 Updated by Eric Helms over 5 years ago

  • Target version deleted (48)

#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

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

#7 Updated by Brad Buckingham about 3 years ago

  • Category changed from Candlepin to Subscriptions

Based on feedback from candlepin team, this is not a candlepin issue; therefore, updating the category so that the same may be propagated to the downstream bugzilla.

#8 Updated by John Mitsch 4 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