Project

General

Profile

Bug #10734

Installation fails due to broken nss/nss-softokn detection on CentOS6

Added by Alexis MOUSSET about 2 years ago. Updated about 2 years ago.

Status:
Released
Priority:
N/A
Category:
Packaging
Target version:
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
Priority:
96

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 issues

Related to Rudder - Bug #9905: java.lang.InternalError when calling the internal API on Redhat because of invalid version of nssReleasedActions

Associated revisions

Revision ffe660d9 (diff)
Added by Benoît PECCATTE about 2 years ago

Fixes #10734: Installation fails due to broken nss/nss-softokn detection on CentOS6

History

#1

Updated by Alexis MOUSSET about 2 years ago

  • Related to Bug #9905: java.lang.InternalError when calling the internal API on Redhat because of invalid version of nss added
#2

Updated by Alexis MOUSSET about 2 years ago

  • Target version set to 3.1.20
#3

Updated by François ARMAND about 2 years ago

  • 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).

#4

Updated by Benoît PECCATTE about 2 years ago

  • Status changed from New to In progress
#5

Updated by Benoît PECCATTE about 2 years ago

  • 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
#6

Updated by Alexis MOUSSET about 2 years ago

  • Status changed from Pending technical review to In progress

I'm taking over this issue!

#7

Updated by Alexis MOUSSET about 2 years ago

  • 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
#8

Updated by Benoît PECCATTE about 2 years ago

  • Status changed from Pending technical review to Pending release
#9

Updated by Vincent MEMBRÉ about 2 years ago

  • 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