| 2020-09-30 20:06:11 |
Lucas Kanashiro |
bug |
|
|
added bug |
| 2020-10-01 12:18:13 |
Lucas Kanashiro |
attachment added |
|
prometheus-alertmanager.debdiff https://bugs.launchpad.net/ubuntu/+source/prometheus-alertmanager/+bug/1897967/+attachment/5416066/+files/prometheus-alertmanager.debdiff |
|
| 2020-10-01 12:29:24 |
Ubuntu Foundations Team Bug Bot |
tags |
|
patch |
|
| 2020-10-01 12:32:44 |
Lucas Kanashiro |
description |
Currently, prometheus-alertmanager version 0.15.3+ds-3 FTBFS in Focal:
https://paste.ubuntu.com/p/CcCYC3w3YC/
The Prometheus common golang library changed its API and the alertmanager version we have in Focal is not ready for it. |
[Impact]
The package FTBFS in Focal likely because a newer version of golang-github-prometheus-common was introduced after prometheus-alertmanager and a rebuild was not done. Not being able to build the package form source does not allow uploads of eventual fixes (security or regular ones) which is definitely not good for the users.
The Prometheus common lib API change which is impacting prometheus-alertmanager is minor. There is an extra argument in NewClientFromConfig function to enable or not HTTP/2. The proposed fix apply a patch enabling HTTP/2 in all the calls made to NewClientFromConfig.
[Test Case]
Try to build the package in Focal:
$ lxc launch ubuntu-daily:focal builder
$ lxc shell builder
# echo "deb-src http://archive.ubuntu.com/ubuntu/ focal main universe" > \
/etc/apt/sources.list.d/source.list
# apt update && apt upgrade -y
# apt install -y dpkg-dev
# apt source prometheus-alertmanager
# apt build-dep -y prometheus-alertmanager
# cd prometheus-alertmanager-0.15.3+ds
# dpkg-buildpackage
To fix the FTBFS apply the debdiff attached to this bug and build the package again.
[Regression Potential]
In the case where the user environment do not support HTTP/2 there might be a regression. HTTP/2 tries to be highly compatible with HTTP/1.1 but there might be any corner case.
[Original Description]
Currently, prometheus-alertmanager version 0.15.3+ds-3 FTBFS in Focal:
https://paste.ubuntu.com/p/CcCYC3w3YC/
The Prometheus common golang library changed its API and the alertmanager version we have in Focal is not ready for it. |
|
| 2020-10-01 12:32:56 |
Lucas Kanashiro |
nominated for series |
|
Ubuntu Focal |
|
| 2020-10-01 12:32:56 |
Lucas Kanashiro |
bug task added |
|
prometheus-alertmanager (Ubuntu Focal) |
|
| 2020-10-01 12:33:06 |
Lucas Kanashiro |
prometheus-alertmanager (Ubuntu): status |
New |
Invalid |
|
| 2020-10-01 12:47:00 |
Lucas Kanashiro |
summary |
FTBFS in Focal |
[SRU] FTBFS in Focal |
|
| 2020-10-01 13:13:14 |
Lucas Kanashiro |
description |
[Impact]
The package FTBFS in Focal likely because a newer version of golang-github-prometheus-common was introduced after prometheus-alertmanager and a rebuild was not done. Not being able to build the package form source does not allow uploads of eventual fixes (security or regular ones) which is definitely not good for the users.
The Prometheus common lib API change which is impacting prometheus-alertmanager is minor. There is an extra argument in NewClientFromConfig function to enable or not HTTP/2. The proposed fix apply a patch enabling HTTP/2 in all the calls made to NewClientFromConfig.
[Test Case]
Try to build the package in Focal:
$ lxc launch ubuntu-daily:focal builder
$ lxc shell builder
# echo "deb-src http://archive.ubuntu.com/ubuntu/ focal main universe" > \
/etc/apt/sources.list.d/source.list
# apt update && apt upgrade -y
# apt install -y dpkg-dev
# apt source prometheus-alertmanager
# apt build-dep -y prometheus-alertmanager
# cd prometheus-alertmanager-0.15.3+ds
# dpkg-buildpackage
To fix the FTBFS apply the debdiff attached to this bug and build the package again.
[Regression Potential]
In the case where the user environment do not support HTTP/2 there might be a regression. HTTP/2 tries to be highly compatible with HTTP/1.1 but there might be any corner case.
[Original Description]
Currently, prometheus-alertmanager version 0.15.3+ds-3 FTBFS in Focal:
https://paste.ubuntu.com/p/CcCYC3w3YC/
The Prometheus common golang library changed its API and the alertmanager version we have in Focal is not ready for it. |
[Impact]
The package FTBFS in Focal likely because a newer version of golang-github-prometheus-common was introduced after prometheus-alertmanager and a rebuild was not done. Not being able to build the package from source does not allow uploads of eventual fixes (security or regular ones) which is definitely not good for the users.
The Prometheus common lib API change which is impacting prometheus-alertmanager is minor. There is an extra argument in NewClientFromConfig function to enable or not HTTP/2. The proposed fix apply a patch enabling HTTP/2 in all the calls made to NewClientFromConfig.
[Test Case]
Try to build the package in Focal:
$ lxc launch ubuntu-daily:focal builder
$ lxc shell builder
# echo "deb-src http://archive.ubuntu.com/ubuntu/ focal main universe" > \
/etc/apt/sources.list.d/source.list
# apt update && apt upgrade -y
# apt install -y dpkg-dev
# apt source prometheus-alertmanager
# apt build-dep -y prometheus-alertmanager
# cd prometheus-alertmanager-0.15.3+ds
# dpkg-buildpackage
To fix the FTBFS apply the debdiff attached to this bug and build the package again.
[Regression Potential]
In the case where the user environment do not support HTTP/2 there might be a regression. HTTP/2 tries to be highly compatible with HTTP/1.1 but there might be any corner case. This would not be a change in the current behavior because this extra argument was added to allow users to disable it, check out this upstream commit:
https://github.com/prometheus/common/commit/273427a9fd1
[Original Description]
Currently, prometheus-alertmanager version 0.15.3+ds-3 FTBFS in Focal:
https://paste.ubuntu.com/p/CcCYC3w3YC/
The Prometheus common golang library changed its API and the alertmanager version we have in Focal is not ready for it. |
|
| 2020-10-01 13:15:50 |
Andreas Hasenack |
description |
[Impact]
The package FTBFS in Focal likely because a newer version of golang-github-prometheus-common was introduced after prometheus-alertmanager and a rebuild was not done. Not being able to build the package from source does not allow uploads of eventual fixes (security or regular ones) which is definitely not good for the users.
The Prometheus common lib API change which is impacting prometheus-alertmanager is minor. There is an extra argument in NewClientFromConfig function to enable or not HTTP/2. The proposed fix apply a patch enabling HTTP/2 in all the calls made to NewClientFromConfig.
[Test Case]
Try to build the package in Focal:
$ lxc launch ubuntu-daily:focal builder
$ lxc shell builder
# echo "deb-src http://archive.ubuntu.com/ubuntu/ focal main universe" > \
/etc/apt/sources.list.d/source.list
# apt update && apt upgrade -y
# apt install -y dpkg-dev
# apt source prometheus-alertmanager
# apt build-dep -y prometheus-alertmanager
# cd prometheus-alertmanager-0.15.3+ds
# dpkg-buildpackage
To fix the FTBFS apply the debdiff attached to this bug and build the package again.
[Regression Potential]
In the case where the user environment do not support HTTP/2 there might be a regression. HTTP/2 tries to be highly compatible with HTTP/1.1 but there might be any corner case. This would not be a change in the current behavior because this extra argument was added to allow users to disable it, check out this upstream commit:
https://github.com/prometheus/common/commit/273427a9fd1
[Original Description]
Currently, prometheus-alertmanager version 0.15.3+ds-3 FTBFS in Focal:
https://paste.ubuntu.com/p/CcCYC3w3YC/
The Prometheus common golang library changed its API and the alertmanager version we have in Focal is not ready for it. |
[Impact]
The package FTBFS in Focal because a newer version of golang-github-prometheus-common was introduced after prometheus-alertmanager and a rebuild was not done. Not being able to build the package from source does not allow uploads of eventual fixes (security or regular ones) which is definitely not good for the users.
The Prometheus common lib API change which is impacting prometheus-alertmanager is minor. There is an extra argument in NewClientFromConfig function to enable or not HTTP/2. The proposed fix apply a patch enabling HTTP/2 in all the calls made to NewClientFromConfig.
[Test Case]
Try to build the package in Focal:
$ lxc launch ubuntu-daily:focal builder
$ lxc shell builder
# echo "deb-src http://archive.ubuntu.com/ubuntu/ focal main universe" > \
/etc/apt/sources.list.d/source.list
# apt update && apt upgrade -y
# apt install -y dpkg-dev
# apt source prometheus-alertmanager
# apt build-dep -y prometheus-alertmanager
# cd prometheus-alertmanager-0.15.3+ds
# dpkg-buildpackage
To fix the FTBFS apply the debdiff attached to this bug and build the package again.
[Regression Potential]
In the case where the user environment do not support HTTP/2 there might be a regression. HTTP/2 tries to be highly compatible with HTTP/1.1 but there might be any corner case. This would not be a change in the current behavior because this extra argument was added to allow users to disable it, check out this upstream commit:
https://github.com/prometheus/common/commit/273427a9fd1
[Original Description]
Currently, prometheus-alertmanager version 0.15.3+ds-3 FTBFS in Focal:
https://paste.ubuntu.com/p/CcCYC3w3YC/
The Prometheus common golang library changed its API and the alertmanager version we have in Focal is not ready for it. |
|
| 2020-10-01 13:16:29 |
Andreas Hasenack |
description |
[Impact]
The package FTBFS in Focal because a newer version of golang-github-prometheus-common was introduced after prometheus-alertmanager and a rebuild was not done. Not being able to build the package from source does not allow uploads of eventual fixes (security or regular ones) which is definitely not good for the users.
The Prometheus common lib API change which is impacting prometheus-alertmanager is minor. There is an extra argument in NewClientFromConfig function to enable or not HTTP/2. The proposed fix apply a patch enabling HTTP/2 in all the calls made to NewClientFromConfig.
[Test Case]
Try to build the package in Focal:
$ lxc launch ubuntu-daily:focal builder
$ lxc shell builder
# echo "deb-src http://archive.ubuntu.com/ubuntu/ focal main universe" > \
/etc/apt/sources.list.d/source.list
# apt update && apt upgrade -y
# apt install -y dpkg-dev
# apt source prometheus-alertmanager
# apt build-dep -y prometheus-alertmanager
# cd prometheus-alertmanager-0.15.3+ds
# dpkg-buildpackage
To fix the FTBFS apply the debdiff attached to this bug and build the package again.
[Regression Potential]
In the case where the user environment do not support HTTP/2 there might be a regression. HTTP/2 tries to be highly compatible with HTTP/1.1 but there might be any corner case. This would not be a change in the current behavior because this extra argument was added to allow users to disable it, check out this upstream commit:
https://github.com/prometheus/common/commit/273427a9fd1
[Original Description]
Currently, prometheus-alertmanager version 0.15.3+ds-3 FTBFS in Focal:
https://paste.ubuntu.com/p/CcCYC3w3YC/
The Prometheus common golang library changed its API and the alertmanager version we have in Focal is not ready for it. |
[Impact]
The package FTBFS in Focal because a newer version of golang-github-prometheus-common was introduced after prometheus-alertmanager and a rebuild was not done. Not being able to build the package from source does not allow uploads of eventual fixes (security or regular ones) which is definitely not good for the users.
The Prometheus common lib API change which is impacting prometheus-alertmanager is minor. There is an extra argument in NewClientFromConfig function to enable or not HTTP/2. The proposed fix apply a patch enabling HTTP/2 in all the calls made to NewClientFromConfig, since this was the previous behavior (http/2 enabled).
[Test Case]
Try to build the package in Focal:
$ lxc launch ubuntu-daily:focal builder
$ lxc shell builder
# echo "deb-src http://archive.ubuntu.com/ubuntu/ focal main universe" > \
/etc/apt/sources.list.d/source.list
# apt update && apt upgrade -y
# apt install -y dpkg-dev
# apt source prometheus-alertmanager
# apt build-dep -y prometheus-alertmanager
# cd prometheus-alertmanager-0.15.3+ds
# dpkg-buildpackage
To fix the FTBFS apply the debdiff attached to this bug and build the package again.
[Regression Potential]
In the case where the user environment do not support HTTP/2 there might be a regression. HTTP/2 tries to be highly compatible with HTTP/1.1 but there might be any corner case. This would not be a change in the current behavior because this extra argument was added to allow users to disable it, check out this upstream commit:
https://github.com/prometheus/common/commit/273427a9fd1
[Original Description]
Currently, prometheus-alertmanager version 0.15.3+ds-3 FTBFS in Focal:
https://paste.ubuntu.com/p/CcCYC3w3YC/
The Prometheus common golang library changed its API and the alertmanager version we have in Focal is not ready for it. |
|
| 2020-10-01 13:23:30 |
Lucas Kanashiro |
description |
[Impact]
The package FTBFS in Focal because a newer version of golang-github-prometheus-common was introduced after prometheus-alertmanager and a rebuild was not done. Not being able to build the package from source does not allow uploads of eventual fixes (security or regular ones) which is definitely not good for the users.
The Prometheus common lib API change which is impacting prometheus-alertmanager is minor. There is an extra argument in NewClientFromConfig function to enable or not HTTP/2. The proposed fix apply a patch enabling HTTP/2 in all the calls made to NewClientFromConfig, since this was the previous behavior (http/2 enabled).
[Test Case]
Try to build the package in Focal:
$ lxc launch ubuntu-daily:focal builder
$ lxc shell builder
# echo "deb-src http://archive.ubuntu.com/ubuntu/ focal main universe" > \
/etc/apt/sources.list.d/source.list
# apt update && apt upgrade -y
# apt install -y dpkg-dev
# apt source prometheus-alertmanager
# apt build-dep -y prometheus-alertmanager
# cd prometheus-alertmanager-0.15.3+ds
# dpkg-buildpackage
To fix the FTBFS apply the debdiff attached to this bug and build the package again.
[Regression Potential]
In the case where the user environment do not support HTTP/2 there might be a regression. HTTP/2 tries to be highly compatible with HTTP/1.1 but there might be any corner case. This would not be a change in the current behavior because this extra argument was added to allow users to disable it, check out this upstream commit:
https://github.com/prometheus/common/commit/273427a9fd1
[Original Description]
Currently, prometheus-alertmanager version 0.15.3+ds-3 FTBFS in Focal:
https://paste.ubuntu.com/p/CcCYC3w3YC/
The Prometheus common golang library changed its API and the alertmanager version we have in Focal is not ready for it. |
[Impact]
The package FTBFS in Focal because a newer version of golang-github-prometheus-common was introduced after prometheus-alertmanager and a rebuild was not done. Not being able to build the package from source does not allow uploads of eventual fixes (security or regular ones) which is definitely not good for the users.
The Prometheus common lib API change which is impacting prometheus-alertmanager is minor. There is an extra argument in NewClientFromConfig function to enable or not HTTP/2. The proposed fix apply a patch enabling HTTP/2 in all the calls made to NewClientFromConfig, since this was the previous behavior (http/2 enabled).
[Test Case]
Try to build the package in Focal:
$ lxc launch ubuntu-daily:focal builder
$ lxc shell builder
# echo "deb-src http://archive.ubuntu.com/ubuntu/ focal main universe" > \
/etc/apt/sources.list.d/source.list
# apt update && apt upgrade -y
# apt install -y dpkg-dev
# apt source prometheus-alertmanager
# apt build-dep -y prometheus-alertmanager
# cd prometheus-alertmanager-0.15.3+ds
# dpkg-buildpackage
To fix the FTBFS apply the debdiff attached to this bug and build the package again.
[Regression Potential]
This SRU would not change the current behavior because this extra argument was added to allow users to disable HTTP/2, check out this upstream commit:
https://github.com/prometheus/common/commit/273427a9fd1
So I believe the potential of a regression is quite low.
[Original Description]
Currently, prometheus-alertmanager version 0.15.3+ds-3 FTBFS in Focal:
https://paste.ubuntu.com/p/CcCYC3w3YC/
The Prometheus common golang library changed its API and the alertmanager version we have in Focal is not ready for it. |
|
| 2020-10-01 15:15:13 |
Lucas Kanashiro |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-10-14 13:25:28 |
Robie Basak |
prometheus-alertmanager (Ubuntu Focal): status |
New |
Fix Committed |
|
| 2020-10-14 13:25:30 |
Robie Basak |
bug |
|
|
added subscriber SRU Verification |
| 2020-10-14 13:25:32 |
Robie Basak |
tags |
patch |
patch verification-needed verification-needed-focal |
|
| 2020-10-14 20:28:52 |
Lucas Kanashiro |
tags |
patch verification-needed verification-needed-focal |
patch verification-done verification-done-focal |
|
| 2020-10-26 09:57:13 |
Launchpad Janitor |
prometheus-alertmanager (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2020-10-26 09:57:16 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
