[upgrade] Periodically untar of upgrade script fails with 'tar: This does not look like a tar archive'

[Andrey Sledzinskiy]

Reproduced on fuel-6.1-upgrade-352-2015-04-26_22-54-38.tar.lrz

Steps:
1. Install 6.0-58 fuel
2. Upload 6.1 upgrade script to master
3. Run command:
lrzuntar fuel-6.1-upgrade-352-2015-04-26_22-54-38.tar.lrz

Actual result - it failed periodically with
Decompressing...
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors

It is reproduced in many tests on CI last time.

We need to decide how to solve it - add retry in tests to untar it twice or fix problem in tarball if there is some.

[Dmitry Pyzhov (dpyzhov)]

Looks like root cause here is issue with copying of tarball. It is not about creation of broken tarball or incorrect unpack procedure. Moving this bug back to QA team

[Nastya Urlapova (aurlapova)]

As I know Igor also had this issue on local environment.

[Ihor Kalnytskyi (ikalnytskyi)]

Well, I got this issue two. When I remove this tarball from master node and re-upload it again (with 'sync' command)

    lrzuntar fuel-6.1-upgrade-352-2015-04-26_22-54-38.tar.lrz; sync

the tarball was extracted correctly. That basically means that the tarball is ok and there're some issues with syncing buffers on fs or something like that (please note, i don't redownload the tarball. just re-scp to my master node vm).

[Ihor Kalnytskyi (ikalnytskyi)]

Sorry, I just paste wrong command. I perform `scp` with sync, not `lrzuntar`.

    scp fuel-6.1-upgrade-352-2015-04-26_22-54-38.tar.lrz root@masternode:/var/tmp; sync

[Artem Panchenko (apanchenko-8)]

Got the same issue on swarm for 7.0 MU1:

2015-11-08 14:26:33,700 - DEBUG helpers.py:328 -- Executing command: 'cd /var && lrzuntar MirantisOpenStack-7.0-upgrade.tar.lrz'
...
2015-11-08 14:27:12,015 - DEBUG helpers.py:328 -- Executing command: 'chmod 755 /var/upgrade.sh'
2015-11-08 14:27:12,073 - DEBUG checkers.py:276 -- Result of cmod is {'exit_code': 1, 'stderr': ["chmod: cannot access `/var/upgrade.sh': No such file or directory\n"], 'stdout': []}

Test failed because upgrade tarball wasn't copied to master node properly. But some time after the test failed I was able to unpack the archive manually, so most probably this bug is about how we upload upgrade tarball. The issue needs further investigation.

[Artem Panchenko (apanchenko-8)]

Moving to 'invalid' for 8.0 because Fuel upgrade using tarball was deprecated and is not supported anymore.

[Alexey Stupnikov (astupnikov)]

We no longer support MOS5.1, MOS6.0, MOS6.1
We deliver only Critical/Security fixes to MOS7.0, MOS8.0.
We deliver only High/Critical/Security fixes to MOS9.2.