[SRU] cloud-init Windows Azure does not have correct futil support for disk format support
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Precise |
Fix Released
|
High
|
Unassigned |
Bug Description
[SRU Justification]
[Explanation] SRU for 1292648 added the ability Cloud-init to format ephemeral devices when a new ephemeral device was put into place. The backport used util.* instead of futil.*.
[IMPACT] Cloud-init stack traces when attempting unmount a device that is not mounted
Cloud-init tries to unmount the default ephemeral disk and uses "try/except" method. Since the wrong util is used, it will stack trace, preventing users from provisioning on Windows Azure.
[TEST-CASE #1] Scratch Boot
1. Build new image from scratch
2. Boot, it should work with ephemeral0 mounted
[TEST-CASE #2] Replace ephemeral0
1. Using test-case #1 instance, remove /dev/sdb1 from /etc/fstab
2. Run "wipefs --all /dev/sdb1"; reboot; device should not be mounted nor should it appear in /etc/fstab
3. Run "mkfs.ext4 /dev/sdb1"; reboot; device should not be mounted nor should it appear in /etc/fstab
4. Run "mkfs.ntfs -L 'Temporary Storage' -f /dev/sdb1 && mount /dev/sdb1 /mnt && touch /mnt/test"; reboot; device should not be mounted nor should it appear in /etc/fstab
5. Run "mount /dev/sdb1 /mnt && rm /mnt/test"; reboot; /dev/sdb1 should be mounted w/ ext4 fs and on /mnt
[TEST-CASE #3] Re-bundle Image
1. Build new image from scratch
2. Boot
3. Capture VM
4. Boot Captured VM, it should have ephemeral0 mounted
Latest Cloud-init on Windows Azure fails to provision on Windows Azure due to incorrect import.
2014-04-03 21:53:24,330 - __init_
2014-04-03 21:53:24,374 - util.py[DEBUG]: Traceback (most recent call last):
File "/usr/lib/
if s.get_data():
File "/usr/lib/
cc_
File "/usr/lib/
except util.ProcessExe
AttributeError: 'module' object has no attribute 'ProcessExecuti
2014-04-03 21:53:24,374 - __init__.py[DEBUG]: Did not find data source. searched classes: ['DataSourceAzu
(END)
Related branches
description: | updated |
tags: | added: patch |
affects: | ubuntu → cloud-init (Ubuntu) |
description: | updated |
Changed in cloud-init (Ubuntu Precise): | |
assignee: | nobody → Ben Howard (utlemming) |
importance: | Undecided → High |
summary: |
- cloud-init datasource uses util.ProcessExecutionError instead of + [SRU] cloud-init datasource uses util.ProcessExecutionError instead of futil.ProcessExecutionError |
description: | updated |
Changed in cloud-init (Ubuntu Precise): | |
status: | New → Fix Committed |
Changed in cloud-init (Ubuntu): | |
status: | Confirmed → Fix Released |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1302229/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]