[Openstack-operators] [neutron] Liberty - DHCP ports keep going to BUILD state

2017-11-05 Thread Christopher Hull
HI all;
Trying to create DHCP on the Public network.  This had been working, but
now all of a sudden the ports are set to BUILD instead of AVAILABLE.

I did a cheat in MariaDB and discovered that something somewhere keeps
setting DHCP to BUILD.   Any ideas?


*MariaDB [neutron]>  update ports set status='AVAILABLE' where id
='37cc930c-6ad3-4355-8ff5-6b75e131c998';*

*Query OK, 1 row affected (0.05 sec)*

*Rows matched: 1  Changed: 1  Warnings: 0*


*MariaDB [neutron]> select status, id  from ports;*

*+---+--+*

*| status| id   |*

*+---+--+*

*| BUILD | 0ebbaf42-6bd9-4853-b041-e00f3da4dd89 |*

*| AVAILABLE | 37cc930c-6ad3-4355-8ff5-6b75e131c998 |*

*+---+--+*

*2 rows in set (0.00 sec)*


*MariaDB [neutron]> select status, id  from ports;*

*++--+*

*| status | id   |*

*++--+*

*| BUILD  | 0ebbaf42-6bd9-4853-b041-e00f3da4dd89 |*

*| BUILD  | 37cc930c-6ad3-4355-8ff5-6b75e131c998 |*

*++--+*

*2 rows in set (0.00 sec)*






- Christopher T. Hull
Sunnyvale CA. 94085
(415) 385 4865
chrishul...@gmail.com
http://chrishull.com
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


Re: [Openstack-operators] [neutron] Liberty - DHCP ports keep going to BUILD state

2017-11-05 Thread Christopher Hull
This is just damn strange.  All of a sudden (well, for the past few weeks),
I CAN NOT create ANY port on the public network.   Just tore down and
recreated the public net from scratch.   What's going on here!!!

It's stuck trying to create the DHCP agent's port.  This is why it's stuck
in BUILD.  Infinite loop.BTW, the Compute node is at 172.22.10.99.
 Maybe I should just change that.  But it would be really nice to know what
changed and why this is happening.


2017-11-05 10:44:10.802 1574 ERROR
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
 resync_a = self.treat_devices_added_updated(devices_added_updated)
2017-11-05 10:44:10.802 1574 ERROR
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
 File
"/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py",
line 1045, in treat_devices_added_updated
2017-11-05 10:44:10.802 1574 ERROR
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
 device_details['port_id'], device_details['device_owner'])
2017-11-05 10:44:10.802 1574 ERROR
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
 File
"/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py",
line 542, in add_interface
2017-11-05 10:44:10.802 1574 ERROR
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
 tap_device_name, device_owner)
2017-11-05 10:44:10.802 1574 ERROR
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
 File
"/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py",
line 480, in add_tap_interface
2017-11-05 10:44:10.802 1574 ERROR
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
 return False
2017-11-05 10:44:10.802 1574 ERROR
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
 File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 195,
in __exit__
2017-11-05 10:44:10.802 1574 ERROR
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
 six.reraise(self.type_, self.value, self.tb)
2017-11-05 10:44:10.802 1574 ERROR
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
 File
"/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py",
line 472, in add_tap_interface
2017-11-05 10:44:10.802 1574 ERROR
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
 tap_device_name, device_owner)
2017-11-05 10:44:10.802 1574 ERROR
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
 File
"/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py",
line 504, in _add_tap_interface
2017-11-05 10:44:10.802 1574 ERROR
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
 segmentation_id)
2017-11-05 10:44:10.802 1574 ERROR
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
 File
"/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py",
line 456, in ensure_physical_in_bridge
2017-11-05 10:44:10.802 1574 ERROR
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
 physical_interface)
2017-11-05 10:44:10.802 1574 ERROR
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
 File
"/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py",
line 275, in ensure_flat_bridge
2017-11-05 10:44:10.802 1574 ERROR
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
 gateway):
2017-11-05 10:44:10.802 1574 ERROR
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
 File
"/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py",
line 416, in ensure_bridge
2017-11-05 10:44:10.802 1574 ERROR
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
 self.update_interface_ip_details(bridge_name, interface, ips, gateway)
2017-11-05 10:44:10.802 1574 ERROR
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
 File
"/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py",
line 355, in update_interface_ip_details
2017-11-05 10:44:10.802 1574 ERROR
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
 dst_device.addr.add(cidr=ip['cidr'])
2017-11-05 10:44:10.802 1574 ERROR
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
 File "/usr/lib/python2.7/site-packages/neutron/agent/linux/ip_lib.py",
line 548, in add
2017-11-05 10:44:10.802 1574 ERROR
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
 self._as_root([net.version], tuple(args))
2017-11-05 10:44:10.802 1574 ERROR
neutron.plugins.ml2.drivers.linuxbridge.ag

[Openstack-operators] [charms] Sydney forum user feedback session (Tues@0950)

2017-11-05 Thread James Page
Hi All

Apologies for the late creation of this pad:

  https://etherpad.openstack.org/p/SYD-forum-charms-ops-feedback

if your planning on attending this session please add your name and any
topics for discussion!

Cheers

James
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


[Openstack-operators] Fast Forward Upgrades

2017-11-05 Thread David Medberry
Some good discussion at the Summit (right now) about Fast Forward Upgrades.

Including some concerns that nova-compute INTENTFULLY fails if greater than
N-1.

More details are appearing in the etherpad.

This convo is VERY well attended by MANY openstack devs. Very heavy dev
room.

https://etherpad.openstack.org/p/SYD-forum-fast-forward-upgrades

and this is in the Operator session in the Dev Forum.
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


[Openstack-operators] [Openstack][Nova][Operators]

2017-11-05 Thread Amit Kumar
Hi All,

I have installed Openstack Pike with Openstack Ansible.

Earlier I was working with Newton release. But with Pike release, I am
noticing that Nova schedule is in force even when I am providing
availability zone with a specific compute node. For the initial set of VMs,
it is honouring availability zone request while creating VMs but while
creating last set of VMs, it is putting VMs on other compute nodes,
probably the nodes which are having more resources. So, my question is that
does Pike and Ocata releases allow over commitment of CPU/RAM/Disk
resources or not? If they do so, then what are the parameters which will go
in the configuration files to make over commitment work? I strictly want to
enforce that VM be instantiated on the host I mention in availability zone.

Regards,
Amit
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators