Public bug reported: Keystone supports notifications via oslo.messaging. Included with oslo.messaging notifications is the ability to emit messages using AMQP (e.g., rabbitmq).
Keystone uses notification extensively in its API to signal when resources are modified (creating, updating, or deleting users, projects, domains, role assignments, etc). If keystone is configured to use AMQP for notifications but the AMQP server isn't reachable, keystone-manage will hang. Steps to reproduce: 1. install a fresh devstack with keystone and rabbit as enabled services 2. configure keystone to emit messages using the messagingv2 driver and put a typo in the connection string [oslo_messaging_notifications] transport_url = rabbit://stackrabbit:[email protected]:5672/ driver = messagingv2 3. restart keystone 4. run keystone-manage bootstrap --bootstrap-password $password You'd expect keystone-manage to handle connections with rabbit gracefully but it hangs. https://pasted.tech/pastes/2a87e13e2e9e7323a93a14419ef6ebf55881621e.raw ** Affects: keystone Importance: Undecided Status: New ** Description changed: Keystone supports notifications via oslo.messaging. Included with oslo.messaging notifications is the ability to emit messages using AMQP (e.g., rabbitmq). Keystone uses notification extensively in its API to signal when resources are modified (creating, updating, or deleting users, projects, domains, role assignments, etc). If keystone is configured to use AMQP for notifications but the AMQP server isn't reachable, keystone-manage will hang. Steps to reproduce: 1. install a fresh devstack with keystone and rabbit as enabled services - 2. configure keystone to emit messages using the messagingv2 driver - 3. shut down rabbit with `systemctl` or put a type in keystone's rabbit connection string - 4. restart keystone - 5 run keystone-manage bootstrap --bootstrap-password $password + 2. configure keystone to emit messages using the messagingv2 driver and put a typo in the connection string + + [oslo_messaging_notifications] + transport_url = rabbit://stackrabbit:[email protected]:5672/ + driver = messagingv2 + + 3. restart keystone + 4. run keystone-manage bootstrap --bootstrap-password $password You'd expect keystone-manage to handle connections with rabbit gracefully but it hangs. https://pasted.tech/pastes/2a87e13e2e9e7323a93a14419ef6ebf55881621e.raw -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1845718 Title: keystone-manage hangs when the AMQP server is down Status in OpenStack Identity (keystone): New Bug description: Keystone supports notifications via oslo.messaging. Included with oslo.messaging notifications is the ability to emit messages using AMQP (e.g., rabbitmq). Keystone uses notification extensively in its API to signal when resources are modified (creating, updating, or deleting users, projects, domains, role assignments, etc). If keystone is configured to use AMQP for notifications but the AMQP server isn't reachable, keystone-manage will hang. Steps to reproduce: 1. install a fresh devstack with keystone and rabbit as enabled services 2. configure keystone to emit messages using the messagingv2 driver and put a typo in the connection string [oslo_messaging_notifications] transport_url = rabbit://stackrabbit:[email protected]:5672/ driver = messagingv2 3. restart keystone 4. run keystone-manage bootstrap --bootstrap-password $password You'd expect keystone-manage to handle connections with rabbit gracefully but it hangs. https://pasted.tech/pastes/2a87e13e2e9e7323a93a14419ef6ebf55881621e.raw To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1845718/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
