RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

On RHEL 7, sosreport's upstart plugin has been largely replaced by the systemd plugin. From the log, it does not seem to collect any relevant data: none of the referenced files exist and the commands, if executed at all, produce a useless output (such as "init: unrecognized option '--version'" or "ls: cannot access /etc/init/: No such file or directory").

Is there any reason to keep it in sos, even if disabled be default?

Version-Release number of selected component (if applicable):
sos-3.2-15.el7.noarch

We support more than a dozen different distributions from the same upstream codebase: some use classical SysV init, some use Upstart, others systemd.

This not a bug any more than e.g. the existence of a Red Hat specific plugin would be in a CentOS, Debian or Ubuntu environment.

Also, I don't see why this is running on your system at all - the plugin will only trigger if a package named 'upstart' exists:

 20 class Upstart(Plugin, RedHatPlugin, DebianPlugin, UbuntuPlugin):
 21     """Upstart init system
 22     """
 23 
 24     plugin_name = 'upstart'
 25     profiles = ('system', 'services', 'boot')
 26     packages = ('upstart',)
 27 

Is that the case on your system? Or is it being force-enabled via the command line?

(In reply to Bryn M. Reeves from comment #3)

> Is that the case on your system? Or is it being force-enabled via the
> command line?

Force-enabled indeed. Sorry about the fuss.