| 2018-11-19 21:58:24 |
Jonathan Rosser |
bug |
|
|
added bug |
| 2018-11-20 11:30:33 |
Karl Stenerud |
haproxy (Ubuntu): status |
New |
Incomplete |
|
| 2018-11-21 08:33:24 |
Karl Stenerud |
haproxy (Ubuntu): status |
Incomplete |
Triaged |
|
| 2018-11-21 08:35:12 |
Karl Stenerud |
haproxy (Ubuntu): importance |
Undecided |
High |
|
| 2018-11-22 16:31:51 |
Robie Basak |
tags |
|
bitesize server-next |
|
| 2018-11-22 16:33:13 |
Robie Basak |
nominated for series |
|
Ubuntu Bionic |
|
| 2018-11-22 16:33:13 |
Robie Basak |
bug task added |
|
haproxy (Ubuntu Bionic) |
|
| 2018-11-22 16:33:19 |
Robie Basak |
haproxy (Ubuntu Bionic): status |
New |
Triaged |
|
| 2018-11-23 10:17:43 |
Christian Ehrhardt |
bug |
|
|
added subscriber Ubuntu Server |
| 2019-01-23 19:20:50 |
Andreas Hasenack |
nominated for series |
|
Ubuntu Cosmic |
|
| 2019-01-23 19:20:50 |
Andreas Hasenack |
bug task added |
|
haproxy (Ubuntu Cosmic) |
|
| 2019-01-23 19:21:21 |
Andreas Hasenack |
haproxy (Ubuntu): status |
Triaged |
Fix Released |
|
| 2019-01-23 19:21:25 |
Andreas Hasenack |
haproxy (Ubuntu Cosmic): status |
New |
Triaged |
|
| 2019-01-23 19:21:29 |
Andreas Hasenack |
haproxy (Ubuntu Bionic): importance |
Undecided |
High |
|
| 2019-01-23 19:21:31 |
Andreas Hasenack |
haproxy (Ubuntu Cosmic): importance |
Undecided |
High |
|
| 2019-01-23 19:41:02 |
Andreas Hasenack |
haproxy (Ubuntu Bionic): assignee |
|
Andreas Hasenack (ahasenack) |
|
| 2019-01-23 19:41:04 |
Andreas Hasenack |
haproxy (Ubuntu Cosmic): assignee |
|
Andreas Hasenack (ahasenack) |
|
| 2019-01-23 19:41:07 |
Andreas Hasenack |
haproxy (Ubuntu Bionic): status |
Triaged |
In Progress |
|
| 2019-01-23 19:41:09 |
Andreas Hasenack |
haproxy (Ubuntu Cosmic): status |
Triaged |
In Progress |
|
| 2019-01-24 19:05:58 |
Andreas Hasenack |
description |
This fault was reported via the haproxy mailing list https://www.mail-archive.com/haproxy@formilux.org/msg31749.html
And then patched in the haproxy code here https://github.com/haproxy/haproxy/commit/52dabbc4fad338233c7f0c96f977a43f8f81452a
Without this patch haproxy is not functional on aarch64/arm64. Experimental deployments of openstack-ansible on arm64 fail because of this bug, and without a fix applied to the ubuntu bionic packages we cannot proceed further as the openstack CI only installs the upstream ubuntu distribution packages. |
[Impact]
* An explanation of the effects of the bug on users and
* justification for backporting the fix to the stable release.
* In addition, it is helpful, but not required, to include an
explanation of how the upload fixes this bug.
[Test Case]
* detailed instructions how to reproduce the bug
* these should allow someone who is not familiar with the affected
package to reproduce the bug and verify that the updated package fixes
the problem.
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
This fault was reported via the haproxy mailing list https://www.mail-archive.com/haproxy@formilux.org/msg31749.html
And then patched in the haproxy code here https://github.com/haproxy/haproxy/commit/52dabbc4fad338233c7f0c96f977a43f8f81452a
Without this patch haproxy is not functional on aarch64/arm64. Experimental deployments of openstack-ansible on arm64 fail because of this bug, and without a fix applied to the ubuntu bionic packages we cannot proceed further as the openstack CI only installs the upstream ubuntu distribution packages. |
|
| 2019-01-24 19:26:42 |
Andreas Hasenack |
description |
[Impact]
* An explanation of the effects of the bug on users and
* justification for backporting the fix to the stable release.
* In addition, it is helpful, but not required, to include an
explanation of how the upload fixes this bug.
[Test Case]
* detailed instructions how to reproduce the bug
* these should allow someone who is not familiar with the affected
package to reproduce the bug and verify that the updated package fixes
the problem.
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
This fault was reported via the haproxy mailing list https://www.mail-archive.com/haproxy@formilux.org/msg31749.html
And then patched in the haproxy code here https://github.com/haproxy/haproxy/commit/52dabbc4fad338233c7f0c96f977a43f8f81452a
Without this patch haproxy is not functional on aarch64/arm64. Experimental deployments of openstack-ansible on arm64 fail because of this bug, and without a fix applied to the ubuntu bionic packages we cannot proceed further as the openstack CI only installs the upstream ubuntu distribution packages. |
[Impact]
* An explanation of the effects of the bug on users and
* justification for backporting the fix to the stable release.
* In addition, it is helpful, but not required, to include an
explanation of how the upload fixes this bug.
[Test Case]
* install haproxy and apache in an up-to-date ubuntu release you are testing, in an arm64 system:
sudo apt update && sudo apt dist-upgrade -y && sudo apt install haproxy apache2 -y
* Create /etc/haproxy/haproxy.cfg with the following contents:
global
chroot /var/lib/haproxy
user haproxy
group haproxy
daemon
maxconn 4096
defaults
log global
option dontlognull
option redispatch
retries 3
timeout client 50s
timeout connect 10s
timeout http-request 5s
timeout server 50s
maxconn 4096
frontend test-front
bind *:8080
mode http
default_backend test-back
backend test-back
mode http
stick store-request src
stick-table type ip size 256k expire 30m
server test-1 localhost:80
* in one terminal, keep tailing the (still nonexistent) haproxy log file:
tail -F /var/log/haproxy.log
* in another terminal, restart haproxy and tail its logs:
sudo systemctl restart haproxy
tail -f /var/log/haproxy.log
* in another terminal, start haproxy:
sudo systemctl restart haproxy
* The haproxy log fill become live, and already show errors:
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [WARNING] 023/191958 (2286) : Exiting Master process...
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [ALERT] 023/191958 (2286) : Current worker 2287 exited with code 143
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [WARNING] 023/191958 (2286) : All workers exited. Exiting... (143)
* Run wget to try to fetch the apache frontpage, via haproxy, limited to one attempt. It will fail:
$ wget -t1 http://localhost:8080
--2019-01-24 19:23:51-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... No data received.
Giving up.
$ echo $?
4
* the haproxy logs will show errors:
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [ALERT] 023/192351 (6411) : Current worker 6412 exited with code 135
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [ALERT] 023/192351 (6411) : exit-on-failure: killing every workers with SIGTERM
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [WARNING] 023/192351 (6411) : All workers exited. Exiting... (135)
* Update the haproxy package and try the wget one more time. This time it will work, and the haproxy logs will stay silent:
wget -t1 http://localhost:8080
--2019-01-24 19:26:14-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... 200 OK
Length: 10918 (11K) [text/html]
Saving to: ‘index.html’
index.html 100%[================================================================================================================================>] 10.66K --.-KB/s in 0s
2019-01-24 19:26:14 (75.3 MB/s) - ‘index.html’ saved [10918/10918]
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
This fault was reported via the haproxy mailing list https://www.mail-archive.com/haproxy@formilux.org/msg31749.html
And then patched in the haproxy code here https://github.com/haproxy/haproxy/commit/52dabbc4fad338233c7f0c96f977a43f8f81452a
Without this patch haproxy is not functional on aarch64/arm64. Experimental deployments of openstack-ansible on arm64 fail because of this bug, and without a fix applied to the ubuntu bionic packages we cannot proceed further as the openstack CI only installs the upstream ubuntu distribution packages. |
|
| 2019-01-24 19:34:03 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/haproxy/+git/haproxy/+merge/362209 |
|
| 2019-01-24 19:39:36 |
Andreas Hasenack |
description |
[Impact]
* An explanation of the effects of the bug on users and
* justification for backporting the fix to the stable release.
* In addition, it is helpful, but not required, to include an
explanation of how the upload fixes this bug.
[Test Case]
* install haproxy and apache in an up-to-date ubuntu release you are testing, in an arm64 system:
sudo apt update && sudo apt dist-upgrade -y && sudo apt install haproxy apache2 -y
* Create /etc/haproxy/haproxy.cfg with the following contents:
global
chroot /var/lib/haproxy
user haproxy
group haproxy
daemon
maxconn 4096
defaults
log global
option dontlognull
option redispatch
retries 3
timeout client 50s
timeout connect 10s
timeout http-request 5s
timeout server 50s
maxconn 4096
frontend test-front
bind *:8080
mode http
default_backend test-back
backend test-back
mode http
stick store-request src
stick-table type ip size 256k expire 30m
server test-1 localhost:80
* in one terminal, keep tailing the (still nonexistent) haproxy log file:
tail -F /var/log/haproxy.log
* in another terminal, restart haproxy and tail its logs:
sudo systemctl restart haproxy
tail -f /var/log/haproxy.log
* in another terminal, start haproxy:
sudo systemctl restart haproxy
* The haproxy log fill become live, and already show errors:
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [WARNING] 023/191958 (2286) : Exiting Master process...
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [ALERT] 023/191958 (2286) : Current worker 2287 exited with code 143
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [WARNING] 023/191958 (2286) : All workers exited. Exiting... (143)
* Run wget to try to fetch the apache frontpage, via haproxy, limited to one attempt. It will fail:
$ wget -t1 http://localhost:8080
--2019-01-24 19:23:51-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... No data received.
Giving up.
$ echo $?
4
* the haproxy logs will show errors:
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [ALERT] 023/192351 (6411) : Current worker 6412 exited with code 135
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [ALERT] 023/192351 (6411) : exit-on-failure: killing every workers with SIGTERM
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [WARNING] 023/192351 (6411) : All workers exited. Exiting... (135)
* Update the haproxy package and try the wget one more time. This time it will work, and the haproxy logs will stay silent:
wget -t1 http://localhost:8080
--2019-01-24 19:26:14-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... 200 OK
Length: 10918 (11K) [text/html]
Saving to: ‘index.html’
index.html 100%[================================================================================================================================>] 10.66K --.-KB/s in 0s
2019-01-24 19:26:14 (75.3 MB/s) - ‘index.html’ saved [10918/10918]
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
This fault was reported via the haproxy mailing list https://www.mail-archive.com/haproxy@formilux.org/msg31749.html
And then patched in the haproxy code here https://github.com/haproxy/haproxy/commit/52dabbc4fad338233c7f0c96f977a43f8f81452a
Without this patch haproxy is not functional on aarch64/arm64. Experimental deployments of openstack-ansible on arm64 fail because of this bug, and without a fix applied to the ubuntu bionic packages we cannot proceed further as the openstack CI only installs the upstream ubuntu distribution packages. |
[Impact]
* An explanation of the effects of the bug on users and
* justification for backporting the fix to the stable release.
* In addition, it is helpful, but not required, to include an
explanation of how the upload fixes this bug.
[Test Case]
* install haproxy and apache in an up-to-date ubuntu release you are testing, in an arm64 system:
sudo apt update && sudo apt dist-upgrade -y && sudo apt install haproxy apache2 -y
* Create /etc/haproxy/haproxy.cfg with the following contents:
global
chroot /var/lib/haproxy
user haproxy
group haproxy
daemon
maxconn 4096
defaults
log global
option dontlognull
option redispatch
retries 3
timeout client 50s
timeout connect 10s
timeout http-request 5s
timeout server 50s
maxconn 4096
frontend test-front
bind *:8080
mode http
default_backend test-back
backend test-back
mode http
stick store-request src
stick-table type ip size 256k expire 30m
server test-1 localhost:80
* in one terminal, keep tailing the (still nonexistent) haproxy log file:
tail -F /var/log/haproxy.log
* in another terminal, restart haproxy:
sudo systemctl restart haproxy
* in another terminal, start haproxy:
sudo systemctl restart haproxy
* The haproxy log fill become live, and already show errors:
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [WARNING] 023/191958 (2286) : Exiting Master process...
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [ALERT] 023/191958 (2286) : Current worker 2287 exited with code 143
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [WARNING] 023/191958 (2286) : All workers exited. Exiting... (143)
* Run wget to try to fetch the apache frontpage, via haproxy, limited to one attempt. It will fail:
$ wget -t1 http://localhost:8080
--2019-01-24 19:23:51-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... No data received.
Giving up.
$ echo $?
4
* the haproxy logs will show errors:
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [ALERT] 023/192351 (6411) : Current worker 6412 exited with code 135
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [ALERT] 023/192351 (6411) : exit-on-failure: killing every workers with SIGTERM
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [WARNING] 023/192351 (6411) : All workers exited. Exiting... (135)
* Update the haproxy package and try the wget one more time. This time it will work, and the haproxy logs will stay silent:
wget -t1 http://localhost:8080
--2019-01-24 19:26:14-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... 200 OK
Length: 10918 (11K) [text/html]
Saving to: ‘index.html’
index.html 100%[================================================================================================================================>] 10.66K --.-KB/s in 0s
2019-01-24 19:26:14 (75.3 MB/s) - ‘index.html’ saved [10918/10918]
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
This fault was reported via the haproxy mailing list https://www.mail-archive.com/haproxy@formilux.org/msg31749.html
And then patched in the haproxy code here https://github.com/haproxy/haproxy/commit/52dabbc4fad338233c7f0c96f977a43f8f81452a
Without this patch haproxy is not functional on aarch64/arm64. Experimental deployments of openstack-ansible on arm64 fail because of this bug, and without a fix applied to the ubuntu bionic packages we cannot proceed further as the openstack CI only installs the upstream ubuntu distribution packages. |
|
| 2019-01-24 19:39:58 |
Andreas Hasenack |
description |
[Impact]
* An explanation of the effects of the bug on users and
* justification for backporting the fix to the stable release.
* In addition, it is helpful, but not required, to include an
explanation of how the upload fixes this bug.
[Test Case]
* install haproxy and apache in an up-to-date ubuntu release you are testing, in an arm64 system:
sudo apt update && sudo apt dist-upgrade -y && sudo apt install haproxy apache2 -y
* Create /etc/haproxy/haproxy.cfg with the following contents:
global
chroot /var/lib/haproxy
user haproxy
group haproxy
daemon
maxconn 4096
defaults
log global
option dontlognull
option redispatch
retries 3
timeout client 50s
timeout connect 10s
timeout http-request 5s
timeout server 50s
maxconn 4096
frontend test-front
bind *:8080
mode http
default_backend test-back
backend test-back
mode http
stick store-request src
stick-table type ip size 256k expire 30m
server test-1 localhost:80
* in one terminal, keep tailing the (still nonexistent) haproxy log file:
tail -F /var/log/haproxy.log
* in another terminal, restart haproxy:
sudo systemctl restart haproxy
* in another terminal, start haproxy:
sudo systemctl restart haproxy
* The haproxy log fill become live, and already show errors:
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [WARNING] 023/191958 (2286) : Exiting Master process...
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [ALERT] 023/191958 (2286) : Current worker 2287 exited with code 143
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [WARNING] 023/191958 (2286) : All workers exited. Exiting... (143)
* Run wget to try to fetch the apache frontpage, via haproxy, limited to one attempt. It will fail:
$ wget -t1 http://localhost:8080
--2019-01-24 19:23:51-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... No data received.
Giving up.
$ echo $?
4
* the haproxy logs will show errors:
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [ALERT] 023/192351 (6411) : Current worker 6412 exited with code 135
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [ALERT] 023/192351 (6411) : exit-on-failure: killing every workers with SIGTERM
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [WARNING] 023/192351 (6411) : All workers exited. Exiting... (135)
* Update the haproxy package and try the wget one more time. This time it will work, and the haproxy logs will stay silent:
wget -t1 http://localhost:8080
--2019-01-24 19:26:14-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... 200 OK
Length: 10918 (11K) [text/html]
Saving to: ‘index.html’
index.html 100%[================================================================================================================================>] 10.66K --.-KB/s in 0s
2019-01-24 19:26:14 (75.3 MB/s) - ‘index.html’ saved [10918/10918]
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
This fault was reported via the haproxy mailing list https://www.mail-archive.com/haproxy@formilux.org/msg31749.html
And then patched in the haproxy code here https://github.com/haproxy/haproxy/commit/52dabbc4fad338233c7f0c96f977a43f8f81452a
Without this patch haproxy is not functional on aarch64/arm64. Experimental deployments of openstack-ansible on arm64 fail because of this bug, and without a fix applied to the ubuntu bionic packages we cannot proceed further as the openstack CI only installs the upstream ubuntu distribution packages. |
[Impact]
* An explanation of the effects of the bug on users and
* justification for backporting the fix to the stable release.
* In addition, it is helpful, but not required, to include an
explanation of how the upload fixes this bug.
[Test Case]
* install haproxy and apache in an up-to-date ubuntu release you are testing, in an arm64 system:
sudo apt update && sudo apt dist-upgrade -y && sudo apt install haproxy apache2 -y
* Create /etc/haproxy/haproxy.cfg with the following contents:
global
chroot /var/lib/haproxy
user haproxy
group haproxy
daemon
maxconn 4096
defaults
log global
option dontlognull
option redispatch
retries 3
timeout client 50s
timeout connect 10s
timeout http-request 5s
timeout server 50s
maxconn 4096
frontend test-front
bind *:8080
mode http
default_backend test-back
backend test-back
mode http
stick store-request src
stick-table type ip size 256k expire 30m
server test-1 localhost:80
* in one terminal, keep tailing the (still nonexistent) haproxy log file:
tail -F /var/log/haproxy.log
* in another terminal, restart haproxy:
sudo systemctl restart haproxy
* The haproxy log will become live, and already show errors:
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [WARNING] 023/191958 (2286) : Exiting Master process...
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [ALERT] 023/191958 (2286) : Current worker 2287 exited with code 143
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [WARNING] 023/191958 (2286) : All workers exited. Exiting... (143)
* Run wget to try to fetch the apache frontpage, via haproxy, limited to one attempt. It will fail:
$ wget -t1 http://localhost:8080
--2019-01-24 19:23:51-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... No data received.
Giving up.
$ echo $?
4
* the haproxy logs will show errors:
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [ALERT] 023/192351 (6411) : Current worker 6412 exited with code 135
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [ALERT] 023/192351 (6411) : exit-on-failure: killing every workers with SIGTERM
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [WARNING] 023/192351 (6411) : All workers exited. Exiting... (135)
* Update the haproxy package and try the wget one more time. This time it will work, and the haproxy logs will stay silent:
wget -t1 http://localhost:8080
--2019-01-24 19:26:14-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... 200 OK
Length: 10918 (11K) [text/html]
Saving to: ‘index.html’
index.html 100%[================================================================================================================================>] 10.66K --.-KB/s in 0s
2019-01-24 19:26:14 (75.3 MB/s) - ‘index.html’ saved [10918/10918]
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
This fault was reported via the haproxy mailing list https://www.mail-archive.com/haproxy@formilux.org/msg31749.html
And then patched in the haproxy code here https://github.com/haproxy/haproxy/commit/52dabbc4fad338233c7f0c96f977a43f8f81452a
Without this patch haproxy is not functional on aarch64/arm64. Experimental deployments of openstack-ansible on arm64 fail because of this bug, and without a fix applied to the ubuntu bionic packages we cannot proceed further as the openstack CI only installs the upstream ubuntu distribution packages. |
|
| 2019-01-24 19:41:47 |
Andreas Hasenack |
description |
[Impact]
* An explanation of the effects of the bug on users and
* justification for backporting the fix to the stable release.
* In addition, it is helpful, but not required, to include an
explanation of how the upload fixes this bug.
[Test Case]
* install haproxy and apache in an up-to-date ubuntu release you are testing, in an arm64 system:
sudo apt update && sudo apt dist-upgrade -y && sudo apt install haproxy apache2 -y
* Create /etc/haproxy/haproxy.cfg with the following contents:
global
chroot /var/lib/haproxy
user haproxy
group haproxy
daemon
maxconn 4096
defaults
log global
option dontlognull
option redispatch
retries 3
timeout client 50s
timeout connect 10s
timeout http-request 5s
timeout server 50s
maxconn 4096
frontend test-front
bind *:8080
mode http
default_backend test-back
backend test-back
mode http
stick store-request src
stick-table type ip size 256k expire 30m
server test-1 localhost:80
* in one terminal, keep tailing the (still nonexistent) haproxy log file:
tail -F /var/log/haproxy.log
* in another terminal, restart haproxy:
sudo systemctl restart haproxy
* The haproxy log will become live, and already show errors:
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [WARNING] 023/191958 (2286) : Exiting Master process...
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [ALERT] 023/191958 (2286) : Current worker 2287 exited with code 143
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [WARNING] 023/191958 (2286) : All workers exited. Exiting... (143)
* Run wget to try to fetch the apache frontpage, via haproxy, limited to one attempt. It will fail:
$ wget -t1 http://localhost:8080
--2019-01-24 19:23:51-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... No data received.
Giving up.
$ echo $?
4
* the haproxy logs will show errors:
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [ALERT] 023/192351 (6411) : Current worker 6412 exited with code 135
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [ALERT] 023/192351 (6411) : exit-on-failure: killing every workers with SIGTERM
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [WARNING] 023/192351 (6411) : All workers exited. Exiting... (135)
* Update the haproxy package and try the wget one more time. This time it will work, and the haproxy logs will stay silent:
wget -t1 http://localhost:8080
--2019-01-24 19:26:14-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... 200 OK
Length: 10918 (11K) [text/html]
Saving to: ‘index.html’
index.html 100%[================================================================================================================================>] 10.66K --.-KB/s in 0s
2019-01-24 19:26:14 (75.3 MB/s) - ‘index.html’ saved [10918/10918]
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
This fault was reported via the haproxy mailing list https://www.mail-archive.com/haproxy@formilux.org/msg31749.html
And then patched in the haproxy code here https://github.com/haproxy/haproxy/commit/52dabbc4fad338233c7f0c96f977a43f8f81452a
Without this patch haproxy is not functional on aarch64/arm64. Experimental deployments of openstack-ansible on arm64 fail because of this bug, and without a fix applied to the ubuntu bionic packages we cannot proceed further as the openstack CI only installs the upstream ubuntu distribution packages. |
[Impact]
* An explanation of the effects of the bug on users and
* justification for backporting the fix to the stable release.
* In addition, it is helpful, but not required, to include an
explanation of how the upload fixes this bug.
[Test Case]
* install haproxy and apache in an up-to-date ubuntu release you are testing, in an arm64 system:
sudo apt update && sudo apt dist-upgrade -y && sudo apt install haproxy apache2 -y
* Create /etc/haproxy/haproxy.cfg with the following contents:
global
chroot /var/lib/haproxy
user haproxy
group haproxy
daemon
maxconn 4096
defaults
log global
option dontlognull
option redispatch
retries 3
timeout client 50s
timeout connect 10s
timeout http-request 5s
timeout server 50s
maxconn 4096
frontend test-front
bind *:8080
mode http
default_backend test-back
backend test-back
mode http
stick store-request src
stick-table type ip size 256k expire 30m
server test-1 localhost:80
* in one terminal, keep tailing the (still nonexistent) haproxy log file:
tail -F /var/log/haproxy.log
* in another terminal, restart haproxy:
sudo systemctl restart haproxy
* The haproxy log will become live, and already show errors:
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [WARNING] 023/191958 (2286) : Exiting Master process...
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [ALERT] 023/191958 (2286) : Current worker 2287 exited with code 143
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [WARNING] 023/191958 (2286) : All workers exited. Exiting... (143)
* Run wget to try to fetch the apache frontpage, via haproxy, limited to one attempt. It will fail:
$ wget -t1 http://localhost:8080
--2019-01-24 19:23:51-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... No data received.
Giving up.
$ echo $?
4
* the haproxy logs will show errors:
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [ALERT] 023/192351 (6411) : Current worker 6412 exited with code 135
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [ALERT] 023/192351 (6411) : exit-on-failure: killing every workers with SIGTERM
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [WARNING] 023/192351 (6411) : All workers exited. Exiting... (135)
* Update the haproxy package and try the wget one more time. This time it will work, and the haproxy logs will stay silent:
$ wget -t1 http://localhost:8080
--2019-01-24 19:26:14-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... 200 OK
Length: 10918 (11K) [text/html]
Saving to: ‘index.html’
index.html 100%[================================================================================================================================>] 10.66K --.-KB/s in 0s
2019-01-24 19:26:14 (75.3 MB/s) - ‘index.html’ saved [10918/10918]
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
This fault was reported via the haproxy mailing list https://www.mail-archive.com/haproxy@formilux.org/msg31749.html
And then patched in the haproxy code here https://github.com/haproxy/haproxy/commit/52dabbc4fad338233c7f0c96f977a43f8f81452a
Without this patch haproxy is not functional on aarch64/arm64. Experimental deployments of openstack-ansible on arm64 fail because of this bug, and without a fix applied to the ubuntu bionic packages we cannot proceed further as the openstack CI only installs the upstream ubuntu distribution packages. |
|
| 2019-01-24 19:43:29 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/haproxy/+git/haproxy/+merge/362210 |
|
| 2019-01-24 19:48:14 |
Andreas Hasenack |
description |
[Impact]
* An explanation of the effects of the bug on users and
* justification for backporting the fix to the stable release.
* In addition, it is helpful, but not required, to include an
explanation of how the upload fixes this bug.
[Test Case]
* install haproxy and apache in an up-to-date ubuntu release you are testing, in an arm64 system:
sudo apt update && sudo apt dist-upgrade -y && sudo apt install haproxy apache2 -y
* Create /etc/haproxy/haproxy.cfg with the following contents:
global
chroot /var/lib/haproxy
user haproxy
group haproxy
daemon
maxconn 4096
defaults
log global
option dontlognull
option redispatch
retries 3
timeout client 50s
timeout connect 10s
timeout http-request 5s
timeout server 50s
maxconn 4096
frontend test-front
bind *:8080
mode http
default_backend test-back
backend test-back
mode http
stick store-request src
stick-table type ip size 256k expire 30m
server test-1 localhost:80
* in one terminal, keep tailing the (still nonexistent) haproxy log file:
tail -F /var/log/haproxy.log
* in another terminal, restart haproxy:
sudo systemctl restart haproxy
* The haproxy log will become live, and already show errors:
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [WARNING] 023/191958 (2286) : Exiting Master process...
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [ALERT] 023/191958 (2286) : Current worker 2287 exited with code 143
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [WARNING] 023/191958 (2286) : All workers exited. Exiting... (143)
* Run wget to try to fetch the apache frontpage, via haproxy, limited to one attempt. It will fail:
$ wget -t1 http://localhost:8080
--2019-01-24 19:23:51-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... No data received.
Giving up.
$ echo $?
4
* the haproxy logs will show errors:
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [ALERT] 023/192351 (6411) : Current worker 6412 exited with code 135
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [ALERT] 023/192351 (6411) : exit-on-failure: killing every workers with SIGTERM
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [WARNING] 023/192351 (6411) : All workers exited. Exiting... (135)
* Update the haproxy package and try the wget one more time. This time it will work, and the haproxy logs will stay silent:
$ wget -t1 http://localhost:8080
--2019-01-24 19:26:14-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... 200 OK
Length: 10918 (11K) [text/html]
Saving to: ‘index.html’
index.html 100%[================================================================================================================================>] 10.66K --.-KB/s in 0s
2019-01-24 19:26:14 (75.3 MB/s) - ‘index.html’ saved [10918/10918]
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
This fault was reported via the haproxy mailing list https://www.mail-archive.com/haproxy@formilux.org/msg31749.html
And then patched in the haproxy code here https://github.com/haproxy/haproxy/commit/52dabbc4fad338233c7f0c96f977a43f8f81452a
Without this patch haproxy is not functional on aarch64/arm64. Experimental deployments of openstack-ansible on arm64 fail because of this bug, and without a fix applied to the ubuntu bionic packages we cannot proceed further as the openstack CI only installs the upstream ubuntu distribution packages. |
[Impact]
haproxy as shipped with bionic and cosmic doesn't work on arm64 architectures, crashing the moment it serves a request.
[Test Case]
* install haproxy and apache in an up-to-date ubuntu release you are testing, in an arm64 system:
sudo apt update && sudo apt dist-upgrade -y && sudo apt install haproxy apache2 -y
* Create /etc/haproxy/haproxy.cfg with the following contents:
global
chroot /var/lib/haproxy
user haproxy
group haproxy
daemon
maxconn 4096
defaults
log global
option dontlognull
option redispatch
retries 3
timeout client 50s
timeout connect 10s
timeout http-request 5s
timeout server 50s
maxconn 4096
frontend test-front
bind *:8080
mode http
default_backend test-back
backend test-back
mode http
stick store-request src
stick-table type ip size 256k expire 30m
server test-1 localhost:80
* in one terminal, keep tailing the (still nonexistent) haproxy log file:
tail -F /var/log/haproxy.log
* in another terminal, restart haproxy:
sudo systemctl restart haproxy
* The haproxy log will become live, and already show errors:
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [WARNING] 023/191958 (2286) : Exiting Master process...
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [ALERT] 023/191958 (2286) : Current worker 2287 exited with code 143
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [WARNING] 023/191958 (2286) : All workers exited. Exiting... (143)
* Run wget to try to fetch the apache frontpage, via haproxy, limited to one attempt. It will fail:
$ wget -t1 http://localhost:8080
--2019-01-24 19:23:51-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... No data received.
Giving up.
$ echo $?
4
* the haproxy logs will show errors:
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [ALERT] 023/192351 (6411) : Current worker 6412 exited with code 135
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [ALERT] 023/192351 (6411) : exit-on-failure: killing every workers with SIGTERM
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [WARNING] 023/192351 (6411) : All workers exited. Exiting... (135)
* Update the haproxy package and try the wget one more time. This time it will work, and the haproxy logs will stay silent:
$ wget -t1 http://localhost:8080
--2019-01-24 19:26:14-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... 200 OK
Length: 10918 (11K) [text/html]
Saving to: ‘index.html’
index.html 100%[================================================================================================================================>] 10.66K --.-KB/s in 0s
2019-01-24 19:26:14 (75.3 MB/s) - ‘index.html’ saved [10918/10918]
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
This fault was reported via the haproxy mailing list https://www.mail-archive.com/haproxy@formilux.org/msg31749.html
And then patched in the haproxy code here https://github.com/haproxy/haproxy/commit/52dabbc4fad338233c7f0c96f977a43f8f81452a
Without this patch haproxy is not functional on aarch64/arm64. Experimental deployments of openstack-ansible on arm64 fail because of this bug, and without a fix applied to the ubuntu bionic packages we cannot proceed further as the openstack CI only installs the upstream ubuntu distribution packages. |
|
| 2019-01-24 20:02:37 |
Andreas Hasenack |
description |
[Impact]
haproxy as shipped with bionic and cosmic doesn't work on arm64 architectures, crashing the moment it serves a request.
[Test Case]
* install haproxy and apache in an up-to-date ubuntu release you are testing, in an arm64 system:
sudo apt update && sudo apt dist-upgrade -y && sudo apt install haproxy apache2 -y
* Create /etc/haproxy/haproxy.cfg with the following contents:
global
chroot /var/lib/haproxy
user haproxy
group haproxy
daemon
maxconn 4096
defaults
log global
option dontlognull
option redispatch
retries 3
timeout client 50s
timeout connect 10s
timeout http-request 5s
timeout server 50s
maxconn 4096
frontend test-front
bind *:8080
mode http
default_backend test-back
backend test-back
mode http
stick store-request src
stick-table type ip size 256k expire 30m
server test-1 localhost:80
* in one terminal, keep tailing the (still nonexistent) haproxy log file:
tail -F /var/log/haproxy.log
* in another terminal, restart haproxy:
sudo systemctl restart haproxy
* The haproxy log will become live, and already show errors:
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [WARNING] 023/191958 (2286) : Exiting Master process...
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [ALERT] 023/191958 (2286) : Current worker 2287 exited with code 143
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [WARNING] 023/191958 (2286) : All workers exited. Exiting... (143)
* Run wget to try to fetch the apache frontpage, via haproxy, limited to one attempt. It will fail:
$ wget -t1 http://localhost:8080
--2019-01-24 19:23:51-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... No data received.
Giving up.
$ echo $?
4
* the haproxy logs will show errors:
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [ALERT] 023/192351 (6411) : Current worker 6412 exited with code 135
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [ALERT] 023/192351 (6411) : exit-on-failure: killing every workers with SIGTERM
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [WARNING] 023/192351 (6411) : All workers exited. Exiting... (135)
* Update the haproxy package and try the wget one more time. This time it will work, and the haproxy logs will stay silent:
$ wget -t1 http://localhost:8080
--2019-01-24 19:26:14-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... 200 OK
Length: 10918 (11K) [text/html]
Saving to: ‘index.html’
index.html 100%[================================================================================================================================>] 10.66K --.-KB/s in 0s
2019-01-24 19:26:14 (75.3 MB/s) - ‘index.html’ saved [10918/10918]
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
This fault was reported via the haproxy mailing list https://www.mail-archive.com/haproxy@formilux.org/msg31749.html
And then patched in the haproxy code here https://github.com/haproxy/haproxy/commit/52dabbc4fad338233c7f0c96f977a43f8f81452a
Without this patch haproxy is not functional on aarch64/arm64. Experimental deployments of openstack-ansible on arm64 fail because of this bug, and without a fix applied to the ubuntu bionic packages we cannot proceed further as the openstack CI only installs the upstream ubuntu distribution packages. |
[Impact]
haproxy as shipped with bionic and cosmic doesn't work on arm64 architectures, crashing the moment it serves a request.
[Test Case]
* install haproxy and apache in an up-to-date ubuntu release you are testing, in an arm64 system:
sudo apt update && sudo apt dist-upgrade -y && sudo apt install haproxy apache2 -y
* Create /etc/haproxy/haproxy.cfg with the following contents:
global
chroot /var/lib/haproxy
user haproxy
group haproxy
daemon
maxconn 4096
defaults
log global
option dontlognull
option redispatch
retries 3
timeout client 50s
timeout connect 10s
timeout http-request 5s
timeout server 50s
maxconn 4096
frontend test-front
bind *:8080
mode http
default_backend test-back
backend test-back
mode http
stick store-request src
stick-table type ip size 256k expire 30m
server test-1 localhost:80
* in one terminal, keep tailing the (still nonexistent) haproxy log file:
tail -F /var/log/haproxy.log
* in another terminal, restart haproxy:
sudo systemctl restart haproxy
* The haproxy log will become live, and already show errors:
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [WARNING] 023/191958 (2286) : Exiting Master process...
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [ALERT] 023/191958 (2286) : Current worker 2287 exited with code 143
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [WARNING] 023/191958 (2286) : All workers exited. Exiting... (143)
* Run wget to try to fetch the apache frontpage, via haproxy, limited to one attempt. It will fail:
$ wget -t1 http://localhost:8080
--2019-01-24 19:23:51-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... No data received.
Giving up.
$ echo $?
4
* the haproxy logs will show errors:
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [ALERT] 023/192351 (6411) : Current worker 6412 exited with code 135
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [ALERT] 023/192351 (6411) : exit-on-failure: killing every workers with SIGTERM
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [WARNING] 023/192351 (6411) : All workers exited. Exiting... (135)
* Update the haproxy package and try the wget one more time. This time it will work, and the haproxy logs will stay silent:
$ wget -t1 http://localhost:8080
--2019-01-24 19:26:14-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... 200 OK
Length: 10918 (11K) [text/html]
Saving to: ‘index.html’
index.html 100%[================================================================================================================================>] 10.66K --.-KB/s in 0s
2019-01-24 19:26:14 (75.3 MB/s) - ‘index.html’ saved [10918/10918]
[Regression Potential]
Patch was applied upstream in 1.8.15 and is available in the same form in the latest 1.8.17 release. The patch is a bit low level, but seems to have been well understood.
[Other Info]
It's bad that our DEP8 test didn't catch this, since all it does is start the service and briefly talk to it, but there is no actual proxying going on.
[Original Description]
This fault was reported via the haproxy mailing list https://www.mail-archive.com/haproxy@formilux.org/msg31749.html
And then patched in the haproxy code here https://github.com/haproxy/haproxy/commit/52dabbc4fad338233c7f0c96f977a43f8f81452a
Without this patch haproxy is not functional on aarch64/arm64. Experimental deployments of openstack-ansible on arm64 fail because of this bug, and without a fix applied to the ubuntu bionic packages we cannot proceed further as the openstack CI only installs the upstream ubuntu distribution packages. |
|
| 2019-01-30 18:44:21 |
Andreas Hasenack |
description |
[Impact]
haproxy as shipped with bionic and cosmic doesn't work on arm64 architectures, crashing the moment it serves a request.
[Test Case]
* install haproxy and apache in an up-to-date ubuntu release you are testing, in an arm64 system:
sudo apt update && sudo apt dist-upgrade -y && sudo apt install haproxy apache2 -y
* Create /etc/haproxy/haproxy.cfg with the following contents:
global
chroot /var/lib/haproxy
user haproxy
group haproxy
daemon
maxconn 4096
defaults
log global
option dontlognull
option redispatch
retries 3
timeout client 50s
timeout connect 10s
timeout http-request 5s
timeout server 50s
maxconn 4096
frontend test-front
bind *:8080
mode http
default_backend test-back
backend test-back
mode http
stick store-request src
stick-table type ip size 256k expire 30m
server test-1 localhost:80
* in one terminal, keep tailing the (still nonexistent) haproxy log file:
tail -F /var/log/haproxy.log
* in another terminal, restart haproxy:
sudo systemctl restart haproxy
* The haproxy log will become live, and already show errors:
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [WARNING] 023/191958 (2286) : Exiting Master process...
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [ALERT] 023/191958 (2286) : Current worker 2287 exited with code 143
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [WARNING] 023/191958 (2286) : All workers exited. Exiting... (143)
* Run wget to try to fetch the apache frontpage, via haproxy, limited to one attempt. It will fail:
$ wget -t1 http://localhost:8080
--2019-01-24 19:23:51-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... No data received.
Giving up.
$ echo $?
4
* the haproxy logs will show errors:
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [ALERT] 023/192351 (6411) : Current worker 6412 exited with code 135
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [ALERT] 023/192351 (6411) : exit-on-failure: killing every workers with SIGTERM
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [WARNING] 023/192351 (6411) : All workers exited. Exiting... (135)
* Update the haproxy package and try the wget one more time. This time it will work, and the haproxy logs will stay silent:
$ wget -t1 http://localhost:8080
--2019-01-24 19:26:14-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... 200 OK
Length: 10918 (11K) [text/html]
Saving to: ‘index.html’
index.html 100%[================================================================================================================================>] 10.66K --.-KB/s in 0s
2019-01-24 19:26:14 (75.3 MB/s) - ‘index.html’ saved [10918/10918]
[Regression Potential]
Patch was applied upstream in 1.8.15 and is available in the same form in the latest 1.8.17 release. The patch is a bit low level, but seems to have been well understood.
[Other Info]
It's bad that our DEP8 test didn't catch this, since all it does is start the service and briefly talk to it, but there is no actual proxying going on.
[Original Description]
This fault was reported via the haproxy mailing list https://www.mail-archive.com/haproxy@formilux.org/msg31749.html
And then patched in the haproxy code here https://github.com/haproxy/haproxy/commit/52dabbc4fad338233c7f0c96f977a43f8f81452a
Without this patch haproxy is not functional on aarch64/arm64. Experimental deployments of openstack-ansible on arm64 fail because of this bug, and without a fix applied to the ubuntu bionic packages we cannot proceed further as the openstack CI only installs the upstream ubuntu distribution packages. |
[Impact]
haproxy as shipped with bionic and cosmic doesn't work on arm64 architectures, crashing the moment it serves a request.
[Test Case]
* install haproxy and apache in an up-to-date ubuntu release you are testing, in an arm64 system:
sudo apt update && sudo apt dist-upgrade -y && sudo apt install haproxy apache2 -y
* Create /etc/haproxy/haproxy.cfg with the following contents:
global
chroot /var/lib/haproxy
user haproxy
group haproxy
daemon
maxconn 4096
defaults
log global
option dontlognull
option redispatch
retries 3
timeout client 50s
timeout connect 10s
timeout http-request 5s
timeout server 50s
maxconn 4096
frontend test-front
bind *:8080
mode http
default_backend test-back
backend test-back
mode http
stick store-request src
stick-table type ip size 256k expire 30m
server test-1 localhost:80
* in one terminal, keep tailing the (still nonexistent) haproxy log file:
tail -F /var/log/haproxy.log
* in another terminal, restart haproxy:
sudo systemctl restart haproxy
* The haproxy log will become live, and already show errors:
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [WARNING] 023/191958 (2286) : Exiting Master process...
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [ALERT] 023/191958 (2286) : Current worker 2287 exited with code 143
Jan 24 19:22:23 cosmic-haproxy-1804069 haproxy[2286]: [WARNING] 023/191958 (2286) : All workers exited. Exiting... (143)
* Run wget to try to fetch the apache frontpage, via haproxy, limited to one attempt. It will fail:
$ wget -t1 http://localhost:8080
--2019-01-24 19:23:51-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... No data received.
Giving up.
$ echo $?
4
* the haproxy logs will show errors:
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [ALERT] 023/192351 (6411) : Current worker 6412 exited with code 135
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [ALERT] 023/192351 (6411) : exit-on-failure: killing every workers with SIGTERM
Jan 24 19:24:36 cosmic-haproxy-1804069 haproxy[6411]: [WARNING] 023/192351 (6411) : All workers exited. Exiting... (135)
* Update the haproxy package and try the wget one more time. This time it will work, and the haproxy logs will stay silent:
$ wget -t1 http://localhost:8080
--2019-01-24 19:26:14-- http://localhost:8080/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... 200 OK
Length: 10918 (11K) [text/html]
Saving to: ‘index.html’
index.html 100%[================================================================================================================================>] 10.66K --.-KB/s in 0s
2019-01-24 19:26:14 (75.3 MB/s) - ‘index.html’ saved [10918/10918]
[Regression Potential]
Patch was applied upstream in 1.8.15 and is available in the same form in the latest 1.8.17 release. The patch is a bit low level, but seems to have been well understood.
[Other Info]
After writing the testing instructions for this bug, I decided they could be easily converted to a DEP8 test, which I did and included in this SRU. This new test, very simple but effective, shows that arm64 is working, and that the other architectures didn't break.
[Original Description]
This fault was reported via the haproxy mailing list https://www.mail-archive.com/haproxy@formilux.org/msg31749.html
And then patched in the haproxy code here https://github.com/haproxy/haproxy/commit/52dabbc4fad338233c7f0c96f977a43f8f81452a
Without this patch haproxy is not functional on aarch64/arm64. Experimental deployments of openstack-ansible on arm64 fail because of this bug, and without a fix applied to the ubuntu bionic packages we cannot proceed further as the openstack CI only installs the upstream ubuntu distribution packages. |
|
| 2019-01-31 22:52:44 |
Brian Murray |
haproxy (Ubuntu Cosmic): status |
In Progress |
Fix Committed |
|
| 2019-01-31 22:52:47 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2019-01-31 22:52:48 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2019-01-31 22:52:51 |
Brian Murray |
tags |
bitesize server-next |
bitesize server-next verification-needed verification-needed-cosmic |
|
| 2019-01-31 22:54:14 |
Brian Murray |
haproxy (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2019-01-31 22:54:19 |
Brian Murray |
tags |
bitesize server-next verification-needed verification-needed-cosmic |
bitesize server-next verification-needed verification-needed-bionic verification-needed-cosmic |
|
| 2019-02-04 11:43:05 |
Jonathan Rosser |
tags |
bitesize server-next verification-needed verification-needed-bionic verification-needed-cosmic |
bitesize server-next verification-done-bionic verification-needed verification-needed-cosmic |
|
| 2019-02-06 11:48:04 |
Andreas Hasenack |
tags |
bitesize server-next verification-done-bionic verification-needed verification-needed-cosmic |
bitesize server-next verification-done-bionic verification-done-cosmic verification-needed |
|
| 2019-02-07 12:05:06 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2019-02-07 12:05:20 |
Launchpad Janitor |
haproxy (Ubuntu Cosmic): status |
Fix Committed |
Fix Released |
|
| 2019-02-07 12:18:56 |
Launchpad Janitor |
haproxy (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
