This change removes the ussuri-bionic jobs from check in zuul
for openstack-helm. Ussuri is the only release that is still
using bionic images and this change is part of our effort to
stay up-to-date.
A future change will update the charts to remove ussuri overrides
to reflect this.
Change-Id: I18a55426d92654e7baa422ad92ea9f092d854460
This change updates the tungsten fabric job to use a newer version
of openstack, wallaby, as well as moves it from periodic to
experimental.
Change-Id: I191bdaedba507ee76c04b2a2143362e772bcabc9
The Xena and Yoga jobs have been unstable lately, the compute-kit
job does not run reliable in Zuul. While we diagnose and fix the
issue, this change comments out both X & Y release jobs to reduce
the number of blocked developers and wasted rechecks.
Change-Id: I53f1a9cd8c24939cf73729c5c2a8bb674403fdd6
This verifies that making a configuration change to one of Umbrella's
subcharts results in only the application (DaemonSet, Deployment or
StatefulSet) for that subchart being updated. No other subchart's
application should be updated.
This only validates subcharts from openstack-helm-infra.
Validating the remaining subcharts from openstack-helm will
be done in the future.
OpenStack Umbrella's default values for rabbitmq was configured
to use a host path. This is so rabbitmq retains its data
between StatefulSet changes. Otherwise components fail to authenticate
with rabbitmq after the rabbitmq pods have been recreated. The
OpenStack Umbrella Chart will use the `standard` storage class
by default since that's what is provisioned via minikube.
Change-Id: I8570e32e6ae03563037608d337f31066edf29755
If a Helm upgrade is performed on the OpenStack Umbrella chart using
the exact same configuration as the first release, then it's expected
for no DaemonSets, Deployments, or StatefulSets to be updated.
This did not work as expected.
A few changes were required to support this desired behavior:
1. Update glance's configmap-etc.yaml to trim whitespace and convert
YAML comment to Helm template comment. Before this change, Helm
rendered the template with the YAML comment and a newline for the
install phase. On upgrades, Helm rendered the template without the
YAML comment and newline causing the hash of configmap-etc to change,
thus causing the glance-api Deployment to update.
2. Update openstack.sh script to create a randomly generated memcache
secret for glance. Without this change, the glance-api deployment
changes each time since Helm randomly generates a new memcache
secret if not provided.
This behavior is enforced via a new test script,
validate-umbrella-upgrade-no-side-effects.sh.
The following jobs are always recreated due to hooks:
- keystone-bootstrap
- keystone-credential-setup
- keystone-db-init
- keystone-db-sync
- keystone-domain-manage
- keystone-fernet-setup
- keystone-rabbit-init
- rabbitmq-cluster-wait
Some Jobs are created via CronJobs and could be created during
validation. So far, heat-engine-cleaner has been seen, but others
could be caught too.
So the validation script ignores these pod changes by ignoring if
Jobs were recreated. Plus Jobs being recreated should not impact
the OpenStack deployment.
Change-Id: Iffaa346d814b8d0a3e2292849943219f70d50a23
This change removes the zuul check and gate jobs that run the
train release of openstack. This is part of the effort to continue
support for the latest versions of openstack.
Change-Id: Id44d43fe8d99ae6b3f5405458986ce93d1366282
ADD: include new charts to the umbrella chart for comprehensive
deployment of openstack-helm.
* openvswitch
* libvirt
* neutron
* nova
* placement
Change-Id: I78d1c7c629024c3f9530239dff9f8eb9da598764
This change updates the horizon job to run under the wallaby
release on ubuntu focal image. Due to the dependencies
between the images repo and this one, we will need to create
a separate new job before moving over.
Change-Id: I966adc8ac4a54d3c2c06707ecd6c041fe4708c96
OpenStack Xena currently fails to run due to nova requiring a
version of libvirt that is greater than what comes with ubuntu
focal. This change comments out the job for now while a fix is
made.
Change-Id: Icc06fb6d81ab742b7e88888810d56a5a8aaa2f53
We currently run the TLS job in both check and gating. The TLS job
does not reliably pass however due to resource constraints so
having it run on each check results in quite a few rechecks.
This change moves the TLS job from check to experimental to avoid
having to perform these rechecks while having the ability to
run the job on demand when needed.
Change-Id: Ia44354066cc22c936de7dbab4c56b18527cfaa85
This change adds the minimum version of tls1.2 to not allow insecure
older tls versions to be allowed.
Change-Id: I880ac1caf31d2a26ca78389d5f96b07cf42b61ac
The current bandit job appears to be failing due to a dependency
on setuptools. This change adds in a manual install for setuptools
when running the bandit job.
Change-Id: I6d0f5987c4f1a5fe7cfeed3eddb6d21c3040ebb0
This change cleans up several redundant values and updates several
openstack release references to wallaby.
Change-Id: I547408a81c73b6b3db147582def6e8527e75a5c3
This change modifies the keystone-ldap job to run in check when
the keystone chart contains any modifications. This moves it from
running periodically to running on each keystone change.
Depends-On: https://review.opendev.org/c/openstack/openstack-helm/+/816209
Change-Id: I32008e3a14b0428922071205f873087c2aba071d
The TLS job was previously broken with the change to helm v3, but
has since been fixed. This change makes it voting again.
Change-Id: I3ea6f12a4d165f9ff64e002e860e873a603f6a6d
This change updates the experimental jobs that are
currently working to use helm v3. Later changes should
fix the other issues that they are currently experiencing.
Change-Id: I068a9bb835e1bde4d11d8dee0352c49248c20b15
We currently run multiple jobs that deploy cinder on changes
that have no relation to the service. This change modifies the
job to only run when we modify the cinder chart, test scripts,
or the zuul files themselves.
Change-Id: Ia188193929143cb6ae52266a5a87d2662626d42e
This change migrates the check jobs in OSH to use the
new helm v3 script when deploying kubernetes via
minikube.
This is one step in the move to helm v3. Future changes
will migrate the other jobs.
Change-Id: If741db5997a27ed06584b9af2d50485d8de34a2b
The move to helm v3 breaks the rendering for the ca-issuer chart.
While that gets fixed, we can temporary make the job non-voting
in order to unblock the migration to helm v3.
Change-Id: Ia25ac1f85974fc8c8ac8cf3ffedff746a92f2cf5
Now that the main linting job runs helm v3, this extra job is
no longer needed. This change removes the specific helm v3
linter job.
Change-Id: I40d6be368a4f36242c54b9a57b7e6f7328be8bb6
Now that the kubeadm-aio is fixed, we can re-enable the
multinode jobs for gating against openstack-helm.
Change-Id: Ib1f1bca5f370e0326ea0211dfcfba9544bd458b2
This change removes a bunch of old and duplicated jobs,
duplicate netpol and the old armada jobs that have not
been maintained. Also removed the tls job from
experimental since we run it now in gating.
Change-Id: Ic19520d8790c52d66d62b20a23658c57d954697e
This change adds a helm3 linter to the zuul check job list. The job
currently emits some warnings, these will be cleared up in future
changes.
Change-Id: I4d74ba5464e9e3d78b95298e9778b99f1b387fcd
This change adds the V and W openstack release jobs to the zuul
check list. This will bring OSH testing more in line with the latest
supported releases of OpenStack.
Change-Id: I2cc98159ee9bf1ad3ac5c70a772e2b4c1bbd7fa4
Defines compute kit and cinder jobs for new releases with
corresponding values overrides.
Disables compute agent list test for Wallaby since related API
is removed [0].
Since Wallaby with switch of osc to sdk '--id auto' is no longer
treated specially in 'openstack flavor create'. The same behavior
can be achieved w/o specifying --id flag for flavor creation [1].
Starting Wallaby 'nova-manage api_db version' returns init version
for empty database greater than 0 [2]. _db-sync.sh.tpl logic prior to
this commit does not work due to this. We need to either remove
(done in current commit) or justify and alter previous logic.
[0] https://review.opendev.org/749309
[1] https://review.opendev.org/750151
[2] https://opendev.org/openstack/nova/src/branch/stable/wallaby/nova/db/sqlalchemy/migration.py#L32
Change-Id: I361431d9aa8c1a06c5d59f479fb161ecd87e2ee2
Signed-off-by: Andrii Ostapenko <andrii.ostapenko@att.com>
With the latest removal of the tiller chart, the multinode jobs were
still utilizing the older method of deploying the kubeadm-aio. We
can disable these for now until the jobs get updated to avoid blocking
existing work.
Change-Id: Icbf694a1b23da5e662ba5b894ff45f443f705021
With the latest change[0] officially dropping support for older
non-maintained releases, this change removes several EOL release
jobs as well as bumps anything using those up to the latest
supported T release.
[0] https://review.opendev.org/c/openstack/openstack-helm/+/788380
Change-Id: I8df32c6bcc0b9a0c65aa1299c6a792b27da81ae8
With stein in extended maintenance, this change updates the check
and gate jobs to run train and up, as well as updating some jobs
to use train. Moved stein to periodic.
Change-Id: Icd516f25140ebd479b49da101e4f84326f341274
We already run the rocky jobs in periodic. With Rocky in EOL, we
can remove them from being checked on every change.
Change-Id: I8728297c9b0742cd10977185568c75fc2b8b7e7e
ubuntu-bionic-expanded is not available now. Temporary disable it to
unlock urgent efforts.
Change-Id: Ib6224d7420b0b09c1fbd615437eb15f02e762c34
Signed-off-by: Andrii Ostapenko <andrii.ostapenko@att.com>
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
