Fails to get dpdk feature enabled status for dpdk role.

Bug #1759296 reported by Jaganathan Palanisamy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Jaganathan Palanisamy

Bug Description

DPDK derive params workflow is not invoked and derived parameters for DPDK role when using docker service neutron-ovs-dpdk-agent.yaml file (tripleo-heat-templates/docker/services/neutron-ovs-dpdk-agent.yaml) for deployment.
_get_role_info workflow is failed to get dpdk feature enabled status for DPDK role.

Changed in tripleo:
assignee: nobody → Jaganathan Palanisamy (jaganathanp)
summary: - _get_role_info workflow fails to get dpdk feature when using docker
- service
+ get role info workflow fails to get dpdk feature when using docker
+ service neutron-ovs-dpdk-agent.yaml file
summary: - get role info workflow fails to get dpdk feature when using docker
- service neutron-ovs-dpdk-agent.yaml file
+ Fails to get dpdk feature enabled status for dpdk role.
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-common (master)

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

Changed in tripleo:
status: New → In Progress
Saravanan KR (skramaja)
Changed in tripleo:
importance: Undecided → High
milestone: none → rocky-1
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-common (master)

Reviewed: https://review.openstack.org/556887
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=13e1aca771a90adce5f9ecfc96af1dc3964b59a1
Submitter: Zuul
Branch: master

commit 13e1aca771a90adce5f9ecfc96af1dc3964b59a1
Author: Jaganathan Palanisamy <email address hidden>
Date: Tue Mar 27 11:07:35 2018 -0400

    Fails to get DPDK feature status.

    This change is to get dpdk feature status for a role
    when using docker service neutron-ovs-dpdk-agent.yaml file.
    DPDK derive params workflow is not invoked and derived
    parameters for dpdk role when using docker service
    neutron-ovs-dpdk-agent.yaml file for deployment.
    _get_role_info workflow is failed to get dpdk feature enabled
    status for dpdk role.

    Change-Id: I3e878e5dacf8e78710c892309b0d064506ec7345
    Closes-Bug: #1759296

Changed in tripleo:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-common (stable/queens)

Fix proposed to branch: stable/queens
Review: https://review.openstack.org/557646

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-common (stable/queens)

Reviewed: https://review.openstack.org/557646
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=18204f22b54864b2706a02610ef85533645408e4
Submitter: Zuul
Branch: stable/queens

commit 18204f22b54864b2706a02610ef85533645408e4
Author: Jaganathan Palanisamy <email address hidden>
Date: Tue Mar 27 11:07:35 2018 -0400

    Fails to get DPDK feature status.

    This change is to get dpdk feature status for a role
    when using docker service neutron-ovs-dpdk-agent.yaml file.
    DPDK derive params workflow is not invoked and derived
    parameters for dpdk role when using docker service
    neutron-ovs-dpdk-agent.yaml file for deployment.
    _get_role_info workflow is failed to get dpdk feature enabled
    status for dpdk role.

    Change-Id: I3e878e5dacf8e78710c892309b0d064506ec7345
    Closes-Bug: #1759296
    (cherry picked from commit 13e1aca771a90adce5f9ecfc96af1dc3964b59a1)

tags: added: in-stable-queens
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-common 9.0.0

This issue was fixed in the openstack/tripleo-common 9.0.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-common 8.6.1

This issue was fixed in the openstack/tripleo-common 8.6.1 release.

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.