Bug 997680

Hi hail,  

can you update the sos package to version 1.8 or later without any other additional errata?

Looking at the sos change logs this appears to be where the batch command was introduced.  If this works around the issue that should confirm the root cause assessment.

Hi Rob,

We're using inbox package of redhat5.0 for official certification. Is it permit to update the package? In addition, the higest version of sos package in rhel v5(x86) is sos-1.7-9.62.el5_9.1.noarch in https://rhn.redhat.com/rhn/channels/PackageListSubmit.do?cid=6949. Please check if there's version 1.8 available for rhel5.0(both x86 and x64). 

Following is the all the sos version available searching from https://rhn.redhat.com for Red Hat Enterprise Linux (v. 5 for 32-bit x86):


 	sos-1.3-1.el5.noarch 	System Support Tools
	sos-1.5-1.el5.noarch 	System Support Tools
	sos-1.7-9.1.el5.noarch 	A set of tools to gather troubleshooting information from a system
	sos-1.7-9.16.el5.noarch 	A set of tools to gather troubleshooting information from a system
	sos-1.7-9.16.el5_3.5.noarch 	A set of tools to gather troubleshooting information from a system
	sos-1.7-9.2.el5.noarch 	A set of tools to gather troubleshooting information from a system
	sos-1.7-9.2.el5_2.2.noarch 	A set of tools to gather troubleshooting information from a system
	sos-1.7-9.27.el5.noarch 	A set of tools to gather troubleshooting information from a system
	sos-1.7-9.49.el5.noarch 	A set of tools to gather troubleshooting information from a system
	sos-1.7-9.54.el5.noarch 	A set of tools to gather troubleshooting information from a system
	sos-1.7-9.54.el5_7.1.noarch 	A set of tools to gather troubleshooting information from a system
	sos-1.7-9.62.el5.noarch 	A set of tools to gather troubleshooting information from a system
	sos-1.7-9.62.el5_9.1.noarch 	A set of tools to gather troubleshooting information from a system 


Thanks,
Hai

Hi Hai,

I just did some digging based on your reply.  sos-1.7-9.27.el5 is where the batch command was added in the RHEL5 stream.  1.8 was based on the sos changelog, but my box is RHEL6 so it gave me 1.8 as where this was introduced, as you noted RHEL5 is on a different version stream of 1.7.  Apologies for the confusion.

If you can install just this sos errata, rerun and update this bug with the results that would be most helpful.

I assume there is a certification being performed that is being impeded by this issue? If so, that will leave us with two opens.  1st, what is our best option for unblocking the certification (you are correct, typically errata is not supposed to be applied but the GA installation is required) and 2nd, what fix shall be implemented in the test suite to address this.  These can be solved in parallel with the issue is fully understood.

Hi Rob,

I just upgrade the sos package to sos-1.7-9.27.el5 and rerun the info test on both rhel5.0-x86 and rhel5.0-x64. The test PASS without any error. Please see the ouput.log in attachment. Following is the sosreport usage for sos-1.7-9.27.el5, it contains option: --batch:

[root@prme-swcert-dhcp043 ~]# sosreport --help
usage: sosreport [options]

options:
  -h, --help            show this help message and exit
  -l, --list-plugins    list plugins and available plugin options
  -n NOPLUGINS, --skip-plugins=NOPLUGINS
                        skip these plugins
  -e ENABLEPLUGINS, --enable-plugins=ENABLEPLUGINS
                        enable these plugins
  -o ONLYPLUGINS, --only-plugins=ONLYPLUGINS
                        enable these plugins only
  -k PLUGOPTS           plugin options in plugname.option=value format (see
                        -l)
  -a, --alloptions      enable all options for loaded plugins
  -v, --verbose         increase verbosity
  --no-progressbar      do not display a progress bar.
  --no-multithread      disable multi-threaded gathering mode (slower)
  --batch               do not ask any question (batch mode)
  --ticket-number=TICKETNUMBER
                        associate a ticket number with report
  --name=CUSTOMERNAME   associate a name with report

Some examples:

 enable cluster plugin only and collect dlm lockdumps:
   # sosreport -o cluster -k cluster.lockdump

 disable memory and samba plugins, turn off rpm -Va collection:
   # sosreport -n memory,samba -k rpm.rpmva=off

Created attachment 789031 [details]
sos-1.7-9.27.el5 INFO test output log

Hi Hai,

That looks good.  Would you be able to attach the results.xml.gz from a run.  This will let us test the results package is 100% good against a test catalog confirming this solution.

Also, I wanted to see if there was a specific certification being held up by this bug?

I've discussed this internally, and our current thinking is the best plan of action is to allow for this sosreport errata to be installed on the RHEL5.x releases that include older versions of the sos package and not to spin the test suite to introduce a change to work around the limitations of the old sosreport command.

For the purposes of completeness.  RHEL5.3 includes sos-1.7-9.16 and RHEL5.2 includes sos-1.7.9-2.  The effected releases should be 5.0, 5.1, and 5.2.

On these releases we will accept the sos-1.7-9.16.el5 errata being installed during the test runs and update the .el5 RPM spec file to require this version as a minimum.

(In reply to Rob Landry from comment #8)
> Hi Hai,
> 
> That looks good.  Would you be able to attach the results.xml.gz from a run.
> This will let us test the results package is 100% good against a test
> catalog confirming this solution.
> 
> Also, I wanted to see if there was a specific certification being held up by
> this bug?
> 
> I've discussed this internally, and our current thinking is the best plan of
> action is to allow for this sosreport errata to be installed on the RHEL5.x
> releases that include older versions of the sos package and not to spin the
> test suite to introduce a change to work around the limitations of the old
> sosreport command.

Hi Rob,

There was no specific certification being held up by this bug.

I have rerun all the tests except kdump on rhel5.0 x86 after upgrading the sos package to sos-1.7-9.27.el5. All tests are PASS. Please find the results.xml.gz in attachment.

Thanks,
Hai

Created attachment 789450 [details]
results.xml.gz for rhel5.0-x86

results.xml.gz for rhel5.0-x86 after upgrading the sos package to sos-1.7-9.27.el5

Results check into the test catalog cleanly and look as expected.  If we do another 1.5 spin, we'll also go ahead and add the %requires => on the sos version so the problem can be identified before people are testing.