This bug is believed to be fixed in cloud-init in 17.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug was fixed in the package cloud-init - 0.7.9-153-g16a7302f-
0ubuntu1~17.04.1
---
cloud-init (0.7.9-153-g16a7302f-0ubuntu1~17.04.1) zesty-proposed; urgency=medium
* New upstream snapshot.
- net: fix reading and rendering addresses in cidr format.
[Dimitri John Ledko
This bug was fixed in the package cloud-init - 0.7.9-153-g16a7302f-
0ubuntu1~16.04.1
---
cloud-init (0.7.9-153-g16a7302f-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium
* New upstream snapshot.
- net: fix reading and rendering addresses in cidr format.
[Dimitri John Led
This bug was fixed in the package cloud-init - 0.7.9-153-g16a7302f-
0ubuntu1~16.10.1
---
cloud-init (0.7.9-153-g16a7302f-0ubuntu1~16.10.1) yakkety-proposed;
urgency=medium
* New upstream snapshot.
- net: fix reading and rendering addresses in cidr format.
[Dimitri John Le
First, reproduced and verified the mount was not succeeding. Then,
upgraded to the version in proposed and rebooted confirm that the disk
was mounted. Used the following cmd to boot an instance in azure with
the following cloud-config:
$ az vm create -n ci-test-1687712-$release -g $group --image
I've updated the SRU template providing one that should work.
The original config provided did not have any way to create a partitioned
device , but tried to put a filesystem on the first partition.
** Description changed:
+ === Begin SRU Template ===
+ [Impact]
+ If the user specifies cloud-co
David, for your point '2' above (comment 9), there was never any support
for cmd being an array. That is something that could be added, but is
not a regression.
See the previous code at
https://git.launchpad.net/cloud-init/tree/cloudinit/config/cc_disk_setup.py?id=99faf3ece1badc566e7e75e769ff37
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu Yakkety)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu Zesty)
Importance: Undecided => Me
Based on the above comments, I understand that the proposed update does
not resolve this bug, but does it make things worse?
E.g. can the pending update be released to fix all the other bugs that
were validated correctly, and reopen this bug report to re-fix this
issue again?
--
You received thi
I recommend to back this change out and re-approach. 2 major things we
found during testing
1) While this solution fixes the example given in the docs and the bug
description, another error is hit as seen in comment #7 and comment #8.
This needs debugging.
2) no protection against an array being
Testing fails for me on Xenial - here are my steps:
1) Create a VM in Azure (any size)
2) Update cloud-init to the latest in xenial-proposed
3) Capture VM image
4) Provision a new VM using the following cloud-config:
#cloud-config
fs_setup:
- special:
cmd: mkfs -t %(filesystem)s -L %
With cloud-init on Xenial from proposed (0.7.9-153-g16a7302f-
0ubuntu1~16.04.1) I found the error message is gone, however, I do not
see the disk when I do `ls -s /dev/disk/by-id/`, see below:
My steps:
$ az vm create -n cloud-init-test -g $my_group --image ubuntults
--data-disk-sizes-gb 8 --size
Hello Paul, or anyone else affected,
Accepted cloud-init into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.9-153-g16a7302f-0ubuntu1~16.04.1 in a few hours, and then in
the -proposed repository.
Please help us by testing this
Hello Paul, or anyone else affected,
Accepted cloud-init into yakkety-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.9-153-g16a7302f-0ubuntu1~16.10.1 in a few hours, and then in
the -proposed repository.
Please help us by testing this
Hello Paul, or anyone else affected,
Accepted cloud-init into zesty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.9-153-g16a7302f-0ubuntu1~17.04.1 in a few hours, and then in
the -proposed repository.
Please help us by testing this n
This bug was fixed in the package cloud-init -
0.7.9-144-g2825a917-0ubuntu1
---
cloud-init (0.7.9-144-g2825a917-0ubuntu1) artful; urgency=medium
* New upstream snapshot.
- flake8: move the pinned version of flake8 up to 3.3.0
- tests: Apply workaround for snapd bug in test c
** Changed in: cloud-init
Assignee: (unassigned) => Paul Meyer (paul-meyer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687712
Title:
cc_disk_setup: fs_setup with cmd doesn't work
To manage
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Vishnu C (chalil)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687712
Title:
cc_disk_setup: fs_setup with cmd doesn't work
To man
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687712
Title:
cc_disk_setup: fs_setup with cmd doesn't work
To manage
19 matches
Mail list logo
