Bug ID 700322: Upgrade may fail on a multi blade system when there are scheduled reports in configuration

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP Install/Upgrade(all modules)

Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4

Fixed In:
14.0.0, 13.1.1.5

Opened: Dec 31, 2017
Severity: 3-Major

Symptoms

Unable to upgrade to newer version or hotfix fail. Secondary slot always fails upgrade with the following error in var/log/liveinstall.log: error: status 256 returned by command: F5_INSTALL_SESSION_TYPE=install tmsh -f save sys ucs /var/tmp/fbSBcyXrsz.ucs info: >++++ result: info: Saving active configuration... info: Thrift: Tue Dec 19 10:53:45 2017 TSocket::open() connect() <Host: localhost Port: 9090>Connection refused info: Error during config save. info: Unexpected Error: UCS saving process failed.

Impact

Upgrade fails.

Conditions

1) System has two or more slots (multi-blade) 2) There are scheduled reports in configuration.

Workaround

1) Save configuration for scheduled reports aside. 2) Remove all scheduled reports from configuration. 3) Perform upgrade. 4) Add scheduled reports back to configuration.

Fix Information

On secondary blades monpd listens on slot-specific local address 127.0.3.X, so tmsh should use this address when it establishes connection to monpd (instead of 127.0.0.1)

Behavior Change