We need to be able to support associating 1 or more redhat-release version release pairs with a channel for EUS. rhel 4.5 may have 2 versions of redhat release during its lifetime, and rhel 4.6 must know about the rhel 4.6 redhat-release, as well as the 4.5 redhat-release (for providing zstream channel choices to the client).
It would be worth checking if we can do this via some logic in the application, rather than by adding more data to juggle around
Updating the bug summary to reflect our current thoughts on fixing
Problem: RHEL EUS {5.1.z and 5.2.z} do not appear on base software channel page of RHN. [Current workaround] In order to visible the "5.2.z", a targeted system's base channel once has to take off, so choose "NONE" first. After the base channel has been "NONE", all channels (None, RHEL (non EUS), and RHEL 5.{1,2,3}.z) will be appeared in a drop down menu and being possible to assign.
Verified in webdev.
# VERIFIED version: 20090625.0 All the scenarios described in Comment#4 are checked and fine on webqa. The point with selecting EUS while registering through rhn_register is working and after it's still possible to return to the Base channel (it's available if you first choose "NONE" and then return to Base RHEL5 channel).
Verified in webqa.
Fujitsu requires that select any of base channel RHEL EUS {5.1.z, 5.2.z and 5.3.z} directly from standard base channel without assigned "NONE" first. It seems still All RHEL EUS {5.1.z, 5.2.z and 5.3.z} do not appeared at once when a standard base channel is assigned. Please review and solve this problem thanks.
Setting bug back to Closed CurrentRelease. Eiji, it is not possible to go backwards for EUS as it would break updates.