Bug #6286
closed
When I want to upgrade Rudder to latest version, ncf is NOT updated on SLES11
Description
I want to upgrade Rudder to latest version on a SLES 11 SP 3
Executing (as in the documentation) zypper update rudder* tries to upgrade all rudder--* packages, but not ncf nor ncf-api-virtualenv
zypper info ncf shows that I have version 1398866025:0.201502051823-1.SLES11 available, and the status of my package is
out-of-date (version 139886025:0.201407211105-1.SLES.11)
I so end up with a broken install with an out of date ncf...
Updated by Nicolas CHARLES almost 10 years ago
- Assignee set to Matthieu CERDA
If I run afterwards zypper update ncf, it accepts to update the package ncf
However, it says:
The following package is not supported by its vendor: ncf 1398866025:0.201502051823-1.SLES.11
Updated by Matthieu CERDA almost 10 years ago
- Category set to Documentation
- Status changed from New to Discussion
- Assignee changed from Matthieu CERDA to Nicolas CHARLES
The problem in the doc about upgrades has been fixed in #6288.
The message about vendors is linked to SuSE vendor locking feature, and can be safely ignored ( http://linux.dell.com/repo/hardware/faq.html )
The version required by rudder-techniques, in 2.11.7, is 0.201501221640, which is is why pulling an upgrade from Rudder only will not trigger a ncf upgrade (zypper see an upgrade is available for ncf, but does not pull it as nothing asks it to (rudder-* does not match ncf, and no hard depdendency)).
If this is a problem, it means this dependency is no more up to date and needs an upgrade.
Updated by Nicolas CHARLES almost 10 years ago
- Assignee changed from Nicolas CHARLES to Matthieu CERDA
Matthieu CERDA wrote:
The problem in the doc about upgrades has been fixed in #6288.
The message about vendors is linked to SuSE vendor locking feature, and can be safely ignored ( http://linux.dell.com/repo/hardware/faq.html )
The version required by rudder-techniques, in 2.11.7, is 0.201501221640, which is is why pulling an upgrade from Rudder only will not trigger a ncf upgrade (zypper see an upgrade is available for ncf, but does not pull it as nothing asks it to (rudder-* does not match ncf, and no hard depdendency)).
I fail to understand this. If 0.201501221640 is required, but 0.201407211105 is installed, then the requierement is not met after an upgrade
If this is a problem, it means this dependency is no more up to date and needs an upgrade.
Updated by Florian Heigl almost 10 years ago
I can verify this as of last night :)
ncf update was not pulled in, had to do it manually afterwards. has a trail of issues hiding it since cf-serverd won't run due to promise issues when you have ncf bundles left but no ncf.
Updated by Nicolas CHARLES over 9 years ago
Florian, can you confirm that it used to pull automatically ncf when you upgraded Rudder?
Updated by Nicolas CHARLES over 9 years ago
- Project changed from Rudder to 34
- Category deleted (
Documentation)
Correcting the tracker, it's not a doc issue, it a packaging is broken issue
Updated by Matthieu CERDA over 9 years ago
- Status changed from Discussion to Pending technical review
- Assignee changed from Matthieu CERDA to Benoît PECCATTE
- % Done changed from 0 to 100
- Pull Request set to https://github.com/Normation/rudder-packages/pull/622
Updated by Matthieu CERDA over 9 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-packages|commit:669b9ab28767eb59b74b095b93fd899e93c6c7b3.
Updated by Benoît PECCATTE over 9 years ago
Applied in changeset rudder-packages|commit:51de974b92c6c51cfea29f9dfc7776a000126bfb.
Updated by Vincent MEMBRÉ over 9 years ago
- Subject changed from When I want to upgrade Rudder to latest version, ncf is NOT updated on SLES11 SP3 to When I want to upgrade Rudder to latest version, ncf is NOT updated on SLES11
Updated by Vincent MEMBRÉ over 9 years ago
- Status changed from Pending release to Released
Updated by Benoît PECCATTE over 9 years ago
- Project changed from 34 to Rudder
- Category set to Packaging