While configuring the Red Hat Storage Console to use a remote database server, on providing either 'yes/no' as input for 'Database host name validation' parameter, it is considered as 'No'.
Created attachment 854393[details]
setup answer file
Description of problem:
------------------------
While configuring the RHSC to use a remote database server, on saying 'yes' to the 'database secured connection' question, as follows -
Database host [localhost]: 10.70.37.100
Database port [5432]:
Database secured connection (Yes, No) [No]: yes
Validate host name in secured connection (Yes, No) [Yes]:
Database name [engine]:
Database user [engine]: postgres
Database password:
the following is seen in the configuration preview -
--== CONFIGURATION PREVIEW ==--
Database name : engine
Database secured connection : True
Database host : 10.70.37.100
Database user name : postgres
Database host name validation : False
Datbase port : 5432
PKI organization : redhat
Application mode : gluster
Firewall manager : iptables
Update Firewall : True
Host FQDN : rhsc.cb15
Set application as default page : True
Configure Apache SSL : True
Note the 'Database host name validation : False'
This should have been true.
Version-Release number of selected component (if applicable):
rhsc-2.1.2-0.33.el6rhs.noarch
How reproducible:
Always
Steps to Reproduce:
1. Choose to use a remote database server for RHSC and answer the questions as
explained above.
2. See the configuration preview.
Actual results:
Database host name validation : False is seen.
Expected results:
The Database host name validation should be true.
Additional info:
Attached answer file generated by setup.
The parameter is not 'Database Secured Connection' instead its 'Database host name validation'. And for any input(yes/no) which user provides for this parameter. The system considers it as No. So it would be better if you modify doc_text to be something like this:
While configuring the Red Hat Storage Console to use a remote database server, on providing either 'yes/no' as input for 'Database host name validation' parameter, it is considered as 'No'.
Thank you for submitting this issue for consideration in Red Hat Gluster Storage. The release for which you requested us to review, is now End of Life. Please See https://access.redhat.com/support/policy/updates/rhs/
If you can reproduce this bug against a currently maintained version of Red Hat Gluster Storage, please feel free to file a new report against the current release.
Created attachment 854393 [details] setup answer file Description of problem: ------------------------ While configuring the RHSC to use a remote database server, on saying 'yes' to the 'database secured connection' question, as follows - Database host [localhost]: 10.70.37.100 Database port [5432]: Database secured connection (Yes, No) [No]: yes Validate host name in secured connection (Yes, No) [Yes]: Database name [engine]: Database user [engine]: postgres Database password: the following is seen in the configuration preview - --== CONFIGURATION PREVIEW ==-- Database name : engine Database secured connection : True Database host : 10.70.37.100 Database user name : postgres Database host name validation : False Datbase port : 5432 PKI organization : redhat Application mode : gluster Firewall manager : iptables Update Firewall : True Host FQDN : rhsc.cb15 Set application as default page : True Configure Apache SSL : True Note the 'Database host name validation : False' This should have been true. Version-Release number of selected component (if applicable): rhsc-2.1.2-0.33.el6rhs.noarch How reproducible: Always Steps to Reproduce: 1. Choose to use a remote database server for RHSC and answer the questions as explained above. 2. See the configuration preview. Actual results: Database host name validation : False is seen. Expected results: The Database host name validation should be true. Additional info: Attached answer file generated by setup.