Red Hat Bugzilla – Bug 28285
Update failed due to invalid configuration
Last modified: 2015-01-07 18:43:39 EST
With existing Redhat Network setup on Redhat 7.0 machine after upgrading to fisher I tried to use up2date to test the functionality. The program aborted with an error about an invalid configuration. I removed the configuration and allowed the new version (the one with fisher I presume) to create a new entry it's self and the program functioned correctly.
This is expected behaviour. The beta releases point to a different set of up2date servers than the standard release, and the servers that 7.0 points at do not support up2date services for the beta. The beta version of up2date only supports anonymous registration, and includes none of the RHN web functionality. Sounds like you had registered with the main servers, then tried to use your certificate you got from there with the beta servers, which doesnt work.
This was very minor for me but for someone new to Linux or computers in general this could be quite a problem. Several people around this area if they encounter this will end up calling me to ask how to fix the ('CRASH' as they usually put it often without enough information to find the bug). Would it be possible for the upgrade program to simply remove the /etc/sysconfig/rhn/systemid file?
It doesnt need to for real releases, but the beta is different. The same server and system_id will work for the "live" servers and all the versions supported on it. This is only an issue on beta releases, which are of course, unsupported. I'll see what it would take for the servers to return a more informative error message that will point this out.
Assigned QA to jturner
this will never happen except in the beta case. If you are using the beta, you are expected to have to be a little smarter than the average new user.