Bug 221177 against firstboot has a patch attached to it that modifies the flow from page to page. When testing this on RHEL, this patch breaks the first screen of the rhn-setup package. On this screen, if you do not have RHN enabled (lack of network, no key entered in anaconda, etc.) it displays an error message and then sets the page to the last one of the RHN set. This makes sense. However with the modifications to firstboot for fixing 221177, this will no longer work. The call to setPage in rhn_start_gui.py will skip to the last RHN page like it should, but then firstboot will move to the next page anyway. In this case, the next page will be the second RHN one. From there, everything gets very confused. What I'm proposing to do to fix this is to modify setPage to add a named parameter indicating that a module is requesting to skip ahead, instead of the usual page flow taking place. This will require a modification to rhn_start_gui.py but I believe it will be a very simple one. Would it be possible to make this sort of modification to the RHN firstboot module for 5.1?
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
James - Can you comment on this bug?
we ought to be able to fix this for 5.1.
Okay I've narrowed the offending patch in firstboot down a little bit and I no longer think changes to RHN will be required. Besides, it's getting too late to really do anything here. Closing.