Kickstarting with multiple network interfaces prevents kickstart from completing

Solution Verified - Updated -

Environment

  • Red Hat Network Satellite or Proxy
    • 5.4.1
  • Kickstart
  • Seen on Dell R710

Issue

  • Build from Satellite gives missing package information inconsistently.

  • Uncertain if this is a Satellite issue or a Red Hat Enterprise Linux (RHEL) issue. In Satellite, channels were cloned to a RHEL 5 build as well as another set for RHEL 6 build. These were created from the RHEL synchronized channels. Both channels were provisioned successfully a number of times. However, on certain hosts provisioning fails and the following error is presented:

    libgomp-4.4.6-4.el6.x86_64.rpm cannot be opened. Missing file, corrupt package, or corrupt media
    
  • Every time a build is made on this particular Dell R710 machine, it dies in the same place on the libgomp package as it follows:

    libjpeg-6b-37.x86_64.rpm cannot be opened. Missing file, corrupt package, or corrupt media.
    

Resolution

Root Cause

During kickstart with two network interfaces cabled the network configuration is placed additionally on the non-pxe'd network interface and thus causes the network to fail.

Diagnostic Steps

  1. Since the same kickstart is running on other machines, it is not a corruption issue.
  2. One other important thing is to always make sure to check in on your db tablespace. Use the following command:

    su - oracle
    db-control report
    

    2.1. Keep it below 85-90% to be safe:

        db-control extend
    
  3. Check the md5sum of the file in question with one downloaded from rhn as shown from the second KCS article.

  4. Assuming it is a network issue the retry should work, assuming you get the drac tty working using ctrl+alt+<F#>, it will help to debug.
  5. Go through the RHEL 5 channel and clean up so it looks similar to the actual DVD.
  6. The NIC gets configured twice. At boot the p1p1, NIC gets configured and that is how it starts its build. Later, as it is prepping for install, the em2 (embedded/onboard) NIC gets configured with the same IP address so both stop responding.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.