Files
a67807b9b6017a8a1dc250bd7a7141e6728544cb
ironic-python-agent /zuul.d
Julia Kreger a67807b9b6 Mark standalone job non-voting/remove from gate 
The standalone job at present has a high chance of failure
due to two separate things occuring:
1) The deployed nodes from raid tests can be left in a dirty state
 as the raid configuration remains and is chosen as the root
 device for the next deployment. IF this is chosen by any job,
 such as rescue or a deployment test that attempts to login,
 then the job fails with unable to ssh. The fix for this is
 in the ironic-tempest-plugin but we need to get other fixes
 into stablilize the gate first.
 https://review.opendev.org/#/c/757141/
2) Long running scenarios run in cleaning such as deployment with
 RAID in the standalone suite can encounter conditions where
 the conductor tries to send the next command along before the
 present configuration command has completed. An example is
 downloading the image is still running, while a heartbeat
 has occured in the background and the conductor then seeks
 to perform a second action. This then causes the entire
 deployment to fail, even though it was transitory.
 This should be a relatively easy fix.
 https://review.opendev.org/759906
Also disabling ipa-tempest-bios-ipmi-direct-src and
ipa-tempest-bios-ipmi-iscsi-src for the time being, will revert
in https://review.opendev.org/757812
Change-Id: I08c8c258587dd3786dfa92e7879a80c80971d7df
2020年10月27日 21:28:08 +01:00
..