Hi Scott,
Thanks for testing. I tested again (~10 times) with the latest Trusty
image and I wasn't able to reproduce the issue either. I'm not sure what
happened, if it's some timing issue or was just typo on my part :/ I
did not keep the repro VM around, unfortunately.
In that case I'm OK
Stephen,
I've just tested this on trusty images on azure
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu_DAILY_BUILD-trusty-14_04_5-LTS-amd64-server-20170118-en-us-30GB
and also in openstack (serial 20170112), and found both working.
I just launched instance with the user-data in the description and
This is tested as working on 0.7.8-49-g9e904bb-0ubuntu1~16.04.3 in xenial in
azure
$ cat /etc/cloud/build.info
build_name: server
serial: 20170117
$ cat /proc/swaps
FilenameTypeSizeUsedPriority
/dev/sdb2
This seems resolved in Xenial, but the issue also impacts Trusty. Will
this fix get backported?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642383
Title:
Unable to configure swap space on
The current sru of cloud-init to xenial will fix the swap, but it will
take bug 1647708 to be fixed in order to get the first device mounted.
That should happen with the next cloud-init update to xenial.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This is currently fixed in cloud-init in zesty 0.7.8-67-gc9c9197-0ubuntu1 .
I've verified it functional with the user-data provided in the description on
todays Azure image.
** Changed in: cloud-init (Ubuntu Zesty)
Status: Confirmed => Fix Released
** Description changed:
I'm
** Also affects: cloud-init (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Zesty)
Importance: High
Status: Confirmed
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: cloud-init
Hi,
I uploaded a fix for bug 1460715 to xenial-proposed. It is still in the queue,
and hopefully will be accepted into xenial-proposed soon.
Once 0.7.8-49-g9e904bb-0ubuntu1~16.04.2 is available the example cloud-
config above will successfully enable swap, and the /mnt2 filesystem
will be
Great news, thanks for the update! :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642383
Title:
Unable to configure swap space on ephemeral disk in Azure
To manage notifications about this bug
Hi Stephen, it appears the fix is in trunk now, so hopefully easy enough
to get into zesty & then back to xenial. Need to chat with Scott on
outlook, but yes, priority high for us.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: cloud-init (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642383
Title:
Unable to configure swap space on ephemeral disk in Azure
To manage
Hi Scott et al. Can we please raise the priority of this? It seems
there's no longer a way to create swap space on Ubuntu VMs on Azure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642383
Title:
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Description changed:
I'm following the instructions to send cloud-config and repartition the
ephemeral disk in Azure:
** Description changed:
I'm following the instructions to send cloud-config and repartition the
ephemeral disk in Azure: https://wiki.ubuntu.com/AzureSwapPartitions.
These instructions fail on Ubuntu 14.04 and 16.04 (did not test 12.04
yet).
Repro:
1) Add the following content
Same test on Xenial instance (with 0.7.8-1 cloud-init) fails with:
ubuntu@xenial-161117-1647:~$ sudo cloud-init --file user-data.cfg single --name
cc_disk_setup --frequency always
Cloud-init v. 0.7.8 running 'single' at Thu, 17 Nov 2016 18:46:52 +. Up
6996.70 seconds.
2016-11-17
Attempting to re-run the specific config on an existing Trusty instance:
1) sudo umount /mnt
2) sudo vi /etc/fstab and remove /mnt entry, save, quit
3) write out #cloud-config from this bug to user-data.cfg
4) sudo cloud-init --files user-data.cfg single --name cc_disk_setup
--frequency always
16 matches
Mail list logo