Image/alias detection fails after first successful creation of image in deployment

Bug #1499232 reported by James Page
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nova-compute-lxd (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Four node compute cluster; first nova boot works fine, however subsequent boots, which get scheduled to different hosts, fail - the driver is not creating the image and alias in LXD.

Looking at https://github.com/lxc/nova-compute-lxd/blob/master/nclxd/nova/virt/lxd/container_image.py

https://github.com/lxc/nova-compute-lxd/blob/master/nclxd/nova/virt/lxd/container_image.py#L168

On creation of an alias, the driver updates the properties lxd-image-alias and lxd-manifest in glance.

This seems odd - why would nova update image properties on a glance image?

This then causes subsequent calls to hit https://github.com/lxc/nova-compute-lxd/blob/master/nclxd/nova/virt/lxd/container_image.py#L54

which causes a silent return of the property 'lxd-image-alias' is found on the glance image, causing container creation to fail.

I suggested dropping the update of glance metadata - this seems wrong.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: nova-compute-lxd 0.17-0ubuntu3
ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0
Uname: Linux 4.2.0-10-generic x86_64
ApportVersion: 2.18.1-0ubuntu1
Architecture: amd64
Date: Thu Sep 24 08:41:16 2015
Ec2AMI: ami-0000059e
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.medium
Ec2Kernel: None
Ec2Ramdisk: None
PackageArchitecture: all
ProcEnviron:
 TERM=screen-256color-bce
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nova-compute-lxd
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
James Page (james-page) wrote :
Revision history for this message
Chuck Short (zulcss) wrote :

This has been fixed.

Changed in nova-compute-lxd (Ubuntu):
status: New → 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.