[AMQP 1.0] vhost is ignored when using message routing

Bug #1700835 reported by Ken Giusti
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
oslo.messaging
Fix Released
Undecided
Ken Giusti

Bug Description

If a vhost is provided in the transport_url, then all RPC and Notification client's topics should be isolated to that vhost.

This is not the case for amqp1 - the vhost is ignored and all topics appear in the default namespace.

Ken Giusti (kgiusti)
Changed in oslo.messaging:
assignee: nobody → Ken Giusti (kgiusti)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to oslo.messaging (master)

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

Changed in oslo.messaging:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to oslo.messaging (master)

Reviewed: https://review.openstack.org/478537
Committed: https://git.openstack.org/cgit/openstack/oslo.messaging/commit/?id=263dce9ea8e52632cc07d101d1859034eb3943c7
Submitter: Jenkins
Branch: master

commit 263dce9ea8e52632cc07d101d1859034eb3943c7
Author: Kenneth Giusti <email address hidden>
Date: Tue Jun 27 18:06:16 2017 -0400

    Add support for virtual hosts

    Adds the 'pseudo_vhost' option which when enabled will incorporate the
    virtual host into the address semantics. This creates a 'subnet' like
    address space for each virtual host. Use this when the messaging bus
    does not provide virtual hosting support. It is enabled by default as
    to date none of the supported AMQP 1.0 message buses natively support
    virtual hosting.

    It also updates SSL support: SSL can either use the connection
    hostname or the vhost name when validating a server's
    certificate. This is controlled by the 'ssl_verify_vhost' option.
    This option is disabled by default as it requires both vhost and SNI
    support from the server. By default SSL will use the DNS name from
    the TransportURL.

    Change-Id: I49bb99d1b19e8e7e6fded76198da92ca5f7d65ab
    Closes-Bug: #1700835
    Partial-Bug: #1706987

Changed in oslo.messaging:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to oslo.messaging (stable/pike)

Fix proposed to branch: stable/pike
Review: https://review.openstack.org/502472

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to oslo.messaging (stable/pike)

Reviewed: https://review.openstack.org/502472
Committed: https://git.openstack.org/cgit/openstack/oslo.messaging/commit/?id=a07d852b237d229a0f4dd55fd83379c0581e44e9
Submitter: Jenkins
Branch: stable/pike

commit a07d852b237d229a0f4dd55fd83379c0581e44e9
Author: Kenneth Giusti <email address hidden>
Date: Tue Jun 27 18:06:16 2017 -0400

    Add support for virtual hosts

    Adds the 'pseudo_vhost' option which when enabled will incorporate the
    virtual host into the address semantics. This creates a 'subnet' like
    address space for each virtual host. Use this when the messaging bus
    does not provide virtual hosting support. It is enabled by default as
    to date none of the supported AMQP 1.0 message buses natively support
    virtual hosting.

    It also updates SSL support: SSL can either use the connection
    hostname or the vhost name when validating a server's
    certificate. This is controlled by the 'ssl_verify_vhost' option.
    This option is disabled by default as it requires both vhost and SNI
    support from the server. By default SSL will use the DNS name from
    the TransportURL.

    Change-Id: I49bb99d1b19e8e7e6fded76198da92ca5f7d65ab
    Closes-Bug: #1700835
    Partial-Bug: #1706987
    (cherry picked from commit 263dce9ea8e52632cc07d101d1859034eb3943c7)

tags: added: in-stable-pike
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/oslo.messaging 5.32.0

This issue was fixed in the openstack/oslo.messaging 5.32.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/oslo.messaging 5.30.1

This issue was fixed in the openstack/oslo.messaging 5.30.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.