Bug 505186 - Allow Installation of Cobbler on s390x
Summary: Allow Installation of Cobbler on s390x
Keywords:
Status: CLOSED DUPLICATE of bug 580072
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Provisioning
Version: 530
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Mike McCune
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: 462714
TreeView+ depends on / blocked
 
Reported: 2009-06-10 22:12 UTC by Devan Goodwin
Modified: 2010-08-26 08:55 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-08-26 08:55:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Devan Goodwin 2009-06-10 22:12:59 UTC
Description of problem:

Cobbler as of 1.6.5 has a requirement on the syslinux package, but only for x86 and x86_64 architectures. On s390x, because of this missing requirement (which cannot be added as I understand the syslinux package does not exist on this arch) the Satellite installer prints the following warning:

* Update configuration in database.
* Setting up Cobbler..
Could not find files matching /usr/share/syslinux/pxelinux.0

* Restarting services.

We can't fix the bug originally reported in bug #505133, so we're filing this one to investigate either having it be silently ignored, or having it become an actual error that halts installation. (mdehaan recommends this as pxe provisioning will be broken until syslinux is manually installed)


Version-Release number of selected component (if applicable):

Satellite-5.3.0-RHEL5-re20090605.1, cobbler 1.6.5.

How reproducible:

Seems to be 100% on s390x.

Steps to Reproduce:
1. Begin install.pl on s390x RHEL 5 system.
  
Actual results:

Warning as displayed above.


Expected results:

TBD. :) Could be warning is suppressed, displayed differently, or treated as an error and installation halts.

Additional info:

mdehaan can probably clarify more on why the syslinux requires is removed for s390x, and also as noted above his opinion is that this should become a fatal error for the installer.

Comment 1 Brad Hinson 2010-08-26 08:55:52 UTC

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


Note You need to log in before you can comment on or make changes to this bug.