Public bug reported:
Description:
To support VM instances with >255 vCPUS, we need the patch set below
backported to the Azure 4.18 kernel. These patches include -
- New Hyper-V IOMMU driver. This driver will be Hyper-V specific.
- Minor update to the Hyper-V specific virtual PCI code. Need
Thanks All.
A newer Azure Agent which no longer touches cloud-init data is already
in the pipeline.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803173
Title:
cloud-init disables user on azure
** Tags removed: verification-needed-artful verification-needed-xenial
** Tags added: verification-done-artful verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743053
Title:
FYI, we are looking for this in the default Xenial kernel as well.
There are some bare metal systems in use that wouldn't be able to use
the Azure kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
The team has tested the kernel in comment #5 and confirmed that it
resolves the issue. Thanks!
BTW, we need this patch in Xenial as well since we are using the LTS.
Steve
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'll double check, but I don't think it's needed in linux-image-azure.
Do you have a link to the test kernel packages?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743053
Title:
libata: apply
No longs, this is an upstream fix from the vendor.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743053
Title:
libata: apply
Public bug reported:
Some SSD drives made by LiteOn can crash the kernel due to bad drivers.
A fix for this issue has been submitted upstream:
https://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git/commit/?h=for-4.15-fixes
LITEON EP1 has the same timeout issues as CX1 series devices.
Hi Joseph,
We've tested your previous Xenial test kernel from comment #5. Have
there been any changes that we need to test again, or can we test when
the kernel moves to proposed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Testing fails for me on Xenial - here are my steps:
1) Create a VM in Azure (any size)
2) Update cloud-init to the latest in xenial-proposed
3) Capture VM image
4) Provision a new VM using the following cloud-config:
#cloud-config
fs_setup:
- special:
cmd: mkfs -t %(filesystem)s -L
I tested Xenial as well and verified that the cloud-init package in
proposed resolves this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686514
Title:
Azure: cloud-init does not handle
Hi Scott,
Do you have a new bug number for the issue in comment #13?
Thanks,
Steve
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686514
Title:
Azure: cloud-init does not handle reformatting GPT
Hi Scott,
As an additional test case I've tried to use the steps as described here
to re-partition the ephemeral disk:
https://wiki.ubuntu.com/AzureSwapPartitions.
Using your branch from this bug the sult is that it appears to fail to
repartition but it does format/mount the disks. Here are my
Hi Scott,
The linked branch seems to reliably format the ephemeral disk on large
instances. However, after redeploying the VM I don't see the ephemeral
disk mounted after boot. The cloud-init log does not indicate any error,
and if I type 'mount -a' (or do a simple reboot) then the disk is
Test case from comment #3 passed using the -proposed kernel for Xenial
and Yakkey.
** Tags removed: verification-needed-xenial verification-needed-yakkety
** Tags added: verification-done-xenial verification-done-yakkety
--
You received this bug notification because you are a member of Ubuntu
GPT formatted ephemeral disks have two partitions (unfortunately). The
first is the Microsoft reserved partition
(https://en.wikipedia.org/wiki/Microsoft_Reserved_Partition). This
appears to be tripping up can_dev_be_reformatted().
Function address_ephemeral_resize() will first check if
Adding cloud-init logs. The logs show a number of boots (sorry), but
you should just be able to look at the first two boots to see the issue.
** Attachment added: "cloud-init-output.log"
** Attachment added: "cloud-init.log"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1686514/+attachment/4868359/+files/cloud-init.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Some Azure instances such as L32 or G5 have very large ephemeral disks
which are partitioned via GPT vs. smaller ephemeral disks that have dos
disklabels.
At first boot of an instance the ephemeral disk is prepared and
formatted properly. But if the instance is deallocated
** Tags removed: verification-needed-xenial verification-needed-yakkety
** Tags added: verification-done-xenial verification-done-yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669941
Title:
Hi,
The test looks good, here are my repro steps:
1) Create an Ubuntu 16.04 VM in Azure
2) Attach 128GB data disk
3) Partition and format the disk
# wipefs --all /dev/sdc
# sgdisk -Z /dev/sdc
# sgdisk -n '1:2048::264191' /dev/sdc
# mkfs.ext4 /dev/sdc1
Expected result: mkfs
Public bug reported:
Related bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657539
This issue was fixed in Zesty, but also impacts the Xenial and Yakkety
kernels. Can you please pull this patch back to Xenial+?
https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-
No logs needed. Thanks.
** Description changed:
There has been work upstream to enable encryption support for SMB3
- connections. This is particularly useful with the Azure Files feature as
- encryption is required to connected to an Azure Files storage share from
- on-prem or from a
Public bug reported:
There has been work upstream to enable encryption support for SMB3
connections. This is particularly useful with the Azure Files feature as
encryption is required to connected to an Azure Files storage share from
on-prem or from a different region.
The relevant commits are
Public bug reported:
When using Azure Files, a "Host is down" error can occur with the Linux
CIFS client when the client has been idle for an extended period of
time. Commit 4fcd1813e640 mostly resolved this issue and is already
integrated into the Xenial kernel.
The following additional patch
I've tested unscd with the patch and saw no issues, but unfortunately
there is no simple repro script that generates the failure. Customers
just see this issue appear after some time of running the service.
The customer in comment #3 also confirmed that unscd_0.52-1 fixes the
issue for them, and
Hi Scott,
Thanks for testing. I tested again (~10 times) with the latest Trusty
image and I wasn't able to reproduce the issue either. I'm not sure what
happened, if it's some timing issue or was just typo on my part :/ I
did not keep the repro VM around, unfortunately.
In that case I'm OK
This seems resolved in Xenial, but the issue also impacts Trusty. Will
this fix get backported?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642383
Title:
Unable to configure swap space on
Great news, thanks for the update! :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642383
Title:
Unable to configure swap space on ephemeral disk in Azure
To manage notifications about this bug
Hi Scott et al. Can we please raise the priority of this? It seems
there's no longer a way to create swap space on Ubuntu VMs on Azure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642383
Title:
Public bug reported:
I'm following the instructions to send cloud-config and repartition the
ephemeral disk in Azure: https://wiki.ubuntu.com/AzureSwapPartitions.
These instructions fail on Ubuntu 14.04 and 16.04 (did not test 12.04
yet).
Repro:
1) Add the following content to a file such as
Hi Scott,
I think we would actually like to move to a world where cloud-init can
function independently of the agent and does not start it. The
walinuxagent service can then start after cloud-init is finished, and
function as a guest agent to handle things like VM extensions, etc.
This behavior
Public bug reported:
When using user management tools such as usermod we see spurious
messages due to unscd, for example:
# usermod -a -G testgroup username
sent invalidate(passwd) request, exiting
sent invalidate(group) request, exiting
sent invalidate(passwd) request, exiting
sent
I also see these messages in cloud-init.log. The first set is for the
first provision, and the second is after the first reboot:
[CLOUDINIT] cc_mounts.py[DEBUG]: Attempting to determine the real name of
ephemeral0
[CLOUDINIT] cc_mounts.py[DEBUG]: Mapped metadata name ephemeral0 to
Public bug reported:
During provisioning cloud-init adds an entry for the ephemeral disk in
/etc/fstab. After provisioning this entry is correct and points to
"/dev/disk/azure/resource-part1". This symlink is created dynamically by
66-azure-storage.rules.
For some reason after the first reboot
Related bug: https://bugs.launchpad.net/ubuntu/+source/cloud-
init/+bug/1411582
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603222
Title:
Azure: incorrect entry in fstab for ephemeral disk
To
Public bug reported:
qemu >=2.2.1 had a bug when converting to VHD format, see
https://bugs.launchpad.net/qemu/+bug/1490611
As noted in that bug report, a fix for this issue has been released with QEMU
2.6:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=fb9245c2610932d33ce14
Is it possible to
Public bug reported:
The latest walinuxagent 2.0.16-0ubuntu2~12.04.0 package for Precise
included the postinst file from the Trusty package. The postinst script
configures dhclient.conf so that the DHCP client sends the system's
current hostname to the DHCP server. Unfortunately, the
Tested, respawn logic works now, thanks!
** Tags removed: verification-failed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1549789
Title:
[SRU]
Public bug reported:
Provisioning with a user password is supported on Azure, however it
seems the behavior of cloud-init is to not set the user password if the
user already exists. Ideally, if the user exists, then during
provisioning cloud-init will read the user password from the ovf-env.xml
Can you please take the patch to the upstart file as well from this commit:
https://github.com/Azure/WALinuxAgent/commit/c5c9f763b30f50597e239cbfbf7b0e01edc237a8
Version 2.0.16 has half of this commit already, but since the Ubuntu
packaging is different than what's in the repo it looks like we
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
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
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.
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
Bugs, which is subscribed to Ubuntu.
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
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
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551419
Title:
Fix UUID endianness patch breaks cloud-init on Azure
To manage
Public bug reported:
On Azure, cloud-init relies on the system-uuid as based by SMBIOS a
unique ID for a cloud instance. If this ID ever changes, then cloud-
init will attempt to reprovision the VM.
This recent kernel patch in the Ubuntu kernel corrects the endianness
for some SMBIOS fields,
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
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
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
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
** Tags removed: verification-needed-trusty verification-needed-vivid
** Tags added: verification-done-trusty verification-done-vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1498206
Title:
KY has pushed a patch to LKML that resolves this issue:
https://lkml.org/lkml/2015/11/18/690
This patch needs to be applied to the Vivid kernel and beyond. This is
a critical patch, can you please take this patch as sauce for now so we
can get it out as quickly as possible?
--
You received
HI Joseph,
Can we please raise the priority of this to get it into Trusty and Vivid
as soon as possible? We are seeing more repros of this issue on Azure.
Thanks,
Steve
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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:
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506187
Title:
Azure: cloud-init should
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
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
Public bug reported:
Description of problem:
Large sized VMs with 32 VCPUs and more than 100G memory sometimes hang at boot,
and the console keeps printing logs like "soft lockup - CPU#14 stuck for 23s!"
This particular issue can be resolved with the following patch upstream:
No logs required.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1498206
Title:
Fix CPU lockup on Hyper-V/Azure
To manage
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
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
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.
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1490796
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.
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.
Testing complete, no issues found. Thanks!
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
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
Bugs, which is subscribed to Ubuntu.
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.
Our team has tested the Vivid proposed kernel and found no regressions.
Performance is comparable to previous test kernels.
Thanks!
** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi Joseph,
Do you know will these patches will be available in the next kernel
maintenance release?
Thanks!
Steve
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel
@Joseph, I swear I thought I responded to this bug, sorry for the delay.
We have finished testing the Trusty kernel you posted at
http://kernel.ubuntu.com/~jsalisbury/lp1445195/trusty, and confirmed
performance is better.
Thanks!
Steve
--
You received this bug notification because you are a
We tested the Utopic kernel and it works fine now. No crashes or issues
and performance is better.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195
Title:
[Hyper-V] Kernel patches
We'll test this new kernel. It appears the directory
/~jsalisbury/lp1445195/utopic is empty, but it looks like the kernel
was placed in the /~jsalisbury/lp1445195 directory instead. I assume
this is the correct kernel, but to be safe can you confirm?
Thanks!
Steve
--
You received this bug
Both these test kernels for Trusty and Utopic worked as well.
Thanks,
Steve
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1463584
Title:
[Hyper-V] Add support for VMBus panic notifier handler
To
The test team has tested the Vivid kernel and confirmed that it works as
expected. So let's please ack these patches for the next Vivid kernel.
The Utopic kernel provided crashes at boot time, so we're unable to test
that. Can you help us debug that issue?
--
You received this bug
No logs required.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1463584
Title:
Add support for VMBus panic notifier handler
To
Test case on Hyper-V:
- Run: echo c /proc/sysrq-trigger
- If the Panic Notifier code is present, an event 18590 should be logged.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1463584
Title:
Public bug reported:
Please take these patches to our Hyper-V VMBus driver to enable kernel
crash notification:
Drivers: hv: vmbus: Add support for VMBus panic notifier handler
Hi,
OK, sorry for the delay and misunderstanding. I tested linux-
image-3.2.0-80-generic from precise-proposed and confirmed that it also
has the patch and the issue is resolved.
Thanks again,
Steve
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi,
I confirmed the fix in comment #4. Is there something I should click on
here to validate the fix?
Thanks,
Steve
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1417313
Title:
[Hyper-V] vmbus:
Hi Joseph,
We've tested this kernel and no longer see this issue. I think we are
OK to proceed.
Thanks!
Steve
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1417313
Title:
[Hyper-V] vmbus:
Thanks for this, we will take this kernel and test. The issue is
intermittent and would likely only show up during stress tests, so it
may take a few days for results.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
This issue impacts Ubuntu 12.04.
Whenever a device is unregistered in vmbus_device_unregister
(drivers/hv/vmbus_drv.c), the device name in the log message may contain
garbage as the memory has already been freed by the time pr_info is
called. Log example:
[ 3149.170475]
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:
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:
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
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
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
+1 :)
The [ sdb, mount point ] 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
+1 :)
The [ sdb, mount point ] 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
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
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
Public bug reported:
Please take these upstream patches for the Hyper-V VMBus driver. In
some cases we are seeing crashes due to these bugs on Hyper-V and Azure.
commit 72c6b71c245dac8f371167d97ef471b367d0b66b
Author: K. Y. Srinivasan k...@microsoft.com
Date: Wed Aug 27 16:25:34 2014 -0700
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!
Ah, sorry for the delay. I tested this package with the repro steps
mentioned above and can confirm that this issue is resolved with the
-proposed package.
Thanks!
Steve
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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!
1 - 100 of 147 matches
Mail list logo
