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:
Deleting for host via bootstrap.py script (--remove option) does not remove puppet certificate on Satellite. It seems a regression between 6.2.6 (puppet cert clean works fine) and 6.2.9 (puppet cert clean doesnt work).
Version-Release number of selected component (if applicable):
Sat 6.2.9
How reproducible:
100%
Steps to Reproduce:
1.- register server via bootstrap.py script on node and check puppet cert is present on satellite (puppet auto-sign per domain)
On client
[root.com ~]# ./bootstrap.py -l admin -p pass -s satellite.example.com -o example -L bcn -g rhel -a redhat -O "RedHat 7.3" --force
On server
[root@satellite]# puppet cert list --all (once subscribed)
+ "rhel7.example.com" (SHA256) 29:FD:D1:CC:07:43:F5:87:4D:E4:6F:55:31:15:EC:05:E4:F8:9B:9E:ED:EB:BD:77:38:0E:AE:40:AD:8B:E7:CB
+ "satellite.example.com" (SHA256) 23:C3:36:29:4F:6D:F9:E0:E3:9B:94:BE:5F:9B:F8:1A:8C:C8:1B:46:D5:F2:29:77:E9:1F:24:4A:E1:E6:73:63 (alt names: "DNS:puppet", "DNS:puppet.example.com", "DNS:satellite.example.com")
2.- unregister node via bootstrap.py script and check if puppet cert is removed
On client
[root.com ~]# ./bootstrap.py -l admin -p pass -s satellite.example.com --remove
On server
[root@satellite foreman]# puppet cert list --all (once unsubscribed)
+ "satellite.example.com" (SHA256) 23:C3:36:29:4F:6D:F9:E0:E3:9B:94:BE:5F:9B:F8:1A:8C:C8:1B:46:D5:F2:29:77:E9:1F:24:4A:E1:E6:73:63 (alt names: "DNS:puppet", "DNS:puppet.example.com", "DNS:satellite.example.com")
We can see the following command on Satellite during unsubscribe process :
foreman+ 7353 6569 0 10:51 ? 00:00:00 sh -c /usr/bin/sudo -S /usr/bin/puppet cert --ssldir /var/lib/puppet/ssl --clean rhel7.example.com 2>&1
Actual results:
Puppet client cert was not removed and it must be removed manually o from Satellite WebUI
Expected results:
Puppet client cert is removed when host is deleted.
Additional info:
I can confirm this still happens on 6.2.14
Host registered with bootstrap script creates and autosigns the puppet CA cert correctly.
When the host is unregistered with the following, the certificate is not removed, although all other removal functions appear normal.
# ./bootstrap.py -l <administrator> -s <satellite.example.com> --remove
To complete the host removal, the cert must be removed via the web UI or puppet server command line.
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Rich Jerrido or Bryan Kearney or your account team. If we do not hear from you, we will close this bug out. Thank you.
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.