Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1056530

Summary: [engine-setup] setup fails with Internal error: type object 'Stages' has no attribute 'UPGRADE_FROM_LEGACY_CONFIG'
Product: [Retired] oVirt Reporter: Elad <ebenahar>
Component: ovirt-engine-installerAssignee: Sandro Bonazzola <sbonazzo>
Status: CLOSED CURRENTRELEASE QA Contact: sefi litmanovich <slitmano>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.4CC: bazulay, bugs, dougsland, ebenahar, ecohen, gklein, iheim, lsurette, rbalakri, slitmano, yeylon
Target Milestone: ---   
Target Release: 3.4.0   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: integration
Fixed In Version: ovirt-3.4.0-ga Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-31 12:25:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
setup, server and engine logs none

Description Elad 2014-01-22 11:41:31 UTC
Created attachment 853823 [details]
setup, server and engine logs

Description of problem:
I have an ovirt setup with  ovirt-engine-3.4.0-0.2.master.20140106180914.el6.noarch
I've updated ovirt-engine-setup to ovirt-engine-setup-3.4.0-0.2.master.20140112020439.git9ad8529.el6.noarch
and executed 'engine-setup' command.
It failed with:
[root@dhcp163-52 ~]# engine-setup
***L:ERROR Internal error: type object 'Stages' has no attribute 'UPGRADE_FROM_LEGACY_CONFIG'


Additional info: setup, server and engine logs

Comment 1 Sandro Bonazzola 2014-01-22 12:27:29 UTC
Please try again with 3.4.0 beta, I can't see any UPGRADE_FROM_LEGACY_CONFIG reference in 3.4.0_beta1 code.
If it fails, please attach new logs.

Comment 2 Elad 2014-01-23 14:33:20 UTC
(In reply to Sandro Bonazzola from comment #1)
> Please try again with 3.4.0 beta, I can't see any UPGRADE_FROM_LEGACY_CONFIG
> reference in 3.4.0_beta1 code.
> If it fails, please attach new logs.

I tried engine-setup with 3.4-alpha installed and 3.4-beta repo enabled.

Comment 3 Sandro Bonazzola 2014-01-23 14:45:24 UTC
(In reply to Elad from comment #2)
> (In reply to Sandro Bonazzola from comment #1)
> > Please try again with 3.4.0 beta, I can't see any UPGRADE_FROM_LEGACY_CONFIG
> > reference in 3.4.0_beta1 code.
> > If it fails, please attach new logs.
> 
> I tried engine-setup with 3.4-alpha installed and 3.4-beta repo enabled.

and does it work?

Comment 4 Elad 2014-01-23 15:01:04 UTC
(In reply to Sandro Bonazzola from comment #3)
> (In reply to Elad from comment #2)
> > (In reply to Sandro Bonazzola from comment #1)
> > > Please try again with 3.4.0 beta, I can't see any UPGRADE_FROM_LEGACY_CONFIG
> > > reference in 3.4.0_beta1 code.
> > > If it fails, please attach new logs.
> > 
> > I tried engine-setup with 3.4-alpha installed and 3.4-beta repo enabled.
> 
> and does it work?

No, that's the bug's scenario.
Executing engine-setup while 3.4-beta is installed with enabled 3.4-beta repo succeeds.

Comment 5 sefi litmanovich 2014-02-17 15:08:40 UTC
Verified. 
upgrade from ovirt-beta1 to ovirt-beta2, packages:
ovirt-engine-setup-3.4.0-0.5.beta1.el6.noarch.rpm --> ovirt-engine-setup-3.4.0-0.7.beta2.el6.noarch.rpm works with no errors.

Comment 6 Sandro Bonazzola 2014-03-31 12:25:44 UTC
this is an automated message: moving to Closed CURRENT RELEASE since oVirt 3.4.0 has been released