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.
Pexpect is available in High Availability repository. Server repository itself doesn't contain it.
Closing bug as NOTABUG, because pexpect should be used only by fence-agents package.
I'm changing component to distribution, because bug is not in pexpect but in distribution.
Main problem seems to be, that pexpect is only used by fence-agents package and this is why it is only in HA. yumex is not supported in RHEL, but there may be chance to use it on server by customers.
As a frequent python coder, I think pexpect should pretty certainly be included in the server repository. Of course this is only my opinion. What are the criteria for inclusion other than direct requirement by something else that is included?
There seems to be an pexpect-2.3-6.el6.noarch.rpm on the RHEL6-Server-Install-CD, however it is not found in RHN?
Comment 16Dennis Gregorovic
2011-01-14 19:33:08 UTC
(In reply to comment #15)
> There seems to be an pexpect-2.3-6.el6.noarch.rpm on the
> RHEL6-Server-Install-CD, however it is not found in RHN?
It's in RHN, but not in the base channel. In RHEL 6.0, pexpect is only available through the High Availability channel. The goal of this package is to move the package into the base channel.
Comment 19Alexander Todorov
2011-02-07 12:38:28 UTC
# pwd
/mnt/redhat/nightly/RHEL6.1-20110206.n.0/6
# find -name "pexpect*" | sort
./Client/optional/i386/os/Packages/pexpect-2.3-6.el6.noarch.rpm
./Client/optional/source/SRPMS/pexpect-2.3-6.el6.src.rpm
./Client/optional/x86_64/os/Packages/pexpect-2.3-6.el6.noarch.rpm
./ComputeNode/optional/source/SRPMS/pexpect-2.3-6.el6.src.rpm
./ComputeNode/optional/x86_64/os/Packages/pexpect-2.3-6.el6.noarch.rpm
./Server/i386/os/Packages/pexpect-2.3-6.el6.noarch.rpm
./Server/i386/os/Server/Packages/pexpect-2.3-6.el6.noarch.rpm
./Server/optional/source/SRPMS/pexpect-2.3-6.el6.src.rpm
./Server/source/SRPMS/pexpect-2.3-6.el6.src.rpm
./Server/x86_64/os/Packages/pexpect-2.3-6.el6.noarch.rpm
./Server/x86_64/os/Server/Packages/pexpect-2.3-6.el6.noarch.rpm
./source/SRPMS/pexpect-2.3-6.el6.src.rpm
./Workstation/i386/os/Packages/pexpect-2.3-6.el6.noarch.rpm
./Workstation/i386/os/Workstation/Packages/pexpect-2.3-6.el6.noarch.rpm
./Workstation/optional/source/SRPMS/pexpect-2.3-6.el6.src.rpm
./Workstation/source/SRPMS/pexpect-2.3-6.el6.src.rpm
./Workstation/x86_64/os/Packages/pexpect-2.3-6.el6.noarch.rpm
./Workstation/x86_64/os/Workstation/Packages/pexpect-2.3-6.el6.noarch.rpm
For Server and Workstation variants pexpect is on the system-admin-tools group in comps.xml. For the other variants it is in the optional repo. Moving to VERIFIED.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHEA-2011-0540.html