We have observed that omitting statefulset
on the olso_messaging values can cause octavia
workers to ocasionally fail with:
AMQP server on rabbitmq.openstack.svc.cluster.local:5672 is unreachable:
[Errno 104] Connection reset by peer. Trying again in 1 seconds.:
ConnectionResetError: [Errno 104] Connection reset by peer
This patch aims to keep the pattern used on the other serivces
to setup the transport_url that includes all pods in the statefulset.
Change-Id: I1905dc8f443929a03786fd01d6cf4e50ff5d3cb2
This patch allows the user to set log_config_append
to null which will flip back to the original shipped
logging config.
Change-Id: I1a2b90f208286a61c4ca5799a75d46d44bcd5296
As part of the move to helm v3, all the charts in the OSH repos
will no longer lint/build properly due to a lack of helm serve
in helm v3.
This change modifies the helm-toolkit repo location to the
osh-infra repo in order to account for the removal oh helm serve.
This work is part of the migration to helm v3 and will be utilized
in future changes.
Change-Id: I90d25943d69ad6c76455f7778a4894f00c525c46
The dnsPolicy not being set to "ClusterFirstWithHostNet" results in
the housekeeping service failing to connect to the database.
Change-Id: I23c9f0c561ea61695fbc7ce333a3f331cf31a7a4
This change bumps each openstack chart version up to the next
greatest minor version of 0.2.0, signifying that openstack-helm
will no longer support older, EOL releases for each chart.
Change-Id: I7ce80c7bdc779c1de4472079f18102f506bfbb90
Chart upgrading was failing due to some immutable fields are needed to upgrade before the jobs can be upgraded. For solving this issue, we
have added the helm.sh/hook annotations with post-install and post-upgrade values.
As for hook-weight annotations, we have added these to control the flow of the jobs with hook creation as the jobs are dependent. Like,
db-init jobs need to run before db-sync and so on.
Change-Id: I28dec6d082b95b448752e741e7694d32b2740cfa
With OSH now publishing charts regularly with each change, there
needs to be a way to track these changes in order to track the
changes between chart versions.
This proposed change adds in a reno check job to publish notes
based from the changes to each chart by version as a way to
track and document all the changes that get made to OSH
and published to tarballs.o.o.
Change-Id: Iff8681c697957e4711754fc20b07fa6b728eb584