Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
It looked like "relatively easy task", but apparently it is not.
We do not store product and/or repository references for each package/group/category items in templates. Therefore I don't know to which repository a category belogs to. And this is a problem. I need this to get list of groups from a category in Pulp.
The issue is more generic - I will send an email about that. In my case solutions are:
a) Postpone this and do not support package groups for now.
b) Code the "unwrapping" logic to loop through all repositorories trying to find a package group with the same name. If more than one is found, an error will be issued.
c) Add repository references for each item in the template. This is a bigger change: model change, change in the UI and CLI to support this.
I doubt package group categories are useful. We support them since Pulp
is able to work with them, but for provisioning and template management
they are useless I guess.
They cannot be used in yum. They cannot be used in kickstarts. Only
Anaconda use them to visualize package groups in a better way.
I recommend to remove this feature from templates. We should be able to
track them, display them when working with repositories, but I miss the
point to have them in system templates.
It would be much easier to implement this in ImageFactory, but I am not sure if
this is technically possible. Categories are maybe not visible to yum.
https://bugzilla.redhat.com/show_bug.cgi?id=788560