[Yahoo-eng-team] [Bug 1335744] [NEW] VMware: port group and vm are created in different exsi when using vlanDHCPmanage
Public bug reported: When using vlanDHCPmanage it is supposed to create a portgroup if the portgroups doesn't exist in the vCenter. I found that it is possible that the created portgroup and deployed vm are located in different exsis if there are more than 1 exsi under cluster. The deployment is shown as successful. Of course the IPs are not correct. ** Affects: nova Importance: Undecided Status: New ** Tags: vmware -- 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/1335744 Title: VMware: port group and vm are created in different exsi when using vlanDHCPmanage Status in OpenStack Compute (Nova): New Bug description: When using vlanDHCPmanage it is supposed to create a portgroup if the portgroups doesn't exist in the vCenter. I found that it is possible that the created portgroup and deployed vm are located in different exsis if there are more than 1 exsi under cluster. The deployment is shown as successful. Of course the IPs are not correct. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1335744/+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 1335733] [NEW] Failed to boot instance with admin role
Public bug reported: Sometimes we need to create instances with admin role for some other tenants. But if we're booting the instance with a security group which name is duplicated in Neutron. Then user will run into an error and from the GUI, user don't know what happened. The root cause of this issue is Neutron client doesn't honoured the tenant id, but get all the security group ids with the given name. So we need to fix this from both Nova and Neutron client side. ** Affects: nova Importance: Undecided Assignee: Fei Long Wang (flwang) Status: New ** Affects: python-neutronclient Importance: Undecided Assignee: Fei Long Wang (flwang) Status: New ** Changed in: nova Assignee: (unassigned) => Fei Long Wang (flwang) ** Also affects: python-neutronclient Importance: Undecided Status: New ** Changed in: python-neutronclient Assignee: (unassigned) => Fei Long Wang (flwang) ** Description changed: Sometimes we need to create instances with admin role for some other tenants. But if we're booting the instance with a security group which - is duplicated in Neutron. Then user will run into an error and from the - GUI, user don't know what happened. + name is duplicated in Neutron. Then user will run into an error and from + the GUI, user don't know what happened. The root cause of this issue is Neutron client doesn't honoured the tenant id, but get all the security group ids with the given name. So we need to fix this from both Nova and Neutron client side. -- 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/1335733 Title: Failed to boot instance with admin role Status in OpenStack Compute (Nova): New Status in Python client library for Neutron: New Bug description: Sometimes we need to create instances with admin role for some other tenants. But if we're booting the instance with a security group which name is duplicated in Neutron. Then user will run into an error and from the GUI, user don't know what happened. The root cause of this issue is Neutron client doesn't honoured the tenant id, but get all the security group ids with the given name. So we need to fix this from both Nova and Neutron client side. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1335733/+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 1322681] Re: live-migration --block-migrate fails: XML error: CPU feature `pdpe1gb' specified more than once
** Also affects: nova (Fedora)
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/1322681
Title:
live-migration --block-migrate fails: XML error: CPU feature
`pdpe1gb' specified more than once
Status in OpenStack Compute (Nova):
New
Status in “nova” package in Ubuntu:
Confirmed
Status in “nova” package in Fedora:
New
Bug description:
2014-05-23 15:32:58.767 57916 INFO nova.compute.resource_tracker [-]
Compute_service record updated for chakora:chakora.1ss.qa.lexington
2014-05-23 15:33:42.551 57916 INFO nova.virt.libvirt.driver
[req-9d8c6bac-74ea-4876-9fb2-729f2f525fb2 ff364dfc08b84aab871a802888cfbd76
ce780a90138b466f8a0343d487e3198c] Instance launched has CPU info:
{"vendor": "Intel", "model": "SandyBridge", "arch": "x86_64", "features":
["pdpe1gb", "osxsave", "dca", "pcid", "pdcm", "xtpr", "tm2", "est", "smx",
"vmx", "ds_cpl", "monitor", "dtes64", "pbe", "tm", "ht", "ss", "acpi", "ds",
"vme", "pdpe1gb", "osxsave", "dca", "pcid", "pdcm", "xtpr", "tm2", "est",
"smx", "vmx", "ds_cpl", "monitor", "dtes64", "pbe", "tm", "ht", "ss", "acpi",
"ds", "vme", "lahf_lm", "lm", "rdtscp", "nx", "syscall", "avx", "xsave", "aes",
"tsc-deadline", "popcnt", "x2apic", "sse4.2", "sse4.1", "cx16", "ssse3",
"pclmuldq", "pni", "sse2", "sse", "fxsr", "mmx", "clflush", "pse36", "pat",
"cmov", "mca", "pge", "mtrr", "sep", "apic", "cx8", "mce", "pae", "msr", "tsc",
"pse", "de", "fpu"], "topology": {"cores": 8, "threads": 2, "sockets": 1}}
2014-05-23 15:33:42.556 57916 ERROR nova.virt.libvirt.driver
[req-9d8c6bac-74ea-4876-9fb2-729f2f525fb2 ff364dfc08b84aab871a802888cfbd76
ce780a90138b466f8a0343d487e3198c] CPU doesn't have compatibility.
XML error: CPU feature `pdpe1gb' specified more than once
Refer to http://libvirt.org/html/libvirt-libvirt.html#virCPUCompareResult
2014-05-23 15:33:42.568 57916 ERROR oslo.messaging.rpc.dispatcher [-]
Exception during message handling: XML error: CPU feature `pdpe1gb' specified
more than once
2014-05-23 15:33:42.568 57916 TRACE oslo.messaging.rpc.dispatcher Traceback
(most recent call last):
2014-05-23 15:33:42.568 57916 TRACE oslo.messaging.rpc.dispatcher File
"/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 133,
in _dispatch_and_reply
2014-05-23 15:33:42.568 57916 TRACE oslo.messaging.rpc.dispatcher
incoming.message))
2014-05-23 15:33:42.568 57916 TRACE oslo.messaging.rpc.dispatcher File
"/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 176,
in _dispatch
2014-05-23 15:33:42.568 57916 TRACE oslo.messaging.rpc.dispatcher return
self._do_dispatch(endpoint, method, ctxt, args)
2014-05-23 15:33:42.568 57916 TRACE oslo.messaging.rpc.dispatcher File
"/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 122,
in _do_dispatch
2014-05-23 15:33:42.568 57916 TRACE oslo.messaging.rpc.dispatcher result
= getattr(endpoint, method)(ctxt, **new_args)
2014-05-23 15:33:42.568 57916 TRACE oslo.messaging.rpc.dispatcher File
"/usr/lib/python2.7/dist-packages/nova/exception.py", line 88, in wrapped
2014-05-23 15:33:42.568 57916 TRACE oslo.messaging.rpc.dispatcher payload)
2014-05-23 15:33:42.568 57916 TRACE oslo.messaging.rpc.dispatcher File
"/usr/lib/python2.7/dist-packages/nova/openstack/common/excutils.py", line 68,
in __exit__
2014-05-23 15:33:42.568 57916 TRACE oslo.messaging.rpc.dispatcher
six.reraise(self.type_, self.value, self.tb)
2014-05-23 15:33:42.568 57916 TRACE oslo.messaging.rpc.dispatcher File
"/usr/lib/python2.7/dist-packages/nova/exception.py", line 71, in wrapped
2014-05-23 15:33:42.568 57916 TRACE oslo.messaging.rpc.dispatcher return
f(self, context, *args, **kw)
2014-05-23 15:33:42.568 57916 TRACE oslo.messaging.rpc.dispatcher File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 309, in
decorated_function
2014-05-23 15:33:42.568 57916 TRACE oslo.messaging.rpc.dispatcher e,
sys.exc_info())
2014-05-23 15:33:42.568 57916 TRACE oslo.messaging.rpc.dispatcher File
"/usr/lib/python2.7/dist-packages/nova/openstack/common/excutils.py", line 68,
in __exit__
2014-05-23 15:33:42.568 57916 TRACE oslo.messaging.rpc.dispatcher
six.reraise(self.type_, self.value, self.tb)
2014-05-23 15:33:42.568 57916 TRACE oslo.messaging.rpc.dispatcher File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 296, in
decorated_function
2014-05-23 15:33:42.568 57916 TRACE oslo.messaging.rpc.dispatcher return
function(self, context, *args, **kwargs)
2014-05-23 15:33:42.568 57916 TRACE oslo.messaging.rpc.dispatcher File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 4418, in
check_can_live_migrate_destination
2014-05-23 15:33:42.568 57916 TRACE oslo.messaging.rpc.dispatcher
block_migr
[Yahoo-eng-team] [Bug 1335688] [NEW] Inconsistent capitalization on Networks tab under Launch Instance
Public bug reported: Under Launch Instance -> Networks, the two options are "Selected Networks" and "Available networks". Capitalization of "networks" should probably be consistent. Obviously minor and doesn't affect usability. ** Affects: horizon Importance: Undecided Status: New ** Attachment added: "capitalizationBug.png" https://bugs.launchpad.net/bugs/1335688/+attachment/4142307/+files/capitalizationBug.png -- 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/1335688 Title: Inconsistent capitalization on Networks tab under Launch Instance Status in OpenStack Dashboard (Horizon): New Bug description: Under Launch Instance -> Networks, the two options are "Selected Networks" and "Available networks". Capitalization of "networks" should probably be consistent. Obviously minor and doesn't affect usability. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1335688/+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 1335640] [NEW] Neutron doesn't support OSprofiler
Public bug reported: To be able to improve OpenStack, and as Neutron we should have cross service/project profiler that will build one trace that goes through all services/projects and measures most important parts. So I build special for OpenStack library that allows us to do this. More about it: https://github.com/stackforge/osprofiler ** Affects: neutron Importance: Undecided Assignee: Boris Pavlovic (boris-42) Status: New ** Changed in: neutron Assignee: (unassigned) => Boris Pavlovic (boris-42) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1335640 Title: Neutron doesn't support OSprofiler Status in OpenStack Neutron (virtual network service): New Bug description: To be able to improve OpenStack, and as Neutron we should have cross service/project profiler that will build one trace that goes through all services/projects and measures most important parts. So I build special for OpenStack library that allows us to do this. More about it: https://github.com/stackforge/osprofiler To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1335640/+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 1335618] [NEW] Horizon: Disable buttons when user doesn't fill mandatory fields
Public bug reported: Description of problem: === Many dialogs have mandatory fields. Buttons in these dialogs should be disabled until user fill the mandatory fields. Version-Release number of selected component (if applicable): python-django-horizon-2014.1-7.el7ost.noarch openstack-dashboard-2014.1-7.el7ost.noarch How reproducible: = 100% Steps to Reproduce: === 1. Login to Horizon 2. Click 'Project' --> 'Compute' --> 'Images' 3. Click 'Create Image' Actual results: === Mandatory fields are empty but 'Create Image' button in enabled Expected results: = The button should be disabled until user fill the mandatory fields. Additional info: Two screenshots are enclosed ** Affects: horizon Importance: Undecided Status: New ** Attachment added: "Create Image dialog" https://bugs.launchpad.net/bugs/1335618/+attachment/4141966/+files/Screenshot-Create_Image.png -- 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/1335618 Title: Horizon: Disable buttons when user doesn't fill mandatory fields Status in OpenStack Dashboard (Horizon): New Bug description: Description of problem: === Many dialogs have mandatory fields. Buttons in these dialogs should be disabled until user fill the mandatory fields. Version-Release number of selected component (if applicable): python-django-horizon-2014.1-7.el7ost.noarch openstack-dashboard-2014.1-7.el7ost.noarch How reproducible: = 100% Steps to Reproduce: === 1. Login to Horizon 2. Click 'Project' --> 'Compute' --> 'Images' 3. Click 'Create Image' Actual results: === Mandatory fields are empty but 'Create Image' button in enabled Expected results: = The button should be disabled until user fill the mandatory fields. Additional info: Two screenshots are enclosed To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1335618/+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 1335392] Re: Configure controller node in OpenStack Installation Guide for Ubuntu 12.04/14.04 (LTS) - icehouse
AFAIK all these sections are case insensitive, so either should work. If it does not - as you indicate - , let's file it as bug against Neutron and see what guidance we get from there. ** Also affects: neutron Importance: Undecided Status: New ** Summary changed: - Configure controller node in OpenStack Installation Guide for Ubuntu 12.04/14.04 (LTS) - icehouse + [securitygroup] not recocgnized in ml2_conf.ini ** Summary changed: - [securitygroup] not recocgnized in ml2_conf.ini + [securitygroup] not recognized in ml2_conf.ini -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1335392 Title: [securitygroup] not recognized in ml2_conf.ini Status in OpenStack Neutron (virtual network service): New Status in OpenStack Manuals: New Bug description: The [securitygruop] section of configuration file /etc/neutron/plugins/ml2/ml2_conf.ini should be actually named [SECURITYGROUP] (in capital letters). If you configure the file as indicated (i.e. with the section name in small letters), the plug in does not work properly and the result is that the instances cannot reach the metadata server. I discovered this subtle bug by reverse engineering the file produced by devstack. --- Built: 2014-06-20T10:03:51 00:00 git SHA: cf40d505946951121468a170753d83905d8bdb55 URL: http://docs.openstack.org/icehouse/install-guide/install/apt/content/neutron-ml2-controller-node.html source File: file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishdocs/doc/install-guide/section_neutron-ml2-controller-node.xml xml:id: neutron-ml2-controller-node To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1335392/+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 1335559] [NEW] HyperV driver does not implement hypervisor-uptime feature
Public bug reported: The HyperV driver does not implement hypervisor-uptime feature. Currently NotImplementError is raised. The class Win32_PerfFormattedData_PerfOS_System provides SystemUpTime. This can be used to return the uptime of the HyperV host ** Affects: nova Importance: Undecided Assignee: Sagar Ratnakara Nikam (sagar-r-nikam) Status: New ** Tags: hyper-v ** Changed in: nova Assignee: (unassigned) => Sagar Ratnakara Nikam (sagar-r-nikam) -- 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/1335559 Title: HyperV driver does not implement hypervisor-uptime feature Status in OpenStack Compute (Nova): New Bug description: The HyperV driver does not implement hypervisor-uptime feature. Currently NotImplementError is raised. The class Win32_PerfFormattedData_PerfOS_System provides SystemUpTime. This can be used to return the uptime of the HyperV host To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1335559/+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
