hook failed: neutron-plugin-api-relation-changed for neutron-openvswitch:neutron-plugin-api

Bug #1580271 reported by james beedy
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron-openvswitch (Juju Charms Collection)
Fix Released
High
James Page
Declined for Xenial by James Page

Bug Description

juju version -> tip
maas version -> tip

xenial/mitaka deploy fails due to hook error

hook failed: neutron-plugin-api-relation-changed for neutron-openvswitch:neutron-plugin-api

xenial-mitaka-bundle.yaml -> http://paste.ubuntu.com/16349582/

juju list-spaces -> http://paste.ubuntu.com/16349644/

juju status -> http://paste.ubuntu.com/16349665/

cat /var/log/neutron/neutron-l3-agent.log -> http://paste.ubuntu.com/16349698/

james beedy (jamesbeedy)
Changed in neutron-openvswitch (Juju Charms Collection):
assignee: nobody → OpenStack Charmers (openstack-charmers)
Revision history for this message
james beedy (jamesbeedy) wrote :

debugging neutron-openvswitch shows -> http://paste.ubuntu.com/16351894/

Revision history for this message
james beedy (jamesbeedy) wrote :

debugging neutron-plugin-api-relation-changed hook shows -> http://paste.ubuntu.com/16351958/

Changed in neutron-openvswitch (Juju Charms Collection):
importance: Undecided → Critical
Revision history for this message
james beedy (jamesbeedy) wrote :
Revision history for this message
james beedy (jamesbeedy) wrote :

From hook debugging, I feel like neutron-openvswitch is looking for a public network space? Should it have one?

James Page (james-page)
Changed in neutron-openvswitch (Juju Charms Collection):
importance: Critical → Undecided
assignee: OpenStack Charmers (openstack-charmers) → nobody
Revision history for this message
James Page (james-page) wrote :

No - it should only have a data binding - this problem looks specific to the DVR path - which is using resolve_address (slightly unexpected as that's for API services to use).

Changed in neutron-openvswitch (Juju Charms Collection):
milestone: none → 16.07
importance: Undecided → High
Revision history for this message
james beedy (jamesbeedy) wrote :

This bug only exists when 'enable-dvr' is set to 'true'.

Revision history for this message
james beedy (jamesbeedy) wrote :

@jamespage, replacing resolve_address with `get_host_ip(unit_get('private-address'))` worked as a quick fix for me. Not sure if thats what you are going for though...

James Page (james-page)
Changed in neutron-openvswitch (Juju Charms Collection):
status: New → Triaged
assignee: nobody → James Page (james-page)
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-neutron-openvswitch (master)

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

Revision history for this message
James Page (james-page) wrote :

Pushed proposed fix to master branch to the charm store for general testing:

  cs:~james-page/xenial/neutron-openvswitch-bug1580271

Once this lands into master, we'll sort out a backport to stable/16.04 as well.

James Page (james-page)
tags: added: juju-2.0
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-neutron-openvswitch (master)

Reviewed: https://review.openstack.org/319779
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-openvswitch/commit/?id=4cfdc89c56663d1db4a9f147e62fb1a59e3fceb1
Submitter: Jenkins
Branch: master

commit 4cfdc89c56663d1db4a9f147e62fb1a59e3fceb1
Author: James Page <email address hidden>
Date: Mon May 23 09:46:50 2016 +0100

    Drop use of resolve_address

    The shared secret context makes use of 'resolve_address' to
    resolve the local_ip address of the unit; the resulting
    value is not actually used in the metadata_agent.ini template
    and breaks under Juju 2.0, where resolve_address attempts
    to use network-get to resolve the public endpoint of the
    service using extra bindings (which are not relevant for this
    charm).

    Drop use of resolve address and tidy templates; the default
    127.0.0.1 address is fine for accessing the Nova Metadata
    service from the Neutron Metadata agent proxy.

    Change-Id: I03fc6d1c7c8ca832b02a7df5b1666c04aaecc589
    Close-Bug: 1580271

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-neutron-openvswitch (stable/16.04)

Fix proposed to branch: stable/16.04
Review: https://review.openstack.org/320817

James Page (james-page)
Changed in neutron-openvswitch (Juju Charms Collection):
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-neutron-openvswitch (stable/16.04)

Reviewed: https://review.openstack.org/320817
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-openvswitch/commit/?id=7730097ca9faa1be3bbee9da6421f0149889353e
Submitter: Jenkins
Branch: stable/16.04

commit 7730097ca9faa1be3bbee9da6421f0149889353e
Author: James Page <email address hidden>
Date: Mon May 23 09:46:50 2016 +0100

    Drop use of resolve_address

    The shared secret context makes use of 'resolve_address' to
    resolve the local_ip address of the unit; the resulting
    value is not actually used in the metadata_agent.ini template
    and breaks under Juju 2.0, where resolve_address attempts
    to use network-get to resolve the public endpoint of the
    service using extra bindings (which are not relevant for this
    charm).

    Drop use of resolve address and tidy templates; the default
    127.0.0.1 address is fine for accessing the Nova Metadata
    service from the Neutron Metadata agent proxy.

    Change-Id: I03fc6d1c7c8ca832b02a7df5b1666c04aaecc589
    Close-Bug: 1580271
    (cherry picked from commit 4cfdc89c56663d1db4a9f147e62fb1a59e3fceb1)

James Page (james-page)
Changed in neutron-openvswitch (Juju Charms Collection):
status: Fix Committed → Fix Released
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.