← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1433609] Re: Not adding a image block device mapping causes some valid boot requests to fail

 

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => liberty-1

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1433609

Title:
  Not adding a image block device mapping causes some valid boot
  requests to fail

Status in OpenStack Compute (Nova):
  Fix Released
Status in OpenStack Compute (nova) kilo series:
  Fix Released

Bug description:
  The following commit removed the code in the python nova client that
  would add an image block device mapping entry (source_type: image,
  destination_type: local) in preparation for fixing
  https://bugs.launchpad.net/nova/+bug/1377958.

  However this makes some valid instance boot requests not work as
  expected as they will not pass the block device mapping validation
  because of this. An example would be:

  nova boot test-vm --flavor m1.medium --image centos-vm-32 --nic net-
  id=c3f40e33-d535-4217-916b-1450b8cd3987 --block-device
  id=26b7b917-2794-452a-
  95e5-2efb2ca6e32d,bus=sata,source=volume,bootindex=1

  Which would be a valid boot request previously since the client would
  add a block device with boot_index=0 that would not fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1433609/+subscriptions


References