IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
The logs from TEST-69 still contain a lot of unnecessary shell
metacharacters, so to make the output more readable let's just set
TERM=dumb, instead of having to strip everything semi-manually. Also,
move the related --background= tweak to TEST-69, since it's relevant
only for that particular test.
Follow-up for 8d4bfd38ed941aa8003d7007145eccc01f52a5f6.
v255-only change: --background= is not supported in v255's sd-nspawn, so
that hunk is dropped
(cherry picked from commit 8d9cdb31f7cc41bb2252be70a2410030551aabde)
(cherry picked from commit 93c5ff05dcad782acdf87f4491b053c708a4eb45)
(cherry picked from commit 75d7263080c1c373666a334b873443118f047af2)
(cherry picked from commit 8db3e00695ea262cccf80c7d862e3060b230087d)
TEST-69 still occasionally times out in CI and appears to be stuck on
boot, so let's see if this helps the situation a bit.
(cherry picked from commit 515eb678a057099ee7e462ec83f71b199a368f8a)
(cherry picked from commit 67f620875294782cc4d8a029f97bb144979636bc)
(cherry picked from commit c77a839e9f9ad987c5f13b692d0c5de69bacfc8b)
(cherry picked from commit b26c0f44072c854951df6edcc9a3ef08323fa8f8)
So we capture the container's boot as well.
(cherry picked from commit 04f0c6752c10d152bc1884b2cc92b1f0b2df5de5)
(cherry picked from commit 8303b81fcdeb40cb39a810ce1c19d219b960f664)
(cherry picked from commit 0fd2f6cc93593322cd37195b140191368ea468b7)
(cherry picked from commit d401d011572d03b0b89b0fb1c17c4ea288fb86d6)
Given that the test involves screen(1), sending various control sequences to
resize/clear the screen, most of the logs sent from the python script were
nearly impossible to read or mixed with other messages sent to the console
hence making the debug harder when the test is run manually.
This patch introduces an option to redirect the pexpect IOs into a file (to be
used in $STATEDIR/TEST-69-SHUTDOWN/run-nspawn).
The pexpect logs are also enabled later so the boot logs are skipped since
those are already included in the journal.
(cherry picked from commit cf14d1144717967ebdd150cb21ed5dc00e832a80)
(cherry picked from commit dcea9bc57852b6d86651fed02445cc1c9a772164)
(cherry picked from commit 9fbbd59f9d077b05e336cb511c61b4ff8e3d214f)
(cherry picked from commit d3d3a89bdfecb6121e02ab94b3a0aa77f780d021)
sulogin from the latest util-linux started falling back to vt102 instead
of linux, which makes screen sad (because we install only the linux
terminfo into the test image) and expect trips over the unexpected
warning. Let's just explicitly set TERM=linux before invoking screen to
avoid this.
+ make -C TEST-69-SHUTDOWN setup run
...
INFO:test-shutdown:log in and start screen
root
root
Last login: Sun Mar 3 13:19:31 from 18.191.105.60
-bash-5.2# screen
screen
Cannot find terminfo entry for 'vt102'.
-bash-5.2# ERROR:test-shutdown:Timeout exceeded.
(cherry picked from commit 7a63c5e550d06659096d858dc14dda04726311fa)
(cherry picked from commit 275d720c9d1f2f7a7c563664a4704028a7f41e72)
(cherry picked from commit 58141ed83142b9b2cb2596052295d3b6acf3f212)
(cherry picked from commit ca08e02a4dbdb36f2a4ea6e5f7791820d6be77ca)
losetup in util-linux 2.40 started reporting lost loop devices [0] and
it has an unfortunate side-effect where it reports lost devices even in
containers, which then makes the loop device check "falsely" pass [1].
Let's just check for /dev/loop-control explicitly to "work around" this.
[0] a6ca0456cc
[1] https://github.com/util-linux/util-linux/issues/2824
(cherry picked from commit 0348b500efea840b711903124b30174f97b9ae68)
(cherry picked from commit 5ab85d7f5d7f1d64563a74d4ad90f8a2ffea82a9)
(cherry picked from commit c960f9a3257d14b4eba240603dc2c918e7132168)
(cherry picked from commit 686eb93e2d9800414e45e55fb78ca2e380583e70)
If we're looking for output on stderr, let's make sure it's not
littered with debug logs if SYSTEMD_LOG_LEVEL=debug.
(cherry picked from commit 88d4b97a24d532c1c34cbb99ac46e25f905d3884)
(cherry picked from commit db97c3a48c34fe09fc128dbeb5bdf45726b7e365)
(cherry picked from commit 5fc48f106f4c87d0440ba263c8bdf42c7857a202)
(cherry picked from commit 9fd3d0ee9693388adcb06f7d2c218a50595b27c1)
(cherry picked from commit 7e2bf4c5ee871f797c853d8b6474d4d379dad8e2)
(cherry picked from commit 6cd6d89469da4340aae8b51600df8027186c49c5)
(cherry picked from commit 03efc2b9295f71f6b6e7fc894787f9206119ec89)
(cherry picked from commit 3b21fe189459f5a59470ad626244707283569d6f)
So it's created automagically with proper attributes.
(cherry picked from commit 1b0cf0366814f3ec103d669ed151bc5b3a144563)
(cherry picked from commit 06cdc05ba2b1a38f1efd2f4a8a3a2e3a750d81fb)
(cherry picked from commit 92ab5322f86414a9125e831bb71cf2a75c6e8a8a)
(cherry picked from commit eb09475e7110dddcb87c9b4e549415874e72a745)
Othewise test images are missing the tmpfiles snippets used to create the very
basic files at boot, which can be useful when a test wants to reuse the OS tree
(is already running in) for spawning a new container in pristine state.
(cherry picked from commit 08abfd0b8c8e50e6be411ed9c909e6ccc893f223)
(cherry picked from commit f16f33d5e1e0e0f1ea469931d929a7647ae2d5b1)
(cherry picked from commit 1b690849b06b439eca60a64ea9ce1de2f35ea966)
(cherry picked from commit 858146d0cddf480a4522d6824f7bbe7c55606b60)
Needed since 87282a337d1ba7dc7d755f53b46c64b43718dcf7.
(cherry picked from commit 03b1e10fc8c3d85e98c38df642158076e97025fa)
(cherry picked from commit 048639c653c88905852ef3f4d710fde173916cfd)
(cherry picked from commit 52eaa1b7201cb92eca696959a7a995b5d898adb9)
(cherry picked from commit c74f29b0e1cc154accf93e4ae703885226d5105a)
(cherry picked from commit 76aa0d5db1a93d16a3455b97d0c3327eb9b31b40)
(cherry picked from commit e79860553990392e257a44449e1e5062e8c49651)
(cherry picked from commit f1e798f05eb7865af43fc043276c55e096f428cf)
(cherry picked from commit 9861f63240758bf77d78f671cae12099404c5d50)
The terminate() method sends SIGHUP but this signal is not handled by
systemd-nspawn hence the process just exits leaving the container scope around
breaking futher test executions.
This patch sends SIGTERM instead which is a defined API to request
sytemd-nspawn to stop and release the container's resources properly.
Follow-up for 8a7032cfb108c6daa395686320d9361c2195860a.
(cherry picked from commit 14265c3360b02191975654981715584227c0650e)
(cherry picked from commit 4b0f60de3b5b0d1ce5ab37dba56a9661e600b1f6)
(cherry picked from commit e6f68d43f2c2ee71d99de0eb3a510668d1dcac1c)
(cherry picked from commit 0297abd2a22707b40af84a3e58aa42e17a080554)
With newer versions of AppArmor, unprivileged user namespace creation
may be restricted by default, in which case user manager instances will
not be able to apply PrivateUsers=yes (or the settings which require it).
This can be tested with the kernel.apparmor_restrict_unprivileged_userns
sysctl.
(cherry picked from commit fec0d508a2f3d6bcf9be16a805dfc8facdfd9bb0)
(cherry picked from commit c07a21408b3d99c31dc79db1ac53d46479ccf71a)
(cherry picked from commit 46ecc7aedf0f975a27ebce18cecf64d5a1606f8d)
(cherry picked from commit e0d2c2eb48421569a7143a486bf011cbce5f29c0)
(cherry picked from commit dfdcc7c987bf9d66ecdb7e4a88e8abdb342df299)
(cherry picked from commit 0f78bd6367f2e406c51d2c39aaa455e4b2aec366)
(cherry picked from commit d5404dc2e668c622a8653d9fcae13b535431346c)
(cherry picked from commit 8d6787dc76cfe6cdc947cd4d1c12a5a315b94b9d)
The original way of appending to /etc/systemd/journald.conf doesn't work
anymore, since we no longer ship the default configs in /etc/.
(cherry picked from commit 1d556e9e2a01e538ecddd8a2d8fb843391caf410)
(cherry picked from commit cfe745d9850f2c199c97d789ca04e7f2e2d44d8d)
(cherry picked from commit e1f48e1aae2641b03718879a65ea6f5908b7be3c)
(cherry picked from commit 0f6057a7c444a2e19a1f5487e21a484b08963f61)
knot v3.2 and later does this by default. knot v3.1 still has the default set to
10, but it also introduced a warning that the default will be changed to 0 in
later versions, so it effectively complains about its own default, which then
fails the config check. Let's just set the value explicitly to zero to avoid
that.
~# knotc --version
knotc (Knot DNS), version 3.1.6
~# grep nsec3-iterations test/knot-data/knot.conf || echo nope
nope
~# knotc -c /build/test/knot-data/knot.conf conf-check
warning: config, policy[auto_rollover_nsec3].nsec3-iterations defaults to 10, since version 3.2 the default becomes 0
Configuration is valid
Follow-up to 0652cf8e7b.
(cherry picked from commit cb3244c0dcea80ad35e5bcaf7a07bd449ac65325)
(cherry picked from commit 3158eb9f8f3e64b2729107dc9ef06509b100150e)
(cherry picked from commit 478a284b639a80a377694d615573ddcd33ab3916)
(cherry picked from commit 0e251ccf9f8376fd740f4a754671da59f0b94879)
In Knot 3.2 the nsec3-iterations default was changed to 0 and Knot now
issues a warning if the value is > 0. Let's just use the default value,
since it's not something that's important for our tests.
(cherry picked from commit 0652cf8e7b08c97a52a0995eb8f0dc6bb20a4de0)
(cherry picked from commit 12ee58c2884e240cef4ff282acbfc67f84abb397)
(cherry picked from commit 2bdb09d77f46625d257399de651c13504248ee0a)
(cherry picked from commit 97de0acae70718b4ba5103e826ff144d0a016dae)
(cherry picked from commit 58bcbad86cc910e007fae3c66c3a5cfc17046801)
(cherry picked from commit 44420128b81582eed79eba7672605a11720668c4)
(cherry picked from commit 94726df1d20756dfa410e4b11a1c9918fbb68f62)
(cherry picked from commit 7989c46a173e8a935d4b73c521ee959ac50fb0d2)
udev before #30532 may kill the worker process together with a slow
program, and when running with sanitizers the resulting coredump might
be too big to fit into journal (or the space currently available for
journal):
[ 30.086194] systemd-journald[330]: Failed to write entry to /var/log/journal/e87de9ccbacf4b88924ff6d9ecaaa82d/system.journal (50 items, 68326399 bytes) despite vacuuming, ignoring: Argument list too long
This then makes the test fail, as it checks for the presence of the
coredump.
Since we don't really care about the coredump in this specific case (as
it is an expected one), let's just temporarily override the
testsuite-wide Storage=journal and store the coredumps externally.
This is a v255-stable-only patch, since after #30532 the test no longer
checks for coredumps.
(cherry picked from commit 27fc7a03218464ae9b3395120574b4c06e4c8322)
(cherry picked from commit 668880cc30b3147a069bf0dccd1d8bf2f41d55d2)
(cherry picked from commit 0a18a84f9a311f0403a799ddee0f7c56460c0374)
Arch finally made dbus-broker the default dbus daemon [0], but unlike
Fedora they don't use Alias=dbus.service to make the dbus.symlink under
/etc, instead they create the symlink manually under /usr/lib, so let's
account for that.
[0] b24d15795a
(cherry picked from commit ec6c7bac5c92b26fc17ad165d2defc85da324391)
(cherry picked from commit 7b80fc2587d542b65e0ebc5cece9fca7cf83432a)
(cherry picked from commit 3129beaf0ccb9f9f34737f54ca50e1d0d873bde3)
(cherry picked from commit ec2d0d691e4a3f006fcac50132e88aefa6262d0e)
Follow-up for 22e31655f3f9f54d932d4f48b92b36698e701729.
(cherry picked from commit 0f236e8cd6309cdc392d9e62bc545dcd497a9c50)
(cherry picked from commit 374a0f678817c1ab054587def008e65806f9c437)
(cherry picked from commit 74978b25bc686509c4f89ef6fa0e15453ad4362b)
(cherry picked from commit 1f392470cbbe249d5e706be59c8be799e1917d99)
Installing mdadm without kernel modules is mostly meaningless.
(cherry picked from commit 4ed943e97bb7ef4227837f7a6f607cd313cae70b)
(cherry picked from commit 570766c8b612c734fed642b74218bf1be142ebb1)
(cherry picked from commit 17f7d8d8003fc517d4c49ab0308fe97127a04465)
(cherry picked from commit 5938ba1251783d9379eb1605361cba58c351c344)
(cherry picked from commit 5b4fa6f13cf860afa53c71b52e4ceca25f8f13a5)
(cherry picked from commit a40677469af941118a2d86a386cc7a7ad8ff17ca)
(cherry picked from commit a5ebe751c78cf7fc8af5060b981555adaa5ff34d)
(cherry picked from commit b17e7fca359a04f5d589944e507bda70dd147339)
(Hopefully) a temporary workaround for #30573 where starting a user
session when PID 1 is rate limited stalls even after it leaves the rate
limited state:
[ 11.658201] H systemd[1]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=UnitRemoved cookie=4208 reply_cookie=0 signature=so error-name=n/a error-mes>
[ 11.658233] H systemd[1]: Event source 0x559babdd8bb0 (mount-monitor-dispatch) left rate limit state.
[ 101.562697] H busctl[784]: Failed to get credentials: Transport endpoint is not connected
[ 101.563480] H systemd[1]: systemd-journald.service: Got notification message from PID 300 (WATCHDOG=1)
[ 101.563725] H testsuite-74.sh[784]: BusAddress=unixexec:path=systemd-run,argv1=-M.host,argv2=-PGq,argv3=--wait,argv4=-pUser%3dtestuser,argv5=-pPAMName%3dlogin,argv6=systemd-stdio-bridge,argv7=-punix:path%3d%24%7bXDG_RUNTIME_DIR%7d/bus
[ 101.564136] H systemd[1]: Successfully forked off '(sd-expire)' as PID 787.
[ 101.564754] H systemd[1]: Successfully forked off '(sd-expire)' as PID 788.
[ 101.564831] H testsuite-74.sh[381]: + echo 'Subtest /usr/lib/systemd/tests/testdata/units/testsuite-74.busctl.sh failed'
The issue appeared after ee07fff03b which does a bunch of mounts/umounts
that get PID 1 into a rate limited state, and is frequent enough to be
annoying, so let's temporarily bump the rate limit to alleviate that.
(cherry picked from commit c707e346fbf4d8dba262f1af4fd25e2cb6b109b6)
(cherry picked from commit 4d60fb706918f32f3097687929debeb10a34bee9)
(cherry picked from commit 7215018ffcba7a783cbc19249c360bdf91f9aa8b)
(cherry picked from commit 202ae4d60de9c627d502c4a326956b81942021ed)
(cherry picked from commit 5e46ca9890bb463644f91426678570edc2891163)
(cherry picked from commit fbe064cc74a7a25060d4311b5f3a616b02f3e9c9)
(cherry picked from commit d948b169ad6285adb2f5b32bbaccb013d4223f87)
(cherry picked from commit 29c975fca07b1e73908ca4fd07205431c4ff1696)
And derivates.
Replaces: #30458
(cherry picked from commit f9ba9d3eb7c350f31132ccd9ed1ee3c0c693f5c5)
(cherry picked from commit b1dba6bcaae70849394f34be8850f2e5e2559633)
(cherry picked from commit dc7bc3d34e1cf87e6cf93ba901bd21af24b1ae71)
(cherry picked from commit 850d3d70bcab501fcc2a5df033435c0c0dd6664d)
It's pulled in by one of the udev rules (63-md-raid-arrays.rules) and it
fails every time, because there's no valid email address in
/etc/mdadm.conf:
[ 5.778153] testsuite-64.sh[403]: mdadm: array /dev/md/mdmirror started.
[ 5.819137] kernel: md/raid1:md127: not clean -- starting background reconstruction
[ 5.819141] kernel: md/raid1:md127: active with 2 out of 2 mirrors
[ 5.819159] kernel: md127: detected capacity change from 0 to 129024
[ 5.821950] kernel: md: resync of RAID array md127
...
[ 5.887192] mdadm[424]: mdadm: No mail address or alert command - not monitoring.
[ 5.890772] systemd[1]: Starting mdmonitor.service...
[ 5.891718] systemd[1]: Started mdmonitor.service.
[ 5.892570] systemd[1]: mdmonitor.service: Main process exited, code=exited, status=1/FAILURE
[ 5.892618] systemd[1]: mdmonitor.service: Failed with result 'exit-code'.
And as we (re)assemble the MD devices multiple times, this gets quite
noisy, especially since we later start hitting the service start rate
limit.
Fedora has the mdmonitor.service patched, so it won't start without
/etc/mdadm.conf being present, but Arch uses the upstream unit which
doesn't have such guard.
Let's just mask the service completely, which replaces all that noise
with one warning:
[ 6.553583] testsuite-64.sh[294]: + udevadm wait --settle ...
[ 6.580700] systemd[1]: sys-devices-virtual-block-md127.device: Failed to enqueue SYSTEMD_WANTS job, ignoring: Unit mdmonitor.service is masked.
(cherry picked from commit 22e31655f3f9f54d932d4f48b92b36698e701729)
(cherry picked from commit ef548643668491d4a8371186d2575eb4e4499b4e)
(cherry picked from commit d2e8e28637d56e891c1882d8edda2985935a1bdd)
(cherry picked from commit ad7fbe4ec4325d3526f681b2d408b81fd19cdc0b)
Prompted by https://github.com/systemd/systemd/issues/30140#issuecomment-1837973580.
(cherry picked from commit 470a329d9849d108e28f72d00dd130d130cebb01)
(cherry picked from commit 16f193d51861db4befd6228b773cf7a86c03339a)
(cherry picked from commit 6f584de56e86170c8e4bd426a4b4829b8343f1c0)
(cherry picked from commit 1cdd0c2804c9e991d5d083a32da36cc69a0b78dc)
When [Link] MTU= is specified in a .network file, we have no idea about
that what kind of interface will be configured with the .network file.
The maximum and minimum MTU size depend on the kind of interface.
So, we should not filter MTU eagerly in the parser.
Closes#30140.
(cherry picked from commit a0460dfed617a73f7dbf36a6eb7e474e887ae780)
(cherry picked from commit 2fa0b50566829a2e72b61d9f453a5314192c19ab)
(cherry picked from commit cf8969ee3270413a8340cc824a9faa134227420c)
(cherry picked from commit 6ce4af1a43c4c26a2c1ff0d2a8a768c300fb69ce)
(cherry picked from commit b86f60bfb3340a9fa27cb6f127fba7c827481b50)
(cherry picked from commit c2cc0ca17923034130a0dc1118b20f5a96db8d95)
(cherry picked from commit 7c894f8281818374306e912eaa7b975ca59c22ed)
Follow-up for 923599523c10d8897551e081e6b00cd8002309c3.
(cherry picked from commit 816c269e55220924c4f8b712afd976e83ec0359e)
(cherry picked from commit 6db250e4aee95a6c79f2724092e79b2162d70540)
(cherry picked from commit eb808e153462c67452dc25aba7466bfdce2f4f83)
Otherwise, parsing may unexpectedly succeeds but fail to run writing
.network files with permission error.
Follow-up for 6bc5de53e8410fdec817300185b7ad72cd7775dd.
(cherry picked from commit 9e6d58796158d0418e0e4ba641db5b00aacee695)
(cherry picked from commit 2bc39320fc05ff133620e30be134a1d3f4383be7)
(cherry picked from commit a1295dd327d259c21b19e3d83a420cd1fb4c5765)
Only for ip= stuff, for now.
(cherry picked from commit 6bc5de53e8410fdec817300185b7ad72cd7775dd)
(cherry picked from commit 75b2890c5d2ac1536459e7470f59369ad3e50a62)
(cherry picked from commit 4763b5d3fbd9b7ee70a6fba724de0f3beee84122)
(cherry picked from commit 9d51ab78300364c71a0e1f138e1d2cbc65771b93)
(cherry picked from commit d644d2f562051a86f7a8b2a8e382cee315463bd9)
(cherry picked from commit 948239494414da16147162871bac109b197c35e7)
(cherry picked from commit e60c4b4512c1885fdae7c00550516ef46bf08546)
On Fedora systemd recently moved all of its configuration files to
/usr/lib/ [0], so make sure we account for this case as well.
[ 42.450325] testsuite-17.sh[800]: + mkdir -p /run/udev/rules.d
[ 42.466504] testsuite-17.sh[800]: + cp -f /etc/udev/udev.conf /etc/udev/udev.conf.bckp
[ 42.503348] testsuite-17.sh[802]: cp: cannot stat '/etc/udev/udev.conf': No such file or directory
[0] 29eb35530b
(cherry picked from commit e23fc070e287397d2f047028f953986356badf2f)
(cherry picked from commit 49cc12975c761701e2dc0dc84ee1928b38f98c54)
(cherry picked from commit a22613dd2a13d4f66eef4f132a9c654b87e9b61f)
(cherry picked from commit 82cbbce8e7074f80222477982fb5267c072ea9a0)
Since we restart systemd-udevd here a couple of times, we might hit the
rate limit in later tests:
[ 26.028355] testsuite-17.sh[2074]: + udevadm control -e
[ 26.028355] testsuite-17.sh[2074]: + udevadm control -l emerg
[ 26.126160] systemd[1]: systemd-udevd.service: Start request repeated too quickly.
[ 26.126213] systemd[1]: systemd-udevd.service: Failed with result 'start-limit-hit'.
[ 26.140310] systemd[1]: Failed to start systemd-udevd.service.
[ 26.140897] systemd[1]: systemd-udevd-control.socket: Failed with result 'service-start-limit-hit'.
[ 26.141286] systemd[1]: systemd-udevd-kernel.socket: Failed with result 'service-start-limit-hit'.
[ 26.142225] testsuite-17.sh[2074]: + udevadm control -l alert
[ 26.149206] udevadm[2088]: Failed to send request to set log level: No such file or directory
Follow-up to: 6ef512c0bb
(cherry picked from commit ad23ff13deb4e057d435adb941e58cd552beac02)
(cherry picked from commit 7d029ce868c42f668e692d7a3bf9e22c778840ab)
(cherry picked from commit 8e43acfd06b917a3f056761f2a413d9584b4769e)
(cherry picked from commit 0984feb087c55558094340d6c8fa8d9010059cdd)
The previous patch 466266c does not make sense indeed, that is to say, if the SYSTEMD_READY is not recorded in the database, the GOTO="systemd_end" will not be applied.
The IMPORT{db} is actually a matching token, it returns false when there is no SYSTEMD_READY recorded in the database.
The previous patch 466266c tended to inherit the state of SYSTEMD_READY from the database and skip to the end of current rule file. But when the database does not contain SYSTEMD_READY, e.g., the dm-* is not set db_persistent during initrd and the database will be cleared after switching root, the following rules will still be applied not as expected.
(cherry picked from commit c1a2ada89708d6aeeada496712cb24a4a58e75cc)
(cherry picked from commit 7237dfc88257656540c1dc237bb03258fe7886ac)
(cherry picked from commit 85ee15a81300f6ecf41b8d0f89672cc338a9b098)
It's been there since the test was introduced and I'm not really sure
what was the original intention behind it, but it makes systemd sad:
[ 4.909056] systemd[1]: /usr/lib/systemd/tests/testdata/units/testsuite-44.service:13: Unknown key name 'LogTarget' in section 'Service', ignoring.
(cherry picked from commit d1ac1aa5ca8981e00ac97050c257ff5ee6665770)
(cherry picked from commit 87ac9e3a733a6940a39b161767e34cba9546fa34)
(cherry picked from commit 9560c621fa0e06835ae8f0c6f33bfe986cebe82c)
Prompted by #30029.
(cherry picked from commit fbf946ce22ef778bf6bf04c117b75c9c63ac7e66)
(cherry picked from commit f0e8b27466cfda5886c8316866deecd36b5143ab)
(cherry picked from commit 60097b792d198d3cd2c2ad7ec44c7ba0cf0d835a)
(cherry picked from commit ba8eda568c760cc1b4eb9edcfd1b29818619ce70)
(cherry picked from commit 2d6ee8dba28c8215da6da41738ca20a536d148c4)
(cherry picked from commit c223ca51ac99b682be2ed87ed5fc84c95ecf2161)
41e4ce06fe shortened existing sleeps, which resulted in the check being
sometimes done before the property had a chance to update. Let's do what
what we do with the rest of the checks and retry it a couple of times.
Resolves: #29923
(cherry picked from commit 4e55082f74e7be0669912862a95ed669197ffdb4)
(cherry picked from commit 35724455b225c61890061c24551469064fd0ba65)
(cherry picked from commit c77b806c73495943c9818b4f3c6cdd687e2ac9ee)
(cherry picked from commit 4f7a629e6c11fb2f060f18a62d073410ffa5a0ca)
(cherry picked from commit f58b5ce7dc8232f2305b9c8ce2e73b626a9d0dd8)
(cherry picked from commit cc09085ac30cec40a6863a018471fad65973f6bd)
When running with --build-dir= we need to copy over udev rules from
$BUILD_DIR/udev.d/ and $SOURCE_TREE/udev.d/ to make stuff work as
expected.
(cherry picked from commit 33b0e0c09a438fd565b6c4d059bd14cc9651c40b)
(cherry picked from commit 359fed84eea82238a7ccdf5eb76d635afefdcaa4)
(cherry picked from commit aefe546793830371e8bac3f0e12891862df7b89d)
The systemd-tmpfiles binary will report a fatal error if /tmp is not owned
either by root, or by the current user:
Detected unsafe path transition /tmp (owned by nobody) →
/tmp/test-systemd-tmpfiles.a8qc6n18 (owned by berrange)
during canonicalization of
tmp/test-systemd-tmpfiles.a8qc6n18/test-content.7chd7rdi
When doing development inside a 'toolbox' container (which is required
on a Fedora SilverBlue distro), /tmp is owned by 'nobody', because it
has been passed through from the host and host UID 0 gets mapped to
UID 65536 by usernamespaces. This triggers the unsafe path transition
error message.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
(cherry picked from commit 8473ece90e53040931c880bcbff623f1a5c037cd)
(cherry picked from commit c7482035e3cefbfae2a1cc4b4529ebb705d67531)
(cherry picked from commit 95cbb9e857dc9dec07041d9d85a09928d44107c1)
Currently needed by test-dhcp-server unit test, af_packet is not built-in on
openSUSE distributions.
(cherry picked from commit a1af99df8e29ffb55b0c698eeda2c9bf795fc0e1)
(cherry picked from commit db2193609e554732c0288ccf27d5e58083f9219c)
(cherry picked from commit 0a48f8ac7b0e4cf288b9f2aa05257424d2926288)
'[[ not found'
(cherry picked from commit c7986bc9b64e095399c3e380441b4de26d1276a1)
(cherry picked from commit 52d4f5ec539c746c9a61a3bb4607f965a36675fe)
(cherry picked from commit 5b900490f97f47f8b23803778bc74b6047916638)
