Hide Forgot
Description of problem: When registering a system with arch A to channel with arch B, the system is registered to the default channel instead. rhnreg_ks does not complain and returns 0. When there is no default channel, a message "This system is not subscribed to any channels. RHN channel support will be disabled." is displayed which seems correct. Return value is still 0. How reproducible: Deterministic Steps to Reproduce: A <-s390x B <- x86_64 1. Have a s390x machine 2. Have a Satellite with default channel for that machine synced and another x86_64 channel 3. Have an activation key with the x86_64 channel set as base channel 4. rhnreg_ks --serverUrl=... --activationkey=<key_id> --force Actual results: System is silently registered to the s390x default channel. Expected results: If system with arch A can not be registered to channel with arch B, rhnreg_ks should show warn the user.
Reproduced on 5.6 and 5.7
We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog. This is a low priority bug and has no currently open customer cases. While this bug may still valid, we do not see it being implemented prior to the EOL of the Satellite 5.x product. As such, this is being CLOSED DEFERRED. Closing now to help set customer expectations as early as possible. You are welcome to re-open this bug if needed.