What is the most recent good commit in nova-docker.git for RDO Juno on CentOS 7 ?
I just tested the top one :-
yum install docker-io -y
yum install -y python-pip git
git clone https://github.com/stackforge/nova-docker.git
cd nova-docker/
git checkout 07a57f78aa4b01c2acfb84b0e9e723dabfd650cb
python setup.py install
systemctl start docker
systemctl enable docker
chmod 660 /var/run/docker.sock
mkdir /etc/nova/rootwrap.d
Afterwards I was able reproduce http://cloudssky.com/en/blog/Nova-Doc...
until the point
nova boot --image busybox --flavor m1.tiny --key-name osxkey busybox
Instance spawning for a while and gets ERROR status.
git checkout -b pre-i18n 9045ca43b645e72751099491bf5f4f9e4bddbb91
works fine.
Following https://ask.openstack.org/en/question... fresh Juno branch tested on CentOS 7 Juno VM ( just installed )
# git clone https://github.com/fikovnik/nova-docker.git
# cd nova-docker
# $ git branch -v -a
* master 1ed1820 A note no firewall drivers.
remotes/origin/HEAD -> origin/master
remotes/origin/juno 1a08ea5 Fix the problem when an image is not located in the local docker image registry.
remotes/origin/master 1ed1820 A note no firewall drivers.
# git checkout -b juno origin/juno
# python setup.py install
# systemctl start docker
# systemctl enable docker
# chmod 660 /var/run/docker.sock
# mkdir /etc/nova/rootwrap.d
Glance works, busybox container stay in SPAWN for a while and goes to ERROR state.
Debugging info :-
+--------------------------------------+----------+--------+------------+-------------+------------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+----------+--------+------------+-------------+------------------------+
| ad359e93-3493-480e-a52d-89a4a1a3bf8a | busybox2 | ERROR | - | NOSTATE | demo_network=70.0.0.14 |
+--------------------------------------+----------+--------+------------+-------------+------------------------+
nova-compute.log
2014-12-18 07:35:11.482 17633 DEBUG nova.compute.manager [-] [instance: ad359e93-3493-480e-a52d-89a4a1a3bf8a] Build of instance ad359e93-3493-480e-a52d-89a4a1a3bf8a was re-scheduled: Cannot setup network: Cannot find any PID under container "31d9b2dced43413e4360a4b042c7bf74eaddb839b8f12657d535cfee90ef96e7" _do_build_and_run_instance /usr/lib/python2.7/site-packages/nova/compute/manager.py:2032
nova-conductor.log
2014-12-18 07:35:12.033 4585 ERROR nova.scheduler.utils [req-878f0472-7b95-4b4b-b205-ea0edd54eab8 None] [instance: ad359e93-3493-480e-a52d-89a4a1a3bf8a] Error from last host: ip-192-169-142-45.ip.secureserver.net (node ip-192-169-142-45.ip.secureserver.net): [u'Traceback (most recent call last):\n', u' File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2030, in _do_build_and_run_instance\n filter_properties)\n', u' File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2161, in _build_and_run_instance\n instance_uuid=instance.uuid, reason=six.text_type(e))\n', u'RescheduledException: Build of instance ad359e93-3493-480e-a52d-89a4a1a3bf8a was re-scheduled: Cannot setup network: Cannot find any PID under container "31d9b2dced43413e4360a4b042c7bf74eaddb839b8f12657d535cfee90ef96e7"\n']
2014-12-18 07:35:12.753 4585 WARNING nova.scheduler.driver [req-878f0472-7b95-4b4b-b205-ea0edd54eab8 None] [instance: ad359e93-3493-480e-a52d-89a4a1a3bf8a] NoValidHost exception with message: 'No valid host was found.'
2014-12-18 07:35:12.753 4585 WARNING nova.scheduler.driver [req-878f0472-7b95-4b4b-b205-ea0edd54eab8 None] [instance: ad359e93-3493-480e-a52d-89a4a1a3bf8a] Setting instance to ERROR state.