Yeah I have considered it as nice drive-by improvement unrelated to this bug -
and thanks for doing so.
I just had sorted out some lose ends on rsyslog and they both where part of it.
Since this didn't work last time it is not closed yet, but open at low prio.
As explained TBH I think we won't
@Christian,
https://code.launchpad.net/~sdeziel/ubuntu/+source/rsyslog/+git/rsyslog/+merge/382345
was a 'drive-by' merge proposal not associated with any LP (is that
OK?). As such, I don't consider it related to this bug which can be
closed now AFAICT.
--
You received this bug notification
Let us kill the SRU - given what happened last time and that this is a
a) disabled by default profile
and
b) user fixable by editing a conffile
If it is ok with you I'd better focus on merging the latest version +
your improvement in
** Merge proposal linked:
https://code.launchpad.net/~sdeziel/ubuntu/+source/rsyslog/+git/rsyslog/+merge/382345
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1827253
I want to look at this again ...
** Changed in: rsyslog (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~sdeziel/ubuntu/+source/rsyslog/+git/rsyslog/+merge/382344
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1827253
The 1st SRU for Bionic failed because I typo'ed the path to the binary (rsyslog
!= rsyslogd).
Focal is fixed and Bionic is left with a 'bad' package in bionic-proposed. I
don't think redoing the SRU for Bionic is worth it, it's a default *disabled*
profile after all.
I'd leave things as is or
Simon,
Could you please help identifying the current status of this bug ? Your
original merge requests were postponed to the next SRU for rsyslog in
Bionic, Disco and Eoan, correct ?
During verification time you discovered the difference between "bin" and
"sbin" for the apparmor rule, is that it
Marking as Fix Released for Disco:
+rsyslog (8.32.0-1ubuntu7.1) disco; urgency=medium
+
+ [ Simon Deziel ]
+ * d/usr.sbin.rsyslogd: allow reading/mmap'ing rsyslog binary
+This is required for usage inside containers (LP: #1827253)
+
+ -- Christian Ehrhardt Mon, 14 Oct 2019
08:53:03 +0200
The version in focal-proposed works well, thanks Christian! I hadn't
anticipated the additional roadblocks so I really appreciate you pushing
it forward nevertheless!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in
This bug was fixed in the package rsyslog - 8.2001.0-1ubuntu1
---
rsyslog (8.2001.0-1ubuntu1) focal; urgency=medium
[ Christian Ehrhardt ]
* Merge with Debian unstable (LP: #1862762). Remaining changes:
- debian/00rsyslog.conf Install tmpfiles.d snippet to ensure that the
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/rsyslog/+git/rsyslog/+merge/378910
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1827253
We have a new MP that fixes things for real in Focal.
The former SRUs already have been set to verification-failed and can be
cancelled from -proposed if it helps to clear up things.
** Changed in: rsyslog (Ubuntu Disco)
Status: Fix Committed => Triaged
** Changed in: rsyslog (Ubuntu
** Changed in: rsyslog (Ubuntu)
Status: Fix Released => In Progress
** Also affects: rsyslog (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: rsyslog (Ubuntu Eoan)
Status: New => Triaged
** Changed in: rsyslog (Ubuntu Eoan)
Importance: Undecided => Low
I feel really bad now :/
The initial commit that went in doesn't even fix the problem due to a
typo/confusion. The proposed manual workaround was OK but the merge
proposal was not.
"/usr/sbin/rsyslog mr," != "/usr/sbin/rsyslogd mr,"
I'm failing the verification and have proposed a new MP.
** Merge proposal linked:
https://code.launchpad.net/~sdeziel/ubuntu/+source/rsyslog/+git/rsyslog/+merge/374922
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1827253
Hello Simon, or anyone else affected,
Accepted rsyslog into disco-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/rsyslog/8.32.0-1ubuntu7.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Thanks Łukasz and Christian. I find the block-proposed-* tags idea
interesting if that's not too much work on your side.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
Thanks for the review Łukasz,
I somewhat agree with your summary. The reason I went on with it was because it
was very low hanging fruit and Simon (Bug reporter) is like "The Ubuntu
community good bug reports role model".
But I agree that the update for everyone (it is always installed) might be
Reviewing this, it feels to me like something nice to have, but low-
importance enough that I'd be worried about users getting an upgrade
with no impact for them (and, as per the regression potential, some low-
chance but still regression risk). The SRU policy is a bit conflicted
there: on one
MPs got reviewed and uploaded to D/B SRU queue
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1827253
Title:
[apparmor] missing 'mr' on binary for usage on containers
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/rsyslog/+git/rsyslog/+merge/374072
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/rsyslog/+git/rsyslog/+merge/374073
--
You received this bug notification because you are a member
I prepped the two MPs for the SRU as this isn't the biggest impact fix,
but OTOH patch-on-a-platter and also easy to review for code/impact.
** Changed in: rsyslog (Ubuntu Disco)
Importance: Undecided => Low
** Changed in: rsyslog (Ubuntu Bionic)
Importance: Undecided => Low
**
** Description changed:
+ [Impact]
+
+ * rsyslog ships with a (Default disable) apparmor profile.
+ * Security sensitive users are in general encouraged to enable such
+profiles but unfortunately due to slightly new behavior of the program
+the profile prevents its usage.
+ * Allow
The fix is trivial, so this should be fine.
But I'm just back from PTO and a bit swamped by TODOs right now, so bear with
me as I'll need some time :-)
** Also affects: rsyslog (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: rsyslog (Ubuntu Bionic)
Importance:
I'm hitting the same problem when using a Bionic host with a Bionic
container when using the 5.0 HWE kernel.
@paelzer, I'd appreciate if this could be SRU'ed to Bionic, please :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
This bug was fixed in the package rsyslog - 8.1901.0-1ubuntu2
---
rsyslog (8.1901.0-1ubuntu2) eoan; urgency=medium
[ Simon Deziel ]
* d/usr.sbin.rsyslogd: allow reading/mmap'ing rsyslog binary
This is required for usage inside containers (LP: #1827253)
-- Christian Ehrhardt
On 2019-07-03 10:47 a.m., Christian Ehrhardt wrote:
> I feel bad that this hung around so log, but today I saw it and gave it a
> review.
> This is building in Eoan now.
No worries for the delay, I know where to find you if something more
critical is taking too long to my taste ;) Thank you
This actually is a perfect bug:
- simple case
- solution on a silver plate
- only changing d/* content
- already ubuntu Delta
I feel bad that this hung around so log, but today I saw it and gave it a
review.
This is building in Eoan now.
--
You received this bug notification because you are a
** Changed in: rsyslog (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1827253
Title:
[apparmor] missing 'mr' on binary for
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1827253
Title:
[apparmor] missing 'mr' on binary for usage on containers
Status in rsyslog
** Merge proposal linked:
https://code.launchpad.net/~sdeziel/ubuntu/+source/rsyslog/+git/rsyslog/+merge/366779
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1827253
32 matches
Mail list logo
