Unique name server and instance count

Bug #1085960 reported by Édouard Thuleau
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Opinion
Undecided
Unassigned
OpenStack Dashboard (Horizon)
Fix Released
Low
Unassigned

Bug Description

Horizon proposes to launch many instances in a mean time favor to the field 'Instance Count'.
But if the flag 'osapi_compute_unique_server_name_scope' is set to 'project' or 'global', Horizon will fail to launch more than one VM in a time.

description: updated
Revision history for this message
Gabriel Hurley (gabriel-hurley) wrote :

I'm tempted to fault Nova for this... if they have config flags that make part of the core "launch" API invalid then that's a problem on their end. Horizon is still sending a valid API request.

That said, Horizon *could* add a config flag for this, but all in all I'm not convinced.

Changed in horizon:
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Michael Still (mikal) wrote :

I don't think this is a nova bug, it functioning as configured -- enforcing name uniqueness in the specified scope.

Changed in nova:
status: New → Opinion
Revision history for this message
Brian Waldon (bcwaldon) wrote :
shake.chen (shake-chen)
Changed in horizon:
status: Triaged → 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.