Bug ID 746333: Setting the hostname to non-FQDN value prevents upgrade

Last Modified: May 01, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP Install/Upgrade, LTM(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.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4

Opened: Oct 09, 2018
Severity: 3-Major

Symptoms

Upgrade of the BIG-IP system fails.

Impact

Inability to upgrade. Note: Setting hostname in tmsh CLI does not validate FQDN like the GUI does, so when you use tmsh to set hostnames, make sure to use an FQDN-compliant one.

Conditions

BIG-IP systems that contain hostnames that do not meet FQDN standards. For instance, this could be due to the use of invalid characters, such as asterisk '*'. An example of an invalid hostname is as follows: test***.example.com.

Workaround

When attempting to upgrade you must make sure all hostnames are FQDN compliant.

Fix Information

None

Behavior Change