[Touch-packages] [Bug 1918955] Re: SRU network: fix LXC_NET_NONE cleanup

Marking this fix-released in focal as bug 1923232 was released to focal. So this should be fixed in '1:4.0.6-0ubuntu1~20.04.1'. ** Changed in: lxc (Ubuntu Focal) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1707222] Re: usage of /tmp during boot is not safe due to systemd-tmpfiles-clean

Norman, Thanks for the comment. On first pass, it looks like you've diagnosed a failure correctly. Please open another bug and add output of 'cloud-init collect-logs'. thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1923232] Re: SRU of LXC 4.0.6 to focal (upstream bugfix release)

lxc auto package tests show green for 4.0.6-0ubuntu1 other than i386, which failed previously. * amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lxc/20210525_040935_c4b64@/log.gz * arm64:

[Touch-packages] [Bug 1918955] Re: SRU network: fix LXC_NET_NONE cleanup

** Description changed: Hi. I'm using 20.04, and I need a fix for https://github.com/lxc/lxc/pull/3589 I think my only options to get that via packaging are  a.) https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/lxc-git-master  b.) build my own. I don't love either of those

[Touch-packages] [Bug 1918955] Re: SRU network: fix LXC_NET_NONE cleanup

Just fwi, this is in 4.0.6 which is up for SRU in LP: #1923232. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1918955 Title: SRU network: fix LXC_NET_NONE cleanup Status in

[Touch-packages] [Bug 1923232] Re: SRU of LXC 4.0.6 to focal (upstream bugfix release)

This would fix LP: #1918955. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1923232 Title: SRU of LXC 4.0.6 to focal (upstream bugfix release) Status in lxc package in

[Touch-packages] [Bug 1918955] Re: SRU network: fix LXC_NET_NONE cleanup

** Description changed: Hi. I'm using 20.04, and I need a fix for https://github.com/lxc/lxc/pull/3589 - I think my only options to get that via packaging are - a.) https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/lxc-git-master - b.) build my own. + I think my only options to get

[Touch-packages] [Bug 1918955] [NEW] SRU network: fix LXC_NET_NONE cleanup

Public bug reported: Hi. I'm using 20.04, and I need a fix for https://github.com/lxc/lxc/pull/3589 I think my only options to get that via packaging are a.) https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/lxc-git-master b.) build my own. I don't love either of those options. Can we

[Touch-packages] [Bug 1693900] Re: apt-get update should return exit code != 0 on error

For reference, ubuntu-devel post about '-o APT::Update::Error-Mode=any' at https://lists.ubuntu.com/archives/ubuntu-devel/2021-February/041374.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu.

[Touch-packages] [Bug 1825155] Re: lxc-start crashed with SIGSEGV in cgfsng_payload_create()

I bumped into this yesterday on bionic. The commit 1e04bb71da3ed829 [1] reports to fix it. [1] https://github.com/lxc/lxc/commit/1e04bb71da3ed829761ae8c729c3d021a6a709df Hopefully there will be a 3.0.x update to bionic at some point. ** Also affects: lxc (Ubuntu Focal) Importance: Medium

[Touch-packages] [Bug 1834875] Re: cloud-init growpart race with udev

this seemed to "just work" for me. http://paste.ubuntu.com/p/93dWDPZfZT/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1834875 Title: cloud-init growpart race with udev

[Touch-packages] [Bug 1834875] Re: cloud-init growpart race with udev

a.) I gave the wrong link. ugh. It should have been: https://code.launchpad.net/~smoser/cloud-initramfs-tools/+git/cloud-initramfs-tools/+merge/379774 b.) the fixed link to 'a' probably makes more sense now. But basically you need a newer cloud-initramfs-tools to adjust for the fact that

[Touch-packages] [Bug 1834875] Re: cloud-init growpart race with udev

The fix is in cloud-utils upstream now. Still to do: a.) review/merge cloud-initramfs-tools pull request https://code.launchpad.net/~raharper/cloud-utils/+git/cloud-utils/+merge/379177 b.) upload cloud-initramfs-tools to focal c.) upload cloud-utils to focal d.) any SRU the order of 'b'

[Touch-packages] [Bug 1834875] Re: cloud-init growpart race with udev

** Changed in: cloud-initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1834875 Title: cloud-init growpart race with

[Touch-packages] [Bug 1834875] Re: cloud-init growpart race with udev

** Merge proposal linked: https://code.launchpad.net/~raharper/cloud-utils/+git/cloud-utils/+merge/379177 ** Changed in: cloud-utils Status: New => Fix Committed ** Also affects: cloud-utils (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-utils (Ubuntu)

[Touch-packages] [Bug 1856560] Re: ds-identify - stuck in uninterruptible sleep state

> If someone manually installs Ubuntu Desktop / Server using an installer, > one should not be installing or using cloud-init as clearly, it will never > complete without a correct metadata source present. And when it fails to > complete, it re-attempts to reprovision the machine on every boot.

[Touch-packages] [Bug 1834875] Re: cloud-init growpart race with udev

> > So that means we have this sequence of events: > > a.) growpart change partition table > > b.) growpart call partx > > c.) udev created and events being processed > That is not true. whilst sfdisk is deleting, creating, finishing > partition table (a) and partx is called (b), udev events

[Touch-packages] [Bug 1834875] Re: cloud-init growpart race with udev

I really think you are all *way* over thinking this. a. growpart made a change to the partition table (using sfdisk) b. growpart called partx --update --nr 3 /dev/sda c. growpart exited With a and b growpart created udev events. If you create udev events, you really need to wait for those

[Touch-packages] [Bug 1779156] Re: lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy'

best. fix. ever. working after a reboot. $ snap list lxd Name Version RevTracking Publisher Notes lxd 3.18 12211 stablecanonical✓ - -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu.

[Touch-packages] [Bug 1834875] Re: cloud-init growpart race with udev

If there is a race, or a need to wait, it almost certainly is in cloud- utils (growpart). If you use growpart to grow a partition, the result should be that that is done, and it is ready. The caller should not expect that they have to know additional information (to call 'udevadm settle') or

[Touch-packages] [Bug 1834875] Re: cloud-init growpart race with udev

** Also affects: cloud-utils Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1834875 Title: cloud-init growpart race with udev

[Touch-packages] [Bug 1831258] Re: journalctl --list-boots does not recognize boots in a container

Filed issue with lxcfs at https://github.com/lxc/lxcfs/issues/285 ** Bug watch added: LXCFS bug tracker #285 https://github.com/lxc/lxcfs/issues/285 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1831258] [NEW] journalctl --list-boots does not recognize boots in a container

Public bug reported: $ lxc launch ubuntu-daily:eoan devel1 $ sleep 10 # wait for boot $ lxc exec devel1 /bin/bash root@devel1:~# cat /proc/uptime 183.00 173.00 root@devel1:~# cat /etc/cloud/build.info build_name: server serial: 20190531 root@devel1:~# lsb_release -sc eoan root@devel1:~#

[Touch-packages] [Bug 1723390] Re: lxd containers have become degraded

Quite a pleasent surprise I found today. $ lxc launch ubuntu-daily:devel devel1 $ sleep 20 $ lxc exec devel1 systemctl status | grep State State: running $ lxc exec devel1 -- sh -c 'cat /etc/cloud/build.info; lsb_release -sc' build_name: server serial: 20190531 eoan $ lxc exec devel1 --

[Touch-packages] [Bug 1809027] Re: Make retired Ubuntu keyrings available from the archive

The easiest thing to do would be to just ship a keyring that had the obsolete public signing keys. Then the consumer could hard code that 'precise' was signed with keys A, B, C. and work stuff out like that. Alternatively possibly we might want to deliver some distro-info like data.

[Touch-packages] [Bug 1576353] Re: Install openssh-server with disabled password auth by default on servers

@Adam, > See the comment on the linked debian-cd MP from Marc Deslauriers. Note > that the goal of removing the cloud-image seed is still entirely > reasonable and doable, openssh-server should just move to livecd-rootfs > as something always added to cloud images. Done and done. There's no Your

[Touch-packages] [Bug 1795410] [NEW] cannot bring up window menu via keybinding (alt-space or otherwise)

Public bug reported: I'm accustomed to hitting 'alt-space' to 'Activate the window menu' where there are options like 'Always on Top' or 'Always on visible workspace'. After an upgrade today I can no longer bring up that menu. Alt-space simply does nothing. Configuring the keyboard shortcut in

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

Hm... Our tests show that this is not fixed in cosmic or bionic. https://jenkins.ubuntu.com/server/job/curtin-vmtest-devel-amd64/533/console shows curtin's vmtest failing. Partial output shows: == ERROR:

[Touch-packages] [Bug 1134036] Re: Failure when using ssh with a locale that is not configured on the server

** Changed in: maas (Ubuntu Bionic) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1134036 Title: Failure when using ssh with a locale

Re: [Touch-packages] [Bug 1788188] Re: transient systemd ordering cycle in boot with overlayroot

@xnox, Are you suggesting the /media/root-ro entry in /etc/fstab line for /media/root-ro should have x-systemd.DefaultDependencies=no ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1792168] Re: ifupdown hotplug dhcp fails due to udevadm RestrictAddressFamilies

This is invalid. It actually all still works because: udev hook /lib/udev/rules.d/80-ifupdown.rules calls /lib/udev/ifupdown-hotplug which calls systemctl --no-block start $(systemd-escape --template ifup@.service $INTERFACE) Then the ifup@.service is what actually brings up the device.

[Touch-packages] [Bug 1792168] [NEW] ifupdown hotplug dhcp fails due to udevadm RestrictAddressFamilies

Public bug reported: I haven't verified this, but I believe that ifupdown works through udevadm hooks. So udevadm hotplug event -> ifup eth0. Any subprocesses of a udevadm hook will be restricted by the systemd-udevd.service restrictions, which currently are RestrictAddressFamilies=AF_UNIX

[Touch-packages] [Bug 1788188] Re: transient systemd ordering cycle in boot with overlayroot

I uploaded open-iscsi_2.0.874-5ubuntu8 which has the debug code that we were toying with included. It also includes a fix for FTBFS bug 1791154. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1788188] Re: transient systemd ordering cycle in boot with overlayroot

I've hit that 'retrigger' button 2 more times and have not seen failures. I just did again. Don't know what to do. :-( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1788188

[Touch-packages] [Bug 1788188] Re: transient systemd ordering cycle in boot with overlayroot

here is a pastebin of boot with systemd debugging. http://paste.ubuntu.com/p/vGTRh6WB3B/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1788188 Title: transient systemd

[Touch-packages] [Bug 1788188] Re: transient systemd ordering cycle in boot with overlayroot

I pushed a branch up to https://code.launchpad.net/~smoser/ubuntu/+source/open-iscsi/+git/open-iscsi/+ref/bug/1788188-debug that Christian and I are trying to get some additional debug information out of a failure. -- You received this bug notification because you are a member of Ubuntu Touch

[Touch-packages] [Bug 1788188] [NEW] transient systemd ordering cycle in boot with overlayroot

Public bug reported: open-iscsi test utilizes overlayroot to boot a cloud-image with root filesystem on a read-only iscsi server. The /etc/fstab file in the image looks like this:   LABEL=cloudimg-rootfs /ext4 defaults0 0   #LABEL=UEFI /boot/efi vfatdefaults

[Touch-packages] [Bug 1134036] Re: Failure when using ssh with a locale that is not configured on the server

@mwhudson, your suggested change seems reasonable to me. I don't love the use of 'eval', but it seems reasonably safe here. Instead of quoting you could just reject argv[1] input if it had characters other than [a-zA-z_.-] . Perhaps that makes this more difficult. Also, maybe you should try to

[Touch-packages] [Bug 1785683] [NEW] dep8 tests fail on non-intel

** Changed in: software-properties (Ubuntu) Assignee: (unassigned) => Scott Moser (smoser) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1785683 Title: d

[Touch-packages] [Bug 1667725] Re: [feature request] make full ppa signing public key available over https

** Changed in: software-properties (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1667725 Title: [feature request]

[Touch-packages] [Bug 1667725] Re: [feature request] make full ppa signing public key available over https

** Also affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1724623] Re: Update ubuntu cloud info

cloud-init can collect relevant logs with 'cloud-init collect-logs' that is what we tell people to run (and what gets done with 'ubuntu-bug cloud-init'). I know that is not exactly what you're after. -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1732028] Re: timeout in iscsi boot fail with overlayroot [open-iscsi autopkg tests on LP Infra]

i attached as reference https://hackmd.io/E0ydu7Y7QEe-kroPb6-OOA at some point we can improve the doc in the debian/tests directory with that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1732028] Re: timeout in iscsi boot fail with overlayroot [open-iscsi autopkg tests on LP Infra]

** Description changed: This issue keeps cropping up. It shows itself in open-iscsi autopkg tests. I think it might just be "really slow system". It seems the timeout is only - 1 minute 30 seconds for the disk to appear, and in a happy run you +  1 minute 30 seconds for the disk to appear,

[Touch-packages] [Bug 1779302] Re: should retry reading key from keyserver (in _recv_key)

I saw this "in the wild" with /var/log/cloud-init.log showing: 2018-07-09 15:20:22,666 - util.py[DEBUG]: Running command ['add-apt-repository', 'cloud-archive:ocata'] with allowed return codes [0] (shell=False, capture=True) 2018-07-09 15:20:24,907 - cc_apt_configure.py[ERROR]:

[Touch-packages] [Bug 1779302] [NEW] should retry reading key from keyserver (in _recv_key)

Public bug reported: Some recent events have made keyservers less reliable than they were previously:   https://bitbucket.org/skskeyserver/sks-keyserver/issues/57   https://bitbucket.org/skskeyserver/sks-keyserver/issues/60 We have seen a greatly increased failure rate of retreiving keys

[Touch-packages] [Bug 1749722] Re: NTP: take into account systemd-timesyncd where present

This bug is believed to be fixed in cloud-init in version 18.3. If this is still a problem for you, please make a comment and set the state back to New Thank you. ** Changed in: cloud-init Status: Fix Committed => Fix Released -- You received this bug notification because you are a

[Touch-packages] [Bug 1709603] Re: apt {upgrade, install, source} require an update call first

Just a comment... 'apt' indicates that its cli is unstable and should not be relied upon by scripts. So fixing this general problem in 'apt' (and not apt-get) means you fix it possibly for humans who are typing things, but all non-human package installations needlessly have to 'apt-get update'.

[Touch-packages] [Bug 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.

** Description changed: With trusty, /bin/ping relies on having extended attributes and kernel capabilities to gain the cap_net_raw+p capability. This allows removing the suid bit. However, the tarball cloud images do not preserve the extended attributes, and thus /bin/ping does not

[Touch-packages] [Bug 1302192] Re: capabilities not preserved on installation

** Description changed: Ping is not longer setuid root and I have to ping as root: [~]$ ping kubuntu.org ping: icmp open socket: Operation not permitted [~]$ sudo ping kubuntu.org PING kubuntu.org (91.189.94.156) 56(84) bytes of data. 64 bytes from vostok.canonical.com

[Touch-packages] [Bug 1774458] Re: ubuntu-bug produces links that do not work

I think this was user-error... I think the serial console was just messing with me. I'll re-open if I see it again. ** Changed in: apport (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed

[Touch-packages] [Bug 1774458] [NEW] ubuntu-bug produces links that do not work

Public bug reported: ubuntu-bug is now producing links that do not work. using 'ubuntu-bug' in xenial produces links that look like: https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/0f274d36-64f2-11e8-b34a-002481e7f48a? but the cosmic version produces links like:

[Touch-packages] [Bug 1630946] Re: ubuntu-server depends on open-iscsi and runs iscsid

** Description changed: 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

[Touch-packages] [Bug 1630946] Re: ubuntu-server depends on open-iscsi and runs iscsid

@Christian, Well, the intended goal is that ubuntu-server == cloud-image. we did fairly significant work to get as close as we are. Currently cloud-image [1] differs from ubuntu-server [2] only by presense of cloud-init and openssh-server. The goal was to ultimately drop those also, and

[Touch-packages] [Bug 1759307] Re: missing dependency on isc-dhcp-client (dhclient)

Ugh. the merge proposal at https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/342214 put a build-depends on isc-dhcp-client not a runtime depends. i've opened bug 1766714 to address. -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1762438] Re: stack trace when filing bug (ubuntu-bug systemd)

This was a stock lxc launch. $ lxc launch ubuntu-daily:bionic b4 $ lxc exec b4 /bin/bash root@b4:~# cat /etc/cloud/build.info build_name: server serial: 20180411 root@b4:~# ubuntu-bug systemd *** Collecting problem information The collected information can be sent to the developers to

[Touch-packages] [Bug 1749722] Re: NTP: take into account systemd-timesyncd where present

An upstream commit landed for this bug. To view that commit see the following URL: https://git.launchpad.net/cloud-init/commit/?id=c6dff581 ** Changed in: cloud-init Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch

[Touch-packages] [Bug 1762438] [NEW] stack trace when filing bug (ubuntu-bug systemd)

Public bug reported: # ubuntu-bug systemd *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .ERROR: hook /usr/share/apport/package-hooks/systemd.py crashed: Traceback (most recent call

[Touch-packages] [Bug 1723390] Re: lxd containers have become degraded

root@b3:~# systemctl --no-pager | grep failed ● sys-kernel-config.mount loaded failed failedKernel Configuration File System ● systemd-hostnamed.serviceloaded failed failedHostname Service ●

[Touch-packages] [Bug 1759307] Re: missing dependency on isc-dhcp-client (dhclient)

"Packages that care about networking support in the initramfs should instead take care themselves to depend on isc-dhcp-client." Reworded: Packages that care about should take care to depend on themselves. Generally that's not how things work, and results in maintenance elsewhere. Now

Re: [Touch-packages] [Bug 1759307] Re: missing dependency on isc-dhcp-client (dhclient)

You don't think that at least warrants a Suggests ? On Wed, Mar 28, 2018 at 2:49 AM, Steve Langasek < steve.langa...@canonical.com> wrote: > I don't think this belongs as a dependency of initramfs-tools. The > initramfs-tools package won't fail to create an initramfs if dhclient is > absent,

[Touch-packages] [Bug 1759307] Re: missing dependency on isc-dhcp-client (dhclient)

An upstream commit landed for this bug. To view that commit see the following URL: https://git.launchpad.net/cloud-init/commit/?id=5b9dc4bc -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.

[Touch-packages] [Bug 1633643] Re: unnecessary dependency upon isc-dhcp-client

Related bug 1759307 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1633643 Title: unnecessary dependency upon isc-dhcp-client Status in initramfs-tools package

[Touch-packages] [Bug 1759307] Re: missing dependency on isc-dhcp-client (dhclient)

** Description changed: - cloud-init uses isc-dhcp-client (through 'dhclient') to obtain temporary dhcp ip addresses. - it currently does not identify a dependency on it. + cloud-init uses isc-dhcp-client (through 'dhclient') to obtain temporary + dhcp ip addresses. It currently does not

Re: [Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives

Joseph, Thanks for providing the link to the mailing list post. That is very helpful. On Fri, Mar 23, 2018 at 4:15 PM, Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > SRU request submitted: > https://lists.ubuntu.com/archives/kernel-team/2018-March/090976.html > > -- > You received

[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives

An upstream commit landed for this bug. To view that commit see the following URL: https://git.launchpad.net/curtin/commit/?id=bd40234f -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu.

[Touch-packages] [Bug 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu

See my attached log for verification of artful. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1734167 Title: DNS doesn't work in no-cloud as launched by ubuntu Status

[Touch-packages] [Bug 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu

** Attachment added: "verification log on artful" https://bugs.launchpad.net/cloud-init/+bug/1734167/+attachment/5081507/+files/lp-1734167-verify-artful.txt ** Tags removed: verification-needed verification-needed-artful ** Tags added: verification-done verification-done-artful -- You

[Touch-packages] [Bug 1751797] Re: NetworkManager incorrectly uses resolved' route-only DNS setting, resulting in dns resolution only working for domains in 'search'.

** Changed in: network-manager (Ubuntu) Importance: Undecided => Critical -- 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/1751797 Title: NetworkManager

[Touch-packages] [Bug 1751797] Re: dns resolution only works for domains in 'search'.

connection.id: System Ethernet connection.uuid:72c7fac3-c017-4b76-9954-b4fb08262376 connection.stable-id: -- connection.type:802-3-ethernet connection.interface-name: -- connection.autoconnect:

[Touch-packages] [Bug 1751797] Re: dns resolution only works for domains in 'search'.

$ systemd-resolve --status enp0s25 Link 2 (enp0s25) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 10.7.0.1 fdfd::::1 DNS Domain: ~mydomain.com $ cat

[Touch-packages] [Bug 1751797] Re: dns resolution only works for domains in 'search'.

** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1751797 Title: dns resolution only

[Touch-packages] [Bug 1714308] Re: dns does not work in initramfs after configure_networking

** Merge proposal unlinked: https://code.launchpad.net/~smoser/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/341203 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.

[Touch-packages] [Bug 1713803] Re: replacement of resolvconf with systemd needs integration

** Merge proposal linked: https://code.launchpad.net/~smoser/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/341203 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu.

[Touch-packages] [Bug 1714308] Re: dns does not work in initramfs after configure_networking

** Merge proposal linked: https://code.launchpad.net/~smoser/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/341203 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.

[Touch-packages] [Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

** No longer affects: maas ** No longer affects: nplan (Ubuntu) ** No longer affects: systemd (Ubuntu) ** Changed in: cloud-init Status: New => Confirmed ** Changed in: cloud-init Importance: Undecided => Medium ** Changed in: cloud-init Assignee: (unassigned) => Ryan Harper

Re: [Touch-packages] [Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

I'm pretty sure that if you you rm /etc/resolv.conf and then just write what ever you want in there, it wont get overritten. mv /etc/resolv.conf /etc/resolv.conf.dist echo "nameserver 8.8.8.8" > /etc/resolv.conf On Thu, Mar 8, 2018 at 4:36 PM, Mike Pontillo wrote:

[Touch-packages] [Bug 972077] Re: apt repository disk format has race conditions

Hi. Just to re-iterate what Robie said. If you are seeing hashsum mismatch errors on 16.04 or later, something is wrong. That could be: a.) you have a proxy in your way, and the proxy cached a bad download. Apt is recognizing this and not installing it. That is working as designed. Note, that

[Touch-packages] [Bug 1751797] Re: dns resolution only works for domains in 'search'.

** Changed in: systemd (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1751797 Title: dns resolution only works for domains

[Touch-packages] [Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

Currently maas sends v1 config to cloud-init. cloud-init converts that to netplan. MAAS could certainly change change to either a.) improve the v1 config that it sends to put dns as per-interface b.) send v2 config with dns per-interface. I don't think there is reason to justify either of those

[Touch-packages] [Bug 1750780] Re: Race with local file systems can make open-vm-tools fail to start

I agree with reverting change in bionic, and that xenial still needs some fix. I recreated your failure in xenial and agree with your change there. I used this job as it actually tries to write to the private tmp. If I change 'ExecStart' below to be just '/bin/true' like in your job, it does

[Touch-packages] [Bug 1751797] Re: dns resolution only works for domains in 'search'.

** Description changed: After reboot, dns was broken. + This is a very simple Network Manager managed interface that has dhcp. + + $ nmcli device show enp0s25 | pastebinit + http://paste.ubuntu.com/p/sMVTdrMBxJ/ + + I've attached systemd-resolve --status output. In order to file the

[Touch-packages] [Bug 1732028] Re: transient boot fail with overlayroot [open-iscsi dep8 tests]

** Summary changed: - transient boot fail with overlayroot + transient boot fail with overlayroot [open-iscsi dep8 tests] ** Attachment added: "bionic failure log 2.0.874-5ubuntu2 qemu/1:2.11+dfsg-1ubuntu2"

[Touch-packages] [Bug 1751797] [NEW] dns resolution only works for domains in 'search'.

Public bug reported: After reboot, dns was broken. I've attached systemd-resolve --status output. In order to file the bug I just modified /etc/resolv.conf to put the dns server in directly. Other information, it seems like it just will only look for dns under my search domains from the dhcp

[Touch-packages] [Bug 1751797] Re: dns resolution only works for domains in 'search'.

I had hoped that simply disconnect/reconnect of the interface would work, but that did not improve things. (nmcli device disconnect enp0s25 ; nmcli device connect enp0s25) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1750031] Re: scary/unexpected output in adduser and deluser

I've also tried a bionic azure image $ cat /etc/cloud/build.info build_name: server serial: 20180222 It did not reproduce there. So as far as I can tell it shows itself only on Azure 16.04 images. ** Also affects: cloud-images Importance: Undecided Status: New ** Changed in:

[Touch-packages] [Bug 1750031] Re: scary/unexpected output in adduser and deluser

This bug was reproduced on a xenial Azure cloud image $ cat /etc/cloud/build.info build_name: server serial: 20180222 I cannot reproduce it locally in a container. ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1750031] Re: scary/unexpected output in adduser and deluser

** Tags removed: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/1750031 Title: scary/unexpected output in adduser and deluser Status in adduser package in Ubuntu:

[Touch-packages] [Bug 1750851] Re: re-add cloud-initramfs-dyn-netconf to ubuntu-server

cloud-images 20180222 do *not* have cloud-initramfs-dyn-netconf or ubuntu-meta at 1.411. That is expected as it just wasnt fixed at the time of the build. Anything newer than 20180222 should have this fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

Getting this fixed in cloud-init is tricky. In ifupdown (/etc/network/interfaces) world, we just took the "global dns" entries and put them on the loopback device (lo). Since that device would always be brought up, and never really brought down, it served its purpose. That is what Ryan tried

[Touch-packages] [Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

It seems to me that each of maas, cloud-init and netplan could do better here. a.) maas declares 'global' nameserver/dns info. this is kind of silly in that such a thing doesn't really exist. maas has the information necessary to declare the nameserver on the device with the address that has a

[Touch-packages] [Bug 1750851] Re: re-add cloud-initramfs-dyn-netconf to ubuntu-server

Marked as 'fix-committed' as I pushed to the seed branch. I need to wait for some server side things to happen before I can upload ubuntu-meta, but any ubuntu-meta > 1.411 should have this fix. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Fix Committed ** Changed in: ubuntu-meta

[Touch-packages] [Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

MAAS is sending a "global" nameserver, and a ethernet device on a bridge. cloud-init is rendering that nameserver onto the ethernet device rather than on the bridge or as a "global" entry. $ cat my.yaml network: config: [ {"id": "enp0s25", "type": "physical", "name": "enp0s25",

[Touch-packages] [Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

Hi, cloud-init has never updated resolv.conf directly. /etc/resolv.conf in 16.04 is managed via resolvconf through /etc/network/interfaces. /etc/resolv.conf in 18.04 is managed via systemd-resolve (netplan -> systemd-networkd -> systemd-resolve). Can you provide the content of:

[Touch-packages] [Bug 1750851] [NEW] re-add cloud-initramfs-dyn-netconf to ubuntu-server

Public bug reported: I (smoser) removed cloud-initramfs-dyn-netconf from ubuntu-server meta package. That package provides functionality needed by MAAS and cause bug 1748875. Under that bug we re-added cloud-initramfs-dyn-netconf to the initramfs that MAAS publishes. We subsequently saw

[Touch-packages] [Bug 1749222] Re: apport-collect requires python2

Based on Brian's comment, marking wont-fix. Not the end of the world, just less than ideal. ** Changed in: apport (Ubuntu Xenial) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport

[Touch-packages] [Bug 1750031] [NEW] scary/unexpected output in adduser and deluser

Public bug reported: adduser and deluser are now printing to stderr 'sent invalidate(passwd)' and 'sent invalidate(group)'. These are confusing at best and new in bionic. See below. They do not seem harmful, but not wonderful. smoser@ubuntu1:~$ sudo adduser guest Adding user `guest' ... sent

[Touch-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

** Description changed: 1. $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 2. $ apt-cache policy linux-image-`uname -r` linux-image-4.13.0-16-generic: - Installed: 4.13.0-16.19 - Candidate: 4.13.0-16.19 - Version table: - *** 4.13.0-16.19 500 - 500

[Touch-packages] [Bug 1749222] Re: apport-collect requires python2

** Summary changed: - apport-collect requires python2 or suggests installing already-installed python3-apport + apport-collect requires python2 ** Changed in: apport (Ubuntu) Status: New => Fix Released ** Changed in: apport (Ubuntu) Importance: Undecided => Medium ** Also affects:

  1   2   3   4   5   6   >