Bug 1456782 - Host deletion via API does not remove puppet cert from puppet CA
Summary: Host deletion via API does not remove puppet cert from puppet CA
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Puppet
Version: 6.2.9
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Depends On:
Blocks: 1541321
TreeView+ depends on / blocked
 
Reported: 2017-05-30 11:17 UTC by Jordi Claret
Modified: 2022-03-13 14:18 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-07 11:57:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jordi Claret 2017-05-30 11:17:15 UTC
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:

Comment 7 Alberto Losada 2017-07-25 07:39:59 UTC
This issue affects Satellite 6.2.10 as well

Comment 11 Mike McCune 2017-08-15 17:14:27 UTC
 Jordi Claret, we can't reproduce this on 6.2.11, can you assist to see if this can be reproduced with the latest version?

Comment 16 gunter1 2018-04-27 20:50:49 UTC
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.

Comment 17 Bryan Kearney 2018-11-30 15:00:53 UTC
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.

Comment 20 Bryan Kearney 2019-01-04 13:18:18 UTC
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.

Comment 22 Bryan Kearney 2019-02-07 11:57:21 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.