Non working hard reboot test listed in spec 2016.01.required
Bug #1584019 reported by
Ross Martyn
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
defcore |
Fix Released
|
Medium
|
Chris Hoge |
Bug Description
tempest.
This test listed in the 2016.01 spec is bound by guest operating system/filesystem configuration, rather than testing OpenStack API and reboot functionality.
This is because the system is hard rebooted before most operating systems would have committed the public keys to disk (provided by cloud-init). (Password auth is not available in tempest at this time)
Please take a look at the following bug report and responses.
https:/
Essentially, this test is seemingly invalid.
Appreciate any feedback, this may not be the correct forum and I could be mistaken?
To post a comment you must log in.
Looking at the bug, I'm not sure if it qualifies for a flag. It seems that if we can generate a positive result set, even with the extended time to run the tests, we don't want to throw out the capability. Reboot seems like a fairly basic capability, and we should be fixing the underlying test and working around the limitations rather than throwing it out. If there wasn't a workaround, I'd be more inclined to flag.
That said, I'll add this as an agenda item to our next DefCore meeting to take a temperature of the consensus.