Yes - this is absolutely a bug. The underlying issue is that while we create proxy objects for each official type and then also add them to the connection for every alias so that both:
conn.messaging.messages()
and
conn.message.messages()
work ... the creation of the keystoneauth Adapter object is not honoring finding services by alias in the catalog.
https://review.openstack.org/#/c/544356/ should address this, although it needs a few more hours work before it'll be ready to land. Ultimately, that patch should be considered a workaround, and the actual place this should be solved is in keystoneauth ... https://review.openstack.org/#/c/484341/ is a patch that does that which needs to be re-done. However, this fix needs to be put in place and then backported to stable/queens in SDK since we can't get it fixed in keystoneauth for queens (is a new ksa feature)
Yes - this is absolutely a bug. The underlying issue is that while we create proxy objects for each official type and then also add them to the connection for every alias so that both:
conn. messaging. messages( )
and
conn. message. messages( )
work ... the creation of the keystoneauth Adapter object is not honoring finding services by alias in the catalog.
https:/ /review. openstack. org/#/c/ 544356/ should address this, although it needs a few more hours work before it'll be ready to land. Ultimately, that patch should be considered a workaround, and the actual place this should be solved is in keystoneauth ... https:/ /review. openstack. org/#/c/ 484341/ is a patch that does that which needs to be re-done. However, this fix needs to be put in place and then backported to stable/queens in SDK since we can't get it fixed in keystoneauth for queens (is a new ksa feature)