To fix it we change the default param to True.
'show_image_direct_url' will be overridden.
Currently glance v2 doesn't allow to specify custom
locations for image by default, it returns 403.
Closes-Bug: #1740223
Related to https://review.openstack.org/#/c/279630/2
Change-Id: Ib4dd54c69830ab8f3f9812877b026f81c23c224a
The option neutron_endpoint_type is duplicate on these files:
- trove/templates/trove.conf.j2
- trove/templates/trove-taskmanager.conf.j2
We just have to remove one occurrence.
Change-Id: If5c91cf7b491966b1deac42c694af5995df9b11e
Provide support for kolla dev mode in Kuryr. When
'kolla_dev_mode' or 'kuryr_dev_mode' variables are
enabled, source code of Kuryr project is cloned
and bindmounted.
Partially implements: blueprint mount-sources
Change-Id: I74c1ea70b4220a0e91f19403971303ca55652371
interface_driver parameter is missing when using vmware DVS on the
dhcp_agent configuration. As a result we get the following error:
Error loading interface driver 'None'
Change-Id: I302a1392615792bd65cab9c0933cb7f7e5e1880d
Closes-Bug: #1736410
On AArch64 we run VMs without any graphics so nova console is not
available. For now we had to disable it by hand but it can be automated.
Change-Id: Ib903044493ca98c0dd29d3096f66272e130668b0
Although there is an option "enable_fluentd", but there are still
some tasks that make fluentd not configurable.
Change-Id: Ic0a9deb36fce154022925d26411e01a8ffe18b50
Signed-off-by: Xinliang Liu <xinliang.liu@linaro.org>
When a RabbitMQ node in multiple RabbitMQ nodes is started during
multinode deployment, it is required to communicate with each other
to be clustered. However, RabbitMQ nodes cannot communicate between
them due to missing host name in the nodename environment variable
of RabbitMQ. Subsequently, all of RabbitMQs cannot be started and
it will give rise to a deployment failure.
Change-Id: I7b4ba76807750db4a14d859454ba650bdaaf23ca
Signed-off-by: Taeha Kim <kthguru@gmail.com>
In some deployment scenarios the current timeouts
for mariadb bootstrap and kibana registration with
elasticsearch have been found to be too short. These
timeout increases shouldn't introduce any deployment
slowdown in current environment and eliminate
deployment failures in environments with slower
systems.
Change-Id: If33dfff2b42b23eff7ec2230c9b0c5a4c010072e
