| Summary: | [RHEVM-SETUP] - Remote db user is incorrectly configured in setup | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Barak Dagan <bdagan> | ||||
| Component: | ovirt-engine-setup | Assignee: | Ofer Schreiber <oschreib> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jiri Belka <jbelka> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.2.0 | CC: | aberezin, acathrow, bazulay, iheim, jbelka, oschreib, pstehlik, Rhev-m-bugs, sbonazzo, talayan, yeylon | ||||
| Target Milestone: | --- | Keywords: | TestOnly, Triaged | ||||
| Target Release: | 3.2.6 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | integration | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-02-09 23:30:39 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
Barak, what is the BZ# for the fix in 3.3 so we could clone it? (In reply to Arthur Berezin from comment #3) > Barak, what is the BZ# for the fix in 3.3 so we could clone it? Arthur, I'm not sure that the is on for 3.3. 3.3 setup was refactored using otopi, that issue might be fixed then. I find that issue in 3.2 while preparing some remote enviourments. If it is worth fixing in that version, I need 3.2.z flag set, as I don't such permissions. Setting 3.2.z flag, targeting to 3.2.6. It works on 3.3.0 so no code change, TestOnly on 3.3.0 (In reply to Barak Dagan from comment #0) > Created attachment 826662 [details] > engine-setup_2013_11_19_20_05_37.log > > Description of problem: > dwh setup asked for remote user, but accept only the default postgres user: > > Enter the host IP or host name where RHEV Manager DB is running: > fire32-remdb.scl.lab.tlv.redhat.com > Enter the DB port number [5432] : > Enter the remote DB user name [postgres] : engine > Enter the password for the remote DB user : > Warning: Weak Password. > Confirm password : > Configure a secure connection? (make sure SSL is configured on the remote DB > server) ['yes'| 'no'] [no] : no > > Couldn't create temp database on server fire32-remdb.scl.lab.tlv.redhat.com. > Check provided credentials. > > > Entering a remote RHEV Manager DB configuration section. All the > configuration parameters should be provided by the remote DB administrator. > Enter the host IP or host name where RHEV Manager DB is running: > fire32-remdb.scl.lab.tlv.redhat.com > Enter the DB port number [5432] : > Enter the remote DB user name [postgres] : > Enter the password for the remote DB user : > Warning: Weak Password. > Confirm password : > Configure a secure connection? (make sure SSL is configured on the remote DB > server) ['yes'| 'no'] [no] : > Configure NFS share on this server to be used as an ISO Domain? ['yes'| > 'no'] [yes] : > > Version-Release number of selected component (if applicable): > 3.2.4, sf21.1 > > How reproducible: > 100% > > Steps to Reproduce: > 1. prepare remote db vm > 2. create new role in db (engine): > psql -U postgres -c "create user engine password 'engine';" > 3. try to use that user in dwh-setup > > Actual results: > userfails. only postgres user can be used after altering that user with a > new password (postgres) > > Expected results: > use the user entered > > Additional info: This BZ was opened in front of engine-setup installation on 3.2 . The dwh-setup was mentioned by mistake what to test here? The Bug is about using non postgres role for engine setup - on remote db. Currently - in 3.2, the setup asks for remote user, having postgres as default answer, and fails if that user is not postgres. The steps to reproduce are to create another role on the remote db server, and use it's credentials during setup. ok, rhevm-setup-3.3.0-0.46.el6ev.noarch. Tested with remote DB - testengine/testengine. this was fixed for 3.3. |
Created attachment 826662 [details] engine-setup_2013_11_19_20_05_37.log Description of problem: dwh setup asked for remote user, but accept only the default postgres user: Enter the host IP or host name where RHEV Manager DB is running: fire32-remdb.scl.lab.tlv.redhat.com Enter the DB port number [5432] : Enter the remote DB user name [postgres] : engine Enter the password for the remote DB user : Warning: Weak Password. Confirm password : Configure a secure connection? (make sure SSL is configured on the remote DB server) ['yes'| 'no'] [no] : no Couldn't create temp database on server fire32-remdb.scl.lab.tlv.redhat.com. Check provided credentials. Entering a remote RHEV Manager DB configuration section. All the configuration parameters should be provided by the remote DB administrator. Enter the host IP or host name where RHEV Manager DB is running: fire32-remdb.scl.lab.tlv.redhat.com Enter the DB port number [5432] : Enter the remote DB user name [postgres] : Enter the password for the remote DB user : Warning: Weak Password. Confirm password : Configure a secure connection? (make sure SSL is configured on the remote DB server) ['yes'| 'no'] [no] : Configure NFS share on this server to be used as an ISO Domain? ['yes'| 'no'] [yes] : Version-Release number of selected component (if applicable): 3.2.4, sf21.1 How reproducible: 100% Steps to Reproduce: 1. prepare remote db vm 2. create new role in db (engine): psql -U postgres -c "create user engine password 'engine';" 3. try to use that user in dwh-setup Actual results: userfails. only postgres user can be used after altering that user with a new password (postgres) Expected results: use the user entered Additional info: