[Bug 1826447] [NEW] Azure: Backport vIOMMU driver (increase vCPU limits)

[Stephen A. Zarkos]

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 to expand the 
size of an array to allow for a larger number of vCPUs.

There are very large VM instance sizes coming to Azure in 2019, and
Ubuntu will require the following patches in order to function properly:

https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
next.git/commit/?id=29217a4746835fef35279abbd12c1a1efe83bfca

https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
next.git/commit/?id=84fdfafab849036b5aefa52824b5cb42e887ef0e

https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
next.git/commit/?id=c8ccf7599ddac5fa48e06104c44b24709e21eed5

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/controller
/pci-hyperv.c?id=9bc1174280ddf7693e8c29a8f1743809e987ac37

** Affects: linux-azure (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826447

Title:
   Azure: Backport vIOMMU driver (increase vCPU limits)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1826447/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1803173] Re: cloud-init disables user on azure at second reboot

[Stephen A. Zarkos]

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 at second reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1803173/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1743053] Re: libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

[Stephen A. Zarkos]

** 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:
  libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743053/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1743053] Re: libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

[Stephen A. Zarkos]

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.
https://bugs.launchpad.net/bugs/1743053

Title:
  libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743053/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1743053] Re: libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

[Stephen A. Zarkos]

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.
https://bugs.launchpad.net/bugs/1743053

Title:
  libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743053/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1743053] Re: libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

[Stephen A. Zarkos]

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 MAX_SEC_1024 to all LITEON EP1 series devices

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743053/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1743053] Re: libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

[Stephen A. Zarkos]

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 MAX_SEC_1024 to all LITEON EP1 series devices

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743053/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1743053] [NEW] libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

[Stephen A. Zarkos]

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.

Revert max_sectors to the value of 1024.

'e0edc8c54646 ("libata: apply MAX_SEC_1024 to all CX1-JB*-HP devices")'

Signed-off-by: Xinyu Lin 
Signed-off-by: Tejun Heo 
Cc: sta...@vger.kernel.org


At a high level the root cause of this problem is that the device only supports 
commands with a transfer size up to 512KB.  This worked fine with older 
versions of Linux but newer versions are attempting commands with a transfer 
size of 1280KB which is problematic for this device (LITEON EP1-KB480)

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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 MAX_SEC_1024 to all LITEON EP1 series devices

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743053/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1670508] Re: CIFS: Enable encryption for SMB3

[Stephen A. Zarkos]

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.
https://bugs.launchpad.net/bugs/1670508

Title:
  CIFS: Enable encryption for SMB3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670508/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1687712] Re: cc_disk_setup: fs_setup with cmd doesn't work

[Stephen A. Zarkos]

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 %(label)s %(device)s
   filesystem: ext4
   device: /dev/sdb1
   label: repro

I see the following logs in cloud-init.log:

2017-06-22 17:18:49,995 - cc_disk_setup.py[DEBUG]: setting up filesystems: 
[{'cmd': 'mkfs -t %(filesystem)s -L %(label)s %(device)s', 'filesystem': 
'ext4', 'special': None, 'device': '/dev/sdb1', 'label': 'repro'}]
2017-06-22 17:18:49,995 - cc_disk_setup.py[DEBUG]: Creating new filesystem.
2017-06-22 17:18:49,996 - util.py[DEBUG]: Running command ['udevadm', 'settle'] 
with allowed return codes [0] (shell=False, capture=True)
2017-06-22 17:18:50,279 - cc_disk_setup.py[DEBUG]: Checking /dev/sdb1 against 
default devices
2017-06-22 17:18:50,279 - cc_disk_setup.py[DEBUG]: Identifying device to create 
repro filesytem on
2017-06-22 17:18:50,280 - util.py[DEBUG]: Running command ['/bin/lsblk', 
'--pairs', '--output', 'NAME,TYPE,FSTYPE,LABEL', '/dev/sdb1'] with allowed 
return codes [0] (shell=False, capture=True)
2017-06-22 17:18:50,299 - cc_disk_setup.py[WARNING]: Failed to find device 
during available device search.
2017-06-22 17:18:50,308 - cc_disk_setup.py[DEBUG]: Automatic device for 
/dev/sdb1 identified as None
2017-06-22 17:18:50,308 - cc_disk_setup.py[DEBUG]: No device aviable that 
matches request. Skipping fs creation for {'cmd': 'mkfs -t %(filesystem)s -L 
%(label)s %(device)s', 'filesystem': 'ext4', 'special': None, 'device': 
'/dev/sdb1', 'label': 'repro'}
2017-06-22 17:18:50,308 - util.py[DEBUG]: Creating fs for /dev/sdb1 took 0.313 
seconds
2017-06-22 17:18:50,309 - handlers.py[DEBUG]: finish: 
init-network/config-disk_setup: SUCCESS: config-disk_setup ran successfully

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687712

Title:
  cc_disk_setup: fs_setup with cmd doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1687712/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1686514] Re: Azure: cloud-init does not handle reformatting GPT partition ephemeral disks

[Stephen A. Zarkos]

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 reformatting GPT partition ephemeral
  disks

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1686514/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1686514] Re: Azure: cloud-init does not handle reformatting GPT partition ephemeral disks

[Stephen A. Zarkos]

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 partition ephemeral
  disks

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1686514/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1686514] Re: Azure: cloud-init does not handle reformatting GPT partition ephemeral disks

[Stephen A. Zarkos]

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 repro steps

 $ azure group create ubtest 'east us'

 $ azure vm create ubtest ubtest-1604 Linux --image-urn
canonical:UbuntuServer:16.04-LTS:latest --admin-username azureuser
--admin-password '' --nic-name ubtest-1604 --location "East
US" --vnet-name "ubtest" --vnet-address-prefix "10.0.0.0/24" --vnet-
subnet-name "ubtest" --vnet-subnet-address-prefix "10.0.0.0/24"
--public-ip-name "ubtest" --public-ip-domain-name "ubtest" --custom-data
./customdata.txt -z 'Standard_L32s'

The customdata.txt file contains something like the following:

 #cloud-config
 disk_setup:
 ephemeral0:
 table_type: gpt
 layout: [66, [33, 82]]
 overwrite: True
 fs_setup:
 - device: ephemeral0.1
   filesystem: ext4
 - device: ephemeral0.2
   filesystem: swap
 mounts:
 - ["ephemeral0.1", "/mnt"]
 - ["ephemeral0.2", "none", "swap", "sw", "0", "0"]

.
.
Result with default 16.04 image: /mnt is not mounted and we see a failure in 
the cloud-init.log (attached).

Results with branch from this bug: /mnt and swap space are created, but
the partition layout is not applied. So part1 is still type "Microsoft
reserved" and only 120MB, and part2 is type "Microsoft basic data" and
is a 5.5TB swap partition :)

Maybe there's something wrong with my cloud-config?  Do I need to use a
different layout format when table_type is 'gpt'?


** Attachment added: "cloud-init.log"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1686514/+attachment/4878669/+files/cloud-init.log

-- 
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 partition ephemeral
  disks

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1686514/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1686514] Re: Azure: cloud-init does not handle reformatting GPT partition ephemeral disks

[Stephen A. Zarkos]

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
mounted properly with an ext4 filesystem.

To test this I'm creating an L32s VM on Azure with Ubuntu 16.04,
updating cloud-init manually from your git branch, and then I click the
'redeploy' option via the portal.  I see that the ephemeral disk is
partitioned/formatted correctly, but just not mounted.  Am I missing
some configuration?  What is normally responsible for mounting the
ephemeral disk once it is formatted?

Steve

** Attachment added: "cloud-init.log"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1686514/+attachment/4877814/+files/cloud-init.log

-- 
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 partition ephemeral
  disks

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1686514/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1682215] Re: [Hyper-V] mkfs regression in kernel 4.4+

[Stephen A. Zarkos]

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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682215

Title:
  [Hyper-V] mkfs regression in kernel 4.4+

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682215/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1686514] Re: Azure: cloud-init does not handle reformatting GPT partition ephemeral disks

[Stephen A. Zarkos]

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
is_new_instance=True, and if so it will happily format the ephemeral
disk.  That's why this works at first boot.

For subsequent boots where is_new_instance=False,
address_ephemeral_resize() will call can_dev_be_reformatted(). This
function sees that the ephemeral disk has two partitions and returns
false:

if os.path.exists(devpath + suff + "2"):
msg = ('device %s had more than 1 partition: %s, %s' %
   devpath, cand, devpath + suff + "2")
return False, msg

We also end up with the following TypeError in the logs:

 Traceback (most recent call last):
   File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 647, in 
status_wrapper
 ret = functor(name, args)
   File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 415, in 
main_init
 init.activate_datasource()
   File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 369, in 
activate_datasource
 is_new_instance=self.is_new_instance())
   File "/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceAzure.py", 
line 251, in activate
 address_ephemeral_resize(is_new_instance=is_new_instance)
   File "/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceAzure.py", 
line 329, in address_ephemeral_resize
 result, msg = can_dev_be_reformatted(devpath)
   File "/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceAzure.py", 
line 279, in can_dev_be_reformatted
 devpath, cand, devpath + suff + "2")
 TypeError: not enough arguments for format string
.
.
Aside from the TypeError, even if we comment this part there is a later check 
to ensure that this partition is NTFS formatted (which it isn't). This will 
also return false and you will see the following error in the logs:

 "reformattable=False: partition 1 (/dev/disk/cloud/azure_resource-part1
-> /dev/sdb1) on device /dev/disk/cloud/azure_resource was not ntfs
formatted"

I think the correct behavior should be for cloud-init to detect that
this is a GPT formatted ephemeral disk, or check that azure_resource-
part1 is a "Microsoft reserved partition".  And if so skip
azure_resource-part1 and focus on azure_resource-part2 instead to
determine if it is safe to reformat.

-- 
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 partition ephemeral
  disks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1686514/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1686514] Re: Azure: cloud-init does not handle reformatting GPT partition ephemeral disks

[Stephen A. Zarkos]

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"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1686514/+attachment/4868360/+files/cloud-init-output.log

-- 
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 partition ephemeral
  disks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1686514/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1686514] Re: Azure: cloud-init does not handle reformatting GPT partition ephemeral disks

[Stephen A. Zarkos]

** 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.
https://bugs.launchpad.net/bugs/1686514

Title:
  Azure: cloud-init does not handle reformatting GPT partition ephemeral
  disks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1686514/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1686514] [NEW] Azure: cloud-init does not handle reformatting GPT partition ephemeral disks

[Stephen A. Zarkos]

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 and then
reallocated (thus receiving a new ephemeral disk) then cloud-init does
not handle reformatting GPT partition ephemeral disks properly.
Therefore /mnt is never mounted again.

Test cases:
 1. Deploy an L32(s) VM on Azure
 2. Log in and ensure that the ephemeral disk is formatted and mounted to /mnt
 3. Via the portal you can "Redeploy" the VM to a new Azure Host (or 
alternatively stop and deallocate the VM for some time, and then 
restart/reallocate the VM).

Expected Results:
 - After reallocation we expect the ephemeral disk to be formatted and mounted 
to /mnt.

Actual Results:
 - After reallocation /mnt is not mounted and there are errors in the 
cloud-init log.

*This was tested on Ubuntu 16.04 - but may affect other releases.

Note: This bug a regression from previous cloud-init releases. GPT
support for Azure ephemeral disk handling was added to cloud-init via
this bug: https://bugs.launchpad.net/ubuntu/+source/cloud-
init/+bug/1422919.

** Affects: cloud-init (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  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 and then
  reallocated (thus receiving a new ephemeral disk) then cloud-init does
  not handle reformatting GPT partition ephemeral disks properly.
  Therefore /mnt is never mounted again.
  
  Test cases:
-  1. Deploy an L32(s) VM on Azure
-  2. Log in and ensure that the ephemeral disk is formatted and mounted to /mnt
-  3. Via the portal you can "Redeploy" the VM to a new Azure Host (or 
alternatively stop and deallocate the VM for some time, and then 
restart/reallocate the VM).
+  1. Deploy an L32(s) VM on Azure
+  2. Log in and ensure that the ephemeral disk is formatted and mounted to /mnt
+  3. Via the portal you can "Redeploy" the VM to a new Azure Host (or 
alternatively stop and deallocate the VM for some time, and then 
restart/reallocate the VM).
  
  Expected Results:
-  - After reallocation we expect the ephemeral disk to be formatted and 
mounted to /mnt.
+  - After reallocation we expect the ephemeral disk to be formatted and 
mounted to /mnt.
  
  Actual Results:
-  - After reallocation /mnt is not mounted and there are errors in the 
cloud-init log.
+  - After reallocation /mnt is not mounted and there are errors in the 
cloud-init log.
  
+ *This was tested on Ubuntu 16.04 - but may affect other releases.
  
- Note: This bug a regression from previous cloud-init releases. GPT support 
for Azure ephemeral disk handling was added to cloud-init via this bug: 
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1422919.
+ Note: This bug a regression from previous cloud-init releases. GPT
+ support for Azure ephemeral disk handling was added to cloud-init via
+ this bug: https://bugs.launchpad.net/ubuntu/+source/cloud-
+ init/+bug/1422919.

-- 
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 partition ephemeral
  disks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1686514/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1669941] Re: CIFS: Call echo service immediately after socket reconnect

[Stephen A. Zarkos]

** 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:
  CIFS: Call echo service immediately after socket reconnect

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1669941/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1682215] Re: [Hyper-V] mkfs regression in kernel 4.4+

[Stephen A. Zarkos]

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 should return very quickly because
lazy_itable_init is enabled.

Actual test results:

  - Kernel 4.4.0-71.92: mkfs blocks and formatting takes about
8-minutes.

  - Kernel 4.4.0-73.94~lp1682215: mkfs returns immediately.


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/1682215

Title:
  [Hyper-V] mkfs regression in kernel 4.4+

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682215/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1682215] [NEW] [Hyper-V] mkfs regression in kernel 4.4+

[Stephen A. Zarkos]

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-
block.git/commit/?h=for-4.11/block=729204ef49ec00b788ce23deb9eb922a5769f55d

author
Ming Lei 
2016-12-17 10:49:09 (GMT)
committer
Jens Axboe 
2017-01-12 03:47:08 (GMT)
commit
729204ef49ec00b788ce23deb9eb922a5769f55d (patch)
tree
ab5cc3c0aa17fa8b988ed7dfefe888000fac0be3
parent
1661f2e21c8bbf922dcb76faf2126a33ffe4cddb (diff)
block: relax check on sg gap
If the last bvec of the 1st bio and the 1st bvec of the next
bio are physically contigious, and the latter can be merged
to last segment of the 1st bio, we should think they don't
violate sg gap(or virt boundary) limit.

Both Vitaly and Dexuan reported lots of unmergeable small bios
are observed when running mkfs on Hyper-V virtual storage, and
performance becomes quite low. This patch fixes that performance
issue.

The same issue should exist on NVMe, since it sets virt boundary too.

Reported-by: Vitaly Kuznetsov 
Reported-by: Dexuan Cui 
Tested-by: Dexuan Cui 
Cc: Keith Busch 
Signed-off-by: Ming Lei 
Signed-off-by: Jens Axboe 

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682215

Title:
  [Hyper-V] mkfs regression in kernel 4.4+

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682215/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1670508] Re: CIFS: Enable encryption for SMB3

[Stephen A. Zarkos]

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 different region.
+ connections. This is a particularly valuable (and commonly requested)
+ feature with the Azure Files service as encryption is required to
+ connect to an Azure Files storage share from on-prem or from a different
+ Azure region.
  
  The relevant commits are as follows:
  
  CIFS: Fix possible use after free in demultiplex thread
  Commit 61cfac6f267dabcf2740a7ec8a0295833b28b5f5
  
- CIFS: Allow to switch on encryption with seal mount option 
+ CIFS: Allow to switch on encryption with seal mount option
  Commit ae6f8dd4d0c87bfb72da9d9b56342adf53e69c31
  
  CIFS: Add capability to decrypt big read responses
  Commit c42a6abe3012832a68a371dabe17c2ced97e62ad
  
  CIFS: Decrypt and process small encrypted packets
  Commit 4326ed2f6a16ae9d33e4209b540dc9a371aba840
  
  CIFS: Add copy into pages callback for a read operation
  Commit d70b9104b1ca586f73aaf59426756cec3325a40e
  
  CIFS: Add mid handle callback
  Commit 9b7c18a2d4b798963ea80f6769701dcc4c24b55e
  
  CIFS: Add transform header handling callbacks
  Commit 9bb17e0916a03ab901fb684e874d77a1e96b3d1e
  
  CIFS: Encrypt SMB3 requests before sending
  Commit 026e93dc0a3eefb0be060bcb9ecd8d7a7fd5c398
  
  CIFS: Enable encryption during session setup phase
  Commit cabfb3680f78981d26c078a26e5c748531257ebb
  
  CIFS: Add capability to transform requests before sending
  Commit 7fb8986e7449d0a5cebd84d059927afa423fbf85
  
  CIFS: Separate RFC1001 length processing for SMB2 read
  Commit b8f57ee8aad414a3122bff72d7968a94baacb9b6
  
  CIFS: Separate SMB2 sync header processing
  Commit cb200bd6264a80c04e09e8635fa4f3901cabdaef
  
  CIFS: Send RFC1001 length in a separate iov
  Commit 738f9de5cdb9175c19d24cfdf90b4543fc3b47bf
  
  CIFS: Make send_cancel take rqst as argument
  Commit fb2036d817584df42504910fe104f68517e8990e
  
  CIFS: Make SendReceive2() takes resp iov
  Commit da502f7df03d2d0b416775f92ae022f3f82bedd5
  
  CIFS: Separate SMB2 header structure
  Commit 31473fc4f9653b73750d3792ffce6a6e1bdf0da7
  
  cifs: Add soft dependencies
  Commit b9be76d585d48cb25af8db0d35e1ef9030fbe13a
  
  cifs: Only select the required crypto modules
  Commit 3692304bba6164be3810afd41b84ecb0e1e41db1
  
  cifs: Simplify SMB2 and SMB311 dependencies
  Commit c1ecea87471bbb614f8121e00e5787f363140365

** 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/1670508

Title:
  CIFS: Enable encryption for SMB3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670508/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1670508] [NEW] CIFS: Enable encryption for SMB3

[Stephen A. Zarkos]

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 as follows:

CIFS: Fix possible use after free in demultiplex thread
Commit 61cfac6f267dabcf2740a7ec8a0295833b28b5f5

CIFS: Allow to switch on encryption with seal mount option 
Commit ae6f8dd4d0c87bfb72da9d9b56342adf53e69c31

CIFS: Add capability to decrypt big read responses
Commit c42a6abe3012832a68a371dabe17c2ced97e62ad

CIFS: Decrypt and process small encrypted packets
Commit 4326ed2f6a16ae9d33e4209b540dc9a371aba840

CIFS: Add copy into pages callback for a read operation
Commit d70b9104b1ca586f73aaf59426756cec3325a40e

CIFS: Add mid handle callback
Commit 9b7c18a2d4b798963ea80f6769701dcc4c24b55e

CIFS: Add transform header handling callbacks
Commit 9bb17e0916a03ab901fb684e874d77a1e96b3d1e

CIFS: Encrypt SMB3 requests before sending
Commit 026e93dc0a3eefb0be060bcb9ecd8d7a7fd5c398

CIFS: Enable encryption during session setup phase
Commit cabfb3680f78981d26c078a26e5c748531257ebb

CIFS: Add capability to transform requests before sending
Commit 7fb8986e7449d0a5cebd84d059927afa423fbf85

CIFS: Separate RFC1001 length processing for SMB2 read
Commit b8f57ee8aad414a3122bff72d7968a94baacb9b6

CIFS: Separate SMB2 sync header processing
Commit cb200bd6264a80c04e09e8635fa4f3901cabdaef

CIFS: Send RFC1001 length in a separate iov
Commit 738f9de5cdb9175c19d24cfdf90b4543fc3b47bf

CIFS: Make send_cancel take rqst as argument
Commit fb2036d817584df42504910fe104f68517e8990e

CIFS: Make SendReceive2() takes resp iov
Commit da502f7df03d2d0b416775f92ae022f3f82bedd5

CIFS: Separate SMB2 header structure
Commit 31473fc4f9653b73750d3792ffce6a6e1bdf0da7

cifs: Add soft dependencies
Commit b9be76d585d48cb25af8db0d35e1ef9030fbe13a

cifs: Only select the required crypto modules
Commit 3692304bba6164be3810afd41b84ecb0e1e41db1

cifs: Simplify SMB2 and SMB311 dependencies
Commit c1ecea87471bbb614f8121e00e5787f363140365

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670508

Title:
  CIFS: Enable encryption for SMB3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670508/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1669941] [NEW] CIFS: Call echo service immediately after socket reconnect

[Stephen A. Zarkos]

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 is needed to fully resolve a related
corner case. Please take this commit to the Xenial kernel and later:

Call echo service immediately after socket reconnect
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b8c600120fc87d53642476f48c8055b38d6e14c7

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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:
  CIFS: Call echo service immediately after socket reconnect

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1669941/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1376274] Re: unscd segfaults regularly

[Stephen A. Zarkos]

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 this null pointer check is the only change in that
release. To me this seems low risk to keep the null pointer check and
release this.


** 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/1376274

Title:
  unscd segfaults regularly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unscd/+bug/1376274/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1642383] Re: Unable to configure swap space on ephemeral disk in Azure

[Stephen A. Zarkos]

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 calling this resolved since I'm unable to repro
again.

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/1642383

Title:
  Unable to configure swap space on ephemeral disk in Azure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1642383/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1642383] Re: Unable to configure swap space on ephemeral disk in Azure

[Stephen A. Zarkos]

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 ephemeral disk in Azure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1642383/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1642383] Re: Unable to configure swap space on ephemeral disk in Azure

[Stephen A. Zarkos]

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 go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1642383/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1642383] Re: Unable to configure swap space on ephemeral disk in Azure

[Stephen A. Zarkos]

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:
  Unable to configure swap space on ephemeral disk in Azure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1642383/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1642383] [NEW] Unable to configure swap space on ephemeral disk in Azure

[Stephen A. Zarkos]

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 customdata.txt:

 #cloud-config
 disk_setup:
 ephemeral0:
 table_type: mbr
 layout: [66, [33, 82]]
 overwrite: True
 fs_setup:
 - device: ephemeral0.1
   filesystem: ext4
 - device: ephemeral0.2
   filesystem: swap
 mounts:
 - ["ephemeral0.1", "/mnt2"]
 - ["ephemeral0.2", "none", "swap", "sw", "0", "0"]

2) Create a VM in Azure with this cloud-config:

 $ azure group create ubtest 'east us'

 $ azure vm create ubtest ubtest-1604 Linux --image-urn
canonical:UbuntuServer:16.04.0-LTS:latest --admin-username azureuser
--admin-password '' --nic-name ubtest-1604 --location "East
US" --vnet-name "ubtest" --vnet-address-prefix "10.0.0.0/24" --vnet-
subnet-name "ubtest" --vnet-subnet-address-prefix "10.0.0.0/24"
--public-ip-name "ubtest" --public-ip-domain-name "ubtest" --custom-data
./customdata.txt


Expected Result:

 - /dev/disk/cloud/azure_resource should have two partitions; one ext4 and a 
second swap
 - /dev/disk/cloud/azure_resource-part1 should be mounted on /mnt2
 - /dev/disk/cloud/azure_resource-part2 should be active swap space
 - /etc/fstab should be configured correctly


Actual Results:

 - /dev/disk/cloud/azure_resource-part1 is properly mounted on /mnt2.
 - On Ubuntu 14.04, /dev/disk/cloud/azure_resource is re-partitioned as 
expected.
 - On Ubuntu 16.04, /dev/disk/cloud/azure_resource is *not* re-partitioned. 
There is only a single partition (no swap space).
 - On Ubuntu 14.04 and 16.04, /etc/fstab includes an incorrect entry for the 
swap space:

   ephemeral0.2noneswapsw,comment=cloudconfig  0   0

This clearly won't work, it should resolve to "/dev/disk/cloud
/azure_resource-part2".  I do notice that on Ubuntu 14.04, the ephemeral
disk is re-partitioned correctly, but there is no symlink in
/dev/disk/azure/ to the second partition. These symlinks are created by
/lib/udev/rules.d/66-azure-ephemeral.rules. Perhaps cloud-init needs to
re-trigger this udev rule after repartitioning the disk.


FYI, I also tested with the latest cloud-init that is currently in 
xenial-proposed (0.7.8-47-gb6561a1-0ubuntu1~16.04.1) with the same results.

** Affects: cloud-init (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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 go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1642383/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1623570] Re: Azure: cannot start walinux agent (Transaction order is cyclic.)

[Stephen A. Zarkos]

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 of cloud-init starting walinuxagent was needed early on to
allow the agent to communicate with the wire server so that the
provisioning ISO could be attached to the VM.  That's no longer needed.
All cloud-init needs to do is obtain the certificates for the SSH public
key and post 'ready' to the fabric once it has processed its cloud-
config.

Steve

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1623570

Title:
  Azure: cannot start walinux agent (Transaction order is cyclic.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1623570/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1611520] [NEW] unscd is more noisy than nscd while invalidating caches

[Stephen A. Zarkos]

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 invalidate(group) request, exiting

The command completes successfully, but the spurious message looks like
an error and causes concern among our users. This issue was apparently
fixed in Debian here: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=622230. Can Ubuntu please take this fix?

** Affects: unscd (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611520

Title:
  unscd is more noisy than nscd while invalidating caches

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unscd/+bug/1611520/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1603222] Re: Azure: incorrect entry in fstab for ephemeral disk

[Stephen A. Zarkos]

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 
/dev/disk/azure/resource
[CLOUDINIT] cc_mounts.py[DEBUG]: changed default device ephemeral0 => 
/dev/disk/azure/resource-part1

[CLOUDINIT] cc_mounts.py[DEBUG]: Mapped metadata name ephemeral0 to /dev/sdb
[CLOUDINIT] cc_mounts.py[DEBUG]: changed default device ephemeral0 => /dev/sdb1

-- 
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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1603222/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1603222] [NEW] Azure: incorrect entry in fstab for ephemeral disk

[Stephen A. Zarkos]

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 cloud-init overwrites the fstab
entry and changes the "/dev/disk/azure/resource-part1" to the device
name that it points to, i.e. /dev/sdb1.  However, this is incorrect
since /dev/sd* device names are not persistent.


Repro:

1) Provision an Ubuntu VM on Azure (I tested with 14.04.4)
2) The fstab entry for the ephemeral disk (/mnt) correctly points to 
"/dev/disk/azure/resource-part1".
3) Reboot the VM (sudo reboot)
4) The fstab entry now incorrectly points to /dev/sdb1 instead of the symlink.

Impact:
There is a chance that the customer's ephemeral disk will not be mounted 
properly if the device names change after a reboot.

** Affects: cloud-init (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1603222/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1603222] Re: Azure: incorrect entry in fstab for ephemeral disk

[Stephen A. Zarkos]

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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1603222/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1596696] [NEW] qemu-img: backport fix for VHD conversion to Xenial

[Stephen A. Zarkos]

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 have this fix backported to Xenial (Qemu v2.5) so that
LTS users will not encounter this issue?

** Affects: qemu (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1596696

Title:
  qemu-img: backport fix for VHD conversion to Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1596696/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1579192] [NEW] dhclient.conf regression in walinuxagent 2.0.16-0ubuntu2~12.04.0

[Stephen A. Zarkos]

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 dhclient.conf
configuration is different for Precise and Trusty, and thus this
functionality regressed in Precise.

The solution is to just replace the postinst file in the Precise package
for the 2.0.16 walinuxagent with one from an older/correct package, and
rebuild the package.  If it helps I've attached the correct postinst
file for Precise to this bug.


Repro:
 - Create an Ubuntu 12.04 VM in Azure
 - Upgrade to the latest walinuxagent package for Precise 
(2.0.16-0ubuntu2~12.04.0)
 - Change the hostname
 - Run "sudo ifdown eth0 && sudo ifup eth0"
 - After a few seconds run "hostname -f"

Expected: Hostname is resolvable.

Result: Hostname is not resolvable because the new hostname was not sent
to the DHCP server, because the dhclient.conf configuration is
incorrect.

** Affects: walinuxagent (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "postinst"
   https://bugs.launchpad.net/bugs/1579192/+attachment/4657472/+files/postinst

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579192

Title:
  dhclient.conf regression in walinuxagent 2.0.16-0ubuntu2~12.04.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1579192/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1549789] Re: [SRU] Updated walinuxagent to 2.0.16

[Stephen A. Zarkos]

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] Updated walinuxagent to 2.0.16

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1549789/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1571822] [NEW] Azure: cloud-init will not set password on existing user

[Stephen A. Zarkos]

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
file as usual and attempt to set that password for the existing user.

Repro:
1) Capture or upload a user image with a pre-created user
2) Provision a VM with a password

Expected: password is (re)set on the user account based on the info in the 
ovf-env.xml file.
Result: password is not set.

** Affects: cloud-init (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571822

Title:
  Azure: cloud-init will not set password on existing user

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1571822/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1549789] Re: [SRU] Updated walinuxagent to 2.0.16

[Stephen A. Zarkos]

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 missed
the other half.

-- 
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] Updated walinuxagent to 2.0.16

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1549789/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1555902] [NEW] Azure: Precise should use the same instance ID detection as Trusty

[Stephen A. Zarkos]

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
detection logic as Trusty.

Related Bugs:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1506187
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1551419

** Affects: cloud-init (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1555902

Title:
  Azure: Precise should use the same instance ID detection as Trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1555902/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1555902] [NEW] Azure: Precise should use the same instance ID detection as Trusty

[Stephen A. Zarkos]

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
detection logic as Trusty.

Related Bugs:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1506187
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1551419

** Affects: cloud-init (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555902

Title:
  Azure: Precise should use the same instance ID detection as Trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1555902/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure

[Stephen A. Zarkos]

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.
https://bugs.launchpad.net/bugs/1551419

Title:
  Fix UUID endianness patch breaks cloud-init on Azure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1551419/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure

[Stephen A. Zarkos]

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.
https://bugs.launchpad.net/bugs/1551419

Title:
  Fix UUID endianness patch breaks cloud-init on Azure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1551419/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure

[Stephen A. Zarkos]

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
EF6EED16-EAD5-BC4C-AD75-550370C212EE

# uname -r
3.19.0-51-generic
# cat /sys/class/dmi/id/product_uuid && dmidecode -s system-uuid
16ED6EEF-D5EA-4CBC-AD75-550370C212EE
EF6EED16-EAD5-BC4C-AD75-550370C212EE

-- 
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/1551419

Title:
  Fix UUID endianness patch breaks cloud-init on Azure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1551419/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure

[Stephen A. Zarkos]

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
EF6EED16-EAD5-BC4C-AD75-550370C212EE

# uname -r
3.19.0-51-generic
# cat /sys/class/dmi/id/product_uuid && dmidecode -s system-uuid
16ED6EEF-D5EA-4CBC-AD75-550370C212EE
EF6EED16-EAD5-BC4C-AD75-550370C212EE

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1551419/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure

[Stephen A. Zarkos]

** 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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1551419/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1551419] [NEW] Fix UUID endianness patch breaks cloud-init on Azure

[Stephen A. Zarkos]

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, but also has the effect causing cloud-init to
think that the system-uuid has changed:
http://kernel.ubuntu.com/git/ubuntu/ubuntu-
trusty.git/commit/drivers/firmware?id=3ec24c55be6c543797ba3ee9a227a5631aef607e

The impact is that cloud-init attempts to reprovision the VM, often
causing the customer to lose access to their VM.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1551419/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1544764] [NEW] ephemeral-disk-warning.conf should run ephemeral-disk-warning.sh

[Stephen A. Zarkos]

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
service does.

Also, I'm not sure there is a strong need to "chattr +i" this file since
it will be recreated at boot time if needed (the Linux agent doesn't
chattr this file).  What's happening now is customers are finding this
"DATALOSS_WARNING_README.txt" file on partitions other than /mnt
(because "sdb1" as the resource disk is not persistent) and then don't
understand why they cannot delete it :)

Thanks!
Steve

** Affects: walinuxagent (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/bugs/1544764

Title:
  ephemeral-disk-warning.conf should run ephemeral-disk-warning.sh

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1544764/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1544764] [NEW] ephemeral-disk-warning.conf should run ephemeral-disk-warning.sh

[Stephen A. Zarkos]

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
service does.

Also, I'm not sure there is a strong need to "chattr +i" this file since
it will be recreated at boot time if needed (the Linux agent doesn't
chattr this file).  What's happening now is customers are finding this
"DATALOSS_WARNING_README.txt" file on partitions other than /mnt
(because "sdb1" as the resource disk is not persistent) and then don't
understand why they cannot delete it :)

Thanks!
Steve

** Affects: walinuxagent (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1544764

Title:
  ephemeral-disk-warning.conf should run ephemeral-disk-warning.sh

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1544764/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1506187] Re: [SRU] Azure: cloud-init should use VM unique ID

[Stephen A. Zarkos]

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 restarting it I saw that the Instance ID
changed (you can see this in /var/log/waagent.log).  However, the
symlink in /var/lib/cloud/instances/ that links the old Instance ID to
the VM unique ID had been created, and so cloud-init did not attempt to
reprovision the VM.

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:
  [SRU] Azure: cloud-init should use VM unique ID

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1506187/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1506187] Re: [SRU] Azure: cloud-init should use VM unique ID

[Stephen A. Zarkos]

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 restarting it I saw that the Instance ID
changed (you can see this in /var/log/waagent.log).  However, the
symlink in /var/lib/cloud/instances/ that links the old Instance ID to
the VM unique ID had been created, and so cloud-init did not attempt to
reprovision the VM.

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:
  [SRU] Azure: cloud-init should use VM unique ID

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1506187/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1498206] Re: Fix CPU lockup on Hyper-V/Azure

[Stephen A. Zarkos]

** 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:
  Fix CPU lockup on Hyper-V/Azure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1498206/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1508706] Re: Networking hangs on azure using hv_netvsc; bisected

[Stephen A. Zarkos]

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 this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508706

Title:
  Networking hangs on azure using hv_netvsc; bisected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508706/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1498206] Re: Fix CPU lockup on Hyper-V/Azure

[Stephen A. Zarkos]

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.
https://bugs.launchpad.net/bugs/1498206

Title:
  Fix CPU lockup on Hyper-V/Azure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1498206/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1506187] Re: Azure: cloud-init should use VM unique ID

[Stephen A. Zarkos]

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: cloud-init should use VM unique ID

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1506187/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1506187] Re: Azure: cloud-init should use VM unique ID

[Stephen A. Zarkos]

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 use VM unique ID

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1506187/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1506187] [NEW] Azure: cloud-init should use VM unique ID

[Stephen A. Zarkos]

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 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

** Affects: cloud-init (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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 use VM unique ID

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1506187/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1506187] [NEW] Azure: cloud-init should use VM unique ID

[Stephen A. Zarkos]

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 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

** Affects: cloud-init (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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: cloud-init should use VM unique ID

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1506187/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1498206] [NEW] Fix CPU lockup on Hyper-V/Azure

[Stephen A. Zarkos]

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: 
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/arch/x86/kernel/cpu?id=88c9281a9fba67636ab26c1fd6afbc78a632374f

Repro rate is low.  To repro, provision a larger VM (i.e. G5 VM on
Azure) and reboot many times, monitoring the console until the "soft
lockup - CPU" error is seen.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1498206/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1498206] Re: Fix CPU lockup on Hyper-V/Azure

[Stephen A. Zarkos]

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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1498206/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1498179] [NEW] Azure: After changing hostname, old hostname is still published to DHCP after reboot

[Stephen A. Zarkos]

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 hostname is always pushed to Azure DNS instead of the new one.

Repro steps:

  - Create Ubuntu 14.04 VM on Azure
  - Edit /etc/hostname to change the hostname
  - Reboot the VM
  - After reboot, the hostname will be changed, but commands like 'hostname -f' 
and 'sudo' will complain that the new hostname cannot be found via a DNS lookup.

Next, bounce DHCP to force the DNS update and check that the new
hostname has been published:

  - Run "sudo ifdown eth0 && sudo ifup eth0"
  - After a few seconds run: "host NEWHOSTNAME".

DNS lookup to the new hostname should succeed now indicating that the
new hostname was pushed to the DHCP server and into Azure DNS.  Commands
like 'hostname -f' and 'sudo' will work now.

However, after rebooting the OLD hostname will again be published to
DNS:

  - Run 'sudo reboot'
  - After logging in, run "host OLDHOSTNAME" and see that the old hostname is 
again published to DNS.  Commands like "hostname -f" and "host NEWHOSTNAME" 
will again fail.

** Affects: cloud-init (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1498179

Title:
  Azure: After changing hostname, old hostname is still published to
  DHCP after reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1498179/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1498179] [NEW] Azure: After changing hostname, old hostname is still published to DHCP after reboot

[Stephen A. Zarkos]

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 hostname is always pushed to Azure DNS instead of the new one.

Repro steps:

  - Create Ubuntu 14.04 VM on Azure
  - Edit /etc/hostname to change the hostname
  - Reboot the VM
  - After reboot, the hostname will be changed, but commands like 'hostname -f' 
and 'sudo' will complain that the new hostname cannot be found via a DNS lookup.

Next, bounce DHCP to force the DNS update and check that the new
hostname has been published:

  - Run "sudo ifdown eth0 && sudo ifup eth0"
  - After a few seconds run: "host NEWHOSTNAME".

DNS lookup to the new hostname should succeed now indicating that the
new hostname was pushed to the DHCP server and into Azure DNS.  Commands
like 'hostname -f' and 'sudo' will work now.

However, after rebooting the OLD hostname will again be published to
DNS:

  - Run 'sudo reboot'
  - After logging in, run "host OLDHOSTNAME" and see that the old hostname is 
again published to DNS.  Commands like "hostname -f" and "host NEWHOSTNAME" 
will again fail.

** Affects: cloud-init (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1498179

Title:
  Azure: After changing hostname, old hostname is still published to
  DHCP after reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1498179/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1490796] Re: [SRU] cloud-init must check/format Azure ephemeral disks each boot

[Stephen A. Zarkos]

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.net/bugs/1490796

Title:
  [SRU] cloud-init must check/format Azure ephemeral disks each boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1490796/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1490796] Re: [SRU] cloud-init must check/format Azure ephemeral disks each boot

[Stephen A. Zarkos]

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

Title:
  [SRU] cloud-init must check/format Azure ephemeral disks each boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1490796/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1490796] [NEW] cloud-init must check/format Azure empheral disks each boot

[Stephen A. Zarkos]

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.  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.

** Affects: cloud-init (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1490796

Title:
  cloud-init must check/format Azure empheral disks each boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1490796/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1490796] [NEW] cloud-init must check/format Azure empheral disks each boot

[Stephen A. Zarkos]

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.  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.

** Affects: cloud-init (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1490796

Title:
  cloud-init must check/format Azure empheral disks each boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1490796/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1445195] Re: [Hyper-V] Kernel patches for storvsc

[Stephen A. Zarkos]

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:
  [Hyper-V] Kernel patches for storvsc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1445195/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458052] Re: [SRU] Azure Datasource writes user password in plain text

[Stephen A. Zarkos]

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.
https://bugs.launchpad.net/bugs/1458052

Title:
  [SRU] Azure Datasource writes user password in plain text

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1458052/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458052] Re: [SRU] Azure Datasource writes user password in plain text

[Stephen A. Zarkos]

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://bugs.launchpad.net/bugs/1458052

Title:
  [SRU] Azure Datasource writes user password in plain text

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1458052/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1445195] Re: [Hyper-V] Kernel patches for storvsc

[Stephen A. Zarkos]

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, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195

Title:
  [Hyper-V] Kernel patches for storvsc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1445195/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1445195] Re: [Hyper-V] Kernel patches for storvsc

[Stephen A. Zarkos]

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 patches for storvsc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1445195/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1445195] Re: [Hyper-V] Kernel patches for storvsc

[Stephen A. Zarkos]

@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 member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445195

Title:
  [Hyper-V] Kernel patches for storvsc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1445195/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1445195] Re: [Hyper-V] Kernel patches for storvsc

[Stephen A. Zarkos]

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 for storvsc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1445195/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1445195] Re: [Hyper-V] Kernel patches for storvsc

[Stephen A. Zarkos]

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 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 for storvsc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1445195/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1463584] Re: [Hyper-V] Add support for VMBus panic notifier handler

[Stephen A. Zarkos]

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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463584/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1445195] Re: [Hyper-V] Kernel patches for storvsc

[Stephen A. Zarkos]

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 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 for storvsc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1445195/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1463584] Re: Add support for VMBus panic notifier handler

[Stephen A. Zarkos]

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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463584/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1463584] Re: Add support for VMBus panic notifier handler

[Stephen A. Zarkos]

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:
  Add support for VMBus panic notifier handler

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463584/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1463584] [NEW] Add support for VMBus panic notifier handler

[Stephen A. Zarkos]

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
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/hv?id=96c1d0581d00f7abe033350edb021a9d947d8d81

Drivers: hv: vmbus: Correcting truncation error for constant 
HV_CRASH_CTL_CRASH_NOTIFY
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/hv?id=5ef5b6927f14f29cacd78fa1fb861661a5367f13


In the event of a kernel panic, VMBus driver supports sending five 64-bit 
values to be recorded in the log.  On Hyper-V this is recorded in the event 
log, and on Azure we can use this data to better detect failures like this in 
the guest VM and surface that as part of our diagnostics information.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: kernel-hyper-v

-- 
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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463584/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1417313] Re: [Hyper-V] vmbus: incorrect device name is printed when child device is unregistered

[Stephen A. Zarkos]

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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1417313

Title:
  [Hyper-V] vmbus: incorrect device name is printed when child device is
  unregistered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1417313/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1417313] Re: [Hyper-V] vmbus: incorrect device name is printed when child device is unregistered

[Stephen A. Zarkos]

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: incorrect device name is printed when child device is
  unregistered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1417313/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1417313] Re: [Hyper-V] vmbus: incorrect device name is printed when child device is unregistered

[Stephen A. Zarkos]

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: incorrect device name is printed when child device is
  unregistered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1417313/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1417313] Re: [Hyper-V] vmbus: incorrect device name is printed when child device is unregistered

[Stephen A. Zarkos]

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.
https://bugs.launchpad.net/bugs/1417313

Title:
  [Hyper-V] vmbus: incorrect device name is printed when child device is
  unregistered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1417313/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1417313] [NEW] [Hyper-V] vmbus: incorrect device name is printed when child device is unregistered

[Stephen A. Zarkos]

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] hv_vmbus: child device àõsèè0_5 unregistered

By logging the message just before calling device_unregister, the
correct device name is printed:

  [ 3145.034652] hv_vmbus: child device vmbus_0_5 unregistered


This issue has been resolved with the upstream patch: 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/hv/vmbus_drv.c?id=84672369ffb98a51d4ddf74c20a23636da3ad615

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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: incorrect device name is printed when child device is
  unregistered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1417313/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1374166] Re: Document how to add swap space on Azure resource disk

[Stephen A. Zarkos]

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-to-inject-custom-data/
http://azure.microsoft.com/blog/2014/04/21/custom-data-and-cloud-init-on-windows-azure/

While passing a cloud-config via CustomData will work great during the
initial setup and provisioning of the machine, is there a workflow that
could allow a customer to configure a local cloud-config to configure
swap space post-provisioning?  This is feasible for those distributions
that just use the Azure Linux agent, so preferably there is a way to do
this on Ubuntu as well.

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/1374166

Title:
  Document how to add swap space on Azure resource disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1374166/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1374166] Re: Document how to add swap space on Azure resource disk

[Stephen A. Zarkos]

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-to-inject-custom-data/
http://azure.microsoft.com/blog/2014/04/21/custom-data-and-cloud-init-on-windows-azure/

While passing a cloud-config via CustomData will work great during the
initial setup and provisioning of the machine, is there a workflow that
could allow a customer to configure a local cloud-config to configure
swap space post-provisioning?  This is feasible for those distributions
that just use the Azure Linux agent, so preferably there is a way to do
this on Ubuntu 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/1374166

Title:
  Document how to add swap space on Azure resource disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1374166/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1411582] Re: Azure data source should auto-detect ephemeral disk location

[Stephen A. Zarkos]

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 least knows the order of the disks (IDE or SCSI) that are
attached on the Host side.  And on Azure, the first IDE disk is always
the OS disk, and the second is always the ephemeral disk.  That is known
and must be the case for all VMs.

So in the agent, DeviceForIdePort()[0] always returns the OS disk, and
DeviceForIdePort()[1] always returns the ephemeral disk.  Ideally cloud-
init should use a similar method to auto-detect the ephemeral disk and
update fstab if needed.

Thanks!

-- 
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/1411582

Title:
  Azure data source should auto-detect ephemeral disk location

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1411582/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1374115] Re: Allow cloud-config to modify partitioning and mount point of temporary resource disk in Azure

[Stephen A. Zarkos]

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 cloud
images.  That would be a simple patch to the walinuxagent package unless
cloud-init wants to start using those parameters at some point.

Thanks.

-- 
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/1374115

Title:
  Allow cloud-config to modify partitioning and mount point of temporary
  resource disk in Azure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1374115/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1411582] Re: Azure data source should auto-detect ephemeral disk location

[Stephen A. Zarkos]

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 least knows the order of the disks (IDE or SCSI) that are
attached on the Host side.  And on Azure, the first IDE disk is always
the OS disk, and the second is always the ephemeral disk.  That is known
and must be the case for all VMs.

So in the agent, DeviceForIdePort()[0] always returns the OS disk, and
DeviceForIdePort()[1] always returns the ephemeral disk.  Ideally cloud-
init should use a similar method to auto-detect the ephemeral disk and
update fstab if needed.

Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1411582

Title:
  Azure data source should auto-detect ephemeral disk location

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1411582/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1374115] Re: Allow cloud-config to modify partitioning and mount point of temporary resource disk in Azure

[Stephen A. Zarkos]

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 cloud
images.  That would be a simple patch to the walinuxagent package unless
cloud-init wants to start using those parameters at some point.

Thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374115

Title:
  Allow cloud-config to modify partitioning and mount point of temporary
  resource disk in Azure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1374115/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1410835] Re: Azure ephemeral disk and custom mount points

[Stephen A. Zarkos]

+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 Azure Linux agent).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1410835

Title:
  Azure ephemeral disk and custom mount points

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1410835/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1410835] Re: Azure ephemeral disk and custom mount points

[Stephen A. Zarkos]

+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 Azure Linux agent).

-- 
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/1410835

Title:
  Azure ephemeral disk and custom mount points

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1410835/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1374115] Re: Allow cloud-config to modify partitioning and mount point of temporary resource disk in Azure

[Stephen A. Zarkos]

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
mount point at provision time.   This is on par with with other cloud
providers - the ephemeral disk can be repartitioned and/or mounted at a
different location at provisioning time.

-- 
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/1374115

Title:
  Allow cloud-config to modify partitioning and mount point of temporary
  resource disk in Azure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1374115/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1374115] Re: Allow cloud-config to modify partitioning and mount point of temporary resource disk in Azure

[Stephen A. Zarkos]

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
mount point at provision time.   This is on par with with other cloud
providers - the ephemeral disk can be repartitioned and/or mounted at a
different location at provisioning time.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374115

Title:
  Allow cloud-config to modify partitioning and mount point of temporary
  resource disk in Azure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1374115/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1400947] [NEW] Upstream bugfixes for hv_vmbus

[Stephen A. Zarkos]

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

Drivers: hv: vmbus: Cleanup vmbus_establish_gpadl()


commit b29ef3546aecb253a5552b198cef23750d56e1e4
Author: K. Y. Srinivasan k...@microsoft.com
Date:   Thu Aug 28 18:29:52 2014 -0700

Drivers: hv: vmbus: Cleanup hv_post_message()


commit 98d731bb064a9d1817a6ca9bf8b97051334a7cfe
Author: K. Y. Srinivasan k...@microsoft.com
Date:   Wed Aug 27 16:25:33 2014 -0700

Drivers: hv: vmbus: Cleanup vmbus_close_internal()


commit 45d727cee9e200f5b351528b9fb063b69cf702c8
Author: K. Y. Srinivasan k...@microsoft.com
Date:   Wed Aug 27 16:25:35 2014 -0700

Drivers: hv: vmbus: Fix a bug in vmbus_open()

commit 66be653083057358724d56d817e870e53fb81ca7
Author: K. Y. Srinivasan k...@microsoft.com
Date:   Wed Aug 27 16:25:32 2014 -0700

Drivers: hv: vmbus: Cleanup vmbus_teardown_gpadl()


commit fdeebcc62279119dbeafbc1a2e39e773839025fd
Author: K. Y. Srinivasan k...@microsoft.com
Date:   Wed Aug 27 16:25:31 2014 -0700

Drivers: hv: vmbus: Cleanup vmbus_post_msg()

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1400947

Title:
  Upstream bugfixes for hv_vmbus

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400947/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1382257] Re: [SRU] Add readme to Azure's ephemeral (resource) disk

[Stephen A. Zarkos]

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!

-- 
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/bugs/1382257

Title:
  [SRU] Add readme to Azure's ephemeral (resource) disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1382257/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1367883] Re: [SRU] Add Microsoft-owned MAC address to 75-persistent-net-generator.rules

[Stephen A. Zarkos]

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.
https://bugs.launchpad.net/bugs/1367883

Title:
  [SRU] Add Microsoft-owned MAC address to 75-persistent-net-
  generator.rules

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1367883/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1382257] Re: [SRU] Add readme to Azure's ephemeral (resource) disk

[Stephen A. Zarkos]

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!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1382257

Title:
  [SRU] Add readme to Azure's ephemeral (resource) disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1382257/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs