Bug 1492065

Summary: error by upgrading dwh 4.1 on separate machine
Product: [oVirt] ovirt-engine-dwh Reporter: Lucie Leistnerova <lleistne>
Component: SetupAssignee: Yedidyah Bar David <didi>
Status: CLOSED CURRENTRELEASE QA Contact: Lucie Leistnerova <lleistne>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: bugs, lleistne, lsvaty, sbonazzo, sradco
Target Milestone: ovirt-4.2.0Flags: rule-engine: ovirt-4.2+
lsvaty: testing_ack+
Target Release: 4.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-20 11:01:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1484961    
Bug Blocks:    
Attachments:
Description Flags
logs none

Description Lucie Leistnerova 2017-09-15 11:26:58 UTC
Description of problem:
Upgrading dwh from 4.1 to 4.2 fails with Internal error: type object 'Stages' has no attribute 'DB_CUST_UPGRADEDBMS_DWH'


Version-Release number of selected component (if applicable):
ovirt-engine-dwh-setup-4.1.1-1.el7.centos.noarch
ovirt-engine-dwh-setup-4.2.1-0.0.master.20170912085356.el7.centos.noarch

How reproducible: always


Steps to Reproduce:
1. have DWH 4.1 installed and running on separate machine
2. install 4.2 master repo
3. yum update ovirt-engine-dwh-setup
4. run engine-setup

Actual results: # engine-setup 
***L:ERROR Internal error: type object 'Stages' has no attribute 'DB_CUST_UPGRADEDBMS_DWH'


Expected results: no error, dwh is upgraded


Additional info:

Comment 1 Yedidyah Bar David 2017-09-17 14:22:56 UTC
(In reply to Lucie Leistnerova from comment #0)
> Description of problem:
> Upgrading dwh from 4.1 to 4.2 fails with Internal error: type object
> 'Stages' has no attribute 'DB_CUST_UPGRADEDBMS_DWH'
> 
> 
> Version-Release number of selected component (if applicable):
> ovirt-engine-dwh-setup-4.1.1-1.el7.centos.noarch
> ovirt-engine-dwh-setup-4.2.1-0.0.master.20170912085356.el7.centos.noarch
> 
> How reproducible: always
> 
> 
> Steps to Reproduce:
> 1. have DWH 4.1 installed and running on separate machine
> 2. install 4.2 master repo
> 3. yum update ovirt-engine-dwh-setup

Is this copied from our documentation?

You should update all relevant machines, just as in updating the engine. See also e.g. bug 1306212.

That said, we *can* "fix" current bug, but it will require on-going maintenance which I am not sure is worth it, by changing the dwh spec file from having, under '%package setup':

Requires:       ovirt-engine-setup-plugin-ovirt-engine-common

To:

Requires:       ovirt-engine-setup-plugin-ovirt-engine-common >= 4.2.0

(and then >= 4.3 on the next version, etc.).

Most likely we had similar issues in previous versions - we have this line since 3.4, and so far handled this only using documentation.

> 4. run engine-setup
> 
> Actual results: # engine-setup 
> ***L:ERROR Internal error: type object 'Stages' has no attribute
> 'DB_CUST_UPGRADEDBMS_DWH'
> 
> 
> Expected results: no error, dwh is upgraded
> 
> 
> Additional info:

Comment 2 Yedidyah Bar David 2017-09-17 14:24:05 UTC
Sandro, feel free to ack anyway, might be worth it even if docs are correct.

Comment 3 Lucie Leistnerova 2017-09-18 07:39:50 UTC
To run 'yum update ovirt-engine-dwh-setup' told me the engine-setup.
When I updated 'yum update ovirt-engine*setup*' this error is gone and other appears 

***L:ERROR Internal error: Internal error, plugins set(['otopi', 'ovirt-engine-setup', 'ovirt-engine-checks', 'ovirt-engine-common']) are missing

yum info:

Updating:
 ovirt-engine-setup-base
 ovirt-engine-setup-plugin-ovirt-engine-common
Updating for dependencies:
 otopi
 ovirt-engine-lib

Comment 4 Yedidyah Bar David 2017-09-18 08:21:31 UTC
(In reply to Lucie Leistnerova from comment #3)
> To run 'yum update ovirt-engine-dwh-setup' told me the engine-setup.

I think it should have told you to update also ovirt-engine-setup, no?

Please attach all setup logs, yum log, and used repos. Thanks.

> When I updated 'yum update ovirt-engine*setup*' this error is gone and other
> appears 
> 
> ***L:ERROR Internal error: Internal error, plugins set(['otopi',
> 'ovirt-engine-setup', 'ovirt-engine-checks', 'ovirt-engine-common']) are
> missing

That's bug 1484961.

> 
> yum info:
> 
> Updating:
>  ovirt-engine-setup-base
>  ovirt-engine-setup-plugin-ovirt-engine-common
> Updating for dependencies:
>  otopi
>  ovirt-engine-lib

Comment 5 Lucie Leistnerova 2017-09-18 12:18:47 UTC
(In reply to Yedidyah Bar David from comment #4)
> (In reply to Lucie Leistnerova from comment #3)
> > To run 'yum update ovirt-engine-dwh-setup' told me the engine-setup.
> 
> I think it should have told you to update also ovirt-engine-setup, no?
> 
> Please attach all setup logs, yum log, and used repos. Thanks.
> 

According to documentation DWH on separate machine needs only ovirt-engine-dwh-setup package and its dependencies.
When I installed ovirt-release-master.rpm (4.1 dwh already running) engine-setup fails with:

[ INFO  ] Checking for an update for Setup...
          An update for the Setup packages ovirt-engine-dwh-setup was found. Please update that package by running:
          "yum update ovirt-engine-dwh-setup"
          and then execute Setup again.
[ ERROR ] Failed to execute stage 'Environment customization': Please update the Setup packages

So no ovirt-engine-setup.

Comment 6 Lucie Leistnerova 2017-09-18 12:20:18 UTC
Created attachment 1327358 [details]
logs

Comment 8 Lucie Leistnerova 2017-11-01 12:12:08 UTC
Upgrade was successful 

verified in ovirt-engine-dwh-4.2.1-0.2.master.20171026133424.el7.centos.noarch

Comment 9 Sandro Bonazzola 2017-12-20 11:01:11 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.