large_ops scenario: actual timeout may be larger than specified one

Bug #1250923 reported by Salvatore Orlando
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tempest
In Progress
Undecided
Sean Dague

Bug Description

     def _wait_for_server_status(self, status):
         for server in self.servers:
            self.status_timeout(
                self.compute_client.servers, server.id, status)

The chunk of code above iterates over servers and for each server checks whether it becomes active before the timeout expires.
With a default timeout of 196 seconds, this means that if the first server takes 10 seconds to boot, then the function will wait 196 more seconds for the second server, bringing the total timeout to 206, and so on.

Potential fix approaches:
- have status_timeout return the elapsed time and decrease the timeout for the next check
   CONS: Non-negligible refactoring
- do the check in parallel
   CONS: consistent number of threads spawn; status_timeout will query nova server every build_interval seconds for each thread.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tempest (master)

Fix proposed to branch: master
Review: https://review.openstack.org/56242

Changed in tempest:
assignee: nobody → Salvatore Orlando (salvatore-orlando)
status: New → In Progress
Changed in tempest:
assignee: Salvatore Orlando (salvatore-orlando) → Sean Dague (sdague)
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.