[Bug 1968782] [NEW] CHROOT_SESSION_PURGE is set to false without union-type, so 90apt-sources does not render

2022-04-12 Thread Scott Moser
Public bug reported: I'm not sure if this is incorrect behavior in schroot or incorrect assumption in sbuild-launchpad-chroot. I have a system where I was not able to use union, so the focal-amd64 config that was built by sbuild-launchpad-chroot looks like below. When attempting to build from

[Bug 1859506] Re: swtpm fails in focal with apparor

2022-02-22 Thread Scott Moser
** Summary changed: - swtmp fails in focal with apparor + swtpm fails in focal with apparor -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859506 Title: swtpm fails in focal with apparor To

[Bug 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi

2022-02-17 Thread Scott Moser
@Noah, cloud-init isn't doing anything wrong. Its working as designed. 'growroot', which is provided by cloud-initramfs-tools (upstream [1], package [2]) also didn't do anything wrong. It's sole purpose in the initramfs is to do what it is doing. I'm not sure what code creates the image you've

[Bug 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi

2022-02-16 Thread Scott Moser
> I thought cloud-initramfs-growroot was solely used with old kernels that > can't resize mounted > filesystems but I could be wrong. Wondering though why we install that > package all of a sudden. that is another option, to remove cloud-initramfs-growroot from the image/initrd. The problem

[Bug 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi

2022-02-16 Thread Scott Moser
@Noah, The image you pointed at there has the package 'cloud-initramfs-growroot' in its initramfs. cloud-initramfs-growroot is going to run growpart on the root filesystem during the initramfs unless one of the following files exists on the root filesystem: /var/lib/cloud/instance/root-grown

[Bug 1959324] Re: sbuild-launchpad-chroot does not notice tar extract failures

2022-01-27 Thread Scott Moser
** Also affects: sbuild-launchpad-chroot (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: sbuild-launchpad-chroot (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1959324] [NEW] sbuild-launchpad-chroot does not notice tar extract failures

2022-01-27 Thread Scott Moser
Public bug reported: Nothing is checking exit code of tar when the downloaded tarball is extracted. Tar could fail for many reasons including permission or filesystem full. If tar failed, sbuild-launchpad-chroot would just continue on. The user would likely fail in a less obvious way later on.

[Bug 1784713] Re: cloud-init profile.d files use bash-specific builtin "local"

2021-08-23 Thread Scott Moser
@Eli, I can recreate your problem, but it looks to me like a bug in ksh. ksh complains that 'local can only be used in a function, when as shown below it *is* being used in a function.' My suggestion is to file a bug with ksh2020. root@focal1:~# ksh -c 'foo() { local a=1; echo $?; }; foo' ksh:

[Bug 1940711] [NEW] sign-efi-sig-list uses PKCS7 for variable updates

2021-08-20 Thread Scott Moser
Public bug reported: When building some software (https://github.com/puzzleos/uefi-dev) I ran into a problem/bug in efitools 'sign-efi-sig-list'. The end result in my case was that an attempt to update the PK variable in uefi (ovmf files from 20.04 with qemu from 20.04) resulted in an exit code

[Bug 1918955] Re: SRU network: fix LXC_NET_NONE cleanup

2021-06-23 Thread Scott Moser
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 Bugs, which is

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

2021-06-17 Thread Scott Moser
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 Bugs, which is subscribed to Ubuntu.

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

2021-06-14 Thread Scott Moser
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:

[Bug 1918955] Re: SRU network: fix LXC_NET_NONE cleanup

2021-06-14 Thread Scott Moser
** 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

[Bug 1918955] Re: SRU network: fix LXC_NET_NONE cleanup

2021-06-09 Thread Scott Moser
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918955 Title: SRU network: fix LXC_NET_NONE cleanup To manage notifications about

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

2021-06-09 Thread Scott Moser
This would fix LP: #1918955. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923232 Title: SRU of LXC 4.0.6 to focal (upstream bugfix release) To manage notifications about this bug go to:

[Bug 1918955] Re: SRU network: fix LXC_NET_NONE cleanup

2021-03-12 Thread Scott Moser
** 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

[Bug 1918955] [NEW] SRU network: fix LXC_NET_NONE cleanup

2021-03-12 Thread Scott Moser
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

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

2021-02-18 Thread Scott Moser
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 Bugs, which is subscribed to Ubuntu.

[Bug 1906187] Re: Version tag is not respected when put last

2021-01-19 Thread Scott Moser
** Description changed: I've created a 'network-config' file with Terraform's yamldecode() function that contains (btw. I've tried with the version being a Number w/o quotes and as well as a String as shown here): --- "network": - "ethernets": - "eth0": - "gateway4":

[Bug 1798117] Re: juju sends "network" top level key to user.network-config in lxd containers

2020-12-08 Thread Scott Moser
The change made here seems to be having fallout at https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1906187 ** Description changed: == Short summary == - In lxd containers launched by juju, + In lxd containers launched by juju, /var/lib/cloud/seed/nocloud-net/network-config has: -

[Bug 1473527] Re: module ssh-authkey-fingerprints fails Input/output error: /dev/console

2020-10-30 Thread Scott Moser
There are a slew of bugs and apparently random fallout of /dev/console not working. In my opinion, its really *not* helpful to just ignore that 'write' to stdout fails. Ignoring errors is never really a solution. In this case, cloud-init may have specifically opened /dev/console. But in

[Bug 1885527] Re: cloud-init regenerating ssh-keys

2020-10-29 Thread Scott Moser
** Also affects: cloud-init Importance: Undecided Status: New ** Changed in: cloud-init Status: New => Fix Committed ** Changed in: cloud-init Importance: Undecided => Medium ** Changed in: cloud-init Assignee: (unassigned) => Markus Schade (lp-markusschade) -- You

[Bug 1885527] Re: cloud-init regenerating ssh-keys

2020-10-26 Thread Scott Moser
@Markus, Can you please provide a link to documentation showing that? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885527 Title: cloud-init regenerating ssh-keys To manage notifications about

[Bug 1892447] Re: Why ignore new name server if 3 name servers exists

2020-10-21 Thread Scott Moser
I set back to 'New', Pengpeng's comment does make sense. cloudinit/net/sysconfig.py's render_network_state calls _render_dns. _render_dns then will load the existing file if it is present. So the end result is that if we have a "stale" version of /etc/resolv.conf on the system, then the dns

[Bug 1493188] Re: "overlayfs" no longer exists

2020-09-14 Thread Scott Moser
** Description changed: === Begin SRU Template === [Impact] The 16.10 kernel dropped a legacy kernel module alias that allowed usage of the 'overlay' filesystem via name 'overlayfs'. This broke overlayroot as it explicitly tried to to use 'overlayfs' by name in loading of modules and

[Bug 1888858] Re: document manual_cache_clean better

2020-09-08 Thread Scott Moser
https://github.com/canonical/cloud-init/pull/568 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/158 Title: document manual_cache_clean better To manage notifications about this bug go to:

[Bug 1888858] Re: document manual_cache_clean better

2020-09-01 Thread Scott Moser
** Description changed: LP: #1885527 raised (not for the first time) a general failure of cloud-init's documentation to cover 'manual_cache_clean'. In fact, this configuration value not referenced at all in readthedocs, but only in - doc/examples/cloud-config.txt -

[Bug 1893064] Re: sru cloud-init (20.2-45 to 20.3-0) Xenial, Bionic, and Focal

2020-08-26 Thread Scott Moser
** Changed in: cloud-init (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893064 Title: sru cloud-init (20.2-45 to 20.3-0) Xenial, Bionic, and Focal To

[Bug 1892879] Re: python-ubuntutools package is empty.

2020-08-26 Thread Scott Moser
See bug https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev- tools/+bug/1864571 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892879 Title: python-ubuntutools package is empty. To manage

[Bug 1864571] Re: SRU ubuntu-dev-tools

2020-08-25 Thread Scott Moser
I'm pretty sure this change caused bug 1892879 also. basically, the python-ubuntudevtools package is empty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864571 Title: SRU ubuntu-dev-tools To

[Bug 1892879] [NEW] python-ubuntutools package is empty.

2020-08-25 Thread Scott Moser
Public bug reported: The python-ubuntutools package is empty. root@b1:~# dpkg -L python-ubuntutools /. /usr /usr/share /usr/share/doc /usr/share/doc/python-ubuntutools /usr/share/doc/python-ubuntutools/NEWS.Debian.gz /usr/share/doc/python-ubuntutools/changelog.gz

[Bug 1872163] Re: focal chroots broken due to change in sources.list

2020-08-18 Thread Scott Moser
Verification log of focal. Note 2 things: a.) recent update to the test script b.) if you look closely at the log you'll see '91smoser-schroot-setup' output. That is from https://gist.github.com/smoser/14df5f0cd621e10d2282d7c90345e322 It should not affect the verification of this bug. **

[Bug 1872163] Re: focal chroots broken due to change in sources.list

2020-08-18 Thread Scott Moser
** Attachment added: "updated test - adds user, not root to sbuild" https://bugs.launchpad.net/ubuntu/+source/sbuild-launchpad-chroot/+bug/1872163/+attachment/5402546/+files/test-sbuild-launchpad-chroot -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1872163] Re: focal chroots broken due to change in sources.list

2020-08-18 Thread Scott Moser
** Tags removed: verification-needed-focal ** Tags added: 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/1872163 Title: focal chroots broken due to change in sources.list To

[Bug 1225922] Re: Support static network configuration even on already configured devices

2020-08-18 Thread Scott Moser
I'm going to mark this fix-released. The general bug as described in the description is that cloud-init can't correctly apply networking for all interfaces. cloud-init local applies networking configuration to the system, and should apply before the system brings networking up. Thus appearing

[Bug 1890803] Re: Groovy amd64 / arm64 / PowerPC deployment seems not working

2020-08-17 Thread Scott Moser
[ubuntu/groovy-proposed] cloud-initramfs-tools 0.47ubuntu1 (Accepted) ^ landed Ryan's fix (comment #38 mp 389422) ** Merge proposal linked: https://code.launchpad.net/~raharper/cloud-initramfs-tools/+git/cloud-initramfs-tools/+merge/389422 -- You received this bug notification because you

Re: [Bug 1890803] Re: Groovy amd64 / arm64 / PowerPC deployment seems not working

2020-08-14 Thread Scott Moser
@Rod I wouldn't bother until you see an image with serial greater than 20200813. If it doesn't have cloud-initramfs-tools > 0.45ubuntu1, its not going to work with groovy. then test that and complain with logs if its not working. On Fri, Aug 14, 2020 at 1:15 PM Rod Smith

[Bug 1890803] Re: Groovy amd64 / arm64 / PowerPC deployment seems not working

2020-08-14 Thread Scott Moser
t; Fix Released ** Changed in: cloud-initramfs-tools (Ubuntu) Assignee: (unassigned) => Scott Moser (smoser) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890803 Title: Groovy amd6

[Bug 1873368] Re: ssshuttle server fails to connect endpoints with python 3.8

2020-07-29 Thread Scott Moser
@Eric, William, I think you're taking a very narrow view on this when a more thoughtful review is needed. Ubuntu should identify a general policy on 'client <-> server' version backwards and forwards compatibility guarantees. That policy should be implemented here. The fact this particular

[Bug 1873368] Re: ssshuttle server fails to connect endpoints with python 3.8

2020-07-27 Thread Scott Moser
@Eric, Well... We'd only be carring the change for 20.04. I would not suggest to carry it for 20.10 or beyond. As my change is right now I dont' think I would accept it for upstream. It should be sufficient for a stable release though. I really suspect that if upstream cared about python <

[Bug 1873368] Re: ssshuttle server fails to connect endpoints with python 3.8

2020-07-24 Thread Scott Moser
@all, Please review a MP at https://code.launchpad.net/~smoser/ubuntu/+source/sshuttle/+git/sshuttle/+merge/388062 that will fix this for focal -> trusty and keep focal -> focal working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1873368] Re: ssshuttle server fails to connect endpoints with python 3.8

2020-07-24 Thread Scott Moser
@Lukasz sshuttle does not require itself to be installed on the server. Rather it "pushes" itself from the client to the server. So the code that executes on client is the same as that on the server. Maybe the table below will help: client | server | comment trusty | focal | broken due to

[Bug 1873368] Re: ssshuttle server fails to connect endpoints with python 3.8

2020-07-24 Thread Scott Moser
** Merge proposal linked: https://code.launchpad.net/~smoser/ubuntu/+source/sshuttle/+git/sshuttle/+merge/388062 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873368 Title: ssshuttle server

[Bug 1885527] Re: cloud-init regenerating ssh-keys

2020-07-24 Thread Scott Moser
I opened bug 158 to request better documentation on this feature. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885527 Title: cloud-init regenerating ssh-keys To manage notifications about

[Bug 1888858] [NEW] document manual_cache_clean better

2020-07-24 Thread Scott Moser
Public bug reported: LP: #1885527 raised (not for the first time) a general failure of cloud-init's documentation to cover 'manual_cache_clean'. In fact, this configuration value not referenced at all in readthedocs, but only in doc/examples/cloud-config.txt

[Bug 1885527] Re: cloud-init regenerating ssh-keys

2020-07-24 Thread Scott Moser
@Daniel, > One convenience we could potentially provide: if cloud-init had a way > for image creators to express "when next launched, cloud-init should > treat that instance ID as immutable and permanent" (in a way that could > be undone on subsequent boots, if a user wants to "unfreeze" an

[Bug 1873368] Re: ssshuttle server fails to connect endpoints with python 3.8

2020-07-23 Thread Scott Moser
@William, The fix here does break python < 3.5 (as advertised in the debian/patches/ patch). It is mostly trivial to make this change in a backwards compatible way, so we should probably do that. I wonder what the official policy is on breaking this "client"s interaction with an ubuntu release

[Bug 1491148] Re: growpart doesn't work with mdraid devices

2020-07-16 Thread Scott Moser
** Changed in: cloud-utils (Ubuntu) Assignee: Scott Moser (smoser) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491148 Title: growpart doesn't work with mdraid devi

[Bug 1491148] Re: growpart doesn't work with mdraid devices

2020-07-15 Thread Scott Moser
** Changed in: cloud-utils (Ubuntu) Status: In Progress => Confirmed ** Changed in: cloud-utils (Ubuntu Eoan) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1873368] Re: ssshuttle server fails to connect endpoints with python 3.8

2020-07-14 Thread Scott Moser
@Felipe, Two things I think should be changed in your debdiff: a.) version should be 0.78.5-1ubuntu0.1 instead of 0.78.5-1ubuntu1 per https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging . I'm not certain on that though. b.) the referenced commit (9c873579) is not the

[Bug 1873368] Re: ssshuttle server fails to connect endpoints with python 3.8

2020-07-10 Thread Scott Moser
@slashd, Are you suggesting your 'A' (version 1.0.2) for focal? Unless there are other reasons than this bug, that feels like not the right path for SRU. So that means 'B' is the path forward for focal. So I might suggest just doing 'B' for groovy now (adding ubuntu delta). That would then

[Bug 1885527] Re: cloud-init regenerating ssh-keys

2020-07-02 Thread Scott Moser
@Valery, Some cloud platforms provide the instance id via some non-network channel (dmi data is common). In those cases, cloud-init will check cached value versus the locally-available instance-id before looking for a network available datasource. So, if Hetzner provides that information in

[Bug 1885527] Re: cloud-init regenerating ssh-keys

2020-07-01 Thread Scott Moser
"AGAIN: Why is cloud-init still manipulating the machine *after* initialization and first boot?" Because cloud-init thinks it is a "first boot". A supported use case for cloud-init is: * boot instance on cloud * ssh in * install some packages, prep this instance * stop instance * snapshot

[Bug 1885527] Re: cloud-init regenerating ssh-keys

2020-06-30 Thread Scott Moser
after replying with collected logs, please set the status back to 'new'. thanks for taking the time to file a bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885527 Title: cloud-init

[Bug 1885527] Re: cloud-init regenerating ssh-keys

2020-06-30 Thread Scott Moser
Hi, please attach the output of 'cloud-init collect-logs' when run on a system that demonstrates the problem. cloud-init uses the "instance-id" from the metadata service to indicate a new instance. Some things run once per instance, some things run once per boot. ** Changed in: cloud-init

[Bug 1463072] Re: highlighting on left mouse double click ends at : (colon)

2020-06-08 Thread Scott Moser
this worked for me to set all profiles as I wanted in 20.04 $ val='@ms

[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available

2020-06-03 Thread Scott Moser
@Guilherme, Simply returning non-error (0) in one function in the initramfs isn't going to solve the problem. Anything that is checking the return value of a write() to its stdout will fail. That could be a shell 'echo', it could be a C write(). In order to take that path completion, you'd

[Bug 1796137] Re: huge and slow image 20181002 due to seeded lxd snap

2020-06-01 Thread Scott Moser
@stgraber, The bug subject says "Huge and slow". Shame on me to make 1 bug for 2 issues. But wrt "is this fixed", groovy images are still dramatically bigger *and* slower to boot than bionic images. a.) Huge. Still looks much bigger, 'Huge' can obviously be argued. 346M for current groovy

[Bug 1880704] Re: jump in kernel clock during boot on azure

2020-05-27 Thread Scott Moser
@Anh Vo, Thanks for looking at this. It almost seemed too perfect for me to believe the pre-provisioning stuff kicked in, and that there were exactly zero journal entries in almost 9 days. I would think it'd be nice for cloud-init to clearly state "pre- provisioned system waited X seconds" or

[Bug 1880704] Re: jump in kernel clock during boot on azure

2020-05-26 Thread Scott Moser
In my head there are a few possibilities here: a.) azure correctly guessed that I was going to launch an instance and "pre-provisioned" it a week before I did it. this seems unlikely to me for a number of reasons, but I could be convinced that if this happened, everything is working as

[Bug 1880704] [NEW] jump in kernel clock during boot on azure

2020-05-26 Thread Scott Moser
Public bug reported: I launched a new instance on azure and noticed that it had 'uptime' of 8 days. Debugging a bit with Odd_Bloke in #cloud-init, it certainly seems that it is around the time when timesync ran: $ journalctl -o short-monotonic -u systemd-timesyncd.service --no-pager -- Logs

[Bug 1691772] Re: provide a way to seed NoCloud from network without image modification.

2020-05-20 Thread Scott Moser
** Description changed: === Begin SRU Template === [Impact] In bug 1660385, we made imitating the EC2 datasource more difficult. By design, that broke some users or platforms who have done so in the past. The change here gives users who were using the Ubuntu images in a low-tech

[Bug 1872163] Re: focal chroots broken due to change in sources.list

2020-05-11 Thread Scott Moser
** Description changed: + - Begin SRU info - + [Impact] + Users of sbuild-launchpad-chroot cannot use chroots created with + sbuild-launchpad-chroot with a build-release of focal or groovy. + An attempt to do so fails during 'apt-get update' as the + /etc/apt/sources.list file that is

[Bug 1876139] Re: Groovy cloud-images failing during growpart

2020-05-11 Thread Scott Moser
** Changed in: cloud-init Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876139 Title: Groovy cloud-images failing during growpart To manage notifications

[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available

2020-05-11 Thread Scott Moser
@wgh, My experience is that it is unfortunately not that simple. It may have worked for you. At the point in which it starts to fail, it repeatedly will fail. But up until some point, writes to stdout work fine. I believe this is because there is a buffer and it only begins failing when it has

[Bug 1872163] Re: focal chroots broken due to change in sources.list

2020-05-08 Thread Scott Moser
** Also affects: sbuild-launchpad-chroot (Ubuntu Groovy) Importance: Undecided Status: Confirmed ** Also affects: sbuild-launchpad-chroot (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: sbuild-launchpad-chroot (Ubuntu Bionic) Importance: Undecided

[Bug 1872163] Re: focal chroots broken due to change in sources.list

2020-05-07 Thread Scott Moser
** Merge proposal linked: https://code.launchpad.net/~smoser/ubuntu/+source/sbuild-launchpad-chroot/+git/sbuild-launchpad-chroot/+merge/383600 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872163

[Bug 1573095] Re: Cloud images fail to boot when a serial port is not available

2020-05-07 Thread Scott Moser
The real fix here is kernel improvement (or bug fix if you want to consider current kernel behavior a bug). Anything else is just going to push around the failure. That is what was determined in 2013, and its probably still true how.

[Bug 1876139] Re: Groovy cloud-images failing during growpart

2020-05-06 Thread Scott Moser
** Changed in: cloud-utils Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876139 Title: Groovy cloud-images failing during growpart To manage

[Bug 1876139] Re: Groovy cloud-images failing during growpart

2020-05-05 Thread Scott Moser
https://code.launchpad.net/~smoser/cloud-utils/+git/cloud-utils/+merge/383431 Merge proposal to upstream cloud-utils ^ ** Also affects: cloud-utils Importance: Undecided Status: New ** Changed in: cloud-utils Status: New => Confirmed ** Changed in: cloud-utils Importance:

[Bug 1876139] Re: Groovy cloud-images failing during growpart

2020-05-05 Thread Scott Moser
I realize this is probably just seen as noise. But I think its important that everyone here understand. Growpart supports using either fdisk or gdisk. But I have recently considered deleting the gdisk support. I'm curious why fdisk is seen as "an old package". fdisk/sfdisk supports GPT

[Bug 1876139] Re: Groovy cloud-images failing during growpart

2020-04-30 Thread Scott Moser
independent of how sfdisk gets into a cloud-image, cloud-utils should identify its dependency. Something like https://paste.ubuntu.com/p/Fzwkm2PgqF/ ** Also affects: cloud-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member

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

2020-04-22 Thread Scott Moser
@Markus, Please open a bug against cloud-initramfs-growroot and reference it here (and reference this bug there). Please also provide a full console log. fwiw, generally speaking cloud-initramfs-growroot has not been necessary since at least 14.04, quite possibly even beefore. -- You received

[Bug 1718761] Re: It's not possible to use OverlayFS (mount -t overlay) to stack directories on a ZFS volume

2020-04-20 Thread Scott Moser
I hit this today, and filed bug 1873917 before dupe'ing it to this. I'd think that the main pain points are a.) using overlay in a container that is backed by zfs via lxd b.) using overlay when using zfs root (https://didrocks.fr/2019/10/11/ubuntu-zfs-support-in-19.10-zfs-on-root/) I attached a

[Bug 1873917] Re: zfs not supported as upperdir or workdir for overlay mount

2020-04-20 Thread Scott Moser
*** This bug is a duplicate of bug 1718761 *** https://bugs.launchpad.net/bugs/1718761 ** This bug has been marked a duplicate of bug 1718761 It's not possible to use OverlayFS (mount -t overlay) to stack directories on a ZFS volume -- You received this bug notification because you are

[Bug 1873917] [NEW] zfs not supported as upperdir or workdir for overlay mount

2020-04-20 Thread Scott Moser
Public bug reported: zfs cannot be used as a filesystem for an overlay mount's 'upperdir' or 'workdir' arguement. If you have zfs root, or are inside an lxd that uses zfs then you'll not be able to use overlay mounts without working around this bug. It can be worked around by using a tmpfs. $

[Bug 1872163] Re: focal chroots broken due to change in sources.list

2020-04-17 Thread Scott Moser
(updated from the comment) A workaround patch changing 90apt-sources. ** Patch added: "fix/workaround" https://bugs.launchpad.net/ubuntu/+source/sbuild-launchpad-chroot/+bug/1872163/+attachment/5356285/+files/fix-1872163.diff -- You received this bug notification because you are a member

[Bug 1872163] Re: focal chroots broken due to change in sources.list

2020-04-17 Thread Scott Moser
Here is *a* fix/workaround that I'd expect to work for existing releases and focal $ diff -u /etc/schroot/setup.d/90apt-sources.dist /etc/schroot/setup.d/90apt-sources --- /etc/schroot/setup.d/90apt-sources.dist 2020-04-17 14:26:50.510749407 -0400 +++ /etc/schroot/setup.d/90apt-sources

[Bug 1873507] [NEW] 90apt-sources breaks sources.list in focal builds

2020-04-17 Thread Scott Moser
*** This bug is a duplicate of bug 1872163 *** https://bugs.launchpad.net/bugs/1872163 Public bug reported: the file '/etc/schroot/setup.d/90apt-sources' attempts to enable 'APT_POCKETS' (release, security, updates, proposed). It attempts to change the existing /etc/apt/sources.list.

[Bug 1870346] Re: Wifi configuration

2020-04-03 Thread Scott Moser
In case it wasn't clear above... I don't personally believe that specifying "renderer" should be required or even allowed. Its a hack. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870346 Title:

[Bug 1870346] Re: Wifi configuration

2020-04-03 Thread Scott Moser
In my opinion, the provider of network configuration to an instance (image) should not have to "know" that the image uses networkd, NetworkManager, ifupdown, wikid They just declare "make the networking like this". The operating system inside implements API. Anything else just cannot work.

Re: [Bug 1866563] Re: cloud-init expects sshd service to be available in images should be in the package deps

2020-03-26 Thread Scott Moser
It seems really like this is Recommends. Its not a hard depends. On Mon, Mar 9, 2020 at 2:55 PM Ryan Harper <1866...@bugs.launchpad.net> wrote: > > In particular, user passed in cloud-config for augmenting ssh > configuration in the guest (setting user ssh keys) however, it was > unknown that

Re: [Bug 1868077] Re: A new feature in cloud-init identified possible datasources for this system as:['Ec2', 'None']. However, the datasource used was: Azure

2020-03-23 Thread Scott Moser
@Mohammed, Thank you for your help. I dont think we need anything else from you. Scott On Mon, Mar 23, 2020 at 2:10 PM Mohammed Sameer B <1868...@bugs.launchpad.net> wrote: > > @Scott, > > So shall I consider the issue fixed or still some troubleshooting needs > to be done? > > > Thanks > > -- >

[Bug 1868077] Re: A new feature in cloud-init identified possible datasources for this system as:['Ec2', 'None']. However, the datasource used was: Azure

2020-03-23 Thread Scott Moser
@Mohammed, I was hoping for /var/lib/cloud contents *before* running 'cloud-init clean'. The other logs look fine. @Other cloud-init devs, I'd like someone else to hazard a guess at what went on here. The general issue is: * very old cloud-init (0.7.9) booted on azure * migrated to ec2,

Re: [Bug 1868077] Re: A new feature in cloud-init identified possible datasources for this system as:['Ec2', 'None']. However, the datasource used was: Azure

2020-03-21 Thread Scott Moser
It really seem slike you still have /var/lib/waagent around. See lines in your log like: 2020-03-21 07:36:37,988 - stages.py[DEBUG]: restored from checked cache:ataSourceAzure [seed=/var/lib/waagent] For reference, could youp lease attach: tar -C /var/lib/ -cvf var-lib-cloud.tar.gz cloud/

[Bug 1868077] Re: A new feature in cloud-init identified possible datasources for this system as:['Ec2', 'None']. However, the datasource used was: Azure

2020-03-20 Thread Scott Moser
@Mohammed, the cloud-init.log clearly shows cloud-init still using the Azure datasource due to the presense of /var/lib/waagent I would suggest removing that directory. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

Re: [Bug 1868077] Re: A new feature in cloud-init identified possible datasources for this system as:['Ec2', 'None']. However, the datasource used was: Azure

2020-03-20 Thread Scott Moser
I'd suggest making the changes, and inserting a ssh key that you have access to into root. Then reboot and see what happens. You should then be able to log in and debug a bit, run 'cloud-init collect-logs' and post here. On Fri, Mar 20, 2020 at 10:20 AM Mohammed Sameer B

[Bug 1868077] Re: A new feature in cloud-init identified possible datasources for this system as:['Ec2', 'None']. However, the datasource used was: Azure

2020-03-20 Thread Scott Moser
@Mohammed, If you are using an EBS root, then you can detach the volume and attach to another instance and then collect logs from it. I might suggest that you make a snapshot, then change the volume to and add an ssh key to root's ssh keys and then re-attach that volume to the original instance

[Bug 1868077] Re: A new feature in cloud-init identified possible datasources for this system as:['Ec2', 'None']. However, the datasource used was: Azure

2020-03-19 Thread Scott Moser
@Mohammed, I would do a 'rm -Rf /var/lib/waagent' before migrating future images. And I'd suggest that you can probably just 'touch /var/lib/cloud/instance/warnings/.skip'. But your system is in a wierd state. @Cloud-init devs, What happened here was: a.) instance booted on Azure b.)

[Bug 1868077] Re: A new feature in cloud-init identified possible datasources for this system as:['Ec2', 'None']. However, the datasource used was: Azure

2020-03-19 Thread Scott Moser
Hi Mohammed, Please attach the output of 'cloud-init collect-logs' and then set this back to New. Thanks. ** Changed in: cloud-init (Ubuntu) Status: New => Incomplete ** Tags added: dsid -- You received this bug notification because you are a member of Ubuntu Bugs, which is

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

2020-03-10 Thread Scott Moser
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

[Bug 1866563] Re: cloud-init expects sshd service to be available in images should be in the package deps

2020-03-09 Thread Scott Moser
It'd also be sane to just *not* depend on sshd. cloud-init doesn't really depend on sshd to my knowledge, but probably does throw some warnings or not function perfectly if its not there. nothing about cloud-init should require sshd though. it'd be good to run without it. -- You received this

[Bug 1864107] Re: ssh-import-id broken on Focal

2020-02-28 Thread Scott Moser
** Changed in: ssh-import-id Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864107 Title: ssh-import-id broken on Focal To manage notifications about

[Bug 1864107] Re: ssh-import-id broken on Focal

2020-02-28 Thread Scott Moser
** Changed in: ssh-import-id Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864107 Title: ssh-import-id broken on Focal To manage notifications about this bug go

[Bug 1864107] Re: ssh-import-id broken on Focal

2020-02-25 Thread Scott Moser
** Changed in: ssh-import-id Status: New => Confirmed ** Changed in: ssh-import-id Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: ssh-import-id Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs,

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

2020-02-25 Thread Scott Moser
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834875 Title: cloud-init growpart race with udev To manage notifications

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

2020-02-25 Thread Scott Moser
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

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

2020-02-24 Thread Scott Moser
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'

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

2020-02-24 Thread Scott Moser
** Changed in: cloud-initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834875 Title: cloud-init growpart race with udev To manage

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

2020-02-24 Thread Scott Moser
** 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)

  1   2   3   4   5   6   7   8   9   10   >