Bug 1059318 - [RHEVM-SETUP] - wrong value saved in answer file OVESETUP_DIALOG/confirmUpgrade=bool:True
Summary: [RHEVM-SETUP] - wrong value saved in answer file OVESETUP_DIALOG/confirmUpgra...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-setup
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.3.1
Assignee: Sandro Bonazzola
QA Contact: Barak Dagan
URL:
Whiteboard: integration
Depends On: 1052199
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-29 16:08 UTC by rhev-integ
Modified: 2014-02-27 09:32 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1052199
Environment:
Last Closed: 2014-02-27 09:32:21 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0220 0 normal SHIPPED_LIVE rhevm-setup-plugins bug fix update 2014-02-27 14:31:47 UTC

Comment 1 Sandro Bonazzola 2014-01-29 16:25:18 UTC
packaging: setup: update OVESETUP_DIALOG/confirmUpgrade

OVESETUP_DIALOG/confirmUpgrade is now stored in answer file
with the right value

Comment 3 Barak Dagan 2014-02-06 18:34:30 UTC
Verified on is34.1:

[ INFO  ] Stage: Initializing
[ INFO  ] Stage: Environment setup
.....


However, that line appears twice in the answer file:

OVESETUP_AIO/storageDomainDir=none:None
OVESETUP_DIALOG/confirmUpgrade=bool:False  <---
OVESETUP_DIALOG/confirmUpgrade=bool:False  <---
OVESETUP_SYSTEM/redhatSupportProxyPort=none:None

Comment 6 errata-xmlrpc 2014-02-27 09:32:21 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-0220.html


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