1) Need a freshly installed satellite with NO channels or kickstart trees synced 2) Login to the webui 3) "Manage Kickstarts" 4) create new kickstart profile 5) notice 500 error. Should see: "No Kickstartable Channels found." "No trees were found for the selected channel"
NOTE: Even with channels synced it still blows up. So, this bug is basically stating that the profile creation page is non functional on a satellite.
Upgrading to this RPM or greater will contains the fix for this issue: rhn-java-4.1.0-583.noarch.rpm rhn-java-config-4.1.0-583.noarch.rpm rhn-java-lib-4.1.0-583.noarch.rpm taskomatic-4.1.0-583.noarch.rpm
RPMs can be found here: wget http://vault.rhndev.redhat.com/repo/repository/rhn-java/taskomatic-4.1.0-583.noarch.rpm wget http://vault.rhndev.redhat.com/repo/repository/rhn-java/rhn-java-4.1.0-583.noarch.rpm wget http://vault.rhndev.redhat.com/repo/repository/rhn-java/rhn-java-libs-4.1.0-583.noarch.rpm wget http://vault.rhndev.redhat.com/repo/repository/rhn-java/rhn-java-lib-4.1.0-583.noarch.rpm wget http://vault.rhndev.redhat.com/repo/repository/rhn-java/rhn-java-config-4.1.0-583.noarch.rpm
rhn-java-libs IS NOT a valid pkg so ignore that one, get the other 4.
mass move to ON_QA
moving from ON_DEV to ON_QA
retested on sat with: [root@fjs-0-06 ~]# rpm -q taskomatic rhn-java rhn-java-lib rhn-java-config taskomatic-4.1.0-608 rhn-java-4.1.0-608 rhn-java-lib-4.1.0-608 rhn-java-config-4.1.0-608
what? it's 500-ing again. I just tested it. My sat has two base and three child channels synced: 13:38:47 p rhel-i386-as-4 2867 13:38:48 p rhel-ia64-as-4 3165 13:38:48 p redhat-rhn-proxy-4.1-as-i386-4 109 13:38:48 p rhn-tools-rhel-4-as-i386 656 13:38:48 p rhn-tools-rhel-4-as-ia64 596 And two external distributions created: rhel-4-gold-as-i386-ext: Red Hat Enterprise Linux AS (v. 4 for 32-bit x86) auto-kickstart-ks-rhel-i386-as-4 rhel-4-u3-as-i386: Red Hat Enterprise Linux AS (v. 4 for 32-bit x86) auto-kickstart-ks-rhel-i386-as-4-u3 And I'm trying to create a profile called "ks-rhel-4-gold-as-i386-ext" using "rhel-4-gold-as-i386- ext". ... aw geez. Now I see what the problem is. I already have a profile by that name. I'll create a new bug for this.
There is already an existing bug for the issue in Comment #8: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=192883
moving to closed - currentrelease