[Tempest] [Blazar] Connection Refused Error 111 on Blazar tempest plugin
First time asking a question on the mailing list, I am trying to set up tempest against a quick start yoga (kolla-ansible) deployment with Keystone, Zun, Heat, Blazar, and Nova (1 controller, 1 compute). Default tempest tests are behaving as expected but when I try to run the blazar plugin tests they fail with Errno 111 Connection Refused. I ran a tcpdump on the tempest server side and saw no issues. Tcpdump on controller showed a reset when trying to connect to keystone. Is this an issue with blazar not being able to authenticate against the openstack deployment? The default tempest tests succeed so I don't think my admin_password admin_username etc. are incorrect. Kenny Tran Iowa State University Student Computer Engineer 515-441-5237 | trantk@iastate.edu
Hi Kenny, Do you have internal TLS enabled on your deployment? Support for internal TLS in Blazar was only added this year and would require custom configuration on Yoga. If not, could you please share your blazar.conf file after removing all sensitive information (passwords). Cheers, Pierre Riteau (priteau) On Wed, 3 Apr 2024 at 23:20, Tran, Kenny <trantk@iastate.edu> wrote:
First time asking a question on the mailing list, I am trying to set up tempest against a quick start yoga (kolla-ansible) deployment with Keystone, Zun, Heat, Blazar, and Nova (1 controller, 1 compute). Default tempest tests are behaving as expected but when I try to run the blazar plugin tests they fail with Errno 111 Connection Refused.
I ran a tcpdump on the tempest server side and saw no issues. Tcpdump on controller showed a reset when trying to connect to keystone. Is this an issue with blazar not being able to authenticate against the openstack deployment? The default tempest tests succeed so I don't think my admin_password admin_username etc. are incorrect.
Kenny Tran Iowa State University Student Computer Engineer 515-441-5237 | trantk@iastate.edu
participants (2)
-
Pierre Riteau
-
Tran, Kenny