Description of problem: Auto install RHEV-H, after system install successful, login to RHEV-H, navigate to RHN Registration page, the registration status is RHN. The RHN Registration page should not show the system already registered, we do not add the RHN registration related parameters during auto install. Version-Release number of selected component (if applicable): rhev-hypervisor7-7.2-20151112.1.iso ovirt-node-3.6.0-0.20.20151103git3d3779a.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1. Auto install rhevh with the parameters: BOOTIF=eth0 storage_init=/dev/vda adminpw=prfqPTTTRUVLc firstboot Actual results: After step1, on RHN Registration page the "Registration Status" is RHN. Expected results: After step1, on RHN Registration page the message should be "RHN Registration is required only if you wish to use Red Hat Enterprise Linux ..." Additional info: [root@localhost ~]# cat /var/log/messages | grep storage_init Nov 17 06:23:52 dhcp-10-150 kernel: Command line: initrd=initrd0.img root=live:CDLABEL=rhev-hypervisor7-7.2-20151112.1 rootfstype=auto ro rd.live.image rd.live.check crashkernel=256M rd_NO_MULTIPATH rootflags=ro elevator=deadline install quiet max_loop=256 rhgb rd.luks=0 rd.md=0 rd.dm=0 BOOTIF=eth0 storage_init=/dev/vda adminpw=prfqPTTTRUVLc firstboot BOOT_IMAGE=vmlinuz0 [root@localhost ~]# subscription-manager status +-------------------------------------------+ System Status Details +-------------------------------------------+ Overall Status: Unknown [root@localhost ~]# subscription-manager list +-------------------------------------------+ Installed Product Status +-------------------------------------------+ Product Name: Red Hat Enterprise Virtualization Product ID: 150 Version: 3.6 Arch: x86_64 Status: Unknown Status Details: Starts: Ends:
Created attachment 1095230 [details] RHN page screenshot
Created attachment 1095231 [details] /var/log
Is the TUI only showing that the system is registered or was the system really registered?
It's a cosmetic issue. The system is not registered. *** This bug has been marked as a duplicate of bug 1280215 ***