[Bug 1831772] Re: sru curtin 2019-06-05 - 19.1-7-g37a7a0f4-0ubuntu1
Disco vmtest artifacts ** Attachment added: "Disco vmtest artifacts" https://bugs.launchpad.net/curtin/+bug/1831772/+attachment/5275688/+files/curtin-vmtest-proposed-d-artifacts.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831772 Title: sru curtin 2019-06-05 - 19.1-7-g37a7a0f4-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1831772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831772] Re: sru curtin 2019-06-05 - 19.1-7-g37a7a0f4-0ubuntu1
Cosmic vmtest console log from rerunning tests that timed out. ** Attachment added: "Cosmic vmtest console log from rerunning tests that timed out." https://bugs.launchpad.net/curtin/+bug/1831772/+attachment/5275687/+files/curtin-vmtest-proposed-c-diglett-console.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831772 Title: sru curtin 2019-06-05 - 19.1-7-g37a7a0f4-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1831772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831772] Re: sru curtin 2019-06-05 - 19.1-7-g37a7a0f4-0ubuntu1
Bionic vmtest artifacts from repeating tests that timed out. ** Attachment added: "Bionic vmtest artifacts from repeating tests that timed out." https://bugs.launchpad.net/curtin/+bug/1831772/+attachment/5275680/+files/curtin-vmtest-proposed-b-diglett-artifacts.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831772 Title: sru curtin 2019-06-05 - 19.1-7-g37a7a0f4-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1831772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831772] Re: sru curtin 2019-06-05 - 19.1-7-g37a7a0f4-0ubuntu1
Cosmic vmtest artifacts ** Attachment added: "Cosmic vmtest artifacts" https://bugs.launchpad.net/curtin/+bug/1831772/+attachment/5275684/+files/curtin-vmtest-proposed-c-artifacts.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831772 Title: sru curtin 2019-06-05 - 19.1-7-g37a7a0f4-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1831772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831772] Re: sru curtin 2019-06-05 - 19.1-7-g37a7a0f4-0ubuntu1
Bionic vmtest console log ** Attachment added: "Bionic vmtest console log" https://bugs.launchpad.net/curtin/+bug/1831772/+attachment/5275679/+files/curtin-vmtest-proposed-b-console.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831772 Title: sru curtin 2019-06-05 - 19.1-7-g37a7a0f4-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1831772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831772] Re: sru curtin 2019-06-05 - 19.1-7-g37a7a0f4-0ubuntu1
Bionic curtin-proposed test artifacts. ** Attachment added: "Bionic curtin-proposed test artifacts." https://bugs.launchpad.net/curtin/+bug/1831772/+attachment/5275669/+files/curtin-vmtest-proposed-b-artifacts.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831772 Title: sru curtin 2019-06-05 - 19.1-7-g37a7a0f4-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1831772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835091] Re: subiquity crashes upon reusing failed to assemble raid member partition
The shutdown plan requires that the config for a device being cleared to not include the preserve: True config. The "raid" partition, vda3 is explicitly marked as preserved: true: - device: disk-vda size: 20947402752 flag: linux preserve: true type: partition id: partition-vda3 Curtin would not be able to clear raid metadata from this partition without wipe: set and preserve not present. That said, I do think that curtin can do a few things to resolve this: 1) include partial raids in the discovered config, and can either a) add a field to indicate whether the array is healthy/partial/degrated; array_state maybe b) defer to subiquity to use curtin.block.mdadm.md_check to determine if it wants to include or mark members of the array with wipe so they can be used in other configs. 2) Update how we run clear-holders; Currently we only pass in a list of block devices, of type disk which have 'wipe' set and do not have 'preserve' enabled. This fails the case here where we'd like to wipe vda3 but it has a holder. Concretely; I'd curtin discover would return: - type: raid level: 0 name: md127 devices: - partition-vda3 spare_devices: [] array_state: failed Now, to do that, probert will need to also include partial raids as well. Not sure; it's odd that pyudev didn't have a /dev/md127 entry in the context. The alternative for probert is to run some mdadm commands on the devices which have the ID_FSTYPE set to raid. I'll add a probert task for this bug as well. For clear-holders, curtin will also accept type: partition. I expect the final config to set wipe: superblock on vda3 since it's a raid member; and that clear-holders is called with devices=['/dev/vda3'] - device: disk-vda size: 20947402752 flag: linux wipe: superblock type: partition id: partition-vda3 >From there, clear-holders would find /dev/md127 has a holder of type: raid and then the normal curtin shutdown plan would show us stopping md127, wipe each array member (/dev/vda3). ** Also affects: probert (Ubuntu) Importance: Undecided Status: New ** Changed in: probert (Ubuntu) Importance: Undecided => High ** Changed in: probert (Ubuntu) Status: New => Triaged ** Changed in: curtin Importance: Undecided => High ** Changed in: curtin 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/1835091 Title: subiquity crashes upon reusing failed to assemble raid member partition To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1835091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures
Without the patch, I can reproduce the hang fairly frequently, in one or two loops, which fails in this way: [ 1069.711956] bcache: cancel_writeback_rate_update_dwork() give up waiting for dc->writeback_write_update to quit [ 1088.583986] INFO: task kworker/0:2:436 blocked for more than 120 seconds. [ 1088.590330] Tainted: P O 4.15.0-54-generic #58-Ubuntu [ 1088.595831] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1088.598210] kworker/0:2 D0 436 2 0x8000 [ 1088.598244] Workqueue: events update_writeback_rate [bcache] [ 1088.598246] Call Trace: [ 1088.598255] __schedule+0x291/0x8a0 [ 1088.598258] ? __switch_to_asm+0x40/0x70 [ 1088.598260] schedule+0x2c/0x80 [ 1088.598262] schedule_preempt_disabled+0xe/0x10 [ 1088.598264] __mutex_lock.isra.2+0x18c/0x4d0 [ 1088.598266] ? __switch_to_asm+0x34/0x70 [ 1088.598268] ? __switch_to_asm+0x34/0x70 [ 1088.598270] ? __switch_to_asm+0x40/0x70 [ 1088.598272] __mutex_lock_slowpath+0x13/0x20 [ 1088.598274] ? __mutex_lock_slowpath+0x13/0x20 [ 1088.598276] mutex_lock+0x2f/0x40 [ 1088.598281] update_writeback_rate+0x98/0x2b0 [bcache] [ 1088.598285] process_one_work+0x1de/0x410 [ 1088.598287] worker_thread+0x32/0x410 [ 1088.598289] kthread+0x121/0x140 [ 1088.598291] ? process_one_work+0x410/0x410 [ 1088.598293] ? kthread_create_worker_on_cpu+0x70/0x70 [ 1088.598295] ret_from_fork+0x35/0x40 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796292 Title: Tight timeout for bcache removal causes spurious failures To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures
I've setup our integration test that runs the the CDO-QA bcache/ceph setup. On the updated kernel I got through 10 loops on the deployment before it stacktraced: http://paste.ubuntu.com/p/zVrtvKBfCY/ [ 3939.846908] bcache: bch_cached_dev_attach() Caching vdd as bcache5 on set 275985b3-da58-41f8-9072-958bd960b490 [ 3939.878388] bcache: register_bcache() error /dev/vdd: device already registered (emitting change event) [ 3939.904984] bcache: register_bcache() error /dev/vdd: device already registered (emitting change event) [ 3939.972715] bcache: register_bcache() error /dev/vdd: device already registered (emitting change event) [ 3940.059415] bcache: register_bcache() error /dev/vdd: device already registered (emitting change event) [ 3940.129854] bcache: register_bcache() error /dev/vdd: device already registered (emitting change event) [ 3949.257051] md: md0: resync done. [ 4109.273558] INFO: task python3:19635 blocked for more than 120 seconds. [ 4109.279331] Tainted: P O 4.15.0-55-generic #60+lp796292 [ 4109.284767] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4109.288771] python3 D0 19635 16361 0x [ 4109.288774] Call Trace: [ 4109.288818] __schedule+0x291/0x8a0 [ 4109.288822] ? __switch_to_asm+0x34/0x70 [ 4109.288824] ? __switch_to_asm+0x40/0x70 [ 4109.288826] schedule+0x2c/0x80 [ 4109.288852] bch_bucket_alloc+0x1fa/0x350 [bcache] [ 4109.288866] ? wait_woken+0x80/0x80 [ 4109.288872] __bch_bucket_alloc_set+0xfe/0x150 [bcache] [ 4109.288876] bch_bucket_alloc_set+0x4e/0x70 [bcache] [ 4109.22] __uuid_write+0x59/0x150 [bcache] [ 4109.288895] ? submit_bio+0x73/0x140 [ 4109.288900] ? __write_super+0x137/0x170 [bcache] [ 4109.288905] bch_uuid_write+0x16/0x40 [bcache] [ 4109.288911] __cached_dev_store+0x1a1/0x6d0 [bcache] [ 4109.288916] bch_cached_dev_store+0x39/0xc0 [bcache] [ 4109.288992] sysfs_kf_write+0x3c/0x50 [ 4109.288998] kernfs_fop_write+0x125/0x1a0 [ 4109.289001] __vfs_write+0x1b/0x40 [ 4109.289003] vfs_write+0xb1/0x1a0 [ 4109.289004] SyS_write+0x55/0xc0 [ 4109.289010] do_syscall_64+0x73/0x130 [ 4109.289014] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 4109.289016] RIP: 0033:0x7f8d2833e154 [ 4109.289018] RSP: 002b:7ffcda55a4e8 EFLAGS: 0246 ORIG_RAX: 0001 [ 4109.289020] RAX: ffda RBX: 0008 RCX: 7f8d2833e154 [ 4109.289021] RDX: 0008 RSI: 022b7360 RDI: 0003 [ 4109.289022] RBP: 7f8d288396c0 R08: R09: [ 4109.289022] R10: 0100 R11: 0246 R12: 0003 [ 4109.289026] R13: R14: 022b7360 R15: 01fe8db0 [ 4109.289033] INFO: task bcache_allocato:22317 blocked for more than 120 seconds. [ 4109.292172] Tainted: P O 4.15.0-55-generic #60+lp796292 [ 4109.295345] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4109.298208] bcache_allocato D0 22317 2 0x8000 [ 4109.298212] Call Trace: [ 4109.298217] __schedule+0x291/0x8a0 [ 4109.298225] schedule+0x2c/0x80 [ 4109.298232] bch_bucket_alloc+0x1fa/0x350 [bcache] [ 4109.298235] ? wait_woken+0x80/0x80 [ 4109.298241] bch_prio_write+0x19f/0x340 [bcache] [ 4109.298246] bch_allocator_thread+0x502/0xca0 [bcache] [ 4109.298260] kthread+0x121/0x140 [ 4109.298264] ? bch_invalidate_one_bucket+0x80/0x80 [bcache] [ 4109.298274] ? kthread_create_worker_on_cpu+0x70/0x70 [ 4109.298277] ret_from_fork+0x35/0x40 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796292 Title: Tight timeout for bcache removal causes spurious failures To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833623] Re: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1
I think you'll want to run: cloud-init clean --logs After doing your changes to the images; this will remove most cloud-init state. -- cloud-init will always run on each boot that it detects that it has data to process. So on VMWare, if an OVF iso is provided, or the vmdata is set in the DMI tables; then cloud-init runs. Each datasource reads the instance-id, which is just a unique string to identify the instance and cloud-init remembers this value such that on reboots we don't duplicate "first boot" operations. However, if the image is captured and booted somewhere else (where it would get a different instance id) then it would do the firstboot things again. -- You shouldn't need to disable cloud-init; but you likely need to clean- up after your first boot sequence. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833623 Title: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1833623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833623] Re: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1
Hrm, something looks a bit odd. In the collect logs, I can see that cloud-init found an OVF attached to the instance, however in the cloud- init.log there appears to be an existing boot of cloud-init already present: 2019-06-21 15:33:41,226 - main.py[DEBUG]: Execution continuing, no previous run detected that would allow us to stop early. 2019-06-21 15:33:41,226 - handlers.py[DEBUG]: start: init-network/check-cache: attempting to read from cache [trust] 2019-06-21 15:33:41,227 - util.py[DEBUG]: Reading from /var/lib/cloud/instance/obj.pkl (quiet=False) 2019-06-21 15:33:41,246 - util.py[DEBUG]: Read 7696 bytes from /var/lib/cloud/instance/obj.pkl 2019-06-21 15:33:41,273 - stages.py[DEBUG]: restored from cache: DataSourceNone Which looks wrong to me. I suspect this is some template image? And if so, it doesn't appear to have been cleaned up. Also, the journal is reporting errors: Jun 21 11:34:27.836406 mysql-mcm547807-109524397596 systemd[1]: Set hostname to . Jun 21 11:34:27.836424 mysql-mcm547807-109524397596 systemd[1]: sysinit.target: Found ordering cycle on sysinit.target/start Jun 21 11:34:27.836509 mysql-mcm547807-109524397596 systemd[1]: sysinit.target: Found dependency on cloud-init.service/start Jun 21 11:34:27.836536 mysql-mcm547807-109524397596 systemd[1]: sysinit.target: Found dependency on cloud-init-local.service/start Jun 21 11:34:27.836555 mysql-mcm547807-109524397596 systemd[1]: sysinit.target: Found dependency on open-vm-tools.service/start Jun 21 11:34:27.836574 mysql-mcm547807-109524397596 systemd[1]: sysinit.target: Found dependency on dbus.socket/start Jun 21 11:34:27.836591 mysql-mcm547807-109524397596 systemd[1]: sysinit.target: Found dependency on sysinit.target/start Jun 21 11:34:27.836617 mysql-mcm547807-109524397596 systemd[1]: sysinit.target: Breaking ordering cycle by deleting job cloud-init.service/start Jun 21 11:34:27.836636 mysql-mcm547807-109524397596 systemd[1]: cloud-init.service: Job cloud-init.service/start deleted to break ordering cycle starting with sysinit.target/start Jun 21 11:34:27.836655 mysql-mcm547807-109524397596 systemd[1]: sysinit.target: Found ordering cycle on sysinit.target/start Jun 21 11:34:27.836673 mysql-mcm547807-109524397596 systemd[1]: sysinit.target: Found dependency on cloud-init-local.service/start Jun 21 11:34:27.836696 mysql-mcm547807-109524397596 systemd[1]: sysinit.target: Found dependency on open-vm-tools.service/start Jun 21 11:34:27.836714 mysql-mcm547807-109524397596 systemd[1]: sysinit.target: Found dependency on dbus.socket/start Jun 21 11:34:27.836732 mysql-mcm547807-109524397596 systemd[1]: sysinit.target: Found dependency on sysinit.target/start Jun 21 11:34:27.836751 mysql-mcm547807-109524397596 systemd[1]: sysinit.target: Breaking ordering cycle by deleting job cloud-init-local.service/start Jun 21 11:34:27.836773 mysql-mcm547807-109524397596 systemd[1]: cloud-init-local.service: Job cloud-init-local.service/start deleted to break ordering cycle starting with sysinit.target/start Jun 21 11:34:27.836791 mysql-mcm547807-109524397596 systemd[1]: Created slice User and Session Slice. Which means cloud-init isn't quite working due to the image you're using which has created a dependency loop on cloud-init. This looks something like these bugs: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1793715 https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1804287 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833623 Title: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1833623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834897] Re: probert has too many dependencies for consoleconf
Yuck. This is quite awkward. Neither half of probert wants the other half. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834897 Title: probert has too many dependencies for consoleconf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/probert/+bug/1834897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833623] Re: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1
Hi, Could you run: cloud-init collect-logs and attach the tarball it creates? ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium ** Changed in: cloud-init (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/1833623 Title: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1833623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833192] Re: VMware: post custom script isn't run correctly
Wrong source package ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: evince (Ubuntu) Status: New => Invalid ** Merge proposal linked: https://code.launchpad.net/~xiaofengw/cloud-init/+git/cloud-init/+merge/368902 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833192 Title: VMware: post custom script isn't run correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1833192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831772] Re: sru curtin 2019-06-05 - 19.1-7-g37a7a0f4-0ubuntu1
Thanks, we'll be uploading a replacement source package which drops the dependency on probert in bionic, cosmic and disco. Thanks for the review -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831772 Title: sru curtin 2019-06-05 - 19.1-7-g37a7a0f4-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1831772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831757] Re: curtin from xenial daily ppa not installable
since probert is not yet in main, we can't have probert as a depends in any of the releases. ** Also affects: curtin (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: curtin (Ubuntu Xenial) Status: New => 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/1831757 Title: curtin from xenial daily ppa not installable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1831757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832381] Re: vm fails to boot due to conflicting network configuration when user switches from netplan to eni
Do you happen to have a cloud-init collect-logs output ? I suspect it's easy enough to recreate bug if you've already got logs available, please attach. ** Summary changed: - vm fails to boot due to conflicting network configuration when cloudinit switches from netplan to eni + vm fails to boot due to conflicting network configuration when user switches from netplan to eni ** Changed in: cloud-init (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/1832381 Title: vm fails to boot due to conflicting network configuration when user switches from netplan to eni To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1832381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831787] Re: Bogus routes after DHCP lease change
** Changed in: netplan Status: Incomplete => Invalid ** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831787 Title: Bogus routes after DHCP lease change To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1831787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831757] Re: curtin from xenial daily ppa not installable
https://git.launchpad.net/curtin/commit/?id=55aa836f04657dac67445e154b2ee5fe78b8db8a ** Changed in: curtin (Ubuntu) Status: New => 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/1831757 Title: curtin from xenial daily ppa not installable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1831757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831772] Re: sru curtin 2019-06-05 - 19.1-7-g37a7a0f4-0ubuntu1
** Description changed: == Begin SRU Template == [Impact] This release sports both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: -* + - block-discover: add cli/API for exporting existing storage to config + - curthoooks: disable daemons while reconfiguring mdadm + - mdadm: fix install to existing raid + - block: support multipath devices in lookup and partition_kname + - grub: add grub config to control os_prober,terminal settings in target + - curthooks: chzdev_import must encode data if provided See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/CurtinUpdates Curtin now contains an extensive integration test suite that is ran using the SRU package for each releases. These suite has documentation here: https://curtin.readthedocs.io/en/latest/topics/integration-testing.html In order to avoid regression to existing MAAS product, the MAAS team will run their continuous integration test against the curtin that is in -proposed. A successful run will be required before the proposed curtin can be let into -updates. The curtin team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. Curtin team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. [Discussion] == End SRU Template == - + curtin (19.1-7-g37a7a0f4-0ubuntu1~19.04.1) disco; urgency=medium + + * New upstream snapshot. + - vmtests: determine block name via dname when verifying volume groups + - vmtest: add Centos66/Centos70 FromBionic release and re-add tests + - block-discover: add cli/API for exporting existing storage to config + - vmtest: refactor test_network code for Eoan + - curthoooks: disable daemons while reconfiguring mdadm + [Michael Hudson-Doyle] (LP: #1829325.) + - mdadm: fix install to existing raid [Michael Hudson-Doyle] (LP: #1830157) + - apt_proxy env var set but empty => do not setup any proxy + [Paride Legovini] + - release 19.1 + - vmtest: add missing skip_by_date on Eoan test_network_mtu + - vmtest: remove skip_by_date on Disco Allindata test + - block: support multipath devices in lookup and partition_kname + (LP: #1813228) + - grub: add grub config to control os_prober,terminal settings in target + - vmtest: add eoan tests [Paride Legovini] + - vmtest: add dependency on python3-jsonschema [Paride Legovini] + - Pylint compatibility with Python 3.7 [Paride Legovini] (LP: #1828229) + - vmtest: disable disco multipath test + - vmtests: bump network mtu tests out a bit + - Fix up yaml.load warnings + - vmtest: disable trusty, it's dead jim + - vmtest: reenable UEFI 4k tests, which got dropped when fixing + subclassing. + - vmtests: Add test_kernel_img_conf stub for PsuedoVMBaseClass + - curthooks: chzdev_import must encode data if provided (LP: #1825007) + - vmtest: test for kernel-img conf on ubuntu only + + -- Ryan Harper Wed, 05 Jun 2019 13:46:57 -0500 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831772 Title: sru curtin 2019-06-05 - 19.1-7-g37a7a0f4-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1831772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831787] Re: Bogus routes after DHCP lease change
Looks like this issue, I think: https://github.com/systemd/systemd/issues/12490 ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** 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/1831787 Title: Bogus routes after DHCP lease change To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1831787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831772] Re: sru curtin 2019-06-05 - 19.1-7-g37a7a0f4-0ubuntu1
Not an upstream bug. ** Changed in: curtin 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/1831772 Title: sru curtin 2019-06-05 - 19.1-7-g37a7a0f4-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1831772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831772] [NEW] sru curtin 2019-06-05 - 19.1-7-g37a7a0f4-0ubuntu1
Public bug reported: == Begin SRU Template == [Impact] This release sports both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: * See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/CurtinUpdates Curtin now contains an extensive integration test suite that is ran using the SRU package for each releases. These suite has documentation here: https://curtin.readthedocs.io/en/latest/topics/integration-testing.html In order to avoid regression to existing MAAS product, the MAAS team will run their continuous integration test against the curtin that is in -proposed. A successful run will be required before the proposed curtin can be let into -updates. The curtin team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. Curtin team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. [Discussion] == End SRU Template == ** Affects: curtin Importance: Undecided Status: Invalid ** Affects: curtin (Ubuntu) Importance: Undecided Status: New ** Affects: curtin (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: curtin (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: curtin (Ubuntu Cosmic) Importance: Undecided Status: New ** Affects: curtin (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Cosmic) 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/1831772 Title: sru curtin 2019-06-05 - 19.1-7-g37a7a0f4-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1831772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831757] [NEW] curtin from xenial daily ppa not installable
Public bug reported: On Xenial 1. add-apt-repository --enable-source --yes ppa:curtin-dev/daily 2. apt-get install --no-install-recommends -qy curtin Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: curtin : Depends: probert but it is not installable E: Unable to correct problems, you have held broken packages. failed apt-get install --no-install-recommends -qy curtin ** Affects: curtin (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/1831757 Title: curtin from xenial daily ppa not installable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1831757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures
On Mon, Jun 3, 2019 at 2:05 PM Andrey Grebennikov < agrebennikov1...@gmail.com> wrote: > Is there an estimate on getting this package in bionic-updates please? > We are starting an SRU of curtin this week. SRU's take at least 7 days from when they hit -proposed possibly longer depending on test results. I should have something up in -proposed this week and we'll go from there on testing. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1796292 > > Title: > Tight timeout for bcache removal causes spurious failures > > To manage notifications about this bug go to: > https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796292 Title: Tight timeout for bcache removal causes spurious failures To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830768] Re: Stuck cloud-init status --wait in nested lxd
Can you collect: systemctl list-jobs? >From the logs, it appears that snapd has not yet seeded, which blocks cloud-final.service from running, so it's blocking until snapd is ready. ** Changed in: cloud-init (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/1830768 Title: Stuck cloud-init status --wait in nested lxd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1830768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827929] Re: curtin should support making installed systems BIOS+UEFI hybrid bootable
IIUC "proper partition setup" for callers of curtin is: /boot/EFI partition *and* a grub_bios partition. Something like: config: - id: main_disk type: disk ptable: gpt serial: disk-a name: main_disk wipe: superblock grub_device: true - id: bios_boot type: partition size: 1MB number: 1 - device: main_disk flag: boot id: main_disk_part2 number: 2 size: 512M type: partition wipe: superblock The curtin part would be to ensure that shim-signed *and* grub-pc packages are installed into target. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827929 Title: curtin should support making installed systems BIOS+UEFI hybrid bootable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1827929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829264] Re: incorrect separator for multiple ARP IP targets
Looks to have a fix committed now. https://github.com/CanonicalLtd/netplan/commit/ee94ec118a8aabef8d79e78e7b2f028615a28ce8 ** Changed in: netplan Status: New => 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/1829264 Title: incorrect separator for multiple ARP IP targets To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1829264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821353] Re: bcache-super-show segfaults reading superblock on dasd
Marking this invalid since DASDs can't be used directly without a partition table. ** Changed in: bcache-tools (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/1821353 Title: bcache-super-show segfaults reading superblock on dasd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1821353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures
On Wed, May 8, 2019 at 11:55 PM Trent Lloyd wrote: > I have been running into this (curtin 18.1-17-gae48e86f- > 0ubuntu1~16.04.1) > > I think this commit basically agrees with my thoughts but I just wanted > to share them explicitly in case they are interesting > > (1) If you *unregister* the cache device from the backing device, it > first has to purge all the dirty data back to the backing device. This > may obviously take a while. > > (2) When doing that, I managed to deadlock bcache at least once on > xenial-hwe 4.15 where it was trying to reclaim memory from XFS, which I > assume was trying to write to the bcache.. traceback: > https://pastebin.canonical.com/117528/ - you can't get out of that > without a reboot > Thanks for capturing those; Ive quite a few of my own as an unregister path which _should_ work; but doesn't for various bugs in bcache. I need to attach those OOPS to this bug as well. > > (3) However generally I had good luck simplying "stop"ing the cache > devices (it seems perhaps that is what this bug is designed to do, > switch to stop, instead of unregister?). Specifically though I was > stopping the backing devices, and then later the cache device. It seems > like the current commit is the other way around? > Unregister is just not stable, so stopping is what is being done now. I did attempt stopping bcache devices first and only once all bcache devices were stopped to then stop and remove a cacheset; this proved unreliable under our integration testing of various bcache scenarios. > > ** Tags added: sts > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1796292 > > Title: > Tight timeout for bcache removal causes spurious failures > > To manage notifications about this bug go to: > https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796292 Title: Tight timeout for bcache removal causes spurious failures To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures
Xenial GA kernel bcache unregister oops: http://paste.ubuntu.com/p/BzfHFjzZ8y/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796292 Title: Tight timeout for bcache removal causes spurious failures To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768118] Re: Artful to Bionic upgrade kills all LXD container networking
Reading through the lxd issue log, it appears that a host networking issue/packaging issue triggered on upgrade; unrelated to cloud-init inside the containers. If you feel that cloud-init isn't doing something correct, please re-open this bug with new information. Thanks. ** Changed in: cloud-init (Ubuntu) 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/1768118 Title: Artful to Bionic upgrade kills all LXD container networking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1768118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805673] Re: dname for multipath devices should point to mpath dev
** Changed in: curtin (Ubuntu) Importance: Undecided => High ** Changed in: curtin (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805673 Title: dname for multipath devices should point to mpath dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1805673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805674] Re: curtin should not use filesystem UUID for mounting complex devices
** Changed in: curtin (Ubuntu) Importance: Undecided => High ** Changed in: curtin (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805674 Title: curtin should not use filesystem UUID for mounting complex devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1805674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819043] Re: Lintian warning: package-installs-into-obsolete-dir etc/bash_completion.d/
This was fixed in commit: https://git.launchpad.net/cloud- init/commit/?id=947d3c20891815f164f4c7a8884d1f02ae4a9c5b ** Changed in: cloud-init Status: New => 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/1819043 Title: Lintian warning: package-installs-into-obsolete-dir etc/bash_completion.d/ To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1819043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827704] Re: ConfigDrive network configuration does not applied per boot
Hi, Thanks for reporting this. DataSourceConfigDrive doesn't currently set this value, and likely won't by default. However, we do want to allow user-config to opt-in to this behavior. This is a work-in-progress feature, currently here: https://code.launchpad.net/~raharper/cloud-init/+git/cloud- init/+ref/feature/cloud-init-hotplug-handler ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu) 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/1827704 Title: ConfigDrive network configuration does not applied per boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1827704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824185] Re: Release a new upstream snapshot to disco
** 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/1824185 Title: Release a new upstream snapshot to disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1824185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825444] Re: "make rpm" fails on CentOS after commit 947d3c208
** Changed in: cloud-init (Ubuntu) Status: New => 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/1825444 Title: "make rpm" fails on CentOS after commit 947d3c208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1825444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827929] Re: curtin should support making installed systems BIOS+UEFI hybrid bootable
** Changed in: curtin (Ubuntu) Importance: Undecided => Medium ** Changed in: curtin (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827929 Title: curtin should support making installed systems BIOS+UEFI hybrid bootable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1827929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825413] Re: mdadm, mkfs, other io commands hang, stuck task, bad rip
Sorry, I missed responding. This were run in separate VMs, this is under our curtin vmtest integration testing. Yes, let me get the q35 trace; it doesn't happen as often. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825413 Title: mdadm, mkfs, other io commands hang, stuck task, bad rip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826252] Re: by-id/wwn symlinks for virtio-scsi and multipath-tools not present
Looks like I got it wrong. The critical step is to have *both* serial and wwn set to the same value in the -device config like so: -device scsi- hd,drive=drv2,serial=0x39cc071e72c64cc4,wwn=0x39cc071e72c64cc4 and then the sg_inq command succeeds like so: # /usr/bin/sg_inq --export --inhex=/sys/block/sda/device/vpd_pg83 --raw SCSI_IDENT_LUN_VENDOR=0x39cc071e72c64cc4 SCSI_IDENT_LUN_NAA_LOCAL=39cc071e72c64cc4 and then we get an ID_WWN export correctly: http://paste.ubuntu.com/p/7hGsM2YJNZ/ ** Changed in: curtin Status: New => Invalid ** Changed in: qemu (Ubuntu) Status: New => Invalid ** Changed in: sg3-utils (Ubuntu) Status: New => Invalid ** Changed in: udev (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/1826252 Title: by-id/wwn symlinks for virtio-scsi and multipath-tools not present To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1826252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826252] [NEW] by-id/wwn symlinks for virtio-scsi and multipath-tools not present
Public bug reported: In vmtest, we use virtio-scsi controller with scsi-hd devices. When we supply them with a wwn property, 60-persistent-storage.rules will create a /dev/disk/by-id/wwn- to point to the disk with said property. In disco, we now include multipath-tools which brings in sg3-utils-udev which provides a 55-scsi-sg3_id.rules file which runs before 60 -persistent-storage.rules. In the sg3 rules, it uses sg_inq to extract values from the device. The result is that a virtio-scsi/scsi-hd device does not expose ID_WWN in the same way, and if no serial value is set on the device, sg3 rules will *create* and ID_SERIAL value from the device model and other attributes. This _prevents_ 60-persisten-storage.rules from running scsi_id which *does* find the the ID_WWN property on the scsi-hd. ** Affects: curtin Importance: Undecided Status: New ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Affects: sg3-utils (Ubuntu) Importance: Undecided Status: New ** Affects: udev (Ubuntu) Importance: Undecided Status: New ** Also affects: sg3-utils (Ubuntu) Importance: Undecided Status: New ** Also affects: udev (Ubuntu) Importance: Undecided Status: New ** Also affects: qemu (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/1826252 Title: by-id/wwn symlinks for virtio-scsi and multipath-tools not present To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1826252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825413] Re: mdadm, mkfs, other io commands hang, stuck task, bad rip
Hi Seth, notice only one of the stack tracks have the floppy, the mdadm one does not. I've also recreated this on a qemu q35 machine type which does not include the floppy device. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825413 Title: mdadm, mkfs, other io commands hang, stuck task, bad rip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825413] [NEW] mdadm, mkfs, other io commands hang, stuck task, bad rip
Public bug reported: 1. disco 2. # apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.0.0.13.14 Candidate: 5.0.0.13.14 Version table: *** 5.0.0.13.14 500 500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status 3. installation completes sucessfully 4. Running an installation of Disco creating filesystems and probing things will hang (stuck task) every so often. When it happens, the kernel throws an oops and bad rip value. [ 967.810391] INFO: task mdadm:12213 blocked for more than 120 seconds. [ 967.811787] Tainted: P O 5.0.0-13-generic #14-Ubuntu [ 967.813330] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.815500] mdadm D0 12213 12207 0x [ 967.815503] Call Trace: [ 967.815509] __schedule+0x2d0/0x840 [ 967.815511] ? __switch_to_asm+0x40/0x70 [ 967.815512] ? __switch_to_asm+0x34/0x70 [ 967.815514] schedule+0x2c/0x70 [ 967.815516] schedule_preempt_disabled+0xe/0x10 [ 967.815518] __mutex_lock.isra.10+0x2e4/0x4c0 [ 967.815522] ? exact_lock+0x11/0x20 [ 967.815524] __mutex_lock_slowpath+0x13/0x20 [ 967.815528] mutex_lock+0x2c/0x30 [ 967.815530] __blkdev_get+0x7b/0x550 [ 967.815532] ? bd_acquire+0xd0/0xd0 [ 967.815533] blkdev_get+0x10c/0x330 [ 967.815535] ? bd_acquire+0xd0/0xd0 [ 967.815537] blkdev_open+0x92/0x100 [ 967.815539] do_dentry_open+0x143/0x3a0 [ 967.815540] vfs_open+0x2d/0x30 [ 967.815542] path_openat+0x2d4/0x16d0 [ 967.815547] ? put_device+0x17/0x20 [ 967.815552] ? scsi_device_put+0x2b/0x30 [ 967.815553] do_filp_open+0x93/0x100 [ 967.81] ? strncpy_from_user+0x56/0x1b0 [ 967.815558] ? __alloc_fd+0x46/0x140 [ 967.815560] do_sys_open+0x177/0x280 [ 967.815561] ? _cond_resched+0x19/0x30 [ 967.815563] __x64_sys_openat+0x20/0x30 [ 967.815566] do_syscall_64+0x5a/0x110 [ 967.815567] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 967.815568] RIP: 0033:0x7faa36406cce [ 967.815572] Code: Bad RIP value. [ 967.815573] RSP: 002b:7ffedb663f80 EFLAGS: 0246 ORIG_RAX: 0101 [ 967.815574] RAX: ffda RBX: 4000 RCX: 7faa36406cce [ 967.815575] RDX: 4000 RSI: 564df70257b0 RDI: ff9c [ 967.815576] RBP: 564df70257b0 R08: 564df70257b0 R09: [ 967.815576] R10: R11: 0246 R12: 7ffedb664240 [ 967.815577] R13: R14: 0001 R15: 564df7023e00 [ 967.799227] INFO: task mkfs.btrfs:3767 blocked for more than 120 seconds. [ 967.803509] Tainted: P O 5.0.0-13-generic #14-Ubuntu [ 967.807192] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.810235] mkfs.btrfs D0 3767 1866 0x [ 967.810239] Call Trace: [ 967.810251] __schedule+0x2d0/0x840 [ 967.810254] ? __switch_to_asm+0x34/0x70 [ 967.810256] ? __switch_to_asm+0x40/0x70 [ 967.810258] schedule+0x2c/0x70 [ 967.810260] schedule_timeout+0x258/0x360 [ 967.810277] wait_for_completion+0xb7/0x140 [ 967.810281] ? wake_up_q+0x80/0x80 [ 967.810293] __floppy_read_block_0+0x138/0x190 [floppy] [ 967.810298] ? floppy_cmos_show+0x30/0x30 [floppy] [ 967.810302] floppy_revalidate+0xf8/0x230 [floppy] [ 967.810307] check_disk_change+0x62/0x70 [ 967.810309] floppy_open+0x2ae/0x380 [floppy] [ 967.810311] __blkdev_get+0xe5/0x550 [ 967.810313] ? bd_acquire+0xd0/0xd0 [ 967.810315] blkdev_get+0x10c/0x330 [ 967.810316] ? bd_acquire+0xd0/0xd0 [ 967.810318] blkdev_open+0x92/0x100 [ 967.810321] do_dentry_open+0x143/0x3a0 [ 967.810323] vfs_open+0x2d/0x30 [ 967.810326] path_openat+0x2d4/0x16d0 [ 967.810328] ? filename_lookup.part.60+0xe0/0x170 [ 967.810332] ? strncpy_from_user+0x56/0x1b0 [ 967.810333] do_filp_open+0x93/0x100 [ 967.810353] ? strncpy_from_user+0x56/0x1b0 [ 967.810358] ? __alloc_fd+0x46/0x140 [ 967.810360] do_sys_open+0x177/0x280 [ 967.810362] ? _cond_resched+0x19/0x30 [ 967.810364] __x64_sys_openat+0x20/0x30 [ 967.810368] do_syscall_64+0x5a/0x110 [ 967.810369] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 967.810372] RIP: 0033:0x7f46b99374db [ 967.810377] Code: Bad RIP value. [ 967.810378] RSP: 002b:7ffc9e849d70 EFLAGS: 0246 ORIG_RAX: 0101 [ 967.810380] RAX: ffda RBX: 556674552080 RCX: 7f46b99374db [ 967.810381] RDX: 0008 RSI: 556674552100 RDI: ff9c [ 967.810382] RBP: 55667454a270 R08: 556674552120 R09: 4000 [ 967.810382] R10: R11: 0246 R12: 5cb8c394 [ 967.810383] R13: 7f46b3c4 R14: dcb8c394 R15: 7f46b9988425 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-virtual 5.0.0.13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
[Bug 1825413] Re: mdadm, mkfs, other io commands hang, stuck task, bad rip
root@ubuntu:~# lspci -v -nn 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100] Flags: fast devsel 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] [8086:7000] Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100] Flags: medium devsel 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] [8086:7010] (prog-if 80 [ISA Compatibility mode-only controller, supports bus mastering]) Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100] Flags: bus master, medium devsel, latency 0 [virtual] Memory at 01f0 (32-bit, non-prefetchable) [size=8] [virtual] Memory at 03f0 (type 3, non-prefetchable) [virtual] Memory at 0170 (32-bit, non-prefetchable) [size=8] [virtual] Memory at 0370 (type 3, non-prefetchable) I/O ports at c080 [size=16] Kernel driver in use: ata_piix Kernel modules: pata_acpi 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 03) Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100] Flags: medium devsel, IRQ 9 Kernel driver in use: piix4_smbus Kernel modules: i2c_piix4 00:02.0 VGA compatible controller [0300]: Device [1234:] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Device [1af4:1100] Flags: fast devsel Memory at fd00 (32-bit, prefetchable) [size=16M] Memory at feb9 (32-bit, non-prefetchable) [size=4K] Expansion ROM at 000c [disabled] [size=128K] Kernel driver in use: bochs-drm Kernel modules: bochs_drm 00:03.0 SCSI storage controller [0100]: Red Hat, Inc. Virtio SCSI [1af4:1004] Subsystem: Red Hat, Inc. Virtio SCSI [1af4:0008] Physical Slot: 3 Flags: bus master, fast devsel, latency 0, IRQ 11 I/O ports at c000 [size=64] Memory at feb91000 (32-bit, non-prefetchable) [size=4K] Memory at fe00 (64-bit, prefetchable) [size=16K] Capabilities: [98] MSI-X: Enable+ Count=4 Masked- Capabilities: [84] Vendor Specific Information: VirtIO: Capabilities: [70] Vendor Specific Information: VirtIO: Notify Capabilities: [60] Vendor Specific Information: VirtIO: DeviceCfg Capabilities: [50] Vendor Specific Information: VirtIO: ISR Capabilities: [40] Vendor Specific Information: VirtIO: CommonCfg Kernel driver in use: virtio-pci 00:04.0 Unclassified device [00ff]: Red Hat, Inc. Virtio RNG [1af4:1005] Subsystem: Red Hat, Inc. Virtio RNG [1af4:0004] Physical Slot: 4 Flags: bus master, fast devsel, latency 0, IRQ 10 I/O ports at c040 [size=32] Memory at fe004000 (64-bit, prefetchable) [size=16K] Capabilities: [84] Vendor Specific Information: VirtIO: Capabilities: [70] Vendor Specific Information: VirtIO: Notify Capabilities: [60] Vendor Specific Information: VirtIO: DeviceCfg Capabilities: [50] Vendor Specific Information: VirtIO: ISR Capabilities: [40] Vendor Specific Information: VirtIO: CommonCfg Kernel driver in use: virtio-pci 00:05.0 Ethernet controller [0200]: Red Hat, Inc. Virtio network device [1af4:1000] Subsystem: Red Hat, Inc. Virtio network device [1af4:0001] Physical Slot: 5 Flags: bus master, fast devsel, latency 0, IRQ 10 I/O ports at c060 [size=32] Memory at feb92000 (32-bit, non-prefetchable) [size=4K] Memory at fe008000 (64-bit, prefetchable) [size=16K] Expansion ROM at feb0 [disabled] [size=512K] Capabilities: [98] MSI-X: Enable+ Count=3 Masked- Capabilities: [84] Vendor Specific Information: VirtIO: Capabilities: [70] Vendor Specific Information: VirtIO: Notify Capabilities: [60] Vendor Specific Information: VirtIO: DeviceCfg Capabilities: [50] Vendor Specific Information: VirtIO: ISR Capabilities: [40] Vendor Specific Information: VirtIO: CommonCfg Kernel driver in use: virtio-pci -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825413 Title: mdadm, mkfs, other io commands hang, stuck task, bad rip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825007] Re: chzdev export/prepare-for-import/import bombs out on import in python3.6
Thanks, looks like python3.7 subprocess.Popen.communicate helpfully converts str to bytes, however that hid the bug when I tested this path on s390x disco. The fix will be to encode the string data we passed to util.subp(). ** Changed in: curtin Importance: Undecided => High ** Changed in: curtin Status: New => Confirmed ** Changed in: curtin Assignee: (unassigned) => Ryan Harper (raharper) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825007 Title: chzdev export/prepare-for-import/import bombs out on import in python3.6 To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1825007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1776452] Re: Fail to set DNS server and search domain when customize Ubuntu18.04 to DHCP IP by cloud-init
On Mon, Apr 15, 2019 at 9:21 AM Pengzhen(Peter) Cao wrote: > Hi Ryan, > > As you said, "cloudinit/sources/helpers/vmware/imc/config_nic.py" now > generates v1 network_state dictionary. Should I just add a "DHCPFROMDNS: > true/false" key as V1 format or should I update the output to v2 > together with other fields? > Hi Pengzhen, I would transition to v2 since that now supports DNSFROMDHCP. I do think we should add a key in v1, but I'd like to think about what that looks like before we add it. For now, both sysconfig (PEERDNS) and netplan (v2) (DNSFROMDHCP) have keys that indicate on a per-interface basis whether they should obtain DNS server/search from DHCP results. This will need to be parsed and stored in network_state under the interfaces dictionary, and then in the renderers, for each interface, if the boolean is true emit the correct configuration value (PEERDNS=yes|no, dnsfromdhcp: true|false). We can follow up with a change to eni renderer once we determine how to implement that under ifupdown/dhclient. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1776452 > > Title: > Fail to set DNS server and search domain when customize Ubuntu18.04 to > DHCP IP by cloud-init > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1776452/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776452 Title: Fail to set DNS server and search domain when customize Ubuntu18.04 to DHCP IP by cloud-init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1776452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824172] Re: Do not force value of user properties to on/off
What zfs property are you aware of that takes yes/no or maybe? ** Changed in: curtin (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/1824172 Title: Do not force value of user properties to on/off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1824172/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821994] Re: [FFE] Introduce support for probing more storage types (via a new release)
@Steve, In preparing an upload for probert, in addition to the functional changes, there are some debian directory clean-ups, wondering if those are acceptable under this FFe? (some of the changes are adding package deps for the feature, so I'd assume those are). http://paste.ubuntu.com/p/bZXHkQVzwt/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821994 Title: [FFE] Introduce support for probing more storage types (via a new release) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/probert/+bug/1821994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776452] Re: Fail to set DNS server and search domain when customize Ubuntu18.04 to DHCP IP by cloud-init
Hi, For now, the version from dpkg is the best way. Netplan does have plans for querying feature-flags/--version. https://trello.com/c/ls9KUQuV/42-feature-availability-documentation- introspection-feature-flags -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776452 Title: Fail to set DNS server and search domain when customize Ubuntu18.04 to DHCP IP by cloud-init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1776452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1817049] Re: Subiquity should install security updates before first login
On Thu, Apr 4, 2019 at 9:06 PM Seth Arnold <1817...@bugs.launchpad.net> wrote: > Two methods come to mind: > > - Writing an apt sources.list that omits the -updates pocket > - Writing apt pinning rules that omits the -updates pocket. > > I would prefer we install all updates, unless the user has explicitly > requested only the -security pocket: > > - Updates from -updates may be very important but not involve a security > boundary. > > - Doing a simple apt update && apt upgrade with the configured sources > would be easier than trying to modify the sources or add and remove > pinning without disrupting any pinning the user may have selected. > This is something that is pretty easy to do with curtin config: system_upgrade: enabled: true However, on older releases, this does impact install time. > > Thanks > > -- > You received this bug notification because you are subscribed to > subiquity. > Matching subscriptions: subiquity-bugs > https://bugs.launchpad.net/bugs/1817049 > > Title: > Subiquity should install security updates before first login > > To manage notifications about this bug go to: > https://bugs.launchpad.net/subiquity/+bug/1817049/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817049 Title: Subiquity should install security updates before first login To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1817049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750732] Re: grub package will change the boot order for MaaS deployed system
** Changed in: curtin (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/1750732 Title: grub package will change the boot order for MaaS deployed system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1750732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743966] Re: Trusty deployments fail when custom archive keys are configured
I'm closing the cloud-init task; If there is further information about what cloud-init would need to do here, please reopen. ** Changed in: cloud-init (Ubuntu) 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/1743966 Title: Trusty deployments fail when custom archive keys are configured To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1743966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773397] Re: cloud-init renames interfaces at every boot
Matt, This is expected behavior. MAAS provides network configuration to cloud-init (via curtin). Cloud-init will rename interfaces that are part of the provided network configuration to ensure the configuration will apply. If you need to reconfigure or provide additional configuration, you have a couple options. 1) You could modify the 50-curtin-networking.cfg with your desired changes 2) You can disable cloud-init networking and provide your own in /etc/netplan % cat /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg network: config: disabled ** Changed in: cloud-init (Ubuntu) Status: New => 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/1773397 Title: cloud-init renames interfaces at every boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1773397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756040] Re: bionic: LXD containers don't get fan network IP addresses
Comment #3 correctly diagnoses the issue (bad network-config) which caused cloud-init to error out. And Comment #11 suggests that this configuration has been resolved. I'm closing the cloud-init task here. Please re-open if you believe there is a cloud-init issue that needs fixing. ** Changed in: cloud-init (Ubuntu) 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/1756040 Title: bionic: LXD containers don't get fan network IP addresses To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1756040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821353] Re: bcache-super-show segfaults reading superblock on dasd
There are no restrictions on non-dasd devices so we can update curtin to ensure that we don't allow creating bcache devices on dasd without a partition. I'm not sure whether or not it's worth adding dasd specific checks to bcache-tools to refuse when supplied with a dasd block device. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821353 Title: bcache-super-show segfaults reading superblock on dasd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1821353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821972] Re: Installation error with Ununty Server 18.04 LTS - curthooks
Thanks for reporting the error. Curtin is attempting to extract BootOrder and BootCurrent. A non-zero return code from running efibootmgr -v is unexpected. It's not clear to me if this is a fatal error; it doesn't appear that way to me.If it isn't then ideally we'll need to determine the set of error codes that efibootmgr returns that aren't fatal to obtaining BootOrder and BootCurrent. It may be the case that accepting non-zero exits from the --verbose command could hint that attempting to change BootOrder may fail. ** Changed in: curtin (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/1821972 Title: Installation error with Ununty Server 18.04 LTS - curthooks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1821972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821353] Re: bcache-super-show segfaults reading superblock on dasd
** Attachment added: "core from bcache-super-show" https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1821353/+attachment/5249549/+files/_usr_sbin_bcache-super-show.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821353 Title: bcache-super-show segfaults reading superblock on dasd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1821353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821353] [NEW] bcache-super-show segfaults reading superblock on dasd
Public bug reported: 1. # lsb_release -rd Description:Ubuntu Disco Dingo (development branch) Release:19.04 2. # apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-3 Candidate: 1.0.8-3 Version table: *** 1.0.8-3 500 500 http://us.ports.ubuntu.com/ubuntu-ports disco/main s390x Packages 100 /var/lib/dpkg/status 3. bcache-super-show /dev/dasda Should return the superblock information on the device. 4. segfaults. Reproduce with: $ ls -al /dev/disk/by-path/ccw-0.0.1520 lrwxrwxrwx 1 root root 11 Mar 22 08:34 /dev/disk/by-path/ccw-0.0.1520 -> ../../dasda $ make-bcache --writeback --cache /dev/disk/by-path/ccw-0.0.1520 $ bcache-super-show /dev/disk/by-path/ccw-0.0.1520 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bcache-tools 1.0.8-3 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu21 Architecture: s390x Date: Fri Mar 22 08:38:06 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bcache-tools UpgradeStatus: Upgraded to disco on 2019-02-18 (31 days ago) ** Affects: bcache-tools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug disco s390x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821353 Title: bcache-super-show segfaults reading superblock on dasd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1821353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811117] Re: Failed deployment: FileNotFoundError: [Errno 2] No such file or directory: '/sys/class/block/bcache0/bcache0p1/slaves'
Just to close the loop on comment #17, the SRU includes this commit: https://git.launchpad.net/curtin/commit/?id=b473fd507e6e6ae76c30df3199fdd3adc697d825 which was the additional change needed to completely resolve the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/187 Title: Failed deployment: FileNotFoundError: [Errno 2] No such file or directory: '/sys/class/block/bcache0/bcache0p1/slaves' To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817964] Re: sru curtin 2019-02-27 - 18.2-10-g7afd77fa-0ubuntu1
Cosmic MAAS QA artifacts. ** Attachment added: "maas-qa-sru-proposed-cosmic-curtin-sru-manual.zip" https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1817964/+attachment/5247673/+files/maas-qa-sru-proposed-cosmic-curtin-sru-manual.zip ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-cosmic 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/1817964 Title: sru curtin 2019-02-27 - 18.2-10-g7afd77fa-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1817964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817964] Re: sru curtin 2019-02-27 - 18.2-10-g7afd77fa-0ubuntu1
Xenial curtin-proposed test log. Note there is one expected failure (DiscoAllindata); not a curtin issue (LP: #1818876) ** Attachment added: "curtin-vmtest-proposed-x-console.log" https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1817964/+attachment/5247671/+files/curtin-vmtest-proposed-x-console.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817964 Title: sru curtin 2019-02-27 - 18.2-10-g7afd77fa-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1817964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817964] Re: sru curtin 2019-02-27 - 18.2-10-g7afd77fa-0ubuntu1
Xenial curtin-proposed artifacts. ** Attachment added: "curtin-vmtest-proposed-x-artifacts.tar.xz" https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1817964/+attachment/5247672/+files/curtin-vmtest-proposed-x-artifacts.tar.xz ** Description changed: == Begin SRU Template == [Impact] This release sports both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: - * - dname: relax dname req for disk serial/wwn presence for compatibility - (LP: #1735839) - clear-holders: handle FileNotFound when probing for bcache device slaves - (LP: #187) - Adjust helpers/common to edit GRUB_CMDLINE_LINUX_DEFAULT in place. - (LP: #1527664) - - dname: persistent names based on serial or wwn (LP: #1735839) + - dname: persistent names based on serial or wwn - Fix bug in is_swap_device if a device was smaller than page_size. - (LP: #1803672) - - Add clear-holders to meta-simple (LP: #1786736) - - block_meta: use wipe config when clearing partitions (LP: #1800153) + - Add clear-holders to meta-simple + - block_meta: use wipe config when clearing partitions - apt: Use new format apt config when writing preserve_sources_list. - (LP: #1735950) + See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/CurtinUpdates Curtin now contains an extensive integration test suite that is ran using the SRU package for each releases. These suite has documentation here: https://curtin.readthedocs.io/en/latest/topics/integration-testing.html In order to avoid regression to existing MAAS product, the MAAS team will run their continuous integration test against the curtin that is in -proposed. A successful run will be required before the proposed curtin can be let into -updates. The curtin team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. Curtin team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. - - + DONE: attach curtin-proposed test artifacts from vmtest for every SRU release + DONE: attach maas-proposed test artifacts from vmtest for every SRU release [Other Info] This SRU will be replacing the current version in -proposed (LP: #1795712) + [Discussion] - [Discussion] - == End SRU Template == - + == Changelog == curtin (18.2-10-g7afd77fa-0ubuntu1) disco; urgency=medium * New upstream snapshot. - Support for multi-layers images fsimage-layered:// URI [Jean-Baptiste Lallement] - dname: relax dname req for disk serial/wwn presence for compatibility - (LP: #1735839) - flake8: fix some E117 over-indented issues [Paride Legovini] - bcache: ensure partitions on bcache devices are detected as partition - vmtest: bump skip_by_date out a year for trusty bcache bug - Fix typo in doc/topics/integration-testing.rst. [Paride Legovini] - flake8: Fix two issues found with new version of flake8 - clear-holders: handle FileNotFound when probing for bcache device slaves - (LP: #187) - vmtests: network mtu fix-by bump to post 19.04 release - vmtest: Fix bug preventing explicit disabling of system_upgrade. -- Ryan Harper Wed, 27 Feb 2019 16:43:21 -0600 curtin (18.2-0ubuntu1) disco; urgency=medium * New upstream release (18.2). - Release 18.2 - Adjust helpers/common to edit GRUB_CMDLINE_LINUX_DEFAULT in place. (LP: #1527664) - dname: persistent names based on serial or wwn (LP: #1735839) - Fix bug in is_swap_device if a device was smaller than page_size. (LP: #1803672) - vmtest: add disco tests [Joshua Powers] - unittest: change directory to tmpdir for testing relative files. - Add clear-holders to meta-simple (LP: #1786736) - vmtests: check install log for Out of memory kernel messages and fail - unittest: correctly use tmpdir for my.img [Joshua Powers] (LP: #1803611) - block_meta: use wipe config when clearing partitions (LP: #1800153) - tests: fix vmtests for apt perserve_source_list changes - apt: Use new format apt config when writing preserve_sources_list. (LP: #1735950) - vmtests: multipath mount /home with nofail and validate in unittest - vmtests: fix common collect scripts to not exit failure. - vmtest: handle collect disk unpack failure - vmtests: dont use multiple subclasses in uefi 4k tests - vmtests: disable snapd/seeding to avoid boot hang - jenkins-runner: fix when using --filter only
[Bug 1819038] Re: [FFe] New upstream snapshot
** Changed in: cloud-init (Ubuntu) Status: Triaged => 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/1819038 Title: [FFe] New upstream snapshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819067] Re: cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 -> 18.5-45-g3554ffe8-0ubuntu1
** Changed in: cloud-init (Ubuntu Disco) 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/1819067 Title: cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 -> 18.5-45-g3554ffe8-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819067] Re: cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 -> 18.5-45-g3554ffe8-0ubuntu1
MAAS QA Results for cloud-init on Xenial ** Attachment added: "maas-sru-proposed-cloudinit-xenial.zip" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+attachment/5247649/+files/maas-sru-proposed-cloudinit-xenial.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819067 Title: cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 -> 18.5-45-g3554ffe8-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819067] Re: cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 -> 18.5-45-g3554ffe8-0ubuntu1
MAAS QA Results for cloud-init on Cosmic ** Attachment added: "maas-sru-proposed-cloudinit-cosmic.zip" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+attachment/5247651/+files/maas-sru-proposed-cloudinit-cosmic.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819067 Title: cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 -> 18.5-45-g3554ffe8-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819067] Re: cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 -> 18.5-45-g3554ffe8-0ubuntu1
MAAS QA Results for cloud-init on Bionic ** Attachment added: "maas-sru-proposed-cloudinit-bionic.zip" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+attachment/5247650/+files/maas-sru-proposed-cloudinit-bionic.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819067 Title: cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 -> 18.5-45-g3554ffe8-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820754] Re: bcache null pointer exception , recursive fault
Kernel oops when attempting to stop an online bcache device. ** Attachment added: "trusty-bcache-null.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820754/+attachment/5247406/+files/trusty-bcache-null.txt ** Tags added: curtin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820754 Title: bcache null pointer exception , recursive fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820754] [NEW] bcache null pointer exception , recursive fault
Public bug reported: 1) # cat /proc/version_signature Ubuntu 3.13.0-166.216-generic 3.13.11-ckt39 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-generic 3.13.0.167.178 ProcVersionSignature: Ubuntu 3.13.0-166.216-generic 3.13.11-ckt39 Uname: Linux 3.13.0-166-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 18 20:14 seq crw-rw 1 root audio 116, 33 Mar 18 20:14 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Mar 18 20:23:48 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=/dev/disk/by-id/virtio-boot-disk ds=nocloud-net;seedfrom=http://10.245.168.20:40373/ console=ttyS0 overlayroot=tmpfs ro systemd.mask=snapd.seeded.service systemd.mask=snapd.service iscsi_auto ip=:BOOTIF:dhcp BOOTIF=01-52-54-00-12-34-01 RelatedPackageVersions: linux-restricted-modules-3.13.0-166-generic N/A linux-backports-modules-3.13.0-166-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-disco dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-disco:cvnQEMU:ct1:cvrpc-i440fx-disco: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-disco dmi.sys.vendor: QEMU ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug curtin trusty uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820754 Title: bcache null pointer exception , recursive fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819067] Re: cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 -> 18.5-45-g3554ffe8-0ubuntu1
NoCloud Xenial, Bionic and Cosmic Manual test results. ** Attachment added: "nocloud-all-18.5-45-g3554ffe8-0ubuntu1.txt" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+attachment/5246599/+files/nocloud-all-18.5-45-g3554ffe8-0ubuntu1.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819067 Title: cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 -> 18.5-45-g3554ffe8-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819067] Re: cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 -> 18.5-45-g3554ffe8-0ubuntu1
OpenStack Xenial, Bionic, Cosmic manual test results. ** Attachment added: "openstack-sru-18.5-45-g3554ffe8-0ubuntu1.txt" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+attachment/5246598/+files/openstack-sru-18.5-45-g3554ffe8-0ubuntu1.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819067 Title: cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 -> 18.5-45-g3554ffe8-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819067] Re: cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 -> 18.5-45-g3554ffe8-0ubuntu1
GCE Xenial, Bionic and Cosmic manual test results! ** Attachment added: "gce-sru-18.5-45-g3554ffe8-0ubuntu1.txt" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+attachment/5246597/+files/gce-sru-18.5-45-g3554ffe8-0ubuntu1.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819067 Title: cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 -> 18.5-45-g3554ffe8-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819067] Re: cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 -> 18.5-45-g3554ffe8-0ubuntu1
Azure Xenial, Bionic and Cosmic Manual Test results ** Attachment added: "azure-sru-18.5-45-g3554ffe8-0ubuntu1.txt" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+attachment/5246593/+files/azure-sru-18.5-45-g3554ffe8-0ubuntu1.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819067 Title: cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 -> 18.5-45-g3554ffe8-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819067] Re: cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 -> 18.5-45-g3554ffe8-0ubuntu1
Xenial proposed automated testing of lxd, nocloud-kvm and ec2 platforms, 18.5-45-g3554ffe8-0ubuntu1_16.04.1. ** Attachment added: "cloud-init-integration-proposed-x-console.log" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+attachment/5246588/+files/cloud-init-integration-proposed-x-console.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819067 Title: cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 -> 18.5-45-g3554ffe8-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819067] Re: cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 -> 18.5-45-g3554ffe8-0ubuntu1
EC2 Xenial, Bionic and Cosmic manual test results. ** Attachment added: "ec2-sru-18.5-45-g3554ffe8-0ubuntu1.txt" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+attachment/5246592/+files/ec2-sru-18.5-45-g3554ffe8-0ubuntu1.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819067 Title: cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 -> 18.5-45-g3554ffe8-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819067] Re: cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 -> 18.5-45-g3554ffe8-0ubuntu1
Cosmic proposed automated testing of lxd, nocloud-kvm and ec2 platforms, 18.5-21-g8ee294d5-0ubuntu1_18.10.1 ** Attachment added: "cloud-init-integration-proposed-c-console.log" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+attachment/5246591/+files/cloud-init-integration-proposed-c-console.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819067 Title: cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 -> 18.5-45-g3554ffe8-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819067] Re: cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 -> 18.5-45-g3554ffe8-0ubuntu1
Bionic proposed automated testing of lxd, nocloud-kvm and ec2 platforms, 18.5-45-g3554ffe8-0ubuntu1_18.04.1 ** Attachment added: "cloud-init-integration-proposed-b-console.log" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+attachment/5246590/+files/cloud-init-integration-proposed-b-console.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819067 Title: cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 -> 18.5-45-g3554ffe8-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817964] Re: sru curtin 2019-02-27 - 18.2-10-g7afd77fa-0ubuntu1
Bionic curtin-proposed test log. Note there is one expected failure (DiscoAllindata); not a curtin issue (LP: #1818876) ** Attachment added: "curtin-vmtest-proposed-b-console.log" https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1817964/+attachment/5246220/+files/curtin-vmtest-proposed-b-console.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817964 Title: sru curtin 2019-02-27 - 18.2-10-g7afd77fa-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1817964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817964] Re: sru curtin 2019-02-27 - 18.2-10-g7afd77fa-0ubuntu1
Xenial MAAS QA artifacts. ** Attachment added: "maas-qa-sru-proposed-xenial-curtin-sru-manual.zip" https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1817964/+attachment/5246223/+files/maas-qa-sru-proposed-xenial-curtin-sru-manual.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817964 Title: sru curtin 2019-02-27 - 18.2-10-g7afd77fa-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1817964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817964] Re: sru curtin 2019-02-27 - 18.2-10-g7afd77fa-0ubuntu1
Cosmic curtin-proposed artifacts. ** Attachment added: "curtin-vmtest-proposed-c-artifacts.tar.xz" https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1817964/+attachment/5246219/+files/curtin-vmtest-proposed-c-artifacts.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817964 Title: sru curtin 2019-02-27 - 18.2-10-g7afd77fa-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1817964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817964] Re: sru curtin 2019-02-27 - 18.2-10-g7afd77fa-0ubuntu1
Bionic MAAS QA artifacts ** Attachment added: "maas-qa-sru-proposed-bionic-curtin-sru-manual.zip" https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1817964/+attachment/5246222/+files/maas-qa-sru-proposed-bionic-curtin-sru-manual.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817964 Title: sru curtin 2019-02-27 - 18.2-10-g7afd77fa-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1817964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817964] Re: sru curtin 2019-02-27 - 18.2-10-g7afd77fa-0ubuntu1
Cosmic curtin-proposed test log. Note there is one expected failure (DiscoAllindata); not a curtin issue (LP: #1818876) ** Attachment added: "curtin-vmtest-proposed-c-console.log" https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1817964/+attachment/5246218/+files/curtin-vmtest-proposed-c-console.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817964 Title: sru curtin 2019-02-27 - 18.2-10-g7afd77fa-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1817964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817964] Re: sru curtin 2019-02-27 - 18.2-10-g7afd77fa-0ubuntu1
Bionic curtin-proposed artifacts. ** Attachment added: "curtin-vmtest-proposed-b-artifacts.tar.xz" https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1817964/+attachment/5246221/+files/curtin-vmtest-proposed-b-artifacts.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817964 Title: sru curtin 2019-02-27 - 18.2-10-g7afd77fa-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1817964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780867] Re: hostname unchangeable / some daemon changes and resets /etc/hostname
subiquity is providing configuration to cloud-init to perform configuration on first boot already; cloud-init will happily do what it's told. I think there are several options on the configuration provided to cloud-init. Subiquity can provide the hostname statically into the image and not ask cloud-init to set the hostname. If subiquity did provide hostname to cloud-init, it will need to set the hostname config policy to perform this operation only once (per-once) and not the default (per-boot). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780867 Title: hostname unchangeable / some daemon changes and resets /etc/hostname To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1780867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815254] Re: Azure multiple ips prevent access to metadata service
OK, this is easily reproduced by adding a single static IP in the same subnet as the IP that comes from dhcp'ing on the interface. For example, if you launch an instance with a 10.0.0./24 subnet, the dhcp IP is something like 10.0.0.4 You can login and curl -H Metadata:true "http://169.254.169.254/metadata/instance/network ?api-version=2017-08-01" is successful. If you append: addresses: - 10.0.0.20/24 To /etc/netplan/50-cloud-init.yaml, like this: network: ethernets: eth0: addresses: - 10.0.0.20/24 dhcp4: true match: macaddress: 00:0d:3a:4e:c5:66 set-name: eth0 version: 2 And netplan apply; then the static ip is 'primary' on the interface and the dhcp ip is 'secondary' which results it the wrong source ip when connecting to the metadata services. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815254 Title: Azure multiple ips prevent access to metadata service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1815254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813346] Re: sru cloud-init (18.4.0 update to 18.5-21-g8ee294d5) Xenial, Bionic, Cosmic
** Description changed: == Begin SRU Template == [Impact] This release sports both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: - opennebula: incremental updates to exclude EPOCH* bash 5.0 env variables - lxd: install zfs-linux instead of zfs meta package - cc_set_passwords: Fix regex when parsing hashed passwords - net: Wait for dhclient to daemonize before reading lease file - [Azure] Increase retries when talking to Wireserver during metadata walk - ds-identify: fix wrong variable name in ovf_vmware_transport_guestinfo. - OVF: simplify expected return values of transport functions. - Vmware: Add support for the com.vmware.guestInfo OVF transport. - net: render 'metric' values in per-subnet routes - NoCloud: Allow top level 'network' key in network-config. - ovf: Fix ovf network config generation gateway/routes - azure: detect vnet migration via netlink media change event - OVF: identify label iso9660 filesystems with label 'OVF ENV'. - net: Ephemeral*Network: add connectivity check via URL - azure: _poll_imds only retry on 404. Fail on Timeout - azure: Accept variation in error msg from mount for ntfs volumes - azure: fix regression introduced when persisting ephemeral dhcp lease - azure: add udev rules to create cloud-init Gen2 disk name symlinks - azure: remove /etc/netplan/90-hotplug-azure.yaml when net from IMDS - azure: report ready to fabric after reprovision and reduce logging - instance-data: fallback to instance-data.json if sensitive is absent. - azure: Add apply_network_config option to disable network from IMDS - instance-data: Add standard keys platform and subplatform. Refactor ec2. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/CloudinitUpdates The cloud-init team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. cloud-init team members will not mark ‘verification-done’ until this has happened. * Automated Test Results DONE: attach automated cloud-init-proposed test artifacts sru-artifact-lxd-artful sru-artifact-lxc-xenial DONE: attach automated cloud-init-proposed test artifacts from tests for each release with kvm artifacts sru-artifact-kvm-artful sru-artifact-kvm-xenial DONE: attach Solutions Testing team test results for each LTS sru-artifact-solutions-qa-xenial DONE: attach MAAS Team test results for each LTS sru-artifact-maas-xenial * Manual Test Results DONE: attach manual cloud-init-proposed test artifacts from tests for each release on ec2 datasource sru-artifact-manual-ec2 - TODO: attach manual cloud-init-proposed test artifacts from tests for each release on gce datasource + DONE: attach manual cloud-init-proposed test artifacts from tests for each release on gce datasource sru-artifact-manual-gce DONE: attach manual cloud-init-proposed test artifacts from tests for each release on azure datasource sru-artifact-manual-azure [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. [Discussion] == End SRU Template == == Changelog == 18.5-21 - opennebula: also exclude epochseconds from changed environment vars - systemd: Render generator from template to account for system differences. [Robert Schweikert] - sysconfig: On SUSE, use STARTMODE instead of ONBOOT [Robert Schweikert] - flake8: use ==/!= to compare str, bytes, and int literals [Paride Legovini] 18.5-17 - opennebula: exclude EPOCHREALTIME as known bash env variable with a delta - tox: fix disco httpretty dependencies for py37 - run-container: uncomment baseurl in yum.repos.d/*.repo when using a proxy [Paride Legovini] - lxd: install zfs-linux instead of zfs meta package [Johnson Shi] - net/sysconfig: do not write a resolv.conf file with only the header. [Robert Schweikert] - net: Make sysconfig renderer compatible with Network Manager. [Eduardo Otubo] - cc_set_passwords: Fix regex when parsing hashed passwords [Marlin Cremers] - net: Wait for dhclient to daemonize before reading lease file [Jason Zions] - [Azure] Increase retries when talking to Wireserver during metadata walk [Jason Zions] - Add documentation on adding a datasource. - doc: clean up some datasource documentation. - ds-identify: fix wrong variable name in ovf_vmware_transport_guestinfo. - Scaleway: Support ssh keys provided inside an instance tag. [PORTE Loïc] - OVF: simplify
[Bug 1813346] Re: sru cloud-init (18.4.0 update to 18.5-21-g8ee294d5) Xenial, Bionic, Cosmic
GCE Xenial, Bionic and Cosmic Manual test results. ** Attachment added: "gce-sru-18.5.21.txt" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346/+attachment/5244180/+files/gce-sru-18.5.21.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813346 Title: sru cloud-init (18.4.0 update to 18.5-21-g8ee294d5) Xenial, Bionic, Cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813346] Re: sru cloud-init (18.4.0 update to 18.5-21-g8ee294d5) Xenial, Bionic, Cosmic
MAAS QA Xenial Test Results ** Attachment added: "sru-proposed-cloudinit-xenial.zip" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346/+attachment/5244177/+files/sru-proposed-cloudinit-xenial.zip ** Description changed: == Begin SRU Template == [Impact] This release sports both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: - opennebula: incremental updates to exclude EPOCH* bash 5.0 env variables - lxd: install zfs-linux instead of zfs meta package - cc_set_passwords: Fix regex when parsing hashed passwords - net: Wait for dhclient to daemonize before reading lease file - [Azure] Increase retries when talking to Wireserver during metadata walk - ds-identify: fix wrong variable name in ovf_vmware_transport_guestinfo. - OVF: simplify expected return values of transport functions. - Vmware: Add support for the com.vmware.guestInfo OVF transport. - net: render 'metric' values in per-subnet routes - NoCloud: Allow top level 'network' key in network-config. - ovf: Fix ovf network config generation gateway/routes - azure: detect vnet migration via netlink media change event - OVF: identify label iso9660 filesystems with label 'OVF ENV'. - net: Ephemeral*Network: add connectivity check via URL - azure: _poll_imds only retry on 404. Fail on Timeout - azure: Accept variation in error msg from mount for ntfs volumes - azure: fix regression introduced when persisting ephemeral dhcp lease - azure: add udev rules to create cloud-init Gen2 disk name symlinks - azure: remove /etc/netplan/90-hotplug-azure.yaml when net from IMDS - azure: report ready to fabric after reprovision and reduce logging - instance-data: fallback to instance-data.json if sensitive is absent. - azure: Add apply_network_config option to disable network from IMDS - instance-data: Add standard keys platform and subplatform. Refactor ec2. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/CloudinitUpdates The cloud-init team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. cloud-init team members will not mark ‘verification-done’ until this has happened. * Automated Test Results - TODO: attach automated cloud-init-proposed test artifacts + DONE: attach automated cloud-init-proposed test artifacts sru-artifact-lxd-artful sru-artifact-lxc-xenial - TODO: attach automated cloud-init-proposed test artifacts from tests for each release with kvm artifacts + DONE: attach automated cloud-init-proposed test artifacts from tests for each release with kvm artifacts sru-artifact-kvm-artful sru-artifact-kvm-xenial - TODO: attach Solutions Testing team test results for each LTS + DONE: attach Solutions Testing team test results for each LTS sru-artifact-solutions-qa-xenial - TODO: attach MAAS Team test results for each LTS + DONE: attach MAAS Team test results for each LTS sru-artifact-maas-xenial * Manual Test Results - TODO: attach manual cloud-init-proposed test artifacts from tests for each release on ec2 datasource + DONE: attach manual cloud-init-proposed test artifacts from tests for each release on ec2 datasource sru-artifact-manual-ec2 TODO: attach manual cloud-init-proposed test artifacts from tests for each release on gce datasource sru-artifact-manual-gce - TODO: attach manual cloud-init-proposed test artifacts from tests for each release on azure datasource + DONE: attach manual cloud-init-proposed test artifacts from tests for each release on azure datasource sru-artifact-manual-azure [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. [Discussion] == End SRU Template == == Changelog == 18.5-21 - opennebula: also exclude epochseconds from changed environment vars - systemd: Render generator from template to account for system differences. [Robert Schweikert] - sysconfig: On SUSE, use STARTMODE instead of ONBOOT [Robert Schweikert] - flake8: use ==/!= to compare str, bytes, and int literals [Paride Legovini] 18.5-17 - opennebula: exclude EPOCHREALTIME as known bash env variable with a delta - tox: fix disco httpretty dependencies for py37 - run-container: uncomment baseurl in yum.repos.d/*.repo when using a proxy [Paride Legovini] - lxd: install zfs-linux instead of zfs meta package [Johnson Shi] - net/sysconfig: do not write a resolv.conf file with only the header. [Robert Schweikert] - net: Make sysconfig renderer compatible with Network
[Bug 1813346] Re: sru cloud-init (18.4.0 update to 18.5-21-g8ee294d5) Xenial, Bionic, Cosmic
MAAS QA Bionic test results ** Attachment added: "sru-proposed-cloudinit-bionic.zip" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346/+attachment/5244175/+files/sru-proposed-cloudinit-bionic.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813346 Title: sru cloud-init (18.4.0 update to 18.5-21-g8ee294d5) Xenial, Bionic, Cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813346] Re: sru cloud-init (18.4.0 update to 18.5-21-g8ee294d5) Xenial, Bionic, Cosmic
Azure Xenial, Bionic and Cosmic Manual Test results ** Attachment added: "azure-sru-18.5.21.txt" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346/+attachment/5244173/+files/azure-sru-18.5.21.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813346 Title: sru cloud-init (18.4.0 update to 18.5-21-g8ee294d5) Xenial, Bionic, Cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813346] Re: sru cloud-init (18.4.0 update to 18.5-21-g8ee294d5) Xenial, Bionic, Cosmic
OpenStack Xenial, Bionic and Cosmic Manual test results. ** Attachment added: "openstack-sru-18.5.21.txt" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346/+attachment/5244174/+files/openstack-sru-18.5.21.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813346 Title: sru cloud-init (18.4.0 update to 18.5-21-g8ee294d5) Xenial, Bionic, Cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813346] Re: sru cloud-init (18.4.0 update to 18.5-21-g8ee294d5) Xenial, Bionic, Cosmic
Bionic proposed automated testing of lxd, nocloud-kvm and ec2 platforms, 18.5-21-g8ee294d5-0ubuntu1_18.04.1 ** Attachment added: "cloud-init-integration-proposed-b-console.log" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346/+attachment/5244089/+files/cloud-init-integration-proposed-b-console.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813346 Title: sru cloud-init (18.4.0 update to 18.5-21-g8ee294d5) Xenial, Bionic, Cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813346] Re: sru cloud-init (18.4.0 update to 18.5-21-g8ee294d5) Xenial, Bionic, Cosmic
Cosmic proposed automated testing of lxd, nocloud-kvm and ec2 platforms 18.5-21-g8ee294d5-0ubuntu1_18.10.1 ** Attachment added: "cloud-init-integration-proposed-c-console.log" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346/+attachment/5244090/+files/cloud-init-integration-proposed-c-console.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813346 Title: sru cloud-init (18.4.0 update to 18.5-21-g8ee294d5) Xenial, Bionic, Cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813346] Re: sru cloud-init (18.4.0 update to 18.5-21-g8ee294d5) Xenial, Bionic, Cosmic
EC2 Xenial, Bionic and Cosmic manual test results. ** Attachment added: "ec2-sru-18.5.21.txt" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346/+attachment/5244091/+files/ec2-sru-18.5.21.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813346 Title: sru cloud-init (18.4.0 update to 18.5-21-g8ee294d5) Xenial, Bionic, Cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813346] Re: sru cloud-init (18.4.0 update to 18.5-21-g8ee294d5) Xenial, Bionic, Cosmic
Xenial proposed automated testing of lxd, nocloud-kvm and ec2 platforms, 18.5-21-g8ee294d5-0ubuntu1_16.04.1 ** Attachment added: "cloud-init-integration-proposed-x-console.log" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346/+attachment/5244088/+files/cloud-init-integration-proposed-x-console.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813346 Title: sru cloud-init (18.4.0 update to 18.5-21-g8ee294d5) Xenial, Bionic, Cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796977] Re: Ubuntu 18.04 server installation fails
** Changed in: curtin 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/1796977 Title: Ubuntu 18.04 server installation fails To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1796977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655440] Re: "unconfigured" NIC can still get IPv6 addresses via RA
Curtin will pass the MAAS provided network config to the target. In netplan format, the accept-ra configuration is present and this will be passed through to the target system and reflected in the installed system. I'm marking the curtin portion here invalid. If curtin does need to do something (for say xenial deployments/ifupdown) then please re-open the task and we'll triage accordingly. ** Changed in: curtin 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/1655440 Title: "unconfigured" NIC can still get IPv6 addresses via RA To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1655440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796977] Re: Ubuntu 18.04 server installation fails
This looks like an issue with the installer. I've added the package to this bug. ** Also affects: subiquity (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/1796977 Title: Ubuntu 18.04 server installation fails To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1796977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809529] Re: Shimx64 does not know how to interact with unsecured efi bios
Hello, I added the shim package to this bug as it appears that your issue is related to the shim rather than curtin. If you believe that curtin is related to your issue, please provide additional details about how curtin is involved in your scenario. ** Also affects: shim (Ubuntu) Importance: Undecided Status: New ** Changed in: curtin 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/1809529 Title: Shimx64 does not know how to interact with unsecured efi bios To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1809529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
