Task "netconfig" fails on dpdk enabled nodes

Bug #1675435 reported by Sergii
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Critical
Fuel Sustaining

Bug Description

Detailed bug description:

Steps to reproduce:
 1. Create cluster (In my case there are two compute nodes)
 2. Enable DPDK on interface
 3. Deploy cluster

Expected results:
 Cluster deployed

Actual result:
 Deploy fails with " All nodes are finished. Failed tasks: Task[netconfig/1], Task[netconfig/3] Stopping the deployment process!"

Description of the environment:
 Fuel 10. Checked on build 1499 and 1507

Revision history for this message
Sergii (sgudz) wrote :
Changed in fuel:
assignee: nobody → Fuel for Openstack (fuel)
assignee: Fuel for Openstack (fuel) → nobody
tags: added: blocker-for-qa
Sergii (sgudz)
Changed in fuel:
assignee: nobody → Alexander Ignatov (aignatov)
importance: Undecided → Critical
Sergii (sgudz)
Changed in fuel:
assignee: Alexander Ignatov (aignatov) → MOS Neutron (mos-neutron)
Changed in fuel:
assignee: MOS Neutron (mos-neutron) → Fuel Sustaining (fuel-sustaining-team)
status: New → Confirmed
Revision history for this message
Michael Polenchuk (mpolenchuk) wrote :

There is no hiera cluster.yaml & node.yaml files in snapshot.

Moreover OpNFV project runs dpdk scenarios several times a day and this issue ain't reproducible:
https://build.opnfv.org/ci/view/fuel/job/fuel-os-nosdn-ovs-ha-baremetal-daily-danube/10/
https://build.opnfv.org/ci/view/fuel/job/fuel-os-nosdn-ovs-ha-baremetal-daily-danube/11/
https://build.opnfv.org/ci/view/fuel/job/fuel-os-nosdn-ovs-ha-baremetal-daily-master/251/
https://build.opnfv.org/ci/view/fuel/job/fuel-os-nosdn-ovs-ha-baremetal-daily-master/250/

Also all functional tests are passed (which includes tempest, rally & etc.)
plus benchmark suite is passed as well.

Changed in fuel:
status: Confirmed → Incomplete
Revision history for this message
Sergii (sgudz) wrote :

I found the reason for that. The root cause of deploying fail is that Fuel 10.x allows to start deploy with wrong node attributes configuration. For example, if you select 0 cpu for dpdk fuel will start deploy, but then fails due to lack of cpu for dpdk-lcore-mask

Changed in fuel:
status: Incomplete → Invalid
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.