Guest

Preview Tool

Cisco Bug: CSCvh83268 - Uploading rpm via upgrade link page fails with `md5 NOT OK (MISSING KEYS: (MD5) PGP`

Last Modified

Aug 19, 2019

Products (1)

  • Cisco Tetration Analytics

Known Affected Releases

2.1(1.31) 2.2(1.34)

Description (partial)

Symptom:
Not able to upgrade tetration cluster to 2.2.1.34 due to issue with signed rpm's and the corresponding keys on the orchestrator.

Example Error:

    2018-02-01 20:24:03 INFO Found new rpm file /local/rpms/tetration_os_base_rpm_k9-2.2.1.34-1.el7.x86_64.rpm

    2018-02-01 20:24:03 INFO Validating filename for tetration_os_base_rpm_k9-2.2.1.34-1.el7.x86_64.rpm
    2018-02-01 20:24:03 INFO Verifying RPM /local/rpms/tetration_os_base_rpm_k9-2.2.1.34-1.el7.x86_64.rpm
    2018-02-01 20:24:03 INFO For cmd: ['rpm --dbpath /local/rpms/rpmdb --import /local/upgrade/.pgp/pgp.key'], rc: 0
     stderr: 
     stdout: 
    2018-02-01 20:24:22 INFO For cmd: ['rpm -K /local/rpms/tetration_os_base_rpm_k9-2.2.1.34-1.el7.x86_64.rpm --dbpath /local/rpms/rpmdb'], rc: 1
     stderr: 
     stdout: /local/rpms/tetration_os_base_rpm_k9-2.2.1.34-1.el7.x86_64.rpm: RSA sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#cf9848be) 

    2018-02-01 20:24:22 ERROR Verification failed for /local/rpms/tetration_os_base_rpm_k9-2.2.1.34-1.el7.x86_64.rpm For cmds: ['rpm -K /local/rpms/tetration_os_base_rpm_k9-2.2.1.34-1.el7.x86_64.rpm --dbpath /local/rpms/rpmdb'], rc: 1
     stderr:  stdout: /local/rpms/tetration_os_base_rpm_k9-2.2.1.34-1.el7.x86_64.rpm: RSA sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#cf9848be) 

     
    Traceback (most recent call last):
      File "service/RpmUpgrade.py", line 223, in verify_rpm
        self.run_cmd(cmds=[gpg_ok])
      File "service/RpmUpgrade.py", line 139, in run_cmd
        raise ValueError('For cmds: {0}, rc: {1}\n stderr: {2} stdout: {3}\n '.format(cmds, rc, err, out))
    ValueError: For cmds: ['rpm -K /local/rpms/tetration_os_base_rpm_k9-2.2.1.34-1.el7.x86_64.rpm --dbpath /local/rpms/rpmdb'], rc: 1
     stderr:  stdout: /local/rpms/tetration_os_base_rpm_k9-2.2.1.34-1.el7.x86_64.rpm: RSA sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#cf9848be) 

     
    2018-02-01 20:24:22 INFO Deleting /local/rpms/tetration_os_base_rpm_k9-2.2.1.34-1.el7.x86_64.rpm as it failed verification
    2018-02-01 20:24:22 INFO Deleting files matching /local/rpms/tetration_os_base_rpm_k9-2.2.1.34-1.el7.x86_64.rpm
    2018-02-01 20:24:22 INFO Deleting /local/rpms/tetration_os_base_rpm_k9-2.2.1.34-1.el7.x86_64.rpm
    2018-02-01 20:24:23 ERROR Upgrade for /local/rpms/tetration_os_base_rpm_k9-2.2.1.34-1.el7.x86_64.rpm
     failed. Exception: For cmds: ['rpm -K /local/rpms/tetration_os_base_rpm_k9-2.2.1.34-1.el7.x86_64.rpm --dbpath /local/rpms/rpmdb'], rc: 1
     stderr:  stdout: /local/rpms/tetration_os_base_rpm_k9-2.2.1.34-1.el7.x86_64.rpm: RSA sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#cf9848be) 

     
    Traceback (most recent call last):
      File "service/RpmUpgrade.py", line 353, in check_upgrade_new_rpms
        self.verify_rpm(rpm_path=rpm_file)
      File "service/RpmUpgrade.py", line 223, in verify_rpm
        self.run_cmd(cmds=[gpg_ok])
      File "service/RpmUpgrade.py", line 139, in run_cmd
        raise ValueError('For cmds: {0}, rc: {1}\n stderr: {2} stdout: {3}\n '.format(cmds, rc, err, out))
    ValueError: For cmds: ['rpm -K /local/rpms/tetration_os_base_rpm_k9-2.2.1.34-1.el7.x86_64.rpm --dbpath /local/rpms/rpmdb'], rc: 1
     stderr:  stdout: /local/rpms/tetration_os_base_rpm_k9-2.2.1.34-1.el7.x86_64.rpm: RSA sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#cf9848be) 

     
    2018-02-01 20:24:23 ERROR Upgrade Failed
    FAILED

Conditions:
Upgrading to 2.2.1.34 and 
the failure is for tetration_os_base_rpm_k9-2.2.1.34-1.el7.x86_64.rpm
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.