Bug #10867
closedOpenstack boot from volume always enabled, even if unchecked
Description
We've just upgraded our Foreman installation to 1.8.2 and found that our Openstack provisioning stopped working. We've narrowed the issue down to the new Openstack boot from volume code (see http://projects.theforeman.org/issues/4521).
It seems that even if the "Boot from volume" button is unchecked, Foreman still fires the boot_from_volume function in /usr/share/foreman/app/models/compute_resources/foreman/model/openstack.rb. In our infrastructure this broke our provisioning as we don't use Ceph/block device volumes on Openstack.
On line 76 of openstack.rb:
def create_vm(args = {})
boot_from_volume(args) if args[:boot_from_volume]
....
When I create a new Openstack VM, boot_from_volume always gets called, even though I can see '"boot_from_volume"=>"false"' in the Foreman logs for the new host.
Updated by Andy Taylor over 9 years ago
Correction, I didn't mean Ceph, I meant Cinder :)
Updated by Marek Hulán over 9 years ago
- Translation missing: en.field_release set to 62
Updated by Marek Hulán over 9 years ago
- Related to Bug #4521: Openstack boot from volume added
Updated by Daniel Lobato Garcia over 9 years ago
Looks like ` args[:boot_from_volume] ` is going to return true (boolean) for either "true" or "false" strings.
Updated by Dominic Cleal over 9 years ago
Don't forget that we have Foreman::Cast.to_bool now in develop.
Updated by The Foreman Bot over 9 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/2498 added
- Pull request deleted (
)
Updated by Daniel Lobato Garcia over 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 776cff93637b006cb69063fecf142e776acd1378.