Juniper Openstack

3.2.6 - RHOSP10 : Issue provisioning DPDK compute using ansible script

Bug #1724357 reported by Vivek
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Won't Fix
High
Michael Henkel
Juniper Openstack r5.0.0
R3.2
Won't Fix
High
Michael Henkel
Juniper Openstack r3.2.7.0
R4.0
Won't Fix
High
Michael Henkel
Juniper Openstack r4.0.3.0
R4.1
Won't Fix
High
Michael Henkel
Juniper Openstack r4.1.0.0-fcs "r4.1"
Trunk
Won't Fix
High
Michael Henkel
Juniper Openstack r5.0.0

Bug Description

Facing an issue with DPDK bring up for redhat in 3.2.6. The power state is going to none for DPDK compute.

Hypervisor: 10.87.67.44
Ansible directory: /root/vivek/contrail-ooo-deployer/

changed: [192.168.122.233] => (item=42aba8a8-c9cf-4fde-9803-406516d21975)
changed: [192.168.122.233] => (item=fd36d7bf-1c7b-4011-9eb9-97e22a25d457)
changed: [192.168.122.233] => (item=ab979bb5-2ce8-45ab-8e8d-6435e0091020)
changed: [192.168.122.233] => (item=56e46518-120a-43ea-8368-a28c933de6b8)
changed: [192.168.122.233] => (item=ff74b52a-af9c-4b48-b236-8c0daebae085)
changed: [192.168.122.233] => (item=35fea0e8-f023-4abc-96ff-e50041483a42)
changed: [192.168.122.233] => (item=e46f7570-ec03-4ad4-8d8f-597dfa8b05e6)
changed: [192.168.122.233] => (item=3c2f7f44-d2fd-422f-a589-9193615041c9)

TASK [undercloud_deployer : configure boot mode for ironic nodes] ***********************************************************************************************
fatal: [192.168.122.233]: FAILED! => {"changed": true, "cmd": "source /home/stack/stackrc &&\n /bin/openstack baremetal configure boot", "delta": "0:02:15.859783
", "end": "2017-10-16 18:09:24.628781", "failed": true, "rc": 1, "start": "2017-10-16 18:07:08.768998", "stderr": "Node ab979bb5-2ce8-45ab-8e8d-6435e0091020 powe
r state is in transition. Waiting up to 120 seconds for it to complete.\nTimed out waiting for node ab979bb5-2ce8-45ab-8e8d-6435e0091020 power state.", "stderr_l
ines": ["Node ab979bb5-2ce8-45ab-8e8d-6435e0091020 power state is in transition. Waiting up to 120 seconds for it to complete.", "Timed out waiting for node ab97
9bb5-2ce8-45ab-8e8d-6435e0091020 power state."], "stdout": "", "stdout_lines": []}
        to retry, use: --limit @/root/vivek/contrail-ooo-deployer/playbooks/start.retry

PLAY RECAP ******************************************************************************************************************************************************
192.168.122.233 : ok=83 changed=52 unreachable=0 failed=1
localhost : ok=8 changed=6 unreachable=0 failed=0

[stack@uc-newtonX ~]$ ironic node-list
+--------------------------------------+-----------------------------------------------+---------------+-------------+--------------------+-------------+
| UUID | Name | Instance UUID | Power State | Provisioning State | Maintenance |
+--------------------------------------+-----------------------------------------------+---------------+-------------+--------------------+-------------+
| 42aba8a8-c9cf-4fde-9803-406516d21975 | contrail-analytics-database-1-at-5b9s13-node4 | None | power off | available | False |
| fd36d7bf-1c7b-4011-9eb9-97e22a25d457 | compute-2-at-5b9s13-node3 | None | power off | available | False |
| ab979bb5-2ce8-45ab-8e8d-6435e0091020 | compute-dpdk-1-at-5b10s15-4 | None | None | available | False |
| 56e46518-120a-43ea-8368-a28c933de6b8 | compute-1-at-5b9s13-node3 | None | power off | available | False |
| ff74b52a-af9c-4b48-b236-8c0daebae085 | contrail-controller-1-at-5b9s13-node4 | None | power off | available | False |
| 35fea0e8-f023-4abc-96ff-e50041483a42 | contrail-analytics-1-at-5b9s13-node4 | None | power off | available | False |
| e46f7570-ec03-4ad4-8d8f-597dfa8b05e6 | compute-1-at-5b9s13-node4 | None | power off | available | False |
| 3c2f7f44-d2fd-422f-a589-9193615041c9 | control-1-at-5b9s13-node4 | None | power off | available | False |
+--------------------------------------+-----------------------------------------------+---------------+-------------+--------------------+-------------+

Created [stack@uc-newtonX ~]$/home/stack/dpdk.json to verify if the DPDK node boots up, it comes up fine.
[stack@uc-newtonX ~]$ cat dpdk.json
{
  "nodes": [
    {
      "mac": [
        "90:e2:ba:4c:67:3d"
      ],
      "name": "compute3-dpdk",
      "capabilities" : "profile:compute-dpdk",
      "pm_user": "admin",
      "pm_addr": "10.87.122.164",
      "pm_password": "admin",
      "pm_type": "pxe_ipmitool"
    }
  ]
}

See original description
Vivek (vivekgarg)
description: updated
summary: - 3.2.6 - RHOSP10 Issue provisioning DPDK compute using ansible script
+ 3.2.6 - RHOSP10 : Issue provisioning DPDK compute using ansible script
Jeba Paulaiyan (jebap)
tags: added: provisioning
tags: added: releasenote
Revision history for this message
Jeba Paulaiyan (jebap) wrote :

Notes for release notes:

While provisioning a RHOSP10 cluster with DPDK nodes, the DPDK node power state goes down during introspection stage. As a workaround, delete the DPDK nodes from Ironic configuration and re-add them with right configuration.

1. ironic node-delete <node name>
2. Create json file configuration shown in below example for all DPDK nodes

{
  "nodes": [
    {
      "mac": [
        "90:e2:ba:4c:67:3d"
      ],
      "name": "compute3-dpdk",
      "capabilities" : "profile:compute-dpdk",
      "pm_user": "admin",
      "pm_addr": "10.87.122.164",
      "pm_password": "admin",
      "pm_type": "pxe_ipmitool"
    }
  ]
}

3. openstack baremetal import --json <path to .json>
4. openstack baremetal introspection bulk start

Jeba Paulaiyan (jebap)
information type: Proprietary → Public
Jeba Paulaiyan (jebap)
tags: added: sanityblocker
Revision history for this message
Michael Henkel (mhenkel-3) wrote :

the dpdk node has to be configured correctly in:

[root@5b3s33 contrail-ooo-deployer]# cat inventory/group_vars/ironic_nodes.yml
---
ironic_nodes:
  contrail-dpdk-1-at-5b3s30:
    ip: 10.87.64.31
    mac: 52:54:00:16:54:d8
    role: control
    user: root
    password: c0ntrail123
    memory: 16348
    cpus: 4
    disk_gb: 40
    ipmi_driver: pxe_ipmitool

Revision history for this message
Michael Henkel (mhenkel-3) wrote :

the ansible playbooks are meant to be a help for generating the templates and have a reliable method for deploying.
They are NOT meant to block any release.

Jeba Paulaiyan (jebap)
Changed in juniperopenstack:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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