Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
When I spin up fresh RHEL-7.7-20190514.2 qcow image in OpenStack and run
alternatives --set python /usr/bin/python2
I get no error message printed and the return value of the above command is 2.
This is a bug because of the following promise from the man page of alternatives
"
DIAGNOSTICS
alternatives chatters incessantly about its activities on its standard output channel. If problems occur, alternatives outputs error messages
on its standard error channel and returns an exit status of 2. These diagnostics should be self-explanatory; if you do not find them so, please
report this as a bug.
"
If I run with --verbose, I get
[root@host-10-0-132-192 ~]# alternatives --set python /usr/bin/python2 --verbose
reading /var/lib/alternatives/python
[root@host-10-0-132-192 ~]# ls /var/lib/alternatives/python
ls: cannot access /var/lib/alternatives/python: No such file or directory
I can fix this by issuing
/usr/sbin/alternatives --install /usr/bin/python python /usr/bin/python2 1
Version-Release number of selected component (if applicable):
[root@host-10-0-132-192 ~]# alternatives --version
alternatives version 1.7.4
How reproducible:
Always
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Comment 2Petr Viktorin (pviktori)
2019-05-17 09:40:33 UTC
In RHEL 7, there are no alternatives for python; /usr/bin/python is always Python 2. The same issue happens with any missing alternative:
alternatives --set foo /bar
Changing component to chkconfig.
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 (chkconfig bug fix and enhancement update), 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/RHBA-2020:3890
Description of problem: When I spin up fresh RHEL-7.7-20190514.2 qcow image in OpenStack and run alternatives --set python /usr/bin/python2 I get no error message printed and the return value of the above command is 2. This is a bug because of the following promise from the man page of alternatives " DIAGNOSTICS alternatives chatters incessantly about its activities on its standard output channel. If problems occur, alternatives outputs error messages on its standard error channel and returns an exit status of 2. These diagnostics should be self-explanatory; if you do not find them so, please report this as a bug. " If I run with --verbose, I get [root@host-10-0-132-192 ~]# alternatives --set python /usr/bin/python2 --verbose reading /var/lib/alternatives/python [root@host-10-0-132-192 ~]# ls /var/lib/alternatives/python ls: cannot access /var/lib/alternatives/python: No such file or directory I can fix this by issuing /usr/sbin/alternatives --install /usr/bin/python python /usr/bin/python2 1 Version-Release number of selected component (if applicable): [root@host-10-0-132-192 ~]# alternatives --version alternatives version 1.7.4 How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: