[Yahoo-eng-team] [Bug 1396781] Re: Error in Database Population script for Neutron
Okay Gary, this is documented as it should be in the Juno guide. Typically we won't keep the trunk version of the guide updated as most people are installing a stable version. Matt has done lots of installs and can help you troubleshoot. ** No longer affects: neutron ** Changed in: openstack-manuals Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1396781 Title: Error in Database Population script for Neutron Status in OpenStack Manuals: Won't Fix Bug description: In the 'to finalise installation' section the following script is used su -s /bin/sh -c "neutron-db-manage --config-file /etc/neutron/neutron.conf \ --config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade juno" neutron This reports an error as juno is unknown, to resolve this the script should be changed to su -s /bin/sh -c "neutron-db-manage --config-file /etc/neutron/neutron.conf \ --config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head" neutron An explanation should be added saying that 'head' is equivalent to the latest trunk release. --- Built: 2014-11-26T19:02:57 00:00 git SHA: 5595fde364e55699d2bf5e7b0aabdf9cdd154f00 URL: http://docs.openstack.org/juno/install-guide/install/apt/content/neutron-controller-node.html source File: file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishdocs/doc/install-guide/section_neutron-controller-node.xml xml:id: neutron-controller-node To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-manuals/+bug/1396781/+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 1395368] Re: ExternalNetworksTest[JSON, XML].test_delete_external_networks_with_floating_ip failures
Since https://review.openstack.org/#/c/135903/ is merged things seem to
be working again.
** No longer affects: keystonemiddleware
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1395368
Title:
ExternalNetworksTest[JSON,XML].test_delete_external_networks_with_floating_ip
failures
Status in OpenStack Neutron (virtual network service):
New
Status in Python client library for Glance:
New
Status in Tempest:
Incomplete
Bug description:
I'm unsure as to the root cause (looking through the basic neutron,
nova api logs didn't show much usefulness around the times these
failed)...
Here is the full log and link though:
http://logs.openstack.org/51/136551/2/check/gate-tempest-dsvm-neutron-
src-taskflow-icehouse/8e0bb9f/
2014-11-22 18:50:53.315 | {1}
tempest.api.network.admin.test_external_network_extension.ExternalNetworksTestJSON.test_delete_external_networks_with_floating_ip
[0.984493s] ... FAILED
ft333.2:
tempest.api.network.admin.test_external_network_extension.ExternalNetworksTestXML.test_delete_external_networks_with_floating_ip_StringException:
pythonlogging:'': {{{
2014-11-22 18:54:54,689 2113 DEBUG[tempest.common.rest_client] Request
(ExternalNetworksTestXML:test_delete_external_networks_with_floating_ip): 201
POST http://127.0.0.1:9696/v2.0/networks 0.080s
Request - Headers: {'Content-Type': 'application/xml', 'Accept':
'application/xml', 'X-Auth-Token': ''}
Body:
http://www.w3.org/2001/XMLSchema-instance";
xmlns:router="http://docs.openstack.org/ext/neutron/router/api/v1.0";>True
Response - Headers: {'status': '201', 'content-length': '805',
'connection': 'close', 'date': 'Sat, 22 Nov 2014 18:54:54 GMT', 'content-type':
'application/xml; charset=UTF-8', 'x-openstack-request-id':
'req-9d70cf16-d0ae-46e6-9f40-9c68cc50a2f0'}
Body:
http://openstack.org/quantum/api/v2.0";
xmlns:provider="http://docs.openstack.org/ext/provider/api/v1.0";
xmlns:quantum="http://openstack.org/quantum/api/v2.0";
xmlns:router="http://docs.openstack.org/ext/neutron/router/api/v1.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>ACTIVETruea3451f42641c4a3ab319253134e5a036localTrueFalse0b8004ad-7e9d-4b8c-9de1-efa8177f6dfc
2014-11-22 18:54:54,789 2113 DEBUG[tempest.common.rest_client] Request
(ExternalNetworksTestXML:test_delete_external_networks_with_floating_ip): 201
POST http://127.0.0.1:9696/v2.0/subnets 0.098s
Request - Headers: {'Content-Type': 'application/xml', 'Accept':
'application/xml', 'X-Auth-Token': ''}
Body:
http://www.w3.org/2001/XMLSchema-instance";>40b8004ad-7e9d-4b8c-9de1-efa8177f6dfc10.100.0.0/2810.100.0.1
Response - Headers: {'status': '201', 'content-length': '729',
'connection': 'close', 'date': 'Sat, 22 Nov 2014 18:54:54 GMT', 'content-type':
'application/xml; charset=UTF-8', 'x-openstack-request-id':
'req-4f27ac74-c53f-4dd7-bd90-7bb217c82626'}
Body:
http://openstack.org/quantum/api/v2.0";
xmlns:quantum="http://openstack.org/quantum/api/v2.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>True0b8004ad-7e9d-4b8c-9de1-efa8177f6dfca3451f42641c4a3ab319253134e5a03610.100.0.210.100.0.14410.100.0.110.100.0.0/2849d84272-4d7e-49fd-bf72-0dcf7c923db6
2014-11-22 18:54:54,877 2113 DEBUG[tempest.common.rest_client] Request
(ExternalNetworksTestXML:test_delete_external_networks_with_floating_ip): 201
POST http://127.0.0.1:9696/v2.0/floatingips 0.087s
Request - Headers: {'Content-Type': 'application/xml', 'Accept':
'application/xml', 'X-Auth-Token': ''}
Body:
http://www.w3.org/2001/XMLSchema-instance";>0b8004ad-7e9d-4b8c-9de1-efa8177f6dfc
Response - Headers: {'status': '201', 'content-length': '560',
'connection': 'close', 'date': 'Sat, 22 Nov 2014 18:54:54 GMT', 'content-type':
'application/xml; charset=UTF-8', 'x-openstack-request-id':
'req-f287a723-e173-4c69-b063-c0574860abfc'}
Body:
http://openstack.org/quantum/api/v2.0";
xmlns:quantum="http://openstack.org/quantum/api/v2.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>0b8004ad-7e9d-4b8c-9de1-efa8177f6dfc10.100.0.2a3451f42641c4a3ab319253134e5a036DOWNded008db-5868-45c9-9186-0b700211f0ef
2014-11-22 18:54:54,888 2113 DEBUG[tempest.common.rest_client] Request
(ExternalNetworksTestXML:test_delete_external_networks_with_floating_ip): 200
GET
http://127.0.0.1:9696/v2.0/floatingips?network=0b8004ad-7e9d-4b8c-9de1-efa8177f6dfc
0.009s
Request - Headers: {'Content-Type': 'application/xml', 'Accept':
'application/xml', 'X-Auth-Token': ''}
Body: None
Response - Headers: {'status': '200', 'content-length': '587',
'content-location':
'http://127.0.0.1:9696/v2.0/floatingips?network=0b8004ad-7e9d-4b8c-9de1-efa8177f6dfc',
'connection': 'close', 'date': 'Sat, 22 Nov 2014 18:54:54 GMT',
'content-type': 'application/xml; charset=
[Yahoo-eng-team] [Bug 1397549] [NEW] Attaching volumes with CHAP authentication fails on Hyper-V
Public bug reported: Attaching volumes fails on Hyper-V when the iSCSI when CHAP authentication is required. ** Affects: nova Importance: Medium Assignee: Petrut Lucian (petrutlucian94) Status: Fix Committed ** Tags: hyper-v ** Changed in: nova Assignee: (unassigned) => Petrut Lucian (petrutlucian94) ** Changed in: nova Importance: Undecided => Medium -- 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/1397549 Title: Attaching volumes with CHAP authentication fails on Hyper-V Status in OpenStack Compute (Nova): Fix Committed Bug description: Attaching volumes fails on Hyper-V when the iSCSI when CHAP authentication is required. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1397549/+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 1360139] Re: Live migration hosts dropbox should contain service host
*** This bug is a duplicate of bug 1335999 ***
https://bugs.launchpad.net/bugs/1335999
** This bug has been marked a duplicate of bug 1335999
live migration choosing wrong host names
--
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/1360139
Title:
Live migration hosts dropbox should contain service host
Status in OpenStack Dashboard (Horizon):
In Progress
Bug description:
To populate the available hosts in the live migration form, horizon
use hypervisor hostname else nova api want the service host, which is
not the same thing.
openstack_dashboard/dashboards/admin/instances/forms.py:
def populate_host_choices(self, request, initial):
hosts = initial.get('hosts')
current_host = initial.get('current_host')
host_list = [(host.hypervisor_hostname,
host.hypervisor_hostname)
for host in hosts
if host.service['host'] != current_host]
...
More details:
==
When using libvirt, this later when asked about hostname i.e. "$ virsh
hostname", it will always return a fqdn
(https://github.com/c4milo/libvirt/blob/0eac9d1e90fc3388030c6109aeb1f4860f108054/src/libvirt.c#L1610),
which is what nova will set as hypervisor_hostname
(https://github.com/openstack/nova/blob/f0a43555b79fe3161933bc01d6bb79f1e622bec2/nova/virt/libvirt/driver.py#L4008)
in the NovaCompute table
(https://github.com/openstack/nova/blob/f0a43555b79fe3161933bc01d6bb79f1e622bec2/nova/db/sqlalchemy/models.py#L97).
In the other hand the service (nova-manage service list) will return the host
as the hostname of the compute node i.e. "$ hostname
"
(https://github.com/openstack/nova/blob/f0a43555b79fe3161933bc01d6bb79f1e622bec2/nova/db/sqlalchemy/models.py#L67).
In platform that make a difference between hostname and fqdn i.e. a
call to "$ hostname" and "$ hostname -f" return different things, both
fields service.host != compute_node. hypervisor_hostname will be
different.
As for Nova API, this later accept the service.host, at least that how
it validate the destination host passed
(https://github.com/openstack/nova/blob/f0a43555b79fe3161933bc01d6bb79f1e622bec2/nova/conductor/tasks/live_migrate.py#L85
https://github.com/openstack/nova/blob/f0a43555b79fe3161933bc01d6bb79f1e622bec2/nova/db/sqlalchemy/api.py#L488)
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1360139/+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 1397504] [NEW] In LBaas, delete the pool at the same time direct delete member is not reasonable
Public bug reported: For the user, the member is free from the pool of objects, so delete binding member pool, can't delete the pool and member directly, and should be deleted after the member, then delete the pool.Or,should delete with the prompts. ** Affects: neutron Importance: Undecided Status: New ** Tags: lbaas ** Summary changed: - Delete the pool at the same time deleted member without prompting + delete the pool at the same time direct delete member is not reasonable ** Summary changed: - delete the pool at the same time direct delete member is not reasonable + In LBaas,delete the pool at the same time direct delete member is not reasonable ** Tags added: lbaas -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1397504 Title: In LBaas,delete the pool at the same time direct delete member is not reasonable Status in OpenStack Neutron (virtual network service): New Bug description: For the user, the member is free from the pool of objects, so delete binding member pool, can't delete the pool and member directly, and should be deleted after the member, then delete the pool.Or,should delete with the prompts. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1397504/+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
