-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] On ubuntu machines, x509.certificate_managed is allocating a new certificate on every run. #59170
Comments
See also #52180 |
I can confirm this problem after upgrading to 20.04 with 3001.4. |
Ok, I thought this should be a good way to kill a couple issues with a single patch and just begun my tests. Did the test with Debian 10 master and minion and an Ubuntu 20.04 minion. For both cases I installed Salt with this procedure:
In the minion-only machine the last line ommits the To have the To do the test I used this state:
In the first run the certificate was created, as stated by the original poster:
But, contrary to this report, the second run did as it should be, recognizing that the certificate already exists and didn't creating a new one:
I guess this was fixed or in the modules used by Ubuntu or by some changes in Salt between minion: salt-call --versions-reportSalt Version: Salt: 3003Dependency Versions: System Versions: master/minion: salt-call --versions-reportSalt Version: Salt: 3003Dependency Versions: System Versions: Am I doing something wrong in the tests? Should I test against the |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as outdated.
This comment was marked as outdated.
That was released in 3001.1, so probably not. Also, OP reported this for 3002.2. |
Closing this issue since:
|
Description
Most of my hosts are Debian (buster), but I have 2x Ubuntu 20.04 (focal) boxes.
On the ubuntu hosts, x509.certificate_managed is generating a new certificate on every salt run. On the Debian hosts, it does not.
Setup
It's pretty much the setup documented at: https://docs.saltstack.com/en/latest/ref/states/all/salt.states.x509.html
x509.conf looks like:
Steps to Reproduce the behavior
On the ubuntu hosts, every time I do a salt run, it generates a new certificate. It seems to think the public key is different, but it is not.
Expected behavior
It should only generate a certificate if one doesn't exist or is close to expiry. This works as expected on my Debian hosts, but not my Ubuntu hosts.
Versions Report
salt --versions-report
(Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: