** Changed in: nova
Status: Fix Released => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642679
Title:
The OpenStack network_config.json implementation fails on Hyper-V
compute
Hello,
sorry for the delay, we have successfully tested a latest yakkety
image(we updated via chroot the cloud-init with the one from the
-proposed repo).
Thanks,
Adrian Vladu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
On a second run, also the
http://archive.ubuntu.com/ubuntu/dists/yakkety/main/uefi/grub2-amd64/2.02~beta2-36ubuntu11/grubnetx64.efi
is working on MAAS 2.0. I will come back with some more results as I
want to reproduce the scenario on a clean MAAS installation.
Thank you,
Adrian Vladu
--
You
yakkety builds on archive.ubuntu.com are not working. Can
someone take a look into it?
Thank you,
Adrian Vladu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519836
Title:
MaaS fails to boot Hyper-V
Hi Scott,
I redid the tests - the saucy vm booted and was provisioned successfully on
Hyper-V compute node.
I have used
http://cloud-images.ubuntu.com/saucy/20130909/saucy-server-cloudimg-amd64-disk1.img
.
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Hello,
I will test as soon as the image is up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1220918
Title:
networking does not come up in cloud image on hyper-v
To manage notifications about
I found the package here:
https://launchpad.net/ubuntu/+source/isc-dhcp/4.2.4-7ubuntu7 .
The source used:
https://launchpad.net/ubuntu/+archive/primary/+files/isc-dhcp_4.2.4.orig.tar.gz
After I have installed the package(configure/make/make install), on
reboot the vm has been successfully provi
Martin Pitt, you are right.
I ran:
sudo /etc/init.d/apparmor stop
sudo /etc/init.d/apparmor teardown
sudo update-rc.d -f apparmor remove
After reboot, the instance has been provisioned successfully(I have used http
source for openstack metadata).
--
You received this bug notification because y
