[Yahoo-eng-team] [Bug 1506244] [NEW] support SSH key value over fingerprint for Azure
Public bug reported: Azure is changing the ovf-env.xml file. Instead of passing a fingerprint to the key and obtaining it separately, the SSH public key itself is passed via a new "" parameters: EB0C0AB4B2D5FC35F2F0658D19F44C8283E2DD62 $HOME/UserName/.ssh/authorized_keys ssh-rsa NOTAREALKEY== foo@bar.local ** Affects: cloud-init Importance: Undecided Assignee: Ben Howard (utlemming) Status: New ** Changed in: cloud-init Assignee: (unassigned) => Ben Howard (utlemming) ** Branch linked: lp:~utlemming/cloud-init/lp1506244-ssh-key-value -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1506244 Title: support SSH key value over fingerprint for Azure Status in cloud-init: New Bug description: Azure is changing the ovf-env.xml file. Instead of passing a fingerprint to the key and obtaining it separately, the SSH public key itself is passed via a new "" parameters: EB0C0AB4B2D5FC35F2F0658D19F44C8283E2DD62 $HOME/UserName/.ssh/authorized_keys ssh-rsa NOTAREALKEY== foo@bar.local To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1506244/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1506244] Re: support SSH key value over fingerprint for Azure
** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Trusty) Importance: Undecided Status: New ** Summary changed: - support SSH key value over fingerprint for Azure + [SRU] support SSH key value over fingerprint for Azure ** Description changed: - Azure is changing the ovf-env.xml file. Instead of passing a fingerprint - to the key and obtaining it separately, the SSH public key itself is - passed via a new "" parameters: + SRU JUSTIFICATION - - - - EB0C0AB4B2D5FC35F2F0658D19F44C8283E2DD62 - $HOME/UserName/.ssh/authorized_keys - ssh-rsa NOTAREALKEY== foo@bar.local - - + [BACKGROUND] Azure's meta-data source now supports the use of SSH key + values in addition to fingerprints. + + [IMPACT] Instances booted with out cloud-init support for SSH public key + values will be inaccessable on boot via SSH. + + [FIX] Backport of 15.10 SSH public key support. Starting with 15.10, + cloud-init supports both values (preferred) or generating the SSH public + key from a fingerprint. + + [TEST CASE] + - Update cloud-init from proposed + - Capture instance + - Create instance using SSH fingerprint, confirm instance is accessible via SSH. + - Create instance using SSH public key value, confirm instance is accessible via SSH. + - Create instance using both SSH fingerprint and a different SSH public key value. Confirm that the instance is accessible via SSH only with SSH public key value (i.e. the fingerprint is ignored). + + + [ORIGINAL REPORT] + Azure is changing the ovf-env.xml file. Instead of passing a fingerprint to the key and obtaining it separately, the SSH public key itself is passed via a new "" parameters: + + + + + EB0C0AB4B2D5FC35F2F0658D19F44C8283E2DD62 + $HOME/UserName/.ssh/authorized_keys + ssh-rsa NOTAREALKEY== foo@bar.local + + ** Changed in: cloud-init Status: New => Fix Released ** Changed in: cloud-init (Ubuntu) Status: New => In Progress ** Changed in: cloud-init (Ubuntu Precise) Status: New => In Progress ** Changed in: cloud-init (Ubuntu Trusty) Status: New => In Progress ** Changed in: cloud-init (Ubuntu Vivid) Status: New => In Progress ** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: In Progress ** Also affects: cloud-init (Ubuntu Wily) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Wily) Status: New => Fix Released ** Changed in: cloud-init (Ubuntu Xenial) Status: In Progress => Fix Released ** Changed in: cloud-init (Ubuntu Xenial) Assignee: (unassigned) => Ben Howard (utlemming) ** Changed in: cloud-init (Ubuntu Wily) Assignee: (unassigned) => Ben Howard (utlemming) ** Changed in: cloud-init (Ubuntu Vivid) Assignee: (unassigned) => Ben Howard (utlemming) ** Changed in: cloud-init (Ubuntu Trusty) Assignee: (unassigned) => Ben Howard (utlemming) ** Changed in: cloud-init (Ubuntu Precise) Assignee: (unassigned) => Ben Howard (utlemming) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1506244 Title: [SRU] support SSH key value over fingerprint for Azure Status in cloud-init: Fix Released Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Precise: In Progress Status in cloud-init source package in Trusty: In Progress Status in cloud-init source package in Vivid: In Progress Status in cloud-init source package in Wily: Fix Released Status in cloud-init source package in Xenial: Fix Released Bug description: SRU JUSTIFICATION [BACKGROUND] Azure's meta-data source now supports the use of SSH key values in addition to fingerprints. [IMPACT] Instances booted with out cloud-init support for SSH public key values will be inaccessable on boot via SSH. [FIX] Backport of 15.10 SSH public key support. Starting with 15.10, cloud-init supports both values (preferred) or generating the SSH public key from a fingerprint. [TEST CASE] - Update cloud-init from proposed - Capture instance - Create instance using SSH fingerprint, confirm instance is accessible via SSH. - Create instance using SSH public key value, confirm instance is accessible via SSH. - Create instance using both SSH fingerprint and a different SSH public key value. Confirm that the instance is accessible via SSH only with SSH public key value (i.e. the fi
[Yahoo-eng-team] [Bug 1292648] Re: [SRU] cloud-init should check/format Azure empheral disks each boot
This was fixed released a long time ago. ** Changed in: cloud-init Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1292648 Title: [SRU] cloud-init should check/format Azure empheral disks each boot Status in Init scripts for use on cloud images: Fix Released Status in “cloud-init” package in Ubuntu: Fix Released Status in “cloud-init” source package in Precise: Fix Released Status in “cloud-init” source package in Saucy: Fix Released Bug description: SRU Justification [IMPACT] Users on Windows Azure are guaranteed to have the ephemeral device as ext4 for the first boot. Subsequent boots may result in fuse mounted NTFS file system. [TEST CASE] Defined in comment 3. [Regression Potential] Low. This change is scope only to the Windows Azure datasource and the behavior complies with expected behavior of Windows Azure: the ephemeral disk is not durable between boots. From Microsoft documentation: > Because data on a resource disk may not be durable across reboots, it is often used by > applications and processes running in the virtual machine for transient and temporary > storage of data. It is also used to store page or swap files for the operating system. (See http://www.windowsazure.com/en-us/documentation/articles/storage-windows-attach-disk/) Even so, the change to Cloud-init is scope to only replace the ephemeral disk when the disk is 1) NTFS; 2) has a label of "Temporary Storage"; and 3) has no files on it. When the disk matches, cloud-init will turn the code paths for formating the ephemeral disk for that boot only. [ORIGINAL REPORT] On Windows Azure, the ephemeral disk should be treated as ephemeral per boot, not per instance. Microsoft has informed us that under the following conditions an ephemeral disk may disappear: 1. The user resizes the instance 2. A fault causes the instance to move from one physical host to another 3. A machine is shutdown and then started again Essentially, on Azure, the ephemeral disk is extremely ephemeral. Users who hit any of the above situations are discovering that /mnt is mount with their default NTFS file system. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cloud-init 0.7.5~bzr964-0ubuntu1 [modified: usr/lib/python2.7/dist-packages/cloudinit/config/cc_disk_setup.py usr/lib/python2.7/dist-packages/cloudinit/config/cc_final_message.py usr/lib/python2.7/dist-packages/cloudinit/config/cc_seed_random.py usr/lib/python2.7/dist-packages/cloudinit/sources/DataSourceAzure.py usr/lib/python2.7/dist-packages/cloudinit/sources/DataSourceCloudSigma.py usr/lib/python2.7/dist-packages/cloudinit/sources/DataSourceSmartOS.py] ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 Date: Fri Mar 14 17:53:20 2014 PackageArchitecture: all SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1292648/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1316475] Re: [SRU] CloudSigma DS for causes hangs when serial console present
** Changed in: cloud-init Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1316475 Title: [SRU] CloudSigma DS for causes hangs when serial console present Status in Init scripts for use on cloud images: Fix Released Status in Openstack disk image builder: Fix Released Status in tripleo - openstack on openstack: Invalid Status in “cloud-init” package in Ubuntu: Fix Released Status in “cloud-init” source package in Trusty: Fix Released Bug description: SRU Justification Impact: The Cloud Sigma Datasource read and writes to /dev/ttyS1 if present; the Datasource does not have a time out. On non-CloudSigma Clouds or systems w/ /dev/ttyS1, Cloud-init will block pending a response, which may never come. Further, it is dangerous for a default datasource to write blindly on a serial console as other control plane software and Clouds use /dev/ttyS1 for communication. Fix: The patch queries the BIOS to see if the instance is running on CloudSigma before querying /dev/ttys1. Verification: On both a CloudSigma instance and non-CloudSigma instance with /dev/ttys1: 1. Install new cloud-init 2. Purge existing cloud-init data (rm -rf /var/lib/cloud) 3. Run "cloud-init --debug init" 4. Confirm that CloudSigma provisioned while CloudSigma datasource skipped non-CloudSigma instance Regression: The risk is low, as this change further restrict where the CloudSigma Datasource can run. [Original Report] DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 3 (xid=0x7e777c23) DHCPREQUEST of 10.22.157.186 on eth2 to 255.255.255.255 port 67 (xid=0x7e777c23) DHCPOFFER of 10.22.157.186 from 10.22.157.149 DHCPACK of 10.22.157.186 from 10.22.157.149 bound to 10.22.157.186 -- renewal in 39589 seconds. * Starting Mount network filesystems[ OK ] * Starting configure network device [ OK ] * Stopping Mount network filesystems[ OK ] * Stopping DHCP any connected, but unconfigured network interfaces [ OK ] * Starting configure network device [ OK ] * Stopping DHCP any connected, but unconfigured network interfaces [ OK ] * Starting configure network device [ OK ] And it stops there. I see this on about 10% of deploys. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1316475/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1201969] Re: cloud-init parses Azure setting "DisableSshPassword" incorrectly
** Changed in: cloud-init Status: Fix Committed => Fix Released ** Changed in: cloud-init Assignee: (unassigned) => Ben Howard (utlemming) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1201969 Title: cloud-init parses Azure setting "DisableSshPassword" incorrectly Status in Init scripts for use on cloud images: Fix Released Status in “cloud-init” package in Ubuntu: Fix Released Bug description: Cloud-init is parsing ovf-env.xml incorrecltly. Currently cloud-init takes the value of DisableSshPasswordAuthentication and uses it to set ssh_pwauth. However, DisableSshPasswordAuthentication describes the state of whether or not SSH password authentication should be disabled, while ssh_psauth is asking if it should be enabled or not. To illustration: Setting DisableSshPasswordAuthentication to true means that password authentication should be disabled. While setting cloud-init ssh_pwauth to true means that password authentication should be enabled. The fix for this is to set "ssh_pwauth" to the inverse of DisableSshPasswordAuthentication Patch: === modified file 'cloudinit/sources/DataSourceAzure.py' --- cloudinit/sources/DataSourceAzure.py 2013-07-11 14:16:18 + +++ cloudinit/sources/DataSourceAzure.py 2013-07-16 21:13:26 + @@ -313,7 +313,10 @@ elif name == "ssh": cfg['_pubkeys'] = load_azure_ovf_pubkeys(child) elif name == "disablesshpasswordauthentication": -cfg['ssh_pwauth'] = util.is_true(value) +# The verb 'disablessh..." asks whether to disable password auth. +# Since it is disabled by default, "false" indicates that +# password authentication should be enabled. +cfg['ssh_pwauth'] = util.is_false(value) elif simple: if name in md_props: md[name] = value To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1201969/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1637252] [NEW] sysconfig.py fails to configure network
Public bug reported:
Cloud-init sysconfig.py does not render the subnet configuration
properly when the datasource provides a network configruation.
This can be seen on OpenSUSE LEAP 42 and the upcoming Fedora 25.
Cloud-init v. 0.7.8 running 'init-local' at Wed, 26 Oct 2016 21:49:31 +. Up
6.08 seconds.
2016-10-26 21:49:31,477 - util.py[WARNING]: failed stage init-local
failed run of stage init-local
Traceback (most recent call last):
File "/usr/lib/python3.5/site-packages/cloudinit/cmd/main.py", line 521, in
status_wrapper
ret = functor(name, args)
File "/usr/lib/python3.5/site-packages/cloudinit/cmd/main.py", line 280, in
main_init
init.apply_network_config(bring_up=bool(mode != sources.DSMODE_LOCAL))
File "/usr/lib/python3.5/site-packages/cloudinit/stages.py", line 650, in
apply_network_config
return self.distro.apply_network_config(netcfg, bring_up=bring_up)
File "/usr/lib/python3.5/site-packages/cloudinit/distros/__init__.py", line
162, in apply_network_config
dev_names = self._write_network_config(netconfig)
File "/usr/lib/python3.5/site-packages/cloudinit/distros/rhel.py", line 73,
in _write_network_config
self._net_renderer.render_network_state("/", ns)
File "/usr/lib/python3.5/site-packages/cloudinit/net/sysconfig.py", line 389,
in render_network_state
network_state).items():
File "/usr/lib/python3.5/site-packages/cloudinit/net/sysconfig.py", line 371,
in _render_sysconfig
cls._render_physical_interfaces(network_state, iface_contents)
File "/usr/lib/python3.5/site-packages/cloudinit/net/sysconfig.py", line 297,
in _render_physical_interfaces
start=len(iface.children)):
AttributeError: 'dict' object has no attribute 'children
** Affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1637252
Title:
sysconfig.py fails to configure network
Status in cloud-init:
New
Bug description:
Cloud-init sysconfig.py does not render the subnet configuration
properly when the datasource provides a network configruation.
This can be seen on OpenSUSE LEAP 42 and the upcoming Fedora 25.
Cloud-init v. 0.7.8 running 'init-local' at Wed, 26 Oct 2016 21:49:31 +.
Up 6.08 seconds.
2016-10-26 21:49:31,477 - util.py[WARNING]: failed stage init-local
failed run of stage init-local
Traceback (most recent call last):
File "/usr/lib/python3.5/site-packages/cloudinit/cmd/main.py", line 521, in
status_wrapper
ret = functor(name, args)
File "/usr/lib/python3.5/site-packages/cloudinit/cmd/main.py", line 280, in
main_init
init.apply_network_config(bring_up=bool(mode != sources.DSMODE_LOCAL))
File "/usr/lib/python3.5/site-packages/cloudinit/stages.py", line 650, in
apply_network_config
return self.distro.apply_network_config(netcfg, bring_up=bring_up)
File "/usr/lib/python3.5/site-packages/cloudinit/distros/__init__.py", line
162, in apply_network_config
dev_names = self._write_network_config(netconfig)
File "/usr/lib/python3.5/site-packages/cloudinit/distros/rhel.py", line 73,
in _write_network_config
self._net_renderer.render_network_state("/", ns)
File "/usr/lib/python3.5/site-packages/cloudinit/net/sysconfig.py", line
389, in render_network_state
network_state).items():
File "/usr/lib/python3.5/site-packages/cloudinit/net/sysconfig.py", line
371, in _render_sysconfig
cls._render_physical_interfaces(network_state, iface_contents)
File "/usr/lib/python3.5/site-packages/cloudinit/net/sysconfig.py", line
297, in _render_physical_interfaces
start=len(iface.children)):
AttributeError: 'dict' object has no attribute 'children
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1637252/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1675571] [NEW] 0.7.9-48-g1c795b9-0ubuntu1~16.04.1 with multiple eth0 definitions has no resolvers
Public bug reported:
Regresion from Bug #1657940.
When provisioning with multiple eth0 addresses, /etc/resolv.conf is
empty:
Consider:
root@tester:~# cat /etc/network/interfaces.d/50-cloud-init.cfg
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 138.197.98.102
dns-nameservers 8.8.8.8 8.8.4.4
gateway 138.197.96.1
netmask 255.255.240.0
# control-alias eth0
iface eth0 inet static
address 10.17.0.11
netmask 255.255.0.0
Which then yields an empty /etc/resolv.conf:
root@tester:/run/resolvconf# cat interface/eth0.inet
root@tester:/run/resolvconf# cd /
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
The problem is that resolvconfg does pattern matching for eth*.inet. The
second definition of eth0 has no nameserver and therefore overrides the
definition.
** Affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1675571
Title:
0.7.9-48-g1c795b9-0ubuntu1~16.04.1 with multiple eth0 definitions has
no resolvers
Status in cloud-init:
New
Bug description:
Regresion from Bug #1657940.
When provisioning with multiple eth0 addresses, /etc/resolv.conf is
empty:
Consider:
root@tester:~# cat /etc/network/interfaces.d/50-cloud-init.cfg
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 138.197.98.102
dns-nameservers 8.8.8.8 8.8.4.4
gateway 138.197.96.1
netmask 255.255.240.0
# control-alias eth0
iface eth0 inet static
address 10.17.0.11
netmask 255.255.0.0
Which then yields an empty /etc/resolv.conf:
root@tester:/run/resolvconf# cat interface/eth0.inet
root@tester:/run/resolvconf# cd /
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
The problem is that resolvconfg does pattern matching for eth*.inet.
The second definition of eth0 has no nameserver and therefore
overrides the definition.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1675571/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1675571] Re: 0.7.9-48-g1c795b9-0ubuntu1~16.04.1 with multiple eth0 definitions has no resolvers
** Project changed: cloud-init => cloud-init (Ubuntu)
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1675571
Title:
0.7.9-48-g1c795b9-0ubuntu1~16.04.1 with multiple eth0 definitions has
no resolvers
Status in cloud-init:
Confirmed
Status in cloud-init package in Ubuntu:
Confirmed
Bug description:
Regresion from Bug #1657940.
When provisioning with multiple eth0 addresses, /etc/resolv.conf is
empty:
Consider:
root@tester:~# cat /etc/network/interfaces.d/50-cloud-init.cfg
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 138.197.98.102
dns-nameservers 8.8.8.8 8.8.4.4
gateway 138.197.96.1
netmask 255.255.240.0
# control-alias eth0
iface eth0 inet static
address 10.17.0.11
netmask 255.255.0.0
Which then yields an empty /etc/resolv.conf:
root@tester:/run/resolvconf# cat interface/eth0.inet
root@tester:/run/resolvconf# cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
The problem is that resolvconfg does pattern matching for eth*.inet.
The second definition of eth0 has no nameserver and therefore
overrides the definition.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1675571/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1676908] [NEW] DigitalOcean network improvements
Public bug reported: This is a request to merge the improvements to the linked PR that improves the DigitalOcean datasource. The changes: - No longer bind the nameservers to a specific interface to bring it inline with the other DataSources like OpenStack and SmartOS. - Fix mis-binding the IPV4all address to a secondary interface by considering 'eth0' or 'ens3' first - Consider all network definitions, not just 'public' or 'private'. ** Affects: cloud-init Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1676908 Title: DigitalOcean network improvements Status in cloud-init: New Bug description: This is a request to merge the improvements to the linked PR that improves the DigitalOcean datasource. The changes: - No longer bind the nameservers to a specific interface to bring it inline with the other DataSources like OpenStack and SmartOS. - Fix mis-binding the IPV4all address to a secondary interface by considering 'eth0' or 'ens3' first - Consider all network definitions, not just 'public' or 'private'. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1676908/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1681531] [NEW] networking.service fails on ifup if networking configured via cloud-init
Public bug reported:
When cloud-init configures networking, it uses `ifup`. However, after
cloud-init is done, networking.service runs and attempts an `ifup -a
--read-environment` it fails since the devices are already configured
with a "RTNETLINK answers: File exists" (return code of 1).
The end result is that any service with a dependency of networking fails
to start.
--
>From /var/log/cloud-init.log:
2017-04-10 17:36:11,608 - util.py[DEBUG]: Running command ['ip', 'link', 'set',
'ens3', 'down'] with allowed return codes [0] (shell=False, capture=True)
2017-04-10 17:36:11,615 - util.py[DEBUG]: Running command ['ip', 'link', 'set',
'ens3', 'name', 'eth0'] with allowed return codes [0] (shell=False,
capture=True)
2017-04-10 17:36:11,635 - util.py[DEBUG]: Running command ['ip', 'link', 'set',
'ens4', 'name', 'eth1'] with allowed return codes [0] (shell=False,
capture=True)
2017-04-10 17:36:11,651 - util.py[DEBUG]: Running command ['ip', 'link', 'set',
'eth0', 'up'] with allowed return codes [0] (shell=False, capture=True)
2017-04-10 17:36:11,654 - stages.py[INFO]: Applying network configuration from
ds bringup=False: {'version': 1, 'config': [{'name': 'eth0', 'subnets':
[{'address': '138.197.88.85', 'netmask': '255.255.240.0', 'gateway':
'138.197.80.1', 'type': 'static', 'control': 'auto'}, {'address':
'2604:A880:0800:0010:::2ECE:D001/64', 'gateway':
'2604:A880:0800:0010::::0001', 'type': 'static', 'control':
'auto'}, {'address': '10.17.0.10', 'netmask': '255.255.0.0', 'type': 'static',
'control': 'auto'}], 'mac_address': 'ee:90:f2:c6:dc:db', 'type': 'physical'},
{'name': 'eth1', 'subnets': [{'address': '10.132.92.131', 'netmask':
'255.255.0.0', 'gateway': '10.132.0.1', 'type': 'static', 'control': 'auto'}],
'mac_address': '1a:b6:7c:24:5e:cd', 'type': 'physical'}, {'address':
['2001:4860:4860::8844', '2001:4860:4860::', '8.8.8.8'], 'type':
'nameserver'}]}
2017-04-10 17:36:11,668 - util.py[DEBUG]: Writing to
/etc/network/interfaces.d/50-cloud-init.cfg - wb: [420] 868 bytes
2017-04-10 17:36:11,669 - main.py[DEBUG]: [local] Exiting. datasource
DataSourceDigitalOcean not in local mode.
2017-04-10 17:36:11,674 - util.py[DEBUG]: Reading from /proc/uptime
(quiet=False)
--
>From 'dmesg':
Apr 10 17:36:11 ubuntu systemd[1]: Started Initial cloud-init job
(pre-networking).
Apr 10 17:36:12 ubuntu systemd[1]: Started LSB: AppArmor initialization.
Apr 10 17:36:12 ubuntu systemd[1]: Reached target Network (Pre).
Apr 10 17:36:12 ubuntu systemd[1]: Starting Raise network interfaces...
Apr 10 17:36:13 ubuntu ifup[1099]: Waiting for DAD... Done
Apr 10 17:36:13 ubuntu ifup[1099]: RTNETLINK answers: File exists
Apr 10 17:36:13 ubuntu ifup[1099]: Failed to bring up eth1.
--
$ sudo journalctl -xe -u networking
Apr 10 17:36:12 ubuntu systemd[1]: Starting Raise network interfaces...
-- Subject: Unit networking.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit networking.service has begun starting up.
Apr 10 17:36:13 ubuntu ifup[1099]: Waiting for DAD... Done
Apr 10 17:36:13 ubuntu ifup[1099]: RTNETLINK answers: File exists
Apr 10 17:36:13 ubuntu ifup[1099]: Failed to bring up eth1.
Apr 10 17:36:13 ubuntu systemd[1]: networking.service: Main process exited,
code=exited, status=1/FAILURE
Apr 10 17:36:13 ubuntu systemd[1]: Failed to start Raise network interfaces.
-- Subject: Unit networking.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit networking.service has failed.
--
** Affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Project changed: cloud-init => cloud-init (Ubuntu)
** Summary changed:
- networking.service fails on ifup due to new rendering of 50-cloud-init.cfg
+ networking.service fails on ifup if networking configured via cloud-init
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1681531
Title:
networking.service fails on ifup if networking configured via cloud-
init
Status in cloud-init package in Ubuntu:
New
Bug description:
When cloud-init configures networking, it uses `ifup`. However, after
cloud-init is done, networking.service runs and attempts an `ifup -a
--read-environment` it fails since the devices are already configured
with a "RTNETLINK answers: File exists" (return code of 1).
The end result is that any service with a dependency of networking
fails to start.
--
From /v
[Yahoo-eng-team] [Bug 1676908] Re: DigitalOcean network improvements
Commits have landed, calling this fix released. ** Changed in: cloud-init Status: New => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1676908 Title: DigitalOcean network improvements Status in cloud-init: Fix Released Bug description: This is a request to merge the improvements to the linked PR that improves the DigitalOcean datasource. The changes: - No longer bind the nameservers to a specific interface to bring it inline with the other DataSources like OpenStack and SmartOS. - Fix mis-binding the IPV4all address to a secondary interface by considering 'eth0' or 'ens3' first - Consider all network definitions, not just 'public' or 'private'. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1676908/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1676908] Re: DigitalOcean network improvements
Whoops, the fixes are committed, not released. ** Changed in: cloud-init Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1676908 Title: DigitalOcean network improvements Status in cloud-init: Fix Committed Bug description: This is a request to merge the improvements to the linked PR that improves the DigitalOcean datasource. The changes: - No longer bind the nameservers to a specific interface to bring it inline with the other DataSources like OpenStack and SmartOS. - Fix mis-binding the IPV4all address to a secondary interface by considering 'eth0' or 'ens3' first - Consider all network definitions, not just 'public' or 'private'. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1676908/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1546230] Re: change the default to the nocloud data source
Nack'ing this request. After discussing this idea with the server team offline, this is not desirable. For Snappy and images, livecd-rootfs and/or the image build process should drive the image specific cloud- init configuation. ** Changed in: cloud-init Status: New => Invalid ** Changed in: cloud-init Assignee: (unassigned) => Ben Howard (utlemming) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1546230 Title: change the default to the nocloud data source Status in cloud-init: Invalid Bug description: Today, having cloud-init instead defaults to a data source that might not be the correct one, ideally cloud-init should have a sane default of the common denominator which would be a nocloud data source. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1546230/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1456684] Re: [SRU] cloud-init does not know central (eu-central-1) is a direction for ec2 zones
** Summary changed: - does not know central (eu-central-1) is a direction for ec2 zones + [SRU] cloud-init does not know central (eu-central-1) is a direction for ec2 zones ** Also affects: cloud-init (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Vivid) Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1456684 Title: [SRU] cloud-init does not know central (eu-central-1) is a direction for ec2 zones Status in cloud-init: Fix Committed Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Precise: New Status in cloud-init source package in Trusty: New Status in cloud-init source package in Vivid: New Bug description: cloud-init's code that tries to determine if it is in a ec2 region is simply unaware of the 'central' direction. [Impact] Ubuntu instances launched in the eu-central-1 EC2 region will not discover region-local mirrors. The user will see a degraded experience as they have to interact with mirrors that are further away and under heavier load. They will also potentially have to pay for the bandwidth used this way (as will the default mirror admins). [Test Case] Launch an instance in eu-central-1 and examine the apt sources used. They should be of the form "eu-central-1.ec2.archive.ubuntu.com" instead of "eu-central-1a.clouds.archive.ubuntu.com". [Regression Potential] Limited; the changes are limited to the mirror discovery, and if mirror discovery fails, we have default mirrors that we will use. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1456684/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1490796] Re: [SRU] cloud-init must check/format Azure ephemeral disks each boot
** Also affects: cloud-init (Ubuntu Precise) Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1490796 Title: [SRU] cloud-init must check/format Azure ephemeral disks each boot Status in cloud-init: Fix Committed Status in cloud-init package in Ubuntu: In Progress Status in cloud-init source package in Precise: New Status in cloud-init source package in Trusty: New Status in cloud-init source package in Vivid: New Bug description: [Impact] Sometimes when rebooting an instance in Azure, a different ephemeral disk will be presented. Azure ephemeral disks are presented as NTFS disks, but we reformat them to ext4. With the last cloud-init upload, we shifted to using /dev/disk symlinks to mount these disks (in case they are not presented as the same physical device). Unfortunately, the code that determines if we have a new ephemeral disk was not updated to handle symlinks, so never detects a new disk. [Test Case] 1) Boot an Azure instance and install the new cloud-init. 2) Change the size of the instance using the Azure web interface (as this near-guarantees that the ephemeral disk will be replaced with a new one). This will reboot the instance. 3) Once the instance is rebooted, SSH in and confirm that: a) An ext4 ephemeral disk is mounted at /mnt, and b) cloud-init.log indicates that a fabric formatted ephemeral disk was found on this boot. [Regression Potential] Limited; two LOCs change, to dereference symlinks instead of using paths verbatim. [Original Report] Ubuntu 14.04.3 (20150805) on Azure with cloud-init package 0.7.5-0ubuntu1.8. On Azure cloud-init prepares the ephemeral device as ext4 for the first boot. However, if the VM is ever moved to another Host for any reason, then a new ephemeral disk might be provided to the VM. This ephemeral disk is NTFS formatted, so for subsequent reboots cloud-init must detect and reformat the new disk as ext4. However, with cloud- init 0.7.5-0ubuntu1.8 subsequent boots may result in fuse mounted NTFS file system. This issue occurred in earlier versions of cloud-init, but was fixed with bug 1292648 (https://bugs.launchpad.net/ubuntu/+source/cloud- init/+bug/1292648). So this appears to be a regression. Repro: - Create an Ubuntu 14.04.3 VM on Azure - Resize the VM to a larger size (this typically moves the VM) - Log in and run 'blkid' to show an ntfs formatted ephemeral disk: # blkid /dev/sdb1: LABEL="Temporary Storage" UUID="A43C43DD3C43A95E" TYPE="ntfs" Expected results: - After resizing the ephemeral disk should be formatted as ext4. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1490796/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1411582] Re: [SRU] Azure data source should auto-detect ephemeral disk location
Calling this fix released. ** Changed in: cloud-init Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1411582 Title: [SRU] Azure data source should auto-detect ephemeral disk location Status in cloud-init: Fix Released Status in cloud-init package in Ubuntu: Fix Released Status in walinuxagent package in Ubuntu: Fix Released Status in cloud-init source package in Precise: Fix Released Status in walinuxagent source package in Precise: Fix Released Status in cloud-init source package in Trusty: Fix Released Status in walinuxagent source package in Trusty: Fix Released Status in cloud-init source package in Utopic: Invalid Status in walinuxagent source package in Utopic: Fix Released Status in cloud-init source package in Vivid: Fix Released Status in walinuxagent source package in Vivid: Fix Released Bug description: [Impact] The Azure ephemeral disk will not necessarily remain at the same /dev/sd* location between reboots. This means the drive may not be persistently mounted between reboots. [Test Case] 1) Boot an Azure instance with a cloud-init including this fix. 2) Ensure that the ephemeral disk is mounted at /mnt and formatted as ext4 3) Ensure that /etc/fstab refers to a /dev/disk/... symlink, rather than a /dev/sd* device. [Regression Potential] We now use a udev rule to discover the location of the disk; we have been assured by Microsoft that this rule will always work, so regression potential is minimal. [Original Report] Currently we assume it will be /dev/sdb, but this may change. There is an example of how to handle this in the Azure Linux agent. To quote stevez in a comment on bug 1410835: Device names are not persistent in Linux and could change, so it is not guaranteed that the ephemeral disk will be called /dev/sdb. Ideally this should be auto-detected in cloud-init at runtime (for example, see DeviceForIdePort() in the Azure Linux agent). To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1411582/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1493453] Re: [SRU] vendor_data isn't parsed properly when using the nocloud datasource
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1493453
Title:
[SRU] vendor_data isn't parsed properly when using the nocloud
datasource
Status in cloud-init:
Fix Released
Status in cloud-init package in Ubuntu:
Fix Released
Status in cloud-init source package in Trusty:
Fix Released
Status in cloud-init source package in Vivid:
Fix Released
Status in cloud-init source package in Wily:
Fix Released
Bug description:
SRU Justification:
[IMPACT] The NoCloud Datasource assigns vendor_data to the wrong
cloud-init internal variable. This causes the vendor_data to be
improperly parsed, and prevents it from being consummed.
[FIX] See original report below
[TESTING]
1. Start in-cloud instance
2. Update cloud-init to version in proposed
3. Populate /var/lib/cloud/seed/nocloud/{user,meta,vendor}-data:
meta-data:
instance-id: testing
user-data:
#cloud-config
packages:
- pastebinit
vendor-data:
#cloud-config
runcmd:
- [ "touch", "/tmp/vd-worked" ]
3. Configure instance for NoCloud DS:
$ cat > /etc/cloud/cloud.cfg.d/999-sru.cfg
[Yahoo-eng-team] [Bug 1423972] Re: cloud-init user-data mime conversion fails on base64 encoded data
** Changed in: cloud-init (Ubuntu)
Status: In Progress => Fix Released
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1423972
Title:
cloud-init user-data mime conversion fails on base64 encoded data
Status in cloud-init:
Fix Released
Status in cloud-init package in Ubuntu:
Fix Released
Bug description:
Cloud-init's conversion of user-data to mime fails when the user-data
is base64 encoded due to the Python2 to Python3 switch.
base64.b64decode in Python 2 returns a string, whilst Python3 returns
a byte stream.
Consider:
import base64
hi = "aGkK"
print(type(base64.b64decode(hi)).__name__)
if 'hi' in str(base64.b64decode(hi)):
print("works")
if 'hi' in base64.b64decode(hi):
print("works on Py2")
ben@prongs:~$ python /tmp/proof.py
str
works
works on Py2
ben@prongs:~$ python3 /tmp/proof.py
bytes
works
Traceback (most recent call last):
File "/tmp/proof.py", line 10, in
if 'hi' in base64.b64decode(hi):
TypeError: Type str doesn't support the buffer API
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1423972/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1422993] [NEW] cloud-init AzureDS fails on 15.04
Public bug reported: Ubuntu 15.04 fails to provision on Windows Azure: 2015-02-17 23:07:07,824 - util.py[DEBUG]: Getting data from failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/sources/__init__.py", line 255, in find_source if s.get_data(): File "/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceAzure.py", line 99, in get_data ret = util.mount_cb(cdev, load_azure_ds_dir) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 1493, in mount_cb ret = callback(mountpoint) File "/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceAzure.py", line 597, in load_azure_ds_dir contents = fp.read() File "/usr/lib/python3.4/encodings/ascii.py", line 26, in decode return codecs.ascii_decode(input, self.errors)[0] UnicodeDecodeError: 'ascii' codec can't decode byte 0xef in position 0: ordinal not in range(128) 2015-02-17 23:07:07,987 - util.py[WARNING]: No instance datasource found! Likely bad things to come! 2015-02-17 23:07:07,993 - util.py[DEBUG]: No instance datasource found! Likely bad things to come! ** Affects: cloud-init Importance: Undecided Status: New ** Affects: cloud-init (Ubuntu) Importance: High Status: Confirmed ** Also affects: cloud-init Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1422993 Title: cloud-init AzureDS fails on 15.04 Status in Init scripts for use on cloud images: New Status in cloud-init package in Ubuntu: Confirmed Bug description: Ubuntu 15.04 fails to provision on Windows Azure: 2015-02-17 23:07:07,824 - util.py[DEBUG]: Getting data from failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/sources/__init__.py", line 255, in find_source if s.get_data(): File "/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceAzure.py", line 99, in get_data ret = util.mount_cb(cdev, load_azure_ds_dir) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 1493, in mount_cb ret = callback(mountpoint) File "/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceAzure.py", line 597, in load_azure_ds_dir contents = fp.read() File "/usr/lib/python3.4/encodings/ascii.py", line 26, in decode return codecs.ascii_decode(input, self.errors)[0] UnicodeDecodeError: 'ascii' codec can't decode byte 0xef in position 0: ordinal not in range(128) 2015-02-17 23:07:07,987 - util.py[WARNING]: No instance datasource found! Likely bad things to come! 2015-02-17 23:07:07,993 - util.py[DEBUG]: No instance datasource found! Likely bad things to come! To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1422993/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1423972] Re: cloud-init skips cloud-config modules on 15.04 Azure
** Attachment added: "Potential patch"
https://bugs.launchpad.net/ubuntu/+bug/1423972/+attachment/4323594/+files/lp1423972.patched
** Also affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1423972
Title:
cloud-init skips cloud-config modules on 15.04 Azure
Status in Init scripts for use on cloud images:
New
Status in Ubuntu:
New
Bug description:
Cloud-init is skipping the init modules on Azure. The Azure Datasource
is run and then cloud-config modules are run. This prevents user-
creation, default SSH keys, etc.
[ORIGINAL REPORT]
Cloud-init is not creating the fabric defined user. The root cause
appears that the "users-groups" cloud-config module is not being run.
Feb 20 16:35:33 utl-vivid-en-200932 kernel: [ 34.032275] init: cloud-init
main process (603) terminated with status 1
Feb 20 16:35:33 utl-vivid-en-200932 kernel: [ 34.139874] init: Error while
reading from descriptor: Broken pipe
Feb 20 16:35:33 utl-vivid-en-200932 kernel: [ 34.152660] init: failsafe
main process (838) killed by TERM signal
Feb 20 16:12:47 utl-vivid-en-200910 [CLOUDINIT] util.py[DEBUG]: Running
module ssh-authkey-fingerprints ()
failed#012Traceback (m
ost recent call last):#012 File
"/usr/lib/python3/dist-packages/cloudinit/stages.py", line 664, in
_run_modules#012cc.run(run_name
, mod.handle, func_args, freq=freq)#012 File
"/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 63, in run#012
return self._
runners.run(name, functor, args, freq, clear_on_fail)#012 File
"/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 198, in run
#012results = functor(*args)#012 File
"/usr/lib/python3/dist-packages/cloudinit/config/cc_ssh_authkey_fingerprints.py",
line 103,
in handle#012(key_fn, key_entries) =
ssh_util.extract_authorized_keys(user_name)#012 File
"/usr/lib/python3/dist-packages/cloudini
t/ssh_util.py", line 211, in extract_authorized_keys#012(ssh_dir, pw_ent)
= users_ssh_info(username)#012 File "/usr/lib/python3/di
st-packages/cloudinit/ssh_util.py", line 204, in users_ssh_info#012pw_ent
= pwd.getpwnam(username)#012KeyError: 'getpwnam(): name n
ot found: utlemming'
Feb 20 16:12:47 utl-vivid-en-200910 [CLOUDINIT] stages.py[DEBUG]: Running
module keys-to-console () with
frequency once-per-instance
Snippet on the user
{'cfg': {'_pubkeys': [{'fingerprint':
'8ECDF2795861824ADBE631CF8FF016B85D2A0B04',
'path': '/home/utlemming/.ssh/authorized_keys'}],
'cloud_config_modules': [ ... ],
'disk_setup': {'ephemeral0': {'layout': [100],
'overwrite': True,
'table_type': 'gpt'}},
'fs_setup': [{'device': 'ephemeral0.1',
'filesystem': 'ext4',
'replace_fs': 'ntfs'}],
'ssh_pwauth': False,
'system_info': {'default_user': {'lock_passwd': False,
'name': 'utlemming',
'passwd': '...'}}},
In
---
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
DistroRelease: Ubuntu 15.04
Package: cloud-init 0.7.7~bzr1060-0ubuntu1
PackageArchitecture: all
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Tags: vivid uec-images
Uname: Linux 3.18.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1423972/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1422993] Re: cloud-init AzureDS fails on 15.04
** Changed in: cloud-init Status: Fix Committed => Fix Released ** Changed in: cloud-init (Ubuntu) Assignee: (unassigned) => Ben Howard (utlemming) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1422993 Title: cloud-init AzureDS fails on 15.04 Status in Init scripts for use on cloud images: Fix Released Status in cloud-init package in Ubuntu: Fix Released Bug description: Ubuntu 15.04 fails to provision on Windows Azure: 2015-02-17 23:07:07,824 - util.py[DEBUG]: Getting data from failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/sources/__init__.py", line 255, in find_source if s.get_data(): File "/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceAzure.py", line 99, in get_data ret = util.mount_cb(cdev, load_azure_ds_dir) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 1493, in mount_cb ret = callback(mountpoint) File "/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceAzure.py", line 597, in load_azure_ds_dir contents = fp.read() File "/usr/lib/python3.4/encodings/ascii.py", line 26, in decode return codecs.ascii_decode(input, self.errors)[0] UnicodeDecodeError: 'ascii' codec can't decode byte 0xef in position 0: ordinal not in range(128) 2015-02-17 23:07:07,987 - util.py[WARNING]: No instance datasource found! Likely bad things to come! 2015-02-17 23:07:07,993 - util.py[DEBUG]: No instance datasource found! Likely bad things to come! To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1422993/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1422388] Re: Fetch passwords from CloudStack virtual router
** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu) Milestone: None => precise-updates ** Also affects: cloud-init (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Precise) Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1422388 Title: Fetch passwords from CloudStack virtual router Status in Init scripts for use on cloud images: Fix Committed Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Precise: New Status in cloud-init source package in Trusty: New Status in cloud-init source package in Utopic: New Bug description: CloudStack supports setting passwords in instances, which it would be helpful to support. See [0] for the documentation of this functionality, and [1] for their implementation of it. [0] https://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.0.2/html/Admin_Guide/add-password-management-to-templates.html [1] https://github.com/shankerbalan/cloudstack-scripts/blob/master/cloud-set-guest-password-ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1422388/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1444086] Re: cloud-init removes SharedConfig.XML on new instances of Azure
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Ben Howard (utlemming)
** Package changed: cloud-init (Ubuntu) => walinuxagent (Ubuntu)
** Changed in: walinuxagent (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1444086
Title:
cloud-init removes SharedConfig.XML on new instances of Azure
Status in Init scripts for use on cloud images:
Confirmed
Status in walinuxagent package in Ubuntu:
Confirmed
Bug description:
The Azure DS is removing /var/lib/waagent/SharedConfig.xml on first
boot, causing walinuxagent to fail.
Apr 14 11:46:24 ubuntu [CLOUDINIT] util.py[DEBUG]: Attempting to remove
/var/lib/waagent/SharedConfig.xml
Apr 14 11:46:24 ubuntu [CLOUDINIT] DataSourceAzure.py[INFO]: removed stale
file(s) in '/var/lib/waagent': ['/var/lib/waagent/SharedConfig.xml']
Apr 14 11:46:24 ubuntu [CLOUDINIT] util.py[DEBUG]: Writing to
/var/lib/waagent/ovf-env.xml - wb: [384] 1632 bytes
Apr 14 11:46:24 ubuntu [CLOUDINIT] util.py[DEBUG]: Running command hostname
with allowed return codes [0] (shell=False, capture=True)
Apr 14 11:46:24 ubuntu [CLOUDINIT] util.py[DEBUG]: Running command
['hostname', 'daily-vivid-0414-1ce494fec4'] with allowed return codes [0]
(shell=False, capture=True)
Apr 14 11:46:24 ubuntu [CLOUDINIT] DataSourceAzure.py[DEBUG]: pubhname:
publishing hostname [phostname=ubuntu hostname=daily-vivid-0414-1ce494fec4
policy=True interface=eth0]
Apr 14 11:46:24 ubuntu [CLOUDINIT] util.py[DEBUG]: Reading from /proc/uptime
(quiet=False)
Apr 14 11:46:24 ubuntu [CLOUDINIT] util.py[DEBUG]: Read 11 bytes from
/proc/uptime
Apr 14 11:46:24 ubuntu [CLOUDINIT] util.py[DEBUG]: Running command ['sh',
'-xc', 'i=$interface; x=0; ifdown $i || x=$?; ifup $i || x=$?; exit $x'] with
allowed return codes [0] (shell=False, capture=False)
Apr 14 11:46:26 ubuntu [CLOUDINIT] util.py[DEBUG]: Reading from /proc/uptime
(quiet=False)
Apr 14 11:46:26 ubuntu [CLOUDINIT] util.py[DEBUG]: Read 11 bytes from
/proc/uptime
Apr 14 11:46:26 ubuntu [CLOUDINIT] util.py[DEBUG]: publishing hostname took
2.119 seconds (2.12)
Apr 14 11:46:26 ubuntu [CLOUDINIT] DataSourceAzure.py[DEBUG]: invoking agent:
['service', 'walinuxagent', 'start']
Apr 14 11:46:26 ubuntu [CLOUDINIT] util.py[DEBUG]: Running command
['service', 'walinuxagent', 'start'] with allowed return codes [0]
(shell=False, capture=True)
Apr 14 11:47:27 ubuntu [CLOUDINIT] util.py[DEBUG]: waiting for files took
60.959 seconds
Apr 14 11:47:27 ubuntu [CLOUDINIT] DataSourceAzure.py[WARNING]: Did not find
files, but going on: {'/var/lib/waagent/SharedConfig.xml'}
Apr 14 11:47:27 ubuntu [CLOUDINIT] DataSourceAzure.py[WARNING]:
SharedConfig.xml missing, using static instance-id
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1444086/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1375252] Re: Hostname change is not preserved across reboot on Azure Ubuntu VMs
** Also affects: cloud-init (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: walinuxagent (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: walinuxagent (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: walinuxagent (Ubuntu Utopic) Importance: Undecided Status: New ** Changed in: walinuxagent (Ubuntu Trusty) Status: New => Invalid ** Changed in: walinuxagent (Ubuntu Utopic) Status: New => Invalid ** Changed in: walinuxagent (Ubuntu Vivid) Status: New => Invalid ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Utopic) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Vivid) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu) Assignee: (unassigned) => Ben Howard (utlemming) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1375252 Title: Hostname change is not preserved across reboot on Azure Ubuntu VMs Status in Init scripts for use on cloud images: Fix Committed Status in cloud-init package in Ubuntu: Fix Released Status in walinuxagent package in Ubuntu: Invalid Status in cloud-init source package in Trusty: New Status in walinuxagent source package in Trusty: Invalid Status in cloud-init source package in Utopic: New Status in walinuxagent source package in Utopic: Invalid Status in cloud-init source package in Vivid: New Status in walinuxagent source package in Vivid: Invalid Bug description: Whilst a hostname change is immediately effective using the hostname or hostnamectl commands, and changing the hostname this way is propagated to the hostname field in the Azure dashboard, upon rebooting the Ubuntu VM the hostname reverts to the Virtual Machine name as displayed in the Azure dashboard. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: walinuxagent 2.0.8-0ubuntu1~14.04.0 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 Date: Mon Sep 29 12:48:56 2014 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: walinuxagent UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.waagent.conf: 2014-09-29T09:37:10.758660 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1375252/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1375252] Re: [SRU] Hostname change is not preserved across reboot on Azure Ubuntu VMs
** Changed in: cloud-init Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1375252 Title: [SRU] Hostname change is not preserved across reboot on Azure Ubuntu VMs Status in Init scripts for use on cloud images: Fix Released Status in cloud-init package in Ubuntu: Fix Released Status in walinuxagent package in Ubuntu: Invalid Status in cloud-init source package in Trusty: Fix Released Status in walinuxagent source package in Trusty: Invalid Status in cloud-init source package in Utopic: Fix Released Status in walinuxagent source package in Utopic: Invalid Status in cloud-init source package in Vivid: Fix Released Status in walinuxagent source package in Vivid: Invalid Bug description: SRU Justification [IMPACT] Cloud-init overrides the hostname each boot with the fabric provided name. Users expect that the hostname will not be reset each boot. [Test Case 1] Upgrade from proposed 1. Install cloud-init from proposed 2. Change the hostname via /etc/hostname 3. Reboot 4. Confirm that the new hostname is used [Test Case 2] Reprovision (Follow Test Case 1) 1. Capture Azure VM 2. Start captured VM 3. Confirm that the new fabric name is used [Test Case 3] New Image Launch 1. Build an Azure image from -proposed 2. Boot and confirm that hostname is set properly 3. Follow test case 1 4. Follow test case 2 [Regression Potential] As this is a backport of the 15.10 Datasource, there is a medium regression potential. The 15.10 Datasource fixes a number of Azure provisioning bugs and is thus desirable. [ORIGINAL REPORT] Whilst a hostname change is immediately effective using the hostname or hostnamectl commands, and changing the hostname this way is propagated to the hostname field in the Azure dashboard, upon rebooting the Ubuntu VM the hostname reverts to the Virtual Machine name as displayed in the Azure dashboard. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: walinuxagent 2.0.8-0ubuntu1~14.04.0 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 Date: Mon Sep 29 12:48:56 2014 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: walinuxagent UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.waagent.conf: 2014-09-29T09:37:10.758660 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1375252/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1303986] Re: [FFe] CloudSigma Datasource doesn't handle vendor-data correctly
Attached patch showing that changes only affect the Cloud Sigma DS. ** Summary changed: - CloudSigma Datasource doesn't handle vendor-data correctly + [FFe] CloudSigma Datasource doesn't handle vendor-data correctly ** Changed in: cloud-init Assignee: (unassigned) => Ben Howard (utlemming) ** Description changed: - It appears as the CloudSigma datasource only has support for 'user- - data', and not 'vendor-data.' + Cloud Sigma has asked that we update the DataSource in Cloud-init to + support the 14.04 VendorData construct. The regression potential for + this change is low, as only the cloud-init Cloud-Sigma datasource is + changed, a test suite has been provided and it has been tested by Cloud + Sigma. + + [ORIGINAL BUG REPORT] + It appears as the CloudSigma datasource only has support for 'user-data', and not 'vendor-data.' ** Project changed: cloud-init => cloud-init (Ubuntu) ** Branch linked: lp:~utlemming/ubuntu/trusty/cloud-init/lp1303986 ** Patch added: "debdiff of 0.7.5-0ubuntu1 to 0.7.5-0ubuntu2" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1303986/+attachment/4081252/+files/debdiff.patch -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1303986 Title: [FFe] CloudSigma Datasource doesn't handle vendor-data correctly Status in “cloud-init” package in Ubuntu: New Bug description: Cloud Sigma has asked that we update the DataSource in Cloud-init to support the 14.04 VendorData construct. The regression potential for this change is low, as only the cloud-init Cloud-Sigma datasource is changed, a test suite has been provided and it has been tested by Cloud Sigma. [ORIGINAL BUG REPORT] It appears as the CloudSigma datasource only has support for 'user-data', and not 'vendor-data.' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1303986/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
