[Yahoo-eng-team] [Bug 1678145] [NEW] example chef config broken: upstream apt source has changed
Public bug reported: http://cloudinit.readthedocs.io/en/latest/topics/examples.html#install- and-run-chef-recipes The apt source provided in the example chef config is broken, as upstream has changed. It should now be: source: "deb http://packages.chef.io/repos/apt/stable $RELEASE main" and pull in corresponding gpg key from: https://packages.chef.io/chef.asc I've fixed up and tested locally and will try to get a MR up today. ** Affects: cloud-init Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1678145 Title: example chef config broken: upstream apt source has changed Status in cloud-init: New Bug description: http://cloudinit.readthedocs.io/en/latest/topics/examples.html #install-and-run-chef-recipes The apt source provided in the example chef config is broken, as upstream has changed. It should now be: source: "deb http://packages.chef.io/repos/apt/stable $RELEASE main" and pull in corresponding gpg key from: https://packages.chef.io/chef.asc I've fixed up and tested locally and will try to get a MR up today. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1678145/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1543025] Re: Wrong UTC zoneinfo in cloud-images
Updated status, its long been fix released in the upstream. ** Changed in: cloud-init Status: Triaged => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1543025 Title: Wrong UTC zoneinfo in cloud-images Status in cloud-init: Fix Released Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Fix Released Bug description: ADT runs use cloud-images to create test VM environments. For the Xenial cloud-images I observed a weird issue where libvirt suddenly fails its build-time tests on a time offset test on UTC. Looking at the prepared image (cloud-init did already run there), I found that indeed a command-line of TZ=UTC date reports a CET based time. Looking further this seems to drill down into /usr/share/zoneinfo/UTC -> Zulu and that (Zulu another term for UTC) Zulu file looks quite bigger that the same on other hosts and contains the CET string as well (normal ~128b, wrong size 2335). Forcing a reinstall of tzdata will fix the file and also allows the libvirt test to pass. So I am not sure this is wrong in the initial image base or gets in some way broken during cloud-init. Thats why I start reporting it against cloud-init. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1543025/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1355921] [NEW] [libvirt] When guest configured for threads, poor VCPU accounting
Public bug reported: Noticed while testing: https://blueprints.launchpad.net/nova/+spec /virt-driver-vcpu-topology I have a host advertising 16 VCPUs (2 sockets, each 8 cores). Each core happens to have 8 threads.(This is on a beefy POWER8 system).With the above blueprint, I can now create a 1 socket, 2 core, 8 thread guest. All works fine, except that I noticed Free VCPUS: 0' even though I'm really only using two cores.I'd think I would see 14 free VCPUs in this scenario. Guest lscpu output: [root@bare-precise ~]# lscpu Architecture: ppc64 CPU op-mode(s):32-bit, 64-bit Byte Order:Big Endian CPU(s):16 On-line CPU(s) list: 0-15 Thread(s) per core:8 Core(s) per socket:2 Socket(s): 1 NUMA node(s): 1 Model: IBM pSeries (emulated by qemu) L1d cache: 64K L1i cache: 32K NUMA node0 CPU(s): 0-15 Resulting tracker 2014-08-12 12:17:18.874 96650 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 0 ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1355921 Title: [libvirt] When guest configured for threads, poor VCPU accounting Status in OpenStack Compute (Nova): New Bug description: Noticed while testing: https://blueprints.launchpad.net/nova/+spec /virt-driver-vcpu-topology I have a host advertising 16 VCPUs (2 sockets, each 8 cores). Each core happens to have 8 threads.(This is on a beefy POWER8 system).With the above blueprint, I can now create a 1 socket, 2 core, 8 thread guest. All works fine, except that I noticed Free VCPUS: 0' even though I'm really only using two cores.I'd think I would see 14 free VCPUs in this scenario. Guest lscpu output: [root@bare-precise ~]# lscpu Architecture: ppc64 CPU op-mode(s):32-bit, 64-bit Byte Order:Big Endian CPU(s):16 On-line CPU(s) list: 0-15 Thread(s) per core:8 Core(s) per socket:2 Socket(s): 1 NUMA node(s): 1 Model: IBM pSeries (emulated by qemu) L1d cache: 64K L1i cache: 32K NUMA node0 CPU(s): 0-15 Resulting tracker 2014-08-12 12:17:18.874 96650 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 0 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1355921/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1355921] Re: [libvirt] When guest configured for threads, poor VCPU accounting
Hi there.You didn't actually setup a configuration that would create a VM with threads which was the condition I wrote the bug against. smp 3,sockets=3,cores=1,threads=1 Thanks! ** Changed in: nova Status: Invalid = New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1355921 Title: [libvirt] When guest configured for threads, poor VCPU accounting Status in OpenStack Compute (Nova): New Bug description: Noticed while testing: https://blueprints.launchpad.net/nova/+spec /virt-driver-vcpu-topology I have a host advertising 16 VCPUs (2 sockets, each 8 cores). Each core happens to have 8 threads.(This is on a beefy POWER8 system).With the above blueprint, I can now create a 1 socket, 2 core, 8 thread guest. All works fine, except that I noticed Free VCPUS: 0' even though I'm really only using two cores.I'd think I would see 14 free VCPUs in this scenario. Guest lscpu output: [root@bare-precise ~]# lscpu Architecture: ppc64 CPU op-mode(s):32-bit, 64-bit Byte Order:Big Endian CPU(s):16 On-line CPU(s) list: 0-15 Thread(s) per core:8 Core(s) per socket:2 Socket(s): 1 NUMA node(s): 1 Model: IBM pSeries (emulated by qemu) L1d cache: 64K L1i cache: 32K NUMA node0 CPU(s): 0-15 Resulting tracker 2014-08-12 12:17:18.874 96650 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 0 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1355921/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
