- Red Hat Network Satellite or Proxy
- Seen on Dell R710
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
R710machine, it dies in the same place on the
libgomppackage as it follows:
libjpeg-6b-37.x86_64.rpm cannot be opened. Missing file, corrupt package, or corrupt media.
- The easier solution is to rerun the
satellite-syncon your channels and check
logfiles. More details on the Satellite based kickstart fails with "The file xyz.rpm cannot be opened. This is due to a missing file, a corrupted package or corrupted media" document.
- A more in-depth way to clean up is to do as described in the following article, RHEL6 network installation failing with error 'The file ncurses-base-5.7-3.20090208.el6.x86_64.rpm cannot be opened.
Another option is to modify the
ksdevice=variable as noted by one of the options below:
- Add the
MACaddress of the
- Use the "link" keyword to tell
kickstartto use the interface that has a link status of
- Use the
bootifkeyword to tell
kickstartto use the
ksdevice=bootif(for this to work you need
IPAPPEND 2in your
In order to prevent further issues, the following command can be run:
`ifconfig em2 down`
- Add the
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.
- Since the same
kickstartis running on other machines, it is not a corruption issue.
One other important thing is to always make sure to check in on your
dbtablespace. Use the following command:
su - oracle db-control report
2.1. Keep it below 85-90% to be safe:
md5sumof the file in question with one downloaded from
rhnas shown from the second KCS article.
- Assuming it is a network issue the retry should work, assuming you get the
drac ttyworking using
ctrl+alt+<F#>, it will help to
- Go through the RHEL 5 channel and clean up so it looks similar to the actual
NICgets configured twice. At boot the
NICgets configured and that is how it starts its build. Later, as it is prepping for install, the
NICgets configured with the same
IPaddress 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.