Debugging random failure of atomic upgrade or rollback tests

[kushaldas]

The reboots after those tests are failing randomly. I can not find any clear reproducer yet.

[kushaldas]

Executing command: sudo python3 -m unittest tunirtests.atomictests.TestAtomicUpgradeRun -v
Executing command: @@ sudo reboot
No handlers could be found for logger "paramiko.transport"
Getting ssh exception, sleeping for 30 seconds and then trying again.

Means it is taking more time by when ssh is again working.

[kushaldas]

We are going to enable the following tests specially for atomic images. Means only upgrade/roll back is having trouble for now.

sudo python3 -m unittest tunirtests.atomictests.TestDockerInstalled -v
sudo python3 -m unittest tunirtests.atomictests.TestDockerStorageSetup -v
sudo python3 -m unittest tunirtests.atomictests.TestAtomicFirstBootRun -v
sudo python3 -m unittest tunirtests.atomictests.TestAtomicCommand -v

[nzwulfin]

What about implementing a POLL statement along the lines of the SLEEP statement in tunir? That would make handling continuing after reboots simpler.