Setting "timezone:" fails: NameError: global name 'set_etc_timezone' is not defined
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Current utopic's cloud-init fails to set a proper timezone. In my userdata I have "timezone: Europe/Berlin", but in the generated VM /etc/timezone has the default "Etc/UTC", and /etc/localtime is also just UTC.
A look at the log files shows that the timezone plugin crashes. cloud-init-
2014-09-05 04:46:27,281 - util.py[WARNING]: Running module timezone (<module 'cloudinit.
cloud-init.log:
Sep 5 04:46:27 autopkgtest [CLOUDINIT] stages.py[DEBUG]: Running module timezone (<module 'cloudinit.
Sep 5 04:46:27 autopkgtest [CLOUDINIT] util.py[DEBUG]: Writing to /var/lib/
Sep 5 04:46:27 autopkgtest [CLOUDINIT] helpers.py[DEBUG]: Running config-timezone using lock (<FileLock using file '/var/lib/
Sep 5 04:46:27 autopkgtest [CLOUDINIT] util.py[WARNING]: Running module timezone (<module 'cloudinit.
Sep 5 04:46:27 autopkgtest [CLOUDINIT] util.py[DEBUG]: Running module timezone (<module 'cloudinit.
I attach both complete files for reference.
I noticed this in VMs generated by "adt-buildvm-
Current utopic's cloud-init version is 0.7.6~bzr992-
description: | updated |
tags: | added: regression-release utopic |
this is fix-released in any thing newere than revision 1008.