Due to changes with the drop-root work, we lost the ability to write
to /var/lib/nova/*. This fixes those permissions and ensures cross
container talk works properly between nova_libvirt and nova_compute
Additionally, this fixes another issue introduced which saw that
nova-compute could not run sudo commands as it did not have a proper
sudoers entry
Testing from previous deploys means you need a fresh environment. You
have to remove all of the named volumes that kolla created in docker.
Check these with `docker volume ls`
Signed-off-by: Hui Kang <kangh@us.ibm.com>
Signed-off-by: Artur Zarzycki <azarzycki@mirantis.com>
Co-Authored-By: Sam Yaple <sam@yaple.net>
Co-Authored-By: Hui Kang <kangh@us.ibm.com>
Closes-Bug: #1533350
Change-Id: I7f864c448a2414e0b5d89f48337be411b891df35
Remove the docker max version check since we are not pinning
docker version any more.
Partially-Implements: blueprint precheck-tasks
Change-Id: Icfa10e72c56092931aae016afaeed4c6ce8cb337
Ansible adminrc file already uses v3 as default. So let's
to that in vagrant too.
See file:
ansible/roles/common/templates/admin-openrc.sh.j2
TrivialFix
Change-Id: I23b7ff81808ddc718ae1186887e9764ebc5ab6ef
Support manila as container. First step only supports
building from source.
Change-Id: I60bb67536c9afdb9f0532b3cdc2c400a68608003
Partially-Implements: blueprint enable-manila-containers
This reverts commit b67c20f2db9da48fe5d3de1f5c5fb1887be1f20b.
This change hides the LOG output from the build process in the
console.html. While the build still will succeed/fail it will not update
the log while it is running. It will only dump the output of what its
doing if it fails. This is not ideal for our gates at this time since we
have seen the even the running and successful gates sometimes do not do
what we designed the gate to do (not building the containers we want,
not running the tests we want (recently happened with bashate), etc)
Change-Id: Ida58eef41ee8874e7577fcc24174fed4808f46f1
Option "verbose" from group "DEFAULT" is deprecated for removal.
Its value may be silently ignored in the future.
If this option is not set explicitly, there is no such warning.
Furthermore, the default value of verbose is true, so there is
no need to set this value in config files.
TrivialFix
Change-Id: I3ec2a8900c984a64bc0645672ef89a63975f7f4e
Since Ubuntu and Centos are both valid options it's better
to list their names in both bootstrap files
Trivial-fix
Change-Id: Ie8179403ba550ff61a45aa936fb87e02b9f74861
We currently support any buildarg via --build-args. This patch picks up
the default supported proxy buildargs if set in the user's environment,
to allow for more transparent proxy support.
The --build-args will take precendence.
DocImpact
Implements blueprint: better-proxy-support
Change-Id: I084e5d1cc8f9993d65167878f9983ad58a68e86e
* add a base TestCase class
* load the tests from the project root rather than only tests dir
* add a test case for WorkerThread builder function
Change-Id: Icf878f9249b475a311123c8235c42b1212d02ca6
Partially-implements: bp add-ut-codebase
Ceph-mon bootstrap container shares the same name of `ceph_mon` with
real ceph-mon service. When bootstrapping, it will sleep forever for the
purpose of distribute rings. Later on, when starting real `ceph_mon`
service, kolla_docker module will take bootstrap container as real one
because bootstrap container has a super set of env variables and
kolla_docker doesn't do strict comparing of env variable items.
This change follows the pattern of other bootstrap containers and rename
to use `bootstrap_ceph_mon` to avoid conflict.
Co-Authored-By: Sam Yaple <sam@yaple.net>
Change-Id: I0082820900928c42f9cc778ffd705980fea9ad1c
Closes-Bug: #1535140
