Description of problem: We created a kickstart profile using the Red Hat Enterprise Linux WS (v. 3 for AMD64/Intel EM64T) (ks-rhel-x86_64-ws-3) distribution. This is, in essence, U2. However we cannot kickstart using that distro. Version-Release number of selected component (if applicable): 3.7.1 How reproducible: Always. Steps to Reproduce: 1. Create a kickstart profile using ks-rhel-x86_64-ws-3 2. Kickstart a machine using that profile Actual results: ERROR: Could not find the needed RHN provisioning packages given this system's current base channel and desired target channel. Expected results: Successful kickstart
I think this is jconnor's - Looking at the data in webdev, it looks like the tree in question (label: ks-rhel-x86_64-ws-3) has a 'boot_image' of 'ks-rhel-x86_64-ws-3'. We don't have such a package, but we do have: auto-kickstart-ks-rhel-x86_64-ws-3-u2 auto-kickstart-ks-rhel-x86_64-ws-3-u3 auto-kickstart-ks-rhel-x86_64-ws-3-u4 So I guess the 'plain' distrubution needs to go away and be replaced by one for u2. Same goes for AS and ES, of course.
The missing trees have been added to WEBQA
test plan: Kick an x86_64 box to rhel 3 u 2 (as, es, ws)
rhel 3 U2 kickstarts are failing for some reason, anaconda can't find the scsi hard drive this is the error: VFS: Can't find ext2 filesystem on dev loop(7,0) I was testing on mspevack64.rdu.redhat.com.
Beth, you'll need to open a bug against anaconda. This bug is currently aligned to RHN/kickstart.
I'm setting the bug into NEEDINFO until we can resume testing after fixing anaconda.
See 165162.
In that case, we're back to comment #4 - moving to ON_QA
in process of testing now.
x86_64 rhel-3-u2-ws kickstart works out of webqa. PROD_READY