I note that the issue *doesn't* occur with 23.10 (which has systemd
253.5), tested using an lxd VM:
$ lxc launch --vm images:ubuntu/23.10/cloud mythic
$ lxc shell mythic
# apt-get install systemd-container
...
# machinectl pull-raw
Grr... it works if I first run a dummy command within the machine:
systemd-nspawn -M jammy-rootfs --as-pid2 passwd root
machinectl start jammy-rootfs # it's working now!
machinectl login jammy-rootfs
(Even just "echo hello world" does the job)
However if you go back to a *fresh* image then
** Description changed:
Two-line reproducer: run this on an Ubuntu 22.04 server.
sudo machinectl pull-raw
http://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64.img
jammy-rootfs
sudo machinectl start jammy-rootfs
Response:
Job for
Public bug reported:
Two-line reproducer: run this on an Ubuntu 22.04 server.
sudo machinectl pull-raw
http://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64.img
jammy-rootfs
sudo machinectl start jammy-rootfs
Response:
Job for systemd-nspawn@jammy-rootfs.service failed
This module is now present in Ubuntu 22.04, so this issue can be closed.
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS"
$ dpkg-query -L rsyslog | grep pmciscoios
/usr/lib/x86_64-linux-gnu/rsyslog/pmciscoios.so
--
*** This bug is a duplicate of bug 1641236 ***
https://bugs.launchpad.net/bugs/1641236
The duplicate status of this bug is still wrong.
A workaround has been provided at
https://github.com/lxc/lxd/issues/2930#issuecomment-1418752618
Inside the container:
### Ubuntu 18.04, 20.04
echo
I got the same error, also going via apt-cacher-ng:
$ sudo apt-get update
Hit:1 http://gb.archive.ubuntu.com/ubuntu jammy InRelease
Get:2 http://gb.archive.ubuntu.com/ubuntu jammy-updates InRelease [114 kB]
Get:3 http://gb.archive.ubuntu.com/ubuntu jammy-backports InRelease [99.8 kB]
Hit:4
Public bug reported:
rsyslog has a parser module for Cisco IOS formatted syslog messages:
https://www.rsyslog.com/doc/master/configuration/modules/pmciscoios.html
https://github.com/rsyslog/rsyslog/tree/master/plugins/pmciscoios
It has been in rsyslog since early days (8.3.4); Bionic has 8.16.0.
*** This bug is a duplicate of bug 1641236 ***
https://bugs.launchpad.net/bugs/1641236
I believe this bug has been wrongly marked as a duplicate of #1641236.
I described in the second paragraph of the bug report why this is *not*
a duplicate.
#1641236 is when lxc exec passes an open pty from
Awesome, thanks again!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1630946
Title:
ubuntu-server depends on open-iscsi and runs iscsid
Status in ubuntu-meta
> no matter if we succeed/fail there one can at least later remove open-
iscsid if he wants without taking out the ubuntu-server meta.
That's perfect - thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta
Workaround:
systemctl stop iscsid
systemctl disable iscsid
... but I still object to not being able to remove it without also
removing ubuntu-server.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
Just doing an "apt-get dist-upgrade" on a 16.04 VM:
...
Setting up grub-common (2.02~beta2-36ubuntu3.11) ...
Installing new version of config file /etc/grub.d/10_linux ...
update-rc.d: warning: start and stop actions are no longer supported; falling
back to defaults
Setting up grub-pc-bin
I guess this also makes 1.8.16-0ubuntu1.3 a "security" update, since
sudo+sssd now enforces policy which it should have done before, but
didn't.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
I found out how to enable debugging for sudoers:
Debug sudo /var/log/sudo-debug all@info
Debug sudoers.so /var/log/sudoers-debug all@info
With the *new* sudo I get the following logged matching 'sssd':
May 5 12:40:06 sudo[17912] sssd/ldap sudoHost 'ALL' ... MATCH!
May 5 12:40:06 sudo[17912]
Now trying with @debug instead of @info
Slight munging of output to make it diffable, then diff -u:
--- v1.debug.trim 2017-05-03 20:28:07.78400 +
+++ v2.debug.trim 2017-05-03 20:28:14.03200 +
@@ -38,87 +38,6 @@
-> parse_args @
Some additional info.
I enabled sudo debugging by creating /etc/sudo.conf containing:
Debug sudo /var/log/sudo-debug all@info
Debug sudoers /var/log/sudoers-debug all@info
With the newer (non-functioning) sudo, /var/log/sudo-debug contains:
May 3 18:55:50 sudo[8003] comparing dev 34817 to
Public bug reported:
ubuntu 16.04, enrolled with freeipa-client to FreeIPA 4.4.0 (under
CentOS 7)
With sudo 1.8.16-0ubuntu1, everything is fine:
brian.candler@api-dev:~$ sudo -s
[sudo] password for brian.candler:
root@api-dev:~#
After update to 1.8.16-0ubuntu1.3, it no longer works:
WORKAROUND: if the other application which needs to bind to a UDP port
can be configured to bind to a specific interface, then you can make
isc-dhcp-server bind to a different interface in dhcpd.conf. e.g.
ddns-local-address4 127.0.0.1;
ddns-local-address6 ::1;
--
You received this bug
strace shows that dhcpd is binding to explicit ports which it has chosen
itself:
setsockopt(20, SOL_SOCKET, SO_TIMESTAMP, [1], 4) = 0
setsockopt(20, SOL_IP, IP_MTU_DISCOVER, [0], 4) = 0
getsockopt(20, SOL_SOCKET, SO_RCVBUF, [212992], [4]) = 0
setsockopt(20, SOL_IP, IP_RECVTOS, [1], 4) = 0
Public bug reported:
When isc-dhcp-server starts up, in addition to listening on port 67, it
binds to a random UDP port on an IPv4 socket and another on an IPv6
socket:
# netstat -naup | grep dhcp
udp0 0 0.0.0.0:11075 0.0.0.0:*
8188/dhcpd
udp
Public bug reported:
[ubuntu 16.04, lxd 2.0.8 or 2.0.9, tcpdump 4.7.4 or 4.9.0]
If you ssh into an lxd container as a normal user, and inside that
container run "sudo tcpdump", the tcpdump process is blocked from
writing to stdout/stderr. This appears to be due to apparmor:
disabling apparmor
Workaround is to use IPv4/NAT networking instead of link-local
IPv6/http_proxy.
1. configure your lxdbr0 network with (private) IPv4 addresses and DHCP
pool in /etc/default/lxd-bridge. Also set LXD_IPV4_NAT="true" and
LXD_IPV6_PROXY="false". Restart.
2. "lxc profile edit default" to no longer
Public bug reported:
ubuntu-server has a hard dependency on open-iscsi, which means there is
a daemon running (iscsid), and the package cannot be removed. All
unnecessary daemons are a cause of concern when auditing a system.
Propose moving this to "Recommends" instead, which currently has:
I have two Precise (12.04) servers with
Unattended-Upgrade::Remove-Unused-Dependencies "true";
in 50unattended-upgrades. One of them cleans up its kernels and only
keeps the last two; one of them accumulates kernels over time, and I
occasionally get alerts about /boot filling up.
On the latter
The second issue (not matching predictable NIC names) is #1541678
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1519120
Title:
NetworkManager VLAN support fails
*** This bug is a duplicate of bug 1566930 ***
https://bugs.launchpad.net/bugs/1566930
** This bug has been marked a duplicate of bug 1566930
wget does not support IPv6 address with scoped zone (RFC 4007)
--
You received this bug notification because you are a member of Ubuntu
Touch
This is still an issue with xenial.
The problem this causes is that on an Ubuntu Server system, installing
any package which depends on openssh-client will also pull in pretty
much the whole X11 system. Example:
root@xenial1:~# apt-get install rancid
Reading package lists... Done
Building
Public bug reported:
Inside an lxd container with default profile you get this error with
wget:
root@first:~# wget http://nsrc.org/
Error parsing proxy URL http://[fe80::1%eth0]:13128: Invalid IPv6 numeric
address.
root@first:~# echo $http_proxy
http://[fe80::1%eth0]:13128
The underlying
The workaround is fine, but if you want more detailed description about the
underlying issues (there are more than one) see the Red Hat bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1026430
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Workaround confirmed: console stays on tty1, and the shutdown messages
are shown there. Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1342856
Title:
No
31 matches
Mail list logo
