Since this is the user for which we setup the SSH key.
This commit allows to run kolla-ansible as vagrant user without using
sudo.
This only applies to multinode.
TrivialFix
Change-Id: Ie5231085a66511a520d4dbe5e9f35414acf1900b
The regex used previously would keep the short hostname (hostname -s)
on the 127.0.0.1 line.
Reset the 127.0.0.1 line to keep only localhost.
TrivialFix
Change-Id: I90bdec6793ac5b2d304e178e5114369b7b3b9626
The SUPPORT_NODE variable was missed during a refactoring of
bootstrap.sh and is now unused. Remove it.
TrivialFix
Change-Id: I10ab4368b383dbb620916f70c368153403944001
In vagrant environments, the kolla_internal_vip_address didn't belong
to the private network provisioned on the machine and was failing the
prechecks.
TrivialFix
Change-Id: I0e7e4d134e350c49ef7510c7262677754a83bcbf
This allows us to execute vagrant commands by default on the 'operator'
VM and eliminate one of the difference between AIO and multinode.
TrivialFix
Change-Id: Ia14aa026d1146ec4b1e006c72a2460edfc0cf6eb
This patch check two senario
first if we choose to start a new container
with name say XXX, however in the env a container
already exist with XXX name and second to start a stopped container.
Change-Id: Ibd6c5fbcc6f37ea2481634ac2e6b3edb91ae7aab
Partially-Implements: blueprint ansible-unit-tests
When kolla_internal_vip_address didn't belong to the same network as
network_interface, the prechecks would spit out an ugly error:
Unexpected templating type error occurred on [snip]:
argument of type 'NoneType' is not iterable"
This commit fixes the check to execute properly.
Change-Id: I24a066c212c78e105a923525b131724736ac74b6
The Nova EC2 API is disabled by default, the default value
of the enabled_apis parameter in nova.conf is "osapi_compute, metadata"
The EC2 API is marked as deprecated and will be removed from Nova in
the future.
Change-Id: I6b9d66017e066cde5749be45b367194d2192ead3
Closes-bug: #1586605
This solves the following issue when using latest noVNC sources for
the nova-novncproxy container:
OSError: [Errno 13] Permission denied: '/usr/share/novnc'
Change-Id: Iea1f3dfcc696f53431e99570019e27cdef4ca5cb
Closes-bug: #1593006
In the current CI, we have no regitry service. when running pull action,
it will pull image form docker.io where has no such image too.
The right direction is set up a local regitry service, then push and
pull image from there.
TrivialFix
Change-Id: I3ebea5cdb539cb700487a2dbffa894fcce8f8723
Upgrade the kernel version is not acceptable for the server in most
of case. I do not see the issue when using ubuntu 14.04 default
kernel with docker aufs storage driver.
Even if there is some wrong in the aufs driver, we could recommend
the user to use other drivers, like lvm, brtfs or even overlay driver.
This reverts commit 833c1269c7941498787d49ce879be6c283728407.
Change-Id: I6ee71ecd1ca64777b874bfcc342162622643b89c
If we have bug in contianer or it simplt somehow ended up in Exited
state, cleanup doesn't flush it. It also means it doesn't flush volumes
and that might cause an dirty env.
Closes-Bug: #1587344
Change-Id: Ib5705992500ce7efdc66509df61c381bd33d1954
The verbose parameter is deprecated and should not be used. This
solves the following issue:
Option "verbose" from group "DEFAULT" is deprecated for removal.
Its value may be silently ignored in the future
TrivialFix
Change-Id: Ifb04c3f396a96b6917637af3a90a3ddb1599e29d
This solves the following issue when running an ansible command inside
the kolla-toolbox container:
[Errno 13] Permission denied: '/home/ansible/.ansible'
Change-Id: I654d27c49b7fcc50e018b61146084660894352aa
Closes-bug: #1592268
