Currently, We are looking for string "overcloud" in
`tripleo_overcloud_status_output` to confirm if overcloud is deleted
or not.
Even when overcloud is present, we get "overcloud" in output and
hence we can miss some conditions where overcloud is not
deleted successfully.
~~~
$ openstack overcloud status
+------------+-------------------+
| Stack Name | Deployment Status |
+------------+-------------------+
| overcloud | DEPLOY_SUCCESS |
+------------+-------------------+
~~~
If overcloud is not available, We get:-
~~~
$ openstack overcloud status
No deployment was found for overcloud
~~~
"No deployment was found" string will be better filter to catch
if overcloud is deleted or not.
Change-Id: I41283afbcd81226b9322696d6d5265077684e2be
stack_name variable was missing from overcloud-delete
role. Added home dir var to overcloud-delete role.
Closes-Bug: #1940655
Signed-off-by: Amol Kahat <amolkahat@gmail.com>
Change-Id: Ie1b4ee8b54717614c65839c553c63a1ca589670d
This patch will remove all shell scripts and replace
them with tripleo operator ansible roles.
Change-Id: I1532f87a374631692a732999d3c3ed02fbcb9fef
Signed-off-by: Amol Kahat <amolkahat@gmail.com>
Upgrades yamllint to latest version and adots use of its strict
checking.
Fix all known problems reported by yamllint so we don't have to do
that while touching these files.
Change-Id: I4bdc520d9e2aff086c4b463718bc1e053261a4f5
Story: https://tree.taiga.io/project/tripleo-ci-board/task/381
On promotion jobs we hit problems when overcloud-deletion is
finished too late and we stop the job before, which leads to
failures.
Add time to wait for overcloud delete.
Change-Id: Idb4079b42cb69d7bddc8dd19817da79d49e1dcb3
Related-Bug: #1801525
When pipe is added to command, it should still exit with its
result code, so save it by setting pipeline option before each
command.
Close-Bug: #1676156
Change-Id: Ibbe49b4a15a5b7825447a563fe35af85fd48b3ff
Prepend a timestamp with awk to our deployment and test commands. This
allows html linking from the log servers and also better correlation
with the system logs.
We are not using the "ts" command from the moreutils package to avoid
extra dependencies. The drawback is the lack of sub-second timinig.
It is possible to disable the timestamping by setting the
timestamper_cmd to an empty string.
Also add a README file for the extras-common role.
Closes-Bug: #1673046
Change-Id: I8a2a1e4fde2ba805d3361e2e7a2337e873133ef0
- According to the ansible-lint documentation, we can pass a role directory as
an argument. But due to https://github.com/willthames/ansible-lint/issues/210,
the role directory has to contain a trailing slash!
- This patch fixes the following ansible-lint rules:
* ANSIBLE0004: Git checkouts must contain explicit version
* ANSIBLE0008: Deprecated sudo
* ANSIBLE0011: All tasks should be named
* ANSIBLE0014: Environment variables don't work as part of command
* ANSIBLE0015: Using bare variables is deprecated
- Temporarily skipping the following ansible-lint rules (Fixes will be part of
others patches):
* ANSIBLE0007: Using command rather than an argument to e.g file
We have a lot of 'rm' command and we should use file module instead
* ANSIBLE0012: Commands should not change things if nothing needs doing
* ANSIBLE0013: Use Shell only when shell functionality is required
Change-Id: I3d5591ea9fd1691e8115d7093db87781a08a6082
Signed-off-by: Gael Chamoulaud <gchamoul@redhat.com>
We need to differentiate local_working_dir from working_dir
as well as decouple the stack user from `ansible_user` var.
Both of these are causing issues as we begin to automate
deployments in more environments.
- Cleanup duplicate variables that are consumed via extras-common
- Note: extras-common depends on the common role in OOOQ
- Cleanup redundant var and superfluous quotes from overcloud-scale
role
- Cleanup redundant comments in <role>/defaults/main.yml
Closes-bug: 1654574
Change-Id: I9c7a3166ed1fc5042c11e420223134ea912b45c5
Ghanshyam Mann