Bug 1375161

Summary: Cannot setup a separate host for DWH after upgrading to oVirt 4 (4.0.3)[zstream clone to 3.6.9]
Product: Red Hat Enterprise Virtualization Manager Reporter: Lukas Svaty <lsvaty>
Component: ovirt-engineAssignee: Yedidyah Bar David <didi>
Status: CLOSED CURRENTRELEASE QA Contact: Lukas Svaty <lsvaty>
Severity: high Docs Contact:
Priority: high    
Version: 3.6.8CC: bugs, dfediuck, didi, eedri, lsurette, mgoldboi, rbalakri, Rhev-m-bugs, sradco, srevivo, Stefano.Longo, ykaul, ylavi
Target Milestone: ovirt-3.6.9Keywords: Regression, ZStream
Target Release: 3.6.9   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1372230 Environment:
Last Closed: 2016-09-27 12:22:35 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:
Bug Depends On: 1359844, 1372230    
Bug Blocks:    

Description Lukas Svaty 2016-09-12 10:40:10 UTC
Cloning to 3.6:

packages which reproduced this:
rhevm-setup-plugin-ovirt-engine-common-3.6.9-0.1.el6.noarch
rhevm-dwh-setup-3.6.8-1.el6ev.noarch
rhevm-dwh-3.6.8-1.el6ev.noarch
rhevm-lib-3.6.9-0.1.el6.noarch
rhevm-setup-base-3.6.9-0.1.el6.noarch

+++ This bug was initially created as a clone of Bug #1372230 +++

Description of problem:

Hi All,
I've upgraded my infrastructure - configured with separate hosts for Engine, DWH and Reports -  from oVirt 3.6 to 4.
Clearly first I've upgraded the Engine (without particular difficulties) then I've started the upgrade of DWH host. After the upgrade with yum I've launched engine-setup to update DB, etc., but the result was a laconic

"***L:ERROR Internal error: No module named engine"

Maybe that engine-setup expect to find installed also oVirt engine on the host where it get executed?

Thanks for your support,
Stefano.


Version-Release number of selected component (if applicable):

ovirt-setup-lib-1.0.2-1.el7.centos.noarch
ovirt-engine-dwh-4.0.2-1.el7.centos.noarch
ovirt-engine-lib-4.0.3-1.el7.centos.noarch
ovirt-engine-setup-base-4.0.3-1.el7.centos.noarch
ovirt-release40-4.0.3-1.noarch
ovirt-engine-dwh-setup-4.0.2-1.el7.centos.noarch
ovirt-engine-setup-plugin-ovirt-engine-common-4.0.3-1.el7.centos.noarch


How reproducible:


Steps to Reproduce:
1.Upgrade DWH from oVirt 3.6 to 4
2.launch engine-setup
3. I've also tried with a fresh installation of DWH with the same result

--- Additional comment from Yedidyah Bar David on 2016-09-01 06:12:00 EDT ---

(In reply to Stefano Longo from comment #0)
> Description of problem:
> 
> Hi All,
> I've upgraded my infrastructure - configured with separate hosts for Engine,
> DWH and Reports -  from oVirt 3.6 to 4.
> Clearly first I've upgraded the Engine (without particular difficulties)
> then I've started the upgrade of DWH host. After the upgrade with yum I've
> launched engine-setup to update DB, etc., but the result was a laconic
> 
> "***L:ERROR Internal error: No module named engine"

Can you please attach output of:

OTOPI_DEBUG=1 engine-setup

> 
> Maybe that engine-setup expect to find installed also oVirt engine on the
> host where it get executed?

No, and if it does, it should not.

Thanks.

--- Additional comment from Stefano Longo on 2016-09-01 06:21:15 EDT ---

(In reply to Yedidyah Bar David from comment #1)
> (In reply to Stefano Longo from comment #0)
> > Description of problem:
> > 
> > Hi All,
> > I've upgraded my infrastructure - configured with separate hosts for Engine,
> > DWH and Reports -  from oVirt 3.6 to 4.
> > Clearly first I've upgraded the Engine (without particular difficulties)
> > then I've started the upgrade of DWH host. After the upgrade with yum I've
> > launched engine-setup to update DB, etc., but the result was a laconic
> > 
> > "***L:ERROR Internal error: No module named engine"
> 
> Can you please attach output of:
> 
> OTOPI_DEBUG=1 engine-setup
> 

Sure. Here you are:

OTOPI_DEBUG=1 engine-setup
Loading plugin group otopi
Loading plugin otopi:core (/usr/share/otopi/plugins/otopi/core)
Loading plugin otopi:dialog (/usr/share/otopi/plugins/otopi/dialog)
Loading plugin otopi:network (/usr/share/otopi/plugins/otopi/network)
Loading plugin otopi:packagers (/usr/share/otopi/plugins/otopi/packagers)
Loading plugin otopi:services (/usr/share/otopi/plugins/otopi/services)
Loading plugin otopi:system (/usr/share/otopi/plugins/otopi/system)
Loading plugin otopi:force_fail (/usr/share/otopi/plugins/otopi/debug/force_fail)
Loading plugin otopi:wait_on_error (/usr/share/otopi/plugins/otopi/debug/wait_on_error)
Loading plugin group ovirt-engine-common
Loading plugin ovirt-engine-common:core (/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-common/base/core)
Loading plugin ovirt-engine-common:dialog (/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-common/base/dialog)
Loading plugin ovirt-engine-common:network (/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-common/base/network)
Loading plugin ovirt-engine-common:remote_engine (/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-common/base/remote_engine)
Loading plugin ovirt-engine-common:system (/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-common/base/system)
Loading plugin ovirt-engine-common:config (/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-common/ovirt-engine-common/config)
Loading plugin ovirt-engine-common:core (/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-common/ovirt-engine-common/core)
Loading plugin ovirt-engine-common:provisioning (/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-common/ovirt-engine-common/provisioning)
Loading plugin ovirt-engine-common:system (/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-common/ovirt-engine-common/system)
***L:ERROR Internal error: No module named engine
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/otopi/__main__.py", line 88, in main
    installer.execute()
  File "/usr/lib/python2.7/site-packages/otopi/main.py", line 148, in execute
    sys.exc_info()[2],
  File "/usr/lib/python2.7/site-packages/otopi/util.py", line 81, in raiseExceptionInformation
    exec('raise info[1], None, info[2]')
  File "/usr/lib/python2.7/site-packages/otopi/main.py", line 142, in execute
    self.context.loadPlugins()
  File "/usr/lib/python2.7/site-packages/otopi/context.py", line 798, in loadPlugins
    self._loadPluginGroups(plugindir, needgroups, loadedgroups)
  File "/usr/lib/python2.7/site-packages/otopi/context.py", line 113, in _loadPluginGroups
    self._loadPlugins(path, path, groupname)
  File "/usr/lib/python2.7/site-packages/otopi/context.py", line 70, in _loadPlugins
    self._loadPlugins(base, d, groupname)
  File "/usr/lib/python2.7/site-packages/otopi/context.py", line 70, in _loadPlugins
    self._loadPlugins(base, d, groupname)
  File "/usr/lib/python2.7/site-packages/otopi/context.py", line 101, in _loadPlugins
    os.path.basename(path),
  File "/usr/lib/python2.7/site-packages/otopi/util.py", line 105, in loadModule
    mod_desc
  File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-common/ovirt-engine-common/system/__init__.py", line 27, in <module>
    from . import he
  File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-common/ovirt-engine-common/system/he.py", line 24, in <module>
    from ovirt_engine_setup.engine import constants as oenginecons
PluginLoadException: No module named engine

Thanks,
Stefano.

--- Additional comment from Yedidyah Bar David on 2016-09-01 08:14:12 EDT ---

(In reply to Stefano Longo from comment #2)
> "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-common/ovirt-
> engine-common/system/he.py", line 24, in <module>
>     from ovirt_engine_setup.engine import constants as oenginecons

Ouch. That's a bug.

A plugin in ovirt-engine-common must not import from engine, which does not exist on other machines.

Thanks for the report!

Comment 1 Sandro Bonazzola 2016-09-12 15:01:22 UTC
Closing as duplicate, we'll track on the upstream bug.

*** This bug has been marked as a duplicate of bug 1372230 ***

Comment 2 Sandro Bonazzola 2016-09-12 15:06:15 UTC
Sorry, this was meant to be used for backporting to 3.6

Comment 4 Lukas Svaty 2016-09-15 10:19:04 UTC
verified with:

rhevm-dwh-setup-3.6.8-1.el6ev.noarch
ovirt-setup-lib-1.0.1-1.el6ev.noarch
rhevm-setup-plugin-ovirt-engine-common-3.6.9.2-0.1.el6.noarch
rhevm-setup-base-3.6.9.2-0.1.el6.noarch

Comment 5 Eyal Edri 2016-09-27 12:22:35 UTC
3.6.9 was released.