Bug 1027894

Verification failed on IS23, rhevm-dwh-3.3.0-21.el6ev.noarch:

Step 1:
======
# rhevm-dwh-setup 
Welcome to ovirt-engine-dwh setup utility


This utility can configure a read only user for DB access. Would you like to do so? (yes|no): yes
Provide a username for read-only user : rro
Provide a password for read-only user: 
Warning: Weak Password.
Re-type password: 
Should postgresql be setup with secure connection? (yes|no): no
Creating DB...                                        [ DONE ]
Creating read-only user...^C Error encountered while installing rhevm-dwh, please consult the log file: /var/log/ovirt-engine/rhevm-dwh-setup-2013_11_15_01_00_59.log

Step 2:
======
# rhevm-dwh-setup 
Welcome to ovirt-engine-dwh setup utility


This utility can configure a read only user for DB access. Would you like to do so? (yes|no): yes
Provide a username for read-only user : rro
Provide a password for read-only user: 
Warning: Weak Password.
Re-type password: 
Should postgresql be setup with secure connection? (yes|no): no

Existing DB was found on the system. The size of the detected DB is 19 MB, free space in the backup folder /var/lib/ovirt-engine/backups is approximately 6.0 GB. 
...

Answering "no" will skip the backup step and continue the upgrade without backing up the database (yes|no): no
Are you sure you would like to continue and SKIP the backup of the database ovirt_engine_history?
Answering "no" will stop the upgrade (yes|no): yes
Upgrade DB...                                         [ DONE ]
Creating read-only user...                            [ ERROR ]
Error encountered while installing rhevm-dwh, please consult the log file: /var/log/ovirt-engine/rhevm-dwh-setup-2013_11_15_01_01_39.log


step 3 (https://access.redhat.com/site/solutions/291973):
======
A) yum remove rhevm-dwh
....
  Erasing    :rhevmreports-.3.0-20.el6ev.noarch
  Erasing    : rhevm-dwh-3.3.0-21.el6ev.noarch

B) #dropdb -U postgres ovirt_engine_history
dropdb: could not connect to database postgres: FATAL:  Ident authentication failed for user "postgres"

using (https://bugzilla.redhat.com/show_bug.cgi?id=1027378) solution:
su postgres -c 'dropdb ovirt_engine_history'
su postgres -c 'psql -l'
                                   List of databases
    Name     |  Owner   | Encoding |  Collation  |    Ctype    |   Access privileges   
-------------+----------+----------+-------------+-------------+-----------------------
 engine      | engine   | UTF8     | en_US.UTF-8 | en_US.UTF-8 | 
 engine_test | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | 
 postgres    | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | 
 template0   | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/postgres
                                                               : postgres=CTc/postgres
 template1   | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/postgres
                                                               : postgres=CTc/postgres
(5 rows)

C) #yum install rhevm-reports rhevm-dwh
Installed:  rhevm-dwh.noarch 0:3.3.0-21.el6ev   
            rhevm-reports.noarch 0:3.3.0-20.el6ev


step 4:
======
# rhevm-dwh-setup 
Welcome to ovirt-engine-dwh setup utility


This utility can configure a read only user for DB access. Would you like to do so? (yes|no): yes
Provide a username for read-only user : rro
Provide a password for read-only user: 
Warning: Weak Password.
Re-type password: 
Should postgresql be setup with secure connection? (yes|no): no
Error encountered while installing rhevm-dwh, please consult the log file: /var/log/ovirt-engine/rhevm-dwh-setup-2013_11_15_01_19_33.log

Created attachment 824141 [details]
dwh setup logs

We need to update the KB for this case.

The addition should be:

After removing ovirt_engine_history DB, also remove the 'engine_history' user by executing:

su postgres -c "psql \"drop role engine_history;\""

Yaniv, who should we move this to?

Bryan, can you please update the kbase for 3.3 setup. See comment #5. 
https://access.redhat.com/site/solutions/291973

You can close the bug after this is done.


Thanks!
Yaniv

(In reply to Yaniv Dary from comment #6)
> Bryan, can you please update the kbase for 3.3 setup. See comment #5. 
> https://access.redhat.com/site/solutions/291973
> 
> You can close the bug after this is done.
> 
> 
> Thanks!
> Yaniv

Yaniv, I have updated the kbase. I added what I assumed the step was for RHEV 3.0 as well. Let me know if "step 3" looks correct for both RHEV 3.0 and RHEV 3.1+?

(In reply to Bryan Yount from comment #7)
> (In reply to Yaniv Dary from comment #6)
> > Bryan, can you please update the kbase for 3.3 setup. See comment #5. 
> > https://access.redhat.com/site/solutions/291973
> > 
> > You can close the bug after this is done.
> > 
> > 
> > Thanks!
> > Yaniv
> 
> Yaniv, I have updated the kbase. I added what I assumed the step was for
> RHEV 3.0 as well. Let me know if "step 3" looks correct for both RHEV 3.0
> and RHEV 3.1+?

Don't make any changes other than in the 3.3 version.
This is not needed in pervious versions.


Yaniv

(In reply to Yaniv Dary from comment #8)
> Don't make any changes other than in the 3.3 version.
> This is not needed in pervious versions.

Ok, fixed. Double-check my work. Thanks! Closing BZ as requested.

This bug is currently attached to errata RHEA-2013:15116. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to 
minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 

Thanks in advance.