Timothy, just to give a bit more details: dialog.queryBoolean is a function to ask the user a Yes/No question. There were two places that called instead a non-existent self.dialog.queryBoolean. This caused an error message if the execution reached these places in the code. These two places were: 1. Code checking for existing async tasks (and similar). 2. Code checking for database inconsistencies. If such were found during setup (upgrade), user is prompted asking whether to try and fix (or abort setup). So a potential doc text might be something like: During setup/upgrade, fixed failures while prompting the user whether to stop async tasks or to fix database inconsistencies.
I've tried upgrading from 3.3 to 3.4 (rhevm-setup-3.4.1-0.25.el6ev) with engine stopped in the middle of template creation. The upgrade succeeded, there is no error about missing queryBoolean attribute in the setup log, but the template creation task seems to be stuck and the VM disk locked. Should I consider this as a problem of this patch or a separate issue?
(In reply to Petr Beňas from comment #3) > I've tried upgrading from 3.3 to 3.4 (rhevm-setup-3.4.1-0.25.el6ev) with > engine stopped in the middle of template creation. The upgrade succeeded, > there is no error about missing queryBoolean attribute in the setup log, but > the template creation task seems to be stuck and the VM disk locked. Should > I consider this as a problem of this patch or a separate issue? I think this is a separate issue.
OK, setting Verified then.
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-0960.html