Novaclient import error on oscc ci

Bug #1528180 reported by Kyrylo Romanenko
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Fix Released
High
Vasyl Saienko
6.0.x
Won't Fix
Medium
Vadim Rovachev
6.1.x
Won't Fix
Critical
Vadim Rovachev
7.0.x
Won't Fix
High
Fuel QA Team

Bug Description

Fuel deployment job fails with error
11:02:51 File "/home/jenkins/venv-mos-master/fuel-qa/fuelweb_test/helpers/common.py", line 27, in <module>
11:02:51 from novaclient.v1_1 import Client as NovaClient
11:02:51 ImportError: No module named v1_1

Full job log:
http://paste.openstack.org/show/482393/

Maciej Relewicz (rlu)
tags: added: area-qa
tags: added: system-tests
Revision history for this message
Oleksiy Butenko (obutenko) wrote :
Changed in mos:
status: New → In Progress
Changed in mos:
status: In Progress → Fix Released
status: Fix Released → Fix Committed
status: Fix Committed → In Progress
Revision history for this message
Ilya Bumarskov (ibumarskov) wrote :

It's necessary to apply the fix for stable/6.1 and stable/7.0 branches

Revision history for this message
Ilya Bumarskov (ibumarskov) wrote :

Requirements for python-novaclient was fixed:
https://review.openstack.org/#/c/260446/

Revision history for this message
Vasyl Saienko (vsaienko) wrote :

For stable branches we should set upper bound for python libraries according to global-requirements.
I've opened new bug for it https://bugs.launchpad.net/fuel/+bug/1528538

Vasyl Saienko (vsaienko)
Changed in mos:
status: In Progress → Fix Committed
Revision history for this message
Ksenia Svechnikova (kdemina) wrote :

Changing upper bonds and issue with "ImportError: No module named v1_1" are different issues, isn't it?

Reproduce the "ImportError: No module named v1_1" with patch for upper bonds on custom 7.0 ISO:

https://github.com/openstack/fuel-qa/blob/stable/7.0/fuelweb_test/helpers/common.py#L27
http://jenkins-product.srt.mirantis.net:8080/job/7.0.custom_system_test/971/console

Revision history for this message
Vasyl Saienko (vsaienko) wrote :

We get No module named v1_1 because we using novaclient from master, even for stable branch. It is impossible to make code compatible with all versions of libraries. Upper bounds should be set in order to install library which can work with stable code.
There is fix for 7.0 https://review.openstack.org/#/c/261099/

Revision history for this message
Denis Meltsaykin (dmeltsaykin) wrote :

We have just faced this issue on a big swarm run in 6.1. https://product-ci.infra.mirantis.net/view/6.1_swarm/job/6.1.swarm.runner/8/
For us this is critical, as it blocks us from releasing Maintenance Update, please fix ASAP.

Revision history for this message
Vasyl Saienko (vsaienko) wrote :

Denis: for stable branches we should set upper bounds, there is new bug for it https://bugs.launchpad.net/fuel/+bug/1528538

Revision history for this message
Denis Meltsaykin (dmeltsaykin) wrote :

Vasyl, as I understand this helps not much, as jobs use preinstalled venvs with incompatible version of novaclient.

Revision history for this message
Vasyl Saienko (vsaienko) wrote :

We need to have separate venv for each release. I've opened a bug https://bugs.launchpad.net/fuel/+bug/1529569

Changed in mos:
status: Fix Committed → Fix Released
Revision history for this message
Vadim Rovachev (vrovachev) wrote :

Need to solve this problem for 6.0 version in fuel-main repo because of 6.1 upgrade tests on patching CI.
https://patching-ci.infra.mirantis.net/view/All/job/6.1.system_test.ubuntu.ceph_multinode_compact_neutron.upgrade/2/console

Dina Belova (dbelova)
tags: added: non-release
tags: removed: non-release
tags: added: non-release
Revision history for this message
Alexey Stupnikov (astupnikov) wrote :

We no longer support MOS5.1, MOS6.0, MOS6.1
We deliver only Critical/Security fixes to MOS7.0, MOS8.0.
We deliver only High/Critical/Security fixes to MOS9.2.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.