Bug ID 700250: qkviews for secondary blade appear to be corrupt

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 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

Fixed In:
14.0.0, 13.1.1.2

Opened: Dec 29, 2017
Severity: 3-Major
Related AskF5 Article:
K59327012

Symptoms

Normally, a qkview created on a multi-blade system will include a qkview for every blade on the system. Those qkview files have an error that makes the tar-ball appear corrupt.

Impact

The system posts the following messages: gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now Confuses troubleshooters into thinking that the blade qkview files are corrupt, which they are not.

Conditions

Running a qkview on a system with blades. Attempt to access the tar-ball using the following command: tar -tvzf 127.3.0.2.qkview | tail.

Workaround

None.

Fix Information

By not always writing an errant newline, the problem is solved.

Behavior Change