[Yahoo-eng-team] [Bug 1397239] [NEW] API comments mismatch for get_ports_from_devices
Public bug reported: get_ports_from_devices in ml2/plugin.py will return a emtry dict when the secgroup associated is empty, due to this line ports = db.get_ports_and_sgs(port_ids) but refer to the comment in neutron/db/securitygroups_rpc_base.py, seems it should at least return a dict whose secgroup's value is emtry def get_port_from_device(self, device): Get port dict from device name on an agent. Subclass must provide this method or get_ports_from_devices. :param device: device name which identifies a port on the agent side. What is specified in device depends on a plugin agent implementation. For example, it is a port ID in OVS agent and netdev name in Linux Bridge agent. :return: port dict returned by DB plugin get_port(). In addition, it must contain the following fields in the port dict returned. - device - security_groups - security_group_rules, - security_group_source_groups - fixed_ips ** Affects: neutron Importance: Undecided Assignee: yalei wang (yalei-wang) Status: New ** Changed in: neutron Assignee: (unassigned) = yalei wang (yalei-wang) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1397239 Title: API comments mismatch for get_ports_from_devices Status in OpenStack Neutron (virtual network service): New Bug description: get_ports_from_devices in ml2/plugin.py will return a emtry dict when the secgroup associated is empty, due to this line ports = db.get_ports_and_sgs(port_ids) but refer to the comment in neutron/db/securitygroups_rpc_base.py, seems it should at least return a dict whose secgroup's value is emtry def get_port_from_device(self, device): Get port dict from device name on an agent. Subclass must provide this method or get_ports_from_devices. :param device: device name which identifies a port on the agent side. What is specified in device depends on a plugin agent implementation. For example, it is a port ID in OVS agent and netdev name in Linux Bridge agent. :return: port dict returned by DB plugin get_port(). In addition, it must contain the following fields in the port dict returned. - device - security_groups - security_group_rules, - security_group_source_groups - fixed_ips To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1397239/+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 1397247] [NEW] test_notifications.py:test_send_on_vm_change
Public bug reported: in nova.tests.unit.test_notifications.py: the test_send_on_vm_change is just the same the test_send_task_change, we should change the test_send_on_vm_change: self.instance.task_state=task_state.SPAWING == self.instance.vm_state=vm_state.SUSPENDING ** 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/1397247 Title: test_notifications.py:test_send_on_vm_change Status in OpenStack Compute (Nova): New Bug description: in nova.tests.unit.test_notifications.py: the test_send_on_vm_change is just the same the test_send_task_change, we should change the test_send_on_vm_change: self.instance.task_state=task_state.SPAWING == self.instance.vm_state=vm_state.SUSPENDING To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1397247/+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 1396194] Re: test_dashboard_help_redirection intermittently fails with Element is not currently visible
https://review.openstack.org/#/c/109278/ should has no problem now ** Changed in: horizon Status: Confirmed = Invalid -- 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/1396194 Title: test_dashboard_help_redirection intermittently fails with Element is not currently visible Status in OpenStack Dashboard (Horizon): Invalid Bug description: The integration test for the redirection sometimes fails with the following tracE: == 2014-11-25 02:38:11.596 | 2014-11-25 02:38:11.597 | ERROR: openstack_dashboard.test.integration_tests.tests.test_dashboard_help_redirection.TestDashboardHelp.test_dashboard_help_redirection 2014-11-25 02:38:11.597 | 2014-11-25 02:38:11.598 | -- 2014-11-25 02:38:11.629 | 2014-11-25 02:38:11.600 | _StringException: Traceback (most recent call last): 2014-11-25 02:38:11.629 | 2014-11-25 02:38:11.602 | File /opt/stack/new/horizon/openstack_dashboard/test/integration_tests/helpers.py, line 65, in tearDown 2014-11-25 02:38:11.630 | 2014-11-25 02:38:11.603 | self.home_pg.log_out() 2014-11-25 02:38:11.630 | 2014-11-25 02:38:11.605 | File /opt/stack/new/horizon/openstack_dashboard/test/integration_tests/pages/basepage.py, line 58, in log_out 2014-11-25 02:38:11.630 | 2014-11-25 02:38:11.606 | self.topbar.logout_link.click() 2014-11-25 02:38:11.630 | 2014-11-25 02:38:11.608 | File /opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/selenium/webdriver/remote/webelement.py, line 65, in click 2014-11-25 02:38:11.631 | 2014-11-25 02:38:11.609 | self._execute(Command.CLICK_ELEMENT) 2014-11-25 02:38:11.631 | 2014-11-25 02:38:11.611 | File /opt/stack/new/horizon/openstack_dashboard/test/integration_tests/webdriver.py, line 105, in _execute 2014-11-25 02:38:11.631 | 2014-11-25 02:38:11.612 | params) 2014-11-25 02:38:11.631 | 2014-11-25 02:38:11.614 | File /opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/selenium/webdriver/remote/webelement.py, line 385, in _execute 2014-11-25 02:38:11.631 | 2014-11-25 02:38:11.615 | return self._parent.execute(command, params) 2014-11-25 02:38:11.632 | 2014-11-25 02:38:11.617 | File /opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/selenium/webdriver/remote/webdriver.py, line 173, in execute 2014-11-25 02:38:11.632 | 2014-11-25 02:38:11.618 | self.error_handler.check_response(response) 2014-11-25 02:38:11.632 | 2014-11-25 02:38:11.620 | File /opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/selenium/webdriver/remote/errorhandler.py, line 166, in check_response 2014-11-25 02:38:11.632 | 2014-11-25 02:38:11.621 | raise exception_class(message, screen, stacktrace) 2014-11-25 02:38:11.632 | 2014-11-25 02:38:11.622 | ElementNotVisibleException: Message: Element is not currently visible and so may not be interacted with Noticed in at least 2 reviews: http://logs.openstack.org/78/109278/30/check/gate-horizon-dsvm-integration/5dfb069/console.html http://logs.openstack.org/96/133696/3/check/gate-horizon-dsvm-integration/5b8dc11/console.html To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1396194/+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 1396194] Re: test_dashboard_help_redirection intermittently fails with Element is not currently visible
Please don't close this bug. We want to find out why it happens and make the test more solid so that there are no more intermittent errors on the gate. The goal is to prevent patches from being randomly blocked, and to avoid having to type recheck at all in the first place. ** Changed in: horizon Status: Invalid = Confirmed -- 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/1396194 Title: test_dashboard_help_redirection intermittently fails with Element is not currently visible Status in OpenStack Dashboard (Horizon): Confirmed Bug description: The integration test for the redirection sometimes fails with the following tracE: == 2014-11-25 02:38:11.596 | 2014-11-25 02:38:11.597 | ERROR: openstack_dashboard.test.integration_tests.tests.test_dashboard_help_redirection.TestDashboardHelp.test_dashboard_help_redirection 2014-11-25 02:38:11.597 | 2014-11-25 02:38:11.598 | -- 2014-11-25 02:38:11.629 | 2014-11-25 02:38:11.600 | _StringException: Traceback (most recent call last): 2014-11-25 02:38:11.629 | 2014-11-25 02:38:11.602 | File /opt/stack/new/horizon/openstack_dashboard/test/integration_tests/helpers.py, line 65, in tearDown 2014-11-25 02:38:11.630 | 2014-11-25 02:38:11.603 | self.home_pg.log_out() 2014-11-25 02:38:11.630 | 2014-11-25 02:38:11.605 | File /opt/stack/new/horizon/openstack_dashboard/test/integration_tests/pages/basepage.py, line 58, in log_out 2014-11-25 02:38:11.630 | 2014-11-25 02:38:11.606 | self.topbar.logout_link.click() 2014-11-25 02:38:11.630 | 2014-11-25 02:38:11.608 | File /opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/selenium/webdriver/remote/webelement.py, line 65, in click 2014-11-25 02:38:11.631 | 2014-11-25 02:38:11.609 | self._execute(Command.CLICK_ELEMENT) 2014-11-25 02:38:11.631 | 2014-11-25 02:38:11.611 | File /opt/stack/new/horizon/openstack_dashboard/test/integration_tests/webdriver.py, line 105, in _execute 2014-11-25 02:38:11.631 | 2014-11-25 02:38:11.612 | params) 2014-11-25 02:38:11.631 | 2014-11-25 02:38:11.614 | File /opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/selenium/webdriver/remote/webelement.py, line 385, in _execute 2014-11-25 02:38:11.631 | 2014-11-25 02:38:11.615 | return self._parent.execute(command, params) 2014-11-25 02:38:11.632 | 2014-11-25 02:38:11.617 | File /opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/selenium/webdriver/remote/webdriver.py, line 173, in execute 2014-11-25 02:38:11.632 | 2014-11-25 02:38:11.618 | self.error_handler.check_response(response) 2014-11-25 02:38:11.632 | 2014-11-25 02:38:11.620 | File /opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/selenium/webdriver/remote/errorhandler.py, line 166, in check_response 2014-11-25 02:38:11.632 | 2014-11-25 02:38:11.621 | raise exception_class(message, screen, stacktrace) 2014-11-25 02:38:11.632 | 2014-11-25 02:38:11.622 | ElementNotVisibleException: Message: Element is not currently visible and so may not be interacted with Noticed in at least 2 reviews: http://logs.openstack.org/78/109278/30/check/gate-horizon-dsvm-integration/5dfb069/console.html http://logs.openstack.org/96/133696/3/check/gate-horizon-dsvm-integration/5b8dc11/console.html To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1396194/+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 1387665] Re: Exception in 'System information' results in error code 500
Marking this bug as an invalid, because it is caused by problems in deb-
package (missing egg-info) and is not related to the upstream code.
** Changed in: horizon
Status: In Progress = Invalid
** Changed in: horizon
Importance: Medium = Undecided
** Changed in: horizon
Assignee: Vlad Okhrimenko (vokhrimenko) = (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/1387665
Title:
Exception in 'System information' results in error code 500
Status in OpenStack Dashboard (Horizon):
Invalid
Bug description:
When deploying (via Mirantis Fuel) Ubuntu cluster in 'simple' mode
with nova-network (flat-dhcp): 1 controller , 1 compute. Login to
Horizon and try to open Admin-System information page. We get
error code 500
To reproduce this behavior in devstack:
1. Generate error in try-block
(https://github.com/openstack/horizon/blob/2014.2.b3/openstack_dashboard/dashboards/admin/info/views.py#L36).
For example, add the line:
raise Exception('some error')
2. Go to Admin System Information page
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1387665/+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 1397310] [NEW] Attribute validation errors are logged twice
Public bug reported: In neutron/api/v2/attributes.py, all validation functions debug-log any errors that occur inside them, and return the error message back to caller. In the end, those messages get into _validate_dict() function that also logs those messages, if any. Meaning, we'll get duplicate validation errors in debug logs for every validation failure. Validation functions should not report those messages themselves, instead relying on caller to handle returned error messages as it sees fit. ** 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/1397310 Title: Attribute validation errors are logged twice Status in OpenStack Neutron (virtual network service): New Bug description: In neutron/api/v2/attributes.py, all validation functions debug-log any errors that occur inside them, and return the error message back to caller. In the end, those messages get into _validate_dict() function that also logs those messages, if any. Meaning, we'll get duplicate validation errors in debug logs for every validation failure. Validation functions should not report those messages themselves, instead relying on caller to handle returned error messages as it sees fit. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1397310/+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 1397318] [NEW] Wront return code for inherited role checking
Public bug reported:
As per https://github.com/openstack/keystone-specs/blob/master/api/v3
/identity-api-v3-os-inherit-ext.rst#check-if-user-has-an-inherited-
project-role-on-domain, HEAD /OS-
INHERIT/domains/{domain_id}/users/{user_id}/roles/{role_id}/inherited_to_projects
returns 204 No Content, but the correct return is 200:
curl --verbose -X HEAD -H X-Auth-Token:$TOKEN
http://localhost:5000/v3/OS-INHERIT/domains/default/users/dd55a1c1c05842c29b50ef8ecce681a7/roles/inherited_to_projects;
* Hostname was NOT found in DNS cache
* Trying 127.0.1.1...
* Connected to localhost (127.0.1.1) port 5000 (#0)
HEAD
/v3/OS-INHERIT/domains/default/users/dd55a1c1c05842c29b50ef8ecce681a7/roles/inherited_to_projects
HTTP/1.1
User-Agent: curl/7.35.0
Host: localhost:5000
Accept: */*
X-Auth-Token:9c87d13fa15d41549f634bd06f4551b4
HTTP/1.1 200 OK
Date: Fri, 28 Nov 2014 12:59:10 GMT
* Server Apache/2.4.7 (Ubuntu) is not blacklisted
Server: Apache/2.4.7 (Ubuntu)
Vary: X-Auth-Token
Content-Length: 334
Content-Type: application/json
** Affects: keystone
Importance: Undecided
Assignee: Rodrigo Duarte (rodrigodsousa)
Status: In Progress
** Tags: documentation low-hanging-fruit
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1397318
Title:
Wront return code for inherited role checking
Status in OpenStack Identity (Keystone):
In Progress
Bug description:
As per https://github.com/openstack/keystone-specs/blob/master/api/v3
/identity-api-v3-os-inherit-ext.rst#check-if-user-has-an-inherited-
project-role-on-domain, HEAD /OS-
INHERIT/domains/{domain_id}/users/{user_id}/roles/{role_id}/inherited_to_projects
returns 204 No Content, but the correct return is 200:
curl --verbose -X HEAD -H X-Auth-Token:$TOKEN
http://localhost:5000/v3/OS-INHERIT/domains/default/users/dd55a1c1c05842c29b50ef8ecce681a7/roles/inherited_to_projects;
* Hostname was NOT found in DNS cache
* Trying 127.0.1.1...
* Connected to localhost (127.0.1.1) port 5000 (#0)
HEAD
/v3/OS-INHERIT/domains/default/users/dd55a1c1c05842c29b50ef8ecce681a7/roles/inherited_to_projects
HTTP/1.1
User-Agent: curl/7.35.0
Host: localhost:5000
Accept: */*
X-Auth-Token:9c87d13fa15d41549f634bd06f4551b4
HTTP/1.1 200 OK
Date: Fri, 28 Nov 2014 12:59:10 GMT
* Server Apache/2.4.7 (Ubuntu) is not blacklisted
Server: Apache/2.4.7 (Ubuntu)
Vary: X-Auth-Token
Content-Length: 334
Content-Type: application/json
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1397318/+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 1389938] Re: kvm instance can't be launched with '-serial pty'
Which version of nova? ** Also affects: nova Importance: Undecided Status: New ** Changed in: nova (Ubuntu) Status: New = Incomplete -- 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/1389938 Title: kvm instance can't be launched with '-serial pty' Status in OpenStack Compute (Nova): New Status in nova package in Ubuntu: Incomplete Bug description: 1, version ubuntu@ms01a:~/ming$ uname -a Linux ms01a 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:10:54 UTC 2014 aarch64 aarch64 aarch64 GNU/Linux 2, kvm instance can't be launched, and see below failure log in /var/log/nova/nova-compute.log: 2014-11-05 21:58:58.480 781 INFO nova.compute.manager [-] [instance: 1e3bc825-b44f-47ee-b438-2fc06b133f5d] During sync_power_state the instance has a pending task. Skip. 2014-11-05 21:58:58.697 781 ERROR oslo.messaging.rpc.dispatcher [-] Exception during message handling: internal error: early end of file from monitor: possible problem: qemu-system-aarch64: -serial pty: Failed to create chardev qemu: could not connect serial device to character backend 'pty' 3, once I have done below change, the problem is fixed: nova/virt/libvirt/driver.py: #consolepty = vconfig.LibvirtConfigGuestSerial() #consolepty.type = pty #guest.add_device(consolepty) To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1389938/+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 1352102] Re: users are unable to create ports on provider networks
** Changed in: nova (Ubuntu) Status: Confirmed = 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/1352102 Title: users are unable to create ports on provider networks Status in OpenStack Compute (Nova): Fix Released Status in nova package in Ubuntu: Fix Released Bug description: after commit da66d50010d5b1ba1d7fc9c3d59d81b6c01bb0b0 my users are unable to boot vm attached to provider networks, this is a serious regression for me as we mostly use provider networks. bug which originated the commit https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1284718 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1352102/+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 1381131] [NEW] Unable to detect locale.
You have been subscribed to a public bug: I seem to have some clickable buttons in french and some in english. http://people.canonical.com/~chucks/tmp/francais.png chuck ** Affects: horizon Importance: Undecided Status: New -- Unable to detect locale. https://bugs.launchpad.net/bugs/1381131 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). -- 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 1316556] Re: vmware: boot from image (create volume) is failing
** Changed in: nova (Ubuntu) Status: In Progress = Won't Fix -- 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/1316556 Title: vmware: boot from image (create volume) is failing Status in OpenStack Compute (Nova): Invalid Status in nova package in Ubuntu: Won't Fix Bug description: Nova fails to boot an instance from the image using create volume. Run time environment details: cinder is configured with VMDK driver nova is configured with Vmware Vc driver While nova is trying to provision a instance by creating the volume from the given VMDK image by creating a volume and booting from it, it failed to create the instance, though volume is created properly after given amount of time. This failure is occurring especially when the volume creation is taking more than 180 seconds. Exception thrown by nova compute is: Volume f36bf0ce-ef0d-4200-b15b- cf2de3689bbb did not finish being created even after we waited 221 seconds or 180 attempts. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1316556/+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 1201873] Re: dnsmasq does not use -h, so /etc/hosts sends folks to loopback when they look up the machine it's running on
** Changed in: nova (Ubuntu) Status: Triaged = 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/1201873 Title: dnsmasq does not use -h, so /etc/hosts sends folks to loopback when they look up the machine it's running on Status in OpenStack Compute (Nova): Fix Released Status in nova package in Ubuntu: Fix Released Bug description: from dnsmasq(8): -h, --no-hosts Don't read the hostnames in /etc/hosts. I reliably get bit by this during certain kinds of deployments, where my nova-network/dns host has an entry in /etc/hosts such as: 127.0.1.1hostname.example.com hostname I keep having to edit /etc/hosts on that machine to use a real IP, because juju gets really confused when it looks up certain openstack hostnames and gets sent to its own instance! To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1201873/+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 1396318] Re: Cannot read text in region selection box
** Also affects: horizon Importance: Undecided Status: New -- 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/1396318 Title: Cannot read text in region selection box Status in OpenStack Dashboard (Horizon): New Status in horizon package in Ubuntu: Confirmed Bug description: When multiple regions are configured within Horizon, the region selection dropdown box in the top right corner of the horizon dashboard is not visible due to white text on white background. Steps to reproduce: 1. Install horizon 2. Configure to use multiple regions within keystone (or multiple keystones, 1 per region) 3. log in 4. Observe the region selection box in the top right is white on white text. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1396318/+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 1381131] Re: Unable to detect locale.
*** This bug is a duplicate of bug 1253982 *** https://bugs.launchpad.net/bugs/1253982 ** Package changed: horizon (Ubuntu) = horizon -- 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/1381131 Title: Unable to detect locale. Status in OpenStack Dashboard (Horizon): New Bug description: I seem to have some clickable buttons in french and some in english. http://people.canonical.com/~chucks/tmp/francais.png chuck To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1381131/+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 1310340] Re: live migration fails when use long hostname of a nova compute target host
** Package changed: horizon (Ubuntu) = nova (Ubuntu) -- 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/1310340 Title: live migration fails when use long hostname of a nova compute target host Status in OpenStack Compute (Nova): Confirmed Status in nova package in Ubuntu: New Bug description: Nova don't do live-migration when used long hostname of target host nova show ubuntu14.04 +--+---+ | Property | Value | +--+---+ .. | OS-EXT-SRV-ATTR:host | compute2 | | OS-EXT-SRV-ATTR:hypervisor_hostname | compute2.site.local | .. nova live-migration ubuntu14.04 compute2.site.local ERROR (BadRequest): Compute service of compute2.site.local is unavailable at this time. (HTTP 400) (Request-ID: req-f344c0bf-aaa3-47e6-a24c-8f37e89858e4) but nova live-migration ubuntu14.04 compute2 runs without error Also if you try to do migration through horizon it always fails because horizon use long hostname fo target host. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1310340/+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 1385213] Re: Swift multi-tenant store: upload broken
Glance_store fixes for this were released in 0.1.10. ** Also affects: glance-store Importance: Undecided Status: New ** Changed in: glance-store Status: New = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1385213 Title: Swift multi-tenant store: upload broken Status in OpenStack Image Registry and Delivery Service (Glance): Fix Committed Status in Glance juno series: In Progress Status in OpenStack Glance backend store-drivers library (glance_store): Fix Released Bug description: glance image-upload xxx returns E500 when using the swift multi-tenant backend To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1385213/+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 1397381] [NEW] numa cell ids need to be normalized before creating xml
Public bug reported: When creating instance with numa topology, if that instance is placed on a host numa node different then 0 , invalid libvirt.xml will be generated. it's because instance cell id's are used to store host id assignment. Instance cell id's should be normalized before generating libvirt.xml 2014-11-28 16:35:55.195 ERROR nova.virt.libvirt.driver [-] Error defining a domain with XML: domain type=kvm uuidb90dbaea-ed6f-49fa-b3bf-75137005c621/uuid nameinstance-0005/name memory2097152/memory numatune memory mode=strict nodeset=1/ memnode cellid=1 mode=strict nodeset=1/ /numatune vcpu4/vcpu metadata nova:instance xmlns:nova=http://openstack.org/xmlns/libvirt/nova/1.0; nova:package version=2015.1.0/ nova:namevm1/nova:name nova:creationTime2014-11-28 16:35:55/nova:creationTime nova:flavor name=nano_mini nova:memory2048/nova:memory nova:disk0/nova:disk nova:swap0/nova:swap nova:ephemeral0/nova:ephemeral nova:vcpus4/nova:vcpus /nova:flavor nova:owner nova:user uuid=04d6fa121cbc4b60b57c96eb32b356b1admin/nova:user nova:project uuid=9193517bf6c64d0296d60095c88b2e5ademo/nova:project /nova:owner nova:root type=image uuid=c0fc1ed6-1ee5-47fa-a2e7-f1aee3c6750b/ /nova:instance /metadata sysinfo type=smbios system entry name=manufacturerOpenStack Foundation/entry entry name=productOpenStack Nova/entry entry name=version2015.1.0/entry entry name=serial10881668-12bf-49c2-9efb-28bb8d278929/entry entry name=uuidb90dbaea-ed6f-49fa-b3bf-75137005c621/entry /system /sysinfo os typehvm/type boot dev=hd/ smbios mode=sysinfo/ /os features acpi/ apic/ /features cputune vcpupin vcpu=0 cpuset=10-19,30-39/ vcpupin vcpu=1 cpuset=10-19,30-39/ vcpupin vcpu=2 cpuset=10-19,30-39/ vcpupin vcpu=3 cpuset=10-19,30-39/ /cputune clock offset=utc timer name=pit tickpolicy=delay/ timer name=rtc tickpolicy=catchup/ timer name=hpet present=no/ /clock cpu match=exact topology sockets=4 cores=1 threads=1/ numa cell id=1 cpus=0-3 memory=2097152/ /numa /cpu devices disk type=file device=disk driver name=qemu type=qcow2 cache=none/ source file=/opt/stack/data/nova/instances/b90dbaea-ed6f-49fa-b3bf-75137005c621/disk/ target bus=virtio dev=vda/ /disk disk type=file device=cdrom driver name=qemu type=raw cache=none/ source file=/opt/stack/data/nova/instances/b90dbaea-ed6f-49fa-b3bf-75137005c621/disk.config/ target bus=ide dev=hdd/ /disk interface type=hostdev managed=yes mac address=fa:16:3e:69:8c:17/ source address type=pci domain=0x bus=0x82 slot=0x10 function=0x2/ /source vlan tag id=1000/ /vlan /interface serial type=file source path=/opt/stack/data/nova/instances/b90dbaea-ed6f-49fa-b3bf-75137005c621/console.log/ /serial serial type=pty/ graphics type=vnc autoport=yes keymap=en-us listen=127.0.0.1/ video model type=cirrus/ /video memballoon model=virtio stats period=10/ /memballoon /devices /domain 2014-11-28 16:35:55.195 ERROR nova.compute.manager [-] [instance: b90dbaea-ed6f-49fa-b3bf-75137005c621] Instance failed to spawn 2014-11-28 16:35:55.195 TRACE nova.compute.manager [instance: b90dbaea-ed6f-49fa-b3bf-75137005c621] Traceback (most recent call last): 2014-11-28 16:35:55.195 TRACE nova.compute.manager [instance: b90dbaea-ed6f-49fa-b3bf-75137005c621] File /shared/stack/nova/nova/compute/manager.py, line 2246, in _build_resources 2014-11-28 16:35:55.195 TRACE nova.compute.manager [instance: b90dbaea-ed6f-49fa-b3bf-75137005c621] yield resources 2014-11-28 16:35:55.195 TRACE nova.compute.manager [instance: b90dbaea-ed6f-49fa-b3bf-75137005c621] File /shared/stack/nova/nova/compute/manager.py, line 2116, in _build_and_run_instance 2014-11-28 16:35:55.195 TRACE nova.compute.manager [instance: b90dbaea-ed6f-49fa-b3bf-75137005c621] instance_type=instance_type) 2014-11-28 16:35:55.195 TRACE nova.compute.manager [instance: b90dbaea-ed6f-49fa-b3bf-75137005c621] File /shared/stack/nova/nova/virt/libvirt/driver.py, line 2641, in spawn 2014-11-28 16:35:55.195 TRACE nova.compute.manager [instance: b90dbaea-ed6f-49fa-b3bf-75137005c621] block_device_info, disk_info=disk_info) 2014-11-28 16:35:55.195 TRACE nova.compute.manager [instance: b90dbaea-ed6f-49fa-b3bf-75137005c621] File /shared/stack/nova/nova/virt/libvirt/driver.py, line 4490, in _create_domain_and_network 2014-11-28 16:35:55.195 TRACE nova.compute.manager [instance: b90dbaea-ed6f-49fa-b3bf-75137005c621] power_on=power_on) 2014-11-28 16:35:55.195 TRACE nova.compute.manager [instance: b90dbaea-ed6f-49fa-b3bf-75137005c621] File /shared/stack/nova/nova/virt/libvirt/driver.py, line 4423, in _create_domain 2014-11-28
[Yahoo-eng-team] [Bug 1386147] Re: live-migration failed because of Filter ComputeFilter returned 0 hosts, the instance's status is still migrating.
** Changed in: nova/icehouse Status: New = Invalid -- 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/1386147 Title: live-migration failed because of Filter ComputeFilter returned 0 hosts, the instance's status is still migrating. Status in OpenStack Compute (Nova): Invalid Status in OpenStack Compute (nova) icehouse series: Invalid Bug description: I have three compute nodes, and one instance on host opencos179-24. A live-migration failed, the content of nova-scheduler.log show that Filter ComputeFilter returned 0 hosts. But the instance's status is still migrating. I hope the instance could rollback. log is as follows: http://paste.openstack.org/show/125266/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1386147/+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 1397489] [NEW] VM boot failure since nova to neutron port notification fails
Public bug reported: When I run the latest devstack and use nova boot to create a VM,but it failed. Nova show the VM,it show:message: Build of instance cb509a04-ca8a- 491f-baf1-be01b15f4946 aborted: Failed to allocate the network(s), not rescheduling., code: 500, details: File \/opt/stack/nova/nova/compute/manager.py\, line 2030, in _do_build_and_run_instance and the following error in the nova-compute.log: Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 1714, in _spawn block_device_info) File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py, line 2266, in spawn block_device_info) File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py, line 3681, in _create_domain_and_network raise exception.VirtualInterfaceCreateException() VirtualInterfaceCreateException: Virtual Interface creation failed Adding vif_plugging_is_fatal = False and vif_plugging_timeout = 5 to the compute nodes stops the missing message from being fatal and guests can then be spawned normally and accessed over the network. In the bug: https://bugs.launchpad.net/nova/+bug/1348103 says it happened in cells environment,but it doesn't happen only in cells environment.This problem should arouse our attention more. ** Affects: nova Importance: Undecided Status: New ** Tags: nova ** Project changed: neutron = nova -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1397489 Title: VM boot failure since nova to neutron port notification fails Status in OpenStack Compute (Nova): New Bug description: When I run the latest devstack and use nova boot to create a VM,but it failed. Nova show the VM,it show:message: Build of instance cb509a04-ca8a- 491f-baf1-be01b15f4946 aborted: Failed to allocate the network(s), not rescheduling., code: 500, details: File \/opt/stack/nova/nova/compute/manager.py\, line 2030, in _do_build_and_run_instance and the following error in the nova-compute.log: Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 1714, in _spawn block_device_info) File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py, line 2266, in spawn block_device_info) File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py, line 3681, in _create_domain_and_network raise exception.VirtualInterfaceCreateException() VirtualInterfaceCreateException: Virtual Interface creation failed Adding vif_plugging_is_fatal = False and vif_plugging_timeout = 5 to the compute nodes stops the missing message from being fatal and guests can then be spawned normally and accessed over the network. In the bug: https://bugs.launchpad.net/nova/+bug/1348103 says it happened in cells environment,but it doesn't happen only in cells environment.This problem should arouse our attention more. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1397489/+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
