Jump to content


Photo

7.1.4 Update - Fails on F10


  • Please log in to reply
6 replies to this topic

#1 Chad Hicks

Chad Hicks
  • Members
  • 48 posts

Posted 02 October 2018 - 07:27 AM

Is anyone else having issues installing the 7.1.4 update on F10's?  I deployed the update via our CC to three, and all three updates failed.



#2 Gavin Chappell

Gavin Chappell
  • Moderators
  • 383 posts
  • LocationNottingham, UK

Posted 02 October 2018 - 08:55 AM

The firmware updates sometimes require more space than is usually available on the F10/F100 models. The Campus release notes have some tips on how you may be able to free up more space temporarily for the installation of the upgrade

 

https://campus.barra...migration-notes(section "Disk Space Requirements")



#3 Chad Hicks

Chad Hicks
  • Members
  • 48 posts

Posted 03 October 2018 - 07:46 AM

The firmware updates sometimes require more space than is usually available on the F10/F100 models. The Campus release notes have some tips on how you may be able to free up more space temporarily for the installation of the upgrade

 

https://campus.barra...migration-notes(section "Disk Space Requirements")

Followed instructions on the link provided, and the update took; however, now the boxes are generating Event ID 4410 Release Inconsistencies Detected, RPM Verification Failure.  How is this resolved?  



#4 Gavin Chappell

Gavin Chappell
  • Moderators
  • 383 posts
  • LocationNottingham, UK

Posted 03 October 2018 - 07:52 AM

Sounds like something you should open a support case for.

 

However, if you have access to the firewalls directly, then on the Control->Licenses page you can double click the red error message (I think the wording is "dirty_release_confirmed") and it should tell you which RPM package it thinks has failed the verification.



#5 Chad Hicks

Chad Hicks
  • Members
  • 48 posts

Posted 03 October 2018 - 10:41 AM

Sounds like something you should open a support case for.

 

However, if you have access to the firewalls directly, then on the Control->Licenses page you can double click the red error message (I think the wording is "dirty_release_confirmed") and it should tell you which RPM package it thinks has failed the verification.

Created support case, and only answer they could provide was "Upgrade to 7.2.2" .



#6 Micha Knorpp

Micha Knorpp
  • Members
  • 173 posts
  • LocationGermany, BW

Posted 11 October 2018 - 05:08 AM

Best way to solve this is to delete and rebuild the RPM DBs.

Go to the CLI and do the following:

 

cd /var/lib/rpm
rm __db.*
db_verify /var/lib/rpm/Packages
rpm --rebuilddb


that should fix it. Afterwards apply the update again.


 


regards,
-micha-

#7 Chad Hicks

Chad Hicks
  • Members
  • 48 posts

Posted 11 October 2018 - 08:58 AM

Best way to solve this is to delete and rebuild the RPM DBs.

Go to the CLI and do the following:

 

cd /var/lib/rpm
rm __db.*
db_verify /var/lib/rpm/Packages
rpm --rebuilddb


that should fix it. Afterwards apply the update again.


 

I will give this a shot, then post an update.