Bug 873372 - RHEVM - Installation: Upgrade from 3.0 to 3.1 fails: 'module' object has no attribute 'FILE_RHEVM_CONFIG_BIN'
Summary: RHEVM - Installation: Upgrade from 3.0 to 3.1 fails: 'module' object has no a...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-setup
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: ---
Assignee: Alex Lourie
QA Contact: Pavel Stehlik
URL:
Whiteboard: integration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-05 16:46 UTC by Daniel Paikov
Modified: 2018-11-30 20:48 UTC (History)
9 users (show)

Fixed In Version: si24.1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-04 20:03:08 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
ovirt-engine-upgrade (40.79 KB, application/x-compressed-tar)
2012-11-05 16:46 UTC, Daniel Paikov
no flags Details

Description Daniel Paikov 2012-11-05 16:46:32 UTC
Created attachment 638743 [details]
ovirt-engine-upgrade

rhevm-upgrade from 3.0.8 to si24 fails with the following exception. Attaching log.


2012-11-05 18:38:51::ERROR::rhevm-upgrade::1285::root:: Traceback (most recent call last):
  File "/usr/bin/rhevm-upgrade", line 1278, in <module>
    main(options)
  File "/usr/bin/rhevm-upgrade", line 1219, in main
    runFunc(postFunc, MSG_INFO_RUN_POST)
  File "/usr/bin/rhevm-upgrade", line 661, in runFunc
    func()
  File "/usr/bin/rhevm-upgrade", line 649, in runPost30
    post.run()
  File "/usr/share/ovirt-engine/scripts/post_upgrade30.py", line 176, in run
    updateVdcPkiOptions()
  File "/usr/share/ovirt-engine/scripts/post_upgrade30.py", line 71, in updateVdcPkiOptions
    raise Exception(output_messages.ERR_FAILED_UPD_VDC_OPTIONS%(sys.exc_info()[1]))
Exception: Failed updating configuration parameter: 'module' object has no attribute 'FILE_RHEVM_CONFIG_BIN'

Comment 3 Daniel Paikov 2012-11-13 13:05:42 UTC
Checked on si24.1.


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