deployment can't be started because of KeyError: u'dpdk'

Bug #1616119 reported by Ivan Berezovskiy
30
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Committed
High
Ivan Berezovskiy
Mitaka
Fix Released
High
Fuel Sustaining

Bug Description

Steps to reproduce:
Deploy 9.0 environment - it was successful
Update master node (nailgun, astute in particular)
Try to update the cluster with redeploy-command

Expected result:
Re-deployment is successful

Actual result:
Re-deployment can't be started. Error message in the UI:
KeyError: u'dpdk'

Whole trace from nailgun app.log:
http://paste.openstack.org/show/562492/

Problem is in https://github.com/openstack/fuel-library/blob/stable/mitaka/deployment/puppet/osnailyfacter/modular/netconfig/tasks.yaml#L39:

we should use $.get('dpkg') instead of $.dpdk

Tags: area-library
no longer affects: fuel/newton
tags: added: area-library
summary: - deployment can't start because of KeyError: u'dpdk'
+ deployment can't be started because of KeyError: u'dpdk'
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-library (master)

Fix proposed to branch: master
Review: https://review.openstack.org/359324

Changed in fuel:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-library (stable/mitaka)

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/359326

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-library (master)

Reviewed: https://review.openstack.org/359324
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=a08c3406135bc13be2d555f3ecd21ff3de55297b
Submitter: Jenkins
Branch: master

commit a08c3406135bc13be2d555f3ecd21ff3de55297b
Author: iberezovskiy <email address hidden>
Date: Tue Aug 23 19:23:34 2016 +0300

    Use safe way to get dpdk value

    Change-Id: Icd3b0d910be4f0c8852f957e4ccf1ee55b9f32df
    Closes-bug: #1616119

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-library (stable/mitaka)

Reviewed: https://review.openstack.org/359326
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=91e13c2c468d00b3a09c00b5c0e6c51b445b314d
Submitter: Jenkins
Branch: stable/mitaka

commit 91e13c2c468d00b3a09c00b5c0e6c51b445b314d
Author: iberezovskiy <email address hidden>
Date: Tue Aug 23 19:23:34 2016 +0300

    Use safe way to get dpdk value

    Change-Id: Icd3b0d910be4f0c8852f957e4ccf1ee55b9f32df
    Closes-bug: #1616119

tags: added: on-verification
Revision history for this message
Kristina Berezovskaia (kkuznetsova) wrote :

Verify on
CUSTOM_VERSION=snapshot #208
MAGNET_LINK=magnet:?xt=urn:btih:bfec808dd71ff42c5613a3527733d9012bb1fabc&dn=MirantisOpenStack-9.0.iso&tr=http%3A%2F%2Ftracker01-bud.infra.mirantis.net%3A8080%2Fannounce&tr=http%3A%2F%2Ftracker01-scc.infra.mirantis.net%3A8080%2Fannounce&tr=http%3A%2F%2Ftracker01-msk.infra.mirantis.net%3A8080%2Fannounce&ws=http%3A%2F%2Fvault.infra.mirantis.net%2FMirantisOpenStack-9.0.iso
FUEL_QA_COMMIT=0c21907598acb1da13a03183888d96e1313b74c9
UBUNTU_MIRROR_ID=ubuntu-2016-08-03-174238
CENTOS_MIRROR_ID=centos-7.2.1511-2016-05-31-083834
MOS_UBUNTU_MIRROR_ID=9.0-2016-09-01-112324
MOS_CENTOS_OS_MIRROR_ID=os-2016-06-23-135731
MOS_CENTOS_PROPOSED_MIRROR_ID=proposed-2016-09-01-112324
MOS_CENTOS_UPDATES_MIRROR_ID=updates-2016-06-23-135916
MOS_CENTOS_HOLDBACK_MIRROR_ID=holdback-2016-06-23-140047
MOS_CENTOS_HOTFIX_MIRROR_ID=hotfix-2016-07-18-162958
MOS_CENTOS_SECURITY_MIRROR_ID=security-2016-06-23-140002

I deployed env, that start task fuel redeploy-changes --env 1
End redeployed succesfully without errors

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/fuel-library 10.0.0rc1

This issue was fixed in the openstack/fuel-library 10.0.0rc1 release candidate.

Revision history for this message
Pavel (p.petrov) wrote :

I faced exactly the same situation while deploying 9.2 (#430) on pure 9.0(#495) baremetal cluster.

Here is the 1-st (in the messages sequence) error's trace:
http://paste.openstack.org/show/586946/

and here is the consequent error's trace:
http://paste.openstack.org/show/586947/

Revision history for this message
Timur Nurlygayanov (tnurlygayanov) wrote :

The issue was fixed and verified on MOS 9.1 but we reopened it for 9.2 based on the previous comment.

Revision history for this message
Rudy McComb (rmccomb) wrote :

This issue affected me too.

The solution is

on master node:

grep -irn '\.dpdk' /etc/puppet/modules
change .dpdk to .get('dpdk’)

fuel rel --sync-deployment-tasks --dir /etc/puppet

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/fuel-library 10.0.0

This issue was fixed in the openstack/fuel-library 10.0.0 release.

Revision history for this message
Vladimir Kuklin (vkuklin) wrote :

This issue has surely been fixed in 9.1 https://github.com/openstack/fuel-library/commit/a08c3406135bc13be2d555f3ecd21ff3de55297b - the traceback above shows that the fix was not applied to the environment

tags: removed: on-verification
tags: added: on-verification
Revision history for this message
TatyanaGladysheva (tgladysheva) wrote :

Verified on 9.2 snapshot #610.

tags: removed: on-verification
Revision history for this message
Roman Rufanov (rrufanov) wrote :

downloaded ISO, added just a Controller to new env, then while adding Compute got the error "u'dpdk'".

Revision history for this message
Oleksii Aleksieiev (alexzzman) wrote :

hello. even if you apply the fix to files by installing the 9.2 the environments that were created prior to fix have to be updated separately.

fuel env --env <Env_ID> --deployment-tasks --download

fix the lines in cluster_1/deployment_tasks.yaml file.

fuel env --env <Env_ID> --deployment-tasks --upload

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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