Bug 1702802

Summary: sosreport is missing /var/lib/mistral/overcloud/ansible.log
Product: Red Hat Enterprise Linux 7 Reporter: Alexander Chuzhoy <sasha>
Component: sosAssignee: Pavel Moravec <pmoravec>
Status: CLOSED ERRATA QA Contact: Martin KlusoĊˆ <mkluson>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.5CC: agk, bmr, dbecker, emacchi, gavin, mburns, mkluson, morazi, plambri, pmoravec, sbradley
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: sos-3.7-2.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1702806 (view as bug list) Environment:
Last Closed: 2019-08-06 13:15:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1702806    

Description Alexander Chuzhoy 2019-04-24 19:27:42 UTC
sosreport is missing /var/lib/mistral/overcloud/ansible.log

Environment:
sos-3.6-10.el8.noarch

Steps to reproduce:
Attempt an OC deployment.
Run sosreport to collect logs.

Tried:
sudo sosreport -e openstack_ironic -e openstack_nova --batch -p openstack,openstack_undercloud,openstack_controller --tmp-dir /var/tmp --all-logs --experimental -k docker.all=on;

Result:
/var/lib/mistral/overcloud/ansible.log is missing.

Expected result:
To have /var/lib/mistral/overcloud/ansible.log  in the generated report too.

Comment 4 Pavel Moravec 2019-04-26 06:19:15 UTC
After evaluating pending requests to 7.6.z stream for sosreport, their business justifications, requested changes and amount of affected customers/systems, I decided to release a hotfix for bz1702802 and bz1703330. My plan is to:

- deliver the HF in a week manner (no strict commitment, though)
- do not create extra 7.6.z errata for these two BZs
- include the changes in 7.7 and 8.1 (this is an obvious requirement from the nature of any HF)
  - in case 7.6.z errata would be needed, include the BZs there as well

Please raise your concerns against this plan until Wed 1st May EOB.

Comment 6 Pavel Moravec 2019-04-30 20:25:23 UTC
Hi,
It would be great to verify the fix for RHEL7.7 on a real / not mocked system, could you please do so?


A yum repository for the build of sos-3.7-2.el7 (task 21377022) is available at:

http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/2.el7/

You can install the rpms locally by putting this .repo file in your /etc/yum.repos.d/ directory:

http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/2.el7/sos-3.7-2.el7.repo

RPMs and build logs can be found in the following locations:
http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/2.el7/noarch/

The full list of available rpms is:
http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/2.el7/noarch/sos-3.7-2.el7.src.rpm
http://brew-task-repos.usersys.redhat.com/repos/official/sos/3.7/2.el7/noarch/sos-3.7-2.el7.noarch.rpm

Build output will be available for the next 21 days.

Comment 8 Pavel Moravec 2019-04-30 21:10:08 UTC
HF for RHEL7.6 is available at http://people.redhat.com/pmoravec/sos-3.6-17.el7_6.bz1702802_bz1703330/  (noarch rpm is sufficient, src rpm for FOSS reasons). Worth sharing to customers.

Comment 11 Emilien Macchi 2019-05-01 03:11:24 UTC
Verified:

[root@undercloud sosreport-undercloud-2019-05-01-msjbpng]# pwd
/root/sosreport-undercloud-2019-05-01-msjbpng
[root@undercloud sosreport-undercloud-2019-05-01-msjbpng]# ls var/lib/mistral/config-download-latest/ansible.log
var/lib/mistral/config-download-latest/ansible.log

I'm not QE but I can tell the patch helped to collect /var/lib/mistral/config-download-latest/ansible.log which is what was requested.

Comment 14 errata-xmlrpc 2019-08-06 13:15:47 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:2295