Bug 683631

Summary: [STRATUS 6.1 Bug] xmlrpc3-server is missing from server ISO
Product: Red Hat Enterprise Linux 6 Reporter: Jim Paradis <jparadis>
Component: distributionAssignee: Dennis Gregorovic <dgregor>
Status: CLOSED DUPLICATE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.1CC: chas.horvath, kevin.paetzold, peterm, robert.evans, syeghiay
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-11 19:38:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jim Paradis 2011-03-09 21:47:06 UTC
Description of problem:

Stratus requires xmlrpc3-server to support our system.  This is missing from the RHEL6.1-Server ISO.  While this does not affect factory installs, this makes it difficult for customers to install our product


Steps to Reproduce:
1. Install RHEL6 on a Stratus server
2. Attempt to install ftLinux on top of this
  
Actual results:
Installer complains about missing xmlrpc3-server RPM.  RPM not available on install DVD, need to pull down from RHN or other repositoy

Expected results:
ftLinux install succeeds.

We believe that xmlrpc3-server should at minimum be included in the RHEL6-Server ISO image.

Comment 2 RHEL Program Management 2011-03-09 22:17:40 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 5 Jim Paradis 2011-03-11 19:38:53 UTC

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