Bug 1739616 - Unable to import nodes using staging-ovirt driver. Error: "Failed to get power state for node 1b246f12-ba40-446d-a215-834b07d1a41f. Error: name 'sdk' is not defined "
Summary: Unable to import nodes using staging-ovirt driver. Error: "Failed to get powe...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: async
: ---
Assignee: Alex McLeod
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On: 1721607
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-09 16:38 UTC by Alexander Chuzhoy
Modified: 2019-11-13 11:26 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1721607
Environment:
Last Closed: 2019-11-13 11:26:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Alexander Chuzhoy 2019-08-09 16:38:32 UTC
+++ This bug was initially created as a clone of Bug #1721607 +++

Unable to import nodes using staging-ovirt driver. Error: "Failed to get power state for node 1b246f12-ba40-446d-a215-834b07d1a41f. Error: name 'sdk' is not defined "


Environment:
openstack-ironic-staging-drivers-0.11.1-0.20190420132245.b7c6755.el8ost.noarch
openstack-tripleo-common-10.7.1-0.20190614200406.277902e.el8ost


Steps to reproduce:

Deploy undercloud with:
enabled_hardware_types = ipmi,staging-ovirt


Try to import nodes.

Node definition example from istackenv.json:
      "name": "compute-0",
      "mac": ["00:1a:4a:23:13:4f"],
      "pm_addr": "FQDN",
      "pm_type": "staging-ovirt",
      "pm_user": "<USERNAME>",
      "pm_vm_name": "compute",
      "pm_password": "<PASSWORD>"
      }



Result:
+ openstack overcloud node import /home/stack/instackenv.json
Waiting for messages on queue 'tripleo' with no timeout.
Exception registering nodes: {'result': 'Failure caused by error in tasks: send_message\n\n  send_message [task_ex_id=59763261-373f-4809-9885-33db422219aa] -> Workflow failed due to message status. Status:FAILED Message:({\'result\': \'Node 1b246f12-ba40-446d-a215-834b07d1a41f did not reach state "manageable", the state is "enroll", error: Failed to get power state for node 1b246f12-ba40-446d-a215-834b07d1a41f. Error: name \\\'sdk\\\' is not defined\'}, {\'result\': \'Node 7c0d081c-3c54-4657-adf7-42b04d240b20 did not reach state "manageable", the state is "enroll", error: Failed to get power state for node 7c0d081c-3c54-4657-adf7-42b04d240b20. Error: name \\\'sdk\\\' is not defined\'}, {\'result\': \'Node b866b636-52f4-4cd9-947e-2a572d02c474 did not reach state "manageable", the state is "enroll", error: Failed to get power state for node b866b636-52f4-4cd9-947e-2a572d02c474. Error: name \\\'sdk\\\' is not defined\'}, {\'result\': \'Node b8ea8681-9418-405c-aa0c-da5022acc160 did not reach state "manageable", the state is "enroll", error: Failed to get power state for node b8ea8681-9418-405c-aa0c-da5022acc160. Error: name \\\'sdk\\\' is not defined\'})\n    [wf_ex_id=8ced74e6-427f-4c3d-a7b8-271368a6482a, idx=0]: Workflow failed due to message status. Status:FAILED Message:({\'result\': \'Node 1b246f12-ba40-446d-a215-834b07d1a41f did not reach state "manageable", the state is "enroll", error: Failed to get power state for node 1b246f12-ba40-446d-a215-834b07d1a41f. Error: name \\\'sdk\\\' is not defined\'}, {\'result\': \'Node 7c0d081c-3c54-4657-adf7-42b04d240b20 did not reach state "manageable", the state is "enroll", error: Failed to get power state for node 7c0d081c-3c54-4657-adf7-42b04d240b20. Error: name \\\'sdk\\\' is not defined\'}, {\'result\': \'Node b866b636-52f4-4cd9-947e-2a572d02c474 did not reach state "manageable", the state is "enroll", error: Failed to get power state for node b866b636-52f4-4cd9-947e-2a572d02c474. Error: name \\\'sdk\\\' is not defined\'}, {\'result\': \'Node b8ea8681-9418-405c-aa0c-da5022acc160 did not reach state "manageable", the state is "enroll", error: Failed to get power state for node b8ea8681-9418-405c-aa0c-da5022acc160. Error: name \\\'sdk\\\' is not defined\'})\n', 'status': 'FAILED', 'message': [{'result': 'Node 1b246f12-ba40-446d-a215-834b07d1a41f did not reach state "manageable", the state is "enroll", error: Failed to get power state for node 1b246f12-ba40-446d-a215-834b07d1a41f. Error: name \'sdk\' is not defined'}, {'result': 'Node 7c0d081c-3c54-4657-adf7-42b04d240b20 did not reach state "manageable", the state is "enroll", error: Failed to get power state for node 7c0d081c-3c54-4657-adf7-42b04d240b20. Error: name \'sdk\' is not defined'}, {'result': 'Node b866b636-52f4-4cd9-947e-2a572d02c474 did not reach state "manageable", the state is "enroll", error: Failed to get power state for node b866b636-52f4-4cd9-947e-2a572d02c474. Error: name \'sdk\' is not defined'}, {'result': 'Node b8ea8681-9418-405c-aa0c-da5022acc160 did not reach state "manageable", the state is "enroll", error: Failed to get power state for node b8ea8681-9418-405c-aa0c-da5022acc160. Error: name \'sdk\' is not defined'}]}

[{'result': 'Node 1b246f12-ba40-446d-a215-834b07d1a41f did not reach state "manageable", the state is "enroll", error: Failed to get power state for node 1b246f12-ba40-446d-a215-834b07d1a41f. Error: name \'sdk\' is not defined'}, {'result': 'Node 7c0d081c-3c54-4657-adf7-42b04d240b20 did not reach state "manageable", the state is "enroll", error: Failed to get power state for node 7c0d081c-3c54-4657-adf7-42b04d240b20. Error: name \'sdk\' is not defined'}, {'result': 'Node b866b636-52f4-4cd9-947e-2a572d02c474 did not reach state "manageable", the state is "enroll", error: Failed to get power state for node b866b636-52f4-4cd9-947e-2a572d02c474. Error: name \'sdk\' is not defined'}, {'result': 'Node b8ea8681-9418-405c-aa0c-da5022acc160 did not reach state "manageable", the state is "enroll", error: Failed to get power state for node b8ea8681-9418-405c-aa0c-da5022acc160. Error: name \'sdk\' is not defined'}]
{'result': 'Failure caused by error in tasks: send_message\n\n  send_message [task_ex_id=59763261-373f-4809-9885-33db422219aa] -> Workflow failed due to message status. Status:FAILED Message:({\'result\': \'Node 1b246f12-ba40-446d-a215-834b07d1a41f did not reach state "manageable", the state is "enroll", error: Failed to get power state for node 1b246f12-ba40-446d-a215-834b07d1a41f. Error: name \\\'sdk\\\' is not defined\'}, {\'result\': \'Node 7c0d081c-3c54-4657-adf7-42b04d240b20 did not reach state "manageable", the state is "enroll", error: Failed to get power state for node 7c0d081c-3c54-4657-adf7-42b04d240b20. Error: name \\\'sdk\\\' is not defined\'}, {\'result\': \'Node b866b636-52f4-4cd9-947e-2a572d02c474 did not reach state "manageable", the state is "enroll", error: Failed to get power state for node b866b636-52f4-4cd9-947e-2a572d02c474. Error: name \\\'sdk\\\' is not defined\'}, {\'result\': \'Node b8ea8681-9418-405c-aa0c-da5022acc160 did not reach state "manageable", the state is "enroll", error: Failed to get power state for node b8ea8681-9418-405c-aa0c-da5022acc160. Error: name \\\'sdk\\\' is not defined\'})\n    [wf_ex_id=8ced74e6-427f-4c3d-a7b8-271368a6482a, idx=0]: Workflow failed due to message status. Status:FAILED Message:({\'result\': \'Node 1b246f12-ba40-446d-a215-834b07d1a41f did not reach state "manageable", the state is "enroll", error: Failed to get power state for node 1b246f12-ba40-446d-a215-834b07d1a41f. Error: name \\\'sdk\\\' is not defined\'}, {\'result\': \'Node 7c0d081c-3c54-4657-adf7-42b04d240b20 did not reach state "manageable", the state is "enroll", error: Failed to get power state for node 7c0d081c-3c54-4657-adf7-42b04d240b20. Error: name \\\'sdk\\\' is not defined\'}, {\'result\': \'Node b866b636-52f4-4cd9-947e-2a572d02c474 did not reach state "manageable", the state is "enroll", error: Failed to get power state for node b866b636-52f4-4cd9-947e-2a572d02c474. Error: name \\\'sdk\\\' is not defined\'}, {\'result\': \'Node b8ea8681-9418-405c-aa0c-da5022acc160 did not reach state "manageable", the state is "enroll", error: Failed to get power state for node b8ea8681-9418-405c-aa0c-da5022acc160. Error: name \\\'sdk\\\' is not defined\'})\n', 'status': 'FAILED', 'message': [{'result': 'Node 1b246f12-ba40-446d-a215-834b07d1a41f did not reach state "manageable", the state is "enroll", error: Failed to get power state for node 1b246f12-ba40-446d-a215-834b07d1a41f. Error: name \'sdk\' is not defined'}, {'result': 'Node 7c0d081c-3c54-4657-adf7-42b04d240b20 did not reach state "manageable", the state is "enroll", error: Failed to get power state for node 7c0d081c-3c54-4657-adf7-42b04d240b20. Error: name \'sdk\' is not defined'}, {'result': 'Node b866b636-52f4-4cd9-947e-2a572d02c474 did not reach state "manageable", the state is "enroll", error: Failed to get power state for node b866b636-52f4-4cd9-947e-2a572d02c474. Error: name \'sdk\' is not defined'}, {'result': 'Node b8ea8681-9418-405c-aa0c-da5022acc160 did not reach state "manageable", the state is "enroll", error: Failed to get power state for node b8ea8681-9418-405c-aa0c-da5022acc160. Error: name \'sdk\' is not defined'}]}

--- Additional comment from Alexander Chuzhoy on 2019-06-18 20:43:34 UTC ---



--- Additional comment from Bob Fournier on 2019-06-19 14:08:04 UTC ---

We've verified that the python3-ovirt-engine-sdk4 is there in composes after 6/14 (at least)

(undercloud) [stack@undercloud-0 ~]$ sudo podman exec -it ironic_conductor rpm -qa | grep ovirt
python3-ovirt-engine-sdk4-4.2.9-3.el8ost.x86_64

I'm going to remove this a dup to the patch for the missing package so we can focus on the error message.

--- Additional comment from Bob Fournier on 2019-06-19 14:29:25 UTC ---

Related bug from osp-13 https://bugzilla.redhat.com/show_bug.cgi?id=1626341, however I don't think we need to restart ironic-conductor container in this case.

--- Additional comment from Lon Hohberger on 2019-06-19 18:15:48 UTC ---

python-ovirt-engine-sdk4-4.2.9-4.el8ost has been built which fixes the issue

--- Additional comment from Bob Fournier on 2019-06-19 18:22:27 UTC ---

Change to spec file.

diff --git a/python-ovirt-engine-sdk4.spec b/python-ovirt-engine-sdk4.spec
index dd2d8f0..52d9cab 100644
--- a/python-ovirt-engine-sdk4.spec
+++ b/python-ovirt-engine-sdk4.spec
@@ -3,7 +3,7 @@
 Name: python-ovirt-engine-sdk4
 Summary: Python SDK for version 4 of the oVirt Engine API
 Version: 4.2.9
-Release: 3%{?dist}
+Release: 4%{?dist}
 Group: Development/Languages
 License: ASL 2.0
 URL: http://ovirt.org/wiki/SDK
@@ -14,10 +14,6 @@ BuildRequires: libxml2-devel
 BuildRequires: python3-setuptools
 BuildRequires: python3-devel
 
-Requires: libxml2
-Requires: python3-pycurl
-Requires: python3-six
-
 %description
 This package contains the Python SDK for version 4 of the oVirt Engine
 API.
@@ -25,6 +21,9 @@ API.
 %package -n python3-ovirt-engine-sdk4
 Summary: Python SDK for version 4 of the oVirt Engine API
 Provides: python-ovirt-engine-sdk4
+Requires: libxml2
+Requires: python3-pycurl
+Requires: python3-six
 
 %description -n python3-ovirt-engine-sdk4
 This package contains the Python SDK for version 4 of the oVirt Engine
@@ -46,6 +45,9 @@ API.
 %{python3_sitearch}/*
 
 %changelog
+* Wed Jun 19 2019 Lon Hohberger <lon> - 4.2.9-4
+- Fix requirements
+
 * Tue Jun 4 2019 Lon Hohberger <lon> - 4.2.9-3
 - Port to RHEL8 / OpenStack Platform 15.0
 - Virtual provides python-ovirt-engine-sdk4

--- Additional comment from RHEL Product and Program Management on 2019-06-19 18:28:59 UTC ---

Please review this bug and update to a specific component according to the package in which the patch has been modified.

--- Additional comment from Bob Fournier on 2019-06-19 18:42:30 UTC ---

Temporarily removing blocker flag, will reinstate.

--- Additional comment from RHEL Product and Program Management on 2019-06-20 15:21:55 UTC ---

This bugzilla has been removed from the release since it  does not have an acked release flag. For details, see https://mojo.redhat.com/docs/DOC-1144661#jive_content_id_OSP_Release_Planning.'

--- Additional comment from RHEL Product and Program Management on 2019-06-20 15:22:39 UTC ---

This item has all 3-acks+; adding blocker+

--- Additional comment from RHEL Product and Program Management on 2019-06-20 15:22:39 UTC ---

This item has been properly Triaged and planned for the release, and Target Release is now set to match the release flag. For details, see https://mojo.redhat.com/docs/DOC-1144661#jive_content_id_OSP_Release_Planning

--- Additional comment from Scott Lewis on 2019-06-24 13:00:40 UTC ---

This item has been properly Triaged and planned for the appropriate release, and is being tagged for tracking.

--- Additional comment from errata-xmlrpc on 2019-06-27 17:12:22 UTC ---

Bug report changed to ON_QA status by Errata System.
A QE request has been submitted for advisory RHEA-2019:41562-03
https://errata.devel.redhat.com/advisory/41562

--- Additional comment from Alexander Chuzhoy on 2019-07-03 17:04:05 UTC ---

Verified:

Environment:
python3-ovirt-engine-sdk4-4.2.9-4.el8ost.x86_64

The reported issue doesn't reproduce.

Comment 3 Alexander Chuzhoy 2019-08-09 16:52:49 UTC
We need to document the need to install python-ovirt-engine-sdk4.x86_64 before running 'openstack undercloud install'.

See no mentioning of that here:
https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html-single/director_installation_and_usage/index#sect-Red_Hat_Virtualization

Comment 8 Alex McLeod 2019-11-13 11:26:36 UTC
Thanks Sasha.

Merged to 13.


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