[Bug 1935786] Re: `systemctl list-units --type=service` does not list user services
you need to use the --user parameter when you want to list user services, e.g. $ systemctl list-units --user --type=service by default, only system services will be listed. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935786 Title: `systemctl list-units --type=service` does not list user services To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1935786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923145] Re: Actually support Ubuntu
ubuntu@lp1923145-g:~$ dpkg -l|grep mkosi ii mkosi 5-1 all create legacy-free OS images ubuntu@lp1923145-g:~$ sudo mkosi ... E: No such script: /usr/share/debootstrap/scripts/"20.10" ... ubuntu@lp1923145-g:~$ dpkg -l|grep mkosi ii mkosi 5-1ubuntu0.20.10.1 all create legacy-free OS images ubuntu@lp1923145-g:~$ sudo mkosi ... ‣ Installing Ubuntu complete. ... ubuntu@lp1923145-f:~$ dpkg -l|grep mkosi ii mkosi 5-1 all create legacy-free OS images ubuntu@lp1923145-f:~$ sudo mkosi ... E: No such script: /usr/share/debootstrap/scripts/"20.04" ... ubuntu@lp1923145-f:~$ dpkg -l|grep mkosi ii mkosi 5-1ubuntu0.20.04.1all create legacy-free OS images ubuntu@lp1923145-f:~$ sudo mkosi ... ‣ Installing Ubuntu complete. ... ** Tags removed: verification-needed verification-needed-focal verification-needed-groovy ** Tags added: verification-done verification-done-focal 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/1923145 Title: Actually support Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mkosi/+bug/1923145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926624] Re: failed to start commit a transient machine-id on disk
how did you install the system onto the usb stick? that service shouldn't run during normal boots. ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926624 Title: failed to start commit a transient machine-id on disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926254] Re: x509 Certificate verification fails when basicConstraints=CA:FALSE, pathlen:0 on self-signed leaf certs
added ubuntu-security to the bug, just for quick review to make sure they don't object to the patch I can sponsor this to -updates if there's no objection -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926254 Title: x509 Certificate verification fails when basicConstraints=CA:FALSE,pathlen:0 on self-signed leaf certs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1926254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849098] Re: ovs agent is stuck with OVSFWTagNotFound when dealing with unbound port
** Description changed:
[Impact]
- somehow port is unbounded, then neutron-openvswitch-agent raise
+ somehow port is unbounded, then neutron-openvswitch-agent raise
OVSFWTagNotFound, then creating new instance will be failed.
[Test Plan]
1. deploy bionic openstack env
2. launch one instance
3. modify neutron-openvswitch-agent code inside nova-compute
- https://pastebin.ubuntu.com/p/nBRKkXmjx8/
4. restart neutron-openvswitch-agent
5. check if there are a lot of cannot get tag for port ..
6. launch another instance.
7. It fails after vif_plugging_timeout, with "virtual interface creation
failed"
[Where problems could occur]
- You need to restart service. and as patch, Basically it will be ok as it adds
only exceptions. but getting or creating vif port part can have issue.
+ issues could occur getting or creating vif port
[Others]
Original description.
neutron-openvswitch-agent meets unbound port:
2019-10-17 11:32:21.868 135 WARNING
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [req-
aae68b42-a99f-4bb3-bcf6-a6d3c4ca9e31 - - - - -] Device
ef34215f-e099-4fd0-935f-c9a42951d166 not defined on plugin or binding
failed
Later when applying firewall rules:
2019-10-17 11:32:21.901 135 INFO neutron.agent.securitygroups_rpc
[req-aae68b42-a99f-4bb3-bcf6-a6d3c4ca9e31 - - - - -] Preparing filters for
devices {'ef34215f-e099-4fd0-935f-c9a42951d166',
'e9c97cf0-1a5e-4d77-b57b-0ba474d12e29', 'fff1bb24-6423-4486-87c4-1fe17c552cca',
'2e20f9ee-bcb5-445c-b31f-d70d276d45c9', '03a60047-cb07-42a4-8b49-619d5982a9bd',
'a452cea2-deaf-4411-bbae-ce83870cbad4', '79b03e5c-9be0-4808-9784-cb4878c3dbd5',
'9b971e75-3c1b-463d-88cf-3f298105fa6e'}
2019-10-17 11:32:21.906 135 ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent
[req-aae68b42-a99f-4bb3-bcf6-a6d3c4ca9e31 - - - - -] Error while processing VIF
ports: neutron.agent.linux.openvswitch_firewall.exceptions.OVSFWTagNotFound:
Cannot get tag for port o-hm0 from its other_config: {}
2019-10-17 11:32:21.906 135 ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent Traceback (most
recent call last):
2019-10-17 11:32:21.906 135 ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent File
"/var/lib/openstack/lib/python3.6/site-packages/neutron/agent/linux/openvswitch_firewall/firewall.py",
line 530, in get_or_create_ofport
2019-10-17 11:32:21.906 135 ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent of_port =
self.sg_port_map.ports[port_id]
2019-10-17 11:32:21.906 135 ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent KeyError:
'ef34215f-e099-4fd0-935f-c9a42951d166'
2019-10-17 11:32:21.906 135 ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent
2019-10-17 11:32:21.906 135 ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent During handling
of the above exception, another exception occurred:
2019-10-17 11:32:21.906 135 ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent
2019-10-17 11:32:21.906 135 ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent Traceback (most
recent call last):
2019-10-17 11:32:21.906 135 ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent File
"/var/lib/openstack/lib/python3.6/site-packages/neutron/agent/linux/openvswitch_firewall/firewall.py",
line 81, in get_tag_from_other_config
2019-10-17 11:32:21.906 135 ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent return
int(other_config['tag'])
2019-10-17 11:32:21.906 135 ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent KeyError: 'tag'
2019-10-17 11:32:21.906 135 ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent
2019-10-17 11:32:21.906 135 ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent During handling
of the above exception, another exception occurred:
2019-10-17 11:32:21.906 135 ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent
2019-10-17 11:32:21.906 135 ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent Traceback (most
recent call last):
2019-10-17 11:32:21.906 135 ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent File
"/var/lib/openstack/lib/python3.6/site-packages/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py",
line 2280, in rpc_loop
2019-10-17 11:32:21.906 135 ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent port_info,
provisioning_needed)
2019-10-17 11:32:21.906 135 ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent File
"/var/lib/openstack/lib/python3.6/site-packages/osprofiler/profiler.py", line
160, in wrapper
2019-10-17 11:32:21.906 135 ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent result =
f(*args, **kwargs)
2019-10-17 11:
[Bug 1894843] Re: [dvr_snat] Router update deletes rfp interface from qrouter even when VM port is present on this host
** Description changed: [Impact] When neutron schedules snat namespaces it sometimes deletes the rfp interface from qrouter namespaces which breaks external network (fip) connectivity. The fix prevents this from happening. [Test Case] * deploy Openstack (Ussuri or above) with dvr_snat enabled in compute hosts. * ensure min. 2 compute hosts * create one ext network and one private network * add private subnet to router and ext as gateway * check which compute has the snat ns (ip netns| grep snat) * create a vm on each compute host * check that qrouter ns on both computes has rfp interface * ip netns| grep qrouter; ip netns exec ip a s| grep rfp * disable and re-enable router * openstack router set --disable ; openstack router set --enable * check again * ip netns| grep qrouter; ip netns exec ip a s| grep rfp [Where problems could occur] - This patch is in fact restoring expected behaviour and is not expected to - introduce any new regressions. + no regression is expected, but if one occurs it would likely result in breakage with external network connectivity - Hello, In the case of dvr_snat l3 agents are deployed on hypervisors there can be race condition. The agent creates snat namespaces on each scheduled host and removes them at second step. At this second step agent removes the rfp interface from qrouter even when there is VM with floating IP on the host. When VM is deployed at the time of second step we can lost external access to VMs floating IP. The issue can be reproduced by hand: 1. Create tenant network and router with external gateway 2. Create VM with floating ip 3. Ensure that VM on the hypervisor without snat-* namespace 4. Set the router to disabled state (openstack router set --disable ) 5. Set the router to enabled state (openstack router set --enabled ) 6. The external access to VMs FIP have lost because L3 agent creates the qrouter namespace without rfp interface. Environment: 1. Neutron with ML2 OVS plugin. 2. L3 agents in dvr_snat mode on each hypervisor 3. openstack-neutron-common-15.1.1-0.2020061910.7d97420.el8ost.noarch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894843 Title: [dvr_snat] Router update deletes rfp interface from qrouter even when VM port is present on this host To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1894843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850779] Re: [L3] snat-ns will be initialized twice for DVR+HA routers during agent restart
** Description changed: If the DVR+HA router has external gateway, the snat-namespace will be initialized twice during agent restart. And that initialized function will run many [1][2] external resource processing actions which will definitely increase the starting time of agent. https://github.com/openstack/neutron/blob/master/neutron/agent/l3/dvr_snat_ns.py#L31-L39 https://github.com/openstack/neutron/blob/master/neutron/agent/l3/namespaces.py#L91-L108 SRU: [Impact] Longer l3-agent initialization time during restarts due to creation of snat namespace and setting corresponding sysctl twice. With this fix, the initialization phase is triggered only once. [Test Case] * deploy Openstack on bionic queens (with neutron dvr l3 ha settings and debug mode on for neutron ) and create a router (If stsstack-bundles are used, here are the commands ./generate-bundle.sh -s bionic -n bionicqueens --dvr-snat-l3ha --create-model --run ./configure # Configure creates a router with external gateway attached ) * Restart neutron-l3-agent on one of the node systemctl restart neutron-l3-agent.service * Check /var/log/neutron/neutron-l3-agent.log and wait for the logs to be settled with all initialization steps - During initialization steps, following sysctl's are configured [1] [2]. + During initialization steps, following sysctl's are configured [1] [2]. Verify if the debug logs show sysctl execution statements are displayed twice after restart for snat namespace. - (If the fix is applied they should be displayed only once) - - grep -inr snat- /var/log/neutron/neutron-l3-agent.log | grep sysctl + (If the fix is applied they should be displayed only once) + + grep -inr snat- /var/log/neutron/neutron-l3-agent.log | + grep sysctl Example log: 2718:2021-04-14 05:17:20.114 10868 DEBUG neutron.agent.linux.utils [-] Running command: ['sudo', 'neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'exec', 'snat-f64dded1-ef73-47b4-bcee-bb25840e9a02', 'sysctl', '-w', 'net.ipv4.ip_forward=1'] create_process /usr/lib/python2.7/dist-packages/neutron/agent/linux/utils.py:87 [Where problems could occur] - This patch reduces the l3 agent initialization time during restart and is not expected to introduce new regressions. + no regression is expected, but if one occurs it would likely result in longer init time and/or failure to correctly init the snat-namespace [1] https://github.com/openstack/neutron/blob/master/neutron/agent/l3/dvr_snat_ns.py#L31-L39 [2] https://github.com/openstack/neutron/blob/master/neutron/agent/l3/namespaces.py#L91-L108 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850779 Title: [L3] snat-ns will be initialized twice for DVR+HA routers during agent restart To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1850779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927161] [NEW] dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one
Public bug reported: [impact] openssl doesn't build source properly because of a badly-constructed patch [test case] $ pull-lp-source openssl groovy ... $ cd openssl-1.1.1f/ $ quilt pop -a ... $ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1f-1ubuntu4.3 dpkg-buildpackage: info: source distribution groovy-security dpkg-buildpackage: info: source changed by Marc Deslauriers dpkg-source --before-build . dpkg-source: warning: can't parse dependency perl:native dpkg-source: error: diff 'openssl-1.1.1f/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned exit status 25 [regression potential] any regression would likely cause a failed build or would affect the functionality that patch pr12272 was added for, which is adding support for Intel CET [scope] this is needed only for g and later this is caused by the bad patch 'pr12272.patch' which is only included in g/h/i, so this does not apply to f or earlier [other info] note that if the patches are applied, this bug is bypassed; i.e. if 'quilt pop -a' is removed from the test case above, the bug doesn't reproduce. this is only a problem when the patches aren't already applied and dpkg-buildpackage needs to call dpkg-source to apply the patches. ** Affects: openssl (Ubuntu) Importance: Low Status: New ** Affects: openssl (Ubuntu Groovy) Importance: Low Status: New ** Affects: openssl (Ubuntu Hirsute) Importance: Low Status: New ** Affects: openssl (Ubuntu Impish) Importance: Low Status: New ** Description changed: [impact] openssl doesn't build properly because of a badly-constructed patch [test case] $ pull-lp-source openssl groovy ... $ cd openssl-1.1.1f/ $ quilt pop -a ... $ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1f-1ubuntu4.3 dpkg-buildpackage: info: source distribution groovy-security dpkg-buildpackage: info: source changed by Marc Deslauriers - dpkg-source --before-build . + dpkg-source --before-build . dpkg-source: warning: can't parse dependency perl:native dpkg-source: error: diff 'openssl-1.1.1f/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned exit status 25 [regression potential] any regression would likely cause a failed build or would affect the functionality that patch pr12272 was added for, which is adding support for Intel CET [scope] this is needed only for g and later this is caused by the bad patch 'pr12272.patch' which is only included in g/h/i, so this does not apply to f or earlier + + [other info] + + note that if the patches are applied, this bug is bypassed; i.e. if + 'quilt pop -a' is removed from the test case above, the bug doesn't + reproduce. this is only a problem when the patches aren't already + applied and dpkg-buildpackage needs to call dpkg-source to apply the + patches. ** Also affects: openssl (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: openssl (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: openssl (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: openssl (Ubuntu Groovy) Importance: Undecided => Low ** Changed in: openssl (Ubuntu Hirsute) Importance: Undecided => Low ** Changed in: openssl (Ubuntu Impish) Importance: Undecided => Low ** Description changed: [impact] - openssl doesn't build properly because of a badly-constructed patch + openssl doesn't build source properly because of a badly-constructed + patch [test case] $ pull-lp-source openssl groovy ... $ cd openssl-1.1.1f/ $ quilt pop -a ... $ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1f-1ubuntu4.3 dpkg-buildpackage: info: source distribution groovy-security dpkg-buildpackage: info: source changed by Marc Deslauriers dpkg-source --before-build . dpkg-source: warning: can't parse dependency perl:native dpkg-source: error: diff 'openssl-1.1.1f/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned exit status 25 [regression potential] any regression would likely cause a failed build or would affect the functionality that patch pr12272 was added for, which is adding support for Intel CET [scope] this is needed only for g and later this is caused by the bad patch 'pr12272.p
[Bug 1927161] Re: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one
** Tags added: block-proposed-hirsute block-proposed-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927161 Title: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927161] Re: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one
** Tags removed: block-proposed-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927161 Title: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926254] Re: x509 Certificate verification fails when basicConstraints=CA:FALSE, pathlen:0 on self-signed leaf certs
uploaded to f/g, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926254 Title: x509 Certificate verification fails when basicConstraints=CA:FALSE,pathlen:0 on self-signed leaf certs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1926254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927161] Re: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one
uploaded to g/h/i, thanks! I also added block-proposed-hirsute tag, since it's a build-time-only problem and doesn't need to get moved to hirsute-updates until (if) another openssl patch comes along. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927161 Title: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923115] Re: Networkd vs udev nic renaming race condition
re: autopkgtests, please note that while the pending-sru page and update_excuses page both show the systemd/i386 test as 'failing', it actually passed: https://autopkgtest.ubuntu.com/packages/s/systemd/bionic/i386 the update_excuses and pending-sru pages appear to be stuck/broken, possibly due to the recent autopkgtest results url change the linux-hwe-5.4/i386 autopkgtest still is failing, but it always fails for everything, so it can be ignored -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923115 Title: Networkd vs udev nic renaming race condition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927004] Re: [MIR] fence-agents
[Summary] There are only some minor concerns listed below, which shouldn't block this, so this is ACK from MIR team. Please see Notes and TODOs below. This does need a security review (though I considered skipping it, but want to err on the side of safety), so I'll assign ubuntu-security List of specific binary packages to be promoted to main: - fence-agents-common - fence-agents-supported Just for clarification, list of binary packages to remain in universe: - fence-agents Notes: 1) The Ubuntu Server team isn't yet subscribed. This is allowed per the new MIR process, but please remember to subscribe before the package is promoted to main. 2) The bug description states CVE-2019-10153 was already fixed, but that doesn't appear correct per the Ubuntu CVE page: https://ubuntu.com/security/CVE-2019-10153 I don't think this medium CVE needs to block MIR, however. 3) I'm concerned about the split of the binary packages which leaves one package in universe; I have no problem with leaving a package in universe, but I'm concerned about the naming. After this MIR, the packages 'fence-agents-supported' and 'fence-agents-common' will be in main and fully supported, but the generically-named binary package 'fence-agents' will remain in universe. I feel like this is going to lead to confusion by users of fence agents in the unsupported 'fence-agents' binary package. Required TODOs: 1) Ubuntu Server Team must subscribe to the package before it's promoted to main. Recommended TODOs: 1) It might be adding more obviousness than is really needed, but I suggest renaming the binary package 'fence-agents' to 'fence-agents-unsupported' to make it clear (to users) that the agents in the package aren't supported. [Duplication] There is no other package in main providing the same functionality. [Dependencies] OK: - no other Dependencies to MIR due to this - no -dev/-debug/-doc packages that need exclusion [Embedded sources and static linking] OK: - no embedded source present - no static linking [Security] OK: - history of CVEs does not look concerning - does not run a daemon as root - does not use webkit1,2 - does not use lib*v8 directly - does not open a port - does not parse data formats - does not process arbitrary web content - does not use centralized online accounts - does not integrate arbitrary javascript into the desktop - does not deal with system authentication (eg, pam), etc) [Common blockers] OK: - does not FTBFS currently - does have a test suite that runs at build time - test suite fails will fail the build upon error. - does have a test suite that runs as autopkgtest - no translation present, but none needed for this case - not a python/go package, no extra constraints to consider in that regard Problems: - The package needs Ubuntu Server team to subscribe [Packaging red flags] OK: - Ubuntu does carry a delta, but it is reasonable and maintenance under control - symbols tracking not applicable for this kind of code. - d/watch is present and looks ok - Upstream update history is good - Debian/Ubuntu update history is good - the (almost) current release is packaged - promoting this does not seem to cause issues for MOTUs that so far maintained the package - no massive Lintian warnings - d/rules is rather clean - Does not have Built-Using - not go package - is not on the lto-disabled list [Upstream red flags] OK: - no incautious use of malloc/sprintf (as far as I can check it) - no use of user nobody - no use of setuid - no important open bugs (crashers, etc) in Debian or Ubuntu or Upstream - no dependency on webkit, qtwebkit, seed or libgoa-* - not part of the UI for extra checks Problems: - warning during the build, but appears harmless: "make[5]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule." - use of sudo, though usage appears reasonable and is optional ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-10153 ** Changed in: fence-agents (Ubuntu) Assignee: Dan Streetman (ddstreet) => Ubuntu Security Team (ubuntu-security) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927004 Title: [MIR] fence-agents To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1927004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927004] Re: [MIR] fence-agents
And of course please do update this bug description with the adjusted binary package names to promote to main, once the packaging is updated with the new names. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927004 Title: [MIR] fence-agents To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1927004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927004] Re: [MIR] fence-agents
Lucas, thanks! The naming sounds good to me, using -core and -extra does seem better than supported/unsupported. No more concerns from me, so this only needs security team review (and server team subscription to the package) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927004 Title: [MIR] fence-agents To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1927004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927779] [NEW] MODULES=list results in error
Public bug reported: [impact] setting MODULES=list in /etc/initramfs-tools/initramfs.conf results in an error/warning when running update-initramfs [test case] edit initramfs.conf to change MODULES=list and run update-initramfs: $ grep MODULES /etc/initramfs-tools/initramfs.conf # MODULES: [ most | netboot | dep | list ] MODULES=list $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.8.0-48-generic find: ‘/var/tmp/mkinitramfs_Yr04uh/lib/modules/5.8.0-48-generic/kernel’: No such file or directory [regression potential] any regression would likely result in an initramfs that did not include the correct/required modules, and/or failure to build a new initramfs [scope] this is needed for g and earlier. this is not fixed in debian, but is fixed in h and i. for debian, MR open: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/48 [other info] this caused some of the 'amd64-*' autopkgtests to fail in h until it was fixed. those autopkgtests don't exist in g and earlier so this was not noticed until now. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: initramfs-tools (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: initramfs-tools (Ubuntu Focal) Importance: Undecided Status: New ** Affects: initramfs-tools (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu) Status: New => Fix Released ** Description changed: [impact] setting MODULES=list in /etc/initramfs-tools/initramfs.conf results in an error/warning when running update-initramfs [test case] edit initramfs.conf to change MODULES=list and run update-initramfs: $ grep MODULES /etc/initramfs-tools/initramfs.conf # MODULES: [ most | netboot | dep | list ] MODULES=list $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.8.0-48-generic find: ‘/var/tmp/mkinitramfs_Yr04uh/lib/modules/5.8.0-48-generic/kernel’: No such file or directory [regression potential] any regression would likely result in an initramfs that did not include the correct/required modules, and/or failure to build a new initramfs [scope] this is needed for g and earlier. this is not fixed in debian, but is fixed in h and i. + for debian, MR open: + https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/48 + [other info] this caused some of the 'amd64-*' autopkgtests to fail in h until it was fixed. those autopkgtests don't exist in g and earlier so this was not noticed until now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927779 Title: MODULES=list results in error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1927779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927779] Re: MODULES=list results in error
** Changed in: initramfs-tools (Ubuntu Bionic) Status: New => Invalid ** Description changed: [impact] setting MODULES=list in /etc/initramfs-tools/initramfs.conf results in an error/warning when running update-initramfs [test case] edit initramfs.conf to change MODULES=list and run update-initramfs: $ grep MODULES /etc/initramfs-tools/initramfs.conf # MODULES: [ most | netboot | dep | list ] MODULES=list $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.8.0-48-generic find: ‘/var/tmp/mkinitramfs_Yr04uh/lib/modules/5.8.0-48-generic/kernel’: No such file or directory [regression potential] any regression would likely result in an initramfs that did not include the correct/required modules, and/or failure to build a new initramfs [scope] - this is needed for g and earlier. + this is needed for f and g. this is not fixed in debian, but is fixed in h and i. + + the code in b is different and doesn't include this bug, so this doesn't + apply to b. for debian, MR open: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/48 [other info] this caused some of the 'amd64-*' autopkgtests to fail in h until it was fixed. those autopkgtests don't exist in g and earlier so this was not noticed until now. ** Changed in: initramfs-tools (Ubuntu Focal) Status: New => In Progress ** Changed in: initramfs-tools (Ubuntu Groovy) Status: New => In Progress ** Changed in: initramfs-tools (Ubuntu Focal) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: initramfs-tools (Ubuntu Groovy) Assignee: (unassigned) => Dan Streetman (ddstreet) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927779 Title: MODULES=list results in error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1927779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917780] Re: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0
** Description changed: [Impact] - * initramfs-tools does not include fsck in initrd if MNT_PASS equals + * initramfs-tools does not include fsck in initrd if MNT_PASS equals zero in the fstab entries. This has lead to the following situation : when dropping to initramfs shell during boot due to fs errors, we are not able to run fsck manually because it is not included in initrd. fsck should be included regardless of the MNT_PASS value. [Test Plan] - * change /etc/fstab with PASSNO set to 0 for all entries - * update-initramfs -u - * lsinitramfs that is just generated - * observe that it includes fsck utilities for the filesystems in /etc/fstab. I.e. fsck.ext4 e2fsck must exist - + * change /etc/fstab with PASSNO set to 0 for all entries + * update-initramfs -u + * lsinitramfs that is just generated + * observe that it includes fsck utilities for the filesystems in /etc/fstab. I.e. fsck.ext4 e2fsck must exist [Where problems could occur] - * The initramfs size will increase slightly upon upgrade, for the same + * The initramfs size will increase slightly upon upgrade, for the same initramfs-tools default options & kernel. However, one can control and remove fsck binaries (or include more of them) by setting FSTYPE variable in the initramfs settings. + + [scope] + + this is required for b/f/g + + this is fixed already in h and i + + [other info] + + debian MR is open: + https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/49 ** Also affects: initramfs-tools (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu Bionic) Status: New => In Progress ** Changed in: initramfs-tools (Ubuntu Groovy) Status: New => In Progress ** Changed in: initramfs-tools (Ubuntu Focal) Status: New => In Progress ** Changed in: initramfs-tools (Ubuntu Groovy) Importance: Undecided => Critical ** Changed in: initramfs-tools (Ubuntu Focal) Importance: Undecided => Critical ** Changed in: initramfs-tools (Ubuntu Bionic) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917780 Title: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1917780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571506] Re: update-initramfs should include firmware from /lib/firmware/updates
** Also affects: initramfs-tools (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu Bionic) 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/1571506 Title: update-initramfs should include firmware from /lib/firmware/updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1571506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927779] Re: MODULES=list results in error
** Changed in: initramfs-tools (Ubuntu Focal) Importance: Undecided => Low ** Changed in: initramfs-tools (Ubuntu Groovy) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927779 Title: MODULES=list results in error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1927779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917780] Re: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0
** Changed in: initramfs-tools (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: initramfs-tools (Ubuntu Focal) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: initramfs-tools (Ubuntu Groovy) Assignee: (unassigned) => Dan Streetman (ddstreet) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917780 Title: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1917780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927779] Re: MODULES=list results in error
uploaded to f/g -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927779 Title: MODULES=list results in error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1927779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917780] Re: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0
uploaded to b/f/g -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917780 Title: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1917780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876570] Re: Could not resume from hibernation when swap is specified as device
uploaded to b/f/g -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876570 Title: Could not resume from hibernation when swap is specified as device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1876570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571506] Re: update-initramfs should include firmware from /lib/firmware/updates
uploaded to bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571506 Title: update-initramfs should include firmware from /lib/firmware/updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1571506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927004] Re: [MIR] fence-agents
I agree -supported is a bad term to use, it indeed is far too ambiguous; the meaning of 'supported' varies wildly depending on who you ask. I think even between us three discussing this the meaning probably is different ;-) I don't have particularly strong feelings on the specific naming of each package, other than not using the plain name 'fence-agents'. I wonder if this topic is worth an email to ubuntu-devel-discuss to come up with some standardized naming for packages that are split into 'good' and 'bad' (and 'ugly') binary debs? Or maybe even debian-devel- discuss...possibly some of the old-school debian/ubuntu people might have already discussed this topic. The -good, -bad, -ugly naming may be most appropriate but we probably shouldn't have people pick naming arbitrarily each time a package is split into multiple debs like this. For example another naming approach might be -stable and -unstable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927004 Title: [MIR] fence-agents To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1927004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827442] Re: [MIR] libheif
It's unclear to me if this ever was approved by the MIR team, possibly comment 1 was intended to be a MIR team review, but it's not clear if that was the intention and certainly doesn't have the normal MIR review details. Technically after security team review, this should have been changed to status 'In Progress' to wait for seeding updates, but I think this got 'lost' in the process since it was in state 'CONFIRMED' but the MIR team has only been looking at 'NEW' state unclaimed bugs. @paelzer I updated the 'All open unclaimed MIR bugs' link on the MIR wiki page to show both NEW and CONFIRMED bugs, and I think we should be sure to include 'CONFIRMED' state bugs in our weekly review, not just 'NEW' state bugs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827442 Title: [MIR] libheif To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libde265/+bug/1827442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927161] Re: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one
ubuntu@lp1927161-h:~$ pull-lp-source openssl hirsute ... ubuntu@lp1927161-h:~$ cd openssl-1.1.1j/ ubuntu@lp1927161-h:~/openssl-1.1.1j$ dpkg-parsechangelog | grep Version Version: 1.1.1j-1ubuntu3.1 ubuntu@lp1927161-h:~/openssl-1.1.1j$ quilt pop -a ubuntu@lp1927161-h:~/openssl-1.1.1j$ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1j-1ubuntu3.1 dpkg-buildpackage: info: source distribution hirsute dpkg-buildpackage: info: source changed by Matthew Ruffell ... dpkg-buildpackage: info: binary and diff upload (original source NOT included) ubuntu@lp1927161-g:~$ pull-lp-source openssl groovy ... ubuntu@lp1927161-g:~$ cd openssl-1.1.1f/ ubuntu@lp1927161-g:~/openssl-1.1.1f$ dpkg-parsechangelog | grep Version Version: 1.1.1f-1ubuntu4.4 ubuntu@lp1927161-g:~/openssl-1.1.1f$ quilt pop -a ... ubuntu@lp1927161-g:~/openssl-1.1.1f$ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1f-1ubuntu4.4 dpkg-buildpackage: info: source distribution groovy dpkg-buildpackage: info: source changed by Matthew Ruffell ... dpkg-buildpackage: info: binary and diff upload (original source NOT included) ** Tags removed: verification-needed verification-needed-groovy verification-needed-hirsute ** Tags added: verification-done verification-done-groovy verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927161 Title: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921475] Re: [2.9.2] Commissioning does not collect correct storage information
systemd doesn't report any 'E:ID_ATA_ROTATION_RATE_RPM' value for the SCSI drive, because it's a SCSI drive, not an ATA drive. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921475 Title: [2.9.2] Commissioning does not collect correct storage information To manage notifications about this bug go to: https://bugs.launchpad.net/lxd/+bug/1921475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927004] Re: [MIR] fence-agents
Thanks Rick. > There's some prior art to this in the archive I think it would really be good for the server team to follow up on this naming convention and get some agreement across the distro (not only for server team maintained packages), as we don't want different teams/people coming up with different naming conventions/styles for the same problem. And then it would be great if it was documented somewhere, maybe at https://packaging.ubuntu.com/html/packaging-new-software.html and/or we could add it to the MIR wiki page (though MIR isn't really the only, or even correct, time for package binary deb naming to be evaluated). Also note that while 'base' and 'extra' might have been used before, you might not have seen Seth's comment 7 that indicated it didn't turn out very well for apparmor, so maybe 'base' and 'extra' aren't the best names, even if they've been used before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927004 Title: [MIR] fence-agents To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1927004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927004] Re: [MIR] fence-agents
I think you might be too focused on this particular package, as I'm not seeing any 'myriad' of use cases; the breakdown is: 1) a 'common' binary deb that provides something that other binary debs use 2) a 'maintained' or 'stable' binary deb that provides stuff that is 'maintained' and/or 'works mostly well' 3) a 'unmaintained' or 'unstable' binary deb that provides stuff that is 'not maintained' and/or 'doesnt work all the time' The specific adjectives may vary, but I think that's the pattern here and I don't think this package (or the resource-agents package) is unique in having that kind of split. All I'm saying is that if more than a couple packages in Ubuntu break down (some of) their binary debs in this kind of way, it would be good to have consistency in the naming of the packages by having a distro- wide discussion (however short that discusssion might be) and then documenting the guidelines in some appropriate place. Otherwise, this will just get repeated for every package that gets split up in the same manner. The Ubuntu community might have some helpful input into this if we give them the chance to voice an opinion by starting a discussion on ubuntu-devel-discuss, instead of just deciding in-house. In any case, I do think that discussing the naming in this MIR bug any further would absolutely be bikeshedding, so I recommend we don't continue here. This remains an ACK from the MIR team, as the naming was never a blocker for MIR. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927004 Title: [MIR] fence-agents To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1927004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927757] Re: sshuttle autopkgtest is rather lengthy
> Can some of the testing be shortened Well the test really does nothing other than run 'ssh' from container A to container B before sshuttle is run and again while it's running. So (other than timeouts) the test can't be shortened much. I think most of the time comes from timeouts and the lxd container management. > or run in parallel? I wish...I tried, this was rejected: https://code.launchpad.net/~ddstreet/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/401036 If you can change vorlon's mind that would be great; the 'big' tests get 4 vcpus so things could (theoretically) be parallelized up to 4 tests at once. However, if the reduction of timeouts and any lxd image handling improvements are done, the test might not need more cores; and also if the main cause of the long test isn't being cpu-bound then parallelization may not help. > A quick look at the logs suggests that a lot of time is spent waiting on timeouts. Perhaps the timeouts could be configured to a shorter number in some cases? probably so, i uploaded a new version (to impish) that reduces the expected timeouts down to 20 seconds, and also the detection of when sshuttle had started seems to have not been working in all cases (since it seems the sshuttle output on success varies across releases). Hopefully this will speed it up some. You might be able to get the length down more by messing with lxd to see if you can use an approach other than snapshotting to put each test instance back into a 'fresh' state; maybe even just re-launching instead of restoring from snapshot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927757 Title: sshuttle autopkgtest is rather lengthy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1927757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928081] [NEW] impossible to run autopkgtest in hirsute
Public bug reported: [impact] the autopkgtest in hirsute was updated to depend on tcpdump (>= 4.99.0) but that version of tcpdump did not make it out of hirsute-proposed [test case] check scapy autopkgtests in hirsute [regression potential] any regression would likely result in autopkgtest failures [scope] this is needed only in h scapy in g and earlier doesn't have any autopkgtests, so this doesn't apply there in i, tcpdump 0.99 is available so the autopkgtest is able to install it ** Affects: scapy (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: scapy (Ubuntu Hirsute) Importance: Low Status: New ** Also affects: scapy (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: scapy (Ubuntu) Status: New => Fix Released ** Changed in: scapy (Ubuntu Hirsute) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928081 Title: impossible to run autopkgtest in hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scapy/+bug/1928081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928081] Re: impossible to run autopkgtest in hirsute
** Description changed: [impact] the autopkgtest in hirsute was updated to depend on tcpdump (>= 4.99.0) but that version of tcpdump did not make it out of hirsute-proposed [test case] check scapy autopkgtests in hirsute [regression potential] any regression would likely result in autopkgtest failures [scope] - this is needed only in h + this is needed in h, and will be needed in i if tcpdump >= 0.99.0 + doesn't make it out of impish-proposed scapy in g and earlier doesn't have any autopkgtests, so this doesn't apply there - - in i, tcpdump 0.99 is available so the autopkgtest is able to install it ** Also affects: scapy (Ubuntu Impish) Importance: Undecided Status: Fix Released ** Changed in: scapy (Ubuntu Impish) Status: Fix Released => New ** Changed in: scapy (Ubuntu Impish) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928081 Title: impossible to run autopkgtest in hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scapy/+bug/1928081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928081] Re: impossible to run autopkgtest in hirsute
** Tags added: block-proposed-hirsute ** Description changed: [impact] the autopkgtest in hirsute was updated to depend on tcpdump (>= 4.99.0) but that version of tcpdump did not make it out of hirsute-proposed [test case] check scapy autopkgtests in hirsute [regression potential] any regression would likely result in autopkgtest failures [scope] this is needed in h, and will be needed in i if tcpdump >= 0.99.0 doesn't make it out of impish-proposed scapy in g and earlier doesn't have any autopkgtests, so this doesn't apply there + + [other info] + + note that this *should not* be applied to impish, as the expectation + there is that tcpdump 0.99.0 will eventually get released to impish- + release, since we're at the start of the cycle now. + + the only way this bug would need a change in the scapy autopkgtest + control file is if tcpdump 0.99.0 doesn't actually make it into impish- + release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928081 Title: impossible to run autopkgtest in hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scapy/+bug/1928081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1664844] Re: No distinction between link-up and link-down interfaces
** Also affects: systemd (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Hirsute) 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/1664844 Title: No distinction between link-up and link-down interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1664844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928198] Re: Failed to start Suspend: A start job for unit systemd-suspend.service has failed.
> [18841.414601] PM: dpm_run_callback(): usb_dev_suspend+0x0/0x20 returns -16 > [18841.414626] PM: Device usb2 failed to suspend async: error -16 you seem to have a usb device that is blocking suspect. You don't have many usb devices: Bus 001 Device 002: ID 8087:8001 Intel Corp. Integrated Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 04f3:2012 Elan Microelectronics Corp. Touchscreen Bus 002 Device 002: ID 8087:07dc Intel Corp. Bluetooth wireless interface Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub my guess would be your touchscreen. ** Package changed: systemd (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928198 Title: Failed to start Suspend: A start job for unit systemd-suspend.service has failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928198] Re: Failed to start Suspend: A start job for unit systemd-suspend.service has failed.
sorry i meant 'blocking suspend' in the last comment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928198 Title: Failed to start Suspend: A start job for unit systemd-suspend.service has failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927161] Re: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one
The only autopkgtests still failing are for 'scapy', those fail due to bug 1928081 and there is an upload of scapy in the queue to fix that -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927161 Title: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928081] Re: impossible to run autopkgtest in hirsute
** Changed in: scapy (Ubuntu Impish) Status: New => Fix Released ** Description changed: [impact] the autopkgtest in hirsute was updated to depend on tcpdump (>= 4.99.0) but that version of tcpdump did not make it out of hirsute-proposed [test case] check scapy autopkgtests in hirsute [regression potential] any regression would likely result in autopkgtest failures [scope] - this is needed in h, and will be needed in i if tcpdump >= 0.99.0 + this is needed in h, and will be needed in i if tcpdump >= 4.99.0 doesn't make it out of impish-proposed scapy in g and earlier doesn't have any autopkgtests, so this doesn't apply there [other info] - note that this *should not* be applied to impish, as the expectation - there is that tcpdump 0.99.0 will eventually get released to impish- - release, since we're at the start of the cycle now. - - the only way this bug would need a change in the scapy autopkgtest - control file is if tcpdump 0.99.0 doesn't actually make it into impish- - release + tcpdump 4.99.0 has been released to impish-release so marking this as + fix released for impish, since the scapy autopkgtest should be able to + run on impish now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928081 Title: impossible to run autopkgtest in hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scapy/+bug/1928081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927779] Re: MODULES=list results in error
ubuntu@lp1927779-g:~$ dpkg -l | grep initramfs-tools ii initramfs-tools0.137ubuntu12 all generic modular initramfs generator (automation) ii initramfs-tools-bin0.137ubuntu12 amd64 binaries used by initramfs-tools ii initramfs-tools-core 0.137ubuntu12 all generic modular initramfs generator (core tools) ubuntu@lp1927779-g:~$ grep MODULES= /etc/initramfs-tools/initramfs.conf MODULES=list ubuntu@lp1927779-g:~$ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.8.0-53-generic find: ‘/var/tmp/mkinitramfs_6itbCp/lib/modules/5.8.0-53-generic/kernel’: No such file or directory ubuntu@lp1927779-g:~$ dpkg -l | grep initramfs-tools ii initramfs-tools0.137ubuntu12.1 all generic modular initramfs generator (automation) ii initramfs-tools-bin0.137ubuntu12.1 amd64 binaries used by initramfs-tools ii initramfs-tools-core 0.137ubuntu12.1 all generic modular initramfs generator (core tools) ubuntu@lp1927779-g:~$ grep MODULES= /etc/initramfs-tools/initramfs.conf MODULES=list ubuntu@lp1927779-g:~$ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.8.0-53-generic ubuntu@lp1927779-g:~$ ** Tags removed: verification-needed-groovy ** Tags added: 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/1927779 Title: MODULES=list results in error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1927779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927779] Re: MODULES=list results in error
ubuntu@lp1927779-f:~$ dpkg -l |grep initramfs-tools ii initramfs-tools0.136ubuntu6.4all generic modular initramfs generator (automation) ii initramfs-tools-bin0.136ubuntu6.4amd64 binaries used by initramfs-tools ii initramfs-tools-core 0.136ubuntu6.4all generic modular initramfs generator (core tools) ubuntu@lp1927779-f:~$ grep MODULES= /etc/initramfs-tools/initramfs.conf MODULES=list ubuntu@lp1927779-f:~$ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.4.0-72-generic find: ‘/var/tmp/mkinitramfs_zLaWLR/lib/modules/5.4.0-72-generic/kernel’: No such file or directory ubuntu@lp1927779-f:~$ dpkg -l |grep initramfs-tools ii initramfs-tools0.136ubuntu6.5all generic modular initramfs generator (automation) ii initramfs-tools-bin0.136ubuntu6.5amd64 binaries used by initramfs-tools ii initramfs-tools-core 0.136ubuntu6.5all generic modular initramfs generator (core tools) ubuntu@lp1927779-f:~$ grep MODULES= /etc/initramfs-tools/initramfs.conf MODULES=list ubuntu@lp1927779-f:~$ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.4.0-72-generic ubuntu@lp1927779-f:~$ ** 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/1927779 Title: MODULES=list results in error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1927779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571506] Re: update-initramfs should include firmware from /lib/firmware/updates
ubuntu@lp1571506-b:~$ dpkg -l|grep initramfs-tools ii initramfs-tools 0.130ubuntu3.11 all generic modular initramfs generator (automation) ii initramfs-tools-bin 0.130ubuntu3.11 amd64binaries used by initramfs-tools ii initramfs-tools-core 0.130ubuntu3.11 all generic modular initramfs generator (core tools) ubuntu@lp1571506-b:~$ sudo lsinitramfs /boot/initrd.img-4.15.0-142-generic | grep firmware lib/udev/rules.d/50-firmware.rules lib/firmware lib/firmware/netronome lib/firmware/netronome/nic_AMDA0081-0001_1x40.nffw lib/firmware/netronome/nic_AMDA0097-0001_2x40.nffw lib/firmware/netronome/nic_AMDA0099-0001_2x25.nffw lib/firmware/netronome/nic_AMDA0097-0001_8x10.nffw lib/firmware/netronome/nic_AMDA0099-0001_2x10.nffw lib/firmware/netronome/nic_AMDA0081-0001_4x10.nffw lib/firmware/netronome/nic_AMDA0097-0001_4x10_1x40.nffw lib/firmware/netronome/nic lib/firmware/netronome/nic/nic_AMDA0081-0001_1x40.nffw lib/firmware/netronome/nic/nic_AMDA0097-0001_2x40.nffw lib/firmware/netronome/nic/nic_AMDA0099-0001_2x25.nffw lib/firmware/netronome/nic/nic_AMDA0097-0001_8x10.nffw lib/firmware/netronome/nic/nic_AMDA0099-0001_2x10.nffw lib/firmware/netronome/nic/nic_AMDA0081-0001_4x10.nffw lib/firmware/netronome/nic/nic_AMDA0097-0001_4x10_1x40.nffw lib/firmware/netronome/nic/nic_AMDA0096-0001_2x10.nffw lib/firmware/netronome/nic_AMDA0096-0001_2x10.nffw lib/firmware/ql2100_fw.bin lib/firmware/ql2400_fw.bin lib/firmware/bnx2x lib/firmware/bnx2x/bnx2x-e1-7.13.1.0.fw lib/firmware/bnx2x/bnx2x-e2-7.13.1.0.fw lib/firmware/bnx2x/bnx2x-e1h-7.13.1.0.fw lib/firmware/mellanox lib/firmware/mellanox/mlxsw_spectrum-13.1530.152.mfa2 lib/firmware/tigon lib/firmware/tigon/tg3_tso.bin lib/firmware/tigon/tg3_tso5.bin lib/firmware/tigon/tg3.bin lib/firmware/ql2322_fw.bin lib/firmware/qlogic lib/firmware/qlogic/1280.bin lib/firmware/qlogic/12160.bin lib/firmware/qlogic/1040.bin lib/firmware/ql2300_fw.bin lib/firmware/ql2500_fw.bin lib/firmware/ql2200_fw.bin lib/modules/4.15.0-142-generic/kernel/drivers/firmware lib/modules/4.15.0-142-generic/kernel/drivers/firmware/iscsi_ibft.ko ubuntu@lp1571506-b:~$ sudo mkdir /lib/firmware/updates ubuntu@lp1571506-b:~$ sudo mv /lib/firmware/bnx2x /lib/firmware/updates/ ubuntu@lp1571506-b:~$ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-4.15.0-142-generic ubuntu@lp1571506-b:~$ sudo lsinitramfs /boot/initrd.img-4.15.0-142-generic | grep firmware lib/udev/rules.d/50-firmware.rules lib/firmware lib/firmware/netronome lib/firmware/netronome/nic_AMDA0081-0001_1x40.nffw lib/firmware/netronome/nic_AMDA0097-0001_2x40.nffw lib/firmware/netronome/nic_AMDA0099-0001_2x25.nffw lib/firmware/netronome/nic_AMDA0097-0001_8x10.nffw lib/firmware/netronome/nic_AMDA0099-0001_2x10.nffw lib/firmware/netronome/nic_AMDA0081-0001_4x10.nffw lib/firmware/netronome/nic_AMDA0097-0001_4x10_1x40.nffw lib/firmware/netronome/nic lib/firmware/netronome/nic/nic_AMDA0081-0001_1x40.nffw lib/firmware/netronome/nic/nic_AMDA0097-0001_2x40.nffw lib/firmware/netronome/nic/nic_AMDA0099-0001_2x25.nffw lib/firmware/netronome/nic/nic_AMDA0097-0001_8x10.nffw lib/firmware/netronome/nic/nic_AMDA0099-0001_2x10.nffw lib/firmware/netronome/nic/nic_AMDA0081-0001_4x10.nffw lib/firmware/netronome/nic/nic_AMDA0097-0001_4x10_1x40.nffw lib/firmware/netronome/nic/nic_AMDA0096-0001_2x10.nffw lib/firmware/netronome/nic_AMDA0096-0001_2x10.nffw lib/firmware/ql2100_fw.bin lib/firmware/ql2400_fw.bin lib/firmware/mellanox lib/firmware/mellanox/mlxsw_spectrum-13.1530.152.mfa2 lib/firmware/tigon lib/firmware/tigon/tg3_tso.bin lib/firmware/tigon/tg3_tso5.bin lib/firmware/tigon/tg3.bin lib/firmware/ql2322_fw.bin lib/firmware/qlogic lib/firmware/qlogic/1280.bin lib/firmware/qlogic/12160.bin lib/firmware/qlogic/1040.bin lib/firmware/ql2300_fw.bin lib/firmware/ql2500_fw.bin lib/firmware/ql2200_fw.bin lib/modules/4.15.0-142-generic/kernel/drivers/firmware lib/modules/4.15.0-142-generic/kernel/drivers/firmware/iscsi_ibft.ko ubuntu@lp1571506-b:~$ sudo lsinitramfs /boot/initrd.img-4.15.0-142-generic | grep firmware | grep bnx2x ubuntu@lp1571506-b:~$ ubuntu@lp1571506-b:~$ dpkg -l|grep initramfs-tools ii initramfs-tools 0.130ubuntu3.12 all generic modular initramfs generator (automation) ii initramfs-tools-bin 0.130ubuntu3.12 amd64binaries used by initramfs-tools ii initramfs-tools-core 0.130ubuntu3.12 all generic modular initramfs generator (core tools) ubuntu@lp1571506-b:~$ sudo lsinitramfs /boot/initrd.img-4.15.0-142-generic | grep firmware lib/udev/rules.d/50-firmware.rules lib/firmware lib/firmware/netronome lib/firmware/netronome/nic_AMDA0081-0001_1x40.nffw lib/firmware/netronome/nic_AMDA0097-0001_2x40.nffw lib/firmware/netronome/nic_AMDA0099-
[Bug 1917780] Re: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0
@joalif do you have time to do verification for this bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917780 Title: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1917780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876570] Re: Could not resume from hibernation when swap is specified as device
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876570 Title: Could not resume from hibernation when swap is specified as device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1876570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916485] Re: test -x fails inside shell scripts in containers
** Description changed: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h - $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz + $ sudo tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days our CI pipelines to recreate Docker images fails for the Hirsute images. From comparison this seems to be caused by apt 2.1.20. The build fails with: 0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of them is required for this operation The simple Dockerfile to reproduce the error - "docker build -t foo ." FROM amd64/ubuntu:hirsute MAINTAINER Florian Lohoff USER root RUN apt-get update \ && DEBIAN_FRONTEND=noninteractive apt-get -y install curl gnupg apt \ && curl https://syncthing.net/release-key.txt | apt-key add - Breaking it down it this seems to be an issue that there is new functionality in apt/apt-key e.g. security hardening that docker prohibits in its containers. Running this manually works only in an --privileged container. So adding keys in unpriviledged container or possibly kubernetes will not work anymore. Flo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1916485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895132] Re: s390x broken with unknown syscall number on kernels < 5.8
Using verification steps from bug 1916485 ubuntu@test-s390x:~$ uname -a Linux test-s390x 4.15.0-143-generic #147-Ubuntu SMP Wed Apr 14 16:16:31 UTC 2021 s390x s390x s390x GNU/Linux ubuntu@test-s390x:~$ mkdir h ubuntu@test-s390x:~$ cd h ubuntu@test-s390x:~/h$ sudo tar xf ../hirsute-server-cloudimg-s390x-root.tar.xz ubuntu@test-s390x:~/h$ sudo systemd-nspawn Spawning container h on /home/ubuntu/h. Press ^] three times within 1s to kill container. root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 root root 1361888 Feb 22 09:33 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail ubuntu@test-s390x:~$ uname -a Linux test-s390x 4.15.0-144-generic #148-Ubuntu SMP Sat May 8 02:31:39 UTC 2021 s390x s390x s390x GNU/Linux ubuntu@test-s390x:~$ mkdir h ubuntu@test-s390x:~$ cd h ubuntu@test-s390x:~/h$ sudo tar xf ../hirsute-server-cloudimg-s390x-root.tar.xz ubuntu@test-s390x:~/h$ sudo systemd-nspawn Spawning container h on /home/ubuntu/h. Press ^] three times within 1s to kill container. root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 root root 1361888 Feb 22 09:33 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" root@h:~# ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895132 Title: s390x broken with unknown syscall number on kernels < 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1895132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923377] Re: Automatically installed systemd:i386 makes graphical boot hang
Sorry, providing a couple lines from the apt update history log isn't enough for anyone to be able to analyze anything. You can try attaching your full journal logs, and the full apt and dpkg logs would help as well, but even the logs may not help and more complete system configuration data may be needed. ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923377 Title: Automatically installed systemd:i386 makes graphical boot hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921696] Re: Failed to start Load/Save RF Kill Switch Status
** Also affects: systemd (Ubuntu Focal) 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/1921696 Title: Failed to start Load/Save RF Kill Switch Status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1921696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921696] Re: Failed to start Load/Save RF Kill Switch Status
ASUS ** Also affects: systemd (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Groovy) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Focal) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Groovy) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Groovy) Status: New => In Progress ** Changed in: systemd (Ubuntu Focal) 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/1921696 Title: Failed to start Load/Save RF Kill Switch Status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1921696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803993] Re: Password appears on the VT1 screen
Unfortunately I can't reproduce this bug, even with the 0.9.3-1ubuntu7.18.04.1 version of plymouth installed, so I can't say for sure that it's fixed with plymouth 0.9.3-1ubuntu7.18.04.2. Also note that the [test case] in the description is wrong, that would be correct with the systemd change made earlier, but that change was reverted upstream and in ubuntu, so the test case steps aren't an accurate indication that the bug is fixed or not. Anyone on this bug able to reproduce the main problem, of key output (e.g. passwords) being printed on the console and visible between login sessions, and/or during shutdown? If not, I think we should consider this bug fixed. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Changed in: plymouth (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1803993 Title: Password appears on the VT1 screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803993] Re: Password appears on the VT1 screen
I'm marking this invalid for systemd (the patch there was reverted) and fix released for plymouth, with the assumption this was fixed with the patch for bug 1817738. If anyone is able to reproduce the problem please add a comment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1803993 Title: Password appears on the VT1 screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921696] Re: Failed to start Load/Save RF Kill Switch Status
** Also affects: systemd via https://github.com/systemd/systemd/issues/18677 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921696 Title: Failed to start Load/Save RF Kill Switch Status To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1921696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923686] Re: Ubuntu 20.10 Network Issue
It's not clear what exactly you are trying to do, or what is changing that you don't like. maybe you should provide both 'good' and 'bad' data for comparison, like the output of 'ip a' and 'ip r' ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923686 Title: Ubuntu 20.10 Network Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905166] Re: systemd-shutdown cannot detach DM
** Changed in: systemd (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905166 Title: systemd-shutdown cannot detach DM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/finalrd/+bug/1905166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920107] Re: Failed messages of sd-umoun show with reboot/shutdown
** Package changed: systemd (Ubuntu) => finalrd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920107 Title: Failed messages of sd-umoun show with reboot/shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1920107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905166] Re: systemd-shutdown cannot detach DM
This actually appears to be bug(s) in the 'finalrd', not systemd; probably bug 1920107 is a dup of this one ** Package changed: systemd (Ubuntu) => finalrd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905166 Title: systemd-shutdown cannot detach DM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/finalrd/+bug/1905166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported
i uploaded, but then saw dannf had already uploaded too a few hours ago...sorry for the duplicate uploads! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879214 Title: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924494] Re: Systemd shutdown order unmounts filesystem used by qemu/kvm guest before shutting down the guest
** Package changed: systemd (Ubuntu) => libvirt (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924494 Title: Systemd shutdown order unmounts filesystem used by qemu/kvm guest before shutting down the guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1924494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925216] [NEW] confusing but harmless warning messages printed about syscalls
Public bug reported: [impact] systemd prints messages that complain about system calls such as: /lib/systemd/system/systemd-journald.service:33: Failed to parse system call, ignoring: pidfd_getfd [test case] boot bionic system with 4.15 kernel that does not support pidfd_getfd syscall [regression potential] any regression would prevent correct configuration of seccomp syscall filters, and/or failure to load/parse unit files that contain SystemCallFilter= directives [scope] this is needed only for b this is fixed upstream by commit 13d92c6300edbb1369f97c2e1bef4c4096de8ddb which was included in v238, so this is fixed in focal and later this is not needed for x as seccomp handling is completely different in that older release [other info] as the warning states, the invalid system call is ignored, which is the correct action, and the patch to fix this just changes the log to debug instead of warning (along with consolidation of several flag params into a single flag enum). Thus, no actual change in behavior should occur (other than logging the messages as debug instead of warning). ** Affects: systemd (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: systemd (Ubuntu Bionic) Importance: Low Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925216 Title: confusing but harmless warning messages printed about syscalls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1925216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925216] Re: confusing but harmless warning messages printed about syscalls
** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925216 Title: confusing but harmless warning messages printed about syscalls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1925216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923115] Re: Networkd vs udev nic renaming race condition
** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923115 Title: Networkd vs udev nic renaming race condition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925215] Re: System completely freezes and requires reboot
First, 21.04 isn't released yet, so you shouldn't be using it unless you're prepared for bugs. Second, it would be better to ask for general debugging help at https://askubuntu.com/ since this is for reporting bugs. There's no information in your attached dmesg that might help, though that is probably because it's from the boot after your hang, so it doesn't include anything useful. If you have any details about any actual bug please attach it. ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925215 Title: System completely freezes and requires reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1925215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925141] Re: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1)
> Actual results: > * CapsLock key switches on CapsLock LED, the LED state indicates current > CapsLock key function > > Expected results: > * CapsLock LED is always off the 'actual results' sounds like correct behavior to me...? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925141 Title: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1) To manage notifications about this bug go to: https://bugs.launchpad.net/kbd-chooser/+bug/1925141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923618] Re: upgrading systemd on groovy terminates sessions
I tried reproducing this in a VM, but it was able to upgrade systemd with no problems, is there anything in your logs indicating why the gnome session was terminated? ** Changed in: systemd (Ubuntu Groovy) Status: New => Incomplete ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923618 Title: upgrading systemd on groovy terminates sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916485] Re: test -x fails inside shell scripts in containers
Problem seems to be on s390x with the 4.15 kernel, faccessat2() still returns EPERM: faccessat2(AT_FDCWD, "/bin/bash", X_OK, AT_EACCESS) = -1 EPERM (Operation not permitted) while on amd64 it now returns ENOSYS which is correctly handled with fallback to faccessat() faccessat2(AT_FDCWD, "/bin/bash", X_OK, AT_EACCESS) = -1 ENOSYS (Function not implemented) faccessat(AT_FDCWD, "/bin/bash", X_OK) = 0 (note both traces were of bash running 'test -x /bin/bash') -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1916485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916485] Re: test -x fails inside shell scripts in containers
Interestingly, faccessat2() does correctly return ENOSYS when using a simple chroot instead of systemd-nspawn: ubuntu@test-s390x:~/h$ sudo systemd-nspawn Spawning container h on /home/ubuntu/h. Press ^] three times within 1s to kill container. root@h:~# test -x /bin/bash || echo "fail" fail root@h:~# exit logout Container h exited successfully. ubuntu@test-s390x:~/h$ sudo chroot . root@test-s390x:/# test -x /bin/bash || echo "fail" root@test-s390x:/# and to verify, stracing bash: faccessat2(AT_FDCWD, "/bin/bash", X_OK, AT_EACCESS) = -1 ENOSYS (Function not implemented) faccessat(AT_FDCWD, "/bin/bash", X_OK) = 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1916485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916485] Re: test -x fails inside shell scripts in containers
It seems the s390x failure on bionic is fixed by the patch(es) for bug 1895132. I'm not 100% sure why it is returning the normal ENOSYS for invalid syscalls except while running under systemd-nspawn, but it might be due to the different syscall entry path taken when _TIF_TRACE is set, and that does get set if _TIF_SECCOMP is set. In any case, I'll send the kernel patches to the ML. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1916485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916485] Re: test -x fails inside shell scripts in containers
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1916485 in case anyone wants to test with the patched kernel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1916485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923618] Re: upgrading systemd on groovy terminates sessions
It looks like something happened to dbus, but it's hard to tell what, if anything. Was this upgrading from 246.6-1ubuntu1.2 to 246.6-1ubuntu1.3, or some other versions? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923618 Title: upgrading systemd on groovy terminates sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925055] Re: Boot stuck in UEFI after enrolling keys for drivers
> But after I install some drivers (NVidia you appear to have 2 separate graphics cards: [4.893710] nvidia :30:00.0: enabling device (0006 -> 0007) [6.034799] i915 :00:02.0: [drm] fb0: i915drmfb frame buffer device my guess would be you're having problems with the kernel choosing the correct graphics device to use, and/or some problem with the driver not correctly updating the screen. I also noticed this: [5.535665] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 however you said disabling secure boot doesn't help, so that's probably not related. Have you tried uninstalling the nvidia driver package to see if that is what's causing the problem? > Return to the original console by Alt+Fn+F1 Just a note, since you're booting with vt.handoff=7 the active VT should be 7, i.e. Ctrl+Alt+F7 You might also want to try booting with all the possibly relevant params removed, i.e. remove 'quiet splash vt.handoff=7' You could also try adding 'nomodeset' to the kernel boot params to see if that helps. In any case, this certainly looks like a kernel issue, not systemd. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895132] Re: s390x broken with unknown syscall number on kernels < 5.8
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Description changed:
SRU Justification
+
+ Note: I marked this as affecting bionic as well, as discovered in bug
+ 1916485.
Impact: On kernels prior to 5.8 when a task is in traced state (due to
audit, ptrace, or seccomp) s390x and a syscall is issued that the kernel
doesn't know about s390x will not return ENOSYS in r2 but instead will
return the syscall number. This breaks userspace all over the place. The
following program compiled on s390x will output 500 instead of -ENOSYS:
root@test:~# cat test.c
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
static inline int dummy_inline_asm(void)
{
register long r1 asm("r1") = 500;
register long r2 asm("r2") = -1;
register long r3 asm("r3") = -1;
register long r4 asm("r4") = -1;
register long r5 asm("r5") = -1;
register long __res_r2 asm("r2");
asm volatile(
"svc 0\n\t"
: "=d"(__res_r2)
: "d"(r1), "0"(r2), "d"(r3), "d"(r4), "d"(r5)
: "memory");
return (int) __res_r2;
}
static inline int dummy_syscall(void)
{
return syscall(500, -1, -1, -1, -1);
}
int main(int argc, char *argv[])
{
printf("Uhm: %d\n", dummy_inline_asm());
printf("Uhm: %d\n", dummy_syscall());
exit(EXIT_SUCCESS);
}
This breaks LXD on s390x currently completely as well as strace.
Fix: Backport
commit cd29fa798001075a554b978df3a64e6656c25794
Author: Sven Schnelle
Date: Fri Mar 6 13:18:31 2020 +0100
s390/ptrace: return -ENOSYS when invalid syscall is supplied
The current code returns the syscall number which an invalid
syscall number is supplied and tracing is enabled. This makes
the strace testsuite fail.
Signed-off-by: Sven Schnelle
Signed-off-by: Vasily Gorbik
which got released with 5.8. The commit missed to Cc stable and although
I've asked Sven to include it in stable I'm not sure when or if it will
show up there.
Regression Potential: Limited to s390x.
Test Case: The reproducer given above needs to output -ENOSYS instead of
500.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895132
Title:
s390x broken with unknown syscall number on kernels < 5.8
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1895132/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925484] Re: Add Impish Indri
i think this should be released yesterday, since distro-info --devel is now broken for all releases: $ distro-info --date=2021-04-21 --devel hirsute $ distro-info --date=2021-04-22 --devel ubuntu-distro-info: Distribution data outdated. Please check for an update for distro-info-data. See /usr/share/doc/distro-info-data/README.Debian for details. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925484 Title: Add Impish Indri To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/1925484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925484] Re: Add Impish Indri
root@lp1925484-b:~# dpkg -l|grep distro-info-data ii distro-info-data 0.37ubuntu0.10 all information about the distributions' releases (data files) root@lp1925484-b:~# for p in devel supported stable; do echo "\$ distro-info --$p"; distro-info --$p; for m in date=2021-04-23 fullname release; do echo "\$ distro-info --$m --$p"; distro-info --$m --$p; done; done $ distro-info --devel impish $ distro-info --date=2021-04-23 --devel impish $ distro-info --fullname --devel Ubuntu 21.10 "Impish Indri" $ distro-info --release --devel 21.10 $ distro-info --supported bionic focal groovy hirsute impish $ distro-info --date=2021-04-23 --supported bionic focal groovy hirsute impish $ distro-info --fullname --supported Ubuntu 18.04 LTS "Bionic Beaver" Ubuntu 20.04 LTS "Focal Fossa" Ubuntu 20.10 "Groovy Gorilla" Ubuntu 21.04 "Hirsute Hippo" Ubuntu 21.10 "Impish Indri" $ distro-info --release --supported 18.04 LTS 20.04 LTS 20.10 21.04 21.10 $ distro-info --stable hirsute $ distro-info --date=2021-04-23 --stable hirsute $ distro-info --fullname --stable Ubuntu 21.04 "Hirsute Hippo" $ distro-info --release --stable 21.04 ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925484 Title: Add Impish Indri To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/1925484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925484] Re: Add Impish Indri
root@lp1925484-f:~# dpkg -l|grep distro-info-data ii distro-info-data 0.43ubuntu1.5 all information about the distributions' releases (data files) root@lp1925484-f:~# for p in devel supported stable; do echo "\$ distro-info --$p"; distro-info --$p; for m in date=2021-04-23 fullname release; do echo "\$ distro-info --$m --$p"; distro-info --$m --$p; done; done $ distro-info --devel impish $ distro-info --date=2021-04-23 --devel impish $ distro-info --fullname --devel Ubuntu 21.10 "Impish Indri" $ distro-info --release --devel 21.10 $ distro-info --supported bionic focal groovy hirsute impish $ distro-info --date=2021-04-23 --supported bionic focal groovy hirsute impish $ distro-info --fullname --supported Ubuntu 18.04 LTS "Bionic Beaver" Ubuntu 20.04 LTS "Focal Fossa" Ubuntu 20.10 "Groovy Gorilla" Ubuntu 21.04 "Hirsute Hippo" Ubuntu 21.10 "Impish Indri" $ distro-info --release --supported 18.04 LTS 20.04 LTS 20.10 21.04 21.10 $ distro-info --stable hirsute $ distro-info --date=2021-04-23 --stable hirsute $ distro-info --fullname --stable Ubuntu 21.04 "Hirsute Hippo" $ distro-info --release --stable 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/1925484 Title: Add Impish Indri To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/1925484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925484] Re: Add Impish Indri
root@lp1925484-g:~# dpkg -l |grep distro-info-data ii distro-info-data 0.44ubuntu1.5 all information about the distributions' releases (data files) root@lp1925484-g:~# for p in devel supported stable; do echo "\$ distro-info --$p"; distro-info --$p; for m in date=2021-04-23 fullname release; do echo "\$ distro-info --$m --$p"; distro-info --$m --$p; done; done $ distro-info --devel impish $ distro-info --date=2021-04-23 --devel impish $ distro-info --fullname --devel Ubuntu 21.10 "Impish Indri" $ distro-info --release --devel 21.10 $ distro-info --supported bionic focal groovy hirsute impish $ distro-info --date=2021-04-23 --supported bionic focal groovy hirsute impish $ distro-info --fullname --supported Ubuntu 18.04 LTS "Bionic Beaver" Ubuntu 20.04 LTS "Focal Fossa" Ubuntu 20.10 "Groovy Gorilla" Ubuntu 21.04 "Hirsute Hippo" Ubuntu 21.10 "Impish Indri" $ distro-info --release --supported 18.04 LTS 20.04 LTS 20.10 21.04 21.10 $ distro-info --stable hirsute $ distro-info --date=2021-04-23 --stable hirsute $ distro-info --fullname --stable Ubuntu 21.04 "Hirsute Hippo" $ distro-info --release --stable 21.04 ** Tags removed: verification-needed-focal verification-needed-groovy ** Tags added: verification-done-focal 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/1925484 Title: Add Impish Indri To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/1925484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925484] Re: Add Impish Indri
root@lp1925484-x:~# dpkg -l|grep distro-info-data ii distro-info-data 0.28ubuntu0.17 all information about the distributions' releases (data files) root@lp1925484-x:~# for p in devel supported stable; do echo "\$ distro-info --$p"; distro-info --$p; for m in date=2021-04-23 fullname release; do echo "\$ distro-info --$m --$p"; distro-info --$m --$p; done; done $ distro-info --devel impish $ distro-info --date=2021-04-23 --devel impish $ distro-info --fullname --devel Ubuntu 21.10 "Impish Indri" $ distro-info --release --devel 21.10 $ distro-info --supported bionic focal groovy hirsute impish $ distro-info --date=2021-04-23 --supported bionic focal groovy hirsute impish $ distro-info --fullname --supported Ubuntu 18.04 LTS "Bionic Beaver" Ubuntu 20.04 LTS "Focal Fossa" Ubuntu 20.10 "Groovy Gorilla" Ubuntu 21.04 "Hirsute Hippo" Ubuntu 21.10 "Impish Indri" $ distro-info --release --supported 18.04 LTS 20.04 LTS 20.10 21.04 21.10 $ distro-info --stable hirsute $ distro-info --date=2021-04-23 --stable hirsute $ distro-info --fullname --stable Ubuntu 21.04 "Hirsute Hippo" $ distro-info --release --stable 21.04 ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925484 Title: Add Impish Indri To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/1925484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925761] Re: libnns-mymachines update breaks local mdns discovery
> I downgraded systemd to 245.4-ubuntu3 there's a really large delta between that and 245.4-ubuntu3.6, and you very probably were running 245.4-ubuntu3.5 before, not 245.4-ubuntu3. In any case, we'll need more data to look at your problem, can you attach at least your journalctl output from the time when the problem happened ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925761 Title: libnns-mymachines update breaks local mdns discovery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1925761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925987] Re: cornd is not stoped
Sorry, I'm not sure what 'cornd' is, did you possibly mean 'cron'? In any case, you'll need to provide some more info about your problem, like the system logs and/or error messages. ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925987 Title: cornd is not stoped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1925987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926299] [NEW] incorrect sensor is read on Lenovo server BMC
Public bug reported: [impact] ipmi-sensors reads the wrong sensor on a Lenovo BMC (although the problem may happen on other BMCs as well) [test case] run ipmi-sensors over the network using ipmi 1.5 or 2 protocol, and check the sensor output. Specifically for this case, the server is a Lenovo SR665 with only 1 cpu socket populated, and dimms 1-16 are connected to cpu 1 while dimms 17-32 are connected to cpu2, so dimms 17-32 should not return any values. $ ipmi-sensors -u $USERNAME -p $PASSWD -D LAN_2_0 -l USER -h $BMCADDR | grep DIMM | grep Temp 110 | DIMM 1 Temp | Temperature | N/A | C | N/A 113 | DIMM 2 Temp | Temperature | N/A | C | N/A 116 | DIMM 3 Temp | Temperature | N/A | C | N/A 119 | DIMM 4 Temp | Temperature | N/A | C | N/A 122 | DIMM 5 Temp | Temperature | N/A | C | N/A 125 | DIMM 6 Temp | Temperature | N/A | C | N/A 128 | DIMM 7 Temp | Temperature | N/A | C | N/A 131 | DIMM 8 Temp | Temperature | N/A | C | N/A 134 | DIMM 9 Temp | Temperature | 52.00 | C | 'OK' 137 | DIMM 10 Temp | Temperature | 42.00 | C | 'OK' 140 | DIMM 11 Temp | Temperature | N/A | C | N/A 143 | DIMM 12 Temp | Temperature | N/A | C | N/A 146 | DIMM 13 Temp | Temperature | 27.00 | C | 'OK' 149 | DIMM 14 Temp | Temperature | 26.00 | C | 'OK' 152 | DIMM 15 Temp | Temperature | 24.00 | C | 'OK' 155 | DIMM 16 Temp | Temperature | 24.00 | C | 'OK' 158 | DIMM 17 Temp | Temperature | 218.00 | C | 'OK' 161 | DIMM 18 Temp | Temperature | 212.00 | C | 'OK' 165 | DIMM 19 Temp | Temperature | 212.00 | C | 'OK' 173 | DIMM 20 Temp | Temperature | N/A | C | N/A 176 | DIMM 21 Temp | Temperature | N/A | C | N/A 179 | DIMM 22 Temp | Temperature | N/A | C | N/A 182 | DIMM 23 Temp | Temperature | N/A | C | N/A 185 | DIMM 24 Temp | Temperature | N/A | C | N/A 188 | DIMM 25 Temp | Temperature | 0.00 | C | 'At or Below (<=) Lower Non-Critical Threshold' 191 | DIMM 26 Temp | Temperature | 0.00 | C | 'At or Below (<=) Lower Non-Critical Threshold' 194 | DIMM 27 Temp | Temperature | 0.00 | C | 'At or Below (<=) Lower Non-Critical Threshold' 197 | DIMM 28 Temp | Temperature | 0.00 | C | 'At or Below (<=) Lower Non-Critical Threshold' 200 | DIMM 29 Temp | Temperature | 0.00 | C | 'At or Below (<=) Lower Non-Critical Threshold' 203 | DIMM 30 Temp | Temperature | 0.00 | C | 'At or Below (<=) Lower Non-Critical Threshold' 206 | DIMM 31 Temp | Temperature | 0.00 | C | 'At or Below (<=) Lower Non-Critical Threshold' 209 | DIMM 32 Temp | Temperature | N/A | C | N/A [regression potential] any regression would likely result in incorrect values shown for some/all sensor readings [scope] this is not fixed upstream, so it needed in all releases [other info] the problem is that this particular BMC has chosen to use a non-zero 'LUN' number for these sensors; almost all BMCs use the standard LUN number 0, as the spec does state in section 19.3: "Unless otherwise specified, commands that are listed as mandatory must be accessed via LUN 00b" However the spec does allow for implementations to use alternate LUN numbers, specifically section 5.4 describes how the BMC would report the LUN number to the requesting software, and section 7.2 clarifies that while LUN 00b is reserved for devices beloning to the BMC itself and 10b is reserved for SMS messages, LUN numbers 01b and 11b are reserved for 'OEM' use. So it does appear valid for the BMC implementation to place sensor(s) under LUN 01b instead of the default 00b. The cause of the invalid sensor readings in this particular case is because the BMC also defines sensors with the exact same sensor id number, but with LUN 00b. So when freeipmi attempts to read e.g. 'DIMM 17 Temp' sensor, it actually reads the current value for a completely different sensor, which (in this case) isn't even a temperature sensor, resulting in invalid temperature reading shown for the sensor, instead of showing it as N/A (since the DIMM slot isn't populated). Note that ipmitool correctly uses the alternate LUN number so this bug does not exist with that tool, this affects only freeipmi tooling. ** Affects: freeipmi (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/1926299 Title: incorrect sensor is read on Lenovo server BMC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1926299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923115] Re: Networkd vs udev nic renaming race condition
only remaining failed autopkgtests are systemd/i386, which looks like it timed out, and linux-hwe-5.4/i386, which nearly always fails. I started another re-run for systemd/i386 but even if it fails again it seems unlikely the timeout is related to the patch for this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923115 Title: Networkd vs udev nic renaming race condition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925987] Re: crond is not stoped
The screenshot doesn't actually help at all, you'll need to provide actual system logs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925987 Title: crond is not stoped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1925987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925827] Re: [v247] backport routing policy rule fix
thanks, marking verified ** Tags removed: verification-needed verification-needed-hirsute ** Tags added: verification-done verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925827 Title: [v247] backport routing policy rule fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1925827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913421] Re: Load of pre-upgrade qemu modules needs to avoid noexec
> Either as an opt-in or default-on feature. > Both approaches have arguments that speak for them sorry, could you actually list those arguments? Just for clarification > 3. open discussion with the SRU team what the default should be > 3b. If the discussion ends with default off, do we even need to SRU it then? yes, without question. bootstack as well as virtually all people using SRU releases to manage a cloud will need to enable this, if you choose to make it default off. Not having the choice at all doesn't seem like it actually fixes the problem for anyone on SRU releases. Of course as you know my opinion is cloud admins shouldn't need to know about needing to 'enable' this fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913421 Title: Load of pre-upgrade qemu modules needs to avoid noexec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1913421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934981] Re: systemctl suspend-then-hibernate attempts hybrid-sleep instead
** Changed in: systemd (Ubuntu Groovy) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934981 Title: systemctl suspend-then-hibernate attempts hybrid-sleep instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930738] Re: network configuration failed on reboot
can you provide steps to reproduce the problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930738 Title: network configuration failed on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1930738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937089] Re: System76 - systemd and gnome errors, crash with black screen
something appears to have stopped or restarted your dbus service, which will cause widespread problems on the system; you'll need to attach more complete logs for any further debug ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937089 Title: System76 - systemd and gnome errors, crash with black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937117] [NEW] misconfigured networkd may break after networkd restart
Public bug reported: [impact] bug 1929560 fixed an error in setting/clearing an interface 'master' during systemd-networkd startup if the interface was already up, however for any users who have been relying on that bug to manually set an interface 'master' for an interface that's otherwise controlled by systemd-networkd, this will break their system by removing the interface from the 'master' on a systemd-networkd restart. For example, if a user has interface 'eth0' configured to be controlled by systemd-networkd, but then manually does 'ip l set dev eth0 master br0' to add it to the 'br0' bridge, previous behavior would leave 'eth0' in the bridge after a systemd-networkd restart, even though it should not be in the bridge based on the systemd-networkd configuration. The new behavior matches systemd-networkd behavior for all other aspects (i.e. networkd removes all addresses, routes, and other settings it doesn't know about or that are different from its configuration), however it breaks users expecting the previous incorrect behavior. [test case] configure systemd-networkd to control an interface that isn't set with any 'master', and start networkd. For example, an instance configured for DHCP. After networkd has started, manually set the interface 'master' to an existing bridge. Restart networkd, and check if the interface still has the bridge 'master' or not. [regression potential] the main potential is for problems for those with misconfigured systems, relying on specific previous incorrect behavior, specifically interfaces controlled by systemd-networkd in part, but also with manual configuration performed outside of systemd-networkd configuration. [scope] this is needed for bionic and focal to restore the previous incorrect behavior; the correct behavior should remain in impish, and (arguably) should remain in hirsute as well [other info] see bug 1929560 for details of the original bug ** Affects: systemd (Ubuntu) Importance: Undecided Status: Invalid ** Affects: systemd (Ubuntu Bionic) Importance: Critical Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: systemd (Ubuntu Focal) Importance: Critical Assignee: Dan Streetman (ddstreet) Status: In Progress ** Tags: regression-update ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Invalid ** Changed in: systemd (Ubuntu Focal) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => High ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: systemd (Ubuntu Focal) Importance: High => Critical ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Focal) Status: New => In Progress ** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937117 Title: misconfigured networkd may break after networkd restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929560] Re: link mac isn't set if already up
> This backport to 18.04 LTS broke all our OpenStack compute nodes I've opened bug 1937117 to revert this fix, however keep in mind your networkd configuration is incorrect and should be fixed as you will have problems later if you continue to mix systemd-networkd management of interface(s) as well as manual/external configuration of those same systemd-networkd-managed interface(s). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929560 Title: link mac isn't set if already up To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1929560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937117] Re: misconfigured networkd may break after networkd restart
Note that the *proper* way to place eth0 into a bridge while also being under systemd-networkd management is to create a .netdev for the bridge and assign eth0 to it, e.g.: $ cat 10-br0.netdev [NetDev] Name=br0 Kind=bridge cat 10-netplan-eth0.network [Match] Name=eth0 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 Bridge=br0 [DHCP] RouteMetric=100 UseMTU=true Or alternately, just remove the .network file for 'eth0' so it's not under systemd-networkd control, and manually and/or externally control it (i.e. manually bring up eth0 and manually place it into br0). ** Description changed: [impact] bug 1929560 fixed an error in setting/clearing an interface 'master' during systemd-networkd startup if the interface was already up, however for any users who have been relying on that bug to manually set an interface 'master' for an interface that's otherwise controlled by systemd-networkd, this will break their system by removing the interface from the 'master' on a systemd-networkd restart. For example, if a user has interface 'eth0' configured to be controlled by systemd-networkd, but then manually does 'ip l set dev eth0 master br0' to add it to the 'br0' bridge, previous behavior would leave 'eth0' in the bridge after a systemd-networkd restart, even though it should not be in the bridge based on the systemd-networkd configuration. The new behavior matches systemd-networkd behavior for all other aspects (i.e. networkd removes all addresses, routes, and other settings it doesn't know about or that are different from its configuration), however it breaks users expecting the previous incorrect behavior. [test case] configure systemd-networkd to control an interface that isn't set with any 'master', and start networkd. For example, an instance configured for DHCP. After networkd has started, manually set the interface 'master' to an existing bridge. Restart networkd, and check if the interface still has the bridge 'master' or not. + e.g., in a newly created cloud-image container, with normal netplan, + check the networkd control of eth0: + + root@lp1937117-f:~# networkctl list eth0 + IDX LINK TYPE OPERATIONAL SETUP + 159 eth0 ether routableconfigured + + create a new bridge and manually place eth0 into it: + + root@lp1937117-f:~# ip l add dev br0 type bridge + root@lp1937117-f:~# ip l set up dev br0 + root@lp1937117-f:~# ip l set dev eth0 master br0 + root@lp1937117-f:~# ip l show dev eth0 + 159: eth0@if160: mtu 1500 qdisc noqueue master br0 state UP mode DEFAULT group default qlen 1000 + link/ether 00:16:3e:56:f8:07 brd ff:ff:ff:ff:ff:ff link-netnsid 0 + + now restart systemd-networkd, and check if eth0 remains under br0: + + root@lp1937117-f:~# systemctl restart systemd-networkd + root@lp1937117-f:~# ip l show dev eth0 + 159: eth0@if160: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 + link/ether 00:16:3e:56:f8:07 brd ff:ff:ff:ff:ff:ff link-netnsid 0 + + [regression potential] the main potential is for problems for those with misconfigured systems, relying on specific previous incorrect behavior, specifically interfaces controlled by systemd-networkd in part, but also with manual configuration performed outside of systemd-networkd configuration. [scope] this is needed for bionic and focal to restore the previous incorrect behavior; the correct behavior should remain in impish, and (arguably) should remain in hirsute as well [other info] see bug 1929560 for details of the original bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937117 Title: misconfigured networkd may break after networkd restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937117] Re: misconfigured networkd may break after networkd restart
** Patch added: "lp1937117-focal.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937117/+attachment/5512598/+files/lp1937117-focal.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937117 Title: misconfigured networkd may break after networkd restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937117] Re: misconfigured networkd may break after networkd restart
** Patch added: "lp1937117-bionic.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937117/+attachment/5512599/+files/lp1937117-bionic.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937117 Title: misconfigured networkd may break after networkd restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937117] Re: misconfigured networkd may break after networkd restart
Attached debdiffs for b/f. Note that Bionic only needs a revert of the patch for the original bug, but Focal requires the patch revert plus an additional small patch to restore the previous behavior, due to other patches added for bug 1664844. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937117 Title: misconfigured networkd may break after networkd restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929560] Re: link mac isn't set if already up
This fix was reverted for Bionic and Focal, so please note that this bug does still exist in those releases and will not be fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929560 Title: link mac isn't set if already up To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1929560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930738] Re: network configuration failed on reboot
->sealed'
failed at src/libsystemd/sd-netlink/netlink-message.c:582, function
netlink_message_read_internal(). Ignoring.
Sep 10 19:47:23 test-server systemd-networkd[346]: ens3: Could not set
address: Connection timed out
Sep 10 19:47:23 test-server systemd-networkd[346]: ens3: Failed
Sep 10 19:47:23 test-server systemd-networkd[346]: ens3: State changed:
configuring -> failed
Sep 10 19:47:23 test-server systemd-networkd[346]: Sent message type=signal
sender=n/a destination=n/a path=/org/freedesktop/network1/link/_32
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=13
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Sep 10 19:47:23 test-server systemd-networkd[346]: NDISC: Stopping IPv6
Router Solicitation client
```
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Bionic)
Status: New => In Progress
** Changed in: systemd (Ubuntu Focal)
Status: New => In Progress
** Changed in: systemd (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: systemd (Ubuntu Focal)
Importance: Undecided => Low
** Changed in: systemd (Ubuntu Bionic)
Importance: Undecided => Low
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: systemd (Ubuntu Focal)
Assignee: (unassigned) => Dan Streetman (ddstreet)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930738
Title:
network configuration failed on reboot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1930738/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930738] Re: network configuration failed on reboot
ation client ``` ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => New ** Changed in: systemd (Ubuntu Bionic) Assignee: Dan Streetman (ddstreet) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930738 Title: network configuration failed on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1930738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937238] Re: systemd-time-wait-sync.service stuck in "activating" state after boot, blocks timers from starting
This is almost certainly because you don't have the systemd-timesyncd package installed, or you don't have the systemd-timesyncd service enabled. On a very quick glance, it seems the systemd-time-wait-sync service should have been bundled into the systemd-timesyncd package when it was split from the main systemd package, however I'll have to look closer to see if there is some reason it wasn't. ** Description changed: + [impact] + + systemd-time-wait-sync service never completes when systemd-timesyncd + package is not installed + + [test case] + + remove the systemd-timesyncd package and enable the systemd-time-wait- + sync service, and reboot. Check status of the service to see it's stuck + in 'activating' state, e.g.: + + ubuntu@lp1937238-f:~$ sudo systemctl status systemd-time-wait-sync.service + ● systemd-time-wait-sync.service - Wait Until Kernel Time Synchronized + Loaded: loaded (/lib/systemd/system/systemd-time-wait-sync.service; enabled; vendor preset: enabled) + Active: activating (start) since Fri 2021-07-23 15:32:12 UTC; 19s ago + + [regression potential] + + TBD + + [scope] + + this is needed in f and later + + the systemd-timesyncd package was split out from the main systemd + package starting in focal, so this problem exists in f and later + + the service doesn't exist in b, so this is not needed there + + [original description] + When I start my server running Ubuntu 20.04 the systemd-time-wait- sync.service is stuck in "activating" state. I noticed this because none of the systemd timer units triggered, because all the timers depend on systemd-time-wait-sync.service. Running "systemctl restart systemd-time- wait-sync.service" manually works around the problem. Some logs and command outputs: - raek@mizar:~$ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 - raek@mizar:~$ systemctl | grep systemd-time-wait-sync.service - systemd-time-wait-sync.service loaded activating start start Wait Until Kernel Time Synchronized - + systemd-time-wait-sync.service loaded activating start start Wait Until Kernel Time Synchronized raek@mizar:~$ systemctl status systemd-time-wait-sync.service ● systemd-time-wait-sync.service - Wait Until Kernel Time Synchronized - Loaded: loaded (/lib/systemd/system/systemd-time-wait-sync.service; enabled; vendor preset: enabled) - Active: activating (start) since Thu 2021-07-22 11:06:52 CEST; 27min ago -Docs: man:systemd-time-wait-sync.service(8) -Main PID: 514 (systemd-time-wa) - Tasks: 1 (limit: 9415) - Memory: 972.0K - CGroup: /system.slice/systemd-time-wait-sync.service - └─514 /lib/systemd/systemd-time-wait-sync + Loaded: loaded (/lib/systemd/system/systemd-time-wait-sync.service; enabled; vendor preset: enabled) + Active: activating (start) since Thu 2021-07-22 11:06:52 CEST; 27min ago + Docs: man:systemd-time-wait-sync.service(8) + Main PID: 514 (systemd-time-wa) + Tasks: 1 (limit: 9415) + Memory: 972.0K + CGroup: /system.slice/systemd-time-wait-sync.service + └─514 /lib/systemd/systemd-time-wait-sync Jul 22 11:06:52 mizar systemd-time-wait-sync[514]: adjtime state 5 status 40 time Thu 2021-07-22 09:06:52.216338 UTC Warning: journal has been rotated since unit was started, output may be incomplete. - raek@mizar:~$ journalctl -b -u systemd-time-wait-sync.service -- Logs begin at Wed 2020-07-08 16:34:13 CEST, end at Thu 2021-07-22 11:36:44 CEST. -- Jul 22 11:06:52 mizar systemd-time-wait-sync[514]: adjtime state 5 status 40 time Thu 2021-07-22 09:06:52.216338 UTC - raek@mizar:~$ dpkg -S /lib/systemd/system/systemd-time-wait-sync.service systemd: /lib/systemd/system/systemd-time-wait-sync.service - raek@mizar:~$ apt-cache policy systemd systemd: - Installed: 245.4-4ubuntu3.11 - Candidate: 245.4-4ubuntu3.11 - Version table: - *** 245.4-4ubuntu3.11 500 - 500 http://se.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages - 100 /var/lib/dpkg/status - 245.4-4ubuntu3.10 500 - 500 http://se.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages - 245.4-4ubuntu3.8 400 - 400 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages - 245.4-4ubuntu3 500 - 500 http://se.archive.ubuntu.com/ubuntu focal/main amd64 Packages + Installed: 245.4-4ubuntu3.11 + Candidate: 245.4-4ubuntu3.11 + Version table: + *** 245.4-4ubuntu3.11 500 + 500 http://se.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages + 100 /var/lib/dpkg/status + 245.4-4ubuntu3.10 500 + 500 http://se.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages + 245.4-4ubuntu3.8 400
[Bug 1927161] Re: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one
multiple patches shouldn't ever be cat'ed into a single file; that is awful. One patch file per actual patch. This fails because quilt allows fuzz, while dpkg-source doesn't, and it shouldn't. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927161 Title: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937953] Re: systemd forcibly disables use of dummy/bond interfaces
> because configuration in /lib/modprobe.d/ overrides configuration in /etc/modprobe.d/ well, not quite. kmod reads files from the dirs in this order: /run/modprobe.d/ /etc/modprobe.d/ /lib/modprobe.d/ any duplicate files, with the exact same name in multiple directories, will ignore the same-named file from later dirs (e.g. as you noticed, /etc/modprobe.d/systemd.conf will override /lib/modprobe.d/systemd.conf). However, once all files are loaded and duplicates removed/ignored, kmod will process the files in lexical - i.e. alphabetical, using strcmp() - order. Since your filename 'local-dummy.conf' is lexically before 'systemd.conf', its content is processed before the content in systemd.conf; thus, your setting is replaced[1]. If you rename your file to any (unique) filename that's lexically *after* systemd.conf, your setting will be used, not the setting in the 'systemd.conf' file. Is that obvious? No. In the man page? Not that I see, and it probably should be, but that should be discussed with upstream for kmod. (1) - note that your setting isn't actually being *replaced*, what modprobe is doing is *appending* each new module option. So when your file is lexically before systemd.conf, what's happening is actually: $ sudo modprobe -v dummy insmod /lib/modules/5.4.0-77-generic/kernel/drivers/net/dummy.ko numdummies=0 $ ip l show dummy0 Device "dummy0" does not exist. $ sudo rmmod dummy $ echo "options dummy numdummies=1" | sudo tee /etc/modprobe.d/a.conf options dummy numdummies=1 $ sudo modprobe -v dummy insmod /lib/modules/5.4.0-77-generic/kernel/drivers/net/dummy.ko numdummies=1 numdummies=0 $ ip l show dummy0 Device "dummy0" does not exist. $ sudo rmmod dummy $ sudo mv /etc/modprobe.d/a.conf /etc/modprobe.d/z.conf $ sudo modprobe -v dummy insmod /lib/modules/5.4.0-77-generic/kernel/drivers/net/dummy.ko numdummies=0 numdummies=1 $ ip l show dummy0 216: dummy0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether f6:25:71:17:bb:ae brd ff:ff:ff:ff:ff:ff $ sudo rmmod dummy $ sudo rm /etc/modprobe.d/z.conf $ sudo modprobe -v dummy insmod /lib/modules/5.4.0-77-generic/kernel/drivers/net/dummy.ko numdummies=0 $ ip l show dummy0 Device "dummy0" does not exist. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937953 Title: systemd forcibly disables use of dummy/bond interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
