[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#987237: marked as done (unblock: openstack-cluster-installer/40.1)

Your message dated Tue, 20 Apr 2021 20:19:44 +0000
with message-id <E1lYwqW-0005i4-My@respighi.debian.org>
and subject line unblock openstack-cluster-installer
has caused the Debian Bug report #987237,
regarding unblock: openstack-cluster-installer/40.1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
987237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987237
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Please unblock package openstack-cluster-installer

tl;dr: the swiftproxy node HAProxy configuration was wrong before
40.1 as it was still a pre-HAProxy 2.1 syntax.

A bit of openstack-cluster-installer internals:
-----------------------------------------------
While I did correct the haproxy configuration for the newer
version of haproxy (ie: >= 2.1) in controller.pp, the swiftproxy.pp
wasn't corrected. This went undetected because it's possible with
OCI to use only the haproxy in controller.pp. Though as soon as one
sets a custom URL for the swift proxy so that clients reach the
haproxy of the proxies, the puppet run fails in Bullseye.

Please unblock openstack-cluster-installer/40.1 to fix this.
Debdiff attached.

Cheers,

Thomas Goirand (zigo)

--- End Message ---
--- Begin Message --- 
Unblocked.

--- End Message ---
Reply to: