[tacker] Critical bug report and backport the fix
Hi tacker team,
As you know, new bug report #1990793 [1] related to K8s resource name and v2 API is submitted by Masaki. The bug will appear if K8s resource name contains `-`.
I think this is a critical issue because users often set resource names that contain `-`. Fortunately, the fix patch [2] has already been submitted.
I suggest that we should backport the fix patch to the stable/zed branch before Zed release. What do you think?
[1] https://bugs.launchpad.net/tacker/+bug/1990793 [2] https://review.opendev.org/c/openstack/tacker/+/859206
Yuta
Hi Yuta,
On 2022/09/26 16:57, Yuta Kazato wrote:
Hi tacker team,
As you know, new bug report #1990793 [1] related to K8s resource name and v2 API is submitted by Masaki. The bug will appear if K8s resource name contains `-`.
I think this is a critical issue because users often set resource names that contain `-`.
Agree.
Fortunately, the fix patch [2] has already been submitted.
I suggest that we should backport the fix patch to the stable/zed branch before Zed release. What do you think?
We should fix the issue in stable/zed, or this k8s support doesn't work for many usecases.
Yasufumi
[1] https://bugs.launchpad.net/tacker/+bug/1990793 [2] https://review.opendev.org/c/openstack/tacker/+/859206
Yuta
Hi Yuta and Yasufumi,
+1
And we have a patch for another critical bug related with pm interface. The bug report [1] and the fix patch [2] have been already posted. This patch also requires a backport to stable/zed.
[1] https://bugs.launchpad.net/tacker/+bug/1990828 [2] https://review.opendev.org/c/openstack/tacker/+/859377
Best Regards, Ueha
-----Original Message----- From: Yasufumi Ogawa yasufum.o@gmail.com Sent: Tuesday, September 27, 2022 10:42 AM To: openstack-discuss@lists.openstack.org Subject: Re: [tacker] Critical bug report and backport the fix
Hi Yuta,
On 2022/09/26 16:57, Yuta Kazato wrote:
Hi tacker team,
As you know, new bug report #1990793 [1] related to K8s resource name and v2 API is submitted by Masaki. The bug will appear if K8s resource name contains `-`.
I think this is a critical issue because users often set resource names that contain `-`.
Agree.
Fortunately, the fix patch [2] has already been submitted.
I suggest that we should backport the fix patch to the stable/zed branch before Zed release. What do you think?
We should fix the issue in stable/zed, or this k8s support doesn't work for many usecases.
Yasufumi
[1] https://bugs.launchpad.net/tacker/+bug/1990793 [2] https://review.opendev.org/c/openstack/tacker/+/859206
Yuta
participants (3)
-
ueha.ayumu@fujitsu.com
-
Yasufumi Ogawa
-
Yuta Kazato