Deployment image not placed in /httpboot

Bug #1478970 reported by Ricardo Carrillo Cruz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bifrost
Fix Released
Undecided
Ricardo Carrillo Cruz

Bug Description

I'm getting the following error when running the deploy-dynamic top-level playbook:

<snip>

TASK: [bifrost-deploy-nodes-dynamic | Deploy to Hardware - Bifrost Default] ***
fatal: [ironic-bm-test3.ftclab.gozer.hpcloud.net -> localhost] => One or more undefined variables: 'dict object' has no attribute 'md5'
fatal: [ironic-bm-test2.ftclab.gozer.hpcloud.net -> localhost] => One or more undefined variables: 'dict object' has no attribute 'md5'
fatal: [ironic-bm-test.ftclab.gozer.hpcloud.net -> localhost] => One or more undefined variables: 'dict object' has no attribute 'md5'
fatal: [ironic-bm-test4.ftclab.gozer.hpcloud.net -> localhost] => One or more undefined variables: 'dict object' has no attribute 'md5'

FATAL: all hosts have already failed -- aborting

</snip>

Problem is that running the install.yaml top-level playbook used to place the deployment_image.qcow2 file on /httpboot, but now it's missing:

<snip>

ubuntu@ironic:/httpboot$ ls
boot.ipxe configdrive-30313436-3631-5355-4534-323059425830.iso.gz configdrive-30313436-3631-5355-4534-323059425832.iso.gz coreos_production_pxe.vmlinuz
configdrive-30313436-3631-5355-4534-323059425759.iso.gz configdrive-30313436-3631-5355-4534-323059425831.iso.gz coreos_production_pxe_image-oem.cpio.gz

< /snip>

The problem seems to me on the bifrost-create-dib-image, prior to commit a5cc0651 we used this:

deploy_image: "{{http_boot_folder}}/{{deploy_image_filename}}"

whereas post a5cc0651 commit we use 'dib_imagename', that has no default and thus it never gets http_boot_folder prepended.

Changed in bifrost:
assignee: nobody → Ricardo Carrillo Cruz (rcarrillocruz)
Changed in bifrost:
status: New → Fix Committed
Changed in bifrost:
milestone: none → 0.0.1
status: Fix Committed → 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.