Open niklaushirt opened 7 years ago
Do you get the same error if you log into the horizon console (http://192.168.27.100 username: demo password: labstack) and try to launch a node from there? Which image are you trying to deploy?
Yep, unfortunately that's exactly what I'm doing. I launch one of the two Ubuntu Images 1404 or 1604 and get the same result. Same thing when using admin.
couple of questions:
vagrant box list
you should see something like this:
stackinabox/openstack (virtualbox, 0.9.7)
Mac OS Sierra 11.12.2 on all three machines I tried this on.
Boxes are as follows: stackina-base-box (virtualbox, 0) stackinabox/opdk (virtualbox, 0.9.3) stackinabox/opdk (virtualbox, 0.9.6) stackinabox/openstack (virtualbox, 0.9.7) ubuntu/trusty64 (virtualbox, 20160304.0.1) ubuntu/trusty64 (virtualbox, 20160314.0.1) ubuntu/xenial64 (virtualbox, 20161209.0.0)
Can you run the 14.04 image successfully?
Still not:
vagrant@openstack:~$ lxc launch ubuntu:16.04 my-ubuntu
gives me
Creating my-ubuntu
Retrieving image: 100%error: Failed to create ZFS filesystem: cannot mount '/var/lib/lxd/images': directory is not empty
But only the first time. The second time it works:
vagrant@openstack:~$ lxc launch ubuntu:16.04 my-ubuntu
Creating my-ubuntu
Starting my-ubuntu
I can download the image from glance without a problem:
vagrant@openstack:~$ glance image-download --file ubuntu1404.tar.xz b169e10a-9c66-449f-84d5-939a3d2666d6
vagrant@openstack:~$ ls
ubuntu1404.tar.xz
But the Instance creation in OpenStack still continuous to fail...
can you try running the ubuntu-14.04-amd64 image from the horizon console and let me know if that work for you or not.
Just FYI running 0.9.8 on Vagrant 1.9.1, VirtualBox-5.1-5.1.14_112924 on RHEL 7.2 (3.10.x kernel) this is fixed for me, I can launch both 14.04 and 16.04 fine.
@sudhakarau1 Thanks for figuring that out! I will update the Vagrantfile to require Vagrant 1.9.1 or higher.
@niklaushirt please upgrade your Vagrant and Virtualbox to 5.1.14 and let me know if it works on your mac.
@niklaushirt Can you verify that upgrading your Vagrant to 1.9.1 and your VirtualBox to 5.1.14 on Mac OS X resolves this issue for you? I'd like to close this one out if I can.
Nope, still got the same issue with Vagrant 1.9.1, VB 5.1.14 and stackinabox 0.99. Mystery, I'll have to play some more with my Macs configuration...
@niklaushirt damn, let's debug this together in Madrid
After discussing with @niklaushirt we have found a work-around for this issue. You must ensure that your environment is setup to use US English localization. I am working on determining why this is happening in @niklaushirt case because he was having the issue when running stackinabox under his native Swedish localization.
As of the Jan, 6th commit I am unable to start a VM in OpenStack (be it via UCDP or directly in the interface) (same in the latest Commit, Jan. 19th). The Error is:
Error: Failed to perform requested operation on instance "demo_fail", the instance has an error status: Please try again later [Error: Build of instance 979ab17a-3411-4ef4-bded-c1f5bd9bda1c aborted: Image is unacceptable: Bad Image format: Image could not be found.].
I tried various combinations of Vagrant (1.9.1 and 1.8.5)/VirtualBox (5.0.30 and 5.1.12) and Macs (RAM/CPU) config but to no avail and the images themselves in Openstack exist as far as I can tell.
Errors found in n-cpu.log: