After oslo.messaging release Ironic gate is broken

Testing ironic master without oslo.messaging 1.12.0 - https://review.openstack.org/#/c/187699/1

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

My hypothesis is that ironic-conductor is seeing this issue because it is a server, but does also make outgoing calls and so it never creates a Client instance, and therefore the option isn't being registered. Since the option is needed by both the client and the server, it should be registered by both in oslo.messaging, so that's what the patch in comment #2 does. There's also a patch to ironic to instantiate a Client just to test the theory (https://review.openstack.org/#/c/187713), but we wouldn't want to land that patch.

http://logs.openstack.org/18/187718/1/check/check-tempest-dsvm-ironic-pxe_ssh/2bfa220/logs/screen-ir-cond.txt.gz?level=TRACE

http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiRXhjZXB0aW9uIGR1cmluZyBtZXNzYWdlIGhhbmRsaW5nOiBubyBzdWNoIG9wdGlvbjogcnBjX3Jlc3BvbnNlX3RpbWVvdXRcIiBBTkQgdGFnczpcInNjcmVlbi1pci1jb25kLnR4dFwiIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiI2MDQ4MDAiLCJncmFwaG1vZGUiOiJjb3VudCIsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sInN0YW1wIjoxNDMzMjc1MzEzMTU0fQ==

This is also hitting designate - see http://logs.openstack.org/28/181528/11/check/gate-designate-dsvm-powerdns/e9f5040/logs/screen-designate-central.txt.gz?level=ERROR#_2015-06-02_18_34_52_772

Reviewed: https://review.openstack.org/187722
Committed: https://git.openstack.org/cgit/openstack/oslo.messaging/commit/?id=887e5a042359ed2b424d6e079f13d460213eeff6
Submitter: Jenkins
Branch: master

commit 887e5a042359ed2b424d6e079f13d460213eeff6
Author: Doug Hellmann <email address hidden>
Date: Tue Jun 2 18:48:33 2015 +0000

    Ensure rpc_response_timeout is registered before using it

    The response code in the rabbit driver doesn't use a Client object, so
    the option is not being registered in servers that don't instantiate
    Client instances (ironic-conductor, for example).

    Change-Id: I7def5e6d4960938a17344db024585a0492d6969d
    Partial-bug: #1461182

This problem only appeared in oslo.messaging, and we have released a hacky fix. I'm leaving the bug open because I intend to produce a non-hacky fix as well.

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

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

commit a0b33a46598499c47ac90eba26f27bff4eab991c
Author: Doug Hellmann <email address hidden>
Date: Wed Jun 3 19:53:27 2015 +0000

    replace rpc_response_timeout use in rabbit driver

    The rabbit driver was using the rpc_response_timeout configuration
    option as a reconnect timeout value, even though the option was defined
    only in oslo_messaging.client and was not always being registered before
    being accessed. An earlier patch fixed this by registering the option
    here in the driver, too, but that breaks several levels of
    abstraction. This changes the driver to define a new option with the
    same default value, so that the driver is only using options it defines
    itself. It also removes the old hacky fix.

    Closes-bug: #1461182

    Change-Id: Ia96c815d157219e12a10d94b87b0156503369a6b