Red Hat Bugzilla – Bug 1008562
[RHEVM-DWH-SETUP] - upgrade fails due to wrong user value in updatePgHba
Last modified: 2014-01-21 09:59:56 EST
Created attachment 798315 [details]
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):
Steps to Reproduce:
1.clean installation of dwh on an "old" rhevm
2.clean installation of reports
3. 2nd installation (upgrade) of dwh
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
What was the original version of rhevm that was installed?
rhevm was upgared few times during version progress.
DHW + reports installed for the first time.
Exception was thrown during dwh second installation (upgrade).
Verified on IS21:
Updated from is20.1 to is21 successfully
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:
Thanks in advance.
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.