Bug 1008562 - [RHEVM-DWH-SETUP] - upgrade fails due to wrong user value in updatePgHba
Summary: [RHEVM-DWH-SETUP] - upgrade fails due to wrong user value in updatePgHba
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-dwh
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.3.0
Assignee: Sandro Bonazzola
QA Contact: Barak Dagan
URL:
Whiteboard: integration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-16 15:20 UTC by Barak Dagan
Modified: 2014-01-21 14:59 UTC (History)
8 users (show)

Fixed In Version: rhevm-dwh-3.3.0-15.el6ev.noarch.rpm
Doc Type: Bug Fix
Doc Text:
Upgrading rhevm-dwh failed because a new user was created, ignoring the existing user, causing user and password mismatch. Now, a read-only user is created upon upgrade only if no user had been created previously.
Clone Of:
Environment:
Last Closed: 2014-01-21 14:59:56 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
setup log (2.73 KB, application/x-compressed-tar)
2013-09-16 15:20 UTC, Barak Dagan
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0036 0 normal SHIPPED_LIVE rhevm-dwh 3.3 bug fix and enhancement update 2014-01-21 19:53:35 UTC
oVirt gerrit 19747 0 None None None Never

Description Barak Dagan 2013-09-16 15:20:42 UTC
Created attachment 798315 [details]
setup log

Description of prhevm-dwh-setuproblem:
running rhevm-dwh-setup twice results a failure:

TypeError: 'in <string>' requires string as left operand, not NoneType


Version-Release number of selected component (if applicable):
is14 (rhevm-dwh-3.3.0-9.el6ev.noarch)

How reproducible:
100%

Steps to Reproduce:
1.clean installation of dwh on an "old" rhevm
2.clean installation of reports
3. 2nd installation (upgrade) of dwh

Actual results:
Error encountered while installing rhevm-dwh, please consult the log file: /var/log/ovirt-engine/rhevm-dwh-setup-2013_09_16_17_36_38.log

Expected results:


Additional info:

Comment 1 Yaniv Lavi 2013-09-16 17:55:15 UTC
What was the original version of rhevm that was installed?



Yaniv

Comment 2 Barak Dagan 2013-09-17 13:59:41 UTC
is14.
rhevm was upgared few times during version progress.
DHW + reports installed for the first time.
Exception was thrown during dwh second installation (upgrade).

Comment 4 Barak Dagan 2013-10-31 17:17:28 UTC
Verified on IS21:

jasperreports-server-pro-5.5.0-4.el6ev.noarch
rhevm-dwh-3.3.0-18.el6ev.noarch
rhevm-reports-3.3.0-18.el6ev.noarch


Updated from is20.1 to is21 successfully

Comment 5 Charlie 2013-11-28 00:53:52 UTC
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.

Comment 8 errata-xmlrpc 2014-01-21 14:59:56 UTC
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-0036.html


Note You need to log in before you can comment on or make changes to this bug.