[Yahoo-eng-team] [Bug 1490796] Re: [SRU] cloud-init must check/format Azure ephemeral disks each boot
** 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/1490796 Title: [SRU] cloud-init must check/format Azure ephemeral disks each boot Status in cloud-init: 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 Trusty: Fix Released Status in cloud-init source package in Vivid: Fix Released 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 1464253] Re: [SRU] CloudStack data source will always set password to "HTTP/1.0 200 OK" on CloudStack 4.5.1 and later
** 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/1464253 Title: [SRU] CloudStack data source will always set password to "HTTP/1.0 200 OK" on CloudStack 4.5.1 and later Status in cloud-init: 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 Trusty: Fix Released Status in cloud-init source package in Utopic: Won't Fix Status in cloud-init source package in Vivid: Fix Released Status in cloud-init source package in Wily: Fix Released Bug description: First reported in https://bugs.launchpad.net/ubuntu/+source/cloud- init/+bug/1440263/comments/6 Older versions of CloudStack return the password as the first thing on the socket after an HTTP request (eschewing the tradition of HTTP response headers), which is what we take and use. This lack of proper HTTP headers has been fixed in ACS 4.5.1, which means we will always use the status line of the HTTP response as the password. [Impact] Ubuntu instances deployed on more recent versions of CloudStack will always set the root password to "HTTP/1.0 200 OK". [Test Case] Launch an instance in a recent CloudStack environment and try to log in using "HTTP/1.0 200 OK" and the password provided by the environment. The former should fail and the latter should work. [Regression Potential] This change moves to using wget rather than our own custom client, which is more inline with CloudStack's own scripting around this. We shouldn't regress on new or old CloudStack environments. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1464253/+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 1506187] Re: [SRU] Azure: cloud-init should use VM unique ID
** Also affects: cloud-init Importance: Undecided Status: New ** Changed in: cloud-init Status: New => In Progress ** Changed in: cloud-init Assignee: (unassigned) => Dan Watkins (daniel-thewatkins) ** Changed in: cloud-init (Ubuntu Xenial) Assignee: Dan Watkins (daniel-thewatkins) => (unassigned) -- 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/1506187 Title: [SRU] Azure: cloud-init should use VM unique ID Status in cloud-init: In Progress Status in cloud-init package in Ubuntu: Confirmed 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 Status in cloud-init source package in Wily: New Status in cloud-init source package in Xenial: Confirmed Bug description: The Azure datasource currently uses the InstanceID from the SharedConfig.xml file. On our new CRP stack, this ID is not guaranteed to be stable and could change if the VM is deallocated. If the InstanceID changes then cloud-init will attempt to reprovision the VM, which could result in temporary loss of access to the VM. Instead cloud-init should switch to use the VM Unique ID, which is guaranteed to be stable everywhere for the lifetime of the VM. The VM unique ID is explained here: https://azure.microsoft.com/en-us/blog /accessing-and-using-azure-vm-unique-id/ In short, the unique ID is available via DMI, and can be accessed with the command 'dmidecode | grep UUID' or even easier via sysfs in the file "/sys/devices/virtual/dmi/id/product_uuid". Steve To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1506187/+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 1470890] Re: [SRU] cc_apt_configure does not understand regions
** 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/1470890 Title: [SRU] cc_apt_configure does not understand regions Status in cloud-init: 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 Trusty: Fix Released Status in cloud-init source package in Vivid: Fix Released Bug description: [Impact] In GCE, we want to deploy Ubuntu mirrors per-region. At the moment, it is impossible to configure cloud-init to look for mirrors with the instance's region substituted in to the mirror DNS name. This will allow us to do so, which will allow us to improve the experience for Ubuntu users on GCE, both in terms of mirror responsiveness and bandwidth costs. [Test Case] On GCE, specify a primary mirror search URL of "http://%(region)s.gce.clouds.archive.ubuntu.com/ubuntu/" and run cloud-init. When running 'apt-get update', you should see a mirror URL which matches the above with the instance's region substituted in. [Regression Potential] There are two existing substitutions for mirror strings: availability_zone and ec2_region. We will need to ensure that each of these can still be used (testing specifically on EC2 for the latter). [Original Report] In _get_package_mirror_info (in cloudinit/distros/__init__.py), there is code that specifically handles converting EC2 availability zones to their corresponding regions. This won't work for other clouds that don't have the same form for availability zones (and even if they _do_, they'll have to be configured using strings containing 'ec2'; weird), which is problematic. This is particularly a problem for GCE. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1470890/+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 1470880] Re: [SRU] GCE datasource reports availability zones incorrectly
** 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/1470880
Title:
[SRU] GCE datasource reports availability zones incorrectly
Status in cloud-init:
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 Trusty:
Fix Released
Status in cloud-init source package in Vivid:
Fix Released
Bug description:
[Impact]
Availability zones and regions on GCE cannot be used for mirror substitution,
making in-cloud mirrors impossible.
[Test Case]
Run the following Python code on trusty and later:
from cloudinit.sources.DataSourceGCE import DataSourceGCE
ds = DataSourceGCE({}, None, None)
ds.get_data()
ds.availability_zone
Or the following code on precise:
from cloudinit.DataSourceGCE import DataSourceGCE
ds = DataSourceGCE({})
ds.get_data()
ds.get_availability_zone()
and confirm that the availability zone is returned (rather than a
relative URL).
[Regression Potential]
This is completely broken at the moment, so it can't get any more broken.
[Original Report]
After querying the cloud fabric, DataSourceGCE will return something along
the lines of "projects/969378662406/zones/europe-west1-d" as its
availability_zone.
This means that other parts of the code that expect a sensible value
for this (most notably the mirror discovery code), are broken on GCE.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1470880/+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 1490081] Re: install maas from lp:maas/stable will fail due to the lack of --force-yes
Hi Ray, I've closed this out, but please do reopen it if you can reproduce. Thanks, Dan ** Changed in: cloud-init Status: New => Invalid -- 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/1490081 Title: install maas from lp:maas/stable will fail due to the lack of --force- yes Status in cloud-init: Invalid Bug description: maas ppa changed from lp:maas-maintainers to lp:maas When changing this cloud-init.cfg, and install maas from cloud-init. I got this following errors. WARNING: The following packages cannot be authenticated! python-maas-client maas-cli maas-common maas-dhcp python-maas-provisioningserver maas-cluster-controller maas-proxy python-psycopg2 python-django-maas maas-region-controller-min maas-region-controller maas maas-dns E: There are problems and -y was used without --force-yes 2015-08-26 04:02:53,255 - util.py[WARNING]: Failed to install packages: ['maas', 'maas-dhcp', 'maas-dns', 'libvirt-bin', 'linux-image-extra-virtual', 'jq', 'juju-core', 'juju-deployer', 'python-bson', 'python-httplib2', 'python-jinja2', 'python-maas-client', 'python-yaml'] 2015-08-26 04:02:53,579 - cc_package_update_upgrade_install.py[WARNING]: 1 failed with exceptions, re-raising the last one 2015-08-26 04:02:53,585 - util.py[WARNING]: Running package-update-upgrade-install () failed Cloud-init v. 0.7.5 running 'modules:final' at Wed, 26 Aug 2015 04:02:53 +. Up 33.00 seconds. + sudo maas-region-admin createadmin --username=ubuntu --password=huawei@123 --email=ubuntu@localhost sudo: maas-region-admin: command not found 2015-08-26 04:02:53,910 - util.py[WARNING]: Failed running /var/lib/cloud/instance/scripts/config-maas.sh [1] 2015-08-26 04:02:53,912 - cc_scripts_user.py[WARNING]: Failed to run module scripts-user (scripts in /var/lib/cloud/instance/scripts) 2015-08-26 04:02:53,912 - util.py[WARNING]: Running scripts-user () failed MAAS controller is now configured. It might be useful to add additional options '--force-yes' to make sure maas packages can be installed To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1490081/+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
** Patch added: "precise.debdiff" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1490796/+attachment/4456140/+files/precise.debdiff ** Also affects: cloud-init Importance: Undecided Status: New ** Changed in: cloud-init Status: New => Fix Committed ** Changed in: cloud-init Assignee: (unassigned) => Dan Watkins (daniel-thewatkins) -- 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 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 1488896] [NEW] WALinuxAgentShim fails to handle colons in packed values in dhclient.eth0.leases
Public bug reported: We currently assume that a single colon in the unknown-245 dhclient key indicates we are dealing with hex; this is not necessarily true. If any part of the IP address is '58', then a colon will be included in the packed values. We should have more robust determination of if we're dealing with a hex string. ** Affects: cloud-init Importance: Undecided Assignee: Dan Watkins (daniel-thewatkins) Status: New ** Changed in: cloud-init Assignee: (unassigned) = Dan Watkins (daniel-thewatkins) -- 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/1488896 Title: WALinuxAgentShim fails to handle colons in packed values in dhclient.eth0.leases Status in cloud-init: New Bug description: We currently assume that a single colon in the unknown-245 dhclient key indicates we are dealing with hex; this is not necessarily true. If any part of the IP address is '58', then a colon will be included in the packed values. We should have more robust determination of if we're dealing with a hex string. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1488896/+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 1488891] [NEW] WALinuxAgentShim fails to handle escaped characters in dhclient.eth0.leases
Public bug reported: For example, a line of option unknown-245 dH\l; in dhclient.eth0.leases should yield an IP address of 100.72.34.108 but instead causes an exception: Traceback (most recent call last): File /usr/lib/python3/dist-packages/cloudinit/sources/DataSourceAzure.py, line 249, in get_data fabric_data = metadata_func() File /usr/lib/python3/dist-packages/cloudinit/sources/helpers/azure.py, line 289, in get_metadata_from_fabric shim = WALinuxAgentShim() File /usr/lib/python3/dist-packages/cloudinit/sources/helpers/azure.py, line 210, in __init__ self.endpoint = self.find_endpoint() File /usr/lib/python3/dist-packages/cloudinit/sources/helpers/azure.py, line 237, in find_endpoint endpoint_ip_address = socket.inet_ntoa(value) OSError: packed IP wrong length for inet_ntoa ** Affects: cloud-init Importance: Undecided Assignee: Dan Watkins (daniel-thewatkins) Status: New ** Changed in: cloud-init Assignee: (unassigned) = Dan Watkins (daniel-thewatkins) ** Summary changed: - WALinuxAgentShim fails to handle escaped characters + WALinuxAgentShim fails to handle escaped characters in dhclient.eth0.leases -- 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/1488891 Title: WALinuxAgentShim fails to handle escaped characters in dhclient.eth0.leases Status in cloud-init: New Bug description: For example, a line of option unknown-245 dH\l; in dhclient.eth0.leases should yield an IP address of 100.72.34.108 but instead causes an exception: Traceback (most recent call last): File /usr/lib/python3/dist-packages/cloudinit/sources/DataSourceAzure.py, line 249, in get_data fabric_data = metadata_func() File /usr/lib/python3/dist-packages/cloudinit/sources/helpers/azure.py, line 289, in get_metadata_from_fabric shim = WALinuxAgentShim() File /usr/lib/python3/dist-packages/cloudinit/sources/helpers/azure.py, line 210, in __init__ self.endpoint = self.find_endpoint() File /usr/lib/python3/dist-packages/cloudinit/sources/helpers/azure.py, line 237, in find_endpoint endpoint_ip_address = socket.inet_ntoa(value) OSError: packed IP wrong length for inet_ntoa To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1488891/+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 1475215] Re: [SRU] cloudinit.cs_utils.Cepko doesn't work under Python 3
** 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/1475215 Title: [SRU] cloudinit.cs_utils.Cepko doesn't work under Python 3 Status in cloud-init: Fix Released Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Vivid: Fix Released Bug description: In Python 3, Serial objects expect to be communicated with in bytes, we still try to pass strings in. [Impact] Versions of Ubuntu which have Python 3 as the default Python (15.04 onwards) won't successfully boot on CloudSigma. [Test Case] Try to boot a vivid (or wily) instance in CloudSigma, and observe your inability to SSH in to it. [Regression Potential] None; cloud-init is completely broken on CloudSigma at the moment. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1475215/+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: Azure data source should auto-detect ephemeral disk location
utopic is EOL. ** Changed in: cloud-init (Ubuntu Precise) Assignee: (unassigned) = Dan Watkins (daniel-thewatkins) ** Changed in: cloud-init (Ubuntu Precise) Status: New = In Progress ** Changed in: cloud-init (Ubuntu Utopic) Status: New = Invalid ** Changed in: cloud-init (Ubuntu Trusty) Status: New = In Progress ** Changed in: cloud-init (Ubuntu Trusty) Assignee: (unassigned) = Dan Watkins (daniel-thewatkins) ** Changed in: cloud-init (Ubuntu Vivid) Status: New = In Progress ** Changed in: cloud-init (Ubuntu Vivid) Assignee: (unassigned) = Dan Watkins (daniel-thewatkins) -- 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: Azure data source should auto-detect ephemeral disk location Status in cloud-init: In Progress 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: In Progress Status in walinuxagent source package in Precise: Fix Released Status in cloud-init source package in Trusty: In Progress 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: In Progress Status in walinuxagent source package in Vivid: Fix Released Bug description: 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 1456684] Re: [SRU] cloud-init does not know central (eu-central-1) is a direction for ec2 zones
** 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/1456684 Title: [SRU] cloud-init does not know central (eu-central-1) is a direction for ec2 zones Status in cloud-init: 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 Trusty: Fix Released Status in cloud-init source package in Vivid: Fix Released 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 1477944] [NEW] Azure data source should handle more than one ProvisioningSection
Public bug reported: Azure have informed us that they will be introducing a second format for metadata in ovf-env.xml, which will be done using multiple versioned ProvisioningSections. At the moment, cloud-init chokes if there is more than a single ProvisioningSection. We should, instead, be looking for the version 1.0 ProvisioningSection and ignoring all others. ** Affects: cloud-init Importance: Undecided Assignee: Dan Watkins (daniel-thewatkins) Status: New ** Changed in: cloud-init Assignee: (unassigned) = Dan Watkins (daniel-thewatkins) -- 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/1477944 Title: Azure data source should handle more than one ProvisioningSection Status in cloud-init: New Bug description: Azure have informed us that they will be introducing a second format for metadata in ovf-env.xml, which will be done using multiple versioned ProvisioningSections. At the moment, cloud-init chokes if there is more than a single ProvisioningSection. We should, instead, be looking for the version 1.0 ProvisioningSection and ignoring all others. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1477944/+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 1475215] Re: [SRU] cloudinit.cs_utils.Cepko doesn't work under Python 3
** Changed in: ubuntu 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/1475215 Title: [SRU] cloudinit.cs_utils.Cepko doesn't work under Python 3 Status in cloud-init: In Progress Status in Ubuntu: Fix Released Bug description: In Python 3, Serial objects expect to be communicated with in bytes, we still try to pass strings in. [Impact] Versions of Ubuntu which have Python 3 as the default Python (15.04 onwards) won't successfully boot on CloudSigma. [Test Case] Try to boot a vivid (or wily) instance in CloudSigma, and observe your inability to SSH in to it. [Regression Potential] None; cloud-init is completely broken on CloudSigma at the moment. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1475215/+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 1470890] Re: cc_apt_configure only understands EC2 availability zones
** Changed in: cloud-init Assignee: (unassigned) = Dan Watkins (daniel-thewatkins) ** Also affects: ubuntu 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/1470890 Title: cc_apt_configure only understands EC2 availability zones Status in cloud-init: Confirmed Status in Ubuntu: New Bug description: In _get_package_mirror_info (in cloudinit/distros/__init__.py), there is code that specifically handles converting EC2 availability zones to their corresponding regions. This won't work for other clouds that don't have the same form for availability zones (and even if they _do_, they'll have to be configured using strings containing 'ec2'; weird), which is problematic. This is particularly a problem for GCE. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1470890/+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 1475215] [NEW] cloudinit.cs_utils.Cepko doesn't work under Python 3
Public bug reported: In Python 3, Serial objects expect to be communicated with in bytes, we still try to pass strings in. ** Affects: cloud-init Importance: Undecided Assignee: Dan Watkins (daniel-thewatkins) Status: In Progress ** Affects: ubuntu Importance: Undecided Status: New ** Also affects: ubuntu Importance: Undecided Status: New ** Changed in: cloud-init Status: New = In Progress ** Changed in: cloud-init Assignee: (unassigned) = Dan Watkins (daniel-thewatkins) -- 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/1475215 Title: cloudinit.cs_utils.Cepko doesn't work under Python 3 Status in cloud-init: In Progress Status in Ubuntu: New Bug description: In Python 3, Serial objects expect to be communicated with in bytes, we still try to pass strings in. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1475215/+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: Azure data source should auto-detect ephemeral disk location
** Also affects: cloud-init Importance: Undecided Status: New ** Changed in: cloud-init Status: New = In Progress ** Changed in: cloud-init Assignee: (unassigned) = Dan Watkins (daniel-thewatkins) -- 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: Azure data source should auto-detect ephemeral disk location Status in Init scripts for use on cloud images: In Progress Status in cloud-init package in Ubuntu: New Status in walinuxagent package in Ubuntu: Fix Released Status in cloud-init source package in Precise: New Status in walinuxagent source package in Precise: Fix Released Status in cloud-init source package in Trusty: New Status in walinuxagent source package in Trusty: Fix Released Status in cloud-init source package in Utopic: New Status in walinuxagent source package in Utopic: Fix Released Status in cloud-init source package in Vivid: New Status in walinuxagent source package in Vivid: Fix Released Bug description: 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 1470890] [NEW] cc_apt_configure only understands EC2 availability zones
Public bug reported: In _get_package_mirror_info (in cloudinit/distros/__init__.py), there is code that specifically handles converting EC2 availability zones to their corresponding regions. This won't work for other clouds that don't have the same form for availability zones (and even if they _do_, they'll have to be configured using strings containing 'ec2'; weird), which is problematic. This is particularly a problem for GCE. ** 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/1470890 Title: cc_apt_configure only understands EC2 availability zones Status in Init scripts for use on cloud images: New Bug description: In _get_package_mirror_info (in cloudinit/distros/__init__.py), there is code that specifically handles converting EC2 availability zones to their corresponding regions. This won't work for other clouds that don't have the same form for availability zones (and even if they _do_, they'll have to be configured using strings containing 'ec2'; weird), which is problematic. This is particularly a problem for GCE. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1470890/+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 1470880] [NEW] GCE datasource reports availability zones incorrectly
Public bug reported: After querying the cloud fabric, DataSourceGCE will return something along the lines of projects/969378662406/zones/europe-west1-d as its availability_zone. This means that other parts of the code that expect a sensible value for this (most notably the mirror discovery code), are broken on GCE. ** 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/1470880 Title: GCE datasource reports availability zones incorrectly Status in Init scripts for use on cloud images: New Bug description: After querying the cloud fabric, DataSourceGCE will return something along the lines of projects/969378662406/zones/europe-west1-d as its availability_zone. This means that other parts of the code that expect a sensible value for this (most notably the mirror discovery code), are broken on GCE. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1470880/+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 1460715] [NEW] MBR disk setup fails in wily because sfdisk no longer accepts M as a valid unit
Public bug reported: Specifically, we get the following output in cc_disk_setup.exec_mkpart_mbr: sfdisk: --Linux option is unnecessary and deprecated sfdisk: unsupported unit 'M' and the manpage says: -u, --unit S Deprecated option. Only the sector unit is supported. So we'll need to shift to using sectors. ** 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/1460715 Title: MBR disk setup fails in wily because sfdisk no longer accepts M as a valid unit Status in Init scripts for use on cloud images: New Bug description: Specifically, we get the following output in cc_disk_setup.exec_mkpart_mbr: sfdisk: --Linux option is unnecessary and deprecated sfdisk: unsupported unit 'M' and the manpage says: -u, --unit S Deprecated option. Only the sector unit is supported. So we'll need to shift to using sectors. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1460715/+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 1437350] Re: Don't use exit status 0 when rejecting login as root
Won't fix in cloud-init because we don't want to break backwards compatibility. ** Changed in: cloud-init Status: In Progress = Invalid ** Changed in: cloud-init Status: Invalid = Opinion ** Changed in: cloud-init Status: Opinion = Invalid -- 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/1437350 Title: Don't use exit status 0 when rejecting login as root Status in CirrOS a tiny cloud guest: In Progress Status in Init scripts for use on cloud images: Invalid Bug description: $ ssh -i mykey root@10.1.0.2 ls Warning: Permanently added '10.1.0.2' (RSA) to the list of known hosts. Please login as 'cirros' user, not as root $ echo $? 0 Since the command is not executed the exit status should be non 0. /root/.ssh/authorized_keys: command=echo Please login as \'cirros\' user, not as root; echo; sleep 10 this part should be changed to: echo Please login as \'cirros\' user, not as root; echo; sleep 10; exit 1 To manage notifications about this bug go to: https://bugs.launchpad.net/cirros/+bug/1437350/+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 1451192] Re: Datasource discovery hangs on CloudStack for 2 minutes
Happy to have helped! ** Changed in: cloud-init Status: New = Invalid -- 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/1451192 Title: Datasource discovery hangs on CloudStack for 2 minutes Status in Init scripts for use on cloud images: Invalid Bug description: I'm trying to build a custom AWS AMI, so I configured the /etc/cloud/cloud.cfg in that way: datasource: Ec2: metadata_urls: - http://169.254.169.254 datasource_list: - Ec2 cloud-init still tries to get the metadata from all datasource modules, and CloudStack module runs for 2 minutes (because of timeouts), so it blocks the instance's OpenSSH startup. I don't really want other modules to be loaded, but failed to find a config example for disabling every datasource except EC2. Is there a correct way to do this? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1451192/+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 1403617] Re: gce datasource does not handle instance ssh keys
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Assignee: (unassigned) = Dan Watkins (daniel-thewatkins)
** Changed in: cloud-init (Ubuntu)
Assignee: Dan Watkins (daniel-thewatkins) = (unassigned)
** 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/1403617
Title:
gce datasource does not handle instance ssh keys
Status in Init scripts for use on cloud images:
Confirmed
Status in cloud-init package in Ubuntu:
Confirmed
Bug description:
The GCE Datasource pulls the per-project SSH but does not handle the
per-instance SSH keys.
The meta-data that it handles is:
url_map = [
('instance-id', 'instance/id', True),
('availability-zone', 'instance/zone', True),
('local-hostname', 'instance/hostname', True),
('public-keys', 'project/attributes/sshKeys', False),
('user-data', 'instance/attributes/user-data', False),
]
It should also handle:
('public-keys', 'instance/attributes/sshKeys', False),
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1403617/+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 Importance: Undecided Status: New ** Changed in: cloud-init Assignee: (unassigned) = Dan Watkins (daniel-thewatkins) ** Changed in: walinuxagent (Ubuntu) Status: In Progress = Invalid ** Changed in: cloud-init Status: New = In Progress ** Also affects: cloud-init (Ubuntu) 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/1375252 Title: Hostname change is not preserved across reboot on Azure Ubuntu VMs Status in Init scripts for use on cloud images: In Progress Status in cloud-init package in Ubuntu: New Status in walinuxagent package in Ubuntu: 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=set 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 1427687] Re: Reading of DMI data is broken
** 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/1427687 Title: Reading of DMI data is broken Status in Init scripts for use on cloud images: Fix Released Status in cloud-init package in Ubuntu: Fix Released Bug description: cloud-init currently assumes that the names of files in /sys/class/dmi/id/ will be the same as the arguments to dmidecode -s would be. This is not the case, so any data source that relies on DMI data is likely to be broken. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1427687/+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 1356855] Re: Cloud-init 0.7.5 Failed to get cloudstack user-data because of trailing slash
** Changed in: cloud-init Status: Fix Committed = Fix Released ** Changed in: cloud-init Assignee: (unassigned) = Dan Watkins (daniel-thewatkins) -- 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/1356855 Title: Cloud-init 0.7.5 Failed to get cloudstack user-data because of trailing slash 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 Trusty: Fix Released Status in cloud-init source package in Utopic: Fix Released Bug description: === Begin SRU Information === [Impact] CloudStack provides an EC2-style metadata server which cloud-init consumes. Unfortunately, the CloudStack metadata server does not exactly match the behaviour of the EC2 metadata server. When an instance using cloud-init is booted in a CloudStack environment, it will fail to retrieve metadata from the metadata server. This leads to cloud-init bailing out and making no changes to the instance, generally rendering it inaccessible and unusable. This patch changes all access to EC2-style metadata servers. Instead of accessing http://.../meta-data to determine the available metadata, cloud-init will access http://.../meta-data/ (i.e. with an added trailing slash). [Test Case] Booting an Ubuntu image configured to use the CloudStack data source within a CloudStack cloud environment. If (for example) the instance name is set correctly, then the fix has worked. [Regression Potential] Regression potential is low; this patch does affect more than just the CloudStack data source, but it is backported from the version of cloud-init in utopic which has been observed working. === End SRU Information === Hi, Cloud-init 0.7.5 fails to get cloudstack user-data because of trailing slash (ok in previous versions). As a temp workaround I use the following patch in url_helper.py line 239 (0.7.5-0ubuntu1): if e.response.status_code == 404: if url.endswith(/): url = url[:-1] req_args[url] = url else: url = url + / req_args[url] = url I don't know how other products (EC2, openstack co) deal with trailing slash Hope that helps Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1356855/+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 1436417] [NEW] Update cloud-init to use SmartOS v2 metadata format
Public bug reported: SmartDC has an updated meta-data format. Cloud-init is currently using the V1 format. The v2 format is safer and doesn't break when queried incorrectly. See joyent-mdata-tools package for information. ** Affects: cloud-init Importance: Undecided Assignee: Dan Watkins (daniel-thewatkins) Status: In Progress ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init Status: New = In Progress ** Changed in: cloud-init Assignee: (unassigned) = Dan Watkins (daniel-thewatkins) ** Also affects: ubuntu Importance: Undecided Status: New ** Package changed: ubuntu = cloud-init (Ubuntu) -- 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/1436417 Title: Update cloud-init to use SmartOS v2 metadata format Status in Init scripts for use on cloud images: In Progress Status in cloud-init package in Ubuntu: New Bug description: SmartDC has an updated meta-data format. Cloud-init is currently using the V1 format. The v2 format is safer and doesn't break when queried incorrectly. See joyent-mdata-tools package for information. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1436417/+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 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/1422388 Title: Fetch passwords from CloudStack virtual router 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 Trusty: Fix Released Status in cloud-init source package in Utopic: Fix Released Bug description: === Begin SRU Information === [Impact] Currently, the CloudStack data source will only handle SSH keys. While SSH keys are the preferred method for authenticating against cloud instances, there are some CloudStack deployments that do not yet support adding SSH keys to instances when creating instances via their web interface. Ubuntu images are unusable through the web interface for users of these CloudStack deployments. [Fix] The CloudStack data source has been extended to interface with CloudStack's password server in order to fetch passwords. These passwords are applied to the ubuntu user. [Test Case] Create an instance through a CloudStack web interface, which will give you a password. Confirm that this password can be used to log in to the ubuntu user. [Regression Potential] The changes are limited to the CloudStack data source so only CloudStack users will be affected. They are designed so that if they fail, they won't stop the CloudStack data source from functioning as it currently does. === End SRU Information === 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 1427687] [NEW] Reading of DMI data is broken
Public bug reported: cloud-init currently assumes that the names of files in /sys/class/dmi/id/ will be the same as the arguments to dmidecode -s would be. This is not the case, so any data source that relies on DMI data is likely to be broken ** Affects: cloud-init Importance: Undecided Assignee: Dan Watkins (daniel-thewatkins) Status: New ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Also affects: cloud-init Importance: Undecided Status: New ** Changed in: cloud-init Assignee: (unassigned) = Dan Watkins (daniel-thewatkins) -- 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/1427687 Title: Reading of DMI data is broken Status in Init scripts for use on cloud images: New Status in cloud-init package in Ubuntu: New Bug description: cloud-init currently assumes that the names of files in /sys/class/dmi/id/ will be the same as the arguments to dmidecode -s would be. This is not the case, so any data source that relies on DMI data is likely to be broken To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1427687/+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
