Skip to main content
Ask Question
Asked a question 4 months ago

Upgrading packages to Bright 8.2 from 8.1 fails using cm-upgrade -i all -f, /var/log/cmdaemon is being peppered with: Mar 20 20:37:00 ourclustercmd: [ CMD ] Info: [EthernetSwitch::getRawValue] switch01, error: Timeout after 500000 μs and 1 retries and /var/log/cm-upgrade.log ends with (2020-03-20 20:31:42,566) Upgrading packages to Bright 8.2. Also notice the logs duplicate not sure if that's a clue or red herring: (2020-03-20 21:08:25,941) Package python2-boto3 not installed, nothing to remove (2020-03-20 21:08:25,941) Package python2-boto3 not installed, nothing to remove (2020-03-20 21:08:26,742) Package python-cffi not installed, nothing to remove (2020-03-20 21:08:26,742) Package python-cffi not installed, nothing to remove (2020-03-20 21:08:27,244) Setting up upgrade (2020-03-20 21:08:27,244) Setting up upgrade (2020-03-20 21:08:28,130) Upgrading packages to Bright 8.2 (2020-03-20 21:08:28,130) Upgrading packages to Bright 8.2 (END)

Where am I?

In Bright Computing, Inc. you can ask and answer questions and share your experience with others!

Hi rkudyba

As you have a support request open for this, we will work on the issue there.
However, for the benefit of the community, you may check the cm-upgrade.log file to determine the reason the upgrade failed.

On the headnode (if upgrading the headnode):
/var/log/cm-upgrade.log

Inside a software image on the headnode (if upgrading a software image):
/cm/image/<your-image>/var/log/cm-upgrade.log