Bug #10734
closed
Installation fails due to broken nss/nss-softokn detection on CentOS6
Added by Alexis Mousset over 7 years ago.
Updated over 7 years ago.
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Very Small
Description
ON an up to date CentOS6, I get:
nss version mismatch, your nss-softokn version (3.14.3) should match your nss version (3.28.4)
I indeed have:
nss-3.28.4-1.el6_9.x86_64
nss-softokn-3.14.3-23.3.el6_8.x86_64
And have no available upgrade.
- Related to Bug #9905: java.lang.InternalError when calling the internal API on Redhat because of invalid version of nss added
- Target version set to 3.1.20
- Subject changed from Broken nss/nss-softokn detection on CentOS6 to Installation fails due to broken nss/nss-softokn detection on CentOS6
- Severity set to Critical - prevents main use of Rudder | no workaround | data loss | security
- User visibility set to Getting started - demo | first install | level 1 Techniques
- Effort required set to Very Small
- Priority changed from 0 to 96
The idea would be to:
- only fail on the couple that is known to fail,
- warn when the version are different, pointing to the RedHat bug, and explaining what can be done if Rudder is broken because of it (update package version).
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Benoît PECCATTE to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-packages/pull/1346
- Status changed from Pending technical review to In progress
I'm taking over this issue!
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Nicolas CHARLES
- Pull Request changed from https://github.com/Normation/rudder-packages/pull/1346 to https://github.com/Normation/rudder-packages/pull/1348
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.1.20, 4.0.5 and 4.1.2 which were released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by