[Bug 1087526] Re: need support for gpt partition tables
fixed in 0.28 ** Changed in: cloud-utils Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1087526 Title: need support for gpt partition tables To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-utils/+bug/1087526/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1302052] Re: mount-image-callback : --dev, --sys, --proc do not work
fixed in 0.28 ** Changed in: cloud-utils Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-utils in Ubuntu. https://bugs.launchpad.net/bugs/1302052 Title: mount-image-callback : --dev, --sys, --proc do not work To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-utils/+bug/1302052/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1303786] Re: ubuntu-ec2-run stack trace
fixed in 0.28 ** Changed in: cloud-utils Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-utils in Ubuntu. https://bugs.launchpad.net/bugs/1303786 Title: ubuntu-ec2-run stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-utils/+bug/1303786/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1259703] Re: growpart on disk larger than 2TB fails
fixed in 0.28 ** Changed in: cloud-utils Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-utils in Ubuntu. https://bugs.launchpad.net/bugs/1259703 Title: growpart on disk larger than 2TB fails To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-utils/+bug/1259703/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1492386] Re: mount-image-callback: must specify format to qemu-nbd
fixed in 0.28 ** Changed in: cloud-utils Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-utils in Ubuntu. https://bugs.launchpad.net/bugs/1492386 Title: mount-image-callback: must specify format to qemu-nbd To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-utils/+bug/1492386/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 641651] Re: uec-query-builds: error: unable to open /etc/cloud/build.info
we no logner use that cron job. ** Changed in: cloud-utils (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-utils in Ubuntu. https://bugs.launchpad.net/bugs/641651 Title: uec-query-builds: error: unable to open /etc/cloud/build.info To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-utils/+bug/641651/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1055211] Re: cloud-run-instances crashed with SyntaxError in unknown(): invalid syntax
** Changed in: cloud-utils (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-utils in Ubuntu. https://bugs.launchpad.net/bugs/1055211 Title: cloud-run-instances crashed with SyntaxError in unknown(): invalid syntax To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-utils/+bug/1055211/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1083183] Re: cloud-utils should recommend qemu-utils
cloud-image-utils was split out, now it depends on qemu-utils and genisoimage. ** Changed in: cloud-utils Status: Triaged => Fix Released ** Changed in: cloud-utils (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-utils in Ubuntu. https://bugs.launchpad.net/bugs/1083183 Title: cloud-utils should recommend qemu-utils To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-utils/+bug/1083183/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 785911] Re: uec-publish-tarball does not take a "--config" parameter
marking this wont-fix. this tool has kind of been deprecated. i would take a well done patch though. ** Changed in: cloud-utils (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-utils in Ubuntu. https://bugs.launchpad.net/bugs/785911 Title: uec-publish-tarball does not take a "--config" parameter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-utils/+bug/785911/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1499600] Re: growpart can't resize partition with two digits
I'm pretty sure this is fixed. I've just tried partitioning a disk with gpt and 11 partitions on xenial and then run $ sudo growpart /dev/vdb 11 sudo: unable to resolve host xenial-20160510-175548 CHANGED: partition=11 start=206848 old: size=204800 end=411648 new: size=83679199,end=83886047 please feel free to re-open if you think otherwise. ** Changed in: cloud-utils (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-utils in Ubuntu. https://bugs.launchpad.net/bugs/1499600 Title: growpart can't resize partition with two digits To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-utils/+bug/1499600/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1252436] Re: ubuntu-cloudimg-query don't know about saucy
fix released in 0.28. Also, the suggestion is to have distro-info (it is Recommends). ** Changed in: cloud-utils (Ubuntu) Status: New => Fix Released ** Changed in: cloud-utils (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-utils in Ubuntu. https://bugs.launchpad.net/bugs/1252436 Title: ubuntu-cloudimg-query don't know about saucy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-utils/+bug/1252436/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1577872] Re: [SRU] curtin in yakkety to supported releases
** Description changed: + == Begin SRU Template == + [Impact] + This update to curtin is required to support features of MAAS 1.9 that is being SRU'd to trusty and wily under bug 1509147. There are also numerous bug fixes that affect the code path used with older maas as well. See the changelog entry below for a full list. + + Changes to wily and xenial much more bug fix only. + + [Test Case] + The test case is really MAAS 1.9 functionality. The MAAS bug 1509147 should include methods for verifying this. + + For curtin's part, curtin now contains fairly extensive continuous integration test on trunk. + Those results can be seen at https://server-team-jenkins.canonical.com/job/curtin-vmtest-venonat/ . + + + [Regression Potential] + The chance for regression here is most likely in using curtin with an older MAAS release. + + + [Other Info] + The version of curtin here is completely backwards compatible with previous versions of MAAS and previous versions of curtin. Specifically a user could take curtin update without MAAS 1.9 SRU to trusty and be fine. + + There are dramatic changes to curtin between the version in 14.04 and + what is being SRU'd. This will no doubt be alarming to a user. + However, there has been extensive work on improving curtin's test suite + both in actual install tests in a VM and in uniti tests. + + == End SRU Template == + + In order to support MAAS sru of 1.9 into trusty, we need a newer version of curtin. Below is the combined debian changelog. - * debian/new-upstream-snapshot, debian/README.source: add - new-upstream-snapshot and mention it in README.source - * debian/control: drop python from curtin-common Depends. - remove unnecessary Depends on util-linux as it is essential. - python3-curtin, python-curtin: drop unnecessary 'curl' from Depends. - python3-curtin, python-curtin: list oauthlib and yaml Depends - * debian/control: add bcache-tools to curtin Depends. - * New upstream snapshot. - - fix timestamp not being updated in reported events - - mdadm: resolve mdadm/bcache and trusty+hwe issues (LP: #1569549, LP: #1514094) - - fix support for 4k disks (LP: #1436632, LP: #1564977) - - emit source /etc/network/interfaces.d/*.cfg in - rendered /etc/network/interfaces - - net: introduce 'control' field to network configuration to allow - for declaring manual controlled interfaces - - disable cloud-init networking as curtin is the source of network config - - block: wipe_volume improvements - - reporter: enhance reporting events to include levels and - improve usefullness of messages - - network: add bonding tests and cleanup newline rendering - - block: fix partition path issue with nvme devices - - fix logic error in kernel installation - - block: add debug regarding raid modules being missing on mdadm create - - add s390x support to curtin and vmtest + * debian/new-upstream-snapshot, debian/README.source: add + new-upstream-snapshot and mention it in README.source + * debian/control: drop python from curtin-common Depends. + remove unnecessary Depends on util-linux as it is essential. + python3-curtin, python-curtin: drop unnecessary 'curl' from Depends. + python3-curtin, python-curtin: list oauthlib and yaml Depends + * debian/control: add bcache-tools to curtin Depends. + * New upstream snapshot. + - fix timestamp not being updated in reported events + - mdadm: resolve mdadm/bcache and trusty+hwe issues (LP: #1569549, LP: #1514094) + - fix support for 4k disks (LP: #1436632, LP: #1564977) + - emit source /etc/network/interfaces.d/*.cfg in + rendered /etc/network/interfaces + - net: introduce 'control' field to network configuration to allow + for declaring manual controlled interfaces + - disable cloud-init networking as curtin is the source of network config + - block: wipe_volume improvements + - reporter: enhance reporting events to include levels and + improve usefullness of messages + - network: add bonding tests and cleanup newline rendering + - block: fix partition path issue with nvme devices + - fix logic error in kernel installation + - block: add debug regarding raid modules being missing on mdadm create + - add s390x support to curtin and vmtest [Wily and Trusty < revno 365] - - support build on xenial where python3 pyflakes is split out - (LP: #1471928) - - fix uefi install path on nvme devices - - numerous unit tests and vmtests improvements. Add running - of pylint for static checking. - - Add bond parsing & improved source, source-directory parsing - of /etc/network/interfaces. (LP: #1536262) - - move global dns-* options under auto lo in /etc/network/interfaces - - partitioning: limited support for odd ordering of partition numbers - (LP: #1543263) - - change use of mkfs.fat to
[Bug 1577872] Re: [SRU] curtin in yakkety to supported releases
I've just uploaded 0.1.0~bzr387-0ubuntu1~YY.MM.1 to each xenial wily and trusty. yakkety does not yet have 387 due to LP: #1560134. ** Description changed: - In order to support MAAS sru of 1.9 into trusty, we need a newer version - of curtin. + In order to support MAAS sru of 1.9 into trusty, we need a newer version of curtin. + Below is the combined debian changelog. - * debian/new-upstream-snapshot, debian/README.source: add - new-upstream-snapshot and mention it in README.source - * debian/control: adjust build dependency as python3-pyflakes in xenial - now provides python3 modules for pyflakes. - * debian/control: wrap-and-sort - * debian/control: list all dependencies of curtin package - * debian/control: change curtin's depend from python-curtin to - python3-curtin. - * debian/control: add python-oauthlib and python3-oauthlib dependency + * debian/new-upstream-snapshot, debian/README.source: add + new-upstream-snapshot and mention it in README.source * debian/control: drop python from curtin-common Depends. remove unnecessary Depends on util-linux as it is essential. python3-curtin, python-curtin: drop unnecessary 'curl' from Depends. - python3-curtin, python-curtin: list oauthlib and yaml explicitly - * New upstream snapshot. - - support build on xenial where python3 pyflakes is split out - - fix uefi install path on nvme devices (LP: #1471928) - - numerous unit tests and vmtests improvements. Add running - of pylint for static checking. - - Add bond parsing & improved source, source-directory parsing - of /etc/network/interfaces. - - move global dns-* options under auto lo in - /etc/network/interfaces (LP: #1536262) - - partitioning: limited support for odd ordering of partition numbers - (LP: #1543263) - - change use of mkfs.fat to mkfs.vfat and add dependency. - (LP: #1539720) - - block-meta: use removable devices if no non-removable devices are - found (LP: #1532062) [Robert Clark] - - Improve 'curtin mkfs' and move mkfs logic to block.mkfs fixes - using btrfs on precise and trusty. - - fix failures caused by systems with invalid system_clock (LP: #1520400) - - support bcache installation on precise (LP: #1449099) - - fix bug in install_grub to partition when storage_config provided - fixing lvm installation on power8 (LP: #1523779). - - block_meta: handle 'preserve' flag for raid devices (LP: #1522147) - - close file descriptors from --config= arguments - - xenial: disable update-motd during an apt-get update - - subp: add decode parameter, defaulting to replace. - this fixes errors when output of a command had non-utf chars - (LP: #1526127) - - support passing an integer or valid float to human2bytes - - Use /proc/mounts to find missing mountpoints rather than relying - entirely on lsblk as lsblk differs widely between ubuntu releases. - - support extracting tar files compressed with xz or bzip or - uncompressed. Previously required gzip compression. - - Improve dependency checking and installation (LP: #1514888) - this fixes curtin running on precise and installing dependencies - it needs. - - Reduce chance udev race with mdadm opening /dev/mdX (LP: #1512857) - - Allow re-use of bcache cache devices with separate backing devices - (LP: #1514094) - - invoke mkfs.ext3 or mkfs.ext4 with -F to fix issues found if - target device had a filesystem already present. - - Partition alignment and sizing fixes (LP: #1513085) - - Set bcache cache_mode if present in storage config (LP: #1510334) - - when apt-get update is called during installation, do not download - translation files and source files, reducing chances for mismatch. - - add system-install sub command. 'curtin system-install pastebinit' - will install packages in a way guaranteed to not prompt. - - add 'system-upgrade' command and config to easily update the - system after installation before reboot. (LP: #1481992) - - fix reporting of FAIL when a subcommand used sys.exit(0) - - grub-install: if fail to find mounted uefi partition, give more - debug output - - network config: add support for dns-search key in subnet and search - in nameserver - - Ensure required networking packages are installed in the target. - (LP: #1491994) - - stop grub from going into graphical/vga mode on installed systems - - curthooks: support specifying kernel/package without mapping - - ChrootableTarget: do not attempt to change resolv.conf if - there is no /etc directory - - list the set of features that curtin has for library users. - users can now check the FEATURES list for a specific feature. - - fix bug in argument parsing --set mykey=foo=bar - - in-target: add '--capture' to in-target and special case
[Bug 1515780] Re: bcache does not work with suspend
## This uses qemu and a maas image to easily test bcache of a root disk
## on a vm. Originally put together for bug 1515780
## It does:
## * downloads a maas image, kernel and initramfs
## * and makes a disk with 1M in front for the bcache header (root.img)
## * creates a disk for cache image (cache0.img)
## * puts a bcache header on the root.img pointing to cache disk by cset uuid
## * boots system with uuid of root filesystem
##
## once booted you can login with 'ubuntu:passw0rd' (from the user-data above)
## suspend with:
## sudo systemctl suspend
## unsuspend with:
##'system_wakeup'
## to issue system_wakeup you need to get to qemu monitor.
## in nographic mode you you toggle between console and qemu monitor with
## the provided 'escape char' (-echr) and 'c'
$ wget
http://images.maas.io/ephemeral-v2/daily/xenial/amd64/20160509/root-image.gz
$ wget
http://images.maas.io/ephemeral-v2/daily/xenial/amd64/20160509/xenial/generic/boot-initrd
$ wget
http://images.maas.io/ephemeral-v2/daily/xenial/amd64/20160509/xenial/generic/boot-kernel
$ sudo apt-get install bcache-tools
## set up the cache disk
$ truncate --size 500M cache0.img
$ make-bcache --cache --writeback cache0.img
UUID: 48320c10-9065-40e1-93cc-d020861e2070
Set UUID: 1d997f00-4d73-40d6-9a09-c9192bf6aed2
version:0
nbuckets: 1000
block_size: 8
bucket_size:1024
nr_in_set: 1
nr_this_dev:0
first_bucket: 1
$ cset_uuid=$(bcache-super-show cache0.img | awk '$1 == "cset.uuid" { print $2
}')
$ echo $cset_uuid
1d997f00-4d73-40d6-9a09-c9192bf6aed2
## setup primary disk
$ truncate --size=1M root.img
$ zcat root-image.gz >> root.img
# 2048 is 1M / 512B sectors
$ make-bcache --bdev --data-offset=2048 "--cset-uuid=${cset_uuid}" root.img
# 1M here is same as our truncate. get the UUID of the filesystem.
$ uuid=$(blkid -p -o export -O 1M root.img | awk -F= '$1 == "UUID" { print $2
}')
## set up a seed disk
$ cat > user-data
[Bug 1515780] Re: bcache does not work with suspend
** Attachment added: "suggested /lib/systemd/system-sleep/bcache.sh" https://bugs.launchpad.net/debian/+source/bcache-tools/+bug/1515780/+attachment/4659445/+files/bcache.sh -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bcache-tools in Ubuntu. https://bugs.launchpad.net/bugs/1515780 Title: bcache does not work with suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1515780/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1515780] Re: bcache does not work with suspend
** Bug watch added: Debian Bug tracker #823860 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823860 ** Also affects: bcache-tools (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823860 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bcache-tools in Ubuntu. https://bugs.launchpad.net/bugs/1515780 Title: bcache does not work with suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1515780/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1577844] Re: Drop unnecessary blocking of all net udev rules
** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1577844 Title: Drop unnecessary blocking of all net udev rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1577844/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1579130] Re: need to support systemd.link renaming of devices in container
** Description changed: We're interested in supporting network configuration of lxc containers via maas/cloud-init yaml format. The end goal is to do: $ lxc init xenial x1 # enter into container and modify /var/lib/cloud/seed/nocloud-net/network-config # to have something like: % cat /var/lib/cloud/seed/nocloud-net/network-config version: 1 config: - - type: physical - mac_address: "00:16:3e:3b:01:7a" - name: foo2 - subnets: - - type: dhcp - control: auto + - type: physical + mac_address: "00:16:3e:3b:01:7a" + name: foo2 + subnets: + - type: dhcp + control: auto $ lxc start x1 $ lxc exec x1 /bin/bash From inside we expect to have a device named 'foo2' at this point that has dhcp'd. + + We've run into a number of issues with this. + a.) we don't get coldplug events for devices in a container, so writing systemd.link (or 70-persistent-net.rules style udev rules files) wont "just work" to apply the name changes. + + b.) systemd.link does rename devices that have been renamed previously, and all lxd instance devices are renamed (from the kernel returned veth into 'eth0'). + That is implemented by check of /sys/devices/virtual/net/eth0/name_assign_type . Value of 4 means renamed. + + c.) systemd.link will not attempt to rename a device that does not have a driver. +To see that run: udevadm test-builtin net_setup_link /sys/class/net/eth0 +http://paste.ubuntu.com/16261974/ + + To force these systemd.link files to run in spite of 'b' on kvm guests + or bare metal, we have found that unbind and rebind of the device will + clear the state and rename would occur. that can be done as shown in + https://bugs.launchpad.net/ubuntu/+source/cloud- + init/+bug/1577844/comments/3 but since there is no 'driver' we cannot + unbind and rebind veth devices. + + Ultimately, we want to allow cloud-init to configure the system once and + then let renaming on reboots not require involvement of cloud-init. And + at the moment the ideal way to affect that would be through systemd.link + files such as /etc/systemd/network/50-cloud-init-foo2.link. + ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Fri May 6 15:42:52 2016 MachineType: LENOVO 33672B7 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) + TERM=xterm-256color + PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=19ac97d5-6973-4193-9a09-2e6bbfa38262 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G8ET96WW (2.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 33672B7 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG8ET96WW(2.56):bd12/18/2013:svnLENOVO:pn33672B7:pvrThinkPadX131e:rvnLENOVO:rn33672B7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 33672B7 dmi.product.version: ThinkPad X131e dmi.sys.vendor: LENOVO ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu) Importance: Undecided => High ** Description changed: We're interested in supporting network configuration of lxc containers via maas/cloud-init yaml format. The end goal is to do: $ lxc init xenial x1 # enter into container and modify /var/lib/cloud/seed/nocloud-net/network-config # to have something like: - % cat /var/lib/cloud/seed/nocloud-net/network-config + $ ncpath=/var/lib/cloud/seed/nocloud-net/network-config + $ sudo tee /var/lib/lxd/containers/x1/rootfs/$ncpath < into 'eth0'). - That is implemented by check of /sys/devices/virtual/net/eth0/name_assign_type . Value of 4 means renamed. + a.) we don't get coldplug events for devices in a container, so writing systemd.link (or 70-persistent-net.rules style udev rules files) wont "just work" to apply the name changes. - c.) systemd.link will not attempt to rename a device that does not have a driver. -To see that run: udevadm test-builtin net_setup_link /sys/class/net/eth0 -http://paste.ubuntu.com/16261974/ + b.) systemd.link does rename devices that have been renamed previously, and all lxd instance devices are renamed (from the kernel returned veth into 'eth0'). + That is implemented by check of /sys/devices/virtual/net/eth0/name_assign_type . Value of 4 means renamed. + + c.) systemd.link will not attempt to rename a device that does not have a d
[Bug 1577872] Re: [SRU] yakkety curtin to trusty and xenial
** Summary changed: - [SRU] xenial curtin to trusty + [SRU] yakkety curtin to trusty and xenial ** Also affects: curtin (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: curtin (Ubuntu Xenial) Status: New => Confirmed ** Changed in: curtin (Ubuntu Xenial) Importance: Undecided => Medium ** Summary changed: - [SRU] yakkety curtin to trusty and xenial + [SRU] curtin in yakkety to supported releases ** Description changed: In order to support MAAS sru of 1.9 into trusty, we need a newer version of curtin. - * debian/new-upstream-snapshot, debian/README.source: add - new-upstream-snapshot and mention it in README.source - * debian/control: adjust build dependency as python3-pyflakes in xenial - now provides python3 modules for pyflakes. - * debian/control: wrap-and-sort - * debian/control: list all dependencies of curtin package - * debian/control: change curtin's depend from python-curtin to - python3-curtin. - * debian/control: add python-oauthlib and python3-oauthlib dependency - * New upstream snapshot. - - support build on xenial where python3 pyflakes is split out - - fix uefi install path on nvme devices (LP: #1471928) - - numerous unit tests and vmtests improvements. Add running - of pylint for static checking. - - Add bond parsing & improved source, source-directory parsing - of /etc/network/interfaces. - - move global dns-* options under auto lo in - /etc/network/interfaces (LP: #1536262) - - partitioning: limited support for odd ordering of partition numbers - (LP: #1543263) - - change use of mkfs.fat to mkfs.vfat and add dependency. - (LP: #1539720) - - block-meta: use removable devices if no non-removable devices are - found (LP: #1532062) [Robert Clark] - - Improve 'curtin mkfs' and move mkfs logic to block.mkfs fixes - using btrfs on precise and trusty. - - fix failures caused by systems with invalid system_clock (LP: #1520400) - - support bcache installation on precise (LP: #1449099) - - fix bug in install_grub to partition when storage_config provided - fixing lvm installation on power8 (LP: #1523779). - - block_meta: handle 'preserve' flag for raid devices (LP: #1522147) - - close file descriptors from --config= arguments - - xenial: disable update-motd during an apt-get update - - subp: add decode parameter, defaulting to replace. - this fixes errors when output of a command had non-utf chars - (LP: #1526127) - - support passing an integer or valid float to human2bytes - - Use /proc/mounts to find missing mountpoints rather than relying - entirely on lsblk as lsblk differs widely between ubuntu releases. - - support extracting tar files compressed with xz or bzip or - uncompressed. Previously required gzip compression. - - Improve dependency checking and installation (LP: #1514888) - this fixes curtin running on precise and installing dependencies - it needs. - - Reduce chance udev race with mdadm opening /dev/mdX (LP: #1512857) - - Allow re-use of bcache cache devices with separate backing devices - (LP: #1514094) - - invoke mkfs.ext3 or mkfs.ext4 with -F to fix issues found if - target device had a filesystem already present. - - Partition alignment and sizing fixes (LP: #1513085) - - Set bcache cache_mode if present in storage config (LP: #1510334) - - when apt-get update is called during installation, do not download - translation files and source files, reducing chances for mismatch. - - add system-install sub command. 'curtin system-install pastebinit' - will install packages in a way guaranteed to not prompt. - - add 'system-upgrade' command and config to easily update the - system after installation before reboot. (LP: #1481992) - - fix reporting of FAIL when a subcommand used sys.exit(0) - - grub-install: if fail to find mounted uefi partition, give more - debug output - - network config: add support for dns-search key in subnet and search - in nameserver - - Ensure required networking packages are installed in the target. - (LP: #1491994) - - stop grub from going into graphical/vga mode on installed systems - - curthooks: support specifying kernel/package without mapping - - ChrootableTarget: do not attempt to change resolv.conf if - there is no /etc directory - - list the set of features that curtin has for library users. - users can now check the FEATURES list for a specific feature. - - fix bug in argument parsing --set mykey=foo=bar - - in-target: add '--capture' to in-target and special case target=/ - - support declaring json in --set argument via --set=json:... - - add reporting function to allow calling a webhook endpoint - with status of curtin install. - - Allow partprobe to return 1
[Bug 1578622] [NEW] glance do not require hypervisor_mapping
Public bug reported: currently the glance mirror requires hypervisor_mapping config in the api. Better to not required that as a library consumer would not necessarily provide it. ** Affects: simplestreams Importance: Medium Status: Fix Committed ** Affects: simplestreams (Ubuntu) Importance: Medium Status: Confirmed ** Affects: simplestreams (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Affects: simplestreams (Ubuntu Yakkety) Importance: Medium Status: Confirmed ** Package changed: ubuntu => simplestreams (Ubuntu) ** Changed in: simplestreams (Ubuntu) Importance: Undecided => Medium ** Changed in: simplestreams (Ubuntu) Status: New => Confirmed ** Also affects: simplestreams Importance: Undecided Status: New ** Changed in: simplestreams Importance: Undecided => Medium ** Changed in: simplestreams Status: New => Fix Committed ** Also affects: simplestreams (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: simplestreams (Ubuntu Yakkety) Importance: Medium Status: Confirmed ** Also affects: simplestreams (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: simplestreams (Ubuntu Xenial) Status: New => Confirmed ** Changed in: simplestreams (Ubuntu Trusty) Status: New => Confirmed ** Changed in: simplestreams (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: simplestreams (Ubuntu Xenial) Importance: Undecided => Medium ** Also affects: simplestreams (Ubuntu Wily) Importance: Undecided Status: New ** Changed in: simplestreams (Ubuntu Wily) Status: New => Confirmed ** Changed in: simplestreams (Ubuntu Wily) Importance: Undecided => Medium ** No longer affects: simplestreams (Ubuntu Wily) ** No longer affects: simplestreams (Ubuntu Trusty) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to simplestreams in Ubuntu. https://bugs.launchpad.net/bugs/1578622 Title: glance do not require hypervisor_mapping To manage notifications about this bug go to: https://bugs.launchpad.net/simplestreams/+bug/1578622/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1578624] [NEW] set custom user agent
Public bug reported: In order for web service to aggregate custom logs, simplestreams client should identify itself via user-agent. ** Affects: simplestreams Importance: Medium Status: Fix Committed ** Affects: simplestreams (Ubuntu) Importance: Medium Status: Confirmed ** Affects: simplestreams (Ubuntu Trusty) Importance: Medium Status: Confirmed ** Affects: simplestreams (Ubuntu Wily) Importance: Medium Status: Confirmed ** Affects: simplestreams (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Affects: simplestreams (Ubuntu Yakkety) Importance: Medium Status: Confirmed ** Also affects: simplestreams (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: simplestreams (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: simplestreams (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: simplestreams (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: simplestreams Importance: Undecided Status: New ** Changed in: simplestreams (Ubuntu Trusty) Status: New => Confirmed ** Changed in: simplestreams (Ubuntu Wily) Status: New => Confirmed ** Changed in: simplestreams (Ubuntu Xenial) Status: New => Confirmed ** Changed in: simplestreams (Ubuntu Yakkety) Status: New => Confirmed ** Changed in: simplestreams (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: simplestreams (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: simplestreams (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: simplestreams (Ubuntu Yakkety) Importance: Undecided => Medium ** Changed in: simplestreams Importance: Undecided => Medium ** Changed in: simplestreams Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to simplestreams in Ubuntu. https://bugs.launchpad.net/bugs/1578624 Title: set custom user agent To manage notifications about this bug go to: https://bugs.launchpad.net/simplestreams/+bug/1578624/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1577844] Re: Drop unnecessary blocking of all net udev rules
some futher thought one reason for the blocking of udev was to have the .link files that cloud-init wrote apply. It turns out that systemd.link will only rename devices once (based on a property in the devices /sys that says it has been renamed). So, for cloud-init to have these apply we will probably have to unbind and bind the device to clear that. that will also generate a hotplug event to get the device changed. http://paste.ubuntu.com/16220589/ ** Attachment added: "unlink and relink script" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1577844/+attachment/4655826/+files/unlink-link-dev -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1577844 Title: Drop unnecessary blocking of all net udev rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1577844/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1577872] [NEW] [SRU] xenial curtin to trusty
Public bug reported: In order to support MAAS sru of 1.9 into trusty, we need a newer version of curtin. * debian/new-upstream-snapshot, debian/README.source: add new-upstream-snapshot and mention it in README.source * debian/control: adjust build dependency as python3-pyflakes in xenial now provides python3 modules for pyflakes. * debian/control: wrap-and-sort * debian/control: list all dependencies of curtin package * debian/control: change curtin's depend from python-curtin to python3-curtin. * debian/control: add python-oauthlib and python3-oauthlib dependency * New upstream snapshot. - support build on xenial where python3 pyflakes is split out - fix uefi install path on nvme devices (LP: #1471928) - numerous unit tests and vmtests improvements. Add running of pylint for static checking. - Add bond parsing & improved source, source-directory parsing of /etc/network/interfaces. - move global dns-* options under auto lo in /etc/network/interfaces (LP: #1536262) - partitioning: limited support for odd ordering of partition numbers (LP: #1543263) - change use of mkfs.fat to mkfs.vfat and add dependency. (LP: #1539720) - block-meta: use removable devices if no non-removable devices are found (LP: #1532062) [Robert Clark] - Improve 'curtin mkfs' and move mkfs logic to block.mkfs fixes using btrfs on precise and trusty. - fix failures caused by systems with invalid system_clock (LP: #1520400) - support bcache installation on precise (LP: #1449099) - fix bug in install_grub to partition when storage_config provided fixing lvm installation on power8 (LP: #1523779). - block_meta: handle 'preserve' flag for raid devices (LP: #1522147) - close file descriptors from --config= arguments - xenial: disable update-motd during an apt-get update - subp: add decode parameter, defaulting to replace. this fixes errors when output of a command had non-utf chars (LP: #1526127) - support passing an integer or valid float to human2bytes - Use /proc/mounts to find missing mountpoints rather than relying entirely on lsblk as lsblk differs widely between ubuntu releases. - support extracting tar files compressed with xz or bzip or uncompressed. Previously required gzip compression. - Improve dependency checking and installation (LP: #1514888) this fixes curtin running on precise and installing dependencies it needs. - Reduce chance udev race with mdadm opening /dev/mdX (LP: #1512857) - Allow re-use of bcache cache devices with separate backing devices (LP: #1514094) - invoke mkfs.ext3 or mkfs.ext4 with -F to fix issues found if target device had a filesystem already present. - Partition alignment and sizing fixes (LP: #1513085) - Set bcache cache_mode if present in storage config (LP: #1510334) - when apt-get update is called during installation, do not download translation files and source files, reducing chances for mismatch. - add system-install sub command. 'curtin system-install pastebinit' will install packages in a way guaranteed to not prompt. - add 'system-upgrade' command and config to easily update the system after installation before reboot. (LP: #1481992) - fix reporting of FAIL when a subcommand used sys.exit(0) - grub-install: if fail to find mounted uefi partition, give more debug output - network config: add support for dns-search key in subnet and search in nameserver - Ensure required networking packages are installed in the target. (LP: #1491994) - stop grub from going into graphical/vga mode on installed systems - curthooks: support specifying kernel/package without mapping - ChrootableTarget: do not attempt to change resolv.conf if there is no /etc directory - list the set of features that curtin has for library users. users can now check the FEATURES list for a specific feature. - fix bug in argument parsing --set mykey=foo=bar - in-target: add '--capture' to in-target and special case target=/ - support declaring json in --set argument via --set=json:... - add reporting function to allow calling a webhook endpoint with status of curtin install. - Allow partprobe to return 1, which is expected when no partition table exists (LP: #1488632). - support storage config providing /dev/disk/by-dname links (LP: #1487533, LP: #1477756) - enable setting of verbosity and showtrace via config file (LP: #1467673) - drop python-parted dependency (LP: #1483196, LP: #1477795) - swap: use fallocate if possible for much faster swap file creation (LP: #1482994) - support network-config, where networking configuration is declared in curtin config that will be applied to the host. - support storage-config, allowing curtin to install
[Bug 1509147] Re: [SRU] MAAS 1.9
** Description changed: We would like to request a SRU for MAAS 1.9. This follow the approval by the Ubuntu Technical Board for backporting new MAAS upstream releases. [Impact] This is a new version of MAAS that provides new features as well as various bug fixes against various issues. It increases MAAS' reliability and serviceability and greatly improves MAAS as a whole. [Regression Potential] Minimal. MAAS has been thoroughly tested stand alone and upgrading from 1.7 and 1.8. It has been QA'd in a CI lab as well as other production deployments: Tests done: 1. Upgraded a production lab from 1.7.6 to 1.9.0 (and 1.9.0 later on). MAAS 1.9 has proven to be more robust, and higher deployment rates without failures than 1.9.0. This lab is a high load lab that stress tests deployments with MAAS. 2. Every MAAS release is thoroughly tested for upgrades. For 1.9, upgrade tests include: - Upgrading from 1.5 to 1.9 directly - Upgrading from 1.5 to 1.7 to 1.8 to 1.9 - Upgrading from 1.7 to 1.9 3. MAAS CI Lab: - Tests Installation (from pkgs), configuration / customization of MAAS, enlistment, commissioning. It also tests deployments with Juju. - Tests various API's - Tests are performed against Trusty. 4. Other manual testing include: - Installation (both fresh and upgrades) - Configuration - Taking nodes through the lifecycle for regression testing. - Custom configuration to ensure proper operation. - Tests API's for regressions, and keeping backwards compatibility. = Changelog = 1.9.0 = Important announcements --- **New Networking Concepts and API's: Fabrics, Spaces and Subnets** With the introduction of new MAAS networking concepts, new API's are also been introduced. These are: * fabrics * spaces * subnets * vlans * fan-networks MAAS 1.9.0 will continue to provide backwards compatibility with the old network API for reading purposes, but moving forward, users are required to use the new API to manipulate fabrics, spaces and subnets. **Advanced Network and Storage Configuration only available for Ubuntu deployments** Users can now perform advanced network and storage configurations for nodes before deployment. The advanced configuration is only available for Ubuntu deployments. All other deployments using third party OS', including CentOS, RHEL, Windows and Custom Images, won't result in such configuration. **Re-commissioning required for upgraded MAAS** Now that storage partitioning and advanced configuration is supported natively, VM nodes in MAAS need to be re-commissioned. * If upgrading from MAAS 1.8, only VM nodes with VirtIO storage devices need to be re-commissioned. * If upgrading from MAAS 1.7, all nodes will need to be re- commissioned in order for MAAS to correctly capture the storage and networking devices. This does not affect nodes that are currently deployed. **Default Storage Partitioning Layout - Flat** With the introduction of custom storage, MAAS has also introduced the concept of partitioning layouts. Partitioning layouts allow the user to quickly auto-configure the disk partitioning scheme after first commissioning or re-commissioning (if selected to do so). The partitioning layouts are set globally on the `Settings` page. The current default Partitioning layout is 'Flat', maintaining backwards compatibility with previous MAAS releases. This means MAAS will take the first disk it finds in the system and use it as the root and boot disk. **Deployment with configured /etc/network/interfaces** Starting with MAAS 1.9, all node deployments will result in writing `/etc/network/interfaces` statically, by default. This increases MAAS' robustness and reliability as users no longer have to depend on DHCP for IP address allocation solely. MAAS will continue to provide IP addresses via DHCP, even though interfaces in `/etc/network/interfaces` may have been configured statically. Major new features -- **Storage Partitioning and Advanced Configuration** MAAS now supports Storage Partitioning and Advanced Configuration natively. This allows MAAS to deploy machines with different Storage Layouts, as well as different complex partitioning configurations. Storage support includes: * LVM * Bcache * Software RAID levels 0, 1, 5, 6, 10. * Advanced partitioning Storace configuration is available both via the WebUI and API. For more information refer to :ref:`storage`. **Advanced Networking (Fabrics, Spaces, Subnetworks) and Node Network Configuration** MAAS now supports Advanced Network configuration, allowing users to not only perform advanced node network configuration, but also allowing users to declare and map their infrastructure in the form of Fa
[Bug 1515780] Re: bcache does not work with suspend
** Changed in: bcache-tools (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bcache-tools in Ubuntu. https://bugs.launchpad.net/bugs/1515780 Title: bcache does not work with suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1515780/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1536262] Re: dns-* e/n/i are misplaced
** Changed in: curtin (Ubuntu) Status: New => Fix Released ** Also affects: curtin (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: curtin (Ubuntu Trusty) Status: New => Confirmed ** Changed in: curtin (Ubuntu Trusty) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1536262 Title: dns-* e/n/i are misplaced To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1536262/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481992] Re: Upgrade of grub-pc during install fails
I consider 'system-upgrade' as the fix for this. Either add config that does: system_updgrade: enabled: True or run curtin system-upgrade as a late_command ** Also affects: curtin Importance: Undecided Status: New ** Changed in: curtin Status: New => Fix Committed ** Changed in: curtin Importance: Undecided => Low ** Changed in: curtin (Ubuntu) Status: New => Fix Released ** Changed in: curtin (Ubuntu) Importance: Undecided => Low ** Also affects: curtin (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: curtin (Ubuntu Trusty) Status: New => Confirmed ** Changed in: curtin (Ubuntu Trusty) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1481992 Title: Upgrade of grub-pc during install fails To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1481992/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1449099] Re: [SRU] bcache-tools to trusty and precise
** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** No longer affects: cloud-init (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1449099 Title: [SRU] bcache-tools to trusty and precise To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1449099/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1575938] Re: Instance path in / if instance-id starts with '/'
** Changed in: cloud-init Status: New => Confirmed ** Changed in: cloud-init Importance: Undecided => Medium ** Changed in: cloud-init Status: Confirmed => In Progress ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1575938 Title: Instance path in / if instance-id starts with '/' To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1575938/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1576692] [NEW] fully support package installation in systemd
Public bug reported: in cloud-init users can install packages via cloud-config: #cloud-config packages: [apache2] Due to some intricacies of systemd and service installation that doesn't work all that well. We fixed the issue for simple services that do not have any dependencies on other services, or at least don't check those dependencies well under bug 1575572. We'd like to have a way to fully support this in cloud-init. Related bugs: * bug 1575572: apache2 fails to start if installed via cloud config (on Xenial) ** Affects: cloud-init Importance: Medium Status: Confirmed ** Affects: cloud-init (Ubuntu) Importance: Medium Status: Confirmed ** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium ** Also affects: cloud-init Importance: Undecided Status: New ** Changed in: cloud-init Status: New => Confirmed ** Changed in: cloud-init Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1576692 Title: fully support package installation in systemd To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1576692/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1575572] Re: apache2 fails to start if installed via cloud config (on Xenial)
** Description changed: Using the following cloud config, apache2 will fail to start on installation on Xenial: #cloud-config packages: - apache2 See for example: $ gcloud compute instances create xenial-$(date +%y%m%d-%H%M) --image ubuntu-1604-xenial-v20160420c --image-project ubuntu-os-cloud --metadata-from-file user-data=cloud-config NAMEZONEMACHINE_TYPE PREEMPTIBLE INTERNAL_IP EXTERNAL_IPSTATUS xenial-160427-1050 europe-west1-d n1-standard-1 10.240.0.7 104.155.86.94 RUNNING $ ssh ubuntu@104.155.86.94 systemctl status apache2.service ● apache2.service - LSB: Apache2 web server -Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled) - Drop-In: /lib/systemd/system/apache2.service.d -└─apache2-systemd.conf -Active: inactive (dead) - Docs: man:systemd-sysv-generator(8) + Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled) + Drop-In: /lib/systemd/system/apache2.service.d + └─apache2-systemd.conf + Active: inactive (dead) + Docs: man:systemd-sysv-generator(8) + + Related Bugs: + * bug 1576692: fully support package installation in systemd ** Description changed: Using the following cloud config, apache2 will fail to start on installation on Xenial: #cloud-config packages: - apache2 See for example: $ gcloud compute instances create xenial-$(date +%y%m%d-%H%M) --image ubuntu-1604-xenial-v20160420c --image-project ubuntu-os-cloud --metadata-from-file user-data=cloud-config NAMEZONEMACHINE_TYPE PREEMPTIBLE INTERNAL_IP EXTERNAL_IPSTATUS xenial-160427-1050 europe-west1-d n1-standard-1 10.240.0.7 104.155.86.94 RUNNING $ ssh ubuntu@104.155.86.94 systemctl status apache2.service ● apache2.service - LSB: Apache2 web server Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled) Drop-In: /lib/systemd/system/apache2.service.d └─apache2-systemd.conf Active: inactive (dead) Docs: man:systemd-sysv-generator(8) Related Bugs: - * bug 1576692: fully support package installation in systemd + * bug 1576692: [cloud-init] fully support package installation in systemd ** No longer affects: cloud-init (Ubuntu Xenial) ** No longer affects: cloud-init (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1575572 Title: apache2 fails to start if installed via cloud config (on Xenial) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1575572/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1575572] Re: apache2 fails to start if installed via cloud config (on Xenial)
> This behaviour of installing packages or configuring your system while the > system isn't booted yet might also bite you in other cases (it certainly bit > me a number of cases). Maybe we should discuss how to move that after the > boot? I do that in > https://git.launchpad.net/~ubuntu-release/+git/autopkgtest-cloud/tree/tools/armf-lxd-slave.userdata > but this doesn't look very pretty. The goal of cloud-init is basically to allow the user to do whatever they could have done by creating their own image. But instead, do that via feeding data to the system. The portion of cloud-init that installs packages for a user can be moved to a later stage, but can't really be moved *out* of boot. sysvinit and upstart support this functionality well. upstart *really* does the right thing in that you can add new jobs and when conditions are met those jobs will be handled. Also note that "in the boot sequence" is not really the problem. The problem is that the package installation is happening before the system is completely booted. As an example of the difference, consider that any hung or blocked systemd service will break installation of services. I can show this by: a.) new xenial container b.) modify /etc/rc.local to have 'sleep 5m' c.) start container d.) lxc exec name apt-get install apache2 e.) apt-get install apache2 The same problem can be shown with 'd' being invoked via ssh, or *any* other mechanism on the system. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1575572 Title: apache2 fails to start if installed via cloud config (on Xenial) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1575572/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1575572] Re: apache2 fails to start if installed via cloud config (on Xenial)
Pitti, in reponse to comment 5 above: > > d.) output of runlevel is stored in RL and then it goes looking for an > > SLINK or SSLINK (/etc/rc$RL.d/S??apache2 or /etc/rcS.d/S??apache2). Neither > > of these exist so it exits without starting the service. > To be sure we are talking about the same thing: Surely update-rc.d should run > before invoke-rc.d in the postinst, so the links should exist in rc[2345].d/. > This is solely about $RL having the wrong value here, not about the links not > existing at all, right? Yes, the links are present and that is functional. but if RL=unknown, then there is no file /etc/rcunknown.d/S??apache2. My statement wasn't terribly clear. If RL=5 all would be good. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1575572 Title: apache2 fails to start if installed via cloud config (on Xenial) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1575572/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1575055] Re: check_instance_id() error on reboots when using config-drive
Thanks for the bug report and the fix. Committed in trunk. I will try to get this uploaded to yakkety and to xenial today. ** Also affects: cloud-init Importance: Undecided Status: New ** Changed in: cloud-init Importance: Undecided => High ** Changed in: cloud-init Status: New => Fix Committed ** Changed in: cloud-init Assignee: (unassigned) => Scott Moser (smoser) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1575055 Title: check_instance_id() error on reboots when using config-drive To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1575055/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1576351] Re: include cloud-init in ubuntu-server disable by default in iso install
I spoke with cyphermox, and it seems that probably the right way for this to happen is for cloud-init to prompt at install time at the proper priority and then the installer will ask. Alternatively, we could seed the question in the installer preseed so there is no prompt and it is disabled. ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1576351 Title: include cloud-init in ubuntu-server disable by default in iso install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1576351/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1576333] [NEW] runs to early
Public bug reported: pollinate runs too early on some of the instances i launch. Basically nothing guarantees that it will have network access when it attempts to run. failure looks something like: $ lxc launch xenial x1 $ sleep 4 $ lxc exec x1 systemctl status pollinate ● pollinate.service - Seed the pseudo random number generator on first boot Loaded: loaded (/lib/systemd/system/pollinate.service; enabled; vendor preset: enabled) Active: inactive (dead) since Thu 2016-04-28 17:16:03 UTC; 1min 17s ago Process: 86 ExecStart=/usr/bin/pollinate (code=exited, status=0/SUCCESS) Main PID: 86 (code=exited, status=0/SUCCESS) Apr 28 17:16:03 ubuntu systemd[1]: Starting Seed the pseudo random number generator on first boot... Apr 28 17:16:03 ubuntu pollinate[106]: client sent challenge to [https://entropy.ubuntu.com/] Apr 28 17:16:03 ubuntu pollinate[86]: <13>Apr 28 17:16:03 pollinate[86]: client sent challenge to [https://entropy.ubuntu.com/] Apr 28 17:16:03 ubuntu pollinate[149]: [432B blob data] Apr 28 17:16:03 ubuntu pollinate[86]: Apr 28 17:16:03 ubuntu <13>Apr 28 17:16:03 pollinate[86]: WARNING: Network communication failed [0]\n % Total % Received % Xferd Average Speed TimeTime Time Current Apr 28 17:16:03 ubuntu pollinate[86]: Dload Upload Total SpentLeft Speed Apr 28 17:16:03 ubuntu pollinate[86]: [139B blob data] Apr 28 17:16:03 ubuntu pollinate[86]: 17:16:03.859980 * Closing connection 0 Apr 28 17:16:03 ubuntu pollinate[86]: curl: (6) Could not resolve host: entropy.ubuntu.com Apr 28 17:16:03 ubuntu systemd[1]: Started Seed the pseudo random number generator on first boot. This seems like it might work: # diff -u /lib/systemd/system/pollinate.service.dist /lib/systemd/system/pollinate.service --- /lib/systemd/system/pollinate.service.dist 2016-04-28 17:19:10.807971336 + +++ /lib/systemd/system/pollinate.service 2016-04-28 17:19:17.839874541 + @@ -2,6 +2,7 @@ Description=Seed the pseudo random number generator on first boot DefaultDependencies=no After=sysinit.target +After=network.target Before=ssh.service [Service] ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pollinate 4.15-0ubuntu1 [modified: usr/bin/pollinate] ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu Apr 28 16:39:17 2016 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) SourcePackage: pollinate UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pollinate (Ubuntu) Importance: Medium Status: Confirmed ** Tags: amd64 apport-bug uec-images xenial ** Changed in: pollinate (Ubuntu) Status: New => Confirmed ** Changed in: pollinate (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pollinate in Ubuntu. https://bugs.launchpad.net/bugs/1576333 Title: runs to early To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1576333/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1575572] Re: apache2 fails to start if installed via cloud config (on Xenial)
Ok, here is what is happening:
a.) dpkg (or apt) install of apache2 (or just about any service) starts
services by calling to /usr/sbin/invoke-rc.d (like 'invoke-rc.d apache2 start').
b.) invoke-rc.d calls 'runlevel' to get the current runlevel and see if this
service should be started.
c.) runlevel during systemd boot writes 'unknown' (single token rather than
previous and current runlevel) and exits 1
the test for failure of RUNLEVELHELPER is bogus in at least 2 ways
('test ! $?' will return 0 for 0 or 1, and additionally it actually only checks
the return code of 'sed' which is going to be 0 anyway as sed did its job).
d.) output of runlevel is stored in RL and then it goes looking for an SLINK
or SSLINK (/etc/rc$RL.d/S??apache2 or /etc/rcS.d/S??apache2). Neither of these
exist so it exits without starting the service.
The problem seems to be that any package install during systemd boot of a
package that only provides sysvinit scripts will fail.
Reading invoke-rc.d, i'm not really sure why a proper systemd service woudlnt
fail also.
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Also affects: init-system-helpers (Ubuntu)
Importance: Undecided
Status: New
** Changed in: init-system-helpers (Ubuntu)
Importance: Undecided => High
** Changed in: init-system-helpers (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1575572
Title:
apache2 fails to start if installed via cloud config (on Xenial)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1575572/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1574963] Re: juju2 lxd launch hostname reverse lookup inconsistent
** Also affects: cloud-images Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1574963 Title: juju2 lxd launch hostname reverse lookup inconsistent To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1574963/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1510345] Re: [SRU] Cloud Images do not bring up networking w/ certain virtual NICs due to device naming rules
this is fix-released from cloud-init perspective in xenial. If you disagree, please state why and open the bug. cloud-init now renders .rules files and configures ENI per the datasource's provided network config or a fallback network config. ** No longer affects: cloud-init ** Changed in: cloud-init (Ubuntu) Status: Triaged => Fix Released ** Changed in: cloud-init (Ubuntu Xenial) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1510345 Title: [SRU] Cloud Images do not bring up networking w/ certain virtual NICs due to device naming rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-on-ec2/+bug/1510345/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1574963] Re: juju2 lxd launch hostname reverse lookup inconsistent
This is solvable in cloud-init, and it would not be terribly invasive for the lxc datasource (nocloud) as that is "local". For other datasources that use the network, its more complex at least for now as getting the hostname would mean dhcp on the network interface and thus advertising 'ubuntu'. The azure datasource actually bounces the network interface after it comes up. So, 2 simple-ish solutions for this a.) cloud-init for nocloud datasource tries to apply the hostname found in the datasource when it applies networking configuration (before networking comes up). That seems quite reasonable. b.) the lxd templates could write /etc/hostname . I thought at one point they did. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1574963 Title: juju2 lxd launch hostname reverse lookup inconsistent To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1574963/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1575055] Re: check_instance_id() error on reboots when using config-drive
** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Xenial) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1575055 Title: check_instance_id() error on reboots when using config-drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1575055/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1570633] Re: [2.0 beta 2] Nodes fail to remain powered after Trusty commission with "Allow SSH" selected
** Changed in: cloud-init Importance: Undecided => Medium ** Changed in: cloud-init Status: Confirmed => Fix Released ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu) Status: New => Fix Released ** Also affects: cloud-init (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1570633 Title: [2.0 beta 2] Nodes fail to remain powered after Trusty commission with "Allow SSH" selected To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1570633/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1571822] Re: Azure: cloud-init will not set password on existing user
** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium ** Also affects: cloud-init Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1571822 Title: Azure: cloud-init will not set password on existing user To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1571822/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1474090] Re: growpart breaks ppc64 images / sfdisk changes partition type
marking fix-released in util-linux as we have 2.27 in xenial. ** Changed in: util-linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-utils in Ubuntu. https://bugs.launchpad.net/bugs/1474090 Title: growpart breaks ppc64 images / sfdisk changes partition type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-utils/+bug/1474090/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1563487] Re: do not delete /etc/network/interfaces.d/eth0.cfg
Not sure why this didn't get marked fix released
cloud-init (0.7.7~bzr1212-0ubuntu1) xenial; urgency=medium
* New upstream snapshot.
- fix iscsi root by not writing interface as 'auto' when networking
information comes from kernel command line (LP: #1568637)
- apply networking less often, when possible only on first
instance boot (LP: #1571004).
- no longer delete /etc/network/interfaces.d/eth0.cfg on
ubuntu (LP: #1563487)
-- Scott Moser Fri, 15 Apr 2016 16:25:43 -0400
** Changed in: cloud-init
Status: Fix Committed => Fix Released
** Changed in: cloud-init
Assignee: Scott Moser (smoser) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1563487
Title:
do not delete /etc/network/interfaces.d/eth0.cfg
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1563487/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1571761] Re: zfs-import-cache.service slows boot by 60 seconds
** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1571761 Title: zfs-import-cache.service slows boot by 60 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1571761/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1571761] Re: zfs-import-cache.service slows boot by 60 seconds
So: a.) zfs-import-cache.service is 'After systemd-udev-settle.service' b.) cloud-init installs /lib/udev/rules.d/79-cloud-init-net-wait.rules which uses IMPORT of /lib/udev/cloud-init-wait to block network device add events until cloud-init-local has written networking configuration I'm pretty sure, then what is happening is: 1.) network device gets added and cloud-init-wait starts its 60 second wait for cloud-init-local to finish. 2.) systemd-udev-settle runs, which waits until queued all events are processed 3.) deadlock until timeout from 1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1571761 Title: zfs-import-cache.service slows boot by 60 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1571761/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1571761] Re: zfs-import-cache.service slows boot by 60 seconds
** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1571761 Title: zfs-import-cache.service slows boot by 60 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1571761/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1568637] Re: iscsi root boot fails without /etc/network/interfaces aid of cloud-initramfs-dyn-netconf
** Description changed: - when i removed the symlink in the maas ephemeral image from /etc/network/interfaces - the iscsi root boot fails, and maas deployment would also fail. + when i removed the symlink in the maas ephemeral image from /etc/network/interfaces the iscsi root boot fails, and maas deployment would also fail. + The real reason for the difference was that cloud-init was rendering 'auto' for the device that was brought up in the initramfs. + + Instead it needs to leave it to be manually controled (no 'auto' or + 'allow-hotplug'). ** Summary changed: - iscsi root boot fails without /etc/network/interfaces aid of cloud-initramfs-dyn-netconf + network config of initramfs devices writes 'auto', breaking iscsi root boot ** Description changed: when i removed the symlink in the maas ephemeral image from /etc/network/interfaces the iscsi root boot fails, and maas deployment would also fail. The real reason for the difference was that cloud-init was rendering 'auto' for the device that was brought up in the initramfs. Instead it needs to leave it to be manually controled (no 'auto' or 'allow-hotplug'). + + Related bugs: + * bug 1570142: [open-isci] net-interface-handler needs updating for newer ifupdown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1568637 Title: network config of initramfs devices writes 'auto', breaking iscsi root boot To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1568637/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1570142] Re: net-interface-handler needs updating for newer ifupdown
** No longer affects: cloud-init (Ubuntu) ** No longer affects: maas-images ** No longer affects: cloud-init ** Description changed: newer ifupdown versions (those in xenial) now keep interface state in /run/network/ifstate. rather than combined in /run/network/ifstate . We need to update /lib/open-iscsi/net-interface-handler to write the interface name into /run/network/ifstate. and then also tear that down on down. The failure can be seen when booting a maas image, if you first move the included symlink out of the way: p="/etc/network/interfaces"; [ -e "$p.link" -o -L "$p.link" ] || mv "$p" "$p.link"; cp "$p.dist" "$p" (maas images ship with /etc/network/interfaces as a symlink to ../../run/network/dynamic-interfaces and /run/network/dynamic-interfaces is populated by cloud-initramfs-dyn-netconf). This affects: - * cloud-init: cloud-init's fallback config currently writes 'auto' for the network device. the cloud-initramfs-dyn-netconf writes 'manual', and so ifupdown doesn't try to bring up *or* down the device. - * maas-images: the single difference from filesystem viewpoint from xenial lxd image to maas image is 'ln -snf ../../run/dynamic-interfaces /etc/network/interfaces' - * open-iscsi: the real need for open-iscsi's udev integration is to get the resolvconf updates applied. + * cloud-init: cloud-init's fallback config currently writes 'auto' for the network device. the cloud-initramfs-dyn-netconf writes 'manual', and so ifupdown doesn't try to bring up *or* down the device. + * maas-images: the single difference from filesystem viewpoint from xenial lxd image to maas image is 'ln -snf ../../run/dynamic-interfaces /etc/network/interfaces' + * open-iscsi: the real need for open-iscsi's udev integration is to get the resolvconf updates applied. + + Related bugs: + * bug 1568637: network config of initramfs devices writes 'auto', breaking iscsi root boot ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Wed Apr 13 23:58:27 2016 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) SourcePackage: open-iscsi UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1570142 Title: net-interface-handler needs updating for newer ifupdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1570142/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1563487] Re: do not delete /etc/network/interfaces.d/eth0.cfg
fixed in trunk at revno 210. ** Changed in: cloud-init Status: Confirmed => Fix Committed ** Changed in: cloud-init Assignee: (unassigned) => Scott Moser (smoser) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1563487 Title: do not delete /etc/network/interfaces.d/eth0.cfg To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1563487/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1563487] Re: do not delete /etc/network/interfaces.d/eth0.cfg
** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu) Status: New => Confirmed ** Changed in: livecd-rootfs (Ubuntu) Importance: Undecided => Medium ** Changed in: livecd-rootfs (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1563487 Title: do not delete /etc/network/interfaces.d/eth0.cfg To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1563487/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1569064] Re: ifupdown wants to configure interfaces it shouldn't (lxdbr0 or veth)
** Summary changed: - ifupdown wants to configure interfaces it shouldn't (lxdbr0) + ifupdown wants to configure interfaces it shouldn't (lxdbr0 or veth) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1569064 Title: ifupdown wants to configure interfaces it shouldn't (lxdbr0 or veth) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1569064/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1569064] Re: ifupdown wants to configure interfaces it shouldn't (lxdbr0)
ok. So under bug 1569974 i fixed cloud-init to not consider the bridge as something it should pick as a fallback nic. However, there is still a problem in that cloud-init may select the host side of a veth device. The result is that $ cat /etc/network/interfaces.d/50-cloud-init.cfg auto vethVH9WCK iface vethVH9WCK inet dhcp So a.) cloud-init needs to find some way to still do the right thing and pick the right nic ignoring those veth devices Note, though in a container eth0 (a veth) *is* the right device. b.) lxd should probably not bring up bridges or do other things before 'network-pre.target' cloud-init-local, the code that determines this runs: 'Before=network-pre.target' The fact taht it finds vethVH9WCK means that lxd ran that early. It probably means that lxd started containers that early, which is probably wrong as those containers might well expect to reach the interwebs during boot, and they will not be able to. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1569064 Title: ifupdown wants to configure interfaces it shouldn't (lxdbr0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1569064/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1569064] Re: ifupdown wants to configure interfaces it shouldn't (lxdbr0)
** This bug is no longer a duplicate of bug 1569974 networking fallback should ignore bridges ** Changed in: lxd (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1569064 Title: ifupdown wants to configure interfaces it shouldn't (lxdbr0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1569064/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1570119] Re: xenial ppc64le cloud image crashes on nested virt
** Also affects: qemu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1570119 Title: xenial ppc64le cloud image crashes on nested virt To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1570119/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1570142] Re: net-interface-handler needs updating for newer ifupdown
At this point, I think the second patch there is doing the right thing. The reason I asked slangasek to NAC my upload was that poweroff wasnt' working correctly. The reason poweroff wasn't working correctly was that cloud-init is writing 'auto eth0' where cloud-initramfs-dyn-netconf is writing 'manual eth0'. cloud-init's version means that ifupdown tries to bring the device down on shutdown. ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Also affects: cloud-init Importance: Undecided Status: New ** Also affects: maas-images Importance: Undecided Status: New ** Changed in: cloud-init Status: New => Confirmed ** Changed in: maas-images Status: New => Confirmed ** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Description changed: newer ifupdown versions (those in xenial) now keep interface state in /run/network/ifstate. rather than combined in /run/network/ifstate . We need to update /lib/open-iscsi/net-interface-handler to write the interface name into /run/network/ifstate. and then also tear that down on down. The failure can be seen when booting a maas image, if you first move the included symlink out of the way: - p="/etc/network/interfaces"; - [ -e "$p.link" -o -L "$p.link" ] || mv "$p" "$p.link"; cp "$p.dist" "$p" + p="/etc/network/interfaces"; + [ -e "$p.link" -o -L "$p.link" ] || mv "$p" "$p.link"; cp "$p.dist" "$p" (maas images ship with /etc/network/interfaces as a symlink to ../../run/network/dynamic-interfaces and /run/network/dynamic-interfaces is populated by cloud-initramfs-dyn-netconf). + + This affects: + * cloud-init: cloud-init's fallback config currently writes 'auto' for the network device. the cloud-initramfs-dyn-netconf writes 'manual', and so ifupdown doesn't try to bring up *or* down the device. + * maas-images: the single difference from filesystem viewpoint from xenial lxd image to maas image is 'ln -snf ../../run/dynamic-interfaces /etc/network/interfaces' + * open-iscsi: the real need for open-iscsi's udev integration is to get the resolvconf updates applied. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Wed Apr 13 23:58:27 2016 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) + TERM=xterm-256color + PATH=(custom, no user) SourcePackage: open-iscsi UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1570142 Title: net-interface-handler needs updating for newer ifupdown To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1570142/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1569064] Re: ifupdown wants to configure interfaces it shouldn't (lxdbr0)
*** This bug is a duplicate of bug 1569974 *** https://bugs.launchpad.net/bugs/1569974 ** This bug has been marked a duplicate of bug 1569974 networking fallback should ignore bridges -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1569064 Title: ifupdown wants to configure interfaces it shouldn't (lxdbr0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1569064/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1543459] Re: login available before cloud-init completed
** Changed in: cloud-init Status: New => Confirmed ** Changed in: cloud-init Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1543459 Title: login available before cloud-init completed To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1543459/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1568150] Re: xenial lxc containers not starting
** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu) Importance: Undecided => High ** Changed in: cloud-init Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1568150 Title: xenial lxc containers not starting To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1568150/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1566824] Re: phone_home module should allow fqdn to be posted
** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1566824 Title: phone_home module should allow fqdn to be posted To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1566824/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1568150] Re: xenial lxc containers not starting
** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init Importance: Undecided => High ** Changed in: cloud-init Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1568150 Title: xenial lxc containers not starting To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1568150/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1569974] Re: networking fallback should ignore bridges
** Also affects: cloud-init Importance: Undecided Status: New ** Changed in: cloud-init Status: New => Confirmed ** Changed in: cloud-init Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1569974 Title: networking fallback should ignore bridges To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1569974/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1569974] [NEW] networking fallback should ignore bridges
Public bug reported: Serge pointed me at an an issue with cloud-init's fallback networking. It will consider bridges as possible devices to dhcp on. Since these bridges are configured only by things like lxd (not /etc/network/interfaces) they're not going to be good devices to 'dhcp' on and get a fallback networking configuration. My short solution is to just ignore bridge devices when searching. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cloud-init 0.7.7~bzr1200-0ubuntu1 [modified: lib/systemd/system/cloud-init-local.service usr/lib/python3/dist-packages/cloudinit/net/__init__.py] ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Wed Apr 13 14:22:57 2016 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug uec-images xenial -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1569974 Title: networking fallback should ignore bridges To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1569974/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1473527] Re: module ssh-authkey-fingerprints fails Input/output error: /dev/console
I've seen this reproduce more and more in curtin tests lately in xenial: https://server-team-jenkins.canonical.com/job/curtin-vmtest-venonat-devel/15/artifact/output/XenialBcacheBasic/logs/install-serial.log/*view*/ https://server-team-jenkins.canonical.com/job/curtin-vmtest-venonat-devel/15/artifact/output/XenialTestBasic/logs/install-serial.log from https://server-team-jenkins.canonical.com/job/curtin-vmtest-venonat-devel/15/artifact/output/XenialTestBasic/logs/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1473527 Title: module ssh-authkey-fingerprints fails Input/output error: /dev/console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1473527/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1569469] [NEW] smartos datasource stacktrace if no system-product-name in dmi data
Public bug reported: if there is no product name in dmi data, cloud-init log will show DataSourceCloudSigma.py[WARNING]: failed to get hypervisor product name via dmi data util.py[WARNING]: Getting data from failed util.py[DEBUG]: Getting data from failed# Traceback (most recent call last):# File "/usr/lib/python3/dist-packages/cloudinit/sources/__init__.py", line 266, in find_source# if s.get_data():# File "/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceSmartOS.py", line 250, in get_data# if 'smartdc' not in system_type.lower():# AttributeError: 'NoneType' object has no attribute 'lower' Fix is simple enough. ** Affects: cloud-init Importance: Medium Status: Confirmed ** Affects: cloud-init (Ubuntu) Importance: Medium Status: Confirmed ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init Status: New => Confirmed ** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1569469 Title: smartos datasource stacktrace if no system-product-name in dmi data To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1569469/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1473527] Re: module ssh-authkey-fingerprints fails Input/output error: /dev/console
** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1473527 Title: module ssh-authkey-fingerprints fails Input/output error: /dev/console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1473527/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.
Marking as 'fix-released' in maas in wily and xenial, as the fix went into trunk at revision 4028. https://code.launchpad.net/~rvb/maas/lp-1313550/+merge/262314 ** Changed in: maas (Ubuntu Wily) Status: New => Fix Released ** Changed in: maas (Ubuntu) Status: Confirmed => Fix Released ** Changed in: maas (Ubuntu Vivid) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1313550 Title: ping does not work as a normal user on trusty tarball cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1313550/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1569018] Re: [FFe] support lxc bridge configuration
fix-commited in trunk at 1202 ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium ** Also affects: cloud-init Importance: Undecided Status: New ** Changed in: cloud-init Status: New => Triaged ** Changed in: cloud-init Status: Triaged => Fix Committed ** Changed in: cloud-init Importance: Undecided => Medium ** Changed in: cloud-init Assignee: (unassigned) => Scott Moser (smoser) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1569018 Title: [FFe] support lxc bridge configuration To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1569018/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1505839] Re: Unable to install from text mode interface
just for some more info, I asked for clarification from cjwatson. $ rmadison gfx-boot-theme-ubuntu gfxboot-theme-ubuntu | 0.13.2 | precise | source, amd64, i386 gfxboot-theme-ubuntu | 0.13.3 | precise-updates | source, amd64, i386 gfxboot-theme-ubuntu | 0.16.1 | trusty | source, amd64, i386 gfxboot-theme-ubuntu | 0.18.0 | vivid | source, amd64, i386 gfxboot-theme-ubuntu | 0.18.0 | wily| source, amd64, i386 gfxboot-theme-ubuntu | 0.20.0 | xenial | source, amd64, i386 Even though gfx-boot-theme-ubuntu did nto change from vivid to wily where the regression occurred, cjwatson suggests that it still may be the cause of the issue as gfxboot-theme-ubuntu and syslinux are very tightly related. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1505839 Title: Unable to install from text mode interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1505839/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1505839] Re: Unable to install from text mode interface
** Package changed: gfxboot (Ubuntu) => gfxboot-theme-ubuntu (Ubuntu) ** Also affects: syslinux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1505839 Title: Unable to install from text mode interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1505839/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1505839] Re: Unable to install from text mode interface
There was some conversation on irc yesterday. http://irclogs.ubuntu.com/2016/04/11/%23ubuntu-devel.html#t20:18 cjwatson suggested likely gfxboot-theme-ubuntu as the bug component. ** Also affects: gfxboot (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1505839 Title: Unable to install from text mode interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1505839/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1568637] Re: iscsi root boot fails without /etc/network/interfaces aid of cloud-initramfs-dyn-netconf
** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu) Importance: Undecided => High ** Changed in: cloud-init Status: New => Confirmed ** Changed in: cloud-init Importance: Undecided => High ** Changed in: maas-images Status: New => Confirmed ** Changed in: maas-images Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1568637 Title: iscsi root boot fails without /etc/network/interfaces aid of cloud- initramfs-dyn-netconf To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1568637/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1505839] Re: Unable to install from text mode interface
A quick bit of testing shows that this regressed between ubuntu-15.04-server-amd64.iso and ubuntu-15.10-server-amd64.iso . So: WORKS: ubuntu-14.04.4-server-amd64.iso WORKS: ubuntu-15.04-server-amd64.iso FAILS: ubuntu-15.10-server-amd64.iso FAILS: xenial-server-amd64-daily-20160411.2.iso Thats good, because it means if the regression was in syslinux, then it was between 3:6.03+dfsg-5ubuntu1 and 3:6.03+dfsg-8ubuntu2 (there was a major version bump in syslinux between trusty and but it still seems to work in vivid. so that is good): $ rmadison syslinux syslinux | 2:4.05+dfsg-2 | precise | source, amd64, i386 syslinux | 3:4.05+dfsg-6+deb8u1 | trusty | source, amd64, i386 syslinux | 3:6.03+dfsg-5ubuntu1 | vivid | source, amd64, i386 syslinux | 3:6.03+dfsg-8ubuntu2 | wily| source, amd64, i386 syslinux | 3:6.03+dfsg-11ubuntu1 | xenial | source, amd64, i386 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1505839 Title: Unable to install from text mode interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1505839/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1569018] [NEW] [FFe] support lxc bridge configuration
Public bug reported: recent changes to lxd added configuration of the lxd bridge. We'd like to enable that in cloud-init. The change allows the user to put config in cloud-config that will basically map to the debconf keys and thus configure their lxd bridge and lxd init on first boot making it immediately useful. it should be safe for regression in that if there is no lxd bridge config, no change in code path will be taken. ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: Triaged ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** No longer affects: cloud-init ** Summary changed: - support lxc bridge configuration + [FFe] support lxc bridge configuration -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1569018 Title: [FFe] support lxc bridge configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1569018/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1568637] [NEW] iscsi root boot fails without /etc/network/interfaces aid of cloud-initramfs-dyn-netconf
Public bug reported: when i removed the symlink in the maas ephemeral image from /etc/network/interfaces the iscsi root boot fails, and maas deployment would also fail. ** Affects: cloud-init Importance: Undecided Status: New ** Affects: maas-images Importance: Undecided Status: New ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Also affects: cloud-init Importance: Undecided Status: New ** Also affects: maas-images Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1568637 Title: iscsi root boot fails without /etc/network/interfaces aid of cloud- initramfs-dyn-netconf To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1568637/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1377308] Re: booting cloud image without initramfs broken
** Also affects: cloud-init (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Trusty) Status: New => Triaged ** Changed in: cloud-init (Ubuntu Trusty) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1377308 Title: booting cloud image without initramfs broken To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1377308/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1545687] Re: Unable to launch a guest using libvirt on PowerNV Ubuntu Host
Hi, I'm marking this bug as 'Invalid' as I'm not able to reproduce it. If you can reproduce with current xenial please do re-open with details. I've collected some virsh capabilities output from the system that I ran this on at http://paste.ubuntu.com/15675510/ ** Changed in: libvirt (Ubuntu) Importance: Undecided => Medium ** Changed in: libvirt (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1545687 Title: Unable to launch a guest using libvirt on PowerNV Ubuntu Host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1545687/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1566468] Re: systemd-modules-load.service: Failing due to missing module 'ib_iser'
** Package changed: cloud-init (Ubuntu) => open-iscsi (Ubuntu) ** Changed in: open-iscsi (Ubuntu) Importance: Undecided => Medium ** Changed in: open-iscsi (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1566468 Title: systemd-modules-load.service: Failing due to missing module 'ib_iser' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1566468/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1566468] Re: systemd-modules-load.service: Failing due to missing module 'ib_iser'
Likely related/result of bug 1115710. The reference to mlx4.conf is what lead me to believe that. I'll dig a bit more tomorrow. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1566468 Title: systemd-modules-load.service: Failing due to missing module 'ib_iser' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1566468/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le
ok. so after playing some, this all comes down to needing 'usb=off' on the qemu command line. works: qemu-system-ppc64 -enable-kvm -machine usb=off -device virtio-net-pci,netdev=net00 -netdev type=user,id=net00 -drive if=virtio,file=xenial-server-cloudimg-ppc64el-disk1.img,format=qcow2 -drive if=virtio,file=my-seed.img,format=raw -snapshot -m 256 -nographic doesnt work: qemu-system-ppc64 -enable-kvm virtio-net-pci,netdev=net00 -netdev type=user,id=net00 -drive if=virtio,file=xenial-server-cloudimg-ppc64el-disk1.img,format=qcow2 -drive if=virtio,file=my-seed.img,format=raw -snapshot -m 256 -nographic the interesting bit of 'doesnt work' is that it *does* work, the user just thinks it doesnt because output is eaten up and doesnt go to console, but it *does* work fine. http://paste.ubuntu.com/15660816/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1563887 Title: qemu-system-ppc64 freezes on starting image on ppc64le To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1563887/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le
Note, that Michael Roth's comments are probably valid. I suspect that if leftyfb ever saw this working on powerVM host, then it was through the kvm_pr module. In my experience, that works generally pretty well (buit my testing has only ever been done powerNV host). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1563887 Title: qemu-system-ppc64 freezes on starting image on ppc64le To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1563887/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le
** Changed in: qemu Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1563887 Title: qemu-system-ppc64 freezes on starting image on ppc64le To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1563887/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1365852] Re: Setting "timezone:" fails: NameError: global name 'set_etc_timezone' is not defined
this is fix-released in any thing newere than revision 1008. ** Changed in: cloud-init (Ubuntu) Status: New => Fix Released ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1365852 Title: Setting "timezone:" fails: NameError: global name 'set_etc_timezone' is not defined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1365852/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1494678] Re: manage_etc_hosts: yes writes wrong hostname with custom hostname
** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1494678 Title: manage_etc_hosts: yes writes wrong hostname with custom hostname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1494678/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1525361] Re: Install of upstream Docker package only fails when running through cloud-init
** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1525361 Title: Install of upstream Docker package only fails when running through cloud-init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1525361/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1514407] Re: NoCloud provider fails with empty ds_cfg
** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1514407 Title: NoCloud provider fails with empty ds_cfg To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1514407/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1523921] Re: cloud-init disk_setup failure: 'list' object has no attribute 'splitlines'
*** This bug is a duplicate of bug 1311463 *** https://bugs.launchpad.net/bugs/1311463 Hi, i've marked as a duplicate. bug 1311463 is correctly triaged to have been nominated for the series that are broken. ** This bug has been marked a duplicate of bug 1311463 disk-setup unable to partition disks -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1523921 Title: cloud-init disk_setup failure: 'list' object has no attribute 'splitlines' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1523921/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1553158] Re: [SRU] Add cloud-init data source for BigStep
** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Low ** Also affects: cloud-init Importance: Undecided Status: New ** Changed in: cloud-init Status: New => Confirmed ** Changed in: cloud-init Importance: Undecided => Low ** Changed in: cloud-init (Ubuntu Trusty) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1553158 Title: [SRU] Add cloud-init data source for BigStep To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1553158/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1562914] Re: vendor-data not working with ConfigDrive in 0.7.5
** Changed in: cloud-init (Ubuntu) Status: New => Fix Released ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1562914 Title: vendor-data not working with ConfigDrive in 0.7.5 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1562914/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1555902] Re: Azure: Precise should use the same instance ID detection as Trusty
** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu) Status: New => Fix Released ** Also affects: cloud-init (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Precise) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Precise) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1555902 Title: Azure: Precise should use the same instance ID detection as Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1555902/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1496960] Re: webhook reporter posts url encoded data not json data
** Changed in: cloud-init Status: New => Fix Committed ** Changed in: cloud-init Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1496960 Title: webhook reporter posts url encoded data not json data To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1496960/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1536964] Re: Remove obsolete syslog.target dep from systemd services
** Changed in: cloud-init (Ubuntu) Importance: Undecided => Low ** Changed in: cloud-init (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1536964 Title: Remove obsolete syslog.target dep from systemd services To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1536964/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1536964] Re: Remove obsolete syslog.target dep from systemd services
fixed in trunk at 1198. ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init Importance: Undecided => Low ** Changed in: cloud-init Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1536964 Title: Remove obsolete syslog.target dep from systemd services To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1536964/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1514407] Re: NoCloud provider fails with empty ds_cfg
fixed in trunk at reno 1194 (missed the --fixes) ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init Importance: Undecided => Medium ** Changed in: cloud-init Status: New => Fix Committed ** Changed in: cloud-init Assignee: (unassigned) => Scott Moser (smoser) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1514407 Title: NoCloud provider fails with empty ds_cfg To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1514407/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1565638] Re: Cloud-init on Xenial won't deploy compressed content in "write_files" - says DecompressionError: Not a gzipped file
** Changed in: cloud-init Status: New => Confirmed ** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1565638 Title: Cloud-init on Xenial won't deploy compressed content in "write_files" - says DecompressionError: Not a gzipped file To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1565638/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1565638] Re: Cloud-init on Xenial won't deploy compressed content in "write_files" - says DecompressionError: Not a gzipped file
fixed in trunk at 1199. ** Changed in: cloud-init Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1565638 Title: Cloud-init on Xenial won't deploy compressed content in "write_files" - says DecompressionError: Not a gzipped file To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1565638/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1543459] Re: login available before cloud-init completed
** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Low ** Also affects: cloud-init Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1543459 Title: login available before cloud-init completed To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1543459/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1563951] Re: Cloud-init does not initialize systemd machine id
Greg, So digged a bit further, it seems that the ubuntu images do the right thing in that /etc/machine-id is not present in the image itself. I suspect your instances that you noticed this on were snapshotted from a once-booted instance or in some other way booted. If that is the case, it would seem like the best advice would be for you to just remove the file before snapshotting an instance for re-use, so that new instances would get a new id generated. Ideally in my mind, cloud-init or systemd or somethign would realize that this is a new instance and do the right thing, but that seems non- trivial at the moment. so i'll leave this as a wishlist bug on cloud- init. Thanks. Scott ** Changed in: cloud-init (Ubuntu) Status: Invalid => Confirmed ** Changed in: cloud-init (Ubuntu) Importance: Medium => Wishlist ** Changed in: livecd-rootfs (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1563951 Title: Cloud-init does not initialize systemd machine id To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1563951/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1563951] Re: Cloud-init does not initialize systemd machine id
Yeah, likely this happens to early in boot for cloud-init to affect. I've marked livecd-rootfs as a target, which is (i think) proper for changing the images themselves. ** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu) Status: New => Confirmed ** Changed in: livecd-rootfs (Ubuntu) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1563951 Title: Cloud-init does not initialize systemd machine id To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1563951/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
