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:
As per customer example - rc scripts (.profile, .bashrc) which doesn't conform to POSIX mode causes issues (i.e. while using tigervnc)
According to the bash manual, names should contain letters, digits and underscores only.
However there are files commonly used inside .bashrc that do not conform to POSIX mode.
The following script use hyphens in function names:
in /etc/bash_completion.d/: rhn-migrate-classic-to-rhsm rhsm-debug rhsm-icon
Version-Release number of selected component (if applicable):
subscription-manager-1.15.9-15.el7.x86_64
Steps to Reproduce:
1. $ bash --posix
2. $ . /etc/profile.d/bash_completion.sh
Actual results:
bash: `_rhn-migrate-classic-to-rhsm': not a valid identifier
bash: `_rhsm-debug': not a valid identifier
bash: `_rhsm-icon': not a valid identifier
Expected results:
no errors
Reproducing the failure :
========================
[root@dhcp35-154 ~]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.3 (Maipo)
[root@dhcp35-154 ~]# rpm -qa subscription-manager*
subscription-manager-1.17.15-1.el7.x86_64
subscription-manager-gui-1.17.15-1.el7.x86_64
subscription-manager-initial-setup-addon-1.17.15-1.el7.x86_64
[root@dhcp35-154 ~]# bash --posix
bash-4.2# source /etc/profile.d/bash_completion.sh
bash: `_itweb-settings': not a valid identifier
bash: `_rhn-migrate-classic-to-rhsm': not a valid identifier
bash: `_rhsm-debug': not a valid identifier
bash: `_rhsm-icon': not a valid identifier
bash-4.2#
bash-4.2# exit
exit
Verifying on latest subscription-manager :
==========================================
[root@dhcp151-206 ~]# subscription-manager version
subscription management server: 0.9.51.24-1
subscription management rules: 5.15.1
subscription-manager: 1.19.16-1.el7
python-rhsm: 1.19.7-1.el7
[root@dhcp151-206 ~]# rpm -qa subscription-manager --changelog | grep 1450049
- 1450049: Replace `-` with `_` in completion functions (khowell)
[root@dhcp151-206 ~]# bash --posix
bash-4.2# source /etc/profile.d/bash_completion.sh
bash: `_itweb-settings': not a valid identifier
bash-4.2#
^^ Observed that error from "rhn-migrate-classic-to-rhsm" , "rhsm-debug" and "rhsm-icon" NO longer appear. The "itweb-settings" failure is tracked under a different bug 1450046 . Hence moving this bug to "verified" as the subscription-manager component related issues are now fixed.
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/RHBA-2017:2083