annoying warning in tripleoclient

Bug #1889380 reported by Cédric Jeanneret
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Medium
Yadnesh Kulkarni

Bug Description

We get this annoying ImportWarning when using the tripleoclient CLI:

/usr/lib64/python3.6/importlib/_bootstrap.py:219: ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__ and __path__
  return f(*args, **kwds)

Revision history for this message
Alex Schultz (alex-schultz) wrote :

This comes from openstackclient not tripleoclient

Revision history for this message
yatin (yatinkarel) wrote :

<< This comes from openstackclient not tripleoclient

May be some issue in tripleoclient on how it's being implemented and thus warning is reported?
Actully i recently filed a bug https://bugs.launchpad.net/tripleo/+bug/1890389 not specifically for this warning. The issue in the other bug happens only when tripleoclient is installed, when it's not installed other clients works fine.

Also wrt the warning, it is not reported in all commands:-

[stack@standalone ~]$ python3 -c "import tripleoclient.v1.overcloud_deploy"
/usr/lib64/python3.6/importlib/_bootstrap.py:219: ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__ and __path__
  return f(*args, **kwds)
[stack@standalone ~]$ python3 -c "import tripleoclient.v1.tripleo_deploy"
[stack@standalone ~]$

Changed in tripleo:
milestone: victoria-3 → wallaby-1
Changed in tripleo:
milestone: wallaby-1 → wallaby-2
Changed in tripleo:
assignee: nobody → Yadnesh Kulkarni (ykulkarn)
Revision history for this message
Yadnesh Kulkarni (ykulkarn) wrote :

The warning seems to be coming from tripleo_common project from line [1]

Changing it to filter only deprecation warnings fixes it
~~~
warnings.filterwarnings('once', category=DeprecationWarning)
~~~

[1] https://opendev.org/openstack/tripleo-common/src/branch/master/tripleo_common/utils/config.py#L36

Revision history for this message
yatin (yatinkarel) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-common 14.0.0

This issue was fixed in the openstack/tripleo-common 14.0.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-common 12.4.3

This issue was fixed in the openstack/tripleo-common 12.4.3 release.

Changed in tripleo:
milestone: wallaby-2 → wallaby-3
Revision history for this message
yatin (yatinkarel) wrote :
Changed in tripleo:
status: Triaged → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-common 11.5.0

This issue was fixed in the openstack/tripleo-common 11.5.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-common 13.2.0

This issue was fixed in the openstack/tripleo-common 13.2.0 release.

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.