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.
Description of problem:
host has some puppet class,
update host puppet classes via API to empty puppet classes does not update the classes
Version-Release number of selected component (if applicable):
7.0 snap 5 and 6
regression from sat 6.10
How reproducible:
Always
Steps to Reproduce:
0. Enable puppet on satellite 7
1. Import puppet class to some <puppet_env>, e.g <generic_1> (puppet module install)
2. create host with puppet environment, default proxy, puppet class
3. check that host has the puppet class assigned, by api request or by ui puppet YAML button, cli is not showing puppet classes
UI shows:
classes:
<generic_1>:
environment: <puppet_env>
4. update the host with empty puppet class, remove the puppet class
5. puppet class is not removed
still showing the same info and in UI Puppet environment -> <puppet_env> -> Classes, shows <generic_1> has 1 one host.
Actual results:
puppet class is not updated
Expected results:
puppet class is updated
classes: {}
Additional info:
adding works fine and removing as well if we do not update via API to empty list of puppet classes
removal via UI works
# CLI
hammer -d host update --id <host-id> --puppetclasses
# API
{"host": {"puppetclass_ids": []}}
FYI, puppetclass_ids are deprecated, the path looks like host/puppet_attributes/puppetclass_ids
The same problem occurs also for:
{"host": { "puppet_attributes": {"puppetclass_ids": []}}}
running under admin/root
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: Satellite 6.11 Release), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2022:5498
Description of problem: host has some puppet class, update host puppet classes via API to empty puppet classes does not update the classes Version-Release number of selected component (if applicable): 7.0 snap 5 and 6 regression from sat 6.10 How reproducible: Always Steps to Reproduce: 0. Enable puppet on satellite 7 1. Import puppet class to some <puppet_env>, e.g <generic_1> (puppet module install) 2. create host with puppet environment, default proxy, puppet class 3. check that host has the puppet class assigned, by api request or by ui puppet YAML button, cli is not showing puppet classes UI shows: classes: <generic_1>: environment: <puppet_env> 4. update the host with empty puppet class, remove the puppet class 5. puppet class is not removed still showing the same info and in UI Puppet environment -> <puppet_env> -> Classes, shows <generic_1> has 1 one host. Actual results: puppet class is not updated Expected results: puppet class is updated classes: {} Additional info: adding works fine and removing as well if we do not update via API to empty list of puppet classes removal via UI works