[Kernel-packages] [Bug 1551419] Re: [SRU] Handle changing UUID endian-ness on Azure in cloud-init

2016-03-15 Thread Launchpad Bug Tracker 
This bug was fixed in the package linux-keystone - 3.13.0-53.78

---
linux-keystone (3.13.0-53.78) trusty; urgency=low

  [ Ike Panhc ]

  * Release Tracking Bug
- LP: #1555956
  * Rebase to Ubuntu-3.13.0-83.127

  [ Ubuntu: 3.13.0-83.127 ]

  * Release Tracking Bug
- LP: #1555839
  * SAUCE: [nf,v2] netfilter: x_tables: don't rely on well-behaving
userspace
- LP: #1555338

 -- Ike Panhc   Sat, 12 Mar 2016 10:03:08 +0800

** Changed in: linux-keystone (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1551419

Title:
  [SRU] Handle changing UUID endian-ness on Azure in cloud-init

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux-keystone package in Ubuntu:
  Invalid
Status in cloud-init source package in Trusty:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-keystone source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in cloud-init source package in Vivid:
  Invalid
Status in linux source package in Vivid:
  Fix Released
Status in linux-keystone source package in Vivid:
  Invalid

Bug description:
  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 incorrectly modifies the
  endianness for some SMBIOS fields, which 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

  cloud-init needs to consider both the reported UUID and the "first
  three fields endian-reversed" UUID as the same, so that users shifting
  between unaffected kernels and affected kernels, or affected kernels
  and fixed kernels do not see their instances reprovisioned.

  [Impact]

  The impact is that cloud-init attempts to reprovision VMs when they
  reboot to use the new kernel, often causing the customer to lose
  access to their VM.

  Once the kernel is fixed, rebooting from an affected kernel to the new
  kernel will have the same effect.

  [Test Case]

  Failure:

  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Upgrade the kernel and reboot.
  3) SSH to the instance; you will observe that you are prompted to change SSH 
host keys because cloud-init has run again.

  Success (upgrade from not broken->broken):

  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade the kernel and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.
  5) Make a note of the instance ID in use (i.e. the target of 
/var/lib/cloud/instance
  6) Reboot again.
  7) Observe that the instance ID has not changed.

  Success (upgrade from broken->fixed):
  1) Boot an Azure instance using an image with a broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_4-LTS-amd64-server-20160222-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade to the fixed kernel (once it is available) and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.

  Success (upgrade from not broken->fixed):
  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade to the fixed kernel (once it is available) and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.

  [Regression Potential]

  The change is limited to the Azure data source.  It affects how
  instance IDs are determined, but the change does so in a limited way.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1551419] Re: [SRU] Handle changing UUID endian-ness on Azure in cloud-init

2016-03-14 Thread Launchpad Bug Tracker 
This bug was fixed in the package linux-lts-utopic -
3.16.0-67.87~14.04.1

---
linux-lts-utopic (3.16.0-67.87~14.04.1) trusty; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
- LP: #1555847

  [ Florian Westphal ]

  * SAUCE: [nf,v2] netfilter: x_tables: don't rely on well-behaving
userspace
- LP: #1555338

linux-lts-utopic (3.16.0-66.86~14.04.1) trusty; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
- LP: #1555277

  [ Upstream Kernel Changes ]

  * Revert "drm/radeon: call hpd_irq_event on resume"
- LP: #1554608

linux-lts-utopic (3.16.0-65.85~14.04.1) trusty; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
- LP: #1552352

  [ Upstream Kernel Changes ]

  * Revert "firmware: dmi_scan: Fix UUID endianness for SMBIOS >= 2.6"
- LP: #1551419

linux-lts-utopic (3.16.0-64.84~14.04.1) trusty; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1550605

  [ Kamal Mostafa ]

  * Merged back 3.16.0-63.83~14.04.1

linux-lts-utopic (3.16.0-63.83~14.04.1) trusty; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
- LP: #1548934

  [ Dan Streetman ]

  * SAUCE: nbd: ratelimit error msgs after socket close
- LP: #1505564

  [ Upstream Kernel Changes ]

  * Revert "workqueue: make sure delayed work run in local cpu"
- LP: #1546320
  * drm/nouveau/nv46: Change mc subdev oclass from nv44 to nv4c
- LP: #1543126
  * veth: don’t modify ip_summed; doing so treats packets with bad
checksums as good.
- LP: #1543126
  * sctp: sctp should release assoc when sctp_make_abort_user return NULL
in sctp_close
- LP: #1543126
  * connector: bump skb->users before callback invocation
- LP: #1543126
  * unix: properly account for FDs passed over unix sockets
- LP: #1543126
  * bridge: Only call /sbin/bridge-stp for the initial network namespace
- LP: #1543126
  * vxlan: fix test which detect duplicate vxlan iface
- LP: #1543126
  * net: sctp: prevent writes to cookie_hmac_alg from accessing invalid
memory
- LP: #1543126
  * tcp_yeah: don't set ssthresh below 2
- LP: #1543126
  * bonding: Prevent IPv6 link local address on enslaved devices
- LP: #1543126
  * phonet: properly unshare skbs in phonet_rcv()
- LP: #1543126
  * net: bpf: reject invalid shifts
- LP: #1543126
  * ipv6: update skb->csum when CE mark is propagated
- LP: #1543126
  * team: Replace rcu_read_lock with a mutex in team_vlan_rx_kill_vid
- LP: #1543126
  * xen-netback: respect user provided max_queues
- LP: #1543126
  * xen-netfront: respect user provided max_queues
- LP: #1543126
  * xen-netfront: print correct number of queues
- LP: #1543126
  * xen-netfront: update num_queues to real created
- LP: #1543126
  * sctp: Prevent soft lockup when sctp_accept() is called during a timeout
event
- LP: #1543126
  * sctp: convert sack_needed and sack_generation to bits
- LP: #1543126
  * sctp: start t5 timer only when peer rwnd is 0 and local state is
SHUTDOWN_PENDING
- LP: #1543126
  * nfs: Fix unused variable error
- LP: #1543126
  * [media] gspca: ov534/topro: prevent a division by 0
- LP: #1543126
  * [media] media: dvb-core: Don't force CAN_INVERSION_AUTO in oneshot mode
- LP: #1543126
  * tools lib traceevent: Fix output of %llu for 64 bit values read on 32
bit machines
- LP: #1543126
  * KVM: x86: expose MSR_TSC_AUX to userspace
- LP: #1543126
  * KVM: x86: correctly print #AC in traces
- LP: #1543126
  * drm/radeon: call hpd_irq_event on resume
- LP: #1543126
  * xhci: refuse loading if nousb is used
- LP: #1543126
  * arm64: Clear out any singlestep state on a ptrace detach operation
- LP: #1543126
  * time: Avoid signed overflow in timekeeping_get_ns()
- LP: #1543126
  * Bluetooth: Add support of Toshiba Broadcom based devices
- LP: #1522949, #1543126
  * rtlwifi: fix memory leak for USB device
- LP: #1543126
  * wlcore/wl12xx: spi: fix oops on firmware load
- LP: #1543126
  * EDAC: Fix the leak of mci->bus->name when bus_register fails
- LP: #1543126
  * EDAC, mc_sysfs: Fix freeing bus' name
- LP: #1543126
  * EDAC: Robustify workqueues destruction
- LP: #1543126
  * arm64: mm: ensure that the zero page is visible to the page table
walker
- LP: #1543126
  * powerpc: Make value-returning atomics fully ordered
- LP: #1543126
  * powerpc: Make {cmp}xchg* and their atomic_ versions fully ordered
- LP: #1543126
  * dm space map metadata: remove unused variable in brb_pop()
- LP: #1543126
  * dm thin: fix race condition when destroying thin pool workqueue
- LP: #1543126
  * futex: Drop refcount if requeue_pi() acquired the rtmutex
- LP: #1543126
  * arm64: mdscr_el1: avoid exposing DCC to userspace
- LP: #1543126
  * arm64: kernel: enforce pmuserenr_el0 initialization and restore
- LP: #1543126
  * drm/radeon: clean up fujitsu quirks
- LP: #1543126
  * mmc: sdio: Fix

[Kernel-packages] [Bug 1551419] Re: [SRU] Handle changing UUID endian-ness on Azure in cloud-init

2016-03-14 Thread Launchpad Bug Tracker 
This bug was fixed in the package linux - 3.19.0-56.62

---
linux (3.19.0-56.62) vivid; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
- LP: #1555832

  [ Florian Westphal ]

  * SAUCE: [nf,v2] netfilter: x_tables: don't rely on well-behaving
userspace
- LP: #1555338

linux (3.19.0-55.61) vivid; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
- LP: #1554708

  [ Upstream Kernel Changes ]

  * Revert "drm/radeon: call hpd_irq_event on resume"
- LP: #1554608

linux (3.19.0-54.60) vivid; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
- LP: #1552337

  [ Upstream Kernel Changes ]

  * Revert "firmware: dmi_scan: Fix UUID endianness for SMBIOS >= 2.6"
- LP: #1551419

linux (3.19.0-53.59) vivid; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1550576

  [ Kamal Mostafa ]

  * Merged back 3.19.0-52.58

linux (3.19.0-52.58) vivid; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
- LP: #1548548

  [ Dan Streetman ]

  * SAUCE: nbd: ratelimit error msgs after socket close
- LP: #1505564

  [ Upstream Kernel Changes ]

  * Revert "ACPI / LPSS: allow to use specific PM domain during ->probe()"
- LP: #1542457
  * Revert "workqueue: make sure delayed work run in local cpu"
- LP: #1546320
  * net: ipmr: fix static mfc/dev leaks on table destruction
- LP: #1542457
  * drm/nouveau/nv46: Change mc subdev oclass from nv44 to nv4c
- LP: #1542457
  * ovl: allow zero size xattr
- LP: #1542457
  * ovl: use a minimal buffer in ovl_copy_xattr
- LP: #1542457
  * [media] vb2: fix a regression in poll() behavior for output,streams
- LP: #1542457
  * [media] gspca: ov534/topro: prevent a division by 0
- LP: #1542457
  * [media] media: dvb-core: Don't force CAN_INVERSION_AUTO in oneshot mode
- LP: #1542457
  * tools lib traceevent: Fix output of %llu for 64 bit values read on 32
bit machines
- LP: #1542457
  * KVM: x86: expose MSR_TSC_AUX to userspace
- LP: #1542457
  * KVM: x86: correctly print #AC in traces
- LP: #1542457
  * drm/radeon: call hpd_irq_event on resume
- LP: #1542457
  * xhci: refuse loading if nousb is used
- LP: #1542457
  * arm64: Clear out any singlestep state on a ptrace detach operation
- LP: #1542457
  * time: Avoid signed overflow in timekeeping_get_ns()
- LP: #1542457
  * ovl: root: copy attr
- LP: #1542457
  * Bluetooth: Add support of Toshiba Broadcom based devices
- LP: #1522949, #1542457
  * rtlwifi: fix memory leak for USB device
- LP: #1542457
  * wlcore/wl12xx: spi: fix oops on firmware load
- LP: #1542457
  * ovl: check dentry positiveness in ovl_cleanup_whiteouts()
- LP: #1542457
  * EDAC, mc_sysfs: Fix freeing bus' name
- LP: #1542457
  * EDAC: Robustify workqueues destruction
- LP: #1542457
  * arm64: mm: ensure that the zero page is visible to the page table
walker
- LP: #1542457
  * powerpc: Make value-returning atomics fully ordered
- LP: #1542457
  * powerpc: Make {cmp}xchg* and their atomic_ versions fully ordered
- LP: #1542457
  * dm space map metadata: remove unused variable in brb_pop()
- LP: #1542457
  * dm thin: fix race condition when destroying thin pool workqueue
- LP: #1542457
  * futex: Drop refcount if requeue_pi() acquired the rtmutex
- LP: #1542457
  * arm64: mdscr_el1: avoid exposing DCC to userspace
- LP: #1542457
  * arm64: kernel: enforce pmuserenr_el0 initialization and restore
- LP: #1542457
  * drm/radeon: Fix off-by-one errors in radeon_vm_bo_set_addr
- LP: #1542457
  * drm/radeon: clean up fujitsu quirks
- LP: #1542457
  * mmc: sdio: Fix invalid vdd in voltage switch power cycle
- LP: #1542457
  * mmc: sdhci: Fix DMA descriptor with zero data length
- LP: #1542457
  * mmc: sdhci: Fix sdhci_runtime_pm_bus_on/off()
- LP: #1542457
  * udf: limit the maximum number of indirect extents in a row
- LP: #1542457
  * [media] rc: sunxi-cir: Initialize the spinlock properly
- LP: #1542457
  * nfs: Fix race in __update_open_stateid()
- LP: #1542457
  * USB: cp210x: add ID for ELV Marble Sound Board 1
- LP: #1542457
  * NFSv4: Don't perform cached access checks before we've OPENed the file
- LP: #1542457
  * NFS: Ensure we revalidate attributes before using execute_ok()
- LP: #1542457
  * Thermal: initialize thermal zone device correctly
- LP: #1542457
  * Thermal: handle thermal zone device properly during system sleep
- LP: #1542457
  * Thermal: do thermal zone update after a cooling device registered
- LP: #1542457
  * posix-clock: Fix return code on the poll method's error path
- LP: #1542457
  * rtlwifi: rtl8723be: Fix module parameter initialization
- LP: #1542457
  * rtlwifi: rtl8723ae: Fix initialization of module parameters
- LP: #1542457
  * rtlwifi: rtl8821ae: Fix errors in parameter initialization
- LP: #1542457
  * rtlwifi: rtl8188ee: Fix module parameter initialization

[Kernel-packages] [Bug 1551419] Re: [SRU] Handle changing UUID endian-ness on Azure in cloud-init

2016-03-14 Thread Launchpad Bug Tracker 
This bug was fixed in the package linux - 3.13.0-83.127

---
linux (3.13.0-83.127) trusty; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
- LP: #1555839

  [ Florian Westphal ]

  * SAUCE: [nf,v2] netfilter: x_tables: don't rely on well-behaving
userspace
- LP: #1555338

linux (3.13.0-82.126) trusty; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
- LP: #1554732

  [ Upstream Kernel Changes ]

  * Revert "drm/radeon: call hpd_irq_event on resume"
- LP: #1554608
  * net: generic dev_disable_lro() stacked device handling
- LP: #1547680

linux (3.13.0-81.125) trusty; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
- LP: #1552316

  [ Upstream Kernel Changes ]

  * Revert "firmware: dmi_scan: Fix UUID endianness for SMBIOS >= 2.6"
- LP: #1551419
  * bcache: Fix a lockdep splat in an error path
- LP: #1551327

linux (3.13.0-80.124) trusty; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
- LP: #1548519

  [ Andy Whitcroft ]

  * [Debian] hv: hv_set_ifconfig -- convert to python3
- LP: #1506521
  * [Debian] hv: hv_set_ifconfig -- switch to approved indentation
- LP: #1540586
  * [Debian] hv: hv_set_ifconfig -- fix numerous parameter handling issues
- LP: #1540586

  [ Dan Streetman ]

  * SAUCE: nbd: ratelimit error msgs after socket close
- LP: #1505564

  [ Upstream Kernel Changes ]

  * Revert "workqueue: make sure delayed work run in local cpu"
- LP: #1546320
  * [media] gspca: ov534/topro: prevent a division by 0
- LP: #1542497
  * [media] media: dvb-core: Don't force CAN_INVERSION_AUTO in oneshot mode
- LP: #1542497
  * tools lib traceevent: Fix output of %llu for 64 bit values read on 32
bit machines
- LP: #1542497
  * KVM: x86: correctly print #AC in traces
- LP: #1542497
  * drm/radeon: call hpd_irq_event on resume
- LP: #1542497
  * xhci: refuse loading if nousb is used
- LP: #1542497
  * arm64: Clear out any singlestep state on a ptrace detach operation
- LP: #1542497
  * time: Avoid signed overflow in timekeeping_get_ns()
- LP: #1542497
  * rtlwifi: fix memory leak for USB device
- LP: #1542497
  * wlcore/wl12xx: spi: fix oops on firmware load
- LP: #1542497
  * EDAC, mc_sysfs: Fix freeing bus' name
- LP: #1542497
  * EDAC: Don't try to cancel workqueue when it's never setup
- LP: #1542497
  * EDAC: Robustify workqueues destruction
- LP: #1542497
  * powerpc: Make value-returning atomics fully ordered
- LP: #1542497
  * powerpc: Make {cmp}xchg* and their atomic_ versions fully ordered
- LP: #1542497
  * dm space map metadata: remove unused variable in brb_pop()
- LP: #1542497
  * dm thin: fix race condition when destroying thin pool workqueue
- LP: #1542497
  * futex: Drop refcount if requeue_pi() acquired the rtmutex
- LP: #1542497
  * drm/radeon: clean up fujitsu quirks
- LP: #1542497
  * mmc: sdio: Fix invalid vdd in voltage switch power cycle
- LP: #1542497
  * mmc: sdhci: Fix sdhci_runtime_pm_bus_on/off()
- LP: #1542497
  * udf: limit the maximum number of indirect extents in a row
- LP: #1542497
  * nfs: Fix race in __update_open_stateid()
- LP: #1542497
  * USB: cp210x: add ID for ELV Marble Sound Board 1
- LP: #1542497
  * NFSv4: Don't perform cached access checks before we've OPENed the file
- LP: #1542497
  * NFS: Fix attribute cache revalidation
- LP: #1542497
  * posix-clock: Fix return code on the poll method's error path
- LP: #1542497
  * rtlwifi: rtl8192de: Fix incorrect module parameter descriptions
- LP: #1542497
  * rtlwifi: rtl8192se: Fix module parameter initialization
- LP: #1542497
  * rtlwifi: rtl8192ce: Fix handling of module parameters
- LP: #1542497
  * rtlwifi: rtl8192cu: Add missing parameter setup
- LP: #1542497
  * bcache: fix a livelock when we cause a huge number of cache misses
- LP: #1542497
  * bcache: Add a cond_resched() call to gc
- LP: #1542497
  * bcache: clear BCACHE_DEV_UNLINK_DONE flag when attaching a backing
device
- LP: #1542497
  * bcache: fix a leak in bch_cached_dev_run()
- LP: #1542497
  * bcache: unregister reboot notifier if bcache fails to unregister device
- LP: #1542497
  * bcache: add mutex lock for bch_is_open
- LP: #1542497
  * bcache: allows use of register in udev to avoid "device_busy" error.
- LP: #1542497
  * bcache: Change refill_dirty() to always scan entire disk if necessary
- LP: #1542497
  * wlcore/wl12xx: spi: fix NULL pointer dereference (Oops)
- LP: #1542497
  * Input: i8042 - add Fujitsu Lifebook U745 to the nomux list
- LP: #1542497
  * libxfs: pack the agfl header structure so XFS_AGFL_SIZE is correct
- LP: #1542497
  * x86/xen: don't reset vcpu_info on a cancelled suspend
- LP: #1542497
  * udf: Prevent buffer overrun with multi-byte characters
- LP: #1542497
  * udf: Check output buffer length when converting name to CS0
- LP: #1542497

[Kernel-packages] [Bug 1551419] Re: [SRU] Handle changing UUID endian-ness on Azure in cloud-init

2016-03-13 Thread Mathew Hodson 
** No longer affects: linux-lts-utopic (Ubuntu)

** No longer affects: linux-lts-utopic (Ubuntu Vivid)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1551419

Title:
  [SRU] Handle changing UUID endian-ness on Azure in cloud-init

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux-keystone package in Ubuntu:
  Invalid
Status in cloud-init source package in Trusty:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux-keystone source package in Trusty:
  Fix Committed
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in cloud-init source package in Vivid:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-keystone source package in Vivid:
  Invalid

Bug description:
  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 incorrectly modifies the
  endianness for some SMBIOS fields, which 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

  cloud-init needs to consider both the reported UUID and the "first
  three fields endian-reversed" UUID as the same, so that users shifting
  between unaffected kernels and affected kernels, or affected kernels
  and fixed kernels do not see their instances reprovisioned.

  [Impact]

  The impact is that cloud-init attempts to reprovision VMs when they
  reboot to use the new kernel, often causing the customer to lose
  access to their VM.

  Once the kernel is fixed, rebooting from an affected kernel to the new
  kernel will have the same effect.

  [Test Case]

  Failure:

  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Upgrade the kernel and reboot.
  3) SSH to the instance; you will observe that you are prompted to change SSH 
host keys because cloud-init has run again.

  Success (upgrade from not broken->broken):

  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade the kernel and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.
  5) Make a note of the instance ID in use (i.e. the target of 
/var/lib/cloud/instance
  6) Reboot again.
  7) Observe that the instance ID has not changed.

  Success (upgrade from broken->fixed):
  1) Boot an Azure instance using an image with a broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_4-LTS-amd64-server-20160222-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade to the fixed kernel (once it is available) and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.

  Success (upgrade from not broken->fixed):
  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade to the fixed kernel (once it is available) and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.

  [Regression Potential]

  The change is limited to the Azure data source.  It affects how
  instance IDs are determined, but the change does so in a limited way.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1551419] Re: [SRU] Handle changing UUID endian-ness on Azure in cloud-init

2016-03-09 Thread Brad Figg 
** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1551419

Title:
  [SRU] Handle changing UUID endian-ness on Azure in cloud-init

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux-keystone package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  New
Status in cloud-init source package in Trusty:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux-keystone source package in Trusty:
  Fix Committed
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in cloud-init source package in Vivid:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-keystone source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid

Bug description:
  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 incorrectly modifies the
  endianness for some SMBIOS fields, which 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

  cloud-init needs to consider both the reported UUID and the "first
  three fields endian-reversed" UUID as the same, so that users shifting
  between unaffected kernels and affected kernels, or affected kernels
  and fixed kernels do not see their instances reprovisioned.

  [Impact]

  The impact is that cloud-init attempts to reprovision VMs when they
  reboot to use the new kernel, often causing the customer to lose
  access to their VM.

  Once the kernel is fixed, rebooting from an affected kernel to the new
  kernel will have the same effect.

  [Test Case]

  Failure:

  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Upgrade the kernel and reboot.
  3) SSH to the instance; you will observe that you are prompted to change SSH 
host keys because cloud-init has run again.

  Success (upgrade from not broken->broken):

  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade the kernel and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.
  5) Make a note of the instance ID in use (i.e. the target of 
/var/lib/cloud/instance
  6) Reboot again.
  7) Observe that the instance ID has not changed.

  Success (upgrade from broken->fixed):
  1) Boot an Azure instance using an image with a broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_4-LTS-amd64-server-20160222-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade to the fixed kernel (once it is available) and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.

  Success (upgrade from not broken->fixed):
  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade to the fixed kernel (once it is available) and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.

  [Regression Potential]

  The change is limited to the Azure data source.  It affects how
  instance IDs are determined, but the change does so in a limited way.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1551419] Re: [SRU] Handle changing UUID endian-ness on Azure in cloud-init

2016-03-08 Thread Ubuntu Foundations Team Bug Bot 
** Tags added: patch

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1551419

Title:
  [SRU] Handle changing UUID endian-ness on Azure in cloud-init

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux-keystone package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  New
Status in cloud-init source package in Trusty:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux-keystone source package in Trusty:
  Fix Committed
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in cloud-init source package in Vivid:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-keystone source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid

Bug description:
  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 incorrectly modifies the
  endianness for some SMBIOS fields, which 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

  cloud-init needs to consider both the reported UUID and the "first
  three fields endian-reversed" UUID as the same, so that users shifting
  between unaffected kernels and affected kernels, or affected kernels
  and fixed kernels do not see their instances reprovisioned.

  [Impact]

  The impact is that cloud-init attempts to reprovision VMs when they
  reboot to use the new kernel, often causing the customer to lose
  access to their VM.

  Once the kernel is fixed, rebooting from an affected kernel to the new
  kernel will have the same effect.

  [Test Case]

  Failure:

  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Upgrade the kernel and reboot.
  3) SSH to the instance; you will observe that you are prompted to change SSH 
host keys because cloud-init has run again.

  Success (upgrade from not broken->broken):

  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade the kernel and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.
  5) Make a note of the instance ID in use (i.e. the target of 
/var/lib/cloud/instance
  6) Reboot again.
  7) Observe that the instance ID has not changed.

  Success (upgrade from broken->fixed):
  1) Boot an Azure instance using an image with a broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_4-LTS-amd64-server-20160222-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade to the fixed kernel (once it is available) and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.

  Success (upgrade from not broken->fixed):
  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade to the fixed kernel (once it is available) and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.

  [Regression Potential]

  The change is limited to the Azure data source.  It affects how
  instance IDs are determined, but the change does so in a limited way.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1551419] Re: [SRU] Handle changing UUID endian-ness on Azure in cloud-init

2016-03-08 Thread Launchpad Bug Tracker 
This bug was fixed in the package cloud-init - 0.7.5-0ubuntu1.17

---
cloud-init (0.7.5-0ubuntu1.17) trusty; urgency=medium

  * Microsoft Azure:
- d/patches/lp-1551419-azure-handle-flipped-uuid-endianness.patch: Handle
  cases where the endianness of the DMI UUID used for the instance ID has
  changed since last boot.(LP: #1551419)

 -- Daniel Watkins   Wed, 02 Mar 2016
14:23:18 +

** Changed in: cloud-init (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1551419

Title:
  [SRU] Handle changing UUID endian-ness on Azure in cloud-init

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux-keystone package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  New
Status in cloud-init source package in Trusty:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux-keystone source package in Trusty:
  Fix Committed
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in cloud-init source package in Vivid:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-keystone source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid

Bug description:
  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 incorrectly modifies the
  endianness for some SMBIOS fields, which 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

  cloud-init needs to consider both the reported UUID and the "first
  three fields endian-reversed" UUID as the same, so that users shifting
  between unaffected kernels and affected kernels, or affected kernels
  and fixed kernels do not see their instances reprovisioned.

  [Impact]

  The impact is that cloud-init attempts to reprovision VMs when they
  reboot to use the new kernel, often causing the customer to lose
  access to their VM.

  Once the kernel is fixed, rebooting from an affected kernel to the new
  kernel will have the same effect.

  [Test Case]

  Failure:

  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Upgrade the kernel and reboot.
  3) SSH to the instance; you will observe that you are prompted to change SSH 
host keys because cloud-init has run again.

  Success (upgrade from not broken->broken):

  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade the kernel and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.
  5) Make a note of the instance ID in use (i.e. the target of 
/var/lib/cloud/instance
  6) Reboot again.
  7) Observe that the instance ID has not changed.

  Success (upgrade from broken->fixed):
  1) Boot an Azure instance using an image with a broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_4-LTS-amd64-server-20160222-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade to the fixed kernel (once it is available) and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.

  Success (upgrade from not broken->fixed):
  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade to the fixed kernel (once it is available) and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.

  [Regression Potential]

  The change is limited to the Azure data source.  It affects how
  instance IDs are determined, but the change does so in a limited way.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1551419] Re: [SRU] Handle changing UUID endian-ness on Azure in cloud-init

2016-03-08 Thread Dan Watkins 
I have tested all of the above cases with the cloud-init from -proposed
and it behaved as expected.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1551419

Title:
  [SRU] Handle changing UUID endian-ness on Azure in cloud-init

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux-keystone package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  New
Status in cloud-init source package in Trusty:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux-keystone source package in Trusty:
  Fix Committed
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in cloud-init source package in Vivid:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-keystone source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid

Bug description:
  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 incorrectly modifies the
  endianness for some SMBIOS fields, which 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

  cloud-init needs to consider both the reported UUID and the "first
  three fields endian-reversed" UUID as the same, so that users shifting
  between unaffected kernels and affected kernels, or affected kernels
  and fixed kernels do not see their instances reprovisioned.

  [Impact]

  The impact is that cloud-init attempts to reprovision VMs when they
  reboot to use the new kernel, often causing the customer to lose
  access to their VM.

  Once the kernel is fixed, rebooting from an affected kernel to the new
  kernel will have the same effect.

  [Test Case]

  Failure:

  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Upgrade the kernel and reboot.
  3) SSH to the instance; you will observe that you are prompted to change SSH 
host keys because cloud-init has run again.

  Success (upgrade from not broken->broken):

  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade the kernel and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.
  5) Make a note of the instance ID in use (i.e. the target of 
/var/lib/cloud/instance
  6) Reboot again.
  7) Observe that the instance ID has not changed.

  Success (upgrade from broken->fixed):
  1) Boot an Azure instance using an image with a broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_4-LTS-amd64-server-20160222-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade to the fixed kernel (once it is available) and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.

  Success (upgrade from not broken->fixed):
  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade to the fixed kernel (once it is available) and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.

  [Regression Potential]

  The change is limited to the Azure data source.  It affects how
  instance IDs are determined, but the change does so in a limited way.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1551419] Re: [SRU] Handle changing UUID endian-ness on Azure in cloud-init

2016-03-04 Thread Launchpad Bug Tracker 
** Branch linked: lp:ubuntu/trusty-proposed/linux-lts-vivid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1551419

Title:
  [SRU] Handle changing UUID endian-ness on Azure in cloud-init

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux-keystone package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  New
Status in cloud-init source package in Trusty:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux-keystone source package in Trusty:
  Fix Committed
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in cloud-init source package in Vivid:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-keystone source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid

Bug description:
  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 incorrectly modifies the
  endianness for some SMBIOS fields, which 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

  cloud-init needs to consider both the reported UUID and the "first
  three fields endian-reversed" UUID as the same, so that users shifting
  between unaffected kernels and affected kernels, or affected kernels
  and fixed kernels do not see their instances reprovisioned.

  [Impact]

  The impact is that cloud-init attempts to reprovision VMs when they
  reboot to use the new kernel, often causing the customer to lose
  access to their VM.

  Once the kernel is fixed, rebooting from an affected kernel to the new
  kernel will have the same effect.

  [Test Case]

  Failure:

  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Upgrade the kernel and reboot.
  3) SSH to the instance; you will observe that you are prompted to change SSH 
host keys because cloud-init has run again.

  Success (upgrade from not broken->broken):

  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade the kernel and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.
  5) Make a note of the instance ID in use (i.e. the target of 
/var/lib/cloud/instance
  6) Reboot again.
  7) Observe that the instance ID has not changed.

  Success (upgrade from broken->fixed):
  1) Boot an Azure instance using an image with a broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_4-LTS-amd64-server-20160222-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade to the fixed kernel (once it is available) and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.

  Success (upgrade from not broken->fixed):
  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade to the fixed kernel (once it is available) and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.

  [Regression Potential]

  The change is limited to the Azure data source.  It affects how
  instance IDs are determined, but the change does so in a limited way.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1551419] Re: [SRU] Handle changing UUID endian-ness on Azure in cloud-init

2016-03-03 Thread Adam Conrad 
Hello Stephen, or anyone else affected,

Accepted cloud-init into trusty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.5-0ubuntu1.17 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: cloud-init (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1551419

Title:
  [SRU] Handle changing UUID endian-ness on Azure in cloud-init

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux-keystone package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  New
Status in cloud-init source package in Trusty:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux-keystone source package in Trusty:
  Fix Committed
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in cloud-init source package in Vivid:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-keystone source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid

Bug description:
  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 incorrectly modifies the
  endianness for some SMBIOS fields, which 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

  cloud-init needs to consider both the reported UUID and the "first
  three fields endian-reversed" UUID as the same, so that users shifting
  between unaffected kernels and affected kernels, or affected kernels
  and fixed kernels do not see their instances reprovisioned.

  [Impact]

  The impact is that cloud-init attempts to reprovision VMs when they
  reboot to use the new kernel, often causing the customer to lose
  access to their VM.

  Once the kernel is fixed, rebooting from an affected kernel to the new
  kernel will have the same effect.

  [Test Case]

  Failure:

  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Upgrade the kernel and reboot.
  3) SSH to the instance; you will observe that you are prompted to change SSH 
host keys because cloud-init has run again.

  Success (upgrade from not broken->broken):

  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade the kernel and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.
  5) Make a note of the instance ID in use (i.e. the target of 
/var/lib/cloud/instance
  6) Reboot again.
  7) Observe that the instance ID has not changed.

  Success (upgrade from broken->fixed):
  1) Boot an Azure instance using an image with a broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_4-LTS-amd64-server-20160222-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade to the fixed kernel (once it is available) and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.

  Success (upgrade from not broken->fixed):
  1) Boot an Azure instance using an image with a pre-broken kernel (e.g. 
b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20160201-en-us-30GB)
  2) Install the new version of cloud-init.
  3) Upgrade to the fixed kernel (once it is available) and reboot.
  4) Observe that you are not prompted when SSHing to instance, as cloud-init 
has not run again.

  [Regression Potential]

  The change is limited to the Azure data source.  It affects how
  instance IDs are