Lets remove the faulty test (_No_valid_host_was_found)
till bug #1947133 is fixed
Related-Bug: #1947133
Change-Id: I4f3b994fd98262fb7e69ccf01734dff8fc16d913
Removing duplicate .txt extension from errors.txt..
Also, Adding errors.txt in artcl_logstash_files so that logstash pick
this up.
As size of logstash file is a factor, Adding errors.txt instead of
individual files seems better approach as errors.txt only contains
error/traceback from different log files.
Change-Id: Ib4519943d6b0ca4607f168318dff11a6d1713796
- Avoid using content provider job and the second standalone one
- Integration jobs are now running as experimental
Change-Id: I8a2f19fd091e827458f6769612c46341259047f3
The tox option to skip source distribution building is skipsdist,
but this seems to be often misspelled skipdist instead, which gets
silently ignored and so does not take effect. Correct it
everywhere, in hopes that new projects will finally stop copying
this mistake around.
See https://tox.readthedocs.io/en/latest/config.html#conf-skipsdist
and https://github.com/tox-dev/tox/issues/1388 for details.
Change-Id: I42016fd82d01db25b1506f07d8631f98e8da399f
We need to be able to see which jobs are failing
on tempest via tripleo-health. The initial
query would be the sova query ( ... FAILED )
In the future.. we could add the tempest test name
and build_status:failed to determine how often
certain tempest tests are failing.
Change-Id: Id3a20500830855da8b01bf0caae96f26671a4590
This repository should not make use of openstack containt files and addresses sanity job failure
caused by switch of nodeset image used for testing.
Change-Id: I7f3eab6ac44f53451114dcd8841bf4300500ab11
We encountered an issue when repoquery took several minutes
which has lead to timeouts and unfinished log collections.
To avoid that this commit adds a timeout which is basically
a fail-safe from collect_logs point of view.
The patch replaces for loop for record_available_packages command
by a single command.
Change-Id: Ie3007414aac14db47696fca62b07e1efa4e1de16
There have been problems with centos7 lately with py2/py3.
Ansible's pip module used python2 instead of python3 for
creating virtual venv which lead to dependency issues with
infrared which should be installed only by py3.
This changes also bumps the linters, removing yamllint which is now
included in ansible-lint.
Change-Id: If117b438fd55b17ead4016aabc3feae6632e722b
We run our deployment on multiple cloud, it is good to
collect nested virt info in order to investigate
server creation related issue.
It is needed for sc10 kvm jobs which is still in
development here:
https://review.rdoproject.org/r/q/topic:%22fix_octavia_kvm%22+(status:open%20OR%20status:merged)
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Change-Id: Ib9d89c9ce0e889a7ee6250f66b55c99a245d6d00
Removes internal sova-patterns.yml and use uri module to load the
same content as JSON from queries repository.
Change-Id: Ic9fd06f911e8c50819b2a10eb91fb9814787b025
Story: TRIPLEOCI-287
- converts lonely unit test to use the official unittest format
for ansible collections.
- adds two tests to sova module
- moves sovalib into sova module as this is required in order to
make the module compatible with both role and collection deployments.
Story: TRIPLEOCI-284
Change-Id: I6e0b2fa4a4b02fbf4133c28d29adaf0e3c16d344
- upgrade linters
- enable black formatting so we don't waste time making flake8 happy
- all the .py files modified by this patch were modified by black itself
Change-Id: I947cf8934a57ad519242757c777b23155fcbe7f4
Because Ansible official testing tools (ansible-test) cannot be used
without a collection, we change the code layout to make conformant.
WARNING: The role is no longer considered to be named
"ansible-role-collect-logs" but "collect_logs" instead, with a
temporary alias called "collect-logs".
Checklist:
- [x] ansible-test sanity checks runs (does not need to pass)
- [x] zuul is still able to use the role
- [x] infrared is still able to use the role
- [x] molecule tests are running and passing
- [x] tripleo-ci jobs still collect the files
One symlink is still needed for infrared until related patch lands:
https://review.gerrithub.io/c/redhat-openstack/infrared/+/508861
Change-Id: Ib87622797a284d837ee579d9cccec0ed73306626
Story: TRIPLEOCI-305
If the stack's name is not 'overcloud' then its rc file is not
collected. Rather than relying on a hard-coded stackrc,
overcloudrc, etc we can use a wildcard to catch them all. This
might also catch a few other files, but that's a small price to
pay.
Change-Id: I4892e3d5ff73eda3cc92406cecaf7611e6b6c304
None of our molecule tests were running but the job was executed.
This includes a fail-safe guard that should prevent such accidents
in the future. This assures the expected number of tests passed.
Change-Id: I6e1f80a7ecea65f42479376ce1a53c519f56bd68
If /usr/bin/python is not available when trying to collect
the logs, then none are collected. In this patch we ensure
that alternative python interpreters are considered when
attempting the log collection. The interpreters are
considered in order of preference, with the system python
being the last and the default when the host is unreachable.
This resolves the issue when infrared has an interpreter
set in the inventory, but it's the wrong one due to the
host recently being upgraded from RHEL7 to RHEL8.
Change-Id: I62ec9b5ed1978806c82a973bb901d527c731d3a9
Since we use the requirements from upper-constraints,
don't add upper cap to 1.3 which is too old version and
u-c is beyond that since pike.
Related-Bug: #1908054
Change-Id: If17755178dcf8f0505f58b3d68db404e878a958d
For dnf module specific issues, where one module is getting disabled
and others getting enabled will give a better insight to debug
podman or package related issues.
Change-Id: Iddc80d30b060b78185b8f4b9b119abc2bbd58ff8
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
frenzyfriday
yatinkarel