Description of problem: rhel-osp-director: should support openstack log collector /sos [root@overcloud-controller-1 heat-admin]# rpm -qa | grep rhos-log-collector [root@overcloud-controller-1 heat-admin]# Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.rpm -qa | grep rhos-log-collector 2. 3. Actual results: Expected results: Additional info:
(In reply to Ofer Blaut from comment #0) > Description of problem: > > rhel-osp-director: should support openstack log collector /sos > > [root@overcloud-controller-1 heat-admin]# rpm -qa | grep rhos-log-collector > [root@overcloud-controller-1 heat-admin]# We are no longer shipping the rhos-log-collector tool provided by the sos-plugins-openstack package in OSP 7. However both the under and over cloud should have sos installed. I'm rebuilding my director env now but please feel free to confirm if this is present in both clouds in the meantime!
(In reply to Lee Yarwood from comment #1) > (In reply to Ofer Blaut from comment #0) > > Description of problem: > > > > rhel-osp-director: should support openstack log collector /sos > > > > [root@overcloud-controller-1 heat-admin]# rpm -qa | grep rhos-log-collector > > [root@overcloud-controller-1 heat-admin]# > > We are no longer shipping the rhos-log-collector tool provided by the > sos-plugins-openstack package in OSP 7. However both the under and over > cloud should have sos installed. I'm rebuilding my director env now but > please feel free to confirm if this is present in both clouds in the > meantime! I've just confirmed that sos is missing for the undercloud and overcloud in the latest puddle. Odd given that the docs were already listing it and I'm sure it's there upstream. I assume we will need seperate instack-undercloud and overcloud-full BZs for this?
A single bug is sufficient, I think. For the undercloud, we could auto-install the package by having a dependency relationship or we could document it. For the overcloud, it's likely a DIB element
(In reply to Mike Burns from comment #3) > A single bug is sufficient, I think. For the undercloud, we could > auto-install the package by having a dependency relationship or we could > document it. > > For the overcloud, it's likely a DIB element Thanks Mike, I've submitted the following .spec change for python-rdomanager-oscplugin so that sos is installed before we run `openstack undercloud install` : Add sos as a required package. https://review.gerrithub.io/237100 Thankfully we already have an element for `sosreport`[1] that we can reuse for the overcloud. I've submitted the following to have this used when building images : Add sosreport element to overcloud images. https://review.gerrithub.io/237099 I assume we use the same process when building images? Lee [1] https://github.com/rdo-management/tripleo-image-elements/tree/mgt-master/elements/sosreport
need to make same image build patch to instack-build-images as well while we're still trying to merge the unified cli for building images
Patches are not yet merged, moving to ON_DEV. Also, the instack-undercloud version of this is not yet fixed.
(In reply to Mike Burns from comment #6) > Patches are not yet merged, moving to ON_DEV. Also, the instack-undercloud > version of this is not yet fixed. Thanks Mike, I've pushed the following instack-build-images patch for this : Add the sosreport element when building images. https://review.gerrithub.io/#/c/237441/
sos is installed on undercloud - instack-undercloud-2.1.2-11.el7ost.noarch [stack@puma33 ~]$ rpm -qa | grep sos sos-3.2-15.el7_1.1.noarch but not on over cloud nodes [heat-admin@overcloud-compute-0 ~]$ sudo rpm -qa | grep sos [heat-admin@overcloud-controller-1 ~]$ rpm -qa | grep sos
python-rdomanager-oscplugin-0.0.8-18.el7ost.noarch ca
[root@overcloud-controller-2 heat-admin]# rpm -qa | grep sos sos-3.2-16.el7ost.2.noarch [heat-admin@overcloud-compute-0 ~]$ rpm -qa | grep sos sos-3.2-16.el7ost.2.noarch python-rdomanager-oscplugin-0.0.8-32.el7ost.noarch
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-2015:1549