This adds a helm test for Horizon, the helm test
runs a selenium webdriver check to verify the dashboard
is up
Change-Id: I3616c05596b2bd94931c39fb774333bf65453d52
Signed-off-by: Steve Wilkerson <sw5822@att.com>
This change removes the network policy overrides from the default
developer deployment scripts now that there is a set of
designated scripts that provide this functionality.
Change-Id: I788845e85314b3a8a9c860fbc77de536113781e0
This change allows the restartPolicy of the tempest test pod to be set
to Never, bringing it in line with other test pod behavior, like rally.
If set to OnFailure, test pods are often deleted before logs can be
viewed.
Change-Id: I312b93784d27109452b2076658e5655210a92b48
This removes the logging overrides for using the oslo log
fluentd handler and formatter from the armada-osh manifest. As
the armada jobs in the openstack-helm repo no longer deploy the
lma components, there's no fluentd instance for the openstack
services to log to
Change-Id: I6aed11871046a2caf705a3c444d169d1d977bdee
Signed-off-by: Steve Wilkerson <sw5822@att.com>
Currently each service uses the same name for their helm test user,
"test". While this works when services are ran sequentially, when
multiple services are deployed and tested at the same time, it can
lead to a race condition where one service deletes the user before
the other is done testing, causing a failure.
This change makes it so that each service defines its own test user
in the form of [service]-test.
Change-Id: Idd7ad3bef78a039f23fb0dd79391e3588e94b73c
The volume variables is changed in mariadb chart.
It affects openstack helm gating job of mariadb, so we need to
change varible to
volume.use_local_path_for_single_pod_cluster.enabled.
Enable the local host path for mariadb data so if the container
is restarted during the gate jobs it can recover successfully.
Story: 2004702
Task: 33462
Depends-on: https://review.opendev.org/661955
Change-Id: Ib55779ddcbe7033da1900f5cd21de46543392d11
Prometheus mysql exporter is failing because of missing label in
network policy for mysql. This is to add the label to the override
yaml
Change-Id: Ic5e2613303f04d2bfab1229d3818a2fc9b4263bc
Signed-off-by: Sreejith Punnapuzha <Sreejith.Punnapuzha@outlook.com>
We now have a process for OSH-images image building,
using Zuul, so we should point the images by default to those
images, instead of pointing to stale images.
Without this, the osh-images build process is completely not
in use, and updating the osh-images process or patching its
code has no impact on OSH.
This should fix it.
Change-Id: I672b8755bf9e182b15eff067479b662529a13477
This PS fixes the heat cadf values key, to use the correct value.
Change-Id: I3efeccc2ba9bbebd7dc4b175244f00173c39d1ef
Signed-off-by: Pete Birley <pete@port.direct>
This adds missing passwords to the armada-osh manifest. These
passwords include: passwords for the test users used for the
openstack chart helm tests, the password for the mariadb sst user
deployed in the openstack namespace, and the mariadb exporter
user for the openstack mariadb instance
Change-Id: Ia04ab3d83d1967c4ab65915adaec53d488f451fb
Create the overrides file necessary for Rocky release:
- api-paste entrypoint neutron.api.versions:Versions.factory deprecated
Deployment script needs to be executed with OSH_OPENSTACK_RELEASE value.
Change-Id: If0d3553bd004426d8e97e1fa62ee9b99f4a895a9
Currently there is fake rpc call "pod_health_probe_method_ignore_errors"
that is passed to the service, just to find out if it is responding. Because
such method does not exist, it is needed to catch and handle the exception
that is inevitably thrown by the service.
While this is technically working correctly, the exceptions pollute the
log files and make it harder for user to see possible real errors.
This is how the error looks like:
ERROR oslo_messaging.rpc.server [-] Exception during message handling: oslo_messaging.rpc.dispatcher.UnsupportedVersion: Endpoint does not support RPC version 1.0. Attempted method: pod_health_probe_method_ignore_errors
ERROR oslo_messaging.rpc.server Traceback (most recent call last):
ERROR oslo_messaging.rpc.server File "/var/lib/openstack/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", line 163, in _process_incoming
ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message)
ERROR oslo_messaging.rpc.server File "/var/lib/openstack/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 276, in dispatch
ERROR oslo_messaging.rpc.server raise UnsupportedVersion(version, method=method)
ERROR oslo_messaging.rpc.server oslo_messaging.rpc.dispatcher.UnsupportedVersion: Endpoint does not support RPC version 1.0. Attempted method: pod_health_probe_method_ignore_errors
This situation is new since https://review.openstack.org/#/c/639711/
which (correctly) increased the default level of logging. Before 639711
error messages from oslo (both real and ones that could be ignored) were not
present in nova logs at all.
Fortunatelly, nova's BaseAPI class provides 'ping' method that is can
be used for this basic purpose by all nova components.
Change-Id: I0062e74bed399206becb8d9e00f9ec805da864a3
