Red Hat Bugzilla – Bug 434849
No available s390.py plugin exists, exists upstream but doesn't work.
Last modified: 2008-02-26 09:08:52 EST
+++ This bug was initially created as a clone of Bug #434846 +++
Description of problem:
There is no s390(x) sos plugin for RHEL 4 or RHEL 5, one exists up stream;
however it does not work on RHEL 4 and 5.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run sosreport
2. review data captured, missing s390 specific information.
3. Download and install F8 (upstream) plugin.
4. Run sosreport again
5. review logs
2008-02-25 13:33:13,056 WARNING: plugin s390.py does not install, skipping
2008-02-25 13:33:13,056 WARNING: could not load plugin s390.py
Either no data is collected for s390 or if using the upstream plugin, the plugin
fails to load and is skipped.
capture s390 information.
I have created a plugin that works and a patch that updates the non-working version.
-- Additional comment from firstname.lastname@example.org on 2008-02-25 15:28 EST --
Created an attachment (id=295836)
Patch that when applied to sos/plugins/s390.py (from F8) will create a working
Created attachment 295838 [details]
Patch, when applied to upstream version of sos/plugins/s390.py will create a working version.
The upstream version does work. It is just the fact that you are using an
upstream plugin with a shipped version of sosreport that tries to access a
function not yet released. In this case policyredhat getArch.
Ive committed some of the patch mainly the ones that we aren't capturing yet.
Please verify by downloading the _entire_ upstream trunk and testing against
both RHEL4 and RHEL5.