[Bug 1892110] Re: Please merge debmirror 2.33 (universe) from Debian testing (main)
No worries about the delay - happy it's being picked up! If there is anything I can do/improve on my part, do let me know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892110 Title: Please merge debmirror 2.33 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892110] Re: Please merge debmirror 2.33 (universe) from Debian testing (main)
I see a SRU being worth it for upstream v2.32 changes. Without those commits, the package produces a mirror that is unusable for Ubuntu 20.04 `apt` clients (and newer). For that reason, I am wondering if I should just pick those commits out, and propose a 20.04+20.10 SRU exclusively for that (as 2.27ubuntu2) instead of pulling all the 2.33 changes in. Any thoughts? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892110 Title: Please merge debmirror 2.33 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906541] [NEW] [SRU] [focal] command-not-found metadata support
Public bug reported: [Impact] * Starting with Ubuntu Focal (20.04), the APT client expects APT sources to provide command-not-found (cnf) metadata files. * This package provides package mirrors, however does not support mirroring this cnf metadata up until upstream version 1:2.32, which is later than the version in Focal (20.04) and Groovy (20.10). * This upload cherry-picks upstream commits 292e9e9c, 39055366 and 9606535d, in order to add the cnf metadata support. [Test Case] * Create a mirror of e.g. `bionic main` and `focal main`: debmirror -d bionic,focal -s main --passive --keyring=/usr/share/keyrings/ubuntu- archive-keyring.gpg --progress /opt/debmirror * Serve the root directory of /opt/debmirror as webroot. * Point APT `sources.list` at this webroot: deb http://mirror.example.com/ubuntu/ focal main * Attempt to run `apt update` on Focal (20.04) client to see that it fails to obtain the cnf metadata. * Optionally run `apt update` on Bionic (18.04) client to see that it works fine without the cnf metadata. [Where problems could occur] * New cnf files are expected to be created and maintained by the debmirror package. The regression risk for incorrectly downloading these files does not serve more harm than not downloading the files whatsoever (current state of 20.04 release), as the APT client does not use the mirror in either case. * The change as uploaded was released in upstream as part of 1:2.32, tagged 23 Mar 2019, and is part of Debian stable. This serves as evidence of it having had testing carried out over time. [Other Info] ** Affects: debmirror (Ubuntu) Importance: Undecided Status: Confirmed ** Patch added: "debmirror_2.27ubuntu2.debdiff" https://bugs.launchpad.net/bugs/1906541/+attachment/5440359/+files/debmirror_2.27ubuntu2.debdiff ** Changed in: debmirror (Ubuntu) Status: New => Incomplete ** Changed in: debmirror (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906541 Title: [SRU] [focal] command-not-found metadata support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1906541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906541] Re: [SRU] [focal] command-not-found metadata support
The relevant upstream changes can be seen at: - https://salsa.debian.org/debian/debmirror/-/commit/292e9e9c999dbfa9cd0269c5b7c8f82af09300fc - https://salsa.debian.org/debian/debmirror/-/commit/39055366f9cd4f161e451cf0621d52f7dc0d5126 - https://salsa.debian.org/debian/debmirror/-/commit/9606535d3789571526f4a208e18b3bfd786e523a -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906541 Title: [SRU] [focal] command-not-found metadata support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1906541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906541] Re: [SRU] [focal] command-not-found metadata support
This SRU further applies to Groovy (20.10) in addition to Focal (20.04). Hirsute (21.04) already has been pushed an upstream merge and is not a concern. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906541 Title: [SRU] [focal] command-not-found metadata support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1906541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899498] Re: Variable $buf not initialized on 2.7 version
This was resolved in upstream commit b50e8880 (https://salsa.debian.org/debian/debmirror/-/commit/b50e8880a187ee5b9e1507201c0815dcd4baf63f) and released as part of version 1:2.28. This resolution is already available as part of the 1:2.33 merge included in Ubuntu Hirsute (21.04). Considering this does not block execution and instead serves as a warning (as Perl simply assumes an empty/0-length initial string for the uninitialized value), this does not appear to directly warrant an SRU (no security vulnerability, no severe regression, no loss of user data, no changes in the environment). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899498 Title: Variable $buf not initialized on 2.7 version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1899498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906541] Re: [SRU] command-not-found metadata support
Thank you for the information, as well as the SecurityTeam/UpdatePreparation link. I will for sure keep that in mind for potential future SRU requests. And thank you for the handling the correction during sponsoring. Let me know if there is anything else I can provide to assist in the process! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906541 Title: [SRU] command-not-found metadata support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1906541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905790] Re: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child
[do_card] (0x4000): Description [/etc/ssl/certs/ca-certificates.crt PKCS#11 Kit ] Manufacturer [PKCS#11 Kit ] flags [1] removable [false] token present [true]. (Sat Feb 27 14:23:47:879084 2021) [p11_child[4287]] [do_card] (0x4000): common name: [ykcs11]. (Sat Feb 27 14:23:47:879090 2021) [p11_child[4287]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/../libykcs11.so]. (Sat Feb 27 14:23:48:000140 2021) [p11_child[4287]] [do_card] (0x4000): Description [Yubico YubiKey CCID 00 00 Yubico (www.yubico.com) ] Manufacturer [Yubico (www.yubico.com) ] flags [7] removable [true] token present [true]. (Sat Feb 27 14:23:48:001134 2021) [p11_child[4287]] [do_card] (0x4000): Found [YubiKey PIV #1234567] in slot [Yubico YubiKey CCID 00 00][0] of module [1][/usr/lib/x86_64-linux-gnu/pkcs11/../libykcs11.so]. (Sat Feb 27 14:23:49:076508 2021) [p11_child[4287]] [do_card] (0x4000): Login NOT required. (Sat Feb 27 14:23:49:076640 2021) [p11_child[4287]] [read_certs] (0x4000): found cert[X.509 Certificate for PIV Authentication][/DC=com/DC=example/OU=Struct/CN=Valters Jansons] (Sat Feb 27 14:23:49:076706 2021) [p11_child[4287]] [do_verification] (0x0040): X509_verify_cert failed [0]. (Sat Feb 27 14:23:49:076715 2021) [p11_child[4287]] [do_verification] (0x0040): X509_verify_cert failed [20][unable to get local issuer certificate]. (Sat Feb 27 14:23:49:076722 2021) [p11_child[4287]] [read_certs] (0x0040): Certificate [X.509 Certificate for PIV Authentication][/DC=com/DC=example/OU=Struct/CN=Valters Jansons] not valid, skipping. (Sat Feb 27 14:23:49:076766 2021) [p11_child[4287]] [read_certs] (0x4000): found cert[X.509 Certificate for PIV Attestation][/CN=Yubico PIV Attestation] (Sat Feb 27 14:23:49:076781 2021) [p11_child[4287]] [do_verification] (0x0040): X509_verify_cert failed [0]. (Sat Feb 27 14:23:49:076787 2021) [p11_child[4287]] [do_verification] (0x0040): X509_verify_cert failed [20][unable to get local issuer certificate]. (Sat Feb 27 14:23:49:076793 2021) [p11_child[4287]] [read_certs] (0x0040): Certificate [X.509 Certificate for PIV Attestation][/CN=Yubico PIV Attestation] not valid, skipping. (Sat Feb 27 14:23:49:076823 2021) [p11_child[4287]] [read_certs] (0x4000): found cert[X.509 Certificate for PIV Attestation 9a][/CN=YubiKey PIV Attestation 9a] (Sat Feb 27 14:23:49:076837 2021) [p11_child[4287]] [do_verification] (0x0040): X509_verify_cert failed [0]. (Sat Feb 27 14:23:49:076843 2021) [p11_child[4287]] [do_verification] (0x0040): X509_verify_cert failed [20][unable to get local issuer certificate]. (Sat Feb 27 14:23:49:076849 2021) [p11_child[4287]] [read_certs] (0x0040): Certificate [X.509 Certificate for PIV Attestation 9a][/CN=YubiKey PIV Attestation 9a] not valid, skipping. (Sat Feb 27 14:23:49:076859 2021) [p11_child[4287]] [do_card] (0x4000): No certificate found. As described in test case outcome 2, trust of the card is outside of the verification scope -- what matters here is the card and certificate are seen, when p11-kit identifies the token is there. As a result, even though the certificate is considered invalid/unusable, this verifies the focal-proposed package finds the card and certificate slots on it. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905790 Title: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1905790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905790] Re: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child
LP appears to have stripped spaces from the `grep` command.
There was filtering on output to reduce verbosity.
Instead of what is seen in previous comment:
# p11-kit list-modules | grep -Eve '^ '
The actual executed verification command there is:
# p11-kit list-modules | grep -Eve '^ {5}'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905790
Title:
Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for
p11_child
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1905790/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926120] [NEW] Please merge debmirror 1:2.34 (universe) from Debian testing (main)
Public bug reported: Upstream has released debmirror 1:2.34: [ Debian Janitor ] * Bump debhelper from old 9 to 12. * Fix day-of-week for changelog entry 20040926. [ Colin Watson ] * Avoid two-argument open. * Avoid bareword file handles. * Correct example in debmirror(1) (closes: #970435). This conflicts and needs to be manually resolved. ** Affects: debmirror (Ubuntu) Importance: Undecided Assignee: Valters Jansons (sigv) Status: In Progress ** Changed in: debmirror (Ubuntu) Assignee: (unassigned) => Valters Jansons (sigv) ** Changed in: debmirror (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926120 Title: Please merge debmirror 1:2.34 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1926120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926120] Re: Please merge debmirror 1:2.34 (universe) from Debian testing (main)
The proposed merge modifies ubuntu-settings.patch, replacing: - documentation "lucid, oneiric, precise" text with "bionic, focal, impish"; - documentation "-d lucid -d precise" example with "-d focal -d impish"; - code defaults "precise" with "impish". The debmirror_2.33ubuntu1-2.34ubuntu1.debdiff highlights this difference clearly. ** Changed in: debmirror (Ubuntu) Assignee: Valters Jansons (sigv) => (unassigned) ** Changed in: debmirror (Ubuntu) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926120 Title: Please merge debmirror 1:2.34 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1926120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926120] Re: Please merge debmirror 1:2.34 (universe) from Debian testing (main)
** Patch added: "debmirror_2.34-2.34ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1926120/+attachment/5492449/+files/debmirror_2.34-2.34ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926120 Title: Please merge debmirror 1:2.34 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1926120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926120] Re: Please merge debmirror 1:2.34 (universe) from Debian testing (main)
** Patch added: "debmirror_2.33ubuntu1-2.34ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1926120/+attachment/5492450/+files/debmirror_2.33ubuntu1-2.34ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926120 Title: Please merge debmirror 1:2.34 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1926120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821251] Re: please add cnf support to debmirror
For completeness sake here, there is a merge request at https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110 which rebases the Ubuntu changes on top of the latest upstream debmirror version, in turn including the required `command-not-found` changes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821251 Title: please add cnf support to debmirror To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-mirror/+bug/1821251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821251] Re: please add cnf support to debmirror
This was handled as a merge in #1892110 and is being handled as an SRU in #1906541 with the patch provided in that SRU ticket including further upstream commits. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821251 Title: please add cnf support to debmirror To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-mirror/+bug/1821251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821251] Re: please add cnf support to debmirror
> The bug linked in the changelog of the SRU is this one, not bug #1906541. Indeed, I am not sure of the proper formatting rules, considering this was my first merge request followed by SRU request of upstream changes. The upstream changelog included the details of the original owner along with this LP# considering the fix originated here. > The SRU template needs to be on this bug How should this be handled as of now? By who? > in general, we should not be opening separate bugs for an SRU In this case, this bug ticket is marked for multiple packages. It seemed more straight-forward to me for the individual changes to be split off in a separate ticket for the SRU itself. Would, instead, multiple SRU templates be expected on this ticket - one for each package? Or would the SRU potentially change depending on the changes required in the individual packages? This process is fairly scary from the outside perspective as these real life scenarios are not covered. Considering this bug has not been fixed for one-and-a-half years, with a patch laying around, I was trying to get the ball rolling. I do ask once again for actionable items as of now, or clarity of whether something should be done whatsoever (as it may instead be handled in other communication channels without information visible to the 'outside world'). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821251 Title: please add cnf support to debmirror To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-mirror/+bug/1821251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821251] Re: please add cnf support to debmirror
TEST CASE: 1. Installed current non-SRU package: apt install debmirror=1:2.27ubuntu1 2. Created a 20.04 Focal mirror: /usr/bin/debmirror -a amd64,i386 -d focal,focal-security,focal-updates,focal-backports -s main,universe,restricted,multiverse --nosource --passive --method=http -h archive.ubuntu.com -r ubuntu --keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg --progress /opt/debmirror 3. Exposed /opt/debmirror as webroot on test.example.com 4. On a separate node, configured APT to use the mirror, via sources.list such as: deb http://test.example.com/ubuntu/ focal main universe restricted multiverse deb http://test.example.com/ubuntu/ focal-security main universe restricted multiverse deb http://test.example.com/ubuntu/ focal-updates main universe restricted multiverse 5. Tried to use mirror on the newly configured client: apt update E: Failed to fetch http://test.example.com/ubuntu/dists/focal/main/cnf/Commands-amd64 404 Not Found [IP: 10.10.10.10 80] E: Failed to fetch http://test.example.com/ubuntu/dists/focal-security/main/cnf/Commands-amd64 404 Not Found [IP: 10.10.10.10 80] E: Failed to fetch http://test.example.com/ubuntu/dists/focal-updates/main/cnf/Commands-amd64 404 Not Found [IP: 10.10.10.10 80] E: Some index files failed to download. They have been ignored, or old ones used instead. 6. Installed SRU package: apt install debmirror=1:2.27ubuntu2.20.04.1 7. Repeated `debmirror` invocation from step 2, in order to pull in cnf files. 8. Repeated `apt update` invocation as from step 5, in order to try using the mirror. VERIFICATION DONE APT client succeeds, and mirrored repository can be successfully used. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821251 Title: please add cnf support to debmirror To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-mirror/+bug/1821251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821251] Re: please add cnf support to debmirror
TEST CASE: 1. Deploy fresh (up-to-date) Ubuntu 20.10 (Groovy) machine. 2. apt install -qqy debmirror=1:2.27ubuntu1 3. debmirror -a amd64 -d groovy -s main --nosource --passive --method=http -h archive.ubuntu.com -r ubuntu --keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg --progress /opt/debmirror 4. echo 'deb file:///opt/debmirror groovy main' > /etc/apt/sources.list.d/file.list 5. apt update # expected E: failed to fetch file:/opt/debmirror/dists/groovy/main/cnf/Commands-amd64 File not found 6. apt install -qqy debmirror=1:2.27ubuntu2.20.10.1 7. debmirror -a amd64 -d groovy -s main --nosource --passive --method=http -h archive.ubuntu.com -r ubuntu --keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg --progress /opt/debmirror 8. echo 'deb file:///opt/debmirror groovy main' > /etc/apt/sources.list.d/file.list 9. apt update # All packages are up to date. VERIFICATION DONE Mirror is usable with updated `debmirror` package. ** Tags removed: verification-needed verification-needed-groovy ** Tags added: verification-done verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821251 Title: please add cnf support to debmirror To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-mirror/+bug/1821251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] [NEW] Invalid SYSLOG_PID for (systemd) journal messages
Public bug reported: [Impact] * On Ubuntu (Focal) 20.04, SSSD 2.2.3-3, logs in Journald have invalid (non-numeric) SYSLOG_PID. Any tooling collecting SYSLOG_PID further, or attempting to work with syslog directly, fail to parse the PID as number. * Systemd does not validate, and simply expects SYSLOG_PID as numeric integers formatted as decimal strings: https://www.freedesktop.org/software/systemd/man/systemd.journal-fields.html#SYSLOG_FACILITY= [Test Case] * Deploy fresh 20.04 image, and update: apt update && apt dist-upgrade * apt -qqy install sssd * cat << EOF > /etc/sssd/sssd.conf [sssd] config_file_version = 2 domains = EXAMPLE.COM services = [nss] [pam] [sudo] [domain/EXAMPLE.COM] id_provider = files access_provider = permit EOF * chmod 600 /etc/sssd/sssd.conf * systemctl restart sssd.service * journalctl -o verbose -u sssd-sudo.service | grep SYSLOG_PID= SYSLOG_PID=sudo * journalctl -u sssd.service # Produces malformed example lines: Dec 07 14:10:00 servername sssd[be[1234]: Starting up * grep sssd /var/log/syslog # Displays non-numeric PIDs: Dec 7 08:00:00 servername sssd[be[EXAMPLE.COM]]: Starting up Dec 7 08:00:00 servername sssd[nss]: Starting up Dec 7 08:00:00 servername sssd[sudo]: Starting up Dec 7 08:00:00 servername sssd[pam]: Starting up [Where problems could occur] * Someone might depend on the malformed output already, and have tooling in place to transform it manually. [Other Info] * Is not reproducible on Ubuntu (Groovy) 20.10 containing SSSD 2.3.1-3. Considering Debian testing is currently at SSSD 2.4.0-1, it does not appear applicable to fix in upstream. ** Affects: sssd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899498] Re: Variable $buf not initialized on 2.27 version
** Summary changed: - Variable $buf not initialized on 2.7 version + Variable $buf not initialized on 2.27 version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899498 Title: Variable $buf not initialized on 2.27 version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1899498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899498] Re: Variable $buf not initialized on 2.27 version
** Patch added: "upstream commit b50e8880a187ee5b9e1507201c0815dcd4baf63f" https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1899498/+attachment/5443821/+files/variable-buf-not-initialized.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899498 Title: Variable $buf not initialized on 2.27 version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1899498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
This could also be something on systemd/journald side. Looking at the source code, it seems SYSLOG_IDENTIFIER is the relevant part that gets set, but then somehow ends up 'leaking' into SYSLOG_PID. https://github.com/SSSD/sssd/blob/sssd-2_2_3/src/util/sss_log.c#L110 There is a further upstream commit which amends the SSSD logging mechanism as https://github.com/SSSD/sssd/commit/18233532b72e62452eac6886652fa633ba055d8c and applying this patch on the 2.2.3-3 source appears to make the SYSLOG_PID go away for me. The change itself modifies the format strings. But the resulting SYSLOG_IDENTIFIER still does not seem fully correct, as with the patch applied I see SYSLOG_IDENTIFIER=sssd_be however I would expect to see SYSLOG_IDENTIFIER=sssd[be[EXAMPLE.COM]]. This does further make me lean in the direction of the bug being on systemd, potentially the processing of sd_journal_send, but I do not have experience in debugging the inner workings there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
** Description changed: [Impact] - * On Ubuntu (Focal) 20.04, SSSD 2.2.3-3, logs in Journald have invalid + * On Ubuntu (Focal) 20.04, SSSD 2.2.3-3, logs in Journald have invalid (non-numeric) SYSLOG_PID. Any tooling collecting SYSLOG_PID further, or attempting to work with syslog directly, fail to parse the PID as number. - * Systemd does not validate, and simply expects SYSLOG_PID as numeric integers formatted as decimal strings: - https://www.freedesktop.org/software/systemd/man/systemd.journal-fields.html#SYSLOG_FACILITY= + * Systemd does not validate, and simply expects SYSLOG_PID as numeric integers formatted as decimal strings: + https://www.freedesktop.org/software/systemd/man/systemd.journal-fields.html#SYSLOG_FACILITY= [Test Case] - * Deploy fresh 20.04 image, and update: -apt update && apt dist-upgrade + * Deploy fresh 20.04 image, and update: + apt update && apt dist-upgrade - * apt -qqy install sssd + * apt -qqy install sssd - * cat << EOF > /etc/sssd/sssd.conf + * cat << EOF > /etc/sssd/sssd.conf [sssd] - config_file_version = 2 - domains = EXAMPLE.COM - services = + config_file_version = 2 + domains = EXAMPLE.COM + services = [nss] [pam] [sudo] [domain/EXAMPLE.COM] - id_provider = files - access_provider = permit + id_provider = files + access_provider = permit EOF - * chmod 600 /etc/sssd/sssd.conf + * chmod 600 /etc/sssd/sssd.conf - * systemctl restart sssd.service + * systemctl restart sssd.service - * journalctl -o verbose -u sssd-sudo.service | grep SYSLOG_PID= -SYSLOG_PID=sudo + * journalctl -o verbose -u sssd-sudo.service | grep SYSLOG_PID= + SYSLOG_PID=sudo - * journalctl -u sssd.service # Produces malformed example lines: -Dec 07 14:10:00 servername sssd[be[1234]: Starting up + * journalctl -u sssd.service # Produces malformed example lines: + Dec 07 14:10:00 servername sssd[be[1234]: Starting up - * grep sssd /var/log/syslog # Displays non-numeric PIDs: -Dec 7 08:00:00 servername sssd[be[EXAMPLE.COM]]: Starting up -Dec 7 08:00:00 servername sssd[nss]: Starting up -Dec 7 08:00:00 servername sssd[sudo]: Starting up -Dec 7 08:00:00 servername sssd[pam]: Starting up + * grep sssd /var/log/syslog # Displays non-numeric PIDs: + Dec 7 08:00:00 servername sssd[be[EXAMPLE.COM]]: Starting up + Dec 7 08:00:00 servername sssd[nss]: Starting up + Dec 7 08:00:00 servername sssd[sudo]: Starting up + Dec 7 08:00:00 servername sssd[pam]: Starting up [Where problems could occur] - * Someone might depend on the malformed output already, and have + * Someone might depend on the malformed output already, and have tooling in place to transform it manually. [Other Info] - - * Is not reproducible on Ubuntu (Groovy) 20.10 containing SSSD 2.3.1-3. Considering Debian testing is currently at SSSD 2.4.0-1, it does not appear applicable to fix in upstream. + + * Is not reproducible on Ubuntu (Groovy) 20.10 containing SSSD 2.3.1-3. + Considering Debian testing is currently at SSSD 2.4.0-1, it does not + appear applicable to fix in upstream. + + * The package itself does not appear to provide any SYSLOG_PID. The + SYSLOG_IDENTIFIER appears to instead 'leak' over into PID, hinting at + trouble on systemd side. SSSD source at: + https://github.com/SSSD/sssd/blob/sssd-2_2_3/src/util/sss_log.c#L110 + + * Applying a change to SYSLOG_IDENTIFIER (prefixing with "sssd[" and suffixing with "]") results in "SYSLOG_IDENTIFIER=sssd_be" being logged, and no SYSLOG_PID being reported. +Cherry-picked upstream commit for testing: https://github.com/SSSD/sssd/commit/18233532b72e62452eac6886652fa633ba055d8c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
** Patch added: "sssd_1.16.1-1ubuntu1.8-2.debdiff" https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+attachment/5460573/+files/sssd_1.16.1-1ubuntu1.8-2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
Upstream developers/maintainers opted to remove custom SYSLOG_IDENTIFIER entirely, allowing the program name to be used in place. This avoids having unexpected "[]" in the TAG. The change is pushed as: - 01cc267 for main branch (upstream version 2.4.1); - 360d8fc for version 1.16 backports. I will prepare debdiffs with the relevant logging changes from upstream. ** Description changed: [Impact] * On Ubuntu (Focal) 20.04, SSSD 2.2.3-3, logs in journald have invalid (non-numeric) SYSLOG_PID. Any tooling collecting SYSLOG_PID further, or attempting to work with syslog directly, fail to parse the PID as number. * systemd does not validate, and simply expects SYSLOG_PID as numeric integers formatted as decimal strings: https://www.freedesktop.org/software/systemd/man/systemd.journal-fields.html#SYSLOG_FACILITY= * Fixed upstream by https://github.com/SSSD/sssd/commit/00e7b1ada3d1c1071eac79b65c17cd2701c2ae6a and https://github.com/SSSD/sssd/commit/18233532b72e62452eac6886652fa633ba055d8c +and https://github.com/SSSD/sssd/commit/01cc2674959ec249702465621f57259fc779650b [Test Case] * Deploy fresh 20.04 image, and update: apt update && apt dist-upgrade * apt -qqy install sssd * cat << EOF > /etc/sssd/sssd.conf [sssd] config_file_version = 2 domains = EXAMPLE.COM services = [nss] [pam] [sudo] [domain/EXAMPLE.COM] id_provider = files access_provider = permit EOF * chmod 600 /etc/sssd/sssd.conf * systemctl restart sssd.service * journalctl -o verbose -u sssd-sudo.service | grep SYSLOG_PID= SYSLOG_PID=sudo * journalctl -u sssd.service # Produces malformed example lines: Dec 07 14:10:00 servername sssd[be[1234]: Starting up * grep sssd /var/log/syslog # Displays non-numeric PIDs: Dec 7 08:00:00 servername sssd[be[EXAMPLE.COM]]: Starting up Dec 7 08:00:00 servername sssd[nss]: Starting up Dec 7 08:00:00 servername sssd[sudo]: Starting up Dec 7 08:00:00 servername sssd[pam]: Starting up [Where problems could occur] * Someone might depend on the malformed output already, and have tooling in -place to transform it manually. + place to transform it manually. - * Changes to log messages can cause lines to get picked up by things like -logwatch that weren't before. + * Changes to log messages can cause lines to get picked up by things like + logwatch that weren't before. ** Patch removed: "sssd_1.16.1-1ubuntu1.8.debdiff" https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+attachment/5456290/+files/sssd_1.16.1-1ubuntu1.8.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
** Patch added: "sssd_2.2.3-3ubuntu0.4-3.debdiff" https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+attachment/5460593/+files/sssd_2.2.3-3ubuntu0.4-3.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
** Patch removed: "sssd_1.16.1-1ubuntu1.8-2.debdiff" https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+attachment/5460573/+files/sssd_1.16.1-1ubuntu1.8-2.debdiff ** Patch added: "sssd_1.16.1-1ubuntu1.8-3.debdiff" https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+attachment/5460591/+files/sssd_1.16.1-1ubuntu1.8-3.debdiff ** Patch removed: "sssd_2.2.3-3ubuntu0.4.debdiff" https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+attachment/5456023/+files/sssd_2.2.3-3ubuntu0.4.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
** Patch removed: "sssd_2.3.1-3ubuntu4.debdiff" https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+attachment/5456636/+files/sssd_2.3.1-3ubuntu4.debdiff ** Patch removed: "sssd_2.3.1-3ubuntu4-2.debdiff" https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+attachment/5456638/+files/sssd_2.3.1-3ubuntu4-2.debdiff ** Patch added: "sssd_2.3.1-3ubuntu4-3.debdiff" https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+attachment/5460597/+files/sssd_2.3.1-3ubuntu4-3.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
** Patch removed: "sssd_2.4.0-1ubuntu4.debdiff" https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+attachment/5456639/+files/sssd_2.4.0-1ubuntu4.debdiff ** Patch added: "sssd_2.4.0-1ubuntu4-2.debdiff" https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+attachment/5460657/+files/sssd_2.4.0-1ubuntu4-2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
These latest debdiffs should include all the necessary changes and should be ready for verification, if there are no concerns about the material changes. To summarize the current proposed changes: Hirsute (21.04) and Groovy (20.10) receive commmits 1823353 and 01cc267 - one to add "sssd[]" in the right places, and other to stop sending the "sssd[]" as SYSLOG_IDENTIFIER. Both of these commits have already been included in the upstream 2.4.1 release. Focal (20.04) receives the same commits as well as 00e7b1a before them - to remove excessive "[sssd[]]" wrapping so that adding "sssd[]" in the later commit makes sense. This has already been included in the upstream 2.3.0 release. Bionic (18.04) receives backports of all three commits Focal receives - 225fe99, 647a130 and 360d8fc. These have not been tagged in the upstream repository with a release tag, however all are included in the sssd-1-16 maintenance branch. Additionally, both Focal (20.04) and Bionic (18.04) receive --with- syslog=journald flag for configure in rules, so that the native journald sending code branch is used - instead of current default which is sending to syslog, which then gets picked into journald. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
Thank you! Similarly as well - feel free to ping me on IRC in case anything comes up. @mhodson tagged this as affecting Bionic, so I provided the patch. It has upstream commit tags, highlighting the upstream Git repository has a maintenance branch for 1.16 at https://github.com/SSSD/sssd/commits/sssd-1-16 On my side, we are using Focal in our infra. So I am personally fine with dropping Bionic if it feels like too much effort for the benefit of cleaning up syslog and journald. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
Performing verification on Groovy (20.10) The case for Groovy was removal of multiple square brackets from syslog output. rsyslog was working with identifiers output such as `be[DOMAIN.COM][1234]:` which is expected to be seen as `sssd_be[1234]:` following the change. # # Install current SSSD from groovy-updates (2.3.1-3ubuntu3) # apt install -y sssd/groovy-updates # apt policy sssd sssd: Installed: 2.3.1-3ubuntu3 Candidate: 2.3.1-3ubuntu3 Version table: 2.3.1-3ubuntu4 400 400 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 Packages *** 2.3.1-3ubuntu3 500 500 http://mirrors.digitalocean.com/ubuntu groovy-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-3 500 500 http://mirrors.digitalocean.com/ubuntu groovy/main amd64 Packages # # Set up minimal SSSD.conf # cat << EOF > /etc/sssd/sssd.conf [sssd] config_file_version = 2 domains = EXAMPLE.COM services = [nss] [pam] [sudo] [domain/EXAMPLE.COM] id_provider = files access_provider = permit EOF # chmod 600 /etc/sssd/sssd.conf # systemctl restart sssd.service # # Check SSSD logging output # journalctl -o verbose -u sssd.service 'MESSAGE=Starting up' | grep SYSLOG_IDENTIFIER= SYSLOG_IDENTIFIER=sssd SYSLOG_IDENTIFIER=be[EXAMPLE.COM] # journalctl -u sssd.service 'MESSAGE=Starting up' -- Logs begin at Wed 2021-02-17 09:11:49 UTC, end at Wed 2021-02-17 09:17:01 UTC. -- Feb 17 09:12:23 groovy-sssd-test sssd[612]: Starting up Feb 17 09:12:23 groovy-sssd-test be[EXAMPLE.COM][646]: Starting up # grep -E '(sssd|be)\[' /var/log/syslog Feb 17 09:12:23 groovy-sssd-test sssd[612]: Starting up Feb 17 09:12:23 groovy-sssd-test be[EXAMPLE.COM][646]: Starting up # # Clean up local log output to see only future logs for verification # journalctl --rotate && journalctl --vacuum-time=1 # echo -n '' > /var/log/syslog # # In-place upgrade to SSSD from groovy-proposed (2.3.1-3ubuntu4) # apt install -y sssd/groovy-proposed # apt policy sssd sssd: Installed: 2.3.1-3ubuntu4 Candidate: 2.3.1-3ubuntu4 Version table: *** 2.3.1-3ubuntu4 400 400 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-3ubuntu3 500 500 http://mirrors.digitalocean.com/ubuntu groovy-updates/main amd64 Packages 2.3.1-3 500 500 http://mirrors.digitalocean.com/ubuntu groovy/main amd64 Packages # # Check SSSD logging output # journalctl -o verbose -u sssd.service 'MESSAGE=Starting up' | grep SYSLOG_IDENTIFIER= SYSLOG_IDENTIFIER=sssd SYSLOG_IDENTIFIER=sssd_be # journalctl -u sssd.service 'MESSAGE=Starting up' -- Logs begin at Wed 2021-02-17 09:21:39 UTC, end at Wed 2021-02-17 09:22:24 UTC. -- Feb 17 09:22:22 groovy-sssd-test sssd[1340]: Starting up Feb 17 09:22:22 groovy-sssd-test sssd_be[1341]: Starting up # grep -E '(sssd|be)\[' /var/log/syslog Feb 17 09:22:22 groovy-sssd-test sssd[1340]: Starting up Feb 17 09:22:22 groovy-sssd-test sssd_be[1341]: Starting up This verifies the groovy-proposed package fixes the SYSLOG_IDENTIFIER/rsyslog format bug. ** Tags removed: verification-needed verification-needed-groovy ** Tags added: verification-done verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
The description was updated to reflect changes in the test case for Groovy verification, as the initial test case was valid for Bionic and Focal (already mitigated on Groovy from upstream). ** Description changed: [Impact] * On Ubuntu (Focal) 20.04, SSSD 2.2.3-3, logs in journald have invalid (non-numeric) SYSLOG_PID. Any tooling collecting SYSLOG_PID further, or attempting to work with syslog directly, fail to parse the PID as number. * systemd does not validate, and simply expects SYSLOG_PID as numeric - integers formatted as decimal strings: https://www.freedesktop.org/software/systemd/man/systemd.journal-fields.html#SYSLOG_FACILITY= + integers formatted as decimal strings: + https://www.freedesktop.org/software/systemd/man/systemd.journal-fields.html#SYSLOG_FACILITY= * Fixed upstream by https://github.com/SSSD/sssd/commit/00e7b1ada3d1c1071eac79b65c17cd2701c2ae6a and https://github.com/SSSD/sssd/commit/18233532b72e62452eac6886652fa633ba055d8c -and https://github.com/SSSD/sssd/commit/01cc2674959ec249702465621f57259fc779650b + and https://github.com/SSSD/sssd/commit/01cc2674959ec249702465621f57259fc779650b [Test Case] * Deploy fresh 20.04 image, and update: apt update && apt dist-upgrade * apt -qqy install sssd * cat << EOF > /etc/sssd/sssd.conf [sssd] config_file_version = 2 domains = EXAMPLE.COM services = [nss] [pam] [sudo] [domain/EXAMPLE.COM] id_provider = files access_provider = permit EOF * chmod 600 /etc/sssd/sssd.conf * systemctl restart sssd.service - * journalctl -o verbose -u sssd-sudo.service | grep SYSLOG_PID= - SYSLOG_PID=sudo + * journalctl -o verbose -u sssd.service 'MESSAGE=Starting up' | + grep SYSLOG_IDENTIFIER= + SYSLOG_IDENTIFIER=sssd + SYSLOG_IDENTIFIER=sssd[be - * journalctl -u sssd.service # Produces malformed example lines: - Dec 07 14:10:00 servername sssd[be[1234]: Starting up + * journalctl -u sssd.service 'MESSAGE=Starting up' + Dec 07 14:10:00 servername sssd[1234]: Starting up + Dec 07 14:10:00 servername sssd[be[1235]: Starting up - * grep sssd /var/log/syslog # Displays non-numeric PIDs: - Dec 7 08:00:00 servername sssd[be[EXAMPLE.COM]]: Starting up - Dec 7 08:00:00 servername sssd[nss]: Starting up - Dec 7 08:00:00 servername sssd[sudo]: Starting up - Dec 7 08:00:00 servername sssd[pam]: Starting up + * grep -E '(sssd|be)[\[\:]' /var/log/syslog + Dec 07 14:10:00 servername sssd: Starting up + Dec 07 14:10:00 servername sssd[be[PROD.WORK]]: Starting up [Where problems could occur] * Someone might depend on the malformed output already, and have tooling in - place to transform it manually. +place to transform it manually. * Changes to log messages can cause lines to get picked up by things like - logwatch that weren't before. +logwatch that weren't before. ** Description changed: [Impact] * On Ubuntu (Focal) 20.04, SSSD 2.2.3-3, logs in journald have invalid (non-numeric) SYSLOG_PID. Any tooling collecting SYSLOG_PID further, or attempting to work with syslog directly, fail to parse the PID as number. * systemd does not validate, and simply expects SYSLOG_PID as numeric integers formatted as decimal strings: - https://www.freedesktop.org/software/systemd/man/systemd.journal-fields.html#SYSLOG_FACILITY= + https://www.freedesktop.org/software/systemd/man/systemd.journal-fields.html#SYSLOG_FACILITY= * Fixed upstream by https://github.com/SSSD/sssd/commit/00e7b1ada3d1c1071eac79b65c17cd2701c2ae6a and https://github.com/SSSD/sssd/commit/18233532b72e62452eac6886652fa633ba055d8c and https://github.com/SSSD/sssd/commit/01cc2674959ec249702465621f57259fc779650b [Test Case] * Deploy fresh 20.04 image, and update: apt update && apt dist-upgrade * apt -qqy install sssd * cat << EOF > /etc/sssd/sssd.conf [sssd] config_file_version = 2 domains = EXAMPLE.COM services = [nss] [pam] [sudo] [domain/EXAMPLE.COM] id_provider = files access_provider = permit EOF * chmod 600 /etc/sssd/sssd.conf * systemctl restart sssd.service - * journalctl -o verbose -u sssd.service 'MESSAGE=Starting up' | + * journalctl -o verbose -u sssd.service 'MESSAGE=Starting up' | grep SYSLOG_IDENTIFIER= - SYSLOG_IDENTIFIER=sssd - SYSLOG_IDENTIFIER=sssd[be + SYSLOG_IDENTIFIER=sssd + SYSLOG_IDENTIFIER=sssd[be - * journalctl -u sssd.service 'MESSAGE=Starting up' + * journalctl -u sssd.service 'MESSAGE=Starting up' Dec 07 14:10:00 servername sssd[1234]: Starting up Dec 07 14:10:00 servername sssd[be[1235]: Starting up - * grep -E '(sssd|be)[\[\:]' /var/log/syslog + * grep -E '(sssd|be)[\[\:]' /var/log/syslog Dec 07 14:10:00 servername sssd: Starting up - Dec 07 14:10:00 servername sssd[be[PROD.WORK]]: Starting up + Dec 07 14:10:00
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
The fix for Hirsute is in 2.4.0-1ubuntu4 which did not get pushed further into -release. Currently Hirsute has 2.4.0-1ubuntu5 in -proposed (since Feb 16) with the global archive ownership rebuild. ** Changed in: sssd (Ubuntu Hirsute) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
Performing verification on Focal (20.04) # # Install current SSSD from focal-updates (2.2.3-3ubuntu0.3) # apt install -y sssd/focal-updates # apt policy sssd sssd: Installed: 2.2.3-3ubuntu0.3 Candidate: 2.2.3-3ubuntu0.3 Version table: 2.2.3-3ubuntu0.4 400 400 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages *** 2.2.3-3ubuntu0.3 500 500 http://mirrors.digitalocean.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.2.3-3ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 2.2.3-3 500 500 http://mirrors.digitalocean.com/ubuntu focal/main amd64 Packages # # Set up minimal SSSD.conf # cat << EOF > /etc/sssd/sssd.conf [sssd] config_file_version = 2 domains = EXAMPLE.COM services = [nss] [pam] [sudo] [domain/EXAMPLE.COM] id_provider = files access_provider = permit EOF # chmod 600 /etc/sssd/sssd.conf # systemctl restart sssd.service # # Check SSSD logging output # journalctl -o verbose -u sssd.service 'MESSAGE=Starting up' | grep SYSLOG_IDENTIFIER= SYSLOG_IDENTIFIER=sssd SYSLOG_IDENTIFIER=sssd[be # journalctl -u sssd.service 'MESSAGE=Starting up' -- Logs begin at Fri 2021-02-19 18:32:32 UTC, end at Fri 2021-02-19 18:32:39 UTC. -- Feb 19 18:32:39 focal-sssd-test sssd[2712]: Starting up Feb 19 18:32:39 focal-sssd-test sssd[be[2723]: Starting up # grep -E '(sssd|be)[\[\:]' /var/log/syslog Feb 19 18:32:39 focal-sssd-test sssd: Starting up Feb 19 18:32:39 focal-sssd-test sssd[be[EXAMPLE.COM]]: Starting up # # Clean up local log output to see only future logs for verification # journalctl --rotate && journalctl --vacuum-time=1 # echo -n '' > /var/log/syslog # # In-place upgrade to SSSD from focal-proposed (2.2.3-3ubuntu0.4) # apt install -y sssd/focal-proposed # apt policy sssd sssd: Installed: 2.2.3-3ubuntu0.4 Candidate: 2.2.3-3ubuntu0.4 Version table: *** 2.2.3-3ubuntu0.4 400 400 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 2.2.3-3ubuntu0.3 500 500 http://mirrors.digitalocean.com/ubuntu focal-updates/main amd64 Packages 2.2.3-3ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 2.2.3-3 500 500 http://mirrors.digitalocean.com/ubuntu focal/main amd64 Packages # # Check SSSD logging output # journalctl -o verbose -u sssd.service 'MESSAGE=Starting up' | grep SYSLOG_IDENTIFIER= SYSLOG_IDENTIFIER=sssd SYSLOG_IDENTIFIER=sssd_be # journalctl -u sssd.service 'MESSAGE=Starting up' -- Logs begin at Fri 2021-02-19 18:33:40 UTC, end at Fri 2021-02-19 18:34:00 UTC. -- Feb 19 18:33:58 focal-sssd-test sssd[3170]: Starting up Feb 19 18:33:58 focal-sssd-test sssd_be[3171]: Starting u # grep -E '(sssd|be)[\[\:]' /var/log/syslog Feb 19 18:33:58 focal-sssd-test sssd[3170]: Starting up Feb 19 18:33:58 focal-sssd-test sssd_be[3171]: Starting up This verifies the focal-proposed package fixes the SYSLOG_PID/SYSLOG_IDENTIFIER/rsyslog format bug. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
Is there any way to assist in moving this bug along? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
It does not appear that systemd-journald is automatically parsing
SYSLOG_IDENTIFIER. The following sample program:
#include
int main(int argc, char *argv[]) {
sd_journal_send("MESSAGE=%s", "Hello world!",
"SYSLOG_IDENTIFIER=%s", "sssd[sudo]",
NULL);
}
produces logs with:
MESSAGE=Hello world!
SYSLOG_IDENTIFIER=sssd[sudo]
There is no SYSLOG_PID, and SYSLOG_IDENTIFIER is the literal
"sssd[sudo]".
/var/log/syslog also contains: "
sssd[sudo][12345]: Hello world!"
systemd.journal-fields documentation also states the fields are not
explicitly validated, so that implies to me no processing on them should
be taking place.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908065
Title:
Invalid SYSLOG_PID for (systemd) journal messages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
Sorry Dan, I did not initially grasp the full implication of your message if it was intended that way. Thank you for the upstream commit linked. Will poke around a bit more and provide a proposed debdiff to be sponspored then, but to summarize from SSSD side: indeed not reproducible with a minimal C program (and is indeed Status: Invalid for systemd) as the sd_journal_send() branch never actually runs from SSSD side. The rules override_dh_auto_configure does not set --with- syslog=journald in the Focal version, and instead leaves the default --with-syslog=syslog path, indicated by Journald showing _TRANSPORT=syslog as well. That must be where the SYSLOG_PID parsing comes in to play, and that is the reason why the syslog messages are indeed malformed the way they are. The newer packages (for 20.10 and 21.04) set the Journald logging configuration flag, and have the referenced program name clean-up commit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
** Patch added: "sssd_2.2.3-3ubuntu0.4.debdiff" https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+attachment/5456023/+files/sssd_2.2.3-3ubuntu0.4.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
Thank you for subscribing ubuntu-sponsors. Feel free to handles this after 2.2.3-3ubuntu0.3 reaches focal-updates, as that was published on focal-proposed yesterday (2021-01-22), and this change is not necessarily of such high priority compared to it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
Sorry, in the last message I meant the Focal 20.04 debdiff includes both. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
The Bionic 20.04 debdiff (as 2.2.3-3ubuntu0.4) does include both referenced commits. I will take a look and provide debdiffs for the other affected versions - Bionic 18.04, Groovy 20.10, Hirsute 21.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
** Patch added: "sssd_1.16.1-1ubuntu1.8.debdiff" https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+attachment/5456290/+files/sssd_1.16.1-1ubuntu1.8.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
** Patch added: "sssd_2.3.1-3ubuntu4.debdiff" https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+attachment/5456636/+files/sssd_2.3.1-3ubuntu4.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
New revision of sssd_2.3.1-3ubuntu4 debdiff with changes to the patch description, clarifying that the previously referred commit is included in an upstream release already and not a part of the patch series. ** Patch added: "sssd_2.3.1-3ubuntu4-2.debdiff" https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+attachment/5456638/+files/sssd_2.3.1-3ubuntu4-2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
** Patch added: "sssd_2.4.0-1ubuntu4.debdiff" https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+attachment/5456639/+files/sssd_2.4.0-1ubuntu4.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
For Bionic (18.04) sssd_1.16.1-1ubuntu1.8.debdiff contains rules change (--with-syslog=journald) along with upstream commits 225fe99 and 647a130 (backports for 1.16). For Focal (20.04) sssd_2.2.3-3ubuntu0.4.debdiff contains rules change (--with-syslog=journald) along with upstream commits 00e7b1a and 1823353. For Groovy (20.10) sssd_2.3.1-3ubuntu4-2.debdiff contains upstream commit 1823353. The rules already contain the Syslog/Journald override, and upstream commit 00e7b1a has already been included in the original source (as part of v2.3.0). For Hirsute (21.04) sssd_2.4.0-1ubuntu4.debdiff contains upstream commit 1823353. Rationale is the same as for Groovy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
Bionic and Hirsute do not have anything in -proposed currently. Focal and Groovy are waiting on LP: #1910611 to be released out from -proposed, and still in need of verification. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
> Probably someone should explain the problem to upstream sssd and suggest they use something other than brackets; literally anything else should avoid this problem, e.g. parenthesis, curly brackets, etc. This formatting with "[" in syslog TAG is already a concern on Groovy and Hirsute even without that upstream commit. For example, you could see "be[EXAMPLE.COM]" provided as SYSLOG_IDENTIFIER in the upstream 2.3.1 and 2.4.0 versions. I will take this discussion upstream then. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages
Opened https://github.com/SSSD/sssd/pull/5477 proposing to replace square brackets with parentheses. I will wait for review there before proposing new debdiffs with the change, in case either I missed something or upstream wants other tokens than parentheses. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892110] [NEW] Please merge debmirror 2.33 (universe) from Debian testing (main)
Public bug reported: MoM reports a conflict for debian/control and debian/rules files. (debian/control) Upstream changed Priority from extra to optional: - https://salsa.debian.org/debian/debmirror/-/commit/b264963519c7528f74ec24d5b227b87578f745b3 (debian/control) Upstream switched from debhelper 7.0.50 to debhelper 9: - https://salsa.debian.org/debian/debmirror/-/commit/bec30c0455701fd08e3830606643850f2431dcd5 (debian/control) Upstream switched from debian/compat to debhelper-compat: - https://salsa.debian.org/debian/debmirror/-/commit/0e3da11567befe68d2db73d041ac97d091866118 (debian/rules) Upstream added automatic updates to package Version: - https://salsa.debian.org/debian/debmirror/-/commit/80cc184229aefedc0eb1882f777f95cc1d4e26b0 - https://salsa.debian.org/debian/debmirror/-/commit/c3bf9787cf2cc0f44724160a7be6e79e549891ce - https://salsa.debian.org/debian/debmirror/-/commit/26d1a28c48a3d1eb5cc1d0f004e7ab4d94ae7512 ** Affects: debmirror (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892110 Title: Please merge debmirror 2.33 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892110] Re: Please merge debmirror 2.33 (universe) from Debian testing (main)
** Changed in: debmirror (Ubuntu) Assignee: (unassigned) => Valters Jansons (valterj) ** Patch added: "debdiff between Debian .dsc and my modified one" https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110/+attachment/5402653/+files/debmirror_2.33_2.33ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892110 Title: Please merge debmirror 2.33 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892110] Re: Please merge debmirror 2.33 (universe) from Debian testing (main)
** Patch added: "debdiff between the old Ubuntu .dsc and my modified one" https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110/+attachment/5402654/+files/debmirror_2.27ubuntu1_2.33ubuntu1.debdiff ** Changed in: debmirror (Ubuntu) Assignee: Valters Jansons (valterj) => (unassigned) ** Changed in: debmirror (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892110 Title: Please merge debmirror 2.33 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892110] Re: Please merge debmirror 2.33 (universe) from Debian testing (main)
** Changed in: debmirror (Ubuntu) Status: Confirmed => Incomplete ** Patch removed: "debdiff between Debian .dsc and my modified one" https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110/+attachment/5402653/+files/debmirror_2.33_2.33ubuntu1.debdiff ** Patch removed: "debdiff between the old Ubuntu .dsc and my modified one" https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110/+attachment/5402654/+files/debmirror_2.27ubuntu1_2.33ubuntu1.debdiff ** Changed in: debmirror (Ubuntu) Assignee: (unassigned) => Valters Jansons (valterj) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892110 Title: Please merge debmirror 2.33 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892110] Re: Please merge debmirror 2.33 (universe) from Debian testing (main)
** Patch added: "debdiff between the old Ubuntu .dsc and my modified one" https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110/+attachment/5402660/+files/debmirror_2.27ubuntu1_2.33ubuntu1.debdiff ** Changed in: debmirror (Ubuntu) Assignee: Valters Jansons (valterj) => (unassigned) ** Changed in: debmirror (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892110 Title: Please merge debmirror 2.33 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892110] Re: Please merge debmirror 2.33 (universe) from Debian testing (main)
Adjusted the changelog for Groovy. ** Patch added: "debdiff between Debian .dsc and my modified one" https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110/+attachment/5402659/+files/debmirror_2.33_2.33ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892110 Title: Please merge debmirror 2.33 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876640] Re: debmirror 2.27 don't download cnf folder
*** This bug is a duplicate of bug 1821251 *** https://bugs.launchpad.net/bugs/1821251 ** This bug has been marked a duplicate of bug 1821251 please add cnf support to debmirror -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876640 Title: debmirror 2.27 don't download cnf folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1876640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892110] Re: Please merge debmirror 2.33 (universe) from Debian testing (main)
** Patch added: "debdiff between the old Ubuntu .dsc and my modified one" https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110/+attachment/5403649/+files/debmirror_2.27ubuntu1_2.33ubuntu1.debdiff ** Patch removed: "debdiff between the old Ubuntu .dsc and my modified one" https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110/+attachment/5402660/+files/debmirror_2.27ubuntu1_2.33ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892110 Title: Please merge debmirror 2.33 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892110] Re: Please merge debmirror 2.33 (universe) from Debian testing (main)
Refreshed the existing patches properly to be based on updated upstream source, without complaints about hunks having been shifted around. ** Patch added: "debdiff between Debian .dsc and my modified one" https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110/+attachment/5403648/+files/debmirror_2.33_2.33ubuntu1.debdiff ** Patch removed: "debdiff between Debian .dsc and my modified one" https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110/+attachment/5402659/+files/debmirror_2.33_2.33ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892110 Title: Please merge debmirror 2.33 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940907] Re: gist-paste command is too old and can no longer authenticate
Fixed upstream in https://github.com/defunkt/gist/commit/635b1437a513e9a13367827ee3f74fbbdaa54aa8 and included in v5.1.0, which is why the v6.0.0 release in Hirsute works as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940907 Title: gist-paste command is too old and can no longer authenticate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gist/+bug/1940907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940907] Re: gist-paste command is too old and can no longer authenticate
** Description changed:
- Please update the `gist` package to the latest version in the
- repositories for 18.04 and 20.04. The current versions in those releases
- have a `gist-paste` command that can no longer authenticate to GitHub,
- making the package useless.
+ [Impact]
- I believe Ubuntu 21.04 uses a working version.
+ * Gist upload (arguable as the core function of the package) is not
+ functioning. Package versions prior to 5.1.0 provide user's access token
+ as a query (URL) parameter, however GitHub changes now require it to be
+ provided as a HTTP(S) header:
+ https://developer.github.com/changes/2019-11-05-deprecated-passwords-
+ and-authorizations-api/#authenticating-using-query-parameters
- $ gist-paste -f Test.java -t java -p -d 'Fast method tester' -R Test.java
- Error: Got Net::HTTPBadRequest from gist: {"message":"Must specify access
token via Authorization header. ht
-
tps://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param","documentation_url":"htt
- ps://docs.github.com/v3/#oauth2-token-sent-in-a-header"}
+ * --login is not functioning. Package versions prior to 6.0.0 use an
+ authentication endpoint that has been shut down since November 2020:
+ https://developer.github.com/changes/2020-02-14-deprecating-oauth-auth-
+ endpoint/
- $ lsb_release -a
- No LSB modules are available.
- Distributor ID: Ubuntu
- Description:Ubuntu 20.04.2 LTS
- Release:20.04
- Codename: focal
+ [Test Plan]
- $ apt-cache policy gist
- gist:
- Installed: 5.0.0-4
- Candidate: 5.0.0-4
- Version table:
- *** 5.0.0-4 500
- 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
- 500 http://archive.ubuntu.com/ubuntu focal/universe i386 Packages
- 100 /var/lib/dpkg/status
+ * rm ~/.gist # stored credentials
+ * gist-paste --login
- ProblemType: Bug
- DistroRelease: Ubuntu 20.04
- Package: gist 5.0.0-4
- ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
- Uname: Linux 5.4.0-77-generic x86_64
- ApportVersion: 2.20.11-0ubuntu27.18
- Architecture: amd64
- CasperMD5CheckResult: skip
- Date: Tue Aug 24 04:42:58 2021
- InstallationDate: Installed on 2021-05-19 (96 days ago)
- InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64
(20200401)
- PackageArchitecture: all
- ProcEnviron:
- TERM=tmux-256color
- PATH=(custom, no user)
- XDG_RUNTIME_DIR=
- LANG=en_US.UTF-8
- SHELL=/bin/bash
- SourcePackage: gist
- UpgradeStatus: No upgrade log present (probably fresh install)
+ Currently (5.0.0-4 focal) fails; output:
+ Obtaining OAuth2 access_token from github.
+ GitHub username: username
+ GitHub password:
+ RuntimeError: Got Net::HTTPNotFound from gist: {"message":"Not
Found","documentation_url":"https://docs.github.com/rest"}
+
+ Expected web-based OAuth; output:
+ Requesting login parameters...
+ Please sign in at https://github.com/login/device
+ and enter code: DEAD-BEEF
+ Success!
https://github.com/settings/connections/applications/402bac389df41f24c62f
+
+ * echo 'class Test {}' > Test.java
+ * gist-paste -f Test.java -t java -p -d 'Fast method tester' -R Test.java
+
+ Currently (5.0.0-4 focal) fails; output:
+ Error: Got Net::HTTPBadRequest from gist: {"message":"Must specify access
token via Authorization header.
https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param","documentation_url":"https://docs.github.com/v3/#oauth2-token-sent-in-a-header"}
+
+ Expected randomly-generated Gist link; output:
+ https://gist.github.com/username/eed178872769488d84378b13de8bb698/raw
+
+ [Where problems could occur]
+
+ * The SRU requires a rewrite of authentication workflow, with a new
+ OAuth (web-based) approach.
+
+The `--login` invocation previously accepted two inputs over stdin,
+ however it now waits for user to do carry out manual steps based on
+ instructions displayed (opening a page in web browser, and entering a
+ code, as visible in Test Plan above). Although automated scripts should
+ not be invoking `--login`, as the relevant token is stored persistently
+ in user's home, if in any case they do so then it could halt further
+ processing of the script.
+
+ [Other Info]
+
+ * These changes have been tested as part of package release on prior Ubuntu
versions, as well as landing in Debian stable:
+- Gist 5.1.0-1 was published in Groovy (20.10) with relevant HTTP(S)
header change.
+- Gist 6.0.0-1 was published in Hirsute (21.04) with relevant changes for
OAuth workflow (--login).
** Summary changed:
- gist-paste command is too old and can no longer authenticate
+ [SRU] Authentication/Authorization broken due to GitHub platform changes
** Patch added: "gist_5.0.0-4ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gist/+bug/1940907/+attachment/5525898/+files/gist_5.0.0-4ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
[Bug 1940907] Re: [SRU] Authentication/Authorization broken due to GitHub platform changes
The patch for v5.0.0 (Focal) looks good to me, and test case passes locally -- I can log in and upload a Gist as expected. I am currently not planning on providing a patch for v4.6.1 (Bionic). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940907 Title: [SRU] Authentication/Authorization broken due to GitHub platform changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gist/+bug/1940907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952248] [NEW] Please merge debmirror 1:2.36 (universe) from Debian testing (main)
Public bug reported: Upstream has released debmirror 1:2.36: [ Sascha Lucas ] * Enable Ubuntu ESM mirroring. [ Debian Janitor ] * Remove constraints unnecessary since buster: + Build-Depends: Drop versioned constraint on libwww-perl and perl. + debmirror: Drop versioned constraint on libwww-perl and perl in Depends. ** Affects: debmirror (Ubuntu) Importance: Undecided Status: Confirmed ** Changed in: debmirror (Ubuntu) Status: New => In Progress ** Changed in: debmirror (Ubuntu) Assignee: (unassigned) => Valters Jansons (sigv) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952248 Title: Please merge debmirror 1:2.36 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1952248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952248] Re: Please merge debmirror 1:2.36 (universe) from Debian testing (main)
The diff applies Depends and Build-Depends change from Debian upstream, while retaining quilt on Build-Depends. All patches are refreshed to apply cleanly. In d/patches/ubuntu-settings.patch, references to Impish (21.10) are replaced with Jammy (22.04). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952248 Title: Please merge debmirror 1:2.36 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1952248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952248] Re: Please merge debmirror 1:2.36 (universe) from Debian testing (main)
** Patch added: "1-2.36-2.36ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1952248/+attachment/5543372/+files/1-2.36-2.36ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952248 Title: Please merge debmirror 1:2.36 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1952248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952248] Re: Please merge debmirror 1:2.36 (universe) from Debian testing (main)
** Patch added: "1-2.35ubuntu1-2.36ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1952248/+attachment/5543373/+files/1-2.35ubuntu1-2.36ubuntu1.debdiff
** Changed in: debmirror (Ubuntu)
Status: In Progress => Confirmed
** Changed in: debmirror (Ubuntu)
Assignee: Valters Jansons (sigv) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952248
Title:
Please merge debmirror 1:2.36 (universe) from Debian testing (main)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1952248/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952248] Re: Please merge debmirror 1:2.36 (universe) from Debian testing (main)
** Patch added: "2-2.35ubuntu1-2.36ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1952248/+attachment/5543375/+files/2-2.35ubuntu1-2.36ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952248 Title: Please merge debmirror 1:2.36 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1952248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952248] Re: Please merge debmirror 1:2.36 (universe) from Debian testing (main)
** Patch added: "2-2.36-2.36ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1952248/+attachment/5543374/+files/2-2.36-2.36ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952248 Title: Please merge debmirror 1:2.36 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1952248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952248] Re: Please merge debmirror 1:2.36 (universe) from Debian testing (main)
Apologies - re-uploaded debdiff, as changelog contained LP bug number for 1:2.35 merge and not this bug. ** Patch removed: "1-2.36-2.36ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1952248/+attachment/5543372/+files/1-2.36-2.36ubuntu1.debdiff ** Patch removed: "1-2.35ubuntu1-2.36ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1952248/+attachment/5543373/+files/1-2.35ubuntu1-2.36ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952248 Title: Please merge debmirror 1:2.36 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1952248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957079] [NEW] [SRU] Update WALinuxAgent to 2.5.0
Public bug reported: [Impact] This release contains both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. See the changelog entry below for a list of changes. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/walinuxagentUpdates The Microsoft Azure Linux Agent team will execute their testsuite, which includes extension testing , against the walinuxagent that is in -proposed. A successful run will be required before the proposed walinuxagent can be let into -updates. The CPC team will be in charge of attaching a summary of testing to the bug. CPC team members will not mark 'verification-done' until this has happened. [Pre-SRU Test Cases] 1.) Launch instance on Azure 2.) Upgrade walinuxagent (usually from PPA) 3.) Confirm that "waagent" is running, check /var/log/waagent.log for errors 4.) Reboot, repeat step 3 [SRU Test Cases] 1.) Build new cloud image with -proposed package 2.) Boot instance 3.) Confirm that instance provisioned 4.) Run standard tests and regression tests 5.) Repeat from step 2 for all other Azure VM Sizes. [Change Log] Current published release (v2.2.46) was officially released 15 Jan 2020. During the subsequent approx two year period there have been multiple intermediate releases, often with lengthy change logs. https://github.com/Azure/WALinuxAgent/releases/tag/v2.2.48.1 - Refactoring GoalState class out of Protocol, making Protocol thread-safe, removing stale dependencies of Protocol and removing the dependency on the file system to read the Protocol info - Adding and improving log messages and adding thread names to each logline - Improving agent status reporting - Provisioning Agent changes - Other fixes https://github.com/Azure/WALinuxAgent/releases/tag/v2.2.49.2 - Improvements in cgroups - Testing and dev-infra improvements - Documentation improvements - Logging and telemetry improvements - Extension workflow improvements - Other https://github.com/Azure/WALinuxAgent/releases/tag/v2.2.52 - Major bug fixes - New features/improvements * Add API for uploading logs via host plugin * Fixed delays for HTTP retries rather than exponential delays - Documentation changes - Other fixes https://github.com/Azure/WALinuxAgent/releases/tag/v2.2.53 - Bug fixes - New features and improvements * Recreate handler environment file on service startup * Add log collection tool and thread * Thread interface * Verify that the CPU and Memory cgroups for the agent are properly initialized; disabled cgroups if they are not active - Telemetry and logging improvements - Documentation updates - Testing and code quality improvements https://github.com/Azure/WALinuxAgent/releases/tag/v2.2.53.1 - Extension Telemetry Pipeline as a private-preview feature https://github.com/Azure/WALinuxAgent/releases/tag/v2.2.54.2 - New Features and Improvements * PA changes to check cloud-init * log collector * cgroups CPU percentage py processor count * Parse InVMGoalStateMetaData from Extension Config * iscsi disk support for agent configs * Add support for VMs with multiple IB devices * Python 3.9 support * Add support for CBL-Mariner distro * Enable Provisioning.MonitorHostName for Ubuntu * Added supportedFeatures flag in status reporting * Parse ext runtime settings * GHA merge validation * Cgroups improvements * renamed the eventsFolder variable for preview and enabled ETP * Agent slice and custom unit files telemetry * Make IPoIB interface online * Add option to disable NetworkConfigurationChanges * Log network configuration on service start * Setup persistent firewall rules on service restart - Bug Fixes https://github.com/Azure/WALinuxAgent/releases/tag/v2.3.0.2 - New Features * Enforce CPUQuota on agent * Add support for RequiredFeatures and GoalStateAggregateStatus APIs * Added fallback locations for extension manifests - Bug fixes - Logging improvements - Test improvements https://github.com/Azure/WALinuxAgent/releases/tag/v2.3.1.1 - revert for reducing the time window where we restart the network interfaces of the VM https://github.com/Azure/WALinuxAgent/releases/tag/v2.4.0.2 - New Features * Support for Multi config - Bug Fixes - Logging improvements - Test improvements https://github.com/Azure/WALinuxAgent/releases/tag/v2.5.0.2 - New Features and improvements * Enable Extension Telemetry Pipeline * Enable Periodic Log Collection in systemd distros * Implement InitialGoalStatePeriod parameter + improvements in logging goal state processing * Fix operation name in InitializeHostPlugin event * Mock systemctl stop cmd * Report transitioning when status file not found * Dont create default status file for Single-Config extensions * Do not create placeholder status file for AKS extensions * Save waagent_status to history folder and add additional details to the status file * Rename Debug.FetchVmSetti
[Bug 1940419] [NEW] Please merge debmirror 1:2.35 (universe) from Debian stable (main)
Public bug reported: Upstream has released debmirror 1:2.35: [ Kees Cook ] * Remove temporary files created while verifying InRelease (closes: #961197). ** Affects: debmirror (Ubuntu) Importance: Undecided Assignee: Valters Jansons (sigv) Status: In Progress ** Changed in: debmirror (Ubuntu) Status: New => In Progress ** Changed in: debmirror (Ubuntu) Assignee: (unassigned) => Valters Jansons (sigv) ** Description changed: Upstream has released debmirror 1:2.35: [ Kees Cook ] - * Remove temporary files created while verifying InRelease (closes: #961197). + * Remove temporary files created while verifying InRelease (closes: + #961197). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940419 Title: Please merge debmirror 1:2.35 (universe) from Debian stable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1940419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940419] Re: Please merge debmirror 1:2.35 (universe) from Debian stable (main)
** Patch added: "debmirror_2.35_2.35ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1940419/+attachment/5518755/+files/debmirror_2.35_2.35ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940419 Title: Please merge debmirror 1:2.35 (universe) from Debian stable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1940419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940419] Re: Please merge debmirror 1:2.35 (universe) from Debian stable (main)
** Patch added: "debmirror_2.34ubuntu1_2.35ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1940419/+attachment/5518756/+files/debmirror_2.34ubuntu1_2.35ubuntu1.debdiff ** Changed in: debmirror (Ubuntu) Assignee: Valters Jansons (sigv) => (unassigned) ** Changed in: debmirror (Ubuntu) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940419 Title: Please merge debmirror 1:2.35 (universe) from Debian stable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1940419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
