Blazar-api fails to execute a call RPC

[Masahito Muroi]

When the blazar-manager receives a call RPC which has not supported keys in its context, the RPC request always fails. The RPC endpoint requires the PRC context to exactly match with supported keys.

The limitation is bit explicit. If oslo.message supports a new key in its context, Blazar needs to follow the change. For example, oslo.messaging added client_timeout parameter from 6.3.0. Blazar-api fails to execute all call RPC because the addition key appears in the context.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/572719
Committed: https://git.openstack.org/cgit/openstack/blazar/commit/?id=29e68d829535650e142f8a228cb016e82917979d
Submitter: Zuul
Branch: master

commit 29e68d829535650e142f8a228cb016e82917979d
Author: Masahito Muroi <email address hidden>
Date: Wed Jun 6 18:57:16 2018 +0900

    Ignore keys unsupported by BlazarContext in its creation

    BlazarContext class raises an error when the class is instantiated
    with unspported keys. The class is used as a context for RPC and
    the RPC is implemented over oslo.messaging. If oslo.messaging
    automatically adds a new key for the context, the RPC execution
    fails since the new key is unexpected by BlazarContext and it
    raises an error.

    This patch relaxes the limitations in BlazarContext. If unexpected
    keys are passed for the class instantiation, the class ignores the
    keys.

    Change-Id: Ibdca6eead0ee726bc10a07ee43e4ef10110d23e2
    Closes-Bug: #1775363

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/blazar 2.0.0.0b2 development milestone.