Fixes to the issues listed and various other small buglets.

How to install

sudo dnf upgrade --advisory=FEDORA-2021-1c1a870ceb

This update has been submitted for testing by zbyszek.

3 weeks ago

This update's test gating status has been changed to 'ignored'.

3 weeks ago

This update's test gating status has been changed to 'waiting'.

3 weeks ago

This update's test gating status has been changed to 'ignored'.

3 weeks ago
User Icon imabug provided feedback 3 weeks ago
karma
BZ#1933137 Warning: The unit file, source configuration file or drop-ins of httpd.service changed on disk. Run 'systemctl daemon-reload' to reload units
User Icon jdieter commented & provided feedback 3 weeks ago
karma

This seems to also fix #1941335

zbyszek edited this update.

3 weeks ago
User Icon zbyszek commented & provided feedback 3 weeks ago

Yeah, it has a patch for that. I forgot to include it in notes though.

User Icon galileo provided feedback 3 weeks ago
karma
BZ#1941335 Starting raid-check.timer renders system unusable

This update has been submitted for stable by bodhi.

3 weeks ago
User Icon adamwill commented & provided feedback 3 weeks ago
karma

I revoked this because of the openQA results. It seems to have broken name resolution really badly in openQA. All the failures failed on DNS lookups.

User Icon mohanboddu commented & provided feedback 3 weeks ago
karma

Just to make sure, I am -ve karma it

User Icon galileo commented & provided feedback 3 weeks ago
karma

While I was able to test the base test cases, and the fix for BZ#1941335, there seems to be some odd networking issue with this new version for me: while I'm able to dig domains just fine, there are a lot of domains that I'm not able to actually ping.

Oddly I am able to ping google.com and bodhi.fedoraproject.org and visit them in a browser, but I'm not able to visit bugzilla.redhat.com, duckduckgo.com, opensource.com, bbc.co.uk.

I'm running Silverblue, and rolling back and forth between the version with this change applied and the one without it (which has systemd-246.10-1.fc33.x86_64), this version does seem to have that issue every time.

User Icon adamwill commented & provided feedback 3 weeks ago

Here's dig @127.0.0.53 output for a name that doesn't work (www.google.com), then one that does (fedoraproject.org):

; <<>> DiG 9.11.28-RedHat-9.11.28-1.fc33 <<>> @127.0.0.53 www.google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32195
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.google.com.            IN  A

;; Query time: 2 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Tue Mar 23 22:20:19 EDT 2021
;; MSG SIZE  rcvd: 32


; <<>> DiG 9.11.28-RedHat-9.11.28-1.fc33 <<>> @127.0.0.53 fedoraproject.org
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9540
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;fedoraproject.org.     IN  A

;; ANSWER SECTION:
fedoraproject.org.  60  IN  A   10.3.163.76
fedoraproject.org.  60  IN  A   10.3.163.75
fedoraproject.org.  60  IN  A   10.3.163.74

;; Query time: 5 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Tue Mar 23 22:20:23 EDT 2021
;; MSG SIZE  rcvd: 83

Here's resolvectl query output for the same two:

?[0;1;31mwww.google.com: resolve call failed: 'www.google.com' does not have any RR of the requested type?[0m

fedoraproject.org: 10.3.163.74                              -- link: ens4
                   10.3.163.75                              -- link: ens4
                   10.3.163.76                              -- link: ens4

-- Information acquired via protocol DNS in 3.3ms.
-- Data is authenticated: no
User Icon adamwill commented & provided feedback 3 weeks ago

Also, oddly, ping 1.1.1.1 works fine but dig @1.1.1.1 anyname fails with "connection timed out; no servers could be reached".

zbyszek edited this update.

New build(s):

  • systemd-246.13-1.fc33

Removed build(s):

  • systemd-246.12-1.fc33

Karma has been reset.

3 weeks ago

This update has been submitted for testing by zbyszek.

3 weeks ago
User Icon zbyszek commented & provided feedback 3 weeks ago

Apologies for the bad version. Please test again. The diff is the first five commits on https://github.com/systemd/systemd-stable/commits/v246-stable.

User Icon adamwill commented & provided feedback 3 weeks ago

@zbyszek given the recent general experiences, wouldn't it be sensible to disable autopush for this and future systemd updates, or at least set the threshold higher than +3?

The bad version here was extremely close to going stable and breaking networking for most of our user base, which would've done huge damage to both Fedora's and systemd's reputations.

User Icon galileo commented & provided feedback 3 weeks ago
karma

I've tested that the new build fixes BZ#1941335 and the base test cases pass, and I don't experience any networking issues with this one.

BZ#1941335 Starting raid-check.timer renders system unusable
User Icon jdieter commented & provided feedback 3 weeks ago

I can verify that this fixes BZ#1941335 in the Europe/Dublin time zone. I'm not leaving overall karma to keep this from getting autopushed.

BZ#1941335 Starting raid-check.timer renders system unusable
User Icon jdieter commented & provided feedback 3 weeks ago

I did notice that this also fixes the networking errors that I belatedly saw with the previous build.

User Icon imabug commented & provided feedback 3 weeks ago

Seems ok here. No odd networking issues seen.

zbyszek edited this update.

3 weeks ago
User Icon zbyszek commented & provided feedback 3 weeks ago

given the recent general experiences, wouldn't it be sensible to disable autopush for this and future systemd updates, or at least set the threshold higher than +3?

Yes, that's reasonable. I disabled autokarma now.

This update has been pushed to testing.

3 weeks ago
karma
BZ#1941335 Starting raid-check.timer renders system unusable

This update can be pushed to stable now if the maintainer wishes

3 weeks ago
User Icon bojan commented & provided feedback 3 weeks ago
karma

Works.

User Icon ersen provided feedback 3 weeks ago
karma

This update has been submitted for stable by zbyszek.

3 weeks ago

zbyszek edited this update.

3 weeks ago

This update has been pushed to stable.

3 weeks ago
User Icon atim provided feedback 3 weeks ago
karma

Please login to add feedback.

Metadata
Type
bugfix
Severity
medium
Karma
5
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
disabled
Stable by Time
14 days
Dates
submitted
3 weeks ago
in testing
3 weeks ago
in stable
3 weeks ago
modified
3 weeks ago
BZ#1930415 systemd-resolved coredump malloc_consolidate(): unaligned fastbin chunk detected
0
0
BZ#1933137 Warning: The unit file, source configuration file or drop-ins of httpd.service changed on disk. Run 'systemctl daemon-reload' to reload units
0
0
BZ#1935084 [abrt] systemd: greedy_realloc(): systemd-resolved killed by SIGABRT
0
0
BZ#1940459 [abrt] systemd: dns_packet_new(): systemd-resolved killed by SIGABRT
0
0
BZ#1941136 [abrt] systemd: sd_event_source_unref(): systemd-resolved killed by SIGSEGV
0
0
BZ#1941335 Starting raid-check.timer renders system unusable
0
1

Automated Test Results

Test Cases

0 5 Test Case base service manipulation
0 5 Test Case base services start
0 5 Test Case base shutdown/reboot