Boot from Volume invalid BDM

Bug #1671921 reported by Logan V
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Opinion
Undecided
Unassigned

Bug Description

Booting from volume in the new launch panel causes the following BDM:
{"server": {"name": "test", "imageRef": "", "availability_zone
  ": "us-dfw-1", "key_name": "test", "flavorRef": "9340639a-2883-48ca-811f-01519e527648", "block_device_mapping": [{"volume_id": "94426a92-5409-428d-8a26-81f94395d9ad", "delete_on_termination": "false", "device_name": "sda"}], "OS-DCF:diskConfig": "AUTO", "max_count": 1, "min_count": 1, "networks": [{"uuid
  ": "82ac236e-384a-420b-aa2c-3003f44cf782"}], "security_groups": [{"name": "4df780bf-b2c5-4c0e-acba-64b9b2f08eaa"}]}}

Nova rejects it with:
{"badRequest": {"message": "Block Device Mapping is Invalid: Boot sequence for the instance and image/block device mapping combin
  ation is not valid.", "code": 400}}}

It seems like it is missing a boot_index?

Revision history for this message
Liyingjun (liyingjun) wrote :

Can't reproduce with the latest master

Changed in horizon:
status: New → Opinion
Revision history for this message
Logan V (loganv) wrote :

Sorry I forgot to state, I am seeing this on Newton.

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.