[Yahoo-eng-team] [Bug 1644486] Re: ml2 subnet context's network is missing provider attributes

[YAMAMOTO Takashi]

** Summary changed:

- ml2: missing subnet
+ ml2 subnet context's network is missing provider attributes

** Also affects: neutron
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1644486

Title:
  ml2 subnet context's network is missing provider attributes

Status in networking-midonet:
  In Progress
Status in neutron:
  In Progress

Bug description:
  eg.

  http://logs.openstack.org/62/398562/8/check/gate-tempest-dsvm-
  networking-midonet-ml2-ubuntu-xenial/53547aa/logs/devstacklog.txt.gz

  2016-11-24 08:54:54.010 | + 
lib/neutron_plugins/services/l3:_neutron_configure_router_v4:340 :   openstack 
--os-cloud devstack-admin --os-region RegionOne router add subnet 
b8da6176-8d34-44d8-8fb5-ec9f170ae238 128cf7d1-ebf1-4f3c-8b87-b41b3d705718
  2016-11-24 08:54:57.002 | NotFoundException: Not Found

  
  for some reason midonet ml2 driver doesn't process create_subnet.

  http://logs.openstack.org/62/398562/8/check/gate-tempest-dsvm-
  networking-midonet-ml2-ubuntu-
  xenial/53547aa/logs/q-svc.txt.gz#_2016-11-24_08_54_46_821

  2016-11-24 08:54:46.821 28248 DEBUG neutron.api.v2.base 
[req-e4e28867-560b-4362-adca-d633bdce7af9 admin -] Request body: {u'subnet': 
{u'name': u'private-subnet', u'network_id': 
u'563d7827-83d9-46f6-8a06-2a044009ef52', u'tenant_id': 
u'2c88bcabe4694139a18650fab5c28e1f', u'gateway_ip': u'10.1.0.1', u'ip_version': 
4, u'subnetpool_id': u'00a09b1b-3426-41fb--ff1766ec1811'}} 
prepare_request_body /opt/stack/new/neutron/neutron/api/v2/base.py:692
  2016-11-24 08:54:46.825 28248 DEBUG neutron.db.quota.driver 
[req-e4e28867-560b-4362-adca-d633bdce7af9 admin -] Resources 
endpoint_group,ikepolicy,ipsecpolicy,ipsec_site_connection,subnetpool,vpnservice
 have unlimited quota limit. It is not required to calculate headroom  
make_reservation /opt/stack/new/neutron/neutron/db/quota/driver.py:190
  2016-11-24 08:54:46.829 28248 DEBUG neutron.quota.resource 
[req-e4e28867-560b-4362-adca-d633bdce7af9 admin -] Usage tracker for 
resource:subnet and tenant:2c88bcabe4694139a18650fab5c28e1f is out of sync, 
need to count used quota count 
/opt/stack/new/neutron/neutron/quota/resource.py:270
  2016-11-24 08:54:46.835 28248 DEBUG neutron.quota.resource 
[req-e4e28867-560b-4362-adca-d633bdce7af9 admin -] Quota usage for subnet was 
recalculated. Used quota:0. count 
/opt/stack/new/neutron/neutron/quota/resource.py:289
  2016-11-24 08:54:46.837 28248 DEBUG neutron.db.quota.driver 
[req-e4e28867-560b-4362-adca-d633bdce7af9 admin -] Attempting to reserve 1 
items for resource subnet. Total usage: 0; quota limit: 100; headroom:100 
make_reservation /opt/stack/new/neutron/neutron/db/quota/driver.py:222
  2016-11-24 08:54:47.033 28248 DEBUG neutron.ipam.driver 
[req-e4e28867-560b-4362-adca-d633bdce7af9 admin -] Loading ipam driver: 
internal get_instance /opt/stack/new/neutron/neutron/ipam/driver.py:51
  2016-11-24 08:54:47.110 28248 DEBUG neutron.callbacks.manager 
[req-e4e28867-560b-4362-adca-d633bdce7af9 admin -] Notify callbacks 
[('neutron.api.rpc.agentnotifiers.dhcp_rpc_agent_api.DhcpAgentNotifyAPI._native_event_send_dhcp_notification--9223372036853078740',
 >)] for subnet, after_create _notify_loop 
/opt/stack/new/neutron/neutron/callbacks/manager.py:142
  2016-11-24 08:54:47.164 28248 WARNING neutron.scheduler.dhcp_agent_scheduler 
[req-e4e28867-560b-4362-adca-d633bdce7af9 admin -] No more DHCP agents
  2016-11-24 08:54:47.165 28248 WARNING 
neutron.api.rpc.agentnotifiers.dhcp_rpc_agent_api 
[req-e4e28867-560b-4362-adca-d633bdce7af9 admin -] Unable to schedule network 
563d7827-83d9-46f6-8a06-2a044009ef52: no agents available; will retry on 
subsequent port and subnet creation events.
  2016-11-24 08:54:47.165 28248 DEBUG 
neutron.api.rpc.agentnotifiers.dhcp_rpc_agent_api 
[req-e4e28867-560b-4362-adca-d633bdce7af9 admin -] Network 
563d7827-83d9-46f6-8a06-2a044009ef52 is not hosted by any dhcp agent 
_notify_agents 
/opt/stack/new/neutron/neutron/api/rpc/agentnotifiers/dhcp_rpc_agent_api.py:185
  2016-11-24 08:54:47.172 28248 DEBUG neutron.quota.resource 
[req-e4e28867-560b-4362-adca-d633bdce7af9 admin -] Persisted dirty status for 
tenant:2c88bcabe4694139a18650fab5c28e1f on resource:subnet mark_dirty 
/opt/stack/new/neutron/neutron/quota/resource.py:193
  2016-11-24 08:54:47.173 28248 DEBUG neutron.callbacks.manager 
[req-e4e28867-560b-4362-adca-d633bdce7af9 admin -] Notify callbacks 
[('neutron.api.rpc.agentnotifiers.dhcp_rpc_agent_api.DhcpAgentNotifyAPI._send_dhcp_notification-1697108',
 >)] for subnet, before_response _notify_loop 
/opt/stack/new/neutron/neutron/callbacks/manager.py:142
  2016-11-24 08:54:47.174 28248 INFO neutron.wsgi 
[req-e4e28867-560b-4362-adca-d633bdce7af9 admin -] 127.0.0.1 - - [24/Nov/2016 
08:54:47] "POST /v2.0/subnets HTTP/1.1" 201 879 0.361234

To manage notifications about this bug go to:

[Yahoo-eng-team] [Bug 1644452] [NEW] nova evacuation [manual process] is failed when the cinder is attached to the VM instance

[santhi swaroop]

Public bug reported:

openstack release is Mitaka. and following are the details about the each 
module in the openstack.
=
[root@~~~]# nova --version
6.0.0
[root@~~~]# neutron --version
6.0.0
[root@~~~]# cinder --version
1.9.0
[root@~~~]# glance --version
2.5.0
=
setup model is like openstack controller+ 2 compute nodes + cinder volume 
attached to the compute nodes. created the VM instance on one compute node 
'tripoli' and trying to do the nova evacuate procedure to move the VM to 
another compute node 'cobolt'. 
[root@tripoli ~]# nova service-list
++--+-+--+-+---++-+
| Id | Binary   | Host| Zone | Status  | State | Updated_at 
| Disabled Reason |
++--+-+--+-+---++-+
| 1  | nova-scheduler   | tripoli | internal | enabled | up| 
2016-11-17T10:18:22.00 | -   |
| 2  | nova-consoleauth | tripoli | internal | enabled | up| 
2016-11-17T10:18:24.00 | -   |
| 3  | nova-conductor   | tripoli | internal | enabled | up| 
2016-11-17T10:18:28.00 | -   |
| 14 | nova-compute | tripoli | nova | enabled | up| 
2016-11-17T10:18:23.00 | -   |
| 15 | nova-compute | cobolt  | cobolt   | enabled | up| 
2016-11-17T10:18:27.00 | 

performed the following tasks to evacuate the VM from tripoli to cobolt..
1. nova service-force-down tripoli nova-compute
2. mysql -u root -p nova
3. MariaDB [nova]> update instances set host='cobolt'  where 
uuid='77f60fa5-54cc-45b1-b094-57eafa6f9c14';
MariaDB [nova]> update instances set node='cobolt'  where 
uuid='77f60fa5-54cc-45b1-b094-57eafa6f9c14';
Query OK, 1 row affected (0.00 sec)
Rows matched: 1  Changed: 1  Warnings: 0
4. [root@tripoli ~]# nova show 77f60fa5-54cc-45b1-b094-57eafa6f9c14
+--+--+
| Property | Value  





  |
+--+--+
| OS-DCF:diskConfig| MANUAL 





  |
| OS-EXT-AZ:availability_zone  | cobolt 





  |
| OS-EXT-SRV-ATTR:host | cobolt 




 

[Yahoo-eng-team] [Bug 1644457] [NEW] keypair quota error

[zhaolihui]

Public bug reported:

Description
===
The nova quota-show was error in key_pairs when add keypair.

Steps to reproduce
==
1.nova keypair-add k_001
2.nova keypair-list
3.nova quota-show --detail

Expected result
===
It is correct with key_pairs in_use.

Actual result
=
Follow command "nova keypair-add k_001", keypair-list display k_001,
and "nova quota-show --detail" was correct with keypair in_use value.

Environment
===
1. Devstack with newton version

** Affects: nova
 Importance: Undecided
 Assignee: zhaolihui (zhaolh)
 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/1644457

Title:
  keypair quota error

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===
  The nova quota-show was error in key_pairs when add keypair.

  Steps to reproduce
  ==
  1.nova keypair-add k_001
  2.nova keypair-list
  3.nova quota-show --detail

  Expected result
  ===
  It is correct with key_pairs in_use.

  Actual result
  =
  Follow command "nova keypair-add k_001", keypair-list display k_001,
  and "nova quota-show --detail" was correct with keypair in_use value.

  Environment
  ===
  1. Devstack with newton version

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1644457/+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 1644312] Re: dnsmasq fails to spawn with older dnsmasq, no DHCP, ports fail to transition to ACTIVE

[OpenStack Infra]

Reviewed:  https://review.openstack.org/401985
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=4e965b42a693a32541079a77ae4416dfadf7
Submitter: Jenkins
Branch:master

commit 4e965b42a693a32541079a77ae4416dfadf7
Author: Ihar Hrachyshka 
Date:   Thu Nov 24 11:42:15 2016 +

Revert "DHCP agent: advertise SLAAC prefixes"

This reverts commit 11c3f0cafd62f9f9b46fd494f9cc6c372f77b1c9.

This patch broke all CentOS installations that ship dnsmasq 2.66 that
does not support --ra-param CLI argument.

Change-Id: I1919f9d3af40bb2f10693420ae08e1ec62accb65
Closes-Bug: #1644312


** Changed in: neutron
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1644312

Title:
  dnsmasq fails to spawn with older dnsmasq, no DHCP, ports fail to
  transition to ACTIVE

Status in neutron:
  Fix Released

Bug description:
  There are sporadic failures occurring during CI testing where vif plug
  notifications aren't being generated by neutron. This results in
  occasional vif plug timeouts when spawning instances.

  See
  
http://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:%5C%22Timeout%20waiting%20for%20vif%20plugging%20callback%20for%20instance%5C%22%20AND%20tags:%5C%22screen-n-cpu.txt%5C%22

  for examples.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1644312/+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 1639239] Re: ValueError for Invalid InitiatorConnector in s390

[OpenStack Infra]

Reviewed:  https://review.openstack.org/395067
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=57f46c1c28a2e3ba1f12ec8f883cf99ccd9979db
Submitter: Jenkins
Branch:master

commit 57f46c1c28a2e3ba1f12ec8f883cf99ccd9979db
Author: Matt Riedemann 
Date:   Tue Nov 8 11:22:42 2016 -0500

libvirt: handle os-brick InvalidConnectorProtocol on init

On init the LibvirtDriver imports it's volume drivers into
a registry for later access during volume operations. Several
of the libvirt volume drivers are using os-brick for the connector.
os-brick can raise an exception when loading a connector class
under certain conditions, e.g. s390x + ISER is not a supported
mapping in os-brick. This in turn causes the LibvirtDriver to
fail to load which causes nova-compute to crash.

This change handles the os-brick specific InvalidConnectorProtocol
exception when importing volume drivers, logs a debug message but
doesn't fail to init the LibvirtDriver.

As part of this change the driver_dict_from_config helper method
is integrated with the _get_volume_drivers method as that was
the only thing using it, and it's cleaner if those are just a
single method.

Depends-On: I7183a479bc12c4e5509f52bf7fdd0fa7ccaa7247

Change-Id: I61376469a409dc5475886e6c79486b815129392a
Closes-Bug: #1639239


** Changed in: nova
   Status: In Progress => Fix Released

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

Title:
  ValueError for Invalid InitiatorConnector in s390

Status in OpenStack Compute (nova):
  Fix Released
Status in os-brick:
  Fix Released

Bug description:
  Description
  ===
  Calling the InitiatorConnector factory results in a ValueError for 
unsupported protocols, which goes unhandled and may crash a calling service.

  Steps to reproduce
  ==
  - clone devstack
  - make stack

  Expected result
  ===
  The nova compute service should run.

  Actual result
  =
  A ValueError is thrown, which, in the case of the nova libvirt driver, is not 
handled appropriately. The compute service crashes.

  Environment
  ===
  os|distro=kvmibm1
  os|vendor=kvmibm
  os|release=1.1.3-beta4.3
  git|cinder|master[f6ab36d]
  git|devstack|master[928b3cd]
  git|nova|master[56138aa]
  pip|os-brick|1.7.0

  Logs & Configs
  ==
  [...]
  2016-11-03 17:56:57.204 46141 INFO nova.virt.driver 
[req-fb30a5af-e87c-4ee0-903c-a5aa7d3ad5e3 - -] Loading compute driver 
'libvirt.LibvirtDriver'
  2016-11-03 17:56:57.442 46141 DEBUG os_brick.initiator.connector 
[req-fb30a5af-e87c-4ee0-903c-a5aa7d3ad5e3 - -] Factory for ISCSI on s390x 
factory /usr/lib/python2.7/site-packages/os_brick/initiator/connector.py:261
  2016-11-03 17:56:57.444 46141 DEBUG os_brick.initiator.connector 
[req-fb30a5af-e87c-4ee0-903c-a5aa7d3ad5e3 - -] Factory for ISCSI on s390x 
factory /usr/lib/python2.7/site-packages/os_brick/initiator/connector.py:261
  2016-11-03 17:56:57.445 46141 DEBUG os_brick.initiator.connector 
[req-fb30a5af-e87c-4ee0-903c-a5aa7d3ad5e3 - -] Factory for ISER on s390x 
factory /usr/lib/python2.7/site-packages/os_brick/initiator/connector.py:261
  2016-11-03 17:56:57.445 46141 CRITICAL nova 
[req-fb30a5af-e87c-4ee0-903c-a5aa7d3ad5e3 - -] ValueError: Invalid 
InitiatorConnector protocol specified ISER
  2016-11-03 17:56:57.445 46141 ERROR nova Traceback (most recent call last):
  2016-11-03 17:56:57.445 46141 ERROR nova   File "/usr/bin/nova-compute", line 
10, in 
  2016-11-03 17:56:57.445 46141 ERROR nova sys.exit(main())
  2016-11-03 17:56:57.445 46141 ERROR nova   File 
"/opt/stack/nova/nova/cmd/compute.py", line 56, in main
  2016-11-03 17:56:57.445 46141 ERROR nova topic=CONF.compute_topic)
  2016-11-03 17:56:57.445 46141 ERROR nova   File 
"/opt/stack/nova/nova/service.py", line 216, in create
  2016-11-03 17:56:57.445 46141 ERROR nova 
periodic_interval_max=periodic_interval_max)
  2016-11-03 17:56:57.445 46141 ERROR nova   File 
"/opt/stack/nova/nova/service.py", line 91, in __init__
  2016-11-03 17:56:57.445 46141 ERROR nova self.manager = 
manager_class(host=self.host, *args, **kwargs)
  2016-11-03 17:56:57.445 46141 ERROR nova   File 
"/opt/stack/nova/nova/compute/manager.py", line 537, in __init__
  2016-11-03 17:56:57.445 46141 ERROR nova self.driver = 
driver.load_compute_driver(self.virtapi, compute_driver)
  2016-11-03 17:56:57.445 46141 ERROR nova   File 
"/opt/stack/nova/nova/virt/driver.py", line 1625, in load_compute_driver
  2016-11-03 17:56:57.445 46141 ERROR nova virtapi)
  2016-11-03 17:56:57.445 46141 ERROR nova   File 
"/usr/lib/python2.7/site-packages/oslo_utils/importutils.py", line 44, in 
import_object
  2016-11-03 17:56:57.445 46141 ERROR nova return 

[Yahoo-eng-team] [Bug 1642062] Re: cloud-init-local.service should be RequiresMountsFor=/var/lib/cloud rather than /var/lib

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init - 0.7.8-49-g9e904bb-
0ubuntu1~16.04.1

---
cloud-init (0.7.8-49-g9e904bb-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * debian/cloud-init.postinst: update /etc/fstab on Azure to fix
future resize operations. (LP: #1611074)
  * New upstream snapshot.
- Add activate_datasource, for datasource specific code paths.
  (LP: #1611074)
- systemd: cloud-init-local use RequiresMountsFor=/var/lib/cloud
  (LP: #1642062)

cloud-init (0.7.8-47-gb6561a1-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/cloud-init.templates: enable DigitalOcean by default [Ben Howard]
  * New upstream snapshot.
- systemd/cloud-init-local.service:
  + replace 'Wants' and 'After' on local-fs.target with more granular
After=systemd-remount-fs.service and RequiresMountsFor=/var/lib
and Before=sysinit.target.
This is done run sufficiently early enough to update /etc/fstab.
(LP: #1611074)
  + add Before=NetworkManager.service so that cloud-init can render
NetworkManager network config before it would apply them.
- systemd/cloud-init.service:
  + add Before=sysinit.target and DefaultDependencies=no (LP: #1611074)
  + drop Requires=networking.service to work where networking.service is
not needed.
  + add Conflicts=shutdown.target
  + drop unnecessary Wants=local-fs.target
- net: support reading ipv6 dhcp config from initramfs [LaMont Jones]
  (LP: #1621615)
- dmidecode: Allow dmidecode to be used on aarch64, and only attempt
  usage on x86, x86_64, and aarch64. [Robert Schweikert]
- disk-config: udev settle after partitioning in gpt format.
  (LP: #1626243)
- Add support for snap create-user on Ubuntu Core images. [Ryan Harper]
  (LP: #1619393)
- Fix sshd restarts for rhel distros. [Jim Gorz]
- Move user/group functions to new ug_util file [Joshua Harlow]
- update Gentoo initscripts to run in the correct order [Matthew Thode]
- MAAS: improve the debugging tool in datasource to consider
  config provided on kernel cmdline.
- lxd: Update network config for LXD 2.3 [Stéphane Graber] (LP: #1640556)
- Decode unicode types in decode_binary [Robert Schweikert]
- Allow ephemeral drive to be unpartitioned [Paul Meyer]
- subp: add 'update_env' argument which allows for more easily adding
  environment variables to a subprocess call.
- Adjust mounts and disk configuration for systemd. (LP: #1611074)
- DataSources:
  + Ec2: protect against non-dictionary in block-device-mapping.
  + AliYun: Add new datasource for Ali-Cloud ECS, that is
available but not enabled by default [kaihuan.pkh]
  + DigitalOcean: use meta-data for network configuration and
enable data source by default. [Ben Howard]
  + OpenNebula: replace parsing of 'ip' command with similar function
available in cloudinit.net.  This fixed unit tests when running
in environment with no networking.
- doc changes:
  + Add documentation on stages of boot.
  + make the RST files consistently formated and other improvements.
  + fixed example to not overwrite /etc/hosts [Chris Glass]
  + fix spelling / typos in ca_certs and scripts_vendor.
  + improve HACKING.rst file
  + Add documentation for logging features. [Wesley Wiedenmeier]
  + Improve module documentation and doc cleanup. [Wesley Wiedenmeier]
- code style and unit test changes:
  + pep8: fix style errors reported by pycodestyle 2.1.0
  + pyflakes: fix issue with pyflakes 1.3 found in ubuntu zesty-proposed.
  + Add coverage dependency to bddeb to fix package build.
  + Add coverage collection to tox unit tests. [Joshua Powers]
  + do not read system /etc/cloud/cloud.cfg.d (LP: #1635350)
  + tests: silence the Cheetah UserWarning about NameMapper C version.
  + Fix python2.6 things found running in centos 6.

 -- Scott Moser   Fri, 18 Nov 2016 16:51:54 -0500

** Changed in: cloud-init (Ubuntu Xenial)
   Status: Fix Committed => 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/1642062

Title:
  cloud-init-local.service should be RequiresMountsFor=/var/lib/cloud
  rather than /var/lib

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  New

Bug description:
  cloud-init-local.service writes to /var/lib/cloud/ and is more correct
  to have that listed here than /var/lib.

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net

[Yahoo-eng-team] [Bug 1644502] Re: port not found error on create_subnet

[OpenStack Infra]

Reviewed:  https://review.openstack.org/402023
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=9e006cbe64717f3743a215293586713394c47467
Submitter: Jenkins
Branch:master

commit 9e006cbe64717f3743a215293586713394c47467
Author: Kevin Benton 
Date:   Thu Nov 24 04:17:15 2016 -0800

Capture NotFound Exceptions in subnet postcommit

Change I28323eddcf34fd12002cc706f4a9bcbb3f976ceb introduced
a subtle difference in the types of exceptions that can be
encountered during the operations after creating a subnet.

Before that change, a giant enclosing transaction would provide
REPEATABLE READ guarantees, so once a port was looked up by
IPAM, calling update_port on that port afterwards in the same
transaction would not result in a PortNotFound exception.
The same applied to looking up a router and then updating its
gateway port.

Now that there is no giant enclosing transaction, we have to
capture the possible PortNotFound and RouterNotFound exceptions
that can occur during these post commit subnet create operations.

Closes-Bug: #1644502
Change-Id: I29e2bf7bcda37ebbcee193f94c8b03df90f24ef1


** Changed in: neutron
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1644502

Title:
  port not found error on create_subnet

Status in neutron:
  Fix Released

Bug description:
  Error spotted during subnet creation for a gate test:

  http://logs.openstack.org/77/401377/2/check/gate-tempest-dsvm-neutron-
  linuxbridge-ubuntu-xenial/8a23d5b/logs/testr_results.html.gz

  
  ft198.9: 
tempest.api.network.test_dhcp_ipv6.NetworksTestDHCPv6.test_dhcpv6_stateless_no_ra[id-ae2f4a5d-03ff-4c42-a3b0-ce2fcb7ea832]_StringException:
 Empty attachments:
stderr
stdout

  pythonlogging:'': {{{
  2016-11-24 08:51:28,627 14933 INFO [tempest.lib.common.rest_client] 
Request (NetworksTestDHCPv6:test_dhcpv6_stateless_no_ra): 404 POST 
https://127.0.0.1:9696/v2.0/subnets 0.458s
  2016-11-24 08:51:28,627 14933 DEBUG[tempest.lib.common.rest_client] 
Request - Headers: {'Content-Type': 'application/json', 'Accept': 
'application/json', 'X-Auth-Token': ''}
  Body: {"subnet": {"gateway_ip": "2003::1", "ip_version": 6, "cidr": 
"2003::/64", "network_id": "211d7f7c-4b6e-4bc6-8149-d831dc2018e8", 
"ipv6_address_mode": "slaac"}}
  Response - Headers: {'status': '404', 'connection': 'close', 'server': 
'Apache/2.4.18 (Ubuntu)', 'content-length': '132', 'x-openstack-request-id': 
'req-9f760fe7-a74e-4d3e-be18-23d5ae27c314', 'content-type': 'application/json', 
'content-location': 'https://127.0.0.1:9696/v2.0/subnets', 'date': 'Thu, 24 Nov 
2016 08:51:28 GMT'}
  Body: {"NeutronError": {"message": "Port 
5d8ffe5b-78b6-48ba-921f-800cfaa923c3 could not be found.", "type": 
"PortNotFound", "detail": ""}}
  2016-11-24 08:51:28,684 14933 INFO [tempest.lib.common.rest_client] 
Request (NetworksTestDHCPv6:tearDown): 200 GET 
https://127.0.0.1:9696/v2.0/ports 0.053s
  2016-11-24 08:51:28,684 14933 DEBUG[tempest.lib.common.rest_client] 
Request - Headers: {'Content-Type': 'application/json', 'Accept': 
'application/json', 'X-Auth-Token': ''}
  Body: None
  Response - Headers: {'status': '200', 'connection': 'close', 'server': 
'Apache/2.4.18 (Ubuntu)', 'content-length': '13', 'x-openstack-request-id': 
'req-e3ccd293-e418-457b-90bd-d6e9a362b8f7', 'content-type': 'application/json', 
'content-location': 'https://127.0.0.1:9696/v2.0/ports', 'date': 'Thu, 24 Nov 
2016 08:51:28 GMT'}
  Body: {"ports": []}
  2016-11-24 08:51:28,754 14933 INFO [tempest.lib.common.rest_client] 
Request (NetworksTestDHCPv6:tearDown): 200 GET 
https://127.0.0.1:9696/v2.0/subnets 0.069s
  2016-11-24 08:51:28,754 14933 DEBUG[tempest.lib.common.rest_client] 
Request - Headers: {'Content-Type': 'application/json', 'Accept': 
'application/json', 'X-Auth-Token': ''}
  Body: None
  Response - Headers: {'status': '200', 'connection': 'close', 'server': 
'Apache/2.4.18 (Ubuntu)', 'content-length': '645', 'x-openstack-request-id': 
'req-5d7d9081-6ea3-427e-94ac-53ea2df1dbc9', 'content-type': 'application/json', 
'content-location': 'https://127.0.0.1:9696/v2.0/subnets', 'date': 'Thu, 24 Nov 
2016 08:51:28 GMT'}
  Body: {"subnets": [{"service_types": [], "description": "", 
"enable_dhcp": true, "network_id": "211d7f7c-4b6e-4bc6-8149-d831dc2018e8", 
"tenant_id": "b1b9117753ee40ab92362496e64e09ea", "created_at": 
"2016-11-24T08:51:28Z", "dns_nameservers": [], "updated_at": 
"2016-11-24T08:51:28Z", "gateway_ip": "2003::1", "ipv6_ra_mode": null, 
"allocation_pools": [{"start": "2003::2", "end": "2003:::::"}], 
"host_routes": [], "revision_number": 2, "ip_version": 6, "ipv6_address_mode": 
"slaac", "cidr": "2003::/64", "project_id": 

[Yahoo-eng-team] [Bug 1619393] Re: cloud-init useradd/groupadd fails on ubuntu-core-16 with readonly /etc/passwd

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init - 0.7.8-49-g9e904bb-
0ubuntu1~16.04.1

---
cloud-init (0.7.8-49-g9e904bb-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * debian/cloud-init.postinst: update /etc/fstab on Azure to fix
future resize operations. (LP: #1611074)
  * New upstream snapshot.
- Add activate_datasource, for datasource specific code paths.
  (LP: #1611074)
- systemd: cloud-init-local use RequiresMountsFor=/var/lib/cloud
  (LP: #1642062)

cloud-init (0.7.8-47-gb6561a1-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/cloud-init.templates: enable DigitalOcean by default [Ben Howard]
  * New upstream snapshot.
- systemd/cloud-init-local.service:
  + replace 'Wants' and 'After' on local-fs.target with more granular
After=systemd-remount-fs.service and RequiresMountsFor=/var/lib
and Before=sysinit.target.
This is done run sufficiently early enough to update /etc/fstab.
(LP: #1611074)
  + add Before=NetworkManager.service so that cloud-init can render
NetworkManager network config before it would apply them.
- systemd/cloud-init.service:
  + add Before=sysinit.target and DefaultDependencies=no (LP: #1611074)
  + drop Requires=networking.service to work where networking.service is
not needed.
  + add Conflicts=shutdown.target
  + drop unnecessary Wants=local-fs.target
- net: support reading ipv6 dhcp config from initramfs [LaMont Jones]
  (LP: #1621615)
- dmidecode: Allow dmidecode to be used on aarch64, and only attempt
  usage on x86, x86_64, and aarch64. [Robert Schweikert]
- disk-config: udev settle after partitioning in gpt format.
  (LP: #1626243)
- Add support for snap create-user on Ubuntu Core images. [Ryan Harper]
  (LP: #1619393)
- Fix sshd restarts for rhel distros. [Jim Gorz]
- Move user/group functions to new ug_util file [Joshua Harlow]
- update Gentoo initscripts to run in the correct order [Matthew Thode]
- MAAS: improve the debugging tool in datasource to consider
  config provided on kernel cmdline.
- lxd: Update network config for LXD 2.3 [Stéphane Graber] (LP: #1640556)
- Decode unicode types in decode_binary [Robert Schweikert]
- Allow ephemeral drive to be unpartitioned [Paul Meyer]
- subp: add 'update_env' argument which allows for more easily adding
  environment variables to a subprocess call.
- Adjust mounts and disk configuration for systemd. (LP: #1611074)
- DataSources:
  + Ec2: protect against non-dictionary in block-device-mapping.
  + AliYun: Add new datasource for Ali-Cloud ECS, that is
available but not enabled by default [kaihuan.pkh]
  + DigitalOcean: use meta-data for network configuration and
enable data source by default. [Ben Howard]
  + OpenNebula: replace parsing of 'ip' command with similar function
available in cloudinit.net.  This fixed unit tests when running
in environment with no networking.
- doc changes:
  + Add documentation on stages of boot.
  + make the RST files consistently formated and other improvements.
  + fixed example to not overwrite /etc/hosts [Chris Glass]
  + fix spelling / typos in ca_certs and scripts_vendor.
  + improve HACKING.rst file
  + Add documentation for logging features. [Wesley Wiedenmeier]
  + Improve module documentation and doc cleanup. [Wesley Wiedenmeier]
- code style and unit test changes:
  + pep8: fix style errors reported by pycodestyle 2.1.0
  + pyflakes: fix issue with pyflakes 1.3 found in ubuntu zesty-proposed.
  + Add coverage dependency to bddeb to fix package build.
  + Add coverage collection to tox unit tests. [Joshua Powers]
  + do not read system /etc/cloud/cloud.cfg.d (LP: #1635350)
  + tests: silence the Cheetah UserWarning about NameMapper C version.
  + Fix python2.6 things found running in centos 6.

 -- Scott Moser   Fri, 18 Nov 2016 16:51:54 -0500

** Changed in: cloud-init (Ubuntu Xenial)
   Status: Fix Committed => 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/1619393

Title:
  cloud-init useradd/groupadd fails on ubuntu-core-16 with readonly
  /etc/passwd

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact] 
  When running under ubuntu-core 16 images, /etc/passwd is read-only.

  If my user-data includes any non-default username, creation fails due to
  the read-only nature of the image.

  This is addressed by useradd/groupadd including a command line flag, 
--extrausers
  which instructs the command to look for a different user/group database in
  

[Yahoo-eng-team] [Bug 1621615] Re: network not configured when ipv6 netbooted into cloud-init

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init - 0.7.8-49-g9e904bb-
0ubuntu1~16.04.1

---
cloud-init (0.7.8-49-g9e904bb-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * debian/cloud-init.postinst: update /etc/fstab on Azure to fix
future resize operations. (LP: #1611074)
  * New upstream snapshot.
- Add activate_datasource, for datasource specific code paths.
  (LP: #1611074)
- systemd: cloud-init-local use RequiresMountsFor=/var/lib/cloud
  (LP: #1642062)

cloud-init (0.7.8-47-gb6561a1-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/cloud-init.templates: enable DigitalOcean by default [Ben Howard]
  * New upstream snapshot.
- systemd/cloud-init-local.service:
  + replace 'Wants' and 'After' on local-fs.target with more granular
After=systemd-remount-fs.service and RequiresMountsFor=/var/lib
and Before=sysinit.target.
This is done run sufficiently early enough to update /etc/fstab.
(LP: #1611074)
  + add Before=NetworkManager.service so that cloud-init can render
NetworkManager network config before it would apply them.
- systemd/cloud-init.service:
  + add Before=sysinit.target and DefaultDependencies=no (LP: #1611074)
  + drop Requires=networking.service to work where networking.service is
not needed.
  + add Conflicts=shutdown.target
  + drop unnecessary Wants=local-fs.target
- net: support reading ipv6 dhcp config from initramfs [LaMont Jones]
  (LP: #1621615)
- dmidecode: Allow dmidecode to be used on aarch64, and only attempt
  usage on x86, x86_64, and aarch64. [Robert Schweikert]
- disk-config: udev settle after partitioning in gpt format.
  (LP: #1626243)
- Add support for snap create-user on Ubuntu Core images. [Ryan Harper]
  (LP: #1619393)
- Fix sshd restarts for rhel distros. [Jim Gorz]
- Move user/group functions to new ug_util file [Joshua Harlow]
- update Gentoo initscripts to run in the correct order [Matthew Thode]
- MAAS: improve the debugging tool in datasource to consider
  config provided on kernel cmdline.
- lxd: Update network config for LXD 2.3 [Stéphane Graber] (LP: #1640556)
- Decode unicode types in decode_binary [Robert Schweikert]
- Allow ephemeral drive to be unpartitioned [Paul Meyer]
- subp: add 'update_env' argument which allows for more easily adding
  environment variables to a subprocess call.
- Adjust mounts and disk configuration for systemd. (LP: #1611074)
- DataSources:
  + Ec2: protect against non-dictionary in block-device-mapping.
  + AliYun: Add new datasource for Ali-Cloud ECS, that is
available but not enabled by default [kaihuan.pkh]
  + DigitalOcean: use meta-data for network configuration and
enable data source by default. [Ben Howard]
  + OpenNebula: replace parsing of 'ip' command with similar function
available in cloudinit.net.  This fixed unit tests when running
in environment with no networking.
- doc changes:
  + Add documentation on stages of boot.
  + make the RST files consistently formated and other improvements.
  + fixed example to not overwrite /etc/hosts [Chris Glass]
  + fix spelling / typos in ca_certs and scripts_vendor.
  + improve HACKING.rst file
  + Add documentation for logging features. [Wesley Wiedenmeier]
  + Improve module documentation and doc cleanup. [Wesley Wiedenmeier]
- code style and unit test changes:
  + pep8: fix style errors reported by pycodestyle 2.1.0
  + pyflakes: fix issue with pyflakes 1.3 found in ubuntu zesty-proposed.
  + Add coverage dependency to bddeb to fix package build.
  + Add coverage collection to tox unit tests. [Joshua Powers]
  + do not read system /etc/cloud/cloud.cfg.d (LP: #1635350)
  + tests: silence the Cheetah UserWarning about NameMapper C version.
  + Fix python2.6 things found running in centos 6.

 -- Scott Moser   Fri, 18 Nov 2016 16:51:54 -0500

** Changed in: cloud-init (Ubuntu Xenial)
   Status: Fix Committed => 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/1621615

Title:
  network not configured when ipv6 netbooted into cloud-init

Status in cloud-init:
  Fix Committed
Status in MAAS:
  In Progress
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-initramfs-tools package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-initramfs-tools source package in Xenial:
  Confirmed
Status in cloud-init source package in Yakkety:
  Confirmed
Status in cloud-initramfs-tools source package in Yakkety:
  Confirmed

Bug description:
  https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1621507 talks of
  how IPv6 netboot with iscsi root disk doesn't work, 

[Yahoo-eng-team] [Bug 1611074] Re: Reformatting of ephemeral drive fails on resize of Azure VM

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init - 0.7.8-49-g9e904bb-
0ubuntu1~16.04.1

---
cloud-init (0.7.8-49-g9e904bb-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * debian/cloud-init.postinst: update /etc/fstab on Azure to fix
future resize operations. (LP: #1611074)
  * New upstream snapshot.
- Add activate_datasource, for datasource specific code paths.
  (LP: #1611074)
- systemd: cloud-init-local use RequiresMountsFor=/var/lib/cloud
  (LP: #1642062)

cloud-init (0.7.8-47-gb6561a1-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/cloud-init.templates: enable DigitalOcean by default [Ben Howard]
  * New upstream snapshot.
- systemd/cloud-init-local.service:
  + replace 'Wants' and 'After' on local-fs.target with more granular
After=systemd-remount-fs.service and RequiresMountsFor=/var/lib
and Before=sysinit.target.
This is done run sufficiently early enough to update /etc/fstab.
(LP: #1611074)
  + add Before=NetworkManager.service so that cloud-init can render
NetworkManager network config before it would apply them.
- systemd/cloud-init.service:
  + add Before=sysinit.target and DefaultDependencies=no (LP: #1611074)
  + drop Requires=networking.service to work where networking.service is
not needed.
  + add Conflicts=shutdown.target
  + drop unnecessary Wants=local-fs.target
- net: support reading ipv6 dhcp config from initramfs [LaMont Jones]
  (LP: #1621615)
- dmidecode: Allow dmidecode to be used on aarch64, and only attempt
  usage on x86, x86_64, and aarch64. [Robert Schweikert]
- disk-config: udev settle after partitioning in gpt format.
  (LP: #1626243)
- Add support for snap create-user on Ubuntu Core images. [Ryan Harper]
  (LP: #1619393)
- Fix sshd restarts for rhel distros. [Jim Gorz]
- Move user/group functions to new ug_util file [Joshua Harlow]
- update Gentoo initscripts to run in the correct order [Matthew Thode]
- MAAS: improve the debugging tool in datasource to consider
  config provided on kernel cmdline.
- lxd: Update network config for LXD 2.3 [Stéphane Graber] (LP: #1640556)
- Decode unicode types in decode_binary [Robert Schweikert]
- Allow ephemeral drive to be unpartitioned [Paul Meyer]
- subp: add 'update_env' argument which allows for more easily adding
  environment variables to a subprocess call.
- Adjust mounts and disk configuration for systemd. (LP: #1611074)
- DataSources:
  + Ec2: protect against non-dictionary in block-device-mapping.
  + AliYun: Add new datasource for Ali-Cloud ECS, that is
available but not enabled by default [kaihuan.pkh]
  + DigitalOcean: use meta-data for network configuration and
enable data source by default. [Ben Howard]
  + OpenNebula: replace parsing of 'ip' command with similar function
available in cloudinit.net.  This fixed unit tests when running
in environment with no networking.
- doc changes:
  + Add documentation on stages of boot.
  + make the RST files consistently formated and other improvements.
  + fixed example to not overwrite /etc/hosts [Chris Glass]
  + fix spelling / typos in ca_certs and scripts_vendor.
  + improve HACKING.rst file
  + Add documentation for logging features. [Wesley Wiedenmeier]
  + Improve module documentation and doc cleanup. [Wesley Wiedenmeier]
- code style and unit test changes:
  + pep8: fix style errors reported by pycodestyle 2.1.0
  + pyflakes: fix issue with pyflakes 1.3 found in ubuntu zesty-proposed.
  + Add coverage dependency to bddeb to fix package build.
  + Add coverage collection to tox unit tests. [Joshua Powers]
  + do not read system /etc/cloud/cloud.cfg.d (LP: #1635350)
  + tests: silence the Cheetah UserWarning about NameMapper C version.
  + Fix python2.6 things found running in centos 6.

 -- Scott Moser   Fri, 18 Nov 2016 16:51:54 -0500

** Changed in: cloud-init (Ubuntu Xenial)
   Status: Fix Committed => 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/1611074

Title:
  Reformatting of ephemeral drive fails on resize of Azure VM

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  In some cases, cloud-init writes entries to /etc/fstab, and on azure it will
  even format a disk for mounting and then write the entry for that 'ephemeral'
  disk there.

  A supported operation on Azure is to "resize" the system.  When you do this
  the system is shut down, resized (given larger/faster disks and more CPU) and
  then brought back up.  In that process, the 

[Yahoo-eng-team] [Bug 1626243] Re: Cloud-init fails to write ext4 filesystem to Azure Ephemeral Drive

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init - 0.7.8-49-g9e904bb-
0ubuntu1~16.04.1

---
cloud-init (0.7.8-49-g9e904bb-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * debian/cloud-init.postinst: update /etc/fstab on Azure to fix
future resize operations. (LP: #1611074)
  * New upstream snapshot.
- Add activate_datasource, for datasource specific code paths.
  (LP: #1611074)
- systemd: cloud-init-local use RequiresMountsFor=/var/lib/cloud
  (LP: #1642062)

cloud-init (0.7.8-47-gb6561a1-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/cloud-init.templates: enable DigitalOcean by default [Ben Howard]
  * New upstream snapshot.
- systemd/cloud-init-local.service:
  + replace 'Wants' and 'After' on local-fs.target with more granular
After=systemd-remount-fs.service and RequiresMountsFor=/var/lib
and Before=sysinit.target.
This is done run sufficiently early enough to update /etc/fstab.
(LP: #1611074)
  + add Before=NetworkManager.service so that cloud-init can render
NetworkManager network config before it would apply them.
- systemd/cloud-init.service:
  + add Before=sysinit.target and DefaultDependencies=no (LP: #1611074)
  + drop Requires=networking.service to work where networking.service is
not needed.
  + add Conflicts=shutdown.target
  + drop unnecessary Wants=local-fs.target
- net: support reading ipv6 dhcp config from initramfs [LaMont Jones]
  (LP: #1621615)
- dmidecode: Allow dmidecode to be used on aarch64, and only attempt
  usage on x86, x86_64, and aarch64. [Robert Schweikert]
- disk-config: udev settle after partitioning in gpt format.
  (LP: #1626243)
- Add support for snap create-user on Ubuntu Core images. [Ryan Harper]
  (LP: #1619393)
- Fix sshd restarts for rhel distros. [Jim Gorz]
- Move user/group functions to new ug_util file [Joshua Harlow]
- update Gentoo initscripts to run in the correct order [Matthew Thode]
- MAAS: improve the debugging tool in datasource to consider
  config provided on kernel cmdline.
- lxd: Update network config for LXD 2.3 [Stéphane Graber] (LP: #1640556)
- Decode unicode types in decode_binary [Robert Schweikert]
- Allow ephemeral drive to be unpartitioned [Paul Meyer]
- subp: add 'update_env' argument which allows for more easily adding
  environment variables to a subprocess call.
- Adjust mounts and disk configuration for systemd. (LP: #1611074)
- DataSources:
  + Ec2: protect against non-dictionary in block-device-mapping.
  + AliYun: Add new datasource for Ali-Cloud ECS, that is
available but not enabled by default [kaihuan.pkh]
  + DigitalOcean: use meta-data for network configuration and
enable data source by default. [Ben Howard]
  + OpenNebula: replace parsing of 'ip' command with similar function
available in cloudinit.net.  This fixed unit tests when running
in environment with no networking.
- doc changes:
  + Add documentation on stages of boot.
  + make the RST files consistently formated and other improvements.
  + fixed example to not overwrite /etc/hosts [Chris Glass]
  + fix spelling / typos in ca_certs and scripts_vendor.
  + improve HACKING.rst file
  + Add documentation for logging features. [Wesley Wiedenmeier]
  + Improve module documentation and doc cleanup. [Wesley Wiedenmeier]
- code style and unit test changes:
  + pep8: fix style errors reported by pycodestyle 2.1.0
  + pyflakes: fix issue with pyflakes 1.3 found in ubuntu zesty-proposed.
  + Add coverage dependency to bddeb to fix package build.
  + Add coverage collection to tox unit tests. [Joshua Powers]
  + do not read system /etc/cloud/cloud.cfg.d (LP: #1635350)
  + tests: silence the Cheetah UserWarning about NameMapper C version.
  + Fix python2.6 things found running in centos 6.

 -- Scott Moser   Fri, 18 Nov 2016 16:51:54 -0500

** Changed in: cloud-init (Ubuntu Xenial)
   Status: Fix Committed => 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/1626243

Title:
  Cloud-init fails to write ext4 filesystem to Azure Ephemeral Drive

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  Confirmed
Status in cloud-init source package in Zesty:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  There is a race condition that occurs when cloud-init tries to partition a
  block device (/dev/sdb) and then put a filesystem on a partition on it.  It is
  possible that cloud-init tries to run mkfs on /dev/sdb1 after partitioning the
  device /dev/sdb 

[Yahoo-eng-team] [Bug 1644519] Re: Mechanism driver's create_subnet_(pre/post)commit functions when called by ML2 plugin doesn't have the correct MTU value in context.network.current

[OpenStack Infra]

Reviewed:  https://review.openstack.org/401995
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=9660c2f0b362705e5e7b49dc9a6d0495a1141fbf
Submitter: Jenkins
Branch:master

commit 9660c2f0b362705e5e7b49dc9a6d0495a1141fbf
Author: Numan Siddique 
Date:   Thu Nov 24 17:16:51 2016 +0530

Update network dict with segment and mtu info in _create_subnet_db

Without this, the mech driver create_submit_(pre/post)commit functions
when called will not have segment and network mtu information in
context.network.current.

Change-Id: I3214a19e2374221b211ac7ab9b98842a1bdfc4a7
Closes-bug: #1644519


** Changed in: neutron
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1644519

Title:
  Mechanism driver's create_subnet_(pre/post)commit functions when
  called by ML2 plugin doesn't have the correct MTU value in
  context.network.current

Status in neutron:
  Fix Released

Bug description:
  the mtu value present in context.network.current doesn't take the
  tunnel encapsulation value into account.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1644519/+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 1635350] Re: unit tests fail as non-root on maas deployed system

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init - 0.7.8-49-g9e904bb-
0ubuntu1~16.04.1

---
cloud-init (0.7.8-49-g9e904bb-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * debian/cloud-init.postinst: update /etc/fstab on Azure to fix
future resize operations. (LP: #1611074)
  * New upstream snapshot.
- Add activate_datasource, for datasource specific code paths.
  (LP: #1611074)
- systemd: cloud-init-local use RequiresMountsFor=/var/lib/cloud
  (LP: #1642062)

cloud-init (0.7.8-47-gb6561a1-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/cloud-init.templates: enable DigitalOcean by default [Ben Howard]
  * New upstream snapshot.
- systemd/cloud-init-local.service:
  + replace 'Wants' and 'After' on local-fs.target with more granular
After=systemd-remount-fs.service and RequiresMountsFor=/var/lib
and Before=sysinit.target.
This is done run sufficiently early enough to update /etc/fstab.
(LP: #1611074)
  + add Before=NetworkManager.service so that cloud-init can render
NetworkManager network config before it would apply them.
- systemd/cloud-init.service:
  + add Before=sysinit.target and DefaultDependencies=no (LP: #1611074)
  + drop Requires=networking.service to work where networking.service is
not needed.
  + add Conflicts=shutdown.target
  + drop unnecessary Wants=local-fs.target
- net: support reading ipv6 dhcp config from initramfs [LaMont Jones]
  (LP: #1621615)
- dmidecode: Allow dmidecode to be used on aarch64, and only attempt
  usage on x86, x86_64, and aarch64. [Robert Schweikert]
- disk-config: udev settle after partitioning in gpt format.
  (LP: #1626243)
- Add support for snap create-user on Ubuntu Core images. [Ryan Harper]
  (LP: #1619393)
- Fix sshd restarts for rhel distros. [Jim Gorz]
- Move user/group functions to new ug_util file [Joshua Harlow]
- update Gentoo initscripts to run in the correct order [Matthew Thode]
- MAAS: improve the debugging tool in datasource to consider
  config provided on kernel cmdline.
- lxd: Update network config for LXD 2.3 [Stéphane Graber] (LP: #1640556)
- Decode unicode types in decode_binary [Robert Schweikert]
- Allow ephemeral drive to be unpartitioned [Paul Meyer]
- subp: add 'update_env' argument which allows for more easily adding
  environment variables to a subprocess call.
- Adjust mounts and disk configuration for systemd. (LP: #1611074)
- DataSources:
  + Ec2: protect against non-dictionary in block-device-mapping.
  + AliYun: Add new datasource for Ali-Cloud ECS, that is
available but not enabled by default [kaihuan.pkh]
  + DigitalOcean: use meta-data for network configuration and
enable data source by default. [Ben Howard]
  + OpenNebula: replace parsing of 'ip' command with similar function
available in cloudinit.net.  This fixed unit tests when running
in environment with no networking.
- doc changes:
  + Add documentation on stages of boot.
  + make the RST files consistently formated and other improvements.
  + fixed example to not overwrite /etc/hosts [Chris Glass]
  + fix spelling / typos in ca_certs and scripts_vendor.
  + improve HACKING.rst file
  + Add documentation for logging features. [Wesley Wiedenmeier]
  + Improve module documentation and doc cleanup. [Wesley Wiedenmeier]
- code style and unit test changes:
  + pep8: fix style errors reported by pycodestyle 2.1.0
  + pyflakes: fix issue with pyflakes 1.3 found in ubuntu zesty-proposed.
  + Add coverage dependency to bddeb to fix package build.
  + Add coverage collection to tox unit tests. [Joshua Powers]
  + do not read system /etc/cloud/cloud.cfg.d (LP: #1635350)
  + tests: silence the Cheetah UserWarning about NameMapper C version.
  + Fix python2.6 things found running in centos 6.

 -- Scott Moser   Fri, 18 Nov 2016 16:51:54 -0500

** Changed in: cloud-init (Ubuntu Xenial)
   Status: Fix Committed => 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/1635350

Title:
  unit tests fail as non-root on maas deployed system

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  Confirmed

Bug description:
  === Begin SRU Template ===
  [Impact]
  Running cloud-init's unit test cases on a system deployed by MAAS would
  fail.  The reason is that the non-root user would not be able to read
  files with MAAS node credentials in /etc/cloud/cloud.cfg.d

  We want this change SRU so that an attempt to build and run tests on a
  system deployed by maas will work rather than fail 

[Yahoo-eng-team] [Bug 1640556] Re: support network configuration for lxd 2.3

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init - 0.7.8-49-g9e904bb-
0ubuntu1~16.04.1

---
cloud-init (0.7.8-49-g9e904bb-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * debian/cloud-init.postinst: update /etc/fstab on Azure to fix
future resize operations. (LP: #1611074)
  * New upstream snapshot.
- Add activate_datasource, for datasource specific code paths.
  (LP: #1611074)
- systemd: cloud-init-local use RequiresMountsFor=/var/lib/cloud
  (LP: #1642062)

cloud-init (0.7.8-47-gb6561a1-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/cloud-init.templates: enable DigitalOcean by default [Ben Howard]
  * New upstream snapshot.
- systemd/cloud-init-local.service:
  + replace 'Wants' and 'After' on local-fs.target with more granular
After=systemd-remount-fs.service and RequiresMountsFor=/var/lib
and Before=sysinit.target.
This is done run sufficiently early enough to update /etc/fstab.
(LP: #1611074)
  + add Before=NetworkManager.service so that cloud-init can render
NetworkManager network config before it would apply them.
- systemd/cloud-init.service:
  + add Before=sysinit.target and DefaultDependencies=no (LP: #1611074)
  + drop Requires=networking.service to work where networking.service is
not needed.
  + add Conflicts=shutdown.target
  + drop unnecessary Wants=local-fs.target
- net: support reading ipv6 dhcp config from initramfs [LaMont Jones]
  (LP: #1621615)
- dmidecode: Allow dmidecode to be used on aarch64, and only attempt
  usage on x86, x86_64, and aarch64. [Robert Schweikert]
- disk-config: udev settle after partitioning in gpt format.
  (LP: #1626243)
- Add support for snap create-user on Ubuntu Core images. [Ryan Harper]
  (LP: #1619393)
- Fix sshd restarts for rhel distros. [Jim Gorz]
- Move user/group functions to new ug_util file [Joshua Harlow]
- update Gentoo initscripts to run in the correct order [Matthew Thode]
- MAAS: improve the debugging tool in datasource to consider
  config provided on kernel cmdline.
- lxd: Update network config for LXD 2.3 [Stéphane Graber] (LP: #1640556)
- Decode unicode types in decode_binary [Robert Schweikert]
- Allow ephemeral drive to be unpartitioned [Paul Meyer]
- subp: add 'update_env' argument which allows for more easily adding
  environment variables to a subprocess call.
- Adjust mounts and disk configuration for systemd. (LP: #1611074)
- DataSources:
  + Ec2: protect against non-dictionary in block-device-mapping.
  + AliYun: Add new datasource for Ali-Cloud ECS, that is
available but not enabled by default [kaihuan.pkh]
  + DigitalOcean: use meta-data for network configuration and
enable data source by default. [Ben Howard]
  + OpenNebula: replace parsing of 'ip' command with similar function
available in cloudinit.net.  This fixed unit tests when running
in environment with no networking.
- doc changes:
  + Add documentation on stages of boot.
  + make the RST files consistently formated and other improvements.
  + fixed example to not overwrite /etc/hosts [Chris Glass]
  + fix spelling / typos in ca_certs and scripts_vendor.
  + improve HACKING.rst file
  + Add documentation for logging features. [Wesley Wiedenmeier]
  + Improve module documentation and doc cleanup. [Wesley Wiedenmeier]
- code style and unit test changes:
  + pep8: fix style errors reported by pycodestyle 2.1.0
  + pyflakes: fix issue with pyflakes 1.3 found in ubuntu zesty-proposed.
  + Add coverage dependency to bddeb to fix package build.
  + Add coverage collection to tox unit tests. [Joshua Powers]
  + do not read system /etc/cloud/cloud.cfg.d (LP: #1635350)
  + tests: silence the Cheetah UserWarning about NameMapper C version.
  + Fix python2.6 things found running in centos 6.

 -- Scott Moser   Fri, 18 Nov 2016 16:51:54 -0500

** Changed in: cloud-init (Ubuntu Xenial)
   Status: Fix Committed => 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/1640556

Title:
  support network configuration for lxd 2.3

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact] 
  Support for lxd configuration of networking does not work with lxd 2.3+ as
  the current path for configuration in cloud-init uses debconf but newer
  lxd does not support configuration that way.

  Prior to LXD 2.3, the bridge configuration was done through distro
  packaging.  With 2.3 and higher, this is now done inside LXD itself, so we
  need to use "lxc network" with 2.3 and higher.

  All 

[Yahoo-eng-team] [Bug 1605793] Re: Calculate MTU on every network fetch instead of on create

[OpenStack Infra]

Reviewed:  https://review.openstack.org/362822
Committed: 
https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=c153b9e3da5a6753225d4c367f33267ae19ee5ff
Submitter: Jenkins
Branch:master

commit c153b9e3da5a6753225d4c367f33267ae19ee5ff
Author: Ihar Hrachyshka 
Date:   Sat Aug 27 18:11:50 2016 +

neutron: MTU is now re-calculated for existing networks

With Iee4f5037bf10b73ba98464143b183aacb59c22f2 in for Newton, Neutron
will re-calculate MTU values for all existing networks on controller
restart in case MTU configuration options are touched.

Change-Id: Ic6a3466291b881ee11d6044d4f02caf33574edb8
Closes-Bug: #1605793


** Changed in: openstack-manuals
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1605793

Title:
  Calculate MTU on every network fetch instead of on create

Status in neutron:
  Incomplete
Status in openstack-manuals:
  Fix Released

Bug description:
  https://review.openstack.org/336805
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.
  Your project "openstack/neutron" is set up so that we directly report the 
documentation bugs against it. If this needs changing, the docimpact-group 
option needs to be added for the project. You can ask the OpenStack infra team 
(#openstack-infra on freenode) for help if you need to.

  commit a984f9554cdcbe93c840a1d8f5c04302e9331e79
  Author: Ihar Hrachyshka 
  Date:   Sat Jul 2 17:30:21 2016 +0200

  Calculate MTU on every network fetch instead of on create
  
  Today, existing networks may not reflect MTU configured for
  neutron-server, if they were created when neutron-server was using
  different MTU setup for its infrastructure, or when it was using bad
  default values for network MTUs (specifically, before Mitaka, all networks
  were getting MTU = 0 by default, disabling both advertisement and data
  path MTU size enforcement).
  
  This patch stops persisting MTU in the database on network create and
  instead calculate it on every network resource fetch.
  
  DocImpact Now changes to MTU configuration options immediately affect
existing network MTUs, not just new networks.
  
  UpgradeImpact Existing networks with invalid MTU persisted in database
may change their MTU values to reflect configuration.
  
  Change-Id: Iee4f5037bf10b73ba98464143b183aacb59c22f2
  Closes-Bug: #1556182

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1605793/+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 1591827] Re: Scsi device can't be recognized in Guest in aarch64

[OpenStack Infra]

Reviewed:  https://review.openstack.org/329403
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=d442c1aa31b0a0cbfa0d057e8b6574002ee2e2fc
Submitter: Jenkins
Branch:master

commit d442c1aa31b0a0cbfa0d057e8b6574002ee2e2fc
Author: KevinZhao 
Date:   Mon Jun 13 02:14:51 2016 +

libvirt: Delete the lase_device of find_disk_dev_for_disk_bus

Delete the last_device parameters of find_disk_dev_for_disk_bus.
Just pick the first available letter on the bus as the device,
instead of hardcoding on the last device for config drive. Also
tweak the test case for this.

Closes-bug: #1591827

Change-Id: I6343d7ab6f1b0aa58f29805e24db7e2c61d1409e
Signed-off-by: Kevin Zhao 


** Changed in: nova
   Status: In Progress => Fix Released

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

Title:
  Scsi device can't be recognized in Guest in aarch64

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Description
  ===
  Using nova to create an instance in Aarch64,the disk.config is the 'cdrom' 
and has the type of 'scsi'.After instance creation ,log into the instance and 
can't see the cdrom device.

  Steps to reproduce
  ==
  1.Using devstack to deploy openstack. Using default local.conf.

  2.Upload the aarch64 image with glance.
  $ source ~/devstack/openrc admin admin
  $ glance image-create --name image-arm64.img --disk-format qcow2 
--container-format bare --visibility public --file 
images/image-arm64-wily.qcow2 --progress
  $ glance image-create --name image-arm64.vmlinuz --disk-format aki 
--container-format aki --visibility public --file 
images/image-arm64-wily.vmlinuz --progress
  $ glance image-create --name image-arm64.initrd --disk-format ari 
--container-format ari --visibility public --file 
images/image-arm64-wily.initrd --progress
  $ IMAGE_UUID=$(glance image-list | grep image-arm64.img | awk '{ print $2 }')
  $ IMAGE_KERNEL_UUID=$(glance image-list | grep image-arm64.vmlinuz | awk '{ 
print $2 }')
  $ IMAGE_INITRD_UUID=$(glance image-list | grep image-arm64.initrd | awk '{ 
print $2 }')
  $ glance image-update --kernel-id ${IMAGE_KERNEL_UUID} --ramdisk-id 
${IMAGE_INITRD_UUID} ${IMAGE_UUID}
  3.Set the scsi model:
  $ glance image-update --property hw_disk_bus --property 
hw_scsi_model=virtio-scsi ${IMAGE_UUID}

  4.nova add keypair
  $ nova keypair-add default --pub-key ~/.ssh/id_rsa.pub

  5.Launch the instance:
  $ image=$(nova image-list | egrep "image-arm64.img"'[^-]' | awk '{ print $2 
}')
  $ nova boot --flavor m1.small--image ${image} --key-name default test-arm64

  6.After creation,use ssh to login into the instance.In the guest:
  $ ls -l /dev
  The we can see that cdrom doesn't exist.

  Expected result
  ===
  After spawningn the instance, login into the guest :
  $ ls -l /dev
  We can see the cdrom is here.

  Actual result
  =
  The xml file of the disk.config is generated by nova ,but can't work.

  Environment
  ===
  1. Exact version of OpenStack you are running. See the following
    list for all releases: http://docs.openstack.org/releases/
     Nova development, commit code: 279f1a9bf65c4b904e01d26f0619a62ed99fc4d3

  2. Which hypervisor did you use?
  Libvirt+KVM
  $ kvm --version
  QEMU emulator version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.1), Copyright 
(c) 2003-2008 Fabrice Bellard
  $ libvirtd --version
  libvirtd (libvirt) 1.3.1

  2. Which storage type did you use?
     In the host file system,all in one physics machine.
  stack@u202154:/opt/stack/nova$ df -hl
  Filesystem Size Used Avail Use% Mounted on
  udev 7.8G 0 7.8G 0% /dev
  tmpfs 1.6G 61M 1.6G 4% /run
  /dev/sda2 917G 41G 830G 5% /
  tmpfs 7.9G 0 7.9G 0% /dev/shm
  tmpfs 5.0M 0 5.0M 0% /run/lock
  tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
  /dev/sda1 511M 888K 511M 1% /boot/efi
  cgmfs 100K 0 100K 0% /run/cgmanager/fs
  tmpfs 1.6G 0 1.6G 0% /run/user/1002
  tmpfs 1.6G 0 1.6G 0% /run/user/1000
  tmpfs 1.6G 0 1.6G 0% /run/user/0

  3. Which networking type did you use?
     nova-network

  4. Environment information:
     Architecture : AARCH64
     OS: Ubuntu 16.04

  Detailed log info is in the accessory.
  The guest xml is also in the log info.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1591827/+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 1644697] [NEW] run_tests.sh should really use upper-constraints

[Richard Jones]

Public bug reported:

We're starting to see lots of compatibility issues that will be solved
if we have run_tests.sh support upper-constraints. This will not stop us
from removing run_tests.sh in Queens, but will allow us avoid issues
along the way and to test the changes now and backport to stable.

** Affects: horizon
 Importance: High
 Status: Triaged


** Tags: mitaka-backport-potential newton-backport-potential

** Changed in: horizon
   Status: New => Triaged

** Changed in: horizon
   Importance: Undecided => High

** Changed in: horizon
Milestone: None => ocata-2

** Tags added: newton-backport-potential

** Tags added: mitaka-backport-potential

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1644697

Title:
  run_tests.sh should really use upper-constraints

Status in OpenStack Dashboard (Horizon):
  Triaged

Bug description:
  We're starting to see lots of compatibility issues that will be solved
  if we have run_tests.sh support upper-constraints. This will not stop
  us from removing run_tests.sh in Queens, but will allow us avoid
  issues along the way and to test the changes now and backport to
  stable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1644697/+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 1644700] [NEW] DHCPAgentOVSTestCase.test_create_subnet_with_dhcp fails

[IWAMOTO Toshihiro]

Public bug reported:

neutron.tests.functional.agent.test_dhcp_agent.DHCPAgentOVSTestCase.test_create_subnet_with_dhcp
sometimes fails with:

Traceback (most recent call last):
  File "neutron/tests/base.py", line 126, in func
return f(self, *args, **kwargs)
  File "neutron/tests/functional/agent/test_dhcp_agent.py", line 261, in 
test_create_subnet_with_dhcp
self.assert_dhcp_resources(network, dhcp_enabled)
  File "neutron/tests/functional/agent/test_dhcp_agent.py", line 162, in 
assert_dhcp_resources
self.assertEqual(dhcp_enabled, ovs.port_exists(iface_name))
  File 
"/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/testtools/testcase.py",
 line 411, in assertEqual
self.assertThat(observed, matcher, message)
  File 
"/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/testtools/testcase.py",
 line 498, in assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: True != False


http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22test_create_subnet_with_dhcp%5C%22

>From 
>http://logs.openstack.org/87/386687/8/check/gate-neutron-dsvm-functional-ubuntu-trusty/3c5b121/logs/dsvm-functional-logs/neutron.tests.functional.agent.test_dhcp_agent.DHCPAgentOVSTestCase.test_create_subnet_with_dhcp.txt.gz
> ,
AddBridgeCommand is failing with an ovsdb transaction timeout.

** Affects: neutron
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1644700

Title:
  DHCPAgentOVSTestCase.test_create_subnet_with_dhcp fails

Status in neutron:
  New

Bug description:
  
neutron.tests.functional.agent.test_dhcp_agent.DHCPAgentOVSTestCase.test_create_subnet_with_dhcp
  sometimes fails with:

  Traceback (most recent call last):
File "neutron/tests/base.py", line 126, in func
  return f(self, *args, **kwargs)
File "neutron/tests/functional/agent/test_dhcp_agent.py", line 261, in 
test_create_subnet_with_dhcp
  self.assert_dhcp_resources(network, dhcp_enabled)
File "neutron/tests/functional/agent/test_dhcp_agent.py", line 162, in 
assert_dhcp_resources
  self.assertEqual(dhcp_enabled, ovs.port_exists(iface_name))
File 
"/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/testtools/testcase.py",
 line 411, in assertEqual
  self.assertThat(observed, matcher, message)
File 
"/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/testtools/testcase.py",
 line 498, in assertThat
  raise mismatch_error
  testtools.matchers._impl.MismatchError: True != False

  
  
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22test_create_subnet_with_dhcp%5C%22

  From 
http://logs.openstack.org/87/386687/8/check/gate-neutron-dsvm-functional-ubuntu-trusty/3c5b121/logs/dsvm-functional-logs/neutron.tests.functional.agent.test_dhcp_agent.DHCPAgentOVSTestCase.test_create_subnet_with_dhcp.txt.gz
 ,
  AddBridgeCommand is failing with an ovsdb transaction timeout.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1644700/+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 1644385] Re: Stable mitaka is currently quite broken

[Richard Jones]

*** This bug is a duplicate of bug 1640620 ***
https://bugs.launchpad.net/bugs/1640620

** This bug has been marked a duplicate of bug 1640620
   Horizon installation docs need to include upper-constraints.txt

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1644385

Title:
  Stable mitaka is currently quite broken

Status in OpenStack Dashboard (Horizon):
  Triaged

Bug description:
  Due to recent xstatic library updates and the lack of support for
  upper-constraints pinning, the Mitaka stable branch is currently quite
  broken.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1644385/+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 1644677] [NEW] example devstack local.conf is broken for stable branches

[Richard Jones]

Public bug reported:

The local.conf example needs to mention using the stable/ tag or
it produces broken devstacks.

** Affects: horizon
 Importance: Medium
 Assignee: Richard Jones (r1chardj0n3s)
 Status: Triaged


** Tags: newton-backport-potential

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1644677

Title:
  example devstack local.conf is broken for stable branches

Status in OpenStack Dashboard (Horizon):
  Triaged

Bug description:
  The local.conf example needs to mention using the stable/ tag
  or it produces broken devstacks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1644677/+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 1644708] [NEW] Unrecognized parameters are not blocked in 'fixed_ips' of Port

[Kengo Hobo]

Public bug reported:

No errors are returned even though there are unrecognized parameter in
Dict for 'fixed_ips'.

Environment
---
master

Expected behavior
-
It is hard to notice that the request is wrong.
Thus, it should be returned 400 error so that user can understand the request 
is wrong.

How to reproduce
-
Create/Update port with fixed_ips parameter that is contained unrecognized 
parameter.
"a" is unrecognized parameter in case below. 

ubuntu@neutron-ml2:/opt/stack/neutron$ curl -i -X PUT -H "X-Auth-Token: $TOKEN" 
http://172.16.1.29:9696/v2.0/ports/42bff786-a7fd-4631-8416-83052d078389 -d 
'{"port": {"fixed_ips":[{"a":"a", "ip_address":"192.168.0.15"}]}}'
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 906
X-Openstack-Request-Id: req-f6b46c50-6f98-470c-a3ea-17eacf765603
Date: Fri, 25 Nov 2016 05:40:59 GMT

{"port": {"allowed_address_pairs": [{"ip_address": "1.1.1.1",
"mac_address": "aa:aa:aa:aa:aa:aa"}], "extra_dhcp_opts": [],
"updated_at": "2016-11-25T05:40:59Z", "device_owner": "",
"revision_number": 9, "binding:profile": {"\u3042": "a"},
"port_security_enabled": true, "fixed_ips": [{"subnet_id": "b89324b7
-4f6c-47b0-a874-601a345a11e2", "ip_address": "192.168.0.15"}], "id":
"42bff786-a7fd-4631-8416-83052d078389", "security_groups":
["e2238dd0-01b2-44a2-a9b3-08e8d2163de5"], "binding:vif_details": {},
"binding:vif_type": "unbound", "mac_address": "fa:16:3e:2d:95:8d",
"project_id": "d713c7d4c02541d8b239d6d9761768e5", "status": "DOWN",
"binding:host_id": "", "description": "", "device_id": "", "name": "",
"admin_state_up": true, "network_id": "af5370f1-a37d-4b36-900e-
4aa6aa939fef", "tenant_id": "d713c7d4c02541d8b239d6d9761768e5",
"created_at": "2016-11-17T09:06:35Z", "binding:vnic_type": "normal"}}

** Affects: neutron
 Importance: Undecided
 Assignee: Kengo Hobo (hobo-kengo)
 Status: New


** Tags: lib

** Changed in: neutron
 Assignee: (unassigned) => Kengo Hobo (hobo-kengo)

** Tags added: lib

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1644708

Title:
  Unrecognized parameters are not blocked in 'fixed_ips' of Port

Status in neutron:
  New

Bug description:
  No errors are returned even though there are unrecognized parameter in
  Dict for 'fixed_ips'.

  Environment
  ---
  master

  Expected behavior
  -
  It is hard to notice that the request is wrong.
  Thus, it should be returned 400 error so that user can understand the request 
is wrong.

  How to reproduce
  -
  Create/Update port with fixed_ips parameter that is contained unrecognized 
parameter.
  "a" is unrecognized parameter in case below. 

  ubuntu@neutron-ml2:/opt/stack/neutron$ curl -i -X PUT -H "X-Auth-Token: 
$TOKEN" http://172.16.1.29:9696/v2.0/ports/42bff786-a7fd-4631-8416-83052d078389 
-d '{"port": {"fixed_ips":[{"a":"a", "ip_address":"192.168.0.15"}]}}'
  HTTP/1.1 200 OK
  Content-Type: application/json
  Content-Length: 906
  X-Openstack-Request-Id: req-f6b46c50-6f98-470c-a3ea-17eacf765603
  Date: Fri, 25 Nov 2016 05:40:59 GMT

  {"port": {"allowed_address_pairs": [{"ip_address": "1.1.1.1",
  "mac_address": "aa:aa:aa:aa:aa:aa"}], "extra_dhcp_opts": [],
  "updated_at": "2016-11-25T05:40:59Z", "device_owner": "",
  "revision_number": 9, "binding:profile": {"\u3042": "a"},
  "port_security_enabled": true, "fixed_ips": [{"subnet_id": "b89324b7
  -4f6c-47b0-a874-601a345a11e2", "ip_address": "192.168.0.15"}], "id":
  "42bff786-a7fd-4631-8416-83052d078389", "security_groups":
  ["e2238dd0-01b2-44a2-a9b3-08e8d2163de5"], "binding:vif_details": {},
  "binding:vif_type": "unbound", "mac_address": "fa:16:3e:2d:95:8d",
  "project_id": "d713c7d4c02541d8b239d6d9761768e5", "status": "DOWN",
  "binding:host_id": "", "description": "", "device_id": "", "name": "",
  "admin_state_up": true, "network_id": "af5370f1-a37d-4b36-900e-
  4aa6aa939fef", "tenant_id": "d713c7d4c02541d8b239d6d9761768e5",
  "created_at": "2016-11-17T09:06:35Z", "binding:vnic_type": "normal"}}

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1644708/+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 1644709] [NEW] mox errors are not being treated as test failures

[Richard Jones]

Public bug reported:

There are some mox errors in test output that should be causing test
runs to fail but are not. For example:

http://logs.openstack.org/25/222825/28/check/gate-horizon-python27
-ubuntu-xenial/15d5669/console.html#_2016-11-25_01_46_56_495148

** Affects: horizon
 Importance: High
 Assignee: Richard Jones (r1chardj0n3s)
 Status: In Progress


** Tags: newton-backport-potential

** Changed in: horizon
   Status: New => Triaged

** Changed in: horizon
   Importance: Undecided => High

** Changed in: horizon
Milestone: None => ocata-2

** Tags added: newton-backport-potential

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1644709

Title:
  mox errors are not being treated as test failures

Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  There are some mox errors in test output that should be causing test
  runs to fail but are not. For example:

  http://logs.openstack.org/25/222825/28/check/gate-horizon-python27
  -ubuntu-xenial/15d5669/console.html#_2016-11-25_01_46_56_495148

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1644709/+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 1644527] [NEW] dhcp server not alocating ip address in vm enviroment

[Milan]

Public bug reported:

I am installing and configuring OpenStack for the second time in VM 
environment. The first time i installed Librety and now Newton. I have three 
VMs (one controller and two compute nodes). 
Both times when i installed and configured OpenStack i get the same problem 
with the DHCP server. My instances were not getting ip address. 

I solve this problem by enabling in /etc/neutron/dhcp_agent.ini the
dhcp_broadcast_reply = true .

Previously the DHCP reply was not broadcast and my machines were not
getting the IP address

** Affects: neutron
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1644527

Title:
  dhcp server not alocating ip address in vm enviroment

Status in neutron:
  New

Bug description:
  I am installing and configuring OpenStack for the second time in VM 
environment. The first time i installed Librety and now Newton. I have three 
VMs (one controller and two compute nodes). 
  Both times when i installed and configured OpenStack i get the same problem 
with the DHCP server. My instances were not getting ip address. 

  I solve this problem by enabling in /etc/neutron/dhcp_agent.ini the
  dhcp_broadcast_reply = true .

  Previously the DHCP reply was not broadcast and my machines were not
  getting the IP address

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1644527/+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 1614506] Re: Volume doesn't gets deleted upon instance termination

[Claudiu Belu]

Hello,

Typically, volumes persist even after the instance they were attached to
is destroyed. I was not aware of delete_on_termination flag. I did some
digging around, and I've noticed that this flag is only mentioned by the
block_device_mapping_v1 api, but not the block_device_mapping_v2, which
you are using [1]. Can you try passing that flag in a
block_device_mapping_v1 request?

Finally, the nova-compute services do not delete volumes, something like
this would be done by the nova-api / nova-conductor services.

[1] http://docs.openstack.org/developer/nova/block_device_mapping.html

Best regards,

Claudiu Belu

** Project changed: compute-hyperv => nova

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

Title:
  Volume doesn't gets deleted upon instance termination

Status in OpenStack Compute (nova):
  New

Bug description:
  Hello!

  I have tried to create OpenStack compute instances from an image via
  the following API requests (according to the API guide
  ):

  ---8<---
  {
  "server" : {
  "name" : "test",
  "flavorRef" : "http://openstack.example.com/flavors/2;,
  "networks" : [{
  "uuid" : "1beeab54-0125-4ac0-8ac1-3614a02e399f",
  "tag": "instance-net"
  }],
  "imageRef": "61d15016-1b4f-4303-9d8a-6f8cb531a0f5",
  "block_device_mapping_v2": [{
  "uuid": "70a599e0-31e7-49b7-b260-868f441e862b",
  "source_type": "image",
  "destination_type": "volume",
  "boot_index": 0,
  "volume_size": "1",
  "tag": "disk1",
  "delete_on_termination": "true"
  }],
  "security_groups": [
  {
  "name": "default"
  }
  ]
  }
  }
  --->8---

  ---8<---
  {
  "server" : {
  "name" : "test",
  "flavorRef" : "http://openstack.example.com/flavors/2;,
  "networks" : [{
  "uuid" : "1beeab54-0125-4ac0-8ac1-3614a02e399f",
  "tag": "instance-net"
  }],
  "imageRef": "61d15016-1b4f-4303-9d8a-6f8cb531a0f5",
  "delete_on_termination": "true"
  "security_groups": [
  {
  "name": "default"
  }
  ]
  }
  }
  --->8---

  Both requests result in creation of instances, no errors present in
  the server response, but when I then remove instances, volumes stay
  there. URL where I submit requests looks as follows: https://:8774/v2/7d0f17355baf480ba2a317467cdf70fc/servers

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1614506/+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 1644535] [NEW] iptables: fail to start ovs/linuxbridge agents on missing sysctl knobs

[OpenStack Infra]

Public bug reported:

https://review.openstack.org/398817
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/neutron" is set up so that we directly report the 
documentation bugs against it. If this needs changing, the docimpact-group 
option needs to be added for the project. You can ask the OpenStack infra team 
(#openstack-infra on freenode) for help if you need to.

commit 4371a4f5cdc6559955af9158c4c28851e77914da
Author: Ihar Hrachyshka 
Date:   Thu Sep 15 21:48:10 2016 +

iptables: fail to start ovs/linuxbridge agents on missing sysctl knobs

For new kernels (3.18+), bridge module is split into two pieces: bridge
and br_netfilter. The latter provides firewall support for bridged
traffic, as well as the following sysctl knobs:

* net.bridge.bridge-nf-call-arptables
* net.bridge.bridge-nf-call-ip6tables
* net.bridge.bridge-nf-call-iptables

Before kernel 3.18, any brctl command was loading the 'bridge' module
with the knobs, so at the moment where we reached iptables setup, they
were always available.

With new 3.18+ kernels, brctl still loads 'bridge' module, but not
br_netfilter. So bridge existance no longer guarantees us knobs'
presence. If we reach _enable_netfilter_for_bridges before the new
module is loaded, then the code will fail, triggering agent resync. It
will also fail to enable bridge firewalling on systems where it's
disabled by default (examples of those systems are most if not all Red
Hat/Fedora based systems), making security groups completely
ineffective.

Systems that don't override default settings for those knobs would work
fine except for this exception in the log file and agent resync. This is
because the first attempt to add a iptables rule using 'physdev' module
(-m physdev) will trigger the kernel module loading. In theory, we could
silently swallow missing knobs, and still operate correctly. But on
second thought, it's quite fragile to rely on that implicit module
loading. In the case where we can't detect whether firewall is enabled,
it's better to fail than hope for the best.

An alternative to the proposed path could be trying
to fix broken deployment, meaning we would need to load the missing
kernel module on agent startup. It's not even clear whether we can
assume the operation would be available to us. Even with that, adding a
rootwrap filter to allow loading code in the kernel sounds quite scary.
If we would follow the path, we would also hit an issue of
distinguishing between cases of built-in kernel module vs. modular one.
A complexity that is probably beyond what Neutron should fix.

The patch introduces a sanity check that would fail on missing
configuration knobs.

DocImpact: document the new deployment requirement in operations guide
UpgradeImpact: deployers relying on agents fixing wrong sysctl defaults
   will need to make sure bridge firewalling is enabled.
   Also, the kernel module providing sysctl knobs must be
   loaded before starting the agent, otherwise it will fail
   to start.

Changes made to this backport:
   neutron/agent/linux/iptables_firewall.py
   - removed deprecation warning when setting sysctl values to 1 as
 they are planned to be removed in Ocata
   neutron/cmd/sanity/checks.py
   - Re-implemented the flow to check only for presence of sysctl
 options instead of checking the values. Kernel options are set
 in runtime thus the values don't matter.

Depends-On: Id6bfd9595f0772a63d1096ef83ebbb6cd630fafd
Change-Id: I9137ea017624ac92a05f73863b77f9ee4681bbe7
Related-Bug: #1622914
(cherry picked from commit e83a44b96a8e3cd81b7cc684ac90486b283a3507)

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: doc neutron

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1644535

Title:
  iptables: fail to start ovs/linuxbridge agents on missing sysctl
  knobs

Status in neutron:
  New

Bug description:
  https://review.openstack.org/398817
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.
  Your project "openstack/neutron" is set up so that we directly report the 
documentation bugs against it. If this needs changing, the docimpact-group 
option needs to be added for the project. You can ask the OpenStack infra team 
(#openstack-infra on freenode) for help if you need to.

  commit 4371a4f5cdc6559955af9158c4c28851e77914da
  Author: Ihar Hrachyshka 
  Date:   Thu Sep 15 21:48:10 2016 +

  iptables: fail to start ovs/linuxbridge agents on missing 

[Yahoo-eng-team] [Bug 1644534] [NEW] Get dnsmasq: bad command line options error message in neutron-dhcp-agent

[Jeffrey Zhang]

Public bug reported:

Get following error message in Kolla's gate

2016-11-23 12:06:55.376 7 DEBUG neutron.agent.linux.utils [-] Running command: 
['sudo', 'neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 
'exec', 'qdhcp-0a9e36c5-2d55-4e6c-b4ba-67fd13e7681e', 'ip', 'addr', 'show', 
'tapbe705a89-82'] create_process 
/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/agent/linux/utils.py:92
2016-11-23 12:06:55.595 7 DEBUG neutron.agent.ovsdb.native.vlog [-] [POLLIN] on 
fd 8 __log_wakeup 
/var/lib/kolla/venv/lib/python2.7/site-packages/ovs/poller.py:202
2016-11-23 12:06:55.676 7 DEBUG neutron.agent.linux.utils [-] Exit code: 0 
execute 
/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/agent/linux/utils.py:149
2016-11-23 12:06:55.677 7 DEBUG neutron.agent.linux.utils [-] Unable to access 
/var/lib/neutron/dhcp/0a9e36c5-2d55-4e6c-b4ba-67fd13e7681e/pid 
get_value_from_file 
/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/agent/linux/utils.py:216
2016-11-23 12:06:55.678 7 DEBUG neutron.agent.linux.utils [-] Running command: 
['sudo', 'neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 
'exec', 'qdhcp-0a9e36c5-2d55-4e6c-b4ba-67fd13e7681e', 'dnsmasq', '--no-hosts', 
'--no-resolv', '--strict-order', '--except-interface=lo', 
'--pid-file=/var/lib/neutron/dhcp/0a9e36c5-2d55-4e6c-b4ba-67fd13e7681e/pid', 
'--dhcp-hostsfile=/var/lib/neutron/dhcp/0a9e36c5-2d55-4e6c-b4ba-67fd13e7681e/host',
 
'--addn-hosts=/var/lib/neutron/dhcp/0a9e36c5-2d55-4e6c-b4ba-67fd13e7681e/addn_hosts',
 
'--dhcp-optsfile=/var/lib/neutron/dhcp/0a9e36c5-2d55-4e6c-b4ba-67fd13e7681e/opts',
 
'--dhcp-leasefile=/var/lib/neutron/dhcp/0a9e36c5-2d55-4e6c-b4ba-67fd13e7681e/leases',
 '--dhcp-match=set:ipxe,175', '--enable-ra', '--ra-param=tapbe705a89-82,0,0', 
'--bind-interfaces', '--interface=tapbe705a89-82', 
'--dhcp-range=set:tag0,10.0.0.0,static,86400s', 
'--dhcp-option-force=option:mtu,1450', '--dhcp-lease-max=256', 
'--conf-file=/etc/neutron/dnsmasq.conf', '--domain=op
 enstacklocal'] create_process 
/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/agent/linux/utils.py:92
2016-11-23 12:06:55.950 7 ERROR neutron.agent.linux.utils [-] Exit code: 1; 
Stdin: ; Stdout: ; Stderr: 
dnsmasq: bad command line options: try --help

2016-11-23 12:06:55.951 7 ERROR neutron.agent.dhcp.agent [-] Unable to enable 
dhcp for 0a9e36c5-2d55-4e6c-b4ba-67fd13e7681e.
2016-11-23 12:06:55.951 7 ERROR neutron.agent.dhcp.agent Traceback (most recent 
call last):
2016-11-23 12:06:55.951 7 ERROR neutron.agent.dhcp.agent   File 
"/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/agent/dhcp/agent.py", 
line 115, in call_driver
2016-11-23 12:06:55.951 7 ERROR neutron.agent.dhcp.agent getattr(driver, 
action)(**action_kwargs)
2016-11-23 12:06:55.951 7 ERROR neutron.agent.dhcp.agent   File 
"/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/agent/linux/dhcp.py", 
line 216, in enable
2016-11-23 12:06:55.951 7 ERROR neutron.agent.dhcp.agent 
self.spawn_process()
2016-11-23 12:06:55.951 7 ERROR neutron.agent.dhcp.agent   File 
"/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/agent/linux/dhcp.py", 
line 437, in spawn_process
2016-11-23 12:06:55.951 7 ERROR neutron.agent.dhcp.agent 
self._spawn_or_reload_process(reload_with_HUP=False)
2016-11-23 12:06:55.951 7 ERROR neutron.agent.dhcp.agent   File 
"/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/agent/linux/dhcp.py", 
line 451, in _spawn_or_reload_process
2016-11-23 12:06:55.951 7 ERROR neutron.agent.dhcp.agent 
pm.enable(reload_cfg=reload_with_HUP)
2016-11-23 12:06:55.951 7 ERROR neutron.agent.dhcp.agent   File 
"/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/agent/linux/external_process.py",
 line 94, in enable
2016-11-23 12:06:55.951 7 ERROR neutron.agent.dhcp.agent 
run_as_root=self.run_as_root)
2016-11-23 12:06:55.951 7 ERROR neutron.agent.dhcp.agent   File 
"/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/agent/linux/ip_lib.py",
 line 882, in execute
2016-11-23 12:06:55.951 7 ERROR neutron.agent.dhcp.agent 
log_fail_as_error=log_fail_as_error, **kwargs)
2016-11-23 12:06:55.951 7 ERROR neutron.agent.dhcp.agent   File 
"/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/agent/linux/utils.py", 
line 147, in execute
2016-11-23 12:06:55.951 7 ERROR neutron.agent.dhcp.agent raise 
ProcessExecutionError(msg, returncode=returncode)
2016-11-23 12:06:55.951 7 ERROR neutron.agent.dhcp.agent ProcessExecutionError: 
Exit code: 1; Stdin: ; Stdout: ; Stderr: 
2016-11-23 12:06:55.951 7 ERROR neutron.agent.dhcp.agent dnsmasq: bad command 
line options: try --help
2016-11-23 12:06:55.951 7 ERROR neutron.agent.dhcp.agent 
2016-11-23 12:06:55.951 7 ERROR neutron.agent.dhcp.agent 
2016-11-23 12:06:55.951 7 INFO neutron.agent.dhcp.agent [-] Finished network 
0a9e36c5-2d55-4e6c-b4ba-67fd13e7681e dhcp configuration


more info please see [0]

[0] http://logs.openstack.org/89/400789/4/check/gate-kolla-ansible-dsvm-

[Yahoo-eng-team] [Bug 1644502] [NEW] port not found error on create_subnet

[Kevin Benton]

Public bug reported:

Error spotted during subnet creation for a gate test:

http://logs.openstack.org/77/401377/2/check/gate-tempest-dsvm-neutron-
linuxbridge-ubuntu-xenial/8a23d5b/logs/testr_results.html.gz


ft198.9: 
tempest.api.network.test_dhcp_ipv6.NetworksTestDHCPv6.test_dhcpv6_stateless_no_ra[id-ae2f4a5d-03ff-4c42-a3b0-ce2fcb7ea832]_StringException:
 Empty attachments:
  stderr
  stdout

pythonlogging:'': {{{
2016-11-24 08:51:28,627 14933 INFO [tempest.lib.common.rest_client] Request 
(NetworksTestDHCPv6:test_dhcpv6_stateless_no_ra): 404 POST 
https://127.0.0.1:9696/v2.0/subnets 0.458s
2016-11-24 08:51:28,627 14933 DEBUG[tempest.lib.common.rest_client] Request 
- Headers: {'Content-Type': 'application/json', 'Accept': 'application/json', 
'X-Auth-Token': ''}
Body: {"subnet": {"gateway_ip": "2003::1", "ip_version": 6, "cidr": 
"2003::/64", "network_id": "211d7f7c-4b6e-4bc6-8149-d831dc2018e8", 
"ipv6_address_mode": "slaac"}}
Response - Headers: {'status': '404', 'connection': 'close', 'server': 
'Apache/2.4.18 (Ubuntu)', 'content-length': '132', 'x-openstack-request-id': 
'req-9f760fe7-a74e-4d3e-be18-23d5ae27c314', 'content-type': 'application/json', 
'content-location': 'https://127.0.0.1:9696/v2.0/subnets', 'date': 'Thu, 24 Nov 
2016 08:51:28 GMT'}
Body: {"NeutronError": {"message": "Port 
5d8ffe5b-78b6-48ba-921f-800cfaa923c3 could not be found.", "type": 
"PortNotFound", "detail": ""}}
2016-11-24 08:51:28,684 14933 INFO [tempest.lib.common.rest_client] Request 
(NetworksTestDHCPv6:tearDown): 200 GET https://127.0.0.1:9696/v2.0/ports 0.053s
2016-11-24 08:51:28,684 14933 DEBUG[tempest.lib.common.rest_client] Request 
- Headers: {'Content-Type': 'application/json', 'Accept': 'application/json', 
'X-Auth-Token': ''}
Body: None
Response - Headers: {'status': '200', 'connection': 'close', 'server': 
'Apache/2.4.18 (Ubuntu)', 'content-length': '13', 'x-openstack-request-id': 
'req-e3ccd293-e418-457b-90bd-d6e9a362b8f7', 'content-type': 'application/json', 
'content-location': 'https://127.0.0.1:9696/v2.0/ports', 'date': 'Thu, 24 Nov 
2016 08:51:28 GMT'}
Body: {"ports": []}
2016-11-24 08:51:28,754 14933 INFO [tempest.lib.common.rest_client] Request 
(NetworksTestDHCPv6:tearDown): 200 GET https://127.0.0.1:9696/v2.0/subnets 
0.069s
2016-11-24 08:51:28,754 14933 DEBUG[tempest.lib.common.rest_client] Request 
- Headers: {'Content-Type': 'application/json', 'Accept': 'application/json', 
'X-Auth-Token': ''}
Body: None
Response - Headers: {'status': '200', 'connection': 'close', 'server': 
'Apache/2.4.18 (Ubuntu)', 'content-length': '645', 'x-openstack-request-id': 
'req-5d7d9081-6ea3-427e-94ac-53ea2df1dbc9', 'content-type': 'application/json', 
'content-location': 'https://127.0.0.1:9696/v2.0/subnets', 'date': 'Thu, 24 Nov 
2016 08:51:28 GMT'}
Body: {"subnets": [{"service_types": [], "description": "", 
"enable_dhcp": true, "network_id": "211d7f7c-4b6e-4bc6-8149-d831dc2018e8", 
"tenant_id": "b1b9117753ee40ab92362496e64e09ea", "created_at": 
"2016-11-24T08:51:28Z", "dns_nameservers": [], "updated_at": 
"2016-11-24T08:51:28Z", "gateway_ip": "2003::1", "ipv6_ra_mode": null, 
"allocation_pools": [{"start": "2003::2", "end": "2003:::::"}], 
"host_routes": [], "revision_number": 2, "ip_version": 6, "ipv6_address_mode": 
"slaac", "cidr": "2003::/64", "project_id": "b1b9117753ee40ab92362496e64e09ea", 
"id": "c6f8c153-899d-4303-9c3a-1e0c5b5a0cf1", "subnetpool_id": null, "name": 
""}]}
2016-11-24 08:51:28,821 14933 INFO [tempest.lib.common.rest_client] Request 
(NetworksTestDHCPv6:tearDown): 200 GET https://127.0.0.1:9696/v2.0/routers 
0.066s
2016-11-24 08:51:28,821 14933 DEBUG[tempest.lib.common.rest_client] Request 
- Headers: {'Content-Type': 'application/json', 'Accept': 'application/json', 
'X-Auth-Token': ''}
Body: None
Response - Headers: {'status': '200', 'connection': 'close', 'server': 
'Apache/2.4.18 (Ubuntu)', 'content-length': '15', 'x-openstack-request-id': 
'req-9b4a0eb1-0afe-4890-b3cd-25630edd1f0f', 'content-type': 'application/json', 
'content-location': 'https://127.0.0.1:9696/v2.0/routers', 'date': 'Thu, 24 Nov 
2016 08:51:28 GMT'}
Body: {"routers": []}
}}}

Traceback (most recent call last):
  File "tempest/api/network/test_dhcp_ipv6.py", line 130, in 
test_dhcpv6_stateless_no_ra
real_ip, eui_ip = self._get_ips_from_subnet(**kwargs)
  File "tempest/api/network/test_dhcp_ipv6.py", line 92, in _get_ips_from_subnet
subnet = self.create_subnet(self.network, **kwargs)
  File "tempest/api/network/base.py", line 178, in create_subnet
**kwargs)
  File "tempest/lib/services/network/subnets_client.py", line 27, in 
create_subnet
return self.create_resource(uri, post_data)
  File "tempest/lib/services/network/base.py", line 60, in create_resource
resp, body = self.post(req_uri, req_post_data)
  File "tempest/lib/common/rest_client.py", line 276, in post
return 

[Yahoo-eng-team] [Bug 1631347] Re: need add context param to nova's confirm_migration function

[OpenStack Infra]

Reviewed:  https://review.openstack.org/383699
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=41bf42a393b1be0ef36de11e47bf649f3f8cf9f8
Submitter: Jenkins
Branch:master

commit 41bf42a393b1be0ef36de11e47bf649f3f8cf9f8
Author: jichenjc 
Date:   Thu Oct 6 18:33:38 2016 +0800

Add context param to confirm_migration virt call

those param will be helpful like other virt layers
e.g do some auditing or log.

Change-Id: I6f4a8ab65de51ec006726aa3da27bf58d141c94f
Closes-Bug: 1631347


** Changed in: nova
   Status: In Progress => Fix Released

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

Title:
  need add context param to nova's confirm_migration function

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  a few nova virt calls has 'context' param send from compute layer to virt 
layer
   but confirm_migration don't have it , sometimes, we might need store some 
info in 
  hypervisor layers, so add context param will help further work

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1631347/+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 1644519] [NEW] Mechanism driver's create_subnet_(pre/post)commit functions when called by ML2 plugin doesn't have the correct MTU value in context.network.current

[Numan Siddique]

Public bug reported:

the mtu value present in context.network.current doesn't take the tunnel
encapsulation value into account.

** Affects: neutron
 Importance: Undecided
 Assignee: Numan Siddique (numansiddique)
 Status: New

** Changed in: neutron
 Assignee: (unassigned) => Numan Siddique (numansiddique)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1644519

Title:
  Mechanism driver's create_subnet_(pre/post)commit functions when
  called by ML2 plugin doesn't have the correct MTU value in
  context.network.current

Status in neutron:
  New

Bug description:
  the mtu value present in context.network.current doesn't take the
  tunnel encapsulation value into account.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1644519/+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 1520043] Re: error message do not disappear after click "cancel" button on form page

[Rob Cresswell]

This is by design. It can be customised in local_settings.py

** Changed in: horizon
   Status: In Progress => Won't Fix

** Changed in: horizon
 Assignee: srikanth (k1039485) => (unassigned)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1520043

Title:
  error message do not disappear after click "cancel" button on form
  page

Status in OpenStack Dashboard (Horizon):
  Won't Fix

Bug description:
  When open a form page in OpenStack horizon GUI or after a click a
  submit button in form page, some thing wrong in backend, one or more
  error message will show up in the main page.

  Then click "cancel" button on form page, the form page disappear, but
  the main page will not be refreshed, so the error messages is still on
  the main page, these message can not be clean by itself, Unless user
  click "x" on the error message.

  see the "Metadata Definitions" panel example in attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1520043/+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 1614506] [NEW] Volume doesn't gets deleted upon instance termination

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hello!

I have tried to create OpenStack compute instances from an image via the
following API requests (according to the API guide
):

---8<---
{
"server" : {
"name" : "test",
"flavorRef" : "http://openstack.example.com/flavors/2;,
"networks" : [{
"uuid" : "1beeab54-0125-4ac0-8ac1-3614a02e399f",
"tag": "instance-net"
}],
"imageRef": "61d15016-1b4f-4303-9d8a-6f8cb531a0f5",
"block_device_mapping_v2": [{
"uuid": "70a599e0-31e7-49b7-b260-868f441e862b",
"source_type": "image",
"destination_type": "volume",
"boot_index": 0,
"volume_size": "1",
"tag": "disk1",
"delete_on_termination": "true"
}],
"security_groups": [
{
"name": "default"
}
]
}
}
--->8---

---8<---
{
"server" : {
"name" : "test",
"flavorRef" : "http://openstack.example.com/flavors/2;,
"networks" : [{
"uuid" : "1beeab54-0125-4ac0-8ac1-3614a02e399f",
"tag": "instance-net"
}],
"imageRef": "61d15016-1b4f-4303-9d8a-6f8cb531a0f5",
"delete_on_termination": "true"
"security_groups": [
{
"name": "default"
}
]
}
}
--->8---

Both requests result in creation of instances, no errors present in the
server response, but when I then remove instances, volumes stay there.
URL where I submit requests looks as follows: https://:8774/v2/7d0f17355baf480ba2a317467cdf70fc/servers

** Affects: nova
 Importance: Undecided
 Status: New

-- 
Volume doesn't gets deleted upon instance termination
https://bugs.launchpad.net/bugs/1614506
You received this bug notification because you are a member of Yahoo! 
Engineering Team, which is subscribed to OpenStack Compute (nova).

-- 
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 1595575] Re: The hash of a notification object does not depend on its SCHEMA

[OpenStack Infra]

Reviewed:  https://review.openstack.org/344334
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=0ac7c988523f0112ec310deb4acd318cf6009bb8
Submitter: Jenkins
Branch:master

commit 0ac7c988523f0112ec310deb4acd318cf6009bb8
Author: Balazs Gibizer 
Date:   Tue Jul 19 17:35:36 2016 +0200

Notification object version test depends on SCHEMA

As ObjectVersionChecker.test_hashes() supports extra_data_func parameter
from ovo 2.6.0 this patch makes the notification object version test
aware of the SCHEMA changes of the notification objects.

The object hashes are updated without version bump as no real
changes was made on the objects just the hash calculation is changed.

Closes-Bug: #1595575
Change-Id: I1375b43280d29026d7d1c0d362740d6077c5061f


** Changed in: nova
   Status: In Progress => Fix Released

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

Title:
  The hash of a notification object does not depend on its SCHEMA

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Description
  ===
  As oslo ObjectVersionChecker.test_hashes() does not provide a way to supply 
exta information to the fingerprint generation the current unit test does not 
detect if the SCHEMA of a versioned notification object has been changed 
without proper version bump. 

  Compare the unit test test_versions with
  test_notification_payload_version_depends_on_the_schema in
  TestNotificationObjectVersions [1]

  The former uses test_hashes without the extra_data_func while the
  later uses the get_hashes() with extra_data_func.

  [1]
  
https://github.com/openstack/nova/blob/master/nova/tests/unit/notifications/objects/test_notification.py#L267

  Steps to reproduce
  ==
  Modify the SCHEMA of one of the notification object. 
  Run the unit test
  SCHEMA changes are not detected

  Environment
  ===
  6a119fc72096fa65678112e151e4a7a00091ce26

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1595575/+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 1618881] Re: Exception raised has double full stop

[OpenStack Infra]

Reviewed:  https://review.openstack.org/363641
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=29273adaf9c31fa22e4580c5af6eb9469290d38c
Submitter: Jenkins
Branch:master

commit 29273adaf9c31fa22e4580c5af6eb9469290d38c
Author: Gary Kotton 
Date:   Wed Aug 31 06:06:43 2016 -0700

Fix InvalidInput exception output

Ensure that only one period ends the data. The exception adds the
period so no need to pass the error_message with a period.

TrivialFix

Change-Id: I411534fc7ea56946a72890808154cc43ba3b6c1d
Closes-bug: #1618881


** Changed in: neutron
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1618881

Title:
  Exception raised has double full stop

Status in neutron:
  Fix Released

Bug description:
  An example:

  Invalid input for operation: Exceeded maximum amount of fixed ips per
  port..

  Reason - neutron lib exception has a full stop:

  class InvalidInput(BadRequest):
  """A bad request due to invalid input.
  A specialization of the BadRequest error indicating bad input was
  specified.
  :param error_message: Details on the operation that failed due to bad
  input.
  """
  message = _("Invalid input for operation: %(error_message)s.")

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1618881/+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 1644513] [NEW] (psycopg2.ProgrammingError) column "deleted" is of type integer but expression is of type boolean

[Julien Danjou]

Public bug reported:

The Telemetry gate is broken with PostgreSQL because of nova-api:

2016-11-24 09:59:34.431 32192 ERROR oslo_db.sqlalchemy.exc_filters 
[req-8ed9761f-b699-4c92-8793-7dca7296d63e 
tempest-TelemetryNotificationAPITest-1553287657 
tempest-TelemetryNotificationAPITest-1553287657] DBAPIError exception wrapped 
from (psycopg2.ProgrammingError) column "deleted" is of type integer but 
expression is of type boolean
LINE 1: ...16-11-24T09:59:34.369835'::timestamp, NULL, NULL, false, 'f2...
 ^
HINT:  You will need to rewrite or cast the expression.
 [SQL: 'INSERT INTO instances (created_at, updated_at, deleted_at, deleted, 
user_id, project_id, image_ref, kernel_id, ramdisk_id, hostname, launch_index, 
key_name, key_data, power_state, vm_state, task_state, memory_mb, vcpus, 
root_gb, ephemeral_gb, ephemeral_key_uuid, host, node, instance_type_id, 
user_data, reservation_id, launched_at, terminated_at, availability_zone, 
display_name, display_description, launched_on, locked, locked_by, os_type, 
architecture, vm_mode, uuid, root_device_name, default_ephemeral_device, 
default_swap_device, config_drive, access_ip_v4, access_ip_v6, 
auto_disk_config, progress, shutdown_terminate, disable_terminate, cell_name, 
cleaned) VALUES (%(created_at)s, %(updated_at)s, %(deleted_at)s, %(deleted)s, 
%(user_id)s, %(project_id)s, %(image_ref)s, %(kernel_id)s, %(ramdisk_id)s, 
%(hostname)s, %(launch_index)s, %(key_name)s, %(key_data)s, %(power_state)s, 
%(vm_state)s, %(task_state)s, %(memory_mb)s, %(vcpus)s, %(root_gb)s, 
%(ephemeral_gb)s, %(ephemeral_key_
 uuid)s, %(host)s, %(node)s, %(instance_type_id)s, %(user_data)s, 
%(reservation_id)s, %(launched_at)s, %(terminated_at)s, %(availability_zone)s, 
%(display_name)s, %(display_description)s, %(launched_on)s, %(locked)s, 
%(locked_by)s, %(os_type)s, %(architecture)s, %(vm_mode)s, %(uuid)s, 
%(root_device_name)s, %(default_ephemeral_device)s, %(default_swap_device)s, 
%(config_drive)s, %(access_ip_v4)s, %(access_ip_v6)s, %(auto_disk_config)s, 
%(progress)s, %(shutdown_terminate)s, %(disable_terminate)s, %(cell_name)s, 
%(cleaned)s) RETURNING instances.id'] [parameters: {'vm_state': u'building', 
'availability_zone': None, 'terminated_at': None, 'ramdisk_id': 
u'52b2ce17-7bbd-42e7-beae-04c68862da89', 'instance_type_id': 11, 'user_data': 
None, 'cleaned': 0, 'vm_mode': None, 'deleted_at': None, 'reservation_id': 
u'r-uo48grph', 'disable_terminate': False, 'display_name': 
u'tempest-ceilometer-instance-28537131', 'uuid': 
'd575169b-72d8-431c-a604-7073460c8d45', 'default_swap_device': None, 
'hostname': 
 u'tempest-ceilometer-instance-28537131', 'launched_on': None, 
'display_description': u'tempest-ceilometer-instance-28537131', 'key_data': 
None, 'deleted': False, 'power_state': 0, 'default_ephemeral_device': None, 
'progress': 0, 'project_id': u'859a6fcd13504baa8032ed210dc49501', 
'launched_at': None, 'architecture': None, 'node': None, 'ephemeral_gb': 0, 
'access_ip_v6': None, 'access_ip_v4': None, 'kernel_id': 
u'8e1eaad4-cb0a-4517-95da-cec482d6169c', 'key_name': None, 'updated_at': None, 
'host': None, 'root_gb': 0, 'user_id': u'f21c50ce019c40e1af23463735ba2b34', 
'task_state': u'scheduling', 'shutdown_terminate': False, 'cell_name': None, 
'ephemeral_key_uuid': None, 'locked': False, 'created_at': 
datetime.datetime(2016, 11, 24, 9, 59, 34, 369835), 'locked_by': None, 
'launch_index': 0, 'memory_mb': 64, 'vcpus': 1, 'image_ref': 
u'788e-adda-45ce-8bbc-dbfe4e087941', 'root_device_name': None, 
'auto_disk_config': False, 'os_type': None, 'config_drive': u''}]
2016-11-24 09:59:34.431 32192 ERROR oslo_db.sqlalchemy.exc_filters Traceback 
(most recent call last):
2016-11-24 09:59:34.431 32192 ERROR oslo_db.sqlalchemy.exc_filters   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1139, 
in _execute_context
2016-11-24 09:59:34.431 32192 ERROR oslo_db.sqlalchemy.exc_filters context)
2016-11-24 09:59:34.431 32192 ERROR oslo_db.sqlalchemy.exc_filters   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/default.py", line 
450, in do_execute
2016-11-24 09:59:34.431 32192 ERROR oslo_db.sqlalchemy.exc_filters 
cursor.execute(statement, parameters)
2016-11-24 09:59:34.431 32192 ERROR oslo_db.sqlalchemy.exc_filters 
ProgrammingError: column "deleted" is of type integer but expression is of type 
boolean
2016-11-24 09:59:34.431 32192 ERROR oslo_db.sqlalchemy.exc_filters LINE 1: 
...16-11-24T09:59:34.369835'::timestamp, NULL, NULL, false, 'f2...
2016-11-24 09:59:34.431 32192 ERROR oslo_db.sqlalchemy.exc_filters  
^
2016-11-24 09:59:34.431 32192 ERROR oslo_db.sqlalchemy.exc_filters HINT:  You 
will need to rewrite or cast the expression.
2016-11-24 09:59:34.431 32192 ERROR oslo_db.sqlalchemy.exc_filters 
2016-11-24 09:59:34.431 32192 ERROR oslo_db.sqlalchemy.exc_filters 
2016-11-24 09:59:34.443 32192 

[Yahoo-eng-team] [Bug 1644517] [NEW] [neutron-vpnaas] libreswan driver requires root

[Paul Bourke]

Public bug reported:

The libreswan device driver attempts to both cleanup[0] and chown[1]
ipsec.secrets to root, using the bare python os module. From what I can
gather it should use neutron-rootwrap to do these operations, otherwise
the operator is forced to run the agent as root.

[0] 
https://github.com/openstack/neutron-vpnaas/blob/master/neutron_vpnaas/services/vpn/device_drivers/libreswan_ipsec.py#L40-L42
[1] 
https://github.com/openstack/neutron-vpnaas/blob/master/neutron_vpnaas/services/vpn/device_drivers/libreswan_ipsec.py#L50-L51

** Affects: neutron
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1644517

Title:
  [neutron-vpnaas] libreswan driver requires root

Status in neutron:
  New

Bug description:
  The libreswan device driver attempts to both cleanup[0] and chown[1]
  ipsec.secrets to root, using the bare python os module. From what I
  can gather it should use neutron-rootwrap to do these operations,
  otherwise the operator is forced to run the agent as root.

  [0] 
https://github.com/openstack/neutron-vpnaas/blob/master/neutron_vpnaas/services/vpn/device_drivers/libreswan_ipsec.py#L40-L42
  [1] 
https://github.com/openstack/neutron-vpnaas/blob/master/neutron_vpnaas/services/vpn/device_drivers/libreswan_ipsec.py#L50-L51

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1644517/+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 1644725] [NEW] Check destination_type when booting with bdm provided

[Zhenyu Zheng]

Public bug reported:

TBD

** Affects: nova
 Importance: Undecided
 Assignee: Zhenyu Zheng (zhengzhenyu)
 Status: New

** Changed in: nova
 Assignee: (unassigned) => Zhenyu Zheng (zhengzhenyu)

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

Title:
  Check destination_type when booting with bdm provided

Status in OpenStack Compute (nova):
  New

Bug description:
  TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1644725/+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 1644725] Re: Check destination_type when booting with bdm provided

[Zhenyu Zheng]

** Description changed:

- TBD
+ When booting instance with block_device_mapping provided, in the current
+ implementation, the "destination_type" is allowed to be None, and this
+ lead to un-sync between Nova and Cinder:
+ 
+ Step 1: Booting with block_device_mapping, leave destination_type to be
+ None:
+ 
+ root@SZX1000191849:/var/log/nova# nova --debug boot  --flavor 1 --image
+ 2ba75018-403f-407b-864a-08564022e1f8 --nic net-id=cce1d2f1-acf4-4646
+ -abdc-069f8d0dbb71 --block-device
+ 'source=volume,id=9f49d5b0-3625-46a2-9ed4-d82f19949148' test_bdm
+ 
+ the corresponding REST call is:
+ DEBUG (session:342) REQ: curl -g -i -X POST 
http://10.229.45.17:8774/v2.1/os-volumes_boot -H "Accept: application/json" -H 
"User-Agent: python-novaclient" -H "OpenStack-API-Version: compute 2.37" -H 
"X-OpenStack-Nova-API-Version: 2.37" -H "X-Auth-Token: 
{SHA1}4d8c2c43338e1c4d96e08bcd1c2f3ff36de14154" -H "Content-Type: 
application/json" -d '{"server": {"name": "test_bdm", "imageRef": 
"2ba75018-403f-407b-864a-08564022e1f8", "block_device_mapping_v2": 
[{"source_type": "image", "delete_on_termination": true, "boot_index": 0, 
"uuid": "2ba75018-403f-407b-864a-08564022e1f8", "destination_type": "local"}, 
{"source_type": "volume", "uuid": "9f49d5b0-3625-46a2-9ed4-d82f19949148"}], 
"flavorRef": "1", "max_count": 1, "min_count": 1, "networks": [{"uuid": 
"cce1d2f1-acf4-4646-abdc-069f8d0dbb71"}]}}'
+ 
+ Step 2: After the instance is successfully launched, the detailed info
+ is like this:
+ 
+ root@SZX1000191849:/var/log/nova# nova show 
83d9ec32-93e0-441a-ae10-00e08b65de0b
+ 
+--+--+
+ | Property | Value
|
+ 
+--+--+
+ | OS-DCF:diskConfig| MANUAL   
|
+ | OS-EXT-AZ:availability_zone  | nova 
|
+ | OS-EXT-SRV-ATTR:host | SZX1000191849
|
+ | OS-EXT-SRV-ATTR:hostname | test-bdm 
|
+ | OS-EXT-SRV-ATTR:hypervisor_hostname  | SZX1000191849
|
+ | OS-EXT-SRV-ATTR:instance_name| instance-0016
|
+ | OS-EXT-SRV-ATTR:kernel_id| 87c9afd6-3a47-4a4c-a804-6b456d68136d 
|
+ | OS-EXT-SRV-ATTR:launch_index | 0
|
+ | OS-EXT-SRV-ATTR:ramdisk_id   | acd02b28-6484-4f90-a5e7-bba7159343e1 
|
+ | OS-EXT-SRV-ATTR:reservation_id   | r-fiqwkq02   
|
+ | OS-EXT-SRV-ATTR:root_device_name | /dev/vda 
|
+ | OS-EXT-SRV-ATTR:user_data| -
|
+ | OS-EXT-STS:power_state   | 1
|
+ | OS-EXT-STS:task_state| -
|
+ | OS-EXT-STS:vm_state  | active   
|
+ | OS-SRV-USG:launched_at   | 2016-11-25T06:50:36.00   
|
+ | OS-SRV-USG:terminated_at | -
|
+ | accessIPv4   |  
|
+ | accessIPv6   |  
|
+ | config_drive |  
|
+ | created  | 2016-11-25T06:50:30Z 
|
+ | description  | -
|
+ | flavor   | m1.tiny (1)  
|
+ | hostId   | 
410c49382deba8e205044b231169b2a656b27b6c994815366712b62e 

[Yahoo-eng-team] [Bug 1644711] [NEW] memory leak in glance api when a big image ~300GB is downloaded via glanceclient in kilo

[Abhishek]

Public bug reported:

memory leak in glance api when a big image ~300GB is downloaded via
glanceclient in kilo.

the backend store is S3. when the glanceclient starts downloading the
image, the glanceclient is stopped.

After stopping the glanceclient process the memory consumed by
associated glance-api starts increasing every second till it consumes
70-80% memory  (seen via top) and finally becoming unresponsive.

Upon restarting the glance-api service the memory consumed is released.

** Affects: glance
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1644711

Title:
  memory leak in glance api when a big image ~300GB is downloaded via
  glanceclient in kilo

Status in Glance:
  New

Bug description:
  memory leak in glance api when a big image ~300GB is downloaded via
  glanceclient in kilo.

  the backend store is S3. when the glanceclient starts downloading the
  image, the glanceclient is stopped.

  After stopping the glanceclient process the memory consumed by
  associated glance-api starts increasing every second till it consumes
  70-80% memory  (seen via top) and finally becoming unresponsive.

  Upon restarting the glance-api service the memory consumed is
  released.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1644711/+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 1644712] [NEW] os disk of instance was deleted when failed to evacaute

[fanzhicheng]

Public bug reported:

nova-compute:  2:13.1.2-0ubuntu2~cloud0 
libvirt-bin:1.3.1-1
storage: ceph

1: create 10 vm in one compute-node1
2: poweroff  compute-node1
3: nova evacaute vm compute-node-2 one by one
4: i find the vm state is error, use commant: rbd -p compute ls |grep vm_id 
,return none , the os disk of vm was deleted, From the nova-compute.log I get 
info:Timeout waiting for vif plugging callback for instance ,I read the nova 
code: 4938 /nova/virt/libvirt/driver.py ,found the self.cleanup(context, 
instance, network_info=network_info,
 block_device_info=block_device_info) 
destroy the disk, I think it is not reasonable for destroy_disks=True

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

Title:
  os disk of instance was deleted when failed to evacaute

Status in OpenStack Compute (nova):
  New

Bug description:
  nova-compute:  2:13.1.2-0ubuntu2~cloud0 
  libvirt-bin:1.3.1-1
  storage: ceph

  1: create 10 vm in one compute-node1
  2: poweroff  compute-node1
  3: nova evacaute vm compute-node-2 one by one
  4: i find the vm state is error, use commant: rbd -p compute ls |grep vm_id 
,return none , the os disk of vm was deleted, From the nova-compute.log I get 
info:Timeout waiting for vif plugging callback for instance ,I read the nova 
code: 4938 /nova/virt/libvirt/driver.py ,found the self.cleanup(context, 
instance, network_info=network_info,
   block_device_info=block_device_info) 
  destroy the disk, I think it is not reasonable for destroy_disks=True

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1644712/+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 1443898] Re: TestVolumeBootPattern.test_volume_boot_pattern fail with libvirt-xen

[Thomas Bechtold]

** Changed in: nova
   Status: Expired => Confirmed

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

Title:
  TestVolumeBootPattern.test_volume_boot_pattern fail with libvirt-xen

Status in OpenStack Compute (nova):
  Confirmed
Status in tempest:
  Invalid

Bug description:
  The following test is failling when runned with libvirt-xen nova compute node.
  
tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_volume_boot_pattern

  This is due to the function _boot_instance_from_volume which create a
  volume with the device name "vda", but this is not supported by Xen.

  Also Nova itself does not reject the device name.

  This is with devstack master.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1443898/+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 1644175] Re: create project command mentioned in Installation guide for Newton throwing error

[murtazasolangi]

** Also affects: ubuntu
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1644175

Title:
  create project command mentioned in Installation guide for Newton
  throwing error

Status in OpenStack Identity (keystone):
  Incomplete
Status in Ubuntu:
  New

Bug description:
  While doing manual installation of Newton release by the following URL:
  http://docs.openstack.org/newton/install-guide-rdo/keystone-users.html

  The project create command throws error. 
  [root@controller ~(keystone_admin)]# openstack project create --domain 
default --description "Service Project" service
  usage: openstack project create [-h] [-f {json,shell,table,value,yaml}]
  [-c COLUMN] [--max-width ]
  [--noindent] [--prefix PREFIX]
  [--description ]
  [--enable | --disable]
  [--property 

[Yahoo-eng-team] [Bug 1642935] Re: can't boot lxd container from volume

[Ondrej Linha]

** Project changed: nova => nova-lxd

** Description changed:

  lxd container initialization failed when booting from block device (lvm)
  
  * ubutnu server 16.04 lts
  ** nova-compute-lxd 14.0.0-0ubuntu1~cloud0
  ** python-nova-lxd 14.0.0-0ubuntu1~cloud0
+ 
+ Test steps:
+ 1. Create volume with image eg. 
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-root.tar.gz
+ 2. Start LXD instance from that volume
+ 
+ Result:
  
  2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager 
[req-9225eff7-0bc0-488e-aa26-f3961f5e57ae 3a3320729a2346a0ae4f44d122fc0c2c 
bae1c166a41547c289fe7ae077272648 - - -] [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26] Instance failed to spawn
  2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26] Traceback (most recent call last):
  2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26]   File 
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2078, in 
_build_resources
  2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26] yield resources
  2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26]   File 
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1920, in 
_build_and_run_instance
  2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26] block_device_info=block_device_info)
  2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26]   File 
"/usr/lib/python2.7/dist-packages/nova/virt/lxd/driver.py", line 274, in spawn
  2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26] self.setup_image(context, instance, 
image_meta)
  2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26]   File 
"/usr/lib/python2.7/dist-packages/nova/virt/lxd/driver.py", line 1177, in 
setup_image
  2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26] 
container_utils.get_container_rootfs_image(image_meta)
  2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26]   File 
"/usr/lib/python2.7/dist-packages/nova/virt/lxd/utils.py", line 30, in 
get_container_rootfs_image
  2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26] return os.path.join(BASE_DIR, 
'%s-rootfs.tar.gz' % image_meta.id)
  2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26]   File 
"/usr/lib/python2.7/dist-packages/oslo_versionedobjects/base.py", line 67, in 
getter
  2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26] self.obj_load_attr(name)
  2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26]   File 
"/usr/lib/python2.7/dist-packages/oslo_versionedobjects/base.py", line 632, in 
obj_load_attr
  2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26] _("Cannot load '%s' in the base 
class") % attrname)
  2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26] NotImplementedError: Cannot load 'id' in 
the base class

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

Title:
  can't boot lxd container from volume

Status in nova-lxd:
  New

Bug description:
  lxd container initialization failed when booting from block device
  (lvm)

  * ubutnu server 16.04 lts
  ** nova-compute-lxd 14.0.0-0ubuntu1~cloud0
  ** python-nova-lxd 14.0.0-0ubuntu1~cloud0

  Test steps:
  1. Create volume with image eg. 
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-root.tar.gz
  2. Start LXD instance from that volume

  Result:

  2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager 
[req-9225eff7-0bc0-488e-aa26-f3961f5e57ae 3a3320729a2346a0ae4f44d122fc0c2c 
bae1c166a41547c289fe7ae077272648 - - -] [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26] Instance failed to spawn
  2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26] Traceback (most recent call last):
  2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26]   File 
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2078, in 
_build_resources
  2016-11-18 12:20:58.308 20325 ERROR nova.compute.manager [instance: 
dab08366-e4a8-43ad-9f6c-9434d1a2ee26] yield resources
  2016-11-18 12:20:58.308 20325 ERROR 

[Yahoo-eng-team] [Bug 1498987] Re: [RFE] DHCP agent should provide ipv6 RAs for isolated networks with ipv6 subnets

[Ihar Hrachyshka]

We revert the patch since it broke CentOS installations. Reopening the
bug.

** Changed in: neutron
   Status: Fix Released => Confirmed

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1498987

Title:
  [RFE] DHCP agent should provide ipv6 RAs for isolated networks with
  ipv6 subnets

Status in neutron:
  Confirmed

Bug description:
  Currently, if there is no router attached to a subnet, then instances
  cannot walk thru IPv6 address assignment because there is nothing on
  the network that multicasts RAs that would provide basic info about
  how ipv6 addressing is handled there. We can have DHCP agent to run
  radvd in that case. Then instances would be able to receive IPv6
  addresses on isolated networks too.

  We could try to rely on https://tools.ietf.org/html/rfc4191.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1498987/+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 1621137] Re: wrong warning (The Keystone URL (either in Horizon settings or in service catalog) points to a v2.0 Keystone endpoint)

[Rob Cresswell]

** Changed in: horizon
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1621137

Title:
  wrong warning (The Keystone URL (either in Horizon settings or in
  service catalog) points to a v2.0 Keystone endpoint)

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  wrong warning printed in current code

  I added some log and seems we need use ["/v2.0"] instead "/v2.0"

  [Wed Sep 07 15:09:40.951167 2016] [:error] [pid 29875] path is /v3, subs is 
/v2.0, t is True
  [Wed Sep 07 15:09:40.951254 2016] [:error] [pid 29875] The Keystone URL 
(either in Horizon settings or in service catalog) points to a v2.0 Keystone 
endpoint, but v3 is specified as the API version to use by Horizon. Using v3 
endpoint for authentication.https://9.60.29.98:35357/v3

  
  def has_in_url_path(url, subs):
  """Test if any of `subs` strings is present in the `url` path."""
  scheme, netloc, path, query, fragment = urlparse.urlsplit(url)
  t = any([sub in path for sub in subs])
  LOG.warn('path is %s, subs is %s, t is %s' % (path, subs, t))
  return t

  
  if get_keystone_version() >= 3 and has_in_url_path(auth_url, "/v2.0"):
  LOG.warning("The Keystone URL (either in Horizon settings or in "
  "service catalog) points to a v2.0 Keystone endpoint, "
  "but v3 is specified as the API version to use by "
  "Horizon. Using v3 endpoint for authentication.%s", 
auth_url)
  auth_url = url_path_replace(auth_url, "/v2.0", "/v3", 1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1621137/+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