Project

General

Profile

Actions

Bug #5820

closed

Rudder 2.11.4 release ncf packages are not signed

Added by Nicolas CHARLES over 9 years ago. Updated about 9 years ago.

Status:
Rejected
Priority:
1
Assignee:
Matthieu CERDA
Category:
Packaging
Target version:
-
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

after an upgrade of Rudder, the package list is as follow:


    Installed Packages
    rudder-agent.x86_64                                 1398866025:2.11.4.release-1.EL.6                     @Rudder_2.11
    rudder-inventory-endpoint.noarch                    1398866025:2.11.4.release-1.EL.6                     @Rudder_2.11
    rudder-inventory-ldap.x86_64                        1398866025:2.11.4.release-1.EL.6                     @Rudder_2.11
    rudder-jetty.noarch                                 1398866025:2.11.4.release-1.EL.6                     @Rudder_2.11
    rudder-reports.noarch                               1398866025:2.11.4.release-1.EL.6                     @Rudder_2.11
    rudder-server-root.noarch                           1398866025:2.11.4.release-1.EL.6                     @Rudder_2.11
    rudder-techniques.noarch                            1398866025:2.11.4.release-1.EL.6                     @Rudder_2.11
    rudder-webapp.noarch                                1398866025:2.11.4.release-1.EL.6                     @Rudder_2.11
    ncf.noarch                                          1398866025:0.201403281937-1.EL.6                     @Rudder_2.10

running yum update ncf fails as No Packages marked for Update

Interestingly, there is no Rudder_2.10 repo defined, and it does not recognise ncf-0.201411131129-1.EL.6 as being younger

Having a not up do date ncf prevent file generation (it does not find the file ncf_list_update)


Related issues 1 (0 open1 closed)

Related to Rudder - Architecture #4563: Clean up RPM packages: reset Epoch to 0 by defaultReleasedJonathan CLARKE2014-03-05Actions
Actions #1

Updated by Nicolas CHARLES over 9 years ago

  • Project changed from Rudder to 34
Actions #2

Updated by Nicolas CHARLES over 9 years ago

I believe this is linked to http://www.rudder-project.org/redmine/issues/4563
There was epoch, there isn't any more, and package manager don't understand package is newer

Actions #3

Updated by Nicolas CHARLES over 9 years ago

  • Subject changed from On Centos 6.5 (and maybe other OS), upgrading Rudder doesn't upgrade ncf to a current version to On Centos and SLES (and maybe other OS), upgrading Rudder doesn't upgrade ncf to a current version
Actions #4

Updated by Nicolas CHARLES over 9 years ago

Another information:
Package ncf-0.201411131129-1.EL.6.noarch.rpm is not signed

That may explain why it does not upgrade automatically

Actions #5

Updated by Nicolas CHARLES over 9 years ago

  • Subject changed from On Centos and SLES (and maybe other OS), upgrading Rudder doesn't upgrade ncf to a current version to ncf packages are not signed, so when upgrading Rudder it doesn't upgrade ncf to a current version

running yum install --nogpgcheck rudder-server-root does install the package, so this is really a signature version

Actions #6

Updated by Nicolas CHARLES over 9 years ago

ho, i meant: a signature issue

Actions #7

Updated by Matthieu CERDA over 9 years ago

  • Status changed from New to Rejected
  • Target version deleted (2.10.8)

This was an issue with the 2.11.4 release only (on RPM packages for RHEL6 and SLES11), due to another ncf package having been added to the release to fix a minor issue that indeed weren't signed. It has been fixed, all should be OK now :)

Actions #8

Updated by Matthieu CERDA over 9 years ago

  • Subject changed from ncf packages are not signed, so when upgrading Rudder it doesn't upgrade ncf to a current version to Rudder 2.11.4 release ncf packages are not signed
Actions #9

Updated by Benoît PECCATTE about 9 years ago

  • Project changed from 34 to Rudder
  • Category set to Packaging
Actions

Also available in: Atom PDF