Bug 2034555 - Deprecation Warning for all openstack cli command
Summary: Deprecation Warning for all openstack cli command
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-tripleoclient
Version: 17.0 (Wallaby)
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: beta
: 17.0
Assignee: Cédric Jeanneret
QA Contact: David Rosenfeld
URL:
Whiteboard:
: 2040602 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-21 10:08 UTC by Ella Shulman
Modified: 2022-09-21 12:18 UTC (History)
9 users (show)

Fixed In Version: python-tripleoclient-16.4.1-0.20220427230225.095182c.el9ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-21 12:18:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 828610 0 None NEW Fix UX UserWarning notification 2022-02-09 21:28:37 UTC
Red Hat Issue Tracker OSP-11905 0 None None None 2021-12-21 10:11:50 UTC
Red Hat Product Errata RHEA-2022:6543 0 None None None 2022-09-21 12:18:36 UTC

Description Ella Shulman 2021-12-21 10:08:50 UTC
Description of problem:
whenever running an OpenStack command there is a deprecation warning for yaml

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

How reproducible:
100%

Steps to Reproduce:
1. source stackrc
2. run an OpenStack CLI command like openstack baremetal node list

Actual results:
this warning before the command output:
/usr/lib64/python3.6/site-packages/_yaml/__init__.py:23: DeprecationWarning: The _yaml extension module is now located at yaml._yaml and its location is subject to change.  To use the LibYAML-based parser and emitter, import from `yaml`: `from yaml import CLoader as Loader, CDumper as Dumper`.
  DeprecationWarning


Expected results:
no deprecation warnings

Additional info:

Comment 1 Brendan Shephard 2021-12-22 02:25:09 UTC
It comes from Ansible and is used by python-tripleoclient. Specifically:

ansible/parsing/yaml/loader.py:    from _yaml import CParser, CEmitter

Seems to already be fixed in Ansible:
https://github.com/ansible/ansible/blob/devel/lib/ansible/parsing/yaml/loader.py

https://github.com/ansible/ansible/commit/bf7d4ce260dc4ffc6074b2a392b9ff4d3794308b#diff-cbb6a146ee7d54e47982953cbf40c0f9754681d6a501a1df9daf7777656f159c


This may just be an issue with the tests we're currently running being on RHEL8. The version of Ansible we ship with OSP17 might already have this fixed.

Comment 2 Alex Schultz 2021-12-22 16:04:47 UTC
We could ignore it in tripleoclient, but let's see if this goes away with ansible 2.12 which is what I believe OSP17 will ship with.  Leaving this open to follow up with later.

Comment 3 Alex Schultz 2022-01-14 15:19:45 UTC
*** Bug 2040602 has been marked as a duplicate of this bug. ***

Comment 9 David Rosenfeld 2022-07-28 20:27:40 UTC
openstack baremetal node list executes without deprecation warning

(undercloud) [stack@undercloud-0 ~]$ openstack baremetal node list
+--------------------------------------+--------------+--------------------------------------+-------------+--------------------+-------------+
| UUID                                 | Name         | Instance UUID                        | Power State | Provisioning State | Maintenance |
+--------------------------------------+--------------+--------------------------------------+-------------+--------------------+-------------+
| db7c57b9-d146-4adb-8212-66e110b5503a | ceph-0       | 213782d9-7720-41ba-8ba6-d918a7b50400 | power on    | active             | False       |
| 3b544005-a151-475d-8a55-4ed4af3681dc | ceph-1       | e2acba97-fbb7-4e4b-bd94-b9ed57fc40a6 | power on    | active             | False       |
| 178638a0-c606-44cf-9978-8413f8027714 | ceph-2       | b5f37315-279d-4dea-a376-759e185ad258 | power on    | active             | False       |
| 12f84002-5cef-45e4-a66d-fc07fcf49c80 | compute-0    | b87db79e-6fc1-4753-870d-0b909497074b | power on    | active             | False       |
| a47aee51-d20a-458a-8160-98eb0a77ccc4 | compute-1    | ee147a51-e85a-4101-a2e1-b34b0284d60c | power on    | active             | False       |
| 63fe41d3-8419-4826-b8ac-c50340baa145 | controller-0 | f0b9cc8d-000b-4ea9-a6c6-17563e61b112 | power on    | active             | False       |
| c323fdf0-3639-4583-acab-4a04c3ae098d | controller-1 | 5f061f4f-e8dd-4b9d-8094-dbf2f5260a34 | power on    | active             | False       |
| 0c3b11df-1e69-456d-b2cb-17546dae10eb | database-0   | 4a73ed84-75ef-411a-80e8-27d616925322 | power on    | active             | False       |
| add3a0d8-7752-47e2-af92-1533c6ccf877 | database-1   | edf7c172-efe1-463a-b968-5f21674ae7e8 | power on    | active             | False       |
| e06f6b1d-ae4b-4281-a2b0-97e01e239932 | database-2   | c7cbd053-93b2-4588-8460-4cb7be11e097 | power on    | active             | False       |
| fa1abb98-f0b9-4f9d-953f-da2ac9ee754d | messaging-0  | 76c84eb4-96a8-4095-ae90-c6289d20929c | power on    | active             | False       |
| cce7be59-6391-4365-86e1-028e4d8f2a93 | messaging-1  | d55872d3-68fa-417e-ac21-0d1a8bdbe343 | power on    | active             | False       |
| cc9bd5bb-27e9-4203-aecc-2a0324bcde95 | messaging-2  | a3bc7a4f-0653-4520-81a3-091faa1841d9 | power on    | active             | False       |
| 8cabcec1-d9ba-41ae-b814-56e798ca54f8 | networker-0  | 2e9c1d17-0d35-4335-b3ec-80e81e40e201 | power on    | active             | False       |
| 267fbc64-b816-4edf-82ff-4e9178a5cadf | networker-1  | ed48891e-ca43-4388-a4cd-75ca3884f25d | power on    | active             | False       |
| 9f9baf8a-dbb9-4381-bfad-819abdd28216 | controller-2 | None                                 | power off   | available          | False       |
+--------------------------------------+--------------+--------------------------------------+-------------+--------------------+-------------+
(undercloud) [stack@undercloud-0 ~]$

Comment 14 errata-xmlrpc 2022-09-21 12:18:08 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Release of components for Red Hat OpenStack Platform 17.0 (Wallaby)), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHEA-2022:6543


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