2019-10-09 19:49:01 |
Tom Cameron |
bug |
|
|
added bug |
2019-10-09 19:52:17 |
Tom Cameron |
bug watch added |
|
https://github.com/systemd/systemd/issues/11571 |
|
2019-10-09 19:52:17 |
Tom Cameron |
bug task added |
|
systemd |
|
2019-10-09 19:55:42 |
Tom Cameron |
summary |
Backport journal-remote fix PR #11953 |
Backport systemd-journal-remote fix PR #11953 |
|
2019-10-10 00:29:48 |
Bug Watch Updater |
systemd: status |
Unknown |
Fix Released |
|
2019-10-10 01:25:09 |
Kevin Carter |
bug task added |
|
openstack-ansible |
|
2019-10-10 01:25:38 |
Launchpad Janitor |
systemd (Ubuntu): status |
New |
Confirmed |
|
2019-10-11 10:37:04 |
Balint Reczey |
nominated for series |
|
Ubuntu Disco |
|
2019-10-11 10:37:04 |
Balint Reczey |
bug task added |
|
systemd (Ubuntu Disco) |
|
2019-10-11 10:37:42 |
Balint Reczey |
systemd (Ubuntu): status |
Confirmed |
Fix Released |
|
2019-10-14 19:02:49 |
Dan Streetman |
description |
I'm requesting that systemd 240 receive the fix in upstream PR 11953 found here https://github.com/systemd/systemd/pull/11953
This fixes remote journal shipping using systemd components. I believe only Disco (19.04) is impacted by this issue. |
[impact]
upstream commit 7fdb237f5473cb8fc2129e57e8a0039526dcb4fd broke remote journal upload, because it added a check to verify the Content-Length header, but the upload may use Transfer-Encoding of 'chunked' which does
not specify Content-Length.
[test case]
see comment 5
[regression potential]
this limits the Transfer-Encoding to only be either unspecified, or 'chunked'. Any other value will fail. However, journal-upload.c does not ever use any other Transfer-Encoding than 'chunked', and this fix comes from upstream and has not changed since applied there.
Any regression would likely result in the failure to upload a remote journal.
[other info]
original description:
--
I'm requesting that systemd 240 receive the fix in upstream PR 11953 found here https://github.com/systemd/systemd/pull/11953
This fixes remote journal shipping using systemd components. I believe only Disco (19.04) is impacted by this issue. |
|
2019-10-14 19:04:45 |
Dan Streetman |
description |
[impact]
upstream commit 7fdb237f5473cb8fc2129e57e8a0039526dcb4fd broke remote journal upload, because it added a check to verify the Content-Length header, but the upload may use Transfer-Encoding of 'chunked' which does
not specify Content-Length.
[test case]
see comment 5
[regression potential]
this limits the Transfer-Encoding to only be either unspecified, or 'chunked'. Any other value will fail. However, journal-upload.c does not ever use any other Transfer-Encoding than 'chunked', and this fix comes from upstream and has not changed since applied there.
Any regression would likely result in the failure to upload a remote journal.
[other info]
original description:
--
I'm requesting that systemd 240 receive the fix in upstream PR 11953 found here https://github.com/systemd/systemd/pull/11953
This fixes remote journal shipping using systemd components. I believe only Disco (19.04) is impacted by this issue. |
[impact]
upstream commit 7fdb237f5473cb8fc2129e57e8a0039526dcb4fd broke remote journal upload, because it added a check to verify the Content-Length header, but the upload may use Transfer-Encoding of 'chunked' which does
not specify Content-Length.
[test case]
see comment 5
[regression potential]
this limits the Transfer-Encoding to only be either unspecified, or 'chunked'. Any other value will fail. However, journal-upload.c does not ever use any other Transfer-Encoding than 'chunked', and this fix comes from upstream and has not changed since applied there.
Any regression would likely result in the failure to upload a remote journal.
[other info]
the commit that caused this is not included in Bionic, and the commit to fix this is already in Eoan; this is needed only in Disco.
original description:
--
I'm requesting that systemd 240 receive the fix in upstream PR 11953 found here https://github.com/systemd/systemd/pull/11953
This fixes remote journal shipping using systemd components. I believe only Disco (19.04) is impacted by this issue. |
|
2019-10-14 19:05:09 |
Dan Streetman |
nominated for series |
|
Ubuntu Eoan |
|
2019-10-14 19:05:09 |
Dan Streetman |
bug task added |
|
systemd (Ubuntu Eoan) |
|
2019-10-14 19:05:09 |
Dan Streetman |
nominated for series |
|
Ubuntu Bionic |
|
2019-10-14 19:05:09 |
Dan Streetman |
bug task added |
|
systemd (Ubuntu Bionic) |
|
2019-10-14 19:05:22 |
Dan Streetman |
systemd (Ubuntu Bionic): status |
New |
Invalid |
|
2019-10-14 19:05:27 |
Dan Streetman |
systemd (Ubuntu Disco): status |
New |
In Progress |
|
2019-10-14 19:05:30 |
Dan Streetman |
systemd (Ubuntu Disco): assignee |
|
Dan Streetman (ddstreet) |
|
2019-10-14 19:05:32 |
Dan Streetman |
systemd (Ubuntu Disco): importance |
Undecided |
Medium |
|
2019-11-09 01:03:36 |
Steve Langasek |
systemd (Ubuntu Disco): status |
In Progress |
Fix Committed |
|
2019-11-09 01:03:39 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
2019-11-09 01:03:42 |
Steve Langasek |
bug |
|
|
added subscriber SRU Verification |
2019-11-09 01:03:46 |
Steve Langasek |
tags |
disco |
disco verification-needed verification-needed-disco |
|
2019-11-14 20:20:04 |
Dan Streetman |
description |
[impact]
upstream commit 7fdb237f5473cb8fc2129e57e8a0039526dcb4fd broke remote journal upload, because it added a check to verify the Content-Length header, but the upload may use Transfer-Encoding of 'chunked' which does
not specify Content-Length.
[test case]
see comment 5
[regression potential]
this limits the Transfer-Encoding to only be either unspecified, or 'chunked'. Any other value will fail. However, journal-upload.c does not ever use any other Transfer-Encoding than 'chunked', and this fix comes from upstream and has not changed since applied there.
Any regression would likely result in the failure to upload a remote journal.
[other info]
the commit that caused this is not included in Bionic, and the commit to fix this is already in Eoan; this is needed only in Disco.
original description:
--
I'm requesting that systemd 240 receive the fix in upstream PR 11953 found here https://github.com/systemd/systemd/pull/11953
This fixes remote journal shipping using systemd components. I believe only Disco (19.04) is impacted by this issue. |
[impact]
upstream commit 7fdb237f5473cb8fc2129e57e8a0039526dcb4fd broke remote journal upload, because it added a check to verify the Content-Length header, but the upload may use Transfer-Encoding of 'chunked' which does
not specify Content-Length.
[test case]
setup 2 systems, A and B. Install systemd-journal-remote on both.
On A:
$ sudo systemctl edit systemd-journal-remote.service
in the editor, add:
[Service]
ExecStart=
ExecStart=/lib/systemd/systemd-journal-remote --listen-http=-3 --output=/var/log/journal/remote/
Then enable/start the socket:
$ sudo systemctl enable systemd-journal-remote.socket
$ sudo systemctl start systemd-journal-remote.socket
Optionally, start the service and verify it is running (not required, since the socket will start the service):
$ sudo systemctl start systemd-journal-remote.service
$ sudo systemctl status systemd-journal-remote.service | grep Active
Active: active (running) since Thu 2019-11-14 20:08:48 UTC; 7min ago
On B:
Edit the file /etc/systemd/journal-upload.conf:
[Upload]
URL=http://192.168.122.184:19532
Replacing the IP address with the actual ip addr of node A. Then enable/start the service:
$ sudo systemctl enable systemd-journal-upload.service
$ sudo systemctl start systemd-journal-upload.service
Check for failure:
ubuntu@lp1847527-d:~$ journalctl -b -u systemd-journal-upload.service
-- Logs begin at Thu 2019-11-14 16:34:08 UTC, end at Thu 2019-11-14 20:19:34 UTC. --
Nov 14 20:19:03 lp1847527-d systemd[1]: Started Journal Remote Upload Service.
Nov 14 20:19:03 lp1847527-d systemd-journal-upload[721]: Upload to http://192.168.122.184:19532/upload failed with code 411: gth Required
Nov 14 20:19:03 lp1847527-d systemd[1]: systemd-journal-upload.service: Main process exited, code=exited, status=1/FAILURE
Nov 14 20:19:03 lp1847527-d systemd[1]: systemd-journal-upload.service: Failed with result 'exit-code'.
[regression potential]
this limits the Transfer-Encoding to only be either unspecified, or 'chunked'. Any other value will fail. However, journal-upload.c does not ever use any other Transfer-Encoding than 'chunked', and this fix comes from upstream and has not changed since applied there.
Any regression would likely result in the failure to upload a remote journal.
[other info]
the commit that caused this is not included in Bionic, and the commit to fix this is already in Eoan; this is needed only in Disco.
original description:
--
I'm requesting that systemd 240 receive the fix in upstream PR 11953 found here https://github.com/systemd/systemd/pull/11953
This fixes remote journal shipping using systemd components. I believe only Disco (19.04) is impacted by this issue. |
|
2019-11-14 20:39:50 |
Dan Streetman |
tags |
disco verification-needed verification-needed-disco |
disco verification-done verification-done-disco |
|
2019-11-25 11:18:51 |
Launchpad Janitor |
systemd (Ubuntu Disco): status |
Fix Committed |
Fix Released |
|
2019-11-25 11:19:29 |
Ćukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
2024-02-13 16:49:19 |
Jonathan Rosser |
openstack-ansible: status |
New |
Invalid |
|