Red Hat Bugzilla – Bug 904044
rhev-h still prompt that "Please input CA/URL" after configure "Satellite" without CA/URL and then configure "RHN"
Last modified: 2014-01-21 14:20:13 EST
Description of problem: rhev-h still prompt that "Please input CA/URL" after configure "Satellite" without CA/URL and then configure "RHN". Version-Release number of selected component (if applicable): rhev-hypervisor6-6.4-20130116.3.0.el6 How reproducible: 100% Steps to Reproduce: 1. Install RHEV-H and configure network. 2. Configure "Satellite" ,don't input CA/URL info, and click "Apply" Button. 3. Then configure Public RHN, click "Apply" Button. Actual results: After step 2, it will prompt that "Invalid RHN URL entered.Please input a CA certificate URL", it's expected behavior. But after step 3, it still prompt that "Invalid RHN URL entered.Please input a CA certificate URL", this wasn't expected behavior to user. Expected results: rhev-h shouldn't prompt that "Please input CA/URL after configure "Satellite" without CA/URL and then configure "RHN" Additional info: --
http://gerrit.ovirt.org/#/c/11452/ Tested as follows: 1. Apply patch 2. Go to RHN page 3. Select satellite and leave URL+CA fields empty and hit apply 4. "Configuration Check"-Dialog with "Invalid RHN URL entered" and "PLease input a CA certificate URL" appears, hit OK 5. (Don't change pages) Select RHN and hit apply 6. "RHN Configuration"-Dialog with "Login/Password must not be empty appears"
Test version: rhev-hypervisor6-6.5-20131017.0.iso ovirt-node-3.0.1-4.el6 Met missed to provide confirm dialog to check "RHN URL/CA URL" is an empty or not in rhev-hypervisor6-6.5-20131017.0.iso, so i report another Bug 1022508 to track this issue, need to waiting Bug 1022508 fixed to verify this bug
Test version: ovirt-node-3.0.1-9.el6_5.noarch.rpm rhevh-6.5-20131213.0.0.iso With redesign setup page for rhevh 6.5, this bug couldn't reproduce again. so change it into "VERIFIED"
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0033.html