openstack-ansible / openstack-ansible

Ansible playbooks for installing OpenStack

OpenStack on Ansible with Vagrant (unofficial)

Note: this isn't the official OpenStack-Ansible project

You almost certainly want openstack/openstack-ansible instead, which is the official OpenStack-Ansible project.

Overview

This repository contains script that will deploy OpenStack into Vagrant virtual machines. These scripts are based on the Official OpenStack Docmentation, havana release, except where otherwise noted.

See also [Vagrant, Ansible and OpenStack on your laptop] (http://www.slideshare.net/lorinh/vagrant-ansible-and-openstack-on-your-laptop) on SlideShare, though this refers to a much older version of this repo and so is now out of date.

Install prereqs

You'll need to install:

• Vagrant
• Ansible
• python-netaddr
• python-novaclient (recommended)

To install Ansible and the other required Python modules:

pip install ansible netaddr python-novaclient

(Optional) Speed up your provisioning

Install Vagrant-cachier plugin:

vagrant plugin install vagrant-cachier

It allow to share a local directory containing packages (Apt, Npm, …) cache among VMs.

Get an Ubuntu 12.04 (precise) Vagrant box

Download a 64-bit Ubuntu Vagrant box:

vagrant box add precise64 http://files.vagrantup.com/precise64.box

Grab this repository

This repository uses a submodule that contains some custom Ansible modules for OpenStack, so there's an extra command required after cloning the repo:

git clone http://github.com/openstack-ansible/openstack-ansible.git
cd openstack-ansible
git submodule update --init

Bring up the cloud

make

This will boot three VMs (controller, network, storage, and a compute node), install OpenStack, and attempt to boot a test VM inside of OpenStack.

If everything works, you should be able to ssh to the instance from any of your vagrant hosts:

• username: cirros
• password: cubswin:)

Note: You may get a "connection refused" when attempting to ssh to the instance. It can take several minutes for the ssh server to respond to requests, even though the cirros instance has booted and is pingable.

Vagrant hosts

The hosts for the standard configuration are:

• 10.1.0.2 (our cloud controller)
• 10.1.0.3 (compute node #1)
• 10.1.0.4 (the quantum network host)
• 10.1.0.5 (the swift storage host)

You should be able to ssh to these VMs (username: vagrant, password: vagrant). You can also authenticate with the vagrant private key, which is included here as the file vagrant_private_key (NOTE: git does not manage file permissions, these must be set to using "chmod 0600 vagrant_private_key" or ssh and ansible will fail with an error).

Interacting with your cloud

You can interact with your cloud directly from your desktop, assuming that you have the python-novaclient installed.

Note that the openrc file will be created on the controller by default.

openstack-ansible's Issues

Failing when setting up the hosts

Error:

TASK [lxc_hosts : Unpack base image] ***************************************************************************************************
fatal: [infra1]: FAILED! => {"changed": false, "msg": "Source '/tmp/ubuntu-base-18.04.3-base-amd64.tar.gz' does not exist"}

To produce this error:

1. Run command openstack-ansible setup-hosts.yml located at openstack-ansible/playbooks

Openstack all in one

I tried to boot openstack all-in-one using the demo playbook, but I realized that is all pointing to vargrants hosts, and thats not what I need.

Theres some way to use this to deploy to one machine?

thanks!

Upgrade novaclient (2.23.0 is currently the latest)

Any interest in package caching with apt-cache-ng?

I could add that in, perhaps run it on the controller?

nova-client

Hi,

I used make to build the vms (the host machine is ubuntu 12.04 x64), but got:
TASK: [capture public key in variable] ****************************************
changed: [controller]

TASK: [add ssh keypair to nova] ***********************************************
fatal: [controller] => failed to parse: Traceback (most recent call last):
File "/home/vagrant/.ansible/tmp/ansible-tmp-1392070238.31-247682162134304/nova_keypair", line 1178, in
main()
File "/home/vagrant/.ansible/tmp/ansible-tmp-1392070238.31-247682162134304/nova_keypair", line 103, in main
nova = nova_client.Client(module.params['login_username'],
NameError: global name 'nova_client' is not defined

I installed python-novaclient on the host, but the same error. Guess I missed something obvious somewhere?

Thanks,

Cloud not ping the VM created by openstack

After successfully install the openstack with latest code , I am able to ping&ssh the buildin cirros vm . but when I create new vm with same image , I could not even ping it . the floating Ip is assigned when I boot the instance. (using demo user)

Here is the net list
vagrant@controller:~$ neutron net-list
+--------------------------------------+----------+----------------------------- ------------------------+
| id | name | subnets |
+--------------------------------------+----------+----------------------------- ------------------------+
| 1ce51229-9eca-4d62-b38b-025f77743d46 | demo-net | b047fa42-5140-4279-b78a-f7a6 1c71d95f 192.168.0.0/24 |
| 4c7dba23-eab5-4434-967a-108527218e95 | public | 51cdc207-eb59-41a0-b7c7-ff1e 44741c24 10.4.0.0/16 |
+--------------------------------------+----------+----------------------------- ------------------------+

create vm with following command

nova boot --flavor m1.tiny --image ca6f49e4-ed84-4be3-b74d-db80d1614c9b --key-name default --security-groups default --nic net-id=4c7dba23-eab5-4434-967a-108527218e95 test1

nova list
+--------------------------------------+--------+--------+------------+-------------+-----------------------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+--------+--------+------------+-------------+-----------------------------------+
| bd096df2-4a13-4efc-bbf3-9bd422264156 | cirros | ACTIVE | None | Running | demo-net=192.168.0.3, 10.4.10.101 |
| bed12078-dc83-452f-99b7-b926b4335667 | test1 | ACTIVE | None | Running | public=10.4.10.106 |
+--------------------------------------+--------+--------+------------+-------------+-----------------------------------+

vagrant@controller:~/coreos$ ping 10.4.10.101
PING 10.4.10.101 (10.4.10.101) 56(84) bytes of data.
64 bytes from 10.4.10.101: icmp_req=1 ttl=63 time=2.94 ms

vagrant@controller:~/coreos$ ping 10.4.10.106
PING 10.4.10.106 (10.4.10.106) 56(84) bytes of data.
From 10.4.0.2 icmp_seq=1 Destination Host Unreachable

I compare the two vm , the difference is the cirros is under demo-net and the one I created is under public , but cirros also has public ip ,not sure how it create ? Also default security group allow ping and ssh , which let me able to ping cirros .

Does anyone across this ?

OSA Victoria - Failure on os-keystone-install.yml

Dear all,

I am trying to install on a baremetal environment a new Openstack cluster using openstack-ansible.
I am following the official Guide (https://docs.openstack.org/project-deploy-guide/openstack-ansible/victoria/) and using Ubuntu 20.04.2 LTS on all the servers.
My configuration is as follow:
1x OSA node
3x infrastructure nodes
4x compute nodes
3x OSD nodes for Ceph

The following tasks have completed with success:

• setup-hosts.yml
• setup-infrastructure.yml

I am now stucked at setting up openstack (setup-openstack.yml). In particular the error appear immediately at os-keystone-install.yml with the log attached below.

Any idea how to proceed? It seems that the first error should be related to an ansible task, and later nothing is completed on the server. I can re-execute the playbook (os-keystone-install.yml) but nothing changes.
Moreover, after failure, I can't find any keystone service running or just installed in the container...
Thanks for the help.

TASK [os_keystone : Ensure keystone service is stopped] ***************************************************************************************************
fatal: [infra1_keystone_container-95b397f8]: FAILED! => {"msg": "The conditional check '(item.status['LoadState'] == 'loaded' | bool)' failed. The error was: error while evaluating conditional ((item.status['LoadState'] == 'loaded' | bool)): 'dict object' has no attribute 'LoadState'\n\nThe error appears to be in '/etc/ansible/roles/os_keystone/tasks/keystone_db_sync.yml': line 55, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: Ensure keystone service is stopped\n ^ here\n"}

RUNNING HANDLER [os_keystone : Restart web server] ***************************************************************************************************
changed: [infra1_keystone_container-95b397f8]

RUNNING HANDLER [os_keystone : Wait for web server to complete starting] ***************************************************************************************************
FAILED - RETRYING: Wait for web server to complete starting (5 retries left).
FAILED - RETRYING: Wait for web server to complete starting (4 retries left).
FAILED - RETRYING: Wait for web server to complete starting (3 retries left).
FAILED - RETRYING: Wait for web server to complete starting (2 retries left).
FAILED - RETRYING: Wait for web server to complete starting (1 retries left).
failed: [infra1_keystone_container-95b397f8] (item=5000) => {"ansible_loop_var": "item", "attempts": 5, "changed": false, "elapsed": 25, "item": 5000, "msg": "Timeout when waiting for 172.29.236.219:5000"}

RUNNING HANDLER [os_keystone : Stop uWSGI] ****************************************************************************************************
FAILED - RETRYING: Stop uWSGI (5 retries left).
FAILED - RETRYING: Stop uWSGI (4 retries left).
FAILED - RETRYING: Stop uWSGI (3 retries left).
FAILED - RETRYING: Stop uWSGI (2 retries left).
FAILED - RETRYING: Stop uWSGI (1 retries left).
failed: [infra1_keystone_container-95b397f8] (item=keystone-wsgi-public) => {"ansible_loop_var": "item", "attempts": 5, "changed": false, "item": "keystone-wsgi-public", "msg": "Could not find the requested service keystone-wsgi-public: host"}

RUNNING HANDLER [os_keystone : Start uWSGI] *****************************************************************************************************
FAILED - RETRYING: Start uWSGI (5 retries left).
FAILED - RETRYING: Start uWSGI (4 retries left).
FAILED - RETRYING: Start uWSGI (3 retries left).
FAILED - RETRYING: Start uWSGI (2 retries left).
FAILED - RETRYING: Start uWSGI (1 retries left).
failed: [infra1_keystone_container-95b397f8] (item=keystone-wsgi-public) => {"ansible_loop_var": "item", "attempts": 5, "changed": false, "item": "keystone-wsgi-public", "msg": "Could not find the requested service keystone-wsgi-public: host"}

RUNNING HANDLER [os_keystone : Wait for uWSGI socket to be ready] ***************************************************************************************************************************************************************************
FAILED - RETRYING: Wait for uWSGI socket to be ready (5 retries left).
FAILED - RETRYING: Wait for uWSGI socket to be ready (4 retries left).
FAILED - RETRYING: Wait for uWSGI socket to be ready (3 retries left).
FAILED - RETRYING: Wait for uWSGI socket to be ready (2 retries left).
FAILED - RETRYING: Wait for uWSGI socket to be ready (1 retries left).
failed: [infra1_keystone_container-95b397f8] (item=35358) => {"ansible_loop_var": "item", "attempts": 5, "changed": false, "elapsed": 25, "item": "35358", "msg": "Timeout when waiting for 127.0.0.1:35358"}

RUNNING HANDLER [os_keystone : meta] *****************************************************************************************************

RUNNING HANDLER [python_venv_build : venv changed] *****************************************************************************************************

PLAY RECAP ****************************************************************************************
infra1_keystone_container-95b397f8 : ok=71 changed=17 unreachable=0 failed=5 skipped=21 rescued=0 ignored=0
localhost : ok=3 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0

Error: "too many arguments to function ‘__ip_select_ident’"

Hi,
I've got this error when trying this playbook on task build openvswitch-datapath kernel module - this may take a while for the compute host.

There is the stacktrace:

make[3]: Entering directory `/usr/src/linux-headers-3.2.0-72-generic'
  CC [M]  /usr/src/modules/openvswitch-datapath/openvswitch/datapath/linux/actions.o
  CC [M]  /usr/src/modules/openvswitch-datapath/openvswitch/datapath/linux/checksum.o
  CC [M]  /usr/src/modules/openvswitch-datapath/openvswitch/datapath/linux/datapath.o
  CC [M]  /usr/src/modules/openvswitch-datapath/openvswitch/datapath/linux/dp_notify.o
  CC [M]  /usr/src/modules/openvswitch-datapath/openvswitch/datapath/linux/flow.o
  CC [M]  /usr/src/modules/openvswitch-datapath/openvswitch/datapath/linux/genl_exec.o
  CC [M]  /usr/src/modules/openvswitch-datapath/openvswitch/datapath/linux/tunnel.o
/usr/src/modules/openvswitch-datapath/openvswitch/datapath/linux/tunnel.c: In function ‘ovs_tnl_send’:
/usr/src/modules/openvswitch-datapath/openvswitch/datapath/linux/tunnel.c:309:3: warning: passing argument 2 of ‘__ip_select_ident’ makes integer from pointer without a cast [enabled by default]
include/net/ip.h:268:6: note: expected ‘int’ but argument is of type ‘struct dst_entry *’
/usr/src/modules/openvswitch-datapath/openvswitch/datapath/linux/tunnel.c:309:3: error: too many arguments to function ‘__ip_select_ident’
include/net/ip.h:268:6: note: declared here
make[4]: *** [/usr/src/modules/openvswitch-datapath/openvswitch/datapath/linux/tunnel.o] Error 1
make[3]: *** [_module_/usr/src/modules/openvswitch-datapath/openvswitch/datapath/linux] Error 2
make[3]: Leaving directory `/usr/src/linux-headers-3.2.0-72-generic'
make[2]: *** [default] Error 2
make[2]: Leaving directory `/usr/src/modules/openvswitch-datapath/openvswitch/datapath/linux'
make[1]: *** [binary-modules] Error 2
make[1]: Leaving directory `/usr/src/modules/openvswitch-datapath'
make: *** [kdist_build] Error 2
BUILD FAILED!
See /var/cache/modass/openvswitch-datapath-source.buildlog.3.2.0-72-generic.1416872702 for details.

FATAL: all hosts have already failed -- aborting

Regards.

Problem running "ansible-playbook openstack.yaml"

During the "make all" execution, the "ansible-playbook openstack.yaml" task failed with this message

Traceback (most recent call last):
File "/home/john/Src/ansible/bin/ansible-playbook", line 225, in
sys.exit(main(sys.argv[1:]))
File "/home/john/Src/ansible/bin/ansible-playbook", line 186, in main
pb.run()
File "/home/john/Src/ansible/lib/ansible/playbook/init.py", line 215, in run
play = Play(self, play_ds, play_basedir)
File "/home/john/Src/ansible/lib/ansible/playbook/play.py", line 104, in init
self._tasks = self._load_tasks(self._ds.get('tasks', []), load_vars)
File "/home/john/Src/ansible/lib/ansible/playbook/play.py", line 286, in _load_tasks
x.tags.extend(self.tags)
AttributeError: tags

The ansible-playbook version is "ansible-playbook 1.2 (devel f90f571f4d) last updated 2013/04/20 17:24:06 (GMT -500)"

Any chance this could move to Apache2 License?

Hey Team,

Any chance the license could change from GPLv3 to Apache2?

`make all` doesn't "just work" with nova package from Fedora 16

Great repo! As I was discussing at http://irclog.perlgeek.de/crimsonfu/2012-10-30#i_6113448 I had a little trouble getting this to work. After vagrant up I had to vagrant ssh controller to set environment variables and run ssh-keygen before I could run nova boot.

Here's the last bit of output from vagrant up:

PLAY RECAP ********************* 
192.168.206.131                : ok=8    changed=6    unreachable=0    failed=0    


./boot-cirros.sh
usage: nova [--username USERNAME] [--apikey APIKEY] [--projectid PROJECTID]
            [--url URL] [--version VERSION]
            <subcommand> ...
nova: error: argument <subcommand>: invalid choice: 'secgroup-add-rule' (choose from 'actions', 'add-fixed-ip', 'backup', 'backup-schedule', 'backup-schedule-delete', 'boot', 'boot-for-account', 'delete', 'diagnostics', 'flavor-list', 'image-create', 'image-delete', 'image-list', 'ip-share', 'ip-unshare', 'ipgroup-create', 'ipgroup-delete', 'ipgroup-list', 'ipgroup-show', 'list', 'migrate', 'pause', 'reboot', 'rebuild', 'remove-fixed-ip', 'rename', 'rescue', 'resize', 'resize-confirm', 'resize-revert', 'resume', 'root-password', 'show', 'suspend', 'unpause', 'unrescue', 'zone', 'zone-add', 'zone-boot', 'zone-delete', 'zone-info', 'zone-list', 'help')
usage: nova [--username USERNAME] [--apikey APIKEY] [--projectid PROJECTID]
            [--url URL] [--version VERSION]
            <subcommand> ...
nova: error: argument <subcommand>: invalid choice: 'secgroup-add-rule' (choose from 'actions', 'add-fixed-ip', 'backup', 'backup-schedule', 'backup-schedule-delete', 'boot', 'boot-for-account', 'delete', 'diagnostics', 'flavor-list', 'image-create', 'image-delete', 'image-list', 'ip-share', 'ip-unshare', 'ipgroup-create', 'ipgroup-delete', 'ipgroup-list', 'ipgroup-show', 'list', 'migrate', 'pause', 'reboot', 'rebuild', 'remove-fixed-ip', 'rename', 'rescue', 'resize', 'resize-confirm', 'resize-revert', 'resume', 'root-password', 'show', 'suspend', 'unpause', 'unrescue', 'zone', 'zone-add', 'zone-boot', 'zone-delete', 'zone-info', 'zone-list', 'help')
usage: nova [--username USERNAME] [--apikey APIKEY] [--projectid PROJECTID]
            [--url URL] [--version VERSION]
            <subcommand> ...
nova: error: argument <subcommand>: invalid choice: 'keypair-add' (choose from 'actions', 'add-fixed-ip', 'backup', 'backup-schedule', 'backup-schedule-delete', 'boot', 'boot-for-account', 'delete', 'diagnostics', 'flavor-list', 'image-create', 'image-delete', 'image-list', 'ip-share', 'ip-unshare', 'ipgroup-create', 'ipgroup-delete', 'ipgroup-list', 'ipgroup-show', 'list', 'migrate', 'pause', 'reboot', 'rebuild', 'remove-fixed-ip', 'rename', 'rescue', 'resize', 'resize-confirm', 'resize-revert', 'resume', 'root-password', 'show', 'suspend', 'unpause', 'unrescue', 'zone', 'zone-add', 'zone-boot', 'zone-delete', 'zone-info', 'zone-list', 'help')
usage: nova boot [--flavor <flavor>] [--image <image>] [--ipgroup <group>]
                 [--meta <key=value>] [--file <dst-path=src-path>]
                 [--key [<path>]]
                 <name>
nova boot: error: argument --image: invalid int value: 'cirros-0.3.0-x86_64'
make: *** [run] Error 2
[pdurbin@tabby openstack-ansible]$ 

Here's what I ran on the controller to get nova boot to work:

vagrant@controller:~$ nova boot --flavor 1 --image cirros-0.3.0-x86_64 --key_name mykey cirros
ERROR: You must provide a username via either --os_username or env[OS_USERNAME]
vagrant@controller:~$ export OS_USERNAME=adminUser
vagrant@controller:~$ export OS_TENANT_NAME=openstackDemo
vagrant@controller:~$ export OS_PASSWORD=secretword
vagrant@controller:~$ export OS_AUTH_URL=http://192.168.206.130:5000/v2.0/
vagrant@controller:~$ export OS_REGION_NAME=RegionOne
vagrant@controller:~$ nova boot --flavor 1 --image cirros-0.3.0-x86_64 --key_name mykey cirros
ERROR: Invalid key_name provided. (HTTP 400)
vagrant@controller:~$ nova keypair-add --pub_key ~/.ssh/id_rsa.pub mykey
ERROR: Can't open or read '/home/vagrant/.ssh/id_rsa.pub': [Errno 2] No such file or directory: '/home/vagrant/.ssh/id_rsa.pub'
vagrant@controller:~$ ssh-keygen              
(snip)
vagrant@controller:~$ nova keypair-add --pub_key ~/.ssh/id_rsa.pub mykey

Problem creating a temporary directory

After vms creation and when an ubuntu repository was about to be added the following message appeared:

TASK: [ensure add-apt-repository, ubuntu-cloud-keyring and ntp are present] ***
The authenticity of host '192.168.206.131 (192.168.206.131)' can't be established.
ECDSA key fingerprint is 11:5d:55:29:8a:77:d8:08:b4:00:9b:a3:61:93:fe:e5.
Are you sure you want to continue connecting (yes/no)? yes
fatal: [192.168.206.131] => could not create temporary directory, SSH (mkdir -p $HOME/.ansible/tmp/ansible-1375404585.58-16393091086278 && chmod a+rx $HOME/.ansible/tmp/ansible-1375404585.58-16393091086278 && echo $HOME/.ansible/tmp/ansible-1375404585.58-16393091086278) exited with result 255
fatal: [192.168.206.130] => could not create temporary directory, SSH (mkdir -p $HOME/.ansible/tmp/ansible-1375404585.58-10499516672503 && chmod a+rx $HOME/.ansible/tmp/ansible-1375404585.58-10499516672503 && echo $HOME/.ansible/tmp/ansible-1375404585.58-10499516672503) exited with result 255

FATAL: all hosts have already failed -- aborting

PLAY RECAP ********************************************************************
to retry, use: --limit @/var/tmp/ansible/openstack.yaml.retry

192.168.206.130 : ok=0 changed=0 unreachable=1 failed=0
192.168.206.131 : ok=0 changed=0 unreachable=1 failed=0

stable/queens did not match any file(s) known to git

Hello, I m using the branch "Rocky" and received these errors on openstack-ansible environment deploy:

changed: [mini-controller_repo_container-b72ba32c] => (item={'name': u'magnum-ui', 'project_group': u'horizon_all', 'fragment': None, 'url': u'https://git.openstack.org/openstack/magnum-ui', 'version': u'2e9cb253eaee45a57f07369e432369dbff8fc173', 'original': u'git+https://git.openstack.org/openstack/magnum-ui@2e9cb253eaee45a57f07369e432369dbff8fc173#egg=magnum_ui&gitname=magnum-ui&projectgroup=horizon_all', 'egg_name': u'magnum_ui'})
FAILED - RETRYING: Clone git repositories (10 retries left).
...
FAILED - RETRYING: Clone git repositories (1 retries left).
failed: [mini-controller_repo_container-b72ba32c] (item={'name': u'molteniron', 'project_group': u'all', 'fragment': None, 'url': u'https://git.openstack.org/openstack/molteniron', 'version': u'stable/queens', 'original': u'git+https://git.openstack.org/openstack/molteniron@stable/queens#egg=molteniron&gitname=molteniron&projectgroup=all', 'egg_name': u'molteniron'}) => {"attempts": 10, "changed": false, "cmd": "/usr/bin/git checkout --force stable/queens", "item": {"egg_name": "molteniron", "fragment": null, "name": "molteniron", "original": "git+https://git.openstack.org/openstack/molteniron@stable/queens#egg=molteniron&gitname=molteniron&projectgroup=all", "project_group": "all", "url": "https://git.openstack.org/openstack/molteniron", "version": "stable/queens"}, "msg": "Failed to checkout stable/queens", "rc": 1, "stderr": "error: pathspec 'stable/queens' did not match any file(s) known to git.\n", "stderr_lines": ["error: pathspec 'stable/queens' did not match any file(s) known to git."], "stdout": "", "stdout_lines": []}

Someone received the same errors?

problems running "nova image-list"

Hi,

The readme file indicates that a ssh login is possible from the node controller. However, I was not sure what is the IP address of the running instance. I tried to run the "nova image-list" command and got this

vagrant@controller:~$ nova image-list
ERROR: You must provide a username via either --os-username or env[OS_USERNAME]

What additions steps are required in order to run this command successfully, get the proper IP address and try an ssh connection?

Thanks,

Enable docker engine as a virtualization

Dear All,

I would like if your ansible scripts support docker containers that can be provisioned using OpenStack.

If not please add it to your RODO it or I can push mine

Thanks in advance
Ahmed Abdullah

Question about openstack-ansible

Hello Developers

Excuse me i didn't find a good place to post this question , so putting it here. You can provide me the answer and close this issue.

1# Is this module only valid for Ubuntu. Can i deploy openstack using this ansible module on CentOS machines.

2# What version of openstack does it deploy , Havana / ICH / J / K ? where file / variable i need to update if i want to change openstack version ?

nova_keypair, NameError: global name 'nova_client' is not defined

I will try to figure this out...but if it's anything obvious let me know. :)

All I did was clone the repo, git submodule update --init, and run make.

TASK: [capture public key in variable] **************************************** 
changed: [controller]

TASK: [add ssh keypair to nova] *********************************************** 
fatal: [controller] => failed to parse: Traceback (most recent call last):
  File "/home/vagrant/.ansible/tmp/ansible-tmp-1396833154.9-61665095293347/nova_keypair", line 1208, in <module>
    main()
  File "/home/vagrant/.ansible/tmp/ansible-tmp-1396833154.9-61665095293347/nova_keypair", line 103, in main
    nova = nova_client.Client(module.params['login_username'],
NameError: global name 'nova_client' is not defined


FATAL: all hosts have already failed -- aborting

PLAY RECAP ******************************************************************** 
           to retry, use: --limit @/Users/curtis/demo.yaml.retry

controller                 : ok=13   changed=4    unreachable=1    failed=0   

make: *** [demo] Error 3

failed to make, because of item "chrony"

Here is the output below:

make
git submodule init
git submodule update
chmod 600 vagrant_private_key
cd testcases/standard; vagrant up
Bringing machine 'controller' up with 'virtualbox' provider...
Bringing machine 'compute' up with 'virtualbox' provider...
Bringing machine 'network' up with 'virtualbox' provider...
Bringing machine 'storage' up with 'virtualbox' provider...
[controller] VirtualBox VM is already running.
[compute] VirtualBox VM is already running.
[network] VirtualBox VM is already running.
[storage] VirtualBox VM is already running.
ansible-playbook -i testcases/standard/ansible_hosts openstack.yaml

PLAY [setup steps that are not specific to a particular role or project] ******

GATHERING FACTS ***************************************************************
ok: [compute]
ok: [storage]
ok: [controller]
ok: [network]

TASK: [update apt cache] ******************************************************
ok: [controller]
ok: [compute]
ok: [network]
ok: [storage]

TASK: [ensure required base packages are present] *****************************
failed: [network] => (item=chrony,python-mysqldb,python-software-properties) => {"failed": true, "item": "chrony,python-mysqldb,python-software-properties"}
msg: No package matching 'chrony' is available
ok: [compute] => (item=chrony,python-mysqldb,python-software-properties)
failed: [storage] => (item=chrony,python-mysqldb,python-software-properties) => {"failed": true, "item": "chrony,python-mysqldb,python-software-properties"}

msg: No package matching 'chrony' is available

Any suggestion?

Thank YOU!

Fatal Error when provisioning…

Hi,
I tested this playbook, and unfortunately this end with several fatal error (the same each time):

fatal: [controller] => template error while templating string: expected token ',', got 'chars'

I may be wrong, but I think it's related somehow to the management_network variable…

If someone has a clue?

Regards.