Bug 1372230 - Cannot setup a separate host for DWH after upgrading to oVirt 4 (4.0.3)
Summary: Cannot setup a separate host for DWH after upgrading to oVirt 4 (4.0.3)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Setup.EngineCommon
Version: 4.0.2
Hardware: Unspecified
OS: Linux
high
high
Target Milestone: ovirt-4.0.4
: 4.0.4.2
Assignee: Yedidyah Bar David
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks: 1351864 1375161
TreeView+ depends on / blocked
 
Reported: 2016-09-01 08:14 UTC by Stefano Longo
Modified: 2017-05-11 09:25 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1375161 (view as bug list)
Environment:
Last Closed: 2016-09-26 12:37:19 UTC
oVirt Team: Integration
Embargoed:
rule-engine: ovirt-4.0.z+
rule-engine: blocker+
mgoldboi: planning_ack+
sbonazzo: devel_ack+
pstehlik: testing_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 63147 0 master MERGED packaging: setup: Move hosted-engine check plugin to engine 2021-02-15 13:20:41 UTC
oVirt gerrit 63451 0 ovirt-engine-4.0 MERGED packaging: setup: Move hosted-engine check plugin to engine 2021-02-15 13:20:41 UTC
oVirt gerrit 63453 0 ovirt-engine-4.0.4 MERGED packaging: setup: Move hosted-engine check plugin to engine 2021-02-15 13:20:42 UTC

Description Stefano Longo 2016-09-01 08:14:22 UTC
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

Comment 1 Yedidyah Bar David 2016-09-01 10:12:00 UTC
(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.

Comment 2 Stefano Longo 2016-09-01 10:21:15 UTC
(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.

Comment 3 Yedidyah Bar David 2016-09-01 12:14:12 UTC
(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 4 Sandro Bonazzola 2016-09-12 15:01:22 UTC
*** Bug 1375161 has been marked as a duplicate of this bug. ***

Comment 5 Red Hat Bugzilla Rules Engine 2016-09-12 15:03:48 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 6 Lukas Svaty 2016-09-14 09:09:03 UTC
verified with:

ovirt-engine-setup-base-4.0.4.2-0.1.el7ev.noarch
ovirt-engine-setup-plugin-ovirt-engine-common-4.0.4.2-0.1.el7ev.noarch
ovirt-engine-dwh-setup-4.0.2-1.el7ev.noarch
ovirt-setup-lib-1.0.2-1.el7ev.noarch


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