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.

Bug 718779

Summary: perl-Net-Telnet is part of HA rhel-x86_64-server-ha-6
Product: Red Hat Enterprise Linux 6 Reporter: Tryggvi Farestveit <tryggvi>
Component: perl-Net-TelnetAssignee: Fabio Massimo Di Nitto <fdinitto>
Status: CLOSED DUPLICATE QA Contact: qe-baseos-daemons
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1CC: ddumas, jwest, lhh, mgrac, ssaha, tommi
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-08 12:52:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tryggvi Farestveit 2011-07-04 15:09:46 UTC
Description of problem:
The package perl-Net-Telnet is part of HA channel. This a generic package needed for non HA stuff. I think it should not be part of the HA channel but the base or optional channel.

Comment 6 RHEL Program Management 2011-07-06 01:38:09 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 7 Tomas Edwardsson 2011-07-06 10:45:22 UTC
Can you please elaborate on what this means? Will it be included in the 6.2 release or how are you planning to procede?

Comment 8 Perry Myers 2011-07-06 12:45:21 UTC
perl-Net-Telnet at the present time and for the next minor release of RHEL 6 (RHEL 6.2) will only be included as part of the RHEL High Availability Add On and RHEL Resilient Storage Add Ons. There are no plans at present to move this package into the RHEL 6 base product repositories.  

The only package in RHEL that requires perl-Net-Telnet is fence-agents, and since fence-agents is only present in the HA and RS Add Ons, that is the reason why perl-Net-Telnet is only in these Add Ons repositories.

Comment 9 Tryggvi Farestveit 2011-07-06 12:58:06 UTC
What about your customers that need perl-Net-Telnet and not HA? You are forcing them to purchase the HA addon just for perl-Net-Telnet.

Comment 16 Jeremy West 2011-08-08 12:52:06 UTC
Marking this as a dup of BZ 715541, with the intent of requesting that this package be moved into the the "optional" channel and out of the HA channel.

*** This bug has been marked as a duplicate of bug 715541 ***