Public bug reported:
The Azure datasource on Trusty utilizes the system-uuid from SMBIOS as a
unique VM ID to identify the instance. Precise still uses the older
method of obtaining the Instance ID via the wire server, which is not
stable in CRP. Precise should move to use the same instance ID
d
It seems the Utopic kernel is impacted as well, I tested
3.16.0-62-generic released on 2/27. I thought that kernel was EOL. Can
we revert the fix here as well?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
http
Hi Dan,
This issue does not repro with the latest Wily kernel, but it should,
right? Can you help me understand why?
This is just testing on Hyper-V:
# uname -r
4.2.0-30-generic
# cat /sys/class/dmi/id/product_uuid && dmidecode -s system-uuid
EF6EED16-EAD5-BC4C-AD75-550370C212EE
Public bug reported:
Hi Ben,
On the latest Trusty package it appears that the upstart file
"ephemeral-disk-warning.conf" still contains and older version of this
script that detects the ephemeral disk by grepping for "sdb1". It
should instead run ephemeral-disk-warning.sh like what the systemd
s
I tested cloud-init 0.7.5-0ubuntu1.15 from -proposed for Trusty on Azure
and confirmed that the new package resolves the issue.
The upgrade path is also working as expected. I first created an Ubuntu
14.04 VM using ARM. After shutting down the VM via the Azure portal
(portal.azure.com) and then
Yes, this is supported in all prod environments. You can remove the
dependency on InstanceID.
Thanks!
Steve
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1506187
Title:
Azure:
Public bug reported:
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 coul
Public bug reported:
Tested with latest Ubuntu 14.04 image on Azure (20150908).
In Azure, the DHCP client on Ubuntu VMs is configured to push the
current hostname to the DHCP server, which then publishes the hostname
into Azure DNS. However, after changing the hostname and rebooting, the
old hos
Tested cloud-init/0.7.5-0ubuntu1.10 and it resolves the issue for me.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.ne
Public bug reported:
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.
Ben, is it possible to SRU this fix back to Precise as well? At least
on Azure we still have plenty of folks that use and love this version.
Thanks,
Steve
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://b
Hi Daniel,
Thanks for doing this, looks great so far! I do have a couple
recommendations:
In case customers are not familiar with the term "Custom Data" or how to use
it, I would recommend linking to our documentation:
http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-how
That's what I meant, on Ubuntu images the ResourceDisk.Format should be
"n" because cloud-init handles this. We do not want the Linux agent and
cloud-init fighting over formatting or reformatting, and then mounting
the resource disk.
You're right, perhaps these parameters should not exist in the
This looks like the correct problem statement - the SCSI layer schedules
these tasks and so subtle timings could cause disk names to change.
This is also we recommend UUIDs or labels or similar to be used in
fstab.
The logic for DeviceForIdePort() is based on the fact that our vmbus
driver at leas
+1 :)
The [ sdb, ] syntax is a bug as well. 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 a
No, the mount location cannot be modified on Ubuntu via the
waagent.conf, that is the issue. I would like a way to modify the mount
point post-provisioning.
The only way to change the mount point on Azure is to use CustomData
(like "user data" on other clouds) to send a cloud-config to modify the
We tested this package using the [TEST] steps above and can confirm that
the readme is created as expected. As an additional step I also resized
the VM to ensure that the temporary disk would need to be reformatted,
and saw in this case that the readme was also created as expected. Well
done!
--
Public bug reported:
When the Azure Linux agent handles the resource disk it adds a file on
the newly formatted partition called "DATALOSS_WARNING_README.txt". The
purpose of this file is to warn customers that the disk is temporary and
may be wiped if the VM is rebooted or moved to another host.
** Summary changed:
- Document ow to add swap space on Azure resource disk
+ Document how to add swap space on Azure resource disk
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/13
Public bug reported:
The process for creating a swap partition on Ubuntu VMs on Azure is not
well understood or documented. Most of the documentation on Azure
generally refers to using the walinuxagent to manage the swap space on
the resource disk (ephemeral disk). However, Ubuntu VMs use cloud-
Public bug reported:
Users would like to use a local cloud-config to modify how the
resource/ephemeral disk is partitioned and where it is mounted on Azure
VMs. Currently it seems this is only customizable via a configuration
sent via CustomData (user data).
If I understand correctly, the Azure
Hello,
Our Linux agent team found a bug while testing a VM extension and has
tagged a new release, v2.0.8. Please package this version instead.
The relevant change in v2.0.8 is the following and should be applied to all:
https://github.com/Azure/WALinuxAgent/commit/cbcd69b70876dbcc3db2a9b8c041b1
We have run our network, VNET, BVT and E2E tests using the walinuxagent
2.0.5 package for Ubuntu 12.04 and found no issues.
Cloud Test Update:
* Network Tests : Completed.
[41 PASS, 1 XFAIL]
Expected Failed Tests :
1. NETWORK-IDNS-SINGLEHS-CHANGED-HOSTNAME
Reason : After c
Public bug reported:
This is a request from Microsoft to please update the walinuxagent
package for Ubuntu 12.04 from v1.3.2 to the latest WALinuxAgent 2.0.5.
The Microsoft team has implemented new features and bugfixes into the
2.0 branch that will not be backported to the 1.x branch. The most
Public bug reported:
Microsoft has released version 2.0.5 of the Azure Linux agent. This
agent has many bugfixes, including important fixes for the extension
handler feature. Please update the current walinuxagent package (based
on v2.0.4) with the latest 2.0.5.
That tag/download for WALinuxAge
Hi Ben,
Is it necessary to revert the patch to /usr/sbin/waagent itself rather
than just the packaging? The original issue was about users calling
'waagent -deprovision', so my concern is that this issue might pop up
again if we revert that patch.
As far as I can tell the fix to waagent is worki
Public bug reported:
After installing the latest walinuxagent package on Ubuntu 13.10 I see
that we end up with a broken configuration in /etc/ssh/sshd_config. The
last line in that file looks like the following:
UsePAM yesClientAliveInterval 180
This is the result of the agent package re-ru
Public bug reported:
This is a formal request to please update the Windows Azure Linux Agent
to version 2.0.4 (tag here:
https://github.com/Azure/WALinuxAgent/releases). We have added an
important capability in 2.0.4 called 'agent injection' that will allow
customers to install new extensions/han
Hi Scott,
I'm not able to repro this using the current dev branch of the CLI tools
and the latest CustomData patches. Can you take a look at the latest
CustomData patches at the pull requests below. They are mostly similar
to yours and should port easily into the version of the xplat tools and
S
It looks like the image dated 20130827 also appears to have this issue.
Should this one be removed as well?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1224684
Title:
[SRU] ca
Public bug reported:
Hello,
The Github repo for Windows Azure Linux Agent has moved to the official
Windows Azure organization on Github. Please update your upstream
sources:
Old repo: https://github.com/Windows-Azure/WALinuxAgent
New repo: https://github.com/WindowsAzure/WALinuxAgent
We use
Hello!
Thank you for confirming that. I think the hostname just looked odd so
just wanted to confirm as we don't have access to this environment.
If the instance is still available we really need more logs to figure
out what went wrong. This will help determine if there's something
wrong on the
Aside from the kernel logs, please also include /var/log/syslog and any other
relevant logs. Long, I believe the contents of /var/lib/waagent were posted
here:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1195524/+attachment/3717115/+files/waagent-info.tar
There is retry logic in
Hi Scott,
Thank you for looking at this. The mount point for the resource disk is
configurable via /etc/waagent.conf (see the "ResourceDisk.MountPoint"
parameter). The default is /mnt/resource, but this could be changed to
another location if desired.
Thanks,
Steve
--
You received this bug no
Hi!
Thank you for looking at this. This issue was fixed upstream a little
while ago, it just needs to make it into the next Ubuntu package update.
Thanks!
Steve
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to walinuxagent in Ubuntu.
Hi Ben,
The MAC prefix for Hyper-V/Azure is "00:15:5D" (see also
http://standards.ieee.org/develop/regauth/oui/oui.txt)
Thanks,
Steve
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to walinuxagent in Ubuntu.
https://bugs.launchpad.net/b
Hello!
As Robie speculated, editing the ClientAliveInterval parameter will help
keep the session open through the load balancer which would otherwise
drop the connection. There has to be some network traffic originating
from either the client or server to keep it open. Possibly your client
sends
37 matches
Mail list logo
