Created attachment 628064[details]
screenshot
Description of problem:
If the rhevm server cannot be resolved, apply it will try compatible port 443 or 8443, and after tried it several times, an exception about /etc/pki/vdsm/certs/cacert.pem cannot be found will occur.
Version-Release number of selected component (if applicable):
RHEV-Hypervisor 6.3-20121015.0.rhev31.el6_3
RHEV Hypervisor 6.3-20121005.0.rhev31.el6_3
How reproducible:
100%
Steps to Reproduce:
1. Configure network and go to RHEV-M.
2. Enter the rhevm server hostname which cannot be resolved.
Actual results:
it will try compatible port 443 or 8443, and after several times try, exception about /etc/pki/vdsm/certs/cacert.pem cannot be found occurrs.
Expected results:
If the rhevm hostname cannot be resolved, it should prompt "the hostname cannot be resolved" instead try compatible port 443 or 8443, and no exception occurs after try more times.
Created attachment 628064 [details] screenshot Description of problem: If the rhevm server cannot be resolved, apply it will try compatible port 443 or 8443, and after tried it several times, an exception about /etc/pki/vdsm/certs/cacert.pem cannot be found will occur. Version-Release number of selected component (if applicable): RHEV-Hypervisor 6.3-20121015.0.rhev31.el6_3 RHEV Hypervisor 6.3-20121005.0.rhev31.el6_3 How reproducible: 100% Steps to Reproduce: 1. Configure network and go to RHEV-M. 2. Enter the rhevm server hostname which cannot be resolved. Actual results: it will try compatible port 443 or 8443, and after several times try, exception about /etc/pki/vdsm/certs/cacert.pem cannot be found occurrs. Expected results: If the rhevm hostname cannot be resolved, it should prompt "the hostname cannot be resolved" instead try compatible port 443 or 8443, and no exception occurs after try more times.