** Changed in: cloud-init
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691489
Title:
fstab entries written by cloud-config may not be mounted
To manage
** Changed in: cloud-init (Ubuntu Zesty)
Status: Confirmed => Won't Fix
** Changed in: cloud-init (Ubuntu Artful)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: cloud-init
Status: Fix Released => Confirmed
** Changed in: cloud-init (Ubuntu Xenial)
Status: Fix Released => Fix Committed
** Changed in: cloud-init (Ubuntu Xenial)
Status: Fix Committed => Confirmed
** Changed in: cloud-init (Ubuntu Zesty)
Status:
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
** Changed in: cloud-init (Ubuntu Artful)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691489
Title:
fstab entries written by cloud-config may not be
As far as I can tell, I don't think we can "delay" the fsck service due
to how the systemd-fstab-generator works on /etc/fstab entries
For entries with a no-zero value for fsck (6th column), then the
generator will write out a .mount file that looks like this:
Not sure what to do here.
We intend to fix the other bug (bug 1717477) by reverting this change.
Thus re-opening this bug.
** Changed in: cloud-init
Status: Fix Committed => Confirmed
** Changed in: cloud-init
Assignee: Balint Reczey (rbalint) => (unassigned)
--
You received this
** Merge proposal linked:
https://code.launchpad.net/~rbalint/cloud-init/+git/cloud-init/+merge/330842
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691489
Title:
fstab entries written by
** Changed in: cloud-init (Ubuntu Yakkety)
Status: Confirmed => Won't Fix
** Description changed:
=== Begin SRU Template ===
[Impact]
There is a race condition on a re-deployment of cloud-init on Azure
where /mnt will not get properly formatted or mounted. This is due to
This release broke a lot of my machines, generating ordering cycles on
every machine.
Please see #1717477
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691489
Title:
fstab entries written by
This bug was fixed in the package cloud-init -
0.7.9-233-ge586fe35-0ubuntu1~16.04.1
---
cloud-init (0.7.9-233-ge586fe35-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium
* debian/cloud-init.templates: enable Scaleway cloud.
* debian/cloud-init.templates: enable Aliyun cloud.
*
This bug was fixed in the package cloud-init -
0.7.9-233-ge586fe35-0ubuntu1~17.04.1
---
cloud-init (0.7.9-233-ge586fe35-0ubuntu1~17.04.1) zesty; urgency=medium
* debian/cloud-init.templates: enable Scaleway cloud.
* debian/cloud-init.templates: enable Aliyun cloud.
* drop the
** Tags removed: verification-needed verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691489
Title:
fstab entries written by
Zesty verification:
# Saw initial failure before upgrade
ubuntu@zesty1:~$ dpkg-query --show cloud-init
cloud-init 0.7.9-153-g16a7302f-0ubuntu1~17.04.2
ubuntu@zesty1:~$ grep reformat /var/log/cloud-init.log
2017-09-12 22:08:16,313 - DataSourceAzure.py[DEBUG]: reformattable=True:
partition 1
Validated across multiple (5) 'clean' reboots that Azure vms don't hit
the race condition with mounts and don't result in cloud-init errors.
ubuntu@xen1:~$ dpkg-query --show cloud-init
cloud-init 0.7.9-233-ge586fe35-0ubuntu1~16.04.1
ubuntu@xen1:~$ grep -i error /var/log/cloud-init.log
Hello Scott, 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-233-ge586fe35-0ubuntu1~16.04.1 in a few hours, and then in
the -proposed repository.
Please help us by testing
** Changed in: cloud-init
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691489
Title:
fstab entries written by cloud-config may not be mounted
To
** Description changed:
- As reported in bug 1686514, sometimes /mnt will not get mounted when re-
- delpoying or stopping-then-starting a Azure vm of L32S. This is
- probably a more generic issue, I suspect shown due to the speed of disks
- on these systems.
+ === Begin SRU Template ===
+
** Changed in: cloud-init
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691489
Title:
fstab entries written by cloud-config may not be mounted
To manage
This bug was fixed in the package cloud-init -
0.7.9-231-g80bf98b9-0ubuntu1
---
cloud-init (0.7.9-231-g80bf98b9-0ubuntu1) artful; urgency=medium
* New upstream snapshot.
- tests: remove 'yakkety' from releases as it is EOL.
- systemd: make systemd-fsck run after
** 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
** Also affects: cloud-init (Ubuntu Artful)
Importance: Medium
21 matches
Mail list logo
