Since we are working in process of removing tempest container
from wallaby release and all the tempest run is switched to
os_tempest for all supported release in tripleo-ci.
This change is not going to affect any periodic jobs also.
It also removes run_tempest and tempest_format var.
Related-Bug: #1916875
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Change-Id: I3d046047833044fd2d75ba399f784be5d992fbef
This was added to reduce the CI wall time. As we're removing
overcloud plan, this won't work. We can skip the converge
step if required later if we want to reduce the time jobs
take.
Change-Id: Ifd0371274fcc42286217a5c47e3998aafa98ddcc
The variable run_tempest was used by validate-tempest. Since now we use
only os_tempest, this variable is no longer required, however, since
use_os_tempest is default to true, we must change it where the
run_tempest is false, like in the upgrade/update jobs, since we don't
run tempest on those.
Change-Id: Idb8166992976ce6303f95f72011aa65fe536931e
Removes the redundant undercloud mapping from featuresets.
We've the default mapping in environments/undercloud.yaml.
Also this CI specific environment is redundant.
Change-Id: I72e41fb8cdebff12aab9704c2a9c4e368410c1ad
This option adds --debug to the cli command which generates an excessive
amount of logs. We shouldn't have this enabled by default.
Change-Id: I655aa888ca10cc622f80f3f267cdaddf844bdf81
From rocky onwards, the file used to identify the containers parameters
passed to be containers-prepare-parameter.yaml. This file had a different
format than in previous releases. At that point, a new variable was
introuduced in tripleo-upgrade to identify this containers parameter file:
uc_containers_prepare_file. To allow a transition from pre-rocky jobs to
post-rocky, the container_registry_file parameter was left to know the
name of the old containers prepare file. This file was removed from the
appended overcloud_deploy.sh files to avoid issues during the upgrade/
update prepare step [0].
Updates/Upgrades jobs were still using the container_registry_file as
the parameter used to set up the containers, pointing at the post-rocky
file containers-prepare-parameter.yaml. The code in [0] then removed it
from the appended -e environmetn files, running the overcloud update
prepare without the right containers-prepare-parameter.yaml.
[0] - https://review.opendev.org/#/c/717698
Change-Id: I6816db7382e7db6d0ae644c9487b2c5ee595a441
Closes-Bug: #1887176
The tripleo-upgrade sets by default to true the launch_sanity_workload parameter
which runs a workload test after performing the overcloud upgrade. This check
does not make sense in upstream CI as we don't have compute node.
Change-Id: I1347e70f548ee5b708fc6bbd0697cbab10fd2f65
Currently, we are using zuul user as overcloud_ssh_user during overcloud
deployment. While for upgrades, we are still passing tripleo-admin. This
is causing the upgrade prepare command to fail.
Change-Id: If4bd02dad8d69ba4c818ba8d800423bcc8ecfea4
Closes-Bug: #1813564
The output from the containers image prepare
step is not the containers-default-parameters.yaml
file with the list of containers, but another file
named containers-prepare-parameters.yaml which
contains the ContainerImagePrepare parameter. This
parameter is used during deployment-steps to get
the list of containers.
Co-Authored-By: Quique Llorente <ellorent@redhat.com>
Closes-Bug: #1789881
Depends-On: If0c7786059f1d0d91d2279f45c67525908633378
Depends-On: I96109c2452d7568da4a9374661a8ba8b9ba71458
Change-Id: I9bd21b67a9bf9254458351e8ba784ed66f9949f4
Tempest container is available and built when we deploy
containerized undercloud.
Since undercloud is containerized from rocky and ongoing, this patch
enable containerized tempest when undercloud is running as container.
Also, moved all tempest related configuration to the end of file to
avoid overwritten options
Depends-On: https://review.openstack.org/#/c/580384/
Change-Id: Icdb0f2b033ad0d1ba2548c591fa32dc649fff319
There was a try in [0] to enable containerized
undercloud in the scneario000 job, but an incompatibility
with the templates used in mixed-versions [1] forced
to disable it.
Trying again with [2].
Also, update custom tht paths for the mixed upgrade
jobs/featuresets configuratuin.
[0] - https://review.openstack.org/#/c/579755/14
[1] - https://bugs.launchpad.net/tripleo/+bug/1781227
[2] - https://review.openstack.org/#/c/465047/13
Co-authored-by: Bogdan Dobrelya <bdobreli@redhat.com>
Change-Id: I7b4592561a3d4229a9b335bad172dad758f83c91
Depends-On: I4e0dcf24b93b8e4afb8359cb5108c4b7b5ba3d55
Once [0] got merged, there is no chance that the
overcloud-upgrade role will run. Upgrade job have
all been moved to use the new tripleo-upgrade, so
we can dispense all overcloud-upgrade related
variables from the featuresets.
[0] - Iaf30244187d27909ab803175843056e0827d0b24
Change-Id: Ibe715cc4f604ba554db8dd4ab2d95391e4b1f311
Same fix than in a7dc4fa424 but for
upgrade job 040.
Repeating commit message for reference.
There has been an inventory and templates change in R undercloud,
variable rename from role_name to tripleo_role_name, to avoid
conflicting with internal ansible vars.
This makes the R undercloud config-download mechanisms incompatible
with Q templates.
Use --no-config-download when deploying Q OC with R UC to prevent
hitting this issue.
Change-Id: Idaa4be0acb37e684b5de1650e7945ded5dd54781
Co-Authored-By: Jiri Stransky <jistr@redhat.com>
Closes-Bug: #1776179
Due to the lack of possibility to upgrade an
environment with a single ceph node, we need
to leave out ceph services from upstream testing
in CI.
This patch also unsets the pingtest in favor of
tempest validations.
Change-Id: I38d2052145a9326406cde46586e6b2c7334a35ac
Closes-Bug: #1771074
We discovered we need to put back stack updates into the converge
operations. This increases the run time of the upgrade procedure
considerably, and e.g. our voting CI job for updates might go over the
time limit. We'll need to start passing --update-plan-only to the
converge operation to keep CI on previous run times.
Change-Id: Idc5dbebc116aba2420d275aab3981186511f298e
Related-Bug: #1768586
As part of the upgrades/updates playbook refactor
it has been removed the existence of a 'legacy'
and 'new' upgrades playbook, which was being
controlled by the 'use_tripleo_upgrade' variable
Iaf30244187d27909ab803175843056e0827d0b24.
Also, it's been moved the parameter container_registry_file
from the overcloud update's playbook into its
corresponding fs.
Related-Bug: #1749740
Depends-On: Iaf30244187d27909ab803175843056e0827d0b24
Depends-On: Iec42b574d697f3acfd668636e3dd11217a3ea25e
Change-Id: I27f13b164bb78619f8830b875ec9f04445ce1e26
First we switched the user to tripleo-admin [1] which made CI on
updates job green, but broke Nova-based environments. We're now
switching the default back to heat-admin [2] which will break updates
job again, so we add support to tripleo-upgrade [3] to customize the
user name and set it here to the value for CI (deployed server
environments).
Fear not, when we switch to --config-download as our only supported
deployment method, tripleo-admin should become unconditionally present
in all environments, and we'll be able to converge to a single method
of logging into the overcloud nodes.
[1] I1ec66886d6d61ccf528e5e27872cf68c7a603727
[2] I0df57002b2305c1e2504c9f7a7d0c326d8ffcaf7
[3] Ib486a812aa9fd96bc753eda122cd05682d97b209
Co-Authored-By: Jose Luis Franco <jfrancoa@redhat.com>
Change-Id: I063d438fbeeded28134658aaefc6c8b7119aee43
Related-Bug: #1759845
Depends-On: I0df57002b2305c1e2504c9f7a7d0c326d8ffcaf7
As stated in https://review.openstack.org/#/c/535859/19 the file has changed and now,
the docker images are expressed as default_parameters.
It fix problems like this:
:8787/tripleomaster/centos-binary-rabbitmq:ad1779c561edabdd6446c5fa39f05e121a327d7f_710b9460'}, {u'imagename': u'192.168.24.1:8787/tripleomaster/centos-binary-rsyslog-base:ad1779c561edabdd6446c5fa39f05e121a327d7f_710b9460'}]}}']
'parameter_defaults': KeyError: 'parameter_defaults'
mistral.executors.default_executor Traceback (most recent call last):
mistral.executors.default_executor File "/usr/lib/python2.7/site-packages/mistral/executors/default_executor.py", line 114, in run_action
mistral.executors.default_executor result = action.run(action_ctx)
mistral.executors.default_executor File "/usr/lib/python2.7/site-packages/tripleo_common/actions/package_update.py", line 82, in run
mistral.executors.default_executor parameters.update(self.container_registry['parameter_defaults'])
mistral.executors.default_executor KeyError: 'parameter_defaults'
Change-Id: I8030db471260151df2059085eac496d6538f4882
This makes use of the tripleo-upgrade role for Pike->Queens upgrade.
Depends-On: I4df06c8a0d5d8133ba64c38b90cef34793776422
Change-Id: I5823a99c4c8eca74f89185f0e643daec39891a3f
deployed_server is no longer common
through out the multinode featuresets.
deploy_steps_ansible_workflow is an
alternative now.
Related-Bug: #1748315
Change-Id: I52b9d68b2bb6efcc438855e5411eb5d56cc5d3d1
This will be used for a new container to container master job in
the tripleo-upgrades-experimental
gate-tripleo-ci-centos-7-container-to-container-upgrades-master
https://review.rdoproject.org/r/10944
Change-Id: If253766a126c45183f8ea263ff8af720e4ced4ad
Ghanshyam Mann