[Bug 1847527] Re: Backport systemd-journal-remote fix PR #11953

[Dan Streetman]

** Description changed:

+ [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.

** Description changed:

  [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.

** Also affects: systemd (Ubuntu Eoan)
   Importance: Undecided
       Status: Fix Released

** Also affects: systemd (Ubuntu Bionic)
   Importance: Undecided
       Status: New

** Changed in: systemd (Ubuntu Bionic)
       Status: New => Invalid

** Changed in: systemd (Ubuntu Disco)
       Status: New => In Progress

** Changed in: systemd (Ubuntu Disco)
     Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Disco)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1847527

Title:
  Backport systemd-journal-remote fix PR #11953

Status in openstack-ansible:
  New
Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Invalid
Status in systemd source package in Disco:
  In Progress
Status in systemd source package in Eoan:
  Fix Released

Bug 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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-ansible/+bug/1847527/+subscriptions