Importing nodes uses json file's pm_type instead of UI's dropdown value

Bug #1642663 reported by Dan Trainor
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Expired
Undecided
Unassigned

Bug Description

When importing nodes in to the UI, only two types of power management drivers are available in the drop-down box: pxe_ipmitool, pxe_ssh.

If nodes are registered from a previously defined json file, the value of the node's pm_type will be used instead of the value listed in the UI's power management dropdown configuration option.

For example, if pm_type in the json file is specified as pxe_drac, even though pxe_drac is not listed in the power management dropdown option, pxe_drac will still be used by the node in Ironic.

Attaching a screenshot of the UI "Register Nodes" screen, the json file used for import, and an 'ironic node-show' for one of the nodes.

Tags: ui
Revision history for this message
Dan Trainor (dtrainor) wrote :
Revision history for this message
Dan Trainor (dtrainor) wrote :

Tried to get screenshot showing the populated list of power managent drivers offered by the UI but that wasn't working.

The only available options are: pxe_ssh, pxe_ipmitool

Revision history for this message
Dan Trainor (dtrainor) wrote :

Output of ironic node-show:

[stack@rdo-ci-fx2-04-s8 ~]$ ironic node-show rdo-ci-fx2-05-s8.v102.rdoci.lab.eng.rdu.redhat.com | grep driver
| driver | pxe_drac |
| driver_info | {u'deploy_kernel': u'ac85f91d-2260-4b50-8974-38f71883842f', |
| driver_internal_info | {} |
[stack@rdo-ci-fx2-04-s8 ~]$

tags: added: ui
Revision history for this message
Dan Trainor (dtrainor) wrote :
Steven Hardy (shardy)
Changed in tripleo:
status: New → Triaged
importance: Undecided → Medium
milestone: none → ocata-2
Revision history for this message
Julie Pichon (jpichon) wrote :

Ironic has an API to list the available drivers:

$ ironic driver-list
+---------------------+-----------------------+
| Supported driver(s) | Active host(s) |
+---------------------+-----------------------+
| pxe_drac | localhost.localdomain |
| pxe_ilo | localhost.localdomain |
| pxe_ipmitool | localhost.localdomain |
| pxe_ssh | localhost.localdomain |
+---------------------+-----------------------+

And it looks like there's already a Mistral mapping for it as well:

http://git.openstack.org/cgit/openstack/mistral/tree/mistral/actions/openstack/mapping.json#n995
"driver_list": "driver.list"

Revision history for this message
Jiri Tomasek (jtomasek) wrote :

@Julie, note that we won't be able to use this until tripleo-common needs to do the instackenv file format conversion to ironic nodes format when registering nodes. Until then we have to hardcode list of supported drivers as tripleo-common needs to support conversion of those. By introduction of using ironic format in instackenv.json we'll be able to remove the conversion logic from tripleo-common (and TripleO UI) and allow user to set any ironic driver (and list drivers using ironic in TripleO UI, as well as list of driver specific properties)

See: https://etherpad.openstack.org/p/gui-ocata line 80

btw. no Mistral needed, we can call Ironic API directly...

Revision history for this message
Julie Pichon (jpichon) wrote :
Changed in tripleo:
milestone: ocata-2 → ocata-3
Changed in tripleo:
milestone: ocata-3 → pike-1
Changed in tripleo:
milestone: pike-1 → pike-2
Changed in tripleo:
milestone: pike-2 → pike-3
Changed in tripleo:
milestone: pike-3 → pike-rc1
Changed in tripleo:
milestone: pike-rc1 → queens-1
Changed in tripleo:
milestone: queens-1 → queens-2
Changed in tripleo:
milestone: queens-2 → queens-3
Changed in tripleo:
milestone: queens-3 → queens-rc1
Changed in tripleo:
milestone: queens-rc1 → rocky-1
Changed in tripleo:
milestone: rocky-1 → rocky-2
Changed in tripleo:
milestone: rocky-2 → rocky-3
Changed in tripleo:
milestone: rocky-3 → rocky-rc1
Changed in tripleo:
milestone: rocky-rc1 → stein-1
Changed in tripleo:
milestone: stein-1 → stein-2
Revision history for this message
Emilien Macchi (emilienm) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE

Changed in tripleo:
importance: Medium → Undecided
status: Triaged → Expired
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.