Non working hard reboot test listed in spec 2016.01.required

Bug #1584019 reported by Ross Martyn
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
defcore
Fix Released
Medium
Chris Hoge

Bug Description

tempest.api.compute.servers.test_server_actions.ServerActionsTestJSON.test_reboot_server_hard

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://bugs.launchpad.net/tempest/+bug/1583987

Essentially, this test is seemingly invalid.

Appreciate any feedback, this may not be the correct forum and I could be mistaken?

Revision history for this message
Chris Hoge (hoge) wrote :

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.

Changed in defcore:
assignee: nobody → Chris Hoge (hoge)
importance: Undecided → Medium
Revision history for this message
Ross Martyn (rossmartyn04) wrote :

Hi Chris,

Much appreciated. I agree that the functionality test is valid, its just that the underlying mechanism for checking that the reboot has worked is flawed. This could be fixed fairly easily by sending a 'sync' to the operating system or performing a soft reboot first!

I was not sure of the approach here, whether to ask for test to be flagged until the tempest/refstack guys had fixed it (given there are bug reports there too), or to use this forum to help move the fix along!

As you can appreciate in the meantime I have a DefCore compliant cloud that is failing one test, hindering our ability to join the marketplace!

Appreciate you bringing it up with the team!

Kindest Regards,

Ross

Revision history for this message
Chris Hoge (hoge) wrote :

Fix committed and released, https://review.openstack.org/#/c/340723

Changed in defcore:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.