Copy the patterns from the rabbit checks, skip some pre-checks when the
container has already been started. Without this change the pre-checks
fail when you re-run the deploy, i.e. the port is not free because
rabbit is already running on that port.
This bug was triggered because murano is enabled, and this change has
been added to add the extra rabbitmq instance by default:
d8fe3ea780c188b6e937ab6f08a8475d2330a9fa
Closes-Bug: #1715135
Change-Id: I0eb8785e7cd4eadfa792ea14a27f54a891b2bf02
Before this change ironic prechecks failed with the error:
'tenant_network_types' is undefined
This problem appears to have been introduced in:
296ddbeb035c6f582b316f066fe2ddffece07aca
Closes-Bug: #1714946
Change-Id: I609ae20c4558370a0a8c4c316cd47cbd1d086331
'progname' is actually only fullfilled for Openstack services logs.
They are missing for MariaDB and RabbitMQ logs.
When using Kibana, "progname" field appears empty, hence it's difficult
to known where logs comes from.
Change-Id: Ifcbfd981a34a8d64ea69d37934c7f0fae10a90b5
Closes-Bug: #1713412
Actual Fluentd config doesn't manage multiline log pattern like:
2017-08-16 21:41:03.097 7 WARNING oslo_config.cfg [-] Option "firewall_driver" from group "DEFAULT" is deprecated for removal (
nova-network is deprecated, as are any related configuration options.
). Its value may be silently ignored in the future.
This log will generate 1 Fluentd event for each line (in previous
example 3 events).
This is really a wrong behaviour and made Kibana interface not friendly.
This patch uses a multiline parser.
Change-Id: Iee337645d1dc42876ec79be08ee3715f11a53d87
Closes-Bug: #1711399
Console access for HyperV VMs is now done via Kolla VIP.
The VIP will point to each HyperV compute node IP on which
FreeRDP-WebConnect is installed.
Closes-Bug: #1714249
Change-Id: I3a5d23425996a5c347ff21df3f99c3f63dd35173
Currently, kolla_keepalived_running may be created and deleted in
parallel which causes prechecks failure. The solution is using
run_once = true.
Closes-Bug: #1714407
Change-Id: I2ec8fc2e867c87175157af8acc11f57313bfaabe
Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
[WARNING]: when statements should not include jinja2 templating
delimiters such as {{ }} or {% %}. Found:
{{ (bootstrap_mongodb_cluster.stdout|from_json).ok != 1 }}
Reason: Ansible 2.3.0 does not like delimiters in when statement.
Fix small typo
Change-Id: I69ea5f640b8e841e532eca97b7ed3959e9335967
Closes-Bug: #1714337
[WARNING]: when statements should not include jinja2 templating
delimiters such as {{ }} or {% %}. Found: {{ 'already' not in mongodb_panko_database.stdout }}
[WARNING]: when statements should not include jinja2 templating
delimiters such as {{ }} or {% %}. Found: {{ mongodb_panko_database.stdout.split()[4] != 'connecting' }}
Reason: Ansible 2.3.0 does not like delimiters in when statement.
Change-Id: If34130ccf03c0fbadd17eb24fa8e71fbbf2bcd70
Closes-Bug: #1714340
They dropped the cloudkitty-api command line[0], so we should add wsgi
support for cloudkitty-api.
[0]https://review.openstack.org/#/c/366043/
Change-Id: Ie34d4f2d5c303bbd7ac09a8ab9e8d9bdc763c57b
Closes-Bug: #1713879
- This change extends the networking-guide to describe
how to enable the newly added support for deploying ovs-dpdk.
Change-Id: I43405760ff315497f9396bfb0b36d6aa7fc5462a
Partially-Implements: blueprint ovs-dpdk
The ansible/kolla-host.yml playbook failed when called with a --limit
flag.
This was due to the fact that only the facts of the subset of hosts
were gathered but the "Generate /etc/hosts for all of the nodes" task
is using the ansible_<IFACE>.ipv4.address variable of all hosts.
The code for this fix is copied from the site.yml playbook
where it was used for the same reason.
Change-Id: I7e70caf750506ad8ab36ec024bd9647dd733fbd0
Closes-Bug: #1713725
storage settings for elasticsearch are not correct.
Need a backend and expecific options for the backend.
Change-Id: I71e35644389b6f97a20daf0f1dec29a30c3c34e3
Closes-Bug: #1713693
Actually a unique 'tail' source is used for all logs files in
kolla/*/*.log.
So log files from services like: chrony, elasticsearch, etcd, grafana,
influxdb, kibana, mongodb... are actually processed by our Fluentd
config, but should not cause all following config will failed to parse
them. It just uses CPU for nothing cause they will
never match the following filters:
* record_transformer => add Hostname, Logger, programname field
* rewrite_tag_filter => rewrite 'programname' TAG if needed
Hence these filters should only be applied to Openstack services logs to
avoid CPU usage.
Furthermore WGI and Apache logs files must be treated differently.
Change-Id: I425979160291e1123e3775e39243bca06ed22c2f
Closes-Bug: #1711390
Sometimes gates fails due lack of disk space,
This change mounts a second disk in opt and moves
registry data to opt.
Disk format commands are excepts from devstack-gate:
dc49f9e6eb/functions.sh (L306)
Change-Id: I606aa491b8cbf678e83281bad1a0ff39d3920ff2
Closes-Bug: #1713652
