[Yahoo-eng-team] [Bug 1690277] [NEW] Enable port_security don't work for old net and port
Public bug reported: Hi, When i try to enable port_security, my old port and network was not in the database networksecuritybindings and port_security_bindings. I tried to do a neutron-db-manage but it was not working. I populate manualy the database and it was working. Do we have an automatic way to populate the database ? Regards, ** 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/1690277 Title: Enable port_security don't work for old net and port Status in neutron: New Bug description: Hi, When i try to enable port_security, my old port and network was not in the database networksecuritybindings and port_security_bindings. I tried to do a neutron-db-manage but it was not working. I populate manualy the database and it was working. Do we have an automatic way to populate the database ? Regards, To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1690277/+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 1690275] [NEW] Create port will allocate reserved MAC address if no MAC provide
Public bug reported: Currently, if create port with no MAC specify, it will automatic allocate an MAC address. But this will allocate an RESERVED MAC address(eg, mac 01:80:c2:00:00:01 reserved for IEEE Pause frame), and if packet with this destination MAC address, it will process by other networking equipment. So when allocate an MAC address, It should be check if Mac has been reserved. Currently, I found those MAC address(From OVS ovs-vswitchd.conf man pages) has been reserved for special purpose. 01:80:c2:00:00:00 IEEE 802.1D Spanning Tree Protocol (STP). 01:80:c2:00:00:01 IEEE Pause frame. 01:80:c2:00:00:0x Other reserved protocols. 00:e0:2b:00:00:00 Extreme Discovery Protocol (EDP). 00:e0:2b:00:00:04 and 00:e0:2b:00:00:06 Ethernet Automatic Protection Switching (EAPS). 01:00:0c:cc:cc:cc Cisco Discovery Protocol (CDP), VLAN Trunking Protocol (VTP), Dynamic Trunking Protocol (DTP), Port Aggregation Protocol (PAgP), and others. 01:00:0c:cc:cc:cd Cisco Shared Spanning Tree Protocol PVSTP+. 01:00:0c:cd:cd:cd Cisco STP Uplink Fast. 01:00:0c:00:00:00 Cisco Inter Switch Link. 01:00:0c:cc:cc:cx Cisco CFM. Start with 01(Multicast mac) we may don't care, but 00:e0:2b:00:00:00(EDP) and 00:e0:2b:00:00:04 and 00:e0:2b:00:00:06 should be check. ** 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/1690275 Title: Create port will allocate reserved MAC address if no MAC provide Status in neutron: New Bug description: Currently, if create port with no MAC specify, it will automatic allocate an MAC address. But this will allocate an RESERVED MAC address(eg, mac 01:80:c2:00:00:01 reserved for IEEE Pause frame), and if packet with this destination MAC address, it will process by other networking equipment. So when allocate an MAC address, It should be check if Mac has been reserved. Currently, I found those MAC address(From OVS ovs-vswitchd.conf man pages) has been reserved for special purpose. 01:80:c2:00:00:00 IEEE 802.1D Spanning Tree Protocol (STP). 01:80:c2:00:00:01 IEEE Pause frame. 01:80:c2:00:00:0x Other reserved protocols. 00:e0:2b:00:00:00 Extreme Discovery Protocol (EDP). 00:e0:2b:00:00:04 and 00:e0:2b:00:00:06 Ethernet Automatic Protection Switching (EAPS). 01:00:0c:cc:cc:cc Cisco Discovery Protocol (CDP), VLAN Trunking Protocol (VTP), Dynamic Trunking Protocol (DTP), Port Aggregation Protocol (PAgP), and others. 01:00:0c:cc:cc:cd Cisco Shared Spanning Tree Protocol PVSTP+. 01:00:0c:cd:cd:cd Cisco STP Uplink Fast. 01:00:0c:00:00:00 Cisco Inter Switch Link. 01:00:0c:cc:cc:cx Cisco CFM. Start with 01(Multicast mac) we may don't care, but 00:e0:2b:00:00:00(EDP) and 00:e0:2b:00:00:04 and 00:e0:2b:00:00:06 should be check. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1690275/+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 1690203] Re: token data doesn't have roles, projects and catalog information
** Also affects: keystone
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/1690203
Title:
token data doesn't have roles, projects and catalog information
Status in OpenStack Identity (keystone):
New
Status in keystoneauth:
New
Bug description:
Token which is generated using keystoneauth1.session.get/post doesn't
have roles, project and catalog information.
>>> from keystoneauth1 import session
>>> from keystoneauth1 import identity
>>> auth = identity.v3.Token('https://localhost:5000/v3',
'gABZFFOeoAYgNRrCDav6UHGM1Zo63kVk4V2mZ_7D41eCdiJUjw8xzo7eJxJR2vAxRaVljc_OUEErrmU9FsTh6OJi01w9D5hc-pAZPlHzZm-fmExPrEHUZQ1Uz9BI31UpDq_iNg4Im2m1cU8xiBdcUpJZeYKh6gxvL95MMlnttCle5u9y15UDB0I2QY2Sy1LEQ9UoEXVO4wk5M4KgOhVRdF36hEY8dpeH0Zo-MB6N6LqiNvHCWko')
>>> s = session.Session(auth=auth, verify=False)
>>> resp = s.get('http://localhost:9292/v2/images', headers={'Accept':
'application/json'})
>>> resp
>>> resp.request.headers
{'Connection': 'keep-alive', 'X-Auth-Token':
'gABZFFPxqrUAkNLOCDGalLVzYutnQoFXlAyCHuSbqOQPzzuFposxT806oJ3WUXd4gTnDkXNFVXCT10gd3fdVHBkIOqlI2pVh_Fba29FKz8knMRwXGaZaRCeZrnbbGGJsDHMlbLhXB11NM5iEKBHrhXQkWrFSHdfG7IyF00XLiFh2ag3hMICBQKSkenr--Wv3OosLuvFErzsQiKC-HYu04EqOSyiDNc9vRs0OIr9pNynF65NCyPM',
'Accept-Encoding': 'gzip, deflate', 'Accept': 'application/json',
'User-Agent': 'keystoneauth1/2.18.0 python-requests/2.10.0 CPython/2.7.5'}
GET /v3/auth/tokens
X-Subject-Token:
gABZFFPxqrUAkNLOCDGalLVzYutnQoFXlAyCHuSbqOQPzzuFposxT806oJ3WUXd4gTnDkXNFVXCT10gd3fdVHBkIOqlI2pVh_Fba29FKz8knMRwXGaZaRCeZrnbbGGJsDHMlbLhXB11NM5iEKBHrhXQkWrFSHdfG7IyF00XLiFh2ag3hMICBQKSkenr--Wv3OosLuvFErzsQiKC-HYu04EqOSyiDNc9vRs0OIr9pNynF65NCyPM
X-Auth-Token:
gABZFFOeoAYgNRrCDav6UHGM1Zo63kVk4V2mZ_7D41eCdiJUjw8xzo7eJxJR2vAxRaVljc_OUEErrmU9FsTh6OJi01w9D5hc-pAZPlHzZm-fmExPrEHUZQ1Uz9BI31UpDq_iNg4Im2m1cU8xiBdcUpJZeYKh6gxvL95MMlnttCle5u9y15UDB0I2QY2Sy1LEQ9UoEXVO4wk5M4KgOhVRdF36hEY8dpeH0Zo-MB6N6LqiNvHCWko
Response:
{"token": {"issued_at": "2017-05-11T12:07:13.00Z", "audit_ids":
["_0-Hir4UTS-ATQmbiOP0Wg", "Zh4SNR-jREugwuoxGXL4wg"], "user": {"id":
"0688b01e6439ca32d698d20789d52169126fb41fb1a4ddafcebb97d854e836c9", "domain":
{"id": "default", "name": "Default"}, "password_expires_at": null, "name":
"root"}, "expires_at": "2017-05-11T18:05:50.00Z", "methods": ["token",
"password"]}}
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1690203/+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 1673613] Re: Special characters are not allowed in connection string
** Also affects: nova/ocata
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/1673613
Title:
Special characters are not allowed in connection string
Status in OpenStack Compute (nova):
Confirmed
Status in OpenStack Compute (nova) ocata series:
New
Bug description:
I installed ocata on a three node config (one controller, two
compute). When executing
openstack server list
on the controller node, I get
Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/
and attach the Nova API log if possible.
(HTTP 500) (Request-ID:
req-7544be6c-3302-4a94-94ac-834a50696ac6)
openstack --debug server list
START with options: [u'--debug', u'server', u'list']
options: Namespace(access_key='', access_secret='***', access_token='***',
access_token_endpoint='', access_token_type='', aodh_endpoint='', auth_type='',
auth_url='http://controller:35357/v3', cacert=None, cert='', client_id='',
client_secret='***', cloud='', code='', consumer_key='', consumer_secret='***',
debug=True, default_domain='default', default_domain_id='',
default_domain_name='', deferred_help=False, discovery_endpoint='',
domain_id='', domain_name='', endpoint='', identity_provider='',
identity_provider_url='', insecure=None, interface='', key='', log_file=None,
old_profile=None, openid_scope='', os_alarming_api_version='2',
os_beta_command=False, os_clustering_api_version='1',
os_compute_api_version='', os_container_infra_api_version='1',
os_data_processing_api_version='1.1', os_data_processing_url='',
os_database_api_version='1', os_dns_api_version='2',
os_identity_api_version='3', os_image_api_version='2',
os_key_manager_api_version='1', os_network_api_version='', os
_object_api_version='', os_orchestration_api_version='1', os_project_id=None,
os_project_name=None, os_queues_api_version='2', os_volume_api_version='',
os_workflow_api_version='2', passcode='', password='***', profile=None,
project_domain_id='', project_domain_name='default', project_id='',
project_name='admin', protocol='', redirect_uri='', region_name='RegionOne',
roles='', timing=False, token='***', trust_id='', url='', user_domain_id='',
user_domain_name='default', user_id='', username='admin', verbose_level=3,
verify=None)
Auth plugin password selected
auth_config_hook(): {'auth_type': 'password', 'beta_command': False,
u'compute_api_version': u'2', 'key': None, u'database_api_version': '1',
'data_processing_api_version': '1.1', 'auth_url': 'http://controller:35357/v3',
u'network_api_version': u'2', u'message': u'', u'image_format': u'qcow2',
'networks': [], u'image_api_version': '2', 'clustering_api_version': '1',
'verify': True, u'dns_api_version': '2', u'object_store_api_version': u'1',
'username': 'admin', u'container_infra_api_version': '1', 'verbose_level': 3,
'region_name': 'RegionOne', 'api_timeout': None, u'baremetal_api_version':
u'1', 'queues_api_version': '2', 'auth': {'user_domain_name': 'default',
'project_name': 'admin', 'project_domain_name': 'default'}, 'default_domain':
'default', u'container_api_version': u'1', u'image_api_use_tasks': False,
u'floating_ip_source': u'neutron', u'orchestration_api_version': '1', 'timing':
False, 'password': '***', u'application_catalog_api_version': u'1', 'cacert':
None, u'key_ma
nager_api_version': '1', u'metering_api_version': u'2', 'deferred_help':
False, u'identity_api_version': '3', 'workflow_api_version': '2',
u'volume_api_version': u'2', 'cert': None, u'secgroup_source': u'neutron',
u'status': u'active', 'alarming_api_version': '2', 'debug': True, u'interface':
None, u'disable_vendor_agent': {}}
defaults: {u'auth_type': 'password', u'status': u'active',
u'compute_api_version': u'2', 'key': None, u'database_api_version': u'1.0',
'api_timeout': None, u'baremetal_api_version': u'1', u'image_api_version':
u'2', u'container_infra_api_version': u'1', u'metering_api_version': u'2',
u'image_api_use_tasks': False, u'floating_ip_source': u'neutron',
u'orchestration_api_version': u'1', 'cacert': None, u'network_api_version':
u'2', u'message': u'', u'image_format': u'qcow2',
u'application_catalog_api_version': u'1', u'key_manager_api_version': u'v1',
'verify': True, u'identity_api_version': u'2.0', u'volume_api_version': u'2',
'cert': None, u'secgroup_source': u'neutron', u'container_api_version': u'1',
u'dns_api_version': u'2', u'object_store_api_version': u'1', u'interface':
None, u'disable_vendor_agent': {}}
cloud cfg: {'auth_type': 'password', 'beta_command': False,
u'compute_api_version': u'2', 'key': None, u'database_api_version': '1',
'data_processing_api_version': '1.1', 'auth_url': 'http://controller:35357/v3',
u'network_api_version': u'2', u'message': u'', u'image_format': u'qcow2',
'networks': [], u'image_api_version': '2', 'clustering_api_version':
[Yahoo-eng-team] [Bug 1690203] [NEW] token data doesn't have roles, projects and catalog information
Public bug reported:
Token which is generated using keystoneauth1.session.get/post doesn't
have roles, project and catalog information.
>>> from keystoneauth1 import session
>>> from keystoneauth1 import identity
>>> auth = identity.v3.Token('https://localhost:5000/v3',
>>> 'gABZFFOeoAYgNRrCDav6UHGM1Zo63kVk4V2mZ_7D41eCdiJUjw8xzo7eJxJR2vAxRaVljc_OUEErrmU9FsTh6OJi01w9D5hc-pAZPlHzZm-fmExPrEHUZQ1Uz9BI31UpDq_iNg4Im2m1cU8xiBdcUpJZeYKh6gxvL95MMlnttCle5u9y15UDB0I2QY2Sy1LEQ9UoEXVO4wk5M4KgOhVRdF36hEY8dpeH0Zo-MB6N6LqiNvHCWko')
>>> s = session.Session(auth=auth, verify=False)
>>> resp = s.get('http://localhost:9292/v2/images', headers={'Accept':
>>> 'application/json'})
>>> resp
>>> resp.request.headers
{'Connection': 'keep-alive', 'X-Auth-Token':
'gABZFFPxqrUAkNLOCDGalLVzYutnQoFXlAyCHuSbqOQPzzuFposxT806oJ3WUXd4gTnDkXNFVXCT10gd3fdVHBkIOqlI2pVh_Fba29FKz8knMRwXGaZaRCeZrnbbGGJsDHMlbLhXB11NM5iEKBHrhXQkWrFSHdfG7IyF00XLiFh2ag3hMICBQKSkenr--Wv3OosLuvFErzsQiKC-HYu04EqOSyiDNc9vRs0OIr9pNynF65NCyPM',
'Accept-Encoding': 'gzip, deflate', 'Accept': 'application/json',
'User-Agent': 'keystoneauth1/2.18.0 python-requests/2.10.0 CPython/2.7.5'}
GET /v3/auth/tokens
X-Subject-Token:
gABZFFPxqrUAkNLOCDGalLVzYutnQoFXlAyCHuSbqOQPzzuFposxT806oJ3WUXd4gTnDkXNFVXCT10gd3fdVHBkIOqlI2pVh_Fba29FKz8knMRwXGaZaRCeZrnbbGGJsDHMlbLhXB11NM5iEKBHrhXQkWrFSHdfG7IyF00XLiFh2ag3hMICBQKSkenr--Wv3OosLuvFErzsQiKC-HYu04EqOSyiDNc9vRs0OIr9pNynF65NCyPM
X-Auth-Token:
gABZFFOeoAYgNRrCDav6UHGM1Zo63kVk4V2mZ_7D41eCdiJUjw8xzo7eJxJR2vAxRaVljc_OUEErrmU9FsTh6OJi01w9D5hc-pAZPlHzZm-fmExPrEHUZQ1Uz9BI31UpDq_iNg4Im2m1cU8xiBdcUpJZeYKh6gxvL95MMlnttCle5u9y15UDB0I2QY2Sy1LEQ9UoEXVO4wk5M4KgOhVRdF36hEY8dpeH0Zo-MB6N6LqiNvHCWko
Response:
{"token": {"issued_at": "2017-05-11T12:07:13.00Z", "audit_ids":
["_0-Hir4UTS-ATQmbiOP0Wg", "Zh4SNR-jREugwuoxGXL4wg"], "user": {"id":
"0688b01e6439ca32d698d20789d52169126fb41fb1a4ddafcebb97d854e836c9", "domain":
{"id": "default", "name": "Default"}, "password_expires_at": null, "name":
"root"}, "expires_at": "2017-05-11T18:05:50.00Z", "methods": ["token",
"password"]}}
** Affects: keystoneauth
Importance: Undecided
Status: New
** Description changed:
- Token which are generated using keystoneauth1.session.get/post doesn't
+ Token which is generated using keystoneauth1.session.get/post doesn't
have roles, project and catalog information.
>>> from keystoneauth1 import session
>>> from keystoneauth1 import identity
>>> auth = identity.v3.Token('https://localhost:5000/v3',
'gABZFFOeoAYgNRrCDav6UHGM1Zo63kVk4V2mZ_7D41eCdiJUjw8xzo7eJxJR2vAxRaVljc_OUEErrmU9FsTh6OJi01w9D5hc-pAZPlHzZm-fmExPrEHUZQ1Uz9BI31UpDq_iNg4Im2m1cU8xiBdcUpJZeYKh6gxvL95MMlnttCle5u9y15UDB0I2QY2Sy1LEQ9UoEXVO4wk5M4KgOhVRdF36hEY8dpeH0Zo-MB6N6LqiNvHCWko')
>>> s = session.Session(auth=auth, verify=False)
>>> resp = s.get('http://localhost:9292/v2/images', headers={'Accept':
'application/json'})
>>> resp
>>> resp.request.headers
{'Connection': 'keep-alive', 'X-Auth-Token':
'gABZFFPxqrUAkNLOCDGalLVzYutnQoFXlAyCHuSbqOQPzzuFposxT806oJ3WUXd4gTnDkXNFVXCT10gd3fdVHBkIOqlI2pVh_Fba29FKz8knMRwXGaZaRCeZrnbbGGJsDHMlbLhXB11NM5iEKBHrhXQkWrFSHdfG7IyF00XLiFh2ag3hMICBQKSkenr--Wv3OosLuvFErzsQiKC-HYu04EqOSyiDNc9vRs0OIr9pNynF65NCyPM',
'Accept-Encoding': 'gzip, deflate', 'Accept': 'application/json',
'User-Agent': 'keystoneauth1/2.18.0 python-requests/2.10.0 CPython/2.7.5'}
-
GET /v3/auth/tokens
X-Subject-Token:
gABZFFPxqrUAkNLOCDGalLVzYutnQoFXlAyCHuSbqOQPzzuFposxT806oJ3WUXd4gTnDkXNFVXCT10gd3fdVHBkIOqlI2pVh_Fba29FKz8knMRwXGaZaRCeZrnbbGGJsDHMlbLhXB11NM5iEKBHrhXQkWrFSHdfG7IyF00XLiFh2ag3hMICBQKSkenr--Wv3OosLuvFErzsQiKC-HYu04EqOSyiDNc9vRs0OIr9pNynF65NCyPM
X-Auth-Token:
gABZFFOeoAYgNRrCDav6UHGM1Zo63kVk4V2mZ_7D41eCdiJUjw8xzo7eJxJR2vAxRaVljc_OUEErrmU9FsTh6OJi01w9D5hc-pAZPlHzZm-fmExPrEHUZQ1Uz9BI31UpDq_iNg4Im2m1cU8xiBdcUpJZeYKh6gxvL95MMlnttCle5u9y15UDB0I2QY2Sy1LEQ9UoEXVO4wk5M4KgOhVRdF36hEY8dpeH0Zo-MB6N6LqiNvHCWko
- Response:
+ Response:
{"token": {"issued_at": "2017-05-11T12:07:13.00Z", "audit_ids":
["_0-Hir4UTS-ATQmbiOP0Wg", "Zh4SNR-jREugwuoxGXL4wg"], "user": {"id":
"0688b01e6439ca32d698d20789d52169126fb41fb1a4ddafcebb97d854e836c9", "domain":
{"id": "default", "name": "Default"}, "password_expires_at": null, "name":
"root"}, "expires_at": "2017-05-11T18:05:50.00Z", "methods": ["token",
"password"]}}
** Project changed: keystone => keystoneauth
--
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/1690203
Title:
token data doesn't have roles, projects and catalog information
Status in keystoneauth:
New
Bug description:
Token which is generated using keystoneauth1.session.get/post doesn't
have roles, project and catalog information.
>>> from keystoneauth1 import session
>>> from keystoneauth1 import identity
>>> auth = identity.v3.Token('https://localhost:
[Yahoo-eng-team] [Bug 1421550] Re: Creating VM image fails under the race condition with detaching volume
Reviewed: https://review.openstack.org/383859 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4aa39c44a4b08ee4e05548d5c258e795089b2bdd Submitter: Jenkins Branch:master commit 4aa39c44a4b08ee4e05548d5c258e795089b2bdd Author: Matthew Booth Date: Fri Oct 7 19:14:38 2016 +0100 libvirt: Fix races with nfs volume mount/umount A single nfs export typically contains multiple volumes. We were handling this in the libvirt driver by: 1. On mount, we 'ensure' the mount is available, so we don't fail if another instance already has it mounted. 2. On umount, we trap and ignore 'device is busy' so we don't fail if another instance is already using it. Unfortunately, while this works for serial mounts and unmounts, there are multiple failure cases when volumes from the same export are mounted and unmounted simultaneously. It causes an error if an instance is stopped: as the qemu process is not actively using the mountpoint it will not prevent an unmount for another volume on the same mountpoint from succeeding. It will not be possible to restart the instance, because its mountpoint will not be mounted. To fix this, we create a singleton manager object, which tracks mounts and umount requests per export, and calls the real mount/umount only when required. It uses per-export locks to allow concurrency while avoiding races. Because we now expect to know the state of the host at all times, we no longer need to execute speculative mount/umount commands. As we track attachments (a mapping from volume to instance) rather than volumes, we also gracefully support multi-attach. This change implements this for nfs, but the solution is intended to be extended to all LibvirtBaseFileSystemVolumeDrivers. Closes-Bug: #1421550 Change-Id: I3155984d76df06371a6c45f633aa448168a96d64 ** 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/1421550 Title: Creating VM image fails under the race condition with detaching volume Status in OpenStack Compute (nova): Fix Released Bug description: Environment: nova 2014.2.1 cinder 2014.2.1 Ubuntu 14.04 LTS Cinder volumes whose backend is NFS are used. There are two 'ACTIVE' VM instances on the same compute node. Creating VM image(VM snapshot) fails under the race condition with detaching volume for the other VM instance. In creating VM image, starting VM instance fails(remains 'SHUTOFF' state) and the VM image is deleted. nova-compute's log is as follows: --- 2015-01-26 10:28:47,000.744 11535 ERROR nova.virt.libvirt.driver [req-7ee6f579-63f5-4822-a2b3-10e53bb1dce0 None] Error launching a defined domain with XML: (snipped...) 2015-01-26 10:28:47,000.767 11535 DEBUG nova.compute.manager [req-7ee6f579-63f5-4822-a2b3-10e53bb1dce0 None] [instance: d613cfc9-109a-4920-bbc1-41ce4146ace0] Cleaning up image e8c3255c-b4e8-4324-addb-365c5d7b1868 decorated_function /usr/lib/python2.7/dist-packages/nova/compute/manager.py:373 2015-01-26 10:28:47,000.767 11535 TRACE nova.compute.manager [instance: d613cfc9-109a-4920-bbc1-41ce4146ace0] Traceback (most recent call last): 2015-01-26 10:28:47,000.767 11535 TRACE nova.compute.manager [instance: d613cfc9-109a-4920-bbc1-41ce4146ace0] File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 369, in decorated_function 2015-01-26 10:28:47,000.767 11535 TRACE nova.compute.manager [instance: d613cfc9-109a-4920-bbc1-41ce4146ace0] *args, **kwargs) 2015-01-26 10:28:47,000.767 11535 TRACE nova.compute.manager [instance: d613cfc9-109a-4920-bbc1-41ce4146ace0] File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 3027, in snapshot_instance 2015-01-26 10:28:47,000.767 11535 TRACE nova.compute.manager [instance: d613cfc9-109a-4920-bbc1-41ce4146ace0] task_states.IMAGE_SNAPSHOT) 2015-01-26 10:28:47,000.767 11535 TRACE nova.compute.manager [instance: d613cfc9-109a-4920-bbc1-41ce4146ace0] File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 3058, in _snapshot_instance 2015-01-26 10:28:47,000.767 11535 TRACE nova.compute.manager [instance: d613cfc9-109a-4920-bbc1-41ce4146ace0] update_task_state) 2015-01-26 10:28:47,000.767 11535 TRACE nova.compute.manager [instance: d613cfc9-109a-4920-bbc1-41ce4146ace0] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 1733, in snapshot 2015-01-26 10:28:47,000.767 11535 TRACE nova.compute.manager [instance: d613cfc9-109a-4920-bbc1-41ce4146ace0] new_dom = self._create_domain(domain=virt_dom) 2015-01-26 10:28:47,000.767 11535
[Yahoo-eng-team] [Bug 1623168] Re: referencing versionutils.deprecated.NEWTON in oslo.log <3.4.0
** Changed in: cinder Status: In Progress => Fix Released -- 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/1623168 Title: referencing versionutils.deprecated.NEWTON in oslo.log <3.4.0 Status in Cinder: Fix Released Status in OpenStack Identity (keystone): Fix Released Bug description: cinder/keymgr/__init__.py contains: versionutils.deprecation_warning(deprecated, versionutils.NEWTON, in_favor_of=castellan, logger=LOG) versionutils.NEWTON does not exist until oslo.log 3.4.0, but Cinder Newton only requires oslo.log>=1.14.0. It is too late in Newton to bump the global requirements for a newer oslo.log. ( https://review.openstack.org/#/c/366418/ ) To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1623168/+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 1690165] [NEW] Gratutuious ARP updates sent by Neutron L3 agent may be ignored by Linux peers
Public bug reported: An ufortunate scenario in Linux kernel explained in https://patchwork.ozlabs.org/patch/760372/ may result in no gARP being honoured by Linux network peers. To work the kernel bug around, we may want to spread updates more, not to hit default kernel locktime which is 1s. ** Affects: neutron Importance: High Assignee: Ihar Hrachyshka (ihar-hrachyshka) Status: In Progress ** Tags: l3-ha l3-ipam-dhcp ** Changed in: neutron Status: New => Confirmed ** Changed in: neutron Assignee: (unassigned) => Ihar Hrachyshka (ihar-hrachyshka) ** Changed in: neutron Importance: Undecided => High ** Tags added: l3-ha l3-ipam-dhcp -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1690165 Title: Gratutuious ARP updates sent by Neutron L3 agent may be ignored by Linux peers Status in neutron: In Progress Bug description: An ufortunate scenario in Linux kernel explained in https://patchwork.ozlabs.org/patch/760372/ may result in no gARP being honoured by Linux network peers. To work the kernel bug around, we may want to spread updates more, not to hit default kernel locktime which is 1s. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1690165/+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 1512880] Re: Failed cold migration with SR-IOV
** Changed in: nova/newton
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/1512880
Title:
Failed cold migration with SR-IOV
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) newton series:
Fix Released
Bug description:
Cold migration of an instance that has an SR-IOV interface fails to
migrate because on migrated compute's nova is trying to use the PCI
device/address that has been allocated from the incoming compute.
Obviously this is failing since the PCI device is not present on the
migrated compute.
See the error "libvirtError: Device :83:10.6 not found: could not
access /sys/bus/pci/devices/:83:10.6/config: No such file or
directory" in the log in the attachment.
Nova should allocate a new PCI device based the hardware configuration
of the compute where the instance is being migrated and this PCI
device should be use to create the instance XML.
Nova version:
commit 2397d636ff6ea3767fe62ee681d609fce4fc98ca
Author: OpenStack Proposal Bot
Date: Tue Oct 27 06:30:34 2015 +
Imported Translations from Zanata
For more information about this automatic import see:
https://wiki.openstack.org/wiki/Translations/Infrastructure
Change-Id: I38f537e37972e5ddae13d388021412d85f6be898
Devstack setup:
* One server configured with controller and compute functions
* Intel 10G port is configured with 8 VFs: $ echo 8 >
/sys/bus/pci/devices/\:85\:00.0/sriov_numvfs
* /etc/nova/nova.conf: pci_passthrough_whitelist =
{"address":"*:85:10.*","physical_network":"default"}
* One server configured with compute function only
* Intel 10G port is configured with 8 VFs: $ echo 8 >
/sys/bus/pci/devices/\:83\:00.0/sriov_numvfs
* /etc/nova/nova.conf: pci_passthrough_whitelist =
{"address":"*:83:10.*","physical_network":"default"}
* Note that it is important for this test that the PCI addresses for the
SR-IOV interfaces are different. We want to validate that new PCI devices are
claimed/allocated on the incoming compute.
Reproduce steps:
1) Boot an instance with an SR-IOV interface:
$ NETID=`neutron net-list | grep default | awk '{print $2}'`
$ neutron port-create $NETID --binding:vnic-type direct --name p-direct
$ PORTID=`neutron port-list | grep "p-direct" | awk '{print $2}'`
$ nova boot test --image=ubuntu --nic port-id=$PORTID --flavor=m1.small
2) Migrate the instance to the other compute:
$ nova migrate test
Expected result:
The instance is successfully migrated on the other server.
Actual result:
The instance failed to migrate. Instance is stuck in error. See log
in attachment for more information.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1512880/+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 1690102] [NEW] "...please file a bug against cloud-init..."
Public bug reported: My system requested me to report a bug according to this login message: ** # A new feature in cloud-init identified possible datasources for# # this system as:# # ['Ec2', 'None'] # # However, the datasource used was: CloudStack # ## # In the future, cloud-init will only attempt to use datasources that# # are identified or specifically configured. # # For more information see # # https://bugs.launchpad.net/bugs/1669675 # ## # If you are seeing this message, please file a bug against # # cloud-init at # #https://bugs.launchpad.net/cloud-init/+filebug?field.tags=dsid # # Make sure to include the cloud provider your instance is # # running on.# ## # After you have filed a bug, you can disable this warning by launching # # your instance with the cloud-config below, or putting that content # # into /etc/cloud/cloud.cfg.d/99-warnings.cfg# ## # #cloud-config # # warnings: # # dsid_missing_source: off # ** This VPS is running: Linux hostname 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename: xenial cloud-init 0.7.9 0.7.9-48-g1c795b9-0ubuntu1~16.04.1 VPS provider is: https://www.pcextreme.nl ** Affects: cloud-init Importance: Undecided Status: New ** Tags: dsid -- 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/1690102 Title: "...please file a bug against cloud-init..." Status in cloud-init: New Bug description: My system requested me to report a bug according to this login message: ** # A new feature in cloud-init identified possible datasources for# # this system as:# # ['Ec2', 'None'] # # However, the datasource used was: CloudStack # ## # In the future, cloud-init will only attempt to use datasources that# # are identified or specifically configured. # # For more information see # # https://bugs.launchpad.net/bugs/1669675 # ## # If you are seeing this message, please file a bug against # # cloud-init at # #https://bugs.launchpad.net/cloud-init/+filebug?field.tags=dsid # # Make sure to include the cloud provider your instance is # # running on.# ## # After you have filed a bug, you can disable this warning by launching # # your instance with the cloud-config below, or putting that content # # into /etc/cloud/cloud.cfg.d/99-warnings.cfg# ## # #cloud-config # # warnings: # # dsid_missing_source: off # ** This VPS is running: Linux hostname 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description: Ubuntu 16.04.2 LTS Release: 16.04 Codename: xenial cloud-init 0.7.9 0.7.9-48-g1c795b9-0ubuntu1~16.04.1 VPS provider is: https://w
[Yahoo-eng-team] [Bug 1690098] [NEW] Remove log translations
Public bug reported: The i18n team has decided not to translate the logs because it seems like it not very useful; operators prefer to have them in English so that they can search for those strings on the internet. See: http://lists.openstack.org/pipermail/openstack-i18n/2016-November/002574.html http://lists.openstack.org/pipermail/openstack-dev/2017-March/113365.html ** Affects: glance Importance: Undecided Assignee: Ngo Quoc Cuong (cuongnq) Status: New ** Tags: i18n ** Changed in: glance Assignee: (unassigned) => Ngo Quoc Cuong (cuongnq) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1690098 Title: Remove log translations Status in Glance: New Bug description: The i18n team has decided not to translate the logs because it seems like it not very useful; operators prefer to have them in English so that they can search for those strings on the internet. See: http://lists.openstack.org/pipermail/openstack-i18n/2016-November/002574.html http://lists.openstack.org/pipermail/openstack-dev/2017-March/113365.html To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1690098/+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 1469498] Re: LbaasV2 session persistence- Create and update
Seeing the issue again on ocata
** Changed in: neutron
Status: Expired => 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/1469498
Title:
LbaasV2 session persistence- Create and update
Status in neutron:
New
Bug description:
When we create a Lbaas pool with session persistence it configured OK
neutron lbaas-pool-create --session-persistence type=HTTP_COOKIE
--lb-algorithm LEAST_CONNECTIONS --listener
4658a507-dccc-41f9-87d7-913d31cab3a1 --protocol HTTP
Created a new pool:
+-++
| Field | Value |
+-++
| admin_state_up | True |
| description ||
| healthmonitor_id||
| id | a626dc28-0126-48f7-acd3-f486827a89c1 |
| lb_algorithm| LEAST_CONNECTIONS |
| listeners | {"id": "4658a507-dccc-41f9-87d7-913d31cab3a1"} |
| members ||
| name||
| protocol| HTTP |
| session_persistence | {"cookie_name": null, "type": "HTTP_COOKIE"} |
| tenant_id | ae0954b9cf0c438e99211227a7f3f937 |
BUT, when we create a pool without session persistence and update it
to do session persistence, the action is different and not user
friendly.
[root@puma09 ~(keystone_redhat)]# neutron lbaas-pool-create --lb-algorithm
LEAST_CONNECTIONS --listener 4658a507-dccc-41f9-87d7-913d31cab3a1 --protocol
HTTP
Created a new pool:
+-++
| Field | Value |
+-++
| admin_state_up | True |
| description ||
| healthmonitor_id||
| id | b9048a69-461a-4503-ba6b-8a2df281f804 |
| lb_algorithm| LEAST_CONNECTIONS |
| listeners | {"id": "4658a507-dccc-41f9-87d7-913d31cab3a1"} |
| members ||
| name||
| protocol| HTTP |
| session_persistence ||
| tenant_id | ae0954b9cf0c438e99211227a7f3f937 |
+-++
[root@puma09 ~(keystone_redhat)]# neutron lbaas-pool-update
b9048a69-461a-4503-ba6b-8a2df281f804 --session-persistence type=HTTP_COOKIE
name 'HTTP_COOKIE' is not defined
[root@puma09 ~(keystone_redhat)]#
we need to configure it in the following way-
neutron lbaas-pool-update b9048a69-461a-4503-ba6b-8a2df281f804
--session-persistence type=dict type=HTTP_COOKIE
Updated pool: b9048a69-461a-4503-ba6b-8a2df281f804
The config and update should be done in same way.
Kilo+ rhel 7.1
openstack-neutron-common-2015.1.0-10.el7ost.noarch
python-neutron-lbaas-2015.1.0-5.el7ost.noarch
openstack-neutron-openvswitch-2015.1.0-10.el7ost.noarch
python-neutronclient-2.4.0-1.el7ost.noarch
openstack-neutron-lbaas-2015.1.0-5.el7ost.noarch
python-neutron-fwaas-2015.1.0-3.el7ost.noarch
openstack-neutron-fwaas-2015.1.0-3.el7ost.noarch
python-neutron-2015.1.0-10.el7ost.noarch
openstack-neutron-2015.1.0-10.el7ost.noarch
openstack-neutron-ml2-2015.1.0-10.el7ost.noarch
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1469498/+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
