[Yahoo-eng-team] [Bug 1590426] [NEW] Keystone Federated Identity assertion name not included in token
Public bug reported:
When using keystone Federated Identitity, the user name, based on the
assertion mapping, is replaced in Keystone tokens by the autogenerated
ID, resulting in e.g. Horizon showing the user's ID instead of the name
(see attachment).
Running "openstack user list" shows the correct data:
+--+--+
| ID | Name |
+--+--+
| 1835f12340674587b8e9b55ac1b43a3c | te...@acme.com |
+--+--+
The issue is clearly visible in the logs:
016-05-26 10:08:02.809220 DEBUG:keystoneauth.identity.v3.base:{"token":
{"issued_at": "2016-05-26T10:08:02.804697Z", "user": {"OS-FEDERATION":
{"identity_provider": {"id": "idp_1"}, "protocol": {"id": "saml2"},
"groups": [{"id": "b07974d2891f4d939b91a288ea933b1e"}]}, "domain":
{"id": "Federated", "name": "Federated"}, "id":
"1835f12340674587b8e9b55ac1b43a3c", "name":
"1835f12340674587b8e9b55ac1b43a3c"}, "methods": ["token"], "expires_at":
"2016-05-26T11:08:02.804676Z", "audit_ids": ["4O86fwqsSd6LSge4123sdx"]}}
** Affects: keystone
Importance: Undecided
Status: New
** Attachment added: "Horizon showing the data coming"
https://bugs.launchpad.net/bugs/1590426/+attachment/4679819/+files/keystone_federated_horizon_issue.png
--
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/1590426
Title:
Keystone Federated Identity assertion name not included in token
Status in OpenStack Identity (keystone):
New
Bug description:
When using keystone Federated Identitity, the user name, based on the
assertion mapping, is replaced in Keystone tokens by the autogenerated
ID, resulting in e.g. Horizon showing the user's ID instead of the
name (see attachment).
Running "openstack user list" shows the correct data:
+--+--+
| ID | Name |
+--+--+
| 1835f12340674587b8e9b55ac1b43a3c | te...@acme.com |
+--+--+
The issue is clearly visible in the logs:
016-05-26 10:08:02.809220
DEBUG:keystoneauth.identity.v3.base:{"token": {"issued_at":
"2016-05-26T10:08:02.804697Z", "user": {"OS-FEDERATION":
{"identity_provider": {"id": "idp_1"}, "protocol": {"id": "saml2"},
"groups": [{"id": "b07974d2891f4d939b91a288ea933b1e"}]}, "domain":
{"id": "Federated", "name": "Federated"}, "id":
"1835f12340674587b8e9b55ac1b43a3c", "name":
"1835f12340674587b8e9b55ac1b43a3c"}, "methods": ["token"],
"expires_at": "2016-05-26T11:08:02.804676Z", "audit_ids":
["4O86fwqsSd6LSge4123sdx"]}}
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1590426/+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 1370292] Re: Possible SQL Injection vulnerability in hyperv plugin
Not a bug as by discussion above, thanks ** Changed in: neutron Status: Incomplete => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1370292 Title: Possible SQL Injection vulnerability in hyperv plugin Status in neutron: Invalid Status in OpenStack Security Advisory: Won't Fix Bug description: On this line: https://github.com/openstack/neutron/blob/master/neutron/plugins/hyperv/agent/utilsv2.py#L190 a raw SQL query is being made with the parameters 'class_name' and 'element_name'. Class name appears to be a hardcoded value in the usage that I saw, but element_name looks like it is set from "switch_port_name". If a malicious user is able to tamper with the switch port name, a SQL injection vulnerability exists. At least this is an unsafe programming practice. A library such as sqlalchemy should be used, or at least prepared statements. If there is no way for a user to tamper with these parameters, this can be fixed in public and treated as security hardening rather than a vulnerability. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1370292/+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 1511607] Re: Hyper-V nova driver does not handle block_device_mapping_v2
There's a blueprint for this: https://blueprints.launchpad.net/nova/+spec/hyper-v-block-device-mapping-support Please note that this BP is already merged in: https://github.com/openstack/compute-hyperv ** Changed in: nova 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/1511607 Title: Hyper-V nova driver does not handle block_device_mapping_v2 Status in OpenStack Compute (nova): Invalid Bug description: Hyper-V nova driver does not handle block_device_mapping_v2 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1511607/+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 1510925] Re: Hyper-V does not support fibre channel
There's an approved blueprint for fibre channel support on Hyper-V: https://blueprints.launchpad.net/nova/+spec/hyperv-fibre-channel ** Changed in: nova 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/1510925 Title: Hyper-V does not support fibre channel Status in Cinder: Invalid Status in OpenStack Compute (nova): Invalid Bug description: hyper-v has no support of cinder fibre-channel attachment. The doc below has not been updated since grizzly. http://docs.openstack.org/liberty/config- reference/content/fibrechannel.html To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1510925/+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 1502583] [NEW] ConfigDrive creation fails on Python 3
Public bug reported: On Python 3, attempting to create a ConfigDrive fails when writing files due to str / bytes differences compared to Python 2. ** Affects: nova Importance: Undecided Assignee: Alessandro Pilotti (alexpilotti) Status: Triaged ** Tags: python3 ** Changed in: nova Status: New => Triaged ** Changed in: nova Assignee: (unassigned) => Alessandro Pilotti (alexpilotti) -- 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/1502583 Title: ConfigDrive creation fails on Python 3 Status in OpenStack Compute (nova): Triaged Bug description: On Python 3, attempting to create a ConfigDrive fails when writing files due to str / bytes differences compared to Python 2. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1502583/+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 1286528] Re: guru-meditation fails on Windows due to non portable signal handling
** Also affects: cinder
Importance: Undecided
Status: New
** Changed in: cinder
Status: New = Confirmed
--
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/1286528
Title:
guru-meditation fails on Windows due to non portable signal handling
Status in Cinder:
Confirmed
Status in OpenStack Compute (Nova):
Fix Released
Status in The Oslo library incubator:
Fix Released
Bug description:
The guru-meditation report fails on Hyper-V due to missing signal
handling.
This is a blocking issue on Windows.
http://64.119.130.115/74060/3/Hyper-V_logs/hv-compute1/nova-
console.log.gz
Traceback (most recent call last):
File c:\OpenStack\virtualenv\Scripts\nova-compute-script.py, line 9, in
module
load_entry_point('nova==2014.1.dev954.g3a611cc', 'console_scripts',
'nova-compute')()
File c:\OpenStack\virtualenv\lib\site-packages\pkg_resources.py, line
353, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File c:\OpenStack\virtualenv\lib\site-packages\pkg_resources.py, line
2321, in load_entry_point
return ep.load()
File c:\OpenStack\virtualenv\lib\site-packages\pkg_resources.py, line
2048, in load
entry = __import__(self.module_name, globals(),globals(), ['__name__'])
File c:\OpenStack\virtualenv\lib\site-packages\nova\cmd\compute.py, line
32, in module
from nova.openstack.common.report import guru_meditation_report as gmr
File
c:\OpenStack\virtualenv\lib\site-packages\nova\openstack\common\report\guru_meditation_report.py,
line 63, in module
class GuruMeditation(object):
File
c:\OpenStack\virtualenv\lib\site-packages\nova\openstack\common\report\guru_meditation_report.py,
line 100, in GuruMeditation
def setup_autorun(cls, version, signum=signal.SIGUSR1):
AttributeError: 'module' object has no attribute 'SIGUSR1'
Nova patch that introduced the issue:
https://github.com/openstack/nova/commit/cec532848f569afb4832029bce4969578472a57a
Review link:
https://review.openstack.org/#/c/69058/
To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1286528/+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 1466049] [NEW] guru meditation report does not work on Windows sue to signal.SIGUSR1
*** This bug is a duplicate of bug 1286528 *** https://bugs.launchpad.net/bugs/1286528 Public bug reported: Trying to load a project that uses guru meditation reports fails on Windows with the following trace (in this case on Cinder): http://paste.openstack.org/show/297998/ The issue is that the attribute signal.SIGUSR1 is not present on Windows: https://github.com/openstack/cinder/blob/f2dc050e4df6ec52a2dad258bb4172ebad47422c/cinder/openstack/common/report/guru_meditation_report.py#L99 ** Affects: cinder Importance: Undecided Status: Confirmed ** Tags: hyper-v windows ** Project changed: pbr = oslo-incubator ** Also affects: cinder Importance: Undecided Status: New ** Also affects: nova Importance: Undecided Status: New ** Changed in: oslo-incubator Status: New = Confirmed ** Changed in: cinder Status: New = Confirmed ** No longer affects: oslo-incubator ** No longer affects: nova ** This bug has been marked a duplicate of bug 1286528 guru-meditation fails on Windows due to non portable signal handling -- 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/1466049 Title: guru meditation report does not work on Windows sue to signal.SIGUSR1 Status in Cinder: Confirmed Bug description: Trying to load a project that uses guru meditation reports fails on Windows with the following trace (in this case on Cinder): http://paste.openstack.org/show/297998/ The issue is that the attribute signal.SIGUSR1 is not present on Windows: https://github.com/openstack/cinder/blob/f2dc050e4df6ec52a2dad258bb4172ebad47422c/cinder/openstack/common/report/guru_meditation_report.py#L99 To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1466049/+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 1400069] [NEW] Hyper-V configdrive is missing the static ip configuration
Public bug reported: The Hyper-V driver is not properly handling static IP configuration injection when flat_injected is true and networks don't have DHCP enabled. ** Affects: nova Importance: Low Assignee: Alessandro Pilotti (alexpilotti) Status: Triaged ** Tags: hyper-v ** Changed in: nova Assignee: (unassigned) = Alessandro Pilotti (alexpilotti) ** Changed in: nova Importance: Undecided = Low -- 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/1400069 Title: Hyper-V configdrive is missing the static ip configuration Status in OpenStack Compute (Nova): Triaged Bug description: The Hyper-V driver is not properly handling static IP configuration injection when flat_injected is true and networks don't have DHCP enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1400069/+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 1400080] [NEW] interfaces.template generation needs to include the hw address for usage on multi-nic Windows machines
Public bug reported: When using networks without DHCP enabled and flat_injected set to True, the interfaces template is injected in the associated instances or included in the config drive metadata. The template includes the interface name, based on a progressive numbering (eth0, eth1, etc). In case of multiple nics, there's no clear way to identify the interfaces in the guest OS if the actual interface naming differs, this is especially valid for Windows instances. Since the MAC address (hardware address) assigned to each vNIC identifies uniquely the interface, providing the mac address during the template generation solves the issue. ** Affects: nova Importance: Low Status: New ** Tags: hyper-v juno-backport-potential windows ** Description changed: When using networks without DHCP enabled and flat_injected set to - True, a the interfaces template is injected in the instance or included - in the config drive metadata. + True, the interfaces template is injected in the associated instances or + included in the config drive metadata. The template includes the interface name, based on a progressive numbering (eth0, eth1, etc). In case of multiple nics, there's no clear - way to identify the interfaces if the interface naming differs, this is - especially valid for Windows instances. + way to identify the interfaces in the guest OS if the actual interface + naming differs, this is especially valid for Windows instances. Since the MAC address (hardware address) assigned to each vNIC identifies uniquely the interface, providing the mac address during the template generation solves the issue. -- 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/1400080 Title: interfaces.template generation needs to include the hw address for usage on multi-nic Windows machines Status in OpenStack Compute (Nova): New Bug description: When using networks without DHCP enabled and flat_injected set to True, the interfaces template is injected in the associated instances or included in the config drive metadata. The template includes the interface name, based on a progressive numbering (eth0, eth1, etc). In case of multiple nics, there's no clear way to identify the interfaces in the guest OS if the actual interface naming differs, this is especially valid for Windows instances. Since the MAC address (hardware address) assigned to each vNIC identifies uniquely the interface, providing the mac address during the template generation solves the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1400080/+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 1298034] Re: Nova Hyper-V driver fails occasionally with a x_wmi_uninitialised_thread exception
** Also affects: neutron Importance: Undecided Status: New ** Changed in: neutron Status: New = Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1298034 Title: Nova Hyper-V driver fails occasionally with a x_wmi_uninitialised_thread exception Status in OpenStack Neutron (virtual network service): Confirmed Status in OpenStack Compute (Nova): In Progress Bug description: The Nova Hyper-V driver can fail occasionally with: x_wmi_uninitialised_thread (WMI returned a syntax error: you're probably running inside a thread without first calling pythoncom.CoInitialize[Ex] http://64.119.130.115/82904/14/Hyper-V_logs/hv-compute1/neutron- hyperv-agent.log.gz Each thread that uses COM needs to initialize COM by calling pythoncom.CoInitialize or pythoncom.CoInitializeEx. Error stack trace: http://64.119.130.115/82904/14/Hyper-V_logs/hv-compute1/neutron- hyperv-agent.log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1298034/+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 1376883] [NEW] Spawning images fails on Hyper-V Technical Preview
Public bug reported: Spawning images fails on the current Hyper-V Technical Preview, due to slight changes in Msvm_ImageManagementService.GetVirtualHardDiskSettingData's return value. 2014-10-02 11:52:40.065 924 TRACE nova.compute.manager [instance: 1864933e-c50d-4f86-8b51-cac6c51bcf4e] Traceback (most recent call last): 2014-10-02 11:52:40.065 924 TRACE nova.compute.manager [instance: 1864933e-c50d-4f86-8b51-cac6c51bcf4e] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\compute\manager.py, line 1738, in _spawn 2014-10-02 11:52:40.065 924 TRACE nova.compute.manager [instance: 1864933e-c50d-4f86-8b51-cac6c51bcf4e] block_device_info) 2014-10-02 11:52:40.065 924 TRACE nova.compute.manager [instance: 1864933e-c50d-4f86-8b51-cac6c51bcf4e] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\virt\hyperv\driver.py, line 58, in spawn 2014-10-02 11:52:40.065 924 TRACE nova.compute.manager [instance: 1864933e-c50d-4f86-8b51-cac6c51bcf4e] admin_password, network_info, block_device_info) 2014-10-02 11:52:40.065 924 TRACE nova.compute.manager [instance: 1864933e-c50d-4f86-8b51-cac6c51bcf4e] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\virt\hyperv\vmops.py, line 101, in wrapper 2014-10-02 11:52:40.065 924 TRACE nova.compute.manager [instance: 1864933e-c50d-4f86-8b51-cac6c51bcf4e] return function(self, *args, **kwds) 2014-10-02 11:52:40.065 924 TRACE nova.compute.manager [instance: 1864933e-c50d-4f86-8b51-cac6c51bcf4e] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\virt\hyperv\vmops.py, line 259, in spawn 2014-10-02 11:52:40.065 924 TRACE nova.compute.manager [instance: 1864933e-c50d-4f86-8b51-cac6c51bcf4e] root_vhd_path = self._create_root_vhd(context, instance) 2014-10-02 11:52:40.065 924 TRACE nova.compute.manager [instance: 1864933e-c50d-4f86-8b51-cac6c51bcf4e] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\virt\hyperv\vmops.py, line 168, in _create_root_vhd 2014-10-02 11:52:40.065 924 TRACE nova.compute.manager [instance: 1864933e-c50d-4f86-8b51-cac6c51bcf4e] base_vhd_info = self._vhdutils.get_vhd_info(base_vhd_path) 2014-10-02 11:52:40.065 924 TRACE nova.compute.manager [instance: 1864933e-c50d-4f86-8b51-cac6c51bcf4e] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\virt\hyperv\vhdutilsv2.py, line 219, in get_vhd_info 2014-10-02 11:52:40.065 924 TRACE nova.compute.manager [instance: 1864933e-c50d-4f86-8b51-cac6c51bcf4e] et = ElementTree.fromstring(vhd_info_xml) 2014-10-02 11:52:40.065 924 TRACE nova.compute.manager [instance: 1864933e-c50d-4f86-8b51-cac6c51bcf4e] AttributeError: 'NoneType' object has no attribute 'text' 2014-10-02 11:52:40.065 924 TRACE nova.compute.manager [instance: 1864933e-c50d-4f86-8b51-cac6c51bcf4e] ** Affects: nova Importance: High Assignee: Alessandro Pilotti (alexpilotti) Status: In Progress ** Tags: hyper-v ** Changed in: nova Importance: Undecided = High ** Changed in: nova Status: New = Triaged -- 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/1376883 Title: Spawning images fails on Hyper-V Technical Preview Status in OpenStack Compute (Nova): In Progress Bug description: Spawning images fails on the current Hyper-V Technical Preview, due to slight changes in Msvm_ImageManagementService.GetVirtualHardDiskSettingData's return value. 2014-10-02 11:52:40.065 924 TRACE nova.compute.manager [instance: 1864933e-c50d-4f86-8b51-cac6c51bcf4e] Traceback (most recent call last): 2014-10-02 11:52:40.065 924 TRACE nova.compute.manager [instance: 1864933e-c50d-4f86-8b51-cac6c51bcf4e] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\compute\manager.py, line 1738, in _spawn 2014-10-02 11:52:40.065 924 TRACE nova.compute.manager [instance: 1864933e-c50d-4f86-8b51-cac6c51bcf4e] block_device_info) 2014-10-02 11:52:40.065 924 TRACE nova.compute.manager [instance: 1864933e-c50d-4f86-8b51-cac6c51bcf4e] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\virt\hyperv\driver.py, line 58, in spawn 2014-10-02 11:52:40.065 924 TRACE nova.compute.manager [instance: 1864933e-c50d-4f86-8b51-cac6c51bcf4e] admin_password, network_info, block_device_info) 2014-10-02 11:52:40.065 924 TRACE nova.compute.manager [instance: 1864933e-c50d-4f86-8b51-cac6c51bcf4e] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\virt\hyperv\vmops.py, line 101, in wrapper 2014-10-02 11:52:40.065 924 TRACE nova.compute.manager [instance: 1864933e-c50d
[Yahoo-eng-team] [Bug 1370531] [NEW] Linux guest images on Hyper-V fail to access local storage when using resized differencing VHDX disks
Public bug reported: Description of the issue Create a differencing disk of a Linux image VHDX (any Linux distro with LIS), resizing it in the process (without resizing the base disk) Create and boot a VM with the disk attached on the IDE controller During boot the hv_storvsc module will start logging repeatedly the following message: hv_storvsc vmbus_0_1: cmd 0x28 scsi status 0x2 srb status 0x4 (along with various I/O errors on sda1). The machine manages to boot eventually after a long delay. The following PowerShell script can be used to reproduce the issue: http://paste.openstack.org/raw/110766/ Tested on: Hyper-V 2012 R2 and with various Linux guests. Workaround: Apply the same technique used for VHD disks, where a copy of the base image is resized before the differencing one is created. ** Affects: nova Importance: High Status: Triaged ** Tags: hyper-v -- 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/1370531 Title: Linux guest images on Hyper-V fail to access local storage when using resized differencing VHDX disks Status in OpenStack Compute (Nova): Triaged Bug description: Description of the issue Create a differencing disk of a Linux image VHDX (any Linux distro with LIS), resizing it in the process (without resizing the base disk) Create and boot a VM with the disk attached on the IDE controller During boot the hv_storvsc module will start logging repeatedly the following message: hv_storvsc vmbus_0_1: cmd 0x28 scsi status 0x2 srb status 0x4 (along with various I/O errors on sda1). The machine manages to boot eventually after a long delay. The following PowerShell script can be used to reproduce the issue: http://paste.openstack.org/raw/110766/ Tested on: Hyper-V 2012 R2 and with various Linux guests. Workaround: Apply the same technique used for VHD disks, where a copy of the base image is resized before the differencing one is created. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1370531/+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 1355857] Re: HyperV: resize of instance fails when trying migration across host
Python raises a very misleading error when failing to access a network share for security issues. Make sure you run the Nova compute service with a user which has SMB access to the target node (e.g Administrator). In particular the service user must not be LOCALSYTEM. ** Changed in: nova Status: Confirmed = 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/1355857 Title: HyperV: resize of instance fails when trying migration across host Status in OpenStack Compute (Nova): Invalid Bug description: I have a devstack setup and 2 hyperv hosts. Both the hosts are in same domain. Compute service and Live Migration is enabled in both the hosts. When I am trying to resize a provisioned instance it succeeds if it is resized in the same host. However, when it is trying to resize and migrate across hosts it fails with following error: Compute.log 2014-08-12 14:03:57.533 2992 DEBUG nova.virt.hyperv.migrationops [req-98eaeb46-1272-40af-9205-09fff169f450 None] [instance: 904fa8eb-7377-4c42-9268-eae266b52648] migrate_disk_and_power_off called migrate_disk_and_power_off C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\virt\hyperv\migrationops.py:114 2014-08-12 14:03:57.533 2992 DEBUG nova.virt.hyperv.vmops [req-98eaeb46-1272-40af-9205-09fff169f450 None] [instance: 904fa8eb-7377-4c42-9268-eae266b52648] Power off instance power_off C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\virt\hyperv\vmops.py:425 2014-08-12 14:03:57.908 2992 DEBUG nova.virt.hyperv.vmutils [req-98eaeb46-1272-40af-9205-09fff169f450 None] WMI job succeeded: Turning Off Virtual Machine, Elapsed=00.217830:000 _wait_for_job C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\virt\hyperv\vmutils.py:481 2014-08-12 14:03:57.908 2992 DEBUG nova.virt.hyperv.vmutils [req-98eaeb46-1272-40af-9205-09fff169f450 None] Successfully changed vm state of instance-05d6 to 3 set_vm_state C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\virt\hyperv\vmutils.py:394 2014-08-12 14:03:57.908 2992 DEBUG nova.virt.hyperv.vmops [req-98eaeb46-1272-40af-9205-09fff169f450 None] Successfully changed state of VM instance-05d6 to: 3 _set_vm_state C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\virt\hyperv\vmops.py:440 2014-08-12 14:03:59.096 2992 DEBUG nova.virt.hyperv.migrationops [req-98eaeb46-1272-40af-9205-09fff169f450 None] Migration target host: 10.1.4.214 _migrate_disk_files C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\virt\hyperv\migrationops.py:53 2014-08-12 14:04:04.753 2992 DEBUG nova.virt.hyperv.pathutils [req-98eaeb46-1272-40af-9205-09fff169f450 None] Creating directory: \\10.1.4.214\C$$\OpenStack\Instances\instance-05d6 _check_create_dir C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\virt\hyperv\pathutils.py:96 2014-08-12 14:07:20.177 2992 ERROR nova.compute.manager [req-98eaeb46-1272-40af-9205-09fff169f450 None] [instance: 904fa8eb-7377-4c42-9268-eae266b52648] Setting instance vm_state to ERROR 2014-08-12 14:07:20.177 2992 TRACE nova.compute.manager [instance: 904fa8eb-7377-4c42-9268-eae266b52648] Traceback (most recent call last): 2014-08-12 14:07:20.177 2992 TRACE nova.compute.manager [instance: 904fa8eb-7377-4c42-9268-eae266b52648] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\compute\manager.py, line 5780, in _error_out_instance_on_exception 2014-08-12 14:07:20.177 2992 TRACE nova.compute.manager [instance: 904fa8eb-7377-4c42-9268-eae266b52648] yield 2014-08-12 14:07:20.177 2992 TRACE nova.compute.manager [instance: 904fa8eb-7377-4c42-9268-eae266b52648] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\compute\manager.py, line 3569, in resize_instance 2014-08-12 14:07:20.177 2992 TRACE nova.compute.manager [instance: 904fa8eb-7377-4c42-9268-eae266b52648] block_device_info) 2014-08-12 14:07:20.177 2992 TRACE nova.compute.manager [instance: 904fa8eb-7377-4c42-9268-eae266b52648] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\virt\hyperv\driver.py, line 191, in migrate_disk_and_power_off 2014-08-12 14:07:20.177 2992 TRACE nova.compute.manager [instance: 904fa8eb-7377-4c42-9268-eae266b52648] block_device_info) 2014-08-12 14:07:20.177 2992 TRACE nova.compute.manager [instance: 904fa8eb-7377-4c42-9268-eae266b52648] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\virt\hyperv\migrationops.py, line 126, in migrate_disk_and_power_off
[Yahoo-eng-team] [Bug 1367786] [NEW] Hyper-V driver should log a clear error message during migrations for remote node permissions errors
Public bug reported: When failing to access a remote SMB UNC path, Python raises the following exception: WindowsError: [Error 123] The filename, directory name, or volume label syntax is incorrect: '' This is definitely misleading when troubleshooting the issue, which occurs during resize / cold migrations. The Nova driver should report a clear error message, making sure the user understands the full context. ** Affects: nova Importance: Low Status: Triaged ** Tags: hyper-v -- 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/1367786 Title: Hyper-V driver should log a clear error message during migrations for remote node permissions errors Status in OpenStack Compute (Nova): Triaged Bug description: When failing to access a remote SMB UNC path, Python raises the following exception: WindowsError: [Error 123] The filename, directory name, or volume label syntax is incorrect: '' This is definitely misleading when troubleshooting the issue, which occurs during resize / cold migrations. The Nova driver should report a clear error message, making sure the user understands the full context. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1367786/+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 1362075] [NEW] Live migration fails on Hyper-V when boot from volume is used
Public bug reported: Live migration fails on Hyper-V when boot from volume is used with CoW, as the target host tries to cache the root disk image in pre_live_migration, but in this case the image_ref is empty. ** Affects: nova Importance: Medium Status: Triaged ** Tags: hyper-v -- 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/1362075 Title: Live migration fails on Hyper-V when boot from volume is used Status in OpenStack Compute (Nova): Triaged Bug description: Live migration fails on Hyper-V when boot from volume is used with CoW, as the target host tries to cache the root disk image in pre_live_migration, but in this case the image_ref is empty. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1362075/+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 1361211] [NEW] Hyper-V agent does not add new VLAN ids to the external port's trunked list on Hyper-V 2008 R2
Public bug reported: This issue affects Hyper-V 2008 R2 and does not affect Hyper-V 2012 and above. The Hyper-V agent is correctly setting the VLAN ID and access mode settings on the vmswitch ports associated with a VM, but not on the trunked list associated with an external port. This is a required configuration. A workaround consists in setting the external port trunked list to contain all possible VLAN ids expected to be used in neutron's network configuration as provided by the following script: https://github.com/cloudbase/devstack-hyperv- incubator/blob/master/trunked_vlans_workaround_2008r2.ps1 ** Affects: neutron Importance: Undecided Status: Confirmed ** Tags: hyper-v ** Changed in: neutron Status: New = Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1361211 Title: Hyper-V agent does not add new VLAN ids to the external port's trunked list on Hyper-V 2008 R2 Status in OpenStack Neutron (virtual network service): Confirmed Bug description: This issue affects Hyper-V 2008 R2 and does not affect Hyper-V 2012 and above. The Hyper-V agent is correctly setting the VLAN ID and access mode settings on the vmswitch ports associated with a VM, but not on the trunked list associated with an external port. This is a required configuration. A workaround consists in setting the external port trunked list to contain all possible VLAN ids expected to be used in neutron's network configuration as provided by the following script: https://github.com/cloudbase/devstack-hyperv- incubator/blob/master/trunked_vlans_workaround_2008r2.ps1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1361211/+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 1361419] [NEW] Hyper-V driver should provide a more detailed exception in case block storage volumes cannot be mounted due to a invalid SAN policy
Public bug reported: On some versions of Windows Server 2008 R2 the SAN policy is set by default to Online All, bringing online any disk, local or shared, attached to the host. Since only offline disks can be attached as passthrough disks to a Hyper-V VM, this prevents Cinder volumes from being attached to instances, resulting in an exception: NotFound: Unable to find a mounted disk for target_iqn: iqn.2010-10.org.openstack:volume-d8904a90-d189-4fc8-a7b4-4fcdc7309166 Since this can be an issue not easy to troubleshoot without knowing the specific context, it'd be useful to include a reference to the SAN policy in the exception message. ** Affects: nova Importance: Low Status: Triaged ** Tags: hyper-v -- 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/1361419 Title: Hyper-V driver should provide a more detailed exception in case block storage volumes cannot be mounted due to a invalid SAN policy Status in OpenStack Compute (Nova): Triaged Bug description: On some versions of Windows Server 2008 R2 the SAN policy is set by default to Online All, bringing online any disk, local or shared, attached to the host. Since only offline disks can be attached as passthrough disks to a Hyper-V VM, this prevents Cinder volumes from being attached to instances, resulting in an exception: NotFound: Unable to find a mounted disk for target_iqn: iqn.2010-10.org.openstack:volume-d8904a90-d189-4fc8-a7b4-4fcdc7309166 Since this can be an issue not easy to troubleshoot without knowing the specific context, it'd be useful to include a reference to the SAN policy in the exception message. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1361419/+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 1360817] [NEW] Hyper-V agent fails on Hyper-V 2008 R2 due to missing remove_all_security_rules method
Public bug reported: A recent regression does not allow the Hyper-V agent to run successfully on Hyper-V 2008 R2, which is currently still a supported platform. The call generating the error is: https://github.com/openstack/neutron/blob/771327adbe9e563506f98ca561de9ded4d987698/neutron/plugins/hyperv/agent/hyperv_neutron_agent.py#L392 ** Affects: nova Importance: Undecided Status: New ** Tags: hyper-v -- 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/1360817 Title: Hyper-V agent fails on Hyper-V 2008 R2 due to missing remove_all_security_rules method Status in OpenStack Compute (Nova): New Bug description: A recent regression does not allow the Hyper-V agent to run successfully on Hyper-V 2008 R2, which is currently still a supported platform. The call generating the error is: https://github.com/openstack/neutron/blob/771327adbe9e563506f98ca561de9ded4d987698/neutron/plugins/hyperv/agent/hyperv_neutron_agent.py#L392 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1360817/+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 1360817] Re: Hyper-V agent fails on Hyper-V 2008 R2 due to missing remove_all_security_rules method
Proposed fix: https://review.openstack.org/#/c/116505/ (Not automatically picked up by Launchpad) ** Also affects: neutron Importance: Undecided Status: New ** No longer affects: nova ** Changed in: neutron Status: New = Confirmed ** Changed in: neutron Assignee: (unassigned) = Alessandro Pilotti (alexpilotti) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1360817 Title: Hyper-V agent fails on Hyper-V 2008 R2 due to missing remove_all_security_rules method Status in OpenStack Neutron (virtual network service): Confirmed Bug description: A recent regression does not allow the Hyper-V agent to run successfully on Hyper-V 2008 R2, which is currently still a supported platform. The call generating the error is: https://github.com/openstack/neutron/blob/771327adbe9e563506f98ca561de9ded4d987698/neutron/plugins/hyperv/agent/hyperv_neutron_agent.py#L392 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1360817/+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 1358702] [NEW] Hyper-V unit test fails on Windows due to path separator inconsistency: nova.tests.virt.hyperv.test_pathutils.PathUtilsTestCase.test_lookup_config_drive_path
Public bug reported: The following test fails due to mismatching in the path separator. FAIL: nova.tests.virt.hyperv.test_pathutils.PathUtilsTestCase.test_lookup_config_drive_path -- _StringException: Empty attachments: pythonlogging:'' Traceback (most recent call last): File C:\OpenStack\nova\nova\tests\virt\hyperv\test_pathutils.py, line 48, i test_lookup_configdrive_path format_ext) File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\ ite-packages\testtools\testcase.py, line 321, in assertEqual self.assertThat(observed, matcher, message) File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\ ite-packages\testtools\testcase.py, line 406, in assertThat raise mismatch_error MismatchError: !=: reference = 'C:/fake_instance_dir\\configdrive.vhd' actual= 'C:/fake_instance_dir/configdrive.vhd' ** Affects: nova Importance: Low Status: Triaged ** Tags: hyper-v ** Changed in: nova Importance: Undecided = Low ** Changed in: nova Status: New = Triaged -- 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/1358702 Title: Hyper-V unit test fails on Windows due to path separator inconsistency: nova.tests.virt.hyperv.test_pathutils.PathUtilsTestCase.test_lookup_config_drive_path Status in OpenStack Compute (Nova): Triaged Bug description: The following test fails due to mismatching in the path separator. FAIL: nova.tests.virt.hyperv.test_pathutils.PathUtilsTestCase.test_lookup_config_drive_path -- _StringException: Empty attachments: pythonlogging:'' Traceback (most recent call last): File C:\OpenStack\nova\nova\tests\virt\hyperv\test_pathutils.py, line 48, i test_lookup_configdrive_path format_ext) File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\ ite-packages\testtools\testcase.py, line 321, in assertEqual self.assertThat(observed, matcher, message) File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\ ite-packages\testtools\testcase.py, line 406, in assertThat raise mismatch_error MismatchError: !=: reference = 'C:/fake_instance_dir\\configdrive.vhd' actual= 'C:/fake_instance_dir/configdrive.vhd' To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1358702/+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 1358719] [NEW] Live migration fails as get_instance_disk_info is not present in the compute driver base class
Public bug reported: The get_instance_disk_info driver has been added to the libvirt compute driver in the following commit: https://github.com/openstack/nova/commit/e4974769743d5967626c1f0415113683411a03a4 This caused regression failures on drivers that do not implement it, e.g.: http://paste.openstack.org/show/97258/ The method has been subsequently added to the base class which, but raising a NotImplementedError(), which still causes the regression: https://github.com/openstack/nova/commit/2bed16c89356554a193a111d268a9587709ed2f7 ** Affects: nova Importance: Medium Status: Triaged ** Tags: hyper-v ** Changed in: nova Importance: Undecided = Medium ** Changed in: nova Status: New = Triaged -- 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/1358719 Title: Live migration fails as get_instance_disk_info is not present in the compute driver base class Status in OpenStack Compute (Nova): Triaged Bug description: The get_instance_disk_info driver has been added to the libvirt compute driver in the following commit: https://github.com/openstack/nova/commit/e4974769743d5967626c1f0415113683411a03a4 This caused regression failures on drivers that do not implement it, e.g.: http://paste.openstack.org/show/97258/ The method has been subsequently added to the base class which, but raising a NotImplementedError(), which still causes the regression: https://github.com/openstack/nova/commit/2bed16c89356554a193a111d268a9587709ed2f7 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1358719/+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 1355177] Re: hyperV: compute service goes off when booting an instance fails
This is the expected behaviour and it's unrelated to the Hyper-V driver. You can tell Nova not to use Neutron by unsetting network_api_class in nova.conf on your Hyper-V compute node(s) which will revert to the default (Nova network). Please note that Nova network is not supported on Hyper-V beyond the very basic flat networking. ** Changed in: nova Status: New = Invalid ** Tags removed: neutron-agent ** Tags added: hyper-v -- 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/1355177 Title: hyperV: compute service goes off when booting an instance fails Status in OpenStack Compute (Nova): Invalid Bug description: I have a 2012 R2 windows machine where hyperV, openstack nova compute service and openstack neutron hyperV agent is installed. I have a devstack running where neutron is not installed. When I am trying to boot an instance, it fails with error: ConnectionFailed: Connection to neutron failed: HTTPConnectionPool(host='x.x.x.x', port=9696): Max retries exceeded with url and further re-scheduled to a different host. But in the mean time compute service becomes dead in the hyperV host. nova list: nova-compute WIN-4EUO2SEHJ92 nova enabledXXX 2014-08-11 09:57:55 compute.log: 014-08-11 10:21:53.653 3924 ERROR nova.compute.manager [req-69c46c41-0aa1-47cc-8abe-7306ec5ef57d None] [instance: 6d430014-faa6-4af5-9701-063f61f4eb40] Instance failed to spawn 2014-08-11 10:21:53.653 3924 TRACE nova.compute.manager [instance: 6d430014-faa6-4af5-9701-063f61f4eb40] Traceback (most recent call last): 2014-08-11 10:21:53.653 3924 TRACE nova.compute.manager [instance: 6d430014-faa6-4af5-9701-063f61f4eb40] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\compute\manager.py, line 2108, in _build_resources 2014-08-11 10:21:53.653 3924 TRACE nova.compute.manager [instance: 6d430014-faa6-4af5-9701-063f61f4eb40] yield resources 2014-08-11 10:21:53.653 3924 TRACE nova.compute.manager [instance: 6d430014-faa6-4af5-9701-063f61f4eb40] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\compute\manager.py, line 1994, in _build_and_run_instance 2014-08-11 10:21:53.653 3924 TRACE nova.compute.manager [instance: 6d430014-faa6-4af5-9701-063f61f4eb40] block_device_info=block_device_info) 2014-08-11 10:21:53.653 3924 TRACE nova.compute.manager [instance: 6d430014-faa6-4af5-9701-063f61f4eb40] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\virt\hyperv\driver.py, line 55, in spawn 2014-08-11 10:21:53.653 3924 TRACE nova.compute.manager [instance: 6d430014-faa6-4af5-9701-063f61f4eb40] admin_password, network_info, block_device_info) 2014-08-11 10:21:53.653 3924 TRACE nova.compute.manager [instance: 6d430014-faa6-4af5-9701-063f61f4eb40] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\virt\hyperv\vmops.py, line 87, in wrapper 2014-08-11 10:21:53.653 3924 TRACE nova.compute.manager [instance: 6d430014-faa6-4af5-9701-063f61f4eb40] return function(self, *args, **kwds) 2014-08-11 10:21:53.653 3924 TRACE nova.compute.manager [instance: 6d430014-faa6-4af5-9701-063f61f4eb40] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\virt\hyperv\vmops.py, line 255, in spawn 2014-08-11 10:21:53.653 3924 TRACE nova.compute.manager [instance: 6d430014-faa6-4af5-9701-063f61f4eb40] self.destroy(instance) 2014-08-11 10:21:53.653 3924 TRACE nova.compute.manager [instance: 6d430014-faa6-4af5-9701-063f61f4eb40] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\openstack\common\excutils.py, line 82, in __exit__ 2014-08-11 10:21:53.653 3924 TRACE nova.compute.manager [instance: 6d430014-faa6-4af5-9701-063f61f4eb40] six.reraise(self.type_, self.value, self.tb) 2014-08-11 10:21:53.653 3924 TRACE nova.compute.manager [instance: 6d430014-faa6-4af5-9701-063f61f4eb40] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\virt\hyperv\vmops.py, line 246, in spawn 2014-08-11 10:21:53.653 3924 TRACE nova.compute.manager [instance: 6d430014-faa6-4af5-9701-063f61f4eb40] root_vhd_path, eph_vhd_path) 2014-08-11 10:21:53.653 3924 TRACE nova.compute.manager [instance: 6d430014-faa6-4af5-9701-063f61f4eb40] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\virt\hyperv\vmops.py, line 289, in create_instance 2014-08-11 10:21:53.653 3924 TRACE nova.compute.manager [instance: 6d430014-faa6-4af5-9701-063f61f4eb40] for vif in network_info: 2014-08-11 10:21:53.653 3924 TRACE nova.compute.manager [instance:
[Yahoo-eng-team] [Bug 1294682] Re: Hyper-v VHDX resizing not working when using differencing images
Converted in blueprint: https://blueprints.launchpad.net/nova/+spec/add- differencing-vhdx-resize-support Merged in Juno ** Changed in: nova Status: In Progress = 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/1294682 Title: Hyper-v VHDX resizing not working when using differencing images Status in OpenStack Compute (Nova): Invalid Bug description: When spawning a new VM using cow images, the root image won't get the size of the flavor. Instead, it will have the size of the base image no resize is attempted. In this case, the proper size should be specified when creating the differencing image. If after that one attempts to resize the VM, the get_internal_vhd_size_by_file_size method will raise an exception as it can't get this info out of the differencing image. Instead of raising this exception, this method may recurse by calling itself on the parent of the differencing image. This happens on both V1 and V2 namespaces. Trace: http://paste.openstack.org/show/73825/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1294682/+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 1354448] [NEW] The Hyper-V driver should raise a InstanceFaultRollback in case of resize down requests
Public bug reported: The Hyper-V driver does not support resize down and is currently rising an exception if the user attempts to do that, causing the instance to go in ERROR state. The driver should use the recently introduced instance faults exception.InstanceFaultRollback instead, which will leave the instance in ACTIVE state as expected. ** Affects: nova Importance: Medium Status: Triaged ** Tags: hyper-v ** Changed in: nova Status: New = Triaged ** 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/1354448 Title: The Hyper-V driver should raise a InstanceFaultRollback in case of resize down requests Status in OpenStack Compute (Nova): Triaged Bug description: The Hyper-V driver does not support resize down and is currently rising an exception if the user attempts to do that, causing the instance to go in ERROR state. The driver should use the recently introduced instance faults exception.InstanceFaultRollback instead, which will leave the instance in ACTIVE state as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1354448/+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 1353697] [NEW] Hyper-V agent raises UnsupportedRpcVersion: Specified RPC version, 1.1, not supported by this endpoint.
Public bug reported: The Hyper-V agent raises: 2014-08-06 10:42:37.096 2052 ERROR neutron.openstack.common.rpc.amqp [req-46340a1a-9143-45c9-b645-2612d41f20a6 None] Exception during message handling 2014-08-06 10:42:37.096 2052 TRACE neutron.openstack.common.rpc.amqp Traceback (most recent call last): 2014-08-06 10:42:37.096 2052 TRACE neutron.openstack.common.rpc.amqp File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\neutron\openstack\common\rpc\amqp.py, line 462, in _process_data 2014-08-06 10:42:37.096 2052 TRACE neutron.openstack.common.rpc.amqp **args) 2014-08-06 10:42:37.096 2052 TRACE neutron.openstack.common.rpc.amqp File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\neutron\openstack\common\rpc\dispatcher.py, line 178, in dispatch 2014-08-06 10:42:37.096 2052 TRACE neutron.openstack.common.rpc.amqp raise rpc_common.UnsupportedRpcVersion(version=version) 2014-08-06 10:42:37.096 2052 TRACE neutron.openstack.common.rpc.amqp UnsupportedRpcVersion: Specified RPC version, 1.1, not supported by this endpoint. 2014-08-06 10:42:37.096 2052 TRACE neutron.openstack.common.rpc.amqp The issue does not affect functionality, but it creates a lot of noise in the logs since the error is logged at each iteration. ** Affects: neutron Importance: Undecided Status: Confirmed ** Tags: hyper-v ** Changed in: neutron Status: New = Incomplete ** Changed in: neutron Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1353697 Title: Hyper-V agent raises UnsupportedRpcVersion: Specified RPC version, 1.1, not supported by this endpoint. Status in OpenStack Neutron (virtual network service): Confirmed Bug description: The Hyper-V agent raises: 2014-08-06 10:42:37.096 2052 ERROR neutron.openstack.common.rpc.amqp [req-46340a1a-9143-45c9-b645-2612d41f20a6 None] Exception during message handling 2014-08-06 10:42:37.096 2052 TRACE neutron.openstack.common.rpc.amqp Traceback (most recent call last): 2014-08-06 10:42:37.096 2052 TRACE neutron.openstack.common.rpc.amqp File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\neutron\openstack\common\rpc\amqp.py, line 462, in _process_data 2014-08-06 10:42:37.096 2052 TRACE neutron.openstack.common.rpc.amqp **args) 2014-08-06 10:42:37.096 2052 TRACE neutron.openstack.common.rpc.amqp File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\neutron\openstack\common\rpc\dispatcher.py, line 178, in dispatch 2014-08-06 10:42:37.096 2052 TRACE neutron.openstack.common.rpc.amqp raise rpc_common.UnsupportedRpcVersion(version=version) 2014-08-06 10:42:37.096 2052 TRACE neutron.openstack.common.rpc.amqp UnsupportedRpcVersion: Specified RPC version, 1.1, not supported by this endpoint. 2014-08-06 10:42:37.096 2052 TRACE neutron.openstack.common.rpc.amqp The issue does not affect functionality, but it creates a lot of noise in the logs since the error is logged at each iteration. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1353697/+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 1347777] [NEW] The compute_driver option description does not include the Hyper-V driver
Public bug reported: The description of the option compute_driver should include hyperv.HyperVDriver along with the other supported drivers https://github.com/openstack/nova/blob/aa018a718654b5f868c1226a6db7630751613d92/nova/virt/driver.py#L35-L38 ** Affects: nova Importance: Low Status: Confirmed ** Tags: hyper-v ** Changed in: nova Status: New = Confirmed ** Changed in: nova Importance: Undecided = Low -- 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/134 Title: The compute_driver option description does not include the Hyper-V driver Status in OpenStack Compute (Nova): Confirmed Bug description: The description of the option compute_driver should include hyperv.HyperVDriver along with the other supported drivers https://github.com/openstack/nova/blob/aa018a718654b5f868c1226a6db7630751613d92/nova/virt/driver.py#L35-L38 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/134/+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 1342348] Re: Hyper-V agent IDE/SCSI related refactoring necessary
** Changed in: nova Status: In Progress = 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/1342348 Title: Hyper-V agent IDE/SCSI related refactoring necessary Status in OpenStack Compute (Nova): Invalid Bug description: Hyper-V Server 2012 R2 introduces a new feature for virtual machines named generation 2, consisting mainly in a new firmware and better support for synthetic devices. Generation 2 VMs don't support IDE devices, which means that local boot, ephemeral disks and DVD Drives must be attached as SCSI, instead of IDE for generation 1 VMs. Since the Virtual Hard Disks and Virtual CD/DVD Disks can be attached to IDE controllers or SCSI controllers (generation 2 only), some constants, variables and methods have been improperly named, having the IDE prefix. e.g.: _IDE_DISK_RES_SUB_TYPE will have to be renamed to _HARD_DISK_RES_SUB_TYPE To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1342348/+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 1335897] [NEW] lockutils blocking issue on Windows due to fcntl
Public bug reported: lockutils is failing on Windows due to an import fcntl (unavailable on Windows). The issue has been introduced with this commit: https://github.com/openstack/oslo- incubator/commit/9b73c19b2e04e6db0dc70046e0ba5e5e22446996 ** Affects: nova Importance: Critical Status: New ** Affects: oslo Importance: Undecided Status: Confirmed ** Tags: hyper-v ** Changed in: oslo Status: New = Confirmed ** Also affects: nova Importance: Undecided Status: New ** Changed in: nova Importance: Undecided = High ** Changed in: nova Importance: High = Critical -- 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/1335897 Title: lockutils blocking issue on Windows due to fcntl Status in OpenStack Compute (Nova): New Status in Oslo - a Library of Common OpenStack Code: Confirmed Bug description: lockutils is failing on Windows due to an import fcntl (unavailable on Windows). The issue has been introduced with this commit: https://github.com/openstack/oslo- incubator/commit/9b73c19b2e04e6db0dc70046e0ba5e5e22446996 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1335897/+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 1322926] [NEW] Hyper-V driver volumes are attached incorrectly when multiple iSCSI servers are present
Public bug reported: Hyper-V can change the order of the mounted drives when rebooting a host and thus passthrough disks can be assigned to the wrong instance resulting in a critical scenario. ** Affects: nova Importance: Critical Status: Triaged ** Tags: hyper-v ** Tags added: hyper-v ** Changed in: nova Status: New = Triaged ** Changed in: nova Importance: Undecided = Critical ** Changed in: nova Milestone: None = juno-1 -- 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/1322926 Title: Hyper-V driver volumes are attached incorrectly when multiple iSCSI servers are present Status in OpenStack Compute (Nova): Triaged Bug description: Hyper-V can change the order of the mounted drives when rebooting a host and thus passthrough disks can be assigned to the wrong instance resulting in a critical scenario. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1322926/+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 1287983] Re: hyperv check failure
** Changed in: neutron Status: New = Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1287983 Title: hyperv check failure Status in OpenStack Neutron (virtual network service): Invalid Status in OpenStack Compute (Nova): Invalid Bug description: http://64.119.130.115/78028/3/ http://64.119.130.115/78028/3/Hyper-V_logs/hv-compute1/nova-compute.log.gz has lot of stacktraces 2014-03-04 18:48:39.417 4516 TRACE nova.compute.manager [instance: db1c9be4-318c-450f-b4bf-5de90cc09c43] ConnectionFailed: Connection to neutron failed: Maximum attempts reached 2014-03-04 18:54:53.631 4516 TRACE nova.virt.hyperv.vmops HyperVException: Operation failed with return value: 32775 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1287983/+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 1301368] [NEW] Hyper-V configdrive is not atatched after resizing an instance
Public bug reported: The following bug fix takes care of copying the configdrive to the resize target, but it does not attach it to the instance. https://bugs.launchpad.net/nova/+bug/1250324 ** Affects: nova Importance: Undecided Assignee: Adrian Vladu (avladu) Status: New ** Tags: hyper-v ** Tags added: hyper-v -- 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/1301368 Title: Hyper-V configdrive is not atatched after resizing an instance Status in OpenStack Compute (Nova): New Bug description: The following bug fix takes care of copying the configdrive to the resize target, but it does not attach it to the instance. https://bugs.launchpad.net/nova/+bug/1250324 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1301368/+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 1298034] [NEW] Nova Hyper-V driver fails occasionally with a x_wmi_uninitialised_thread exception
Public bug reported: The Nova Hyper-V driver can fail occasionally with: x_wmi_uninitialised_thread (WMI returned a syntax error: you're probably running inside a thread without first calling pythoncom.CoInitialize[Ex] http://64.119.130.115/82904/14/Hyper-V_logs/hv-compute1/neutron-hyperv- agent.log.gz Each thread that uses COM needs to initialize COM by calling pythoncom.CoInitialize or pythoncom.CoInitializeEx. Error stack trace: http://64.119.130.115/82904/14/Hyper-V_logs/hv-compute1/neutron-hyperv- agent.log.gz ** Affects: nova Importance: Low Status: New ** Tags: hyper-v ** Tags added: hyper-v ** Changed in: nova Importance: Undecided = Low -- 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/1298034 Title: Nova Hyper-V driver fails occasionally with a x_wmi_uninitialised_thread exception Status in OpenStack Compute (Nova): New Bug description: The Nova Hyper-V driver can fail occasionally with: x_wmi_uninitialised_thread (WMI returned a syntax error: you're probably running inside a thread without first calling pythoncom.CoInitialize[Ex] http://64.119.130.115/82904/14/Hyper-V_logs/hv-compute1/neutron- hyperv-agent.log.gz Each thread that uses COM needs to initialize COM by calling pythoncom.CoInitialize or pythoncom.CoInitializeEx. Error stack trace: http://64.119.130.115/82904/14/Hyper-V_logs/hv-compute1/neutron- hyperv-agent.log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1298034/+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 1297569] [NEW] pre_live_migration fails due to RPC timeout
Public bug reported: Live migration fails when the pre_live_migration execution takes more time than the default RPC timeout. For example, in the case of Hyper-V this can happen if a Glance image needs to be downloaded in the cache before the live migration can take place for a CoW disk. Trace: http://paste.openstack.org/show/74210/ ** Affects: nova Importance: High Assignee: Alessandro Pilotti (alexpilotti) Status: New ** Tags: hyper-v icehouse-rc-potential ** Tags added: hyper-v icehouse-rc-potential ** Changed in: nova Importance: Undecided = High ** Changed in: nova Assignee: (unassigned) = Alessandro Pilotti (alexpilotti) -- 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/1297569 Title: pre_live_migration fails due to RPC timeout Status in OpenStack Compute (Nova): New Bug description: Live migration fails when the pre_live_migration execution takes more time than the default RPC timeout. For example, in the case of Hyper-V this can happen if a Glance image needs to be downloaded in the cache before the live migration can take place for a CoW disk. Trace: http://paste.openstack.org/show/74210/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1297569/+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 1263766] Re: Hyper-V agent fails when ceilometer ACLs are already applied
This bug has bee invalidated by patches that merged subsequently. ** Changed in: neutron Status: In Progress = Incomplete ** Changed in: neutron Status: Incomplete = Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1263766 Title: Hyper-V agent fails when ceilometer ACLs are already applied Status in OpenStack Neutron (virtual network service): Invalid Bug description: The Hyper-V agent fails when the restarted after the ceilometer ACLs have been already applied. Stack trace: http://pastebin.com/xnuszXid To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1263766/+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 1296478] [NEW] Hyper-V's list_instances() returns an empty result set on certain localized versions of the OS
Public bug reported: This issue is related to different values that MSVM_ComputerSystem's Caption property can have on different locales. ** Affects: nova Importance: Undecided Status: New ** Tags: hyper-v ** Tags added: hyper-v -- 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/1296478 Title: Hyper-V's list_instances() returns an empty result set on certain localized versions of the OS Status in OpenStack Compute (Nova): New Bug description: This issue is related to different values that MSVM_ComputerSystem's Caption property can have on different locales. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1296478/+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 1291006] [NEW] Clear text admin password assignment in instance creation should be disabled
Public bug reported: The clear text admin password management available in the instance creation security tab should be removed as it has been superseded in both Nova and Horizon by an encrypted password management. Nova blueprint (Grizzly): https://blueprints.launchpad.net/nova/+spec/get-password Horizon blueprint (Icehouse): https://blueprints.launchpad.net/horizon/+spec/decrypt-and-display-vm-generated-password Since this feature is now available in Horizon as well, providing an option for the users to specify the password is both misleading and non secure. Furthermore, the oldway of providing a clear text passwords works only on selected hypervisors and it does not work for Windows guests, which represent at the moment the main use case since SSH keypair authentication does not apply ** Affects: horizon Importance: Undecided Assignee: Alessandro Pilotti (alexpilotti) Status: New ** Changed in: horizon Assignee: (unassigned) = Alessandro Pilotti (alexpilotti) -- 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/1291006 Title: Clear text admin password assignment in instance creation should be disabled Status in OpenStack Dashboard (Horizon): New Bug description: The clear text admin password management available in the instance creation security tab should be removed as it has been superseded in both Nova and Horizon by an encrypted password management. Nova blueprint (Grizzly): https://blueprints.launchpad.net/nova/+spec/get-password Horizon blueprint (Icehouse): https://blueprints.launchpad.net/horizon/+spec/decrypt-and-display-vm-generated-password Since this feature is now available in Horizon as well, providing an option for the users to specify the password is both misleading and non secure. Furthermore, the oldway of providing a clear text passwords works only on selected hypervisors and it does not work for Windows guests, which represent at the moment the main use case since SSH keypair authentication does not apply To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1291006/+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 1286528] [NEW] guru-meditation fails on Windows due to non portable signal handling
Public bug reported:
The guru-meditation report fails on Hyper-V due to missing signal
handling.
This is a blocking issue on WIndows.
http://64.119.130.115/74060/3/Hyper-V_logs/hv-compute1/nova-
console.log.gz
Traceback (most recent call last):
File c:\OpenStack\virtualenv\Scripts\nova-compute-script.py, line 9, in
module
load_entry_point('nova==2014.1.dev954.g3a611cc', 'console_scripts',
'nova-compute')()
File c:\OpenStack\virtualenv\lib\site-packages\pkg_resources.py, line 353,
in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File c:\OpenStack\virtualenv\lib\site-packages\pkg_resources.py, line 2321,
in load_entry_point
return ep.load()
File c:\OpenStack\virtualenv\lib\site-packages\pkg_resources.py, line 2048,
in load
entry = __import__(self.module_name, globals(),globals(), ['__name__'])
File c:\OpenStack\virtualenv\lib\site-packages\nova\cmd\compute.py, line
32, in module
from nova.openstack.common.report import guru_meditation_report as gmr
File
c:\OpenStack\virtualenv\lib\site-packages\nova\openstack\common\report\guru_meditation_report.py,
line 63, in module
class GuruMeditation(object):
File
c:\OpenStack\virtualenv\lib\site-packages\nova\openstack\common\report\guru_meditation_report.py,
line 100, in GuruMeditation
def setup_autorun(cls, version, signum=signal.SIGUSR1):
AttributeError: 'module' object has no attribute 'SIGUSR1'
** Affects: nova
Importance: Critical
Status: New
** Affects: oslo
Importance: Undecided
Status: New
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: nova
Importance: Undecided = Critical
--
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/1286528
Title:
guru-meditation fails on Windows due to non portable signal handling
Status in OpenStack Compute (Nova):
New
Status in Oslo - a Library of Common OpenStack Code:
New
Bug description:
The guru-meditation report fails on Hyper-V due to missing signal
handling.
This is a blocking issue on WIndows.
http://64.119.130.115/74060/3/Hyper-V_logs/hv-compute1/nova-
console.log.gz
Traceback (most recent call last):
File c:\OpenStack\virtualenv\Scripts\nova-compute-script.py, line 9, in
module
load_entry_point('nova==2014.1.dev954.g3a611cc', 'console_scripts',
'nova-compute')()
File c:\OpenStack\virtualenv\lib\site-packages\pkg_resources.py, line
353, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File c:\OpenStack\virtualenv\lib\site-packages\pkg_resources.py, line
2321, in load_entry_point
return ep.load()
File c:\OpenStack\virtualenv\lib\site-packages\pkg_resources.py, line
2048, in load
entry = __import__(self.module_name, globals(),globals(), ['__name__'])
File c:\OpenStack\virtualenv\lib\site-packages\nova\cmd\compute.py, line
32, in module
from nova.openstack.common.report import guru_meditation_report as gmr
File
c:\OpenStack\virtualenv\lib\site-packages\nova\openstack\common\report\guru_meditation_report.py,
line 63, in module
class GuruMeditation(object):
File
c:\OpenStack\virtualenv\lib\site-packages\nova\openstack\common\report\guru_meditation_report.py,
line 100, in GuruMeditation
def setup_autorun(cls, version, signum=signal.SIGUSR1):
AttributeError: 'module' object has no attribute 'SIGUSR1'
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1286528/+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 1280363] [NEW] Replace exception re-raises with excutils.save_and_reraise_exception() in the HYper-V driver
Public bug reported: A few methods of the Hyper-V driver ops classes use a catch / raise pattern that replaces original exceptions with specific domain exceptions inherited from vmutils.HyperVUtilsException(). The original exception is thus masqueraded and trackable only by analysing the logs. ** Affects: nova Importance: Medium Assignee: Alessandro Pilotti (alexpilotti) Status: In Progress ** Tags: hyper-v ** Tags added: hyper-v ** Changed in: nova Status: New = In Progress ** Changed in: nova Importance: Undecided = Medium ** Changed in: nova Assignee: (unassigned) = Alessandro Pilotti (alexpilotti) -- 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/1280363 Title: Replace exception re-raises with excutils.save_and_reraise_exception() in the HYper-V driver Status in OpenStack Compute (Nova): In Progress Bug description: A few methods of the Hyper-V driver ops classes use a catch / raise pattern that replaces original exceptions with specific domain exceptions inherited from vmutils.HyperVUtilsException(). The original exception is thus masqueraded and trackable only by analysing the logs. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1280363/+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 1280379] [NEW] volumeops are incorrectly inheriting from HyperVAPITestCase
Public bug reported: The VolumeOpsTestCase class in test_hypervapi.py inherits from HyperVAPITestCase, resulting in all the tests from the base class being executed twice. ** Affects: nova Importance: Undecided Status: In Progress ** Tags: hyper-v ** Tags added: hyper-v ** Changed in: nova Status: New = In Progress -- 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/1280379 Title: volumeops are incorrectly inheriting from HyperVAPITestCase Status in OpenStack Compute (Nova): In Progress Bug description: The VolumeOpsTestCase class in test_hypervapi.py inherits from HyperVAPITestCase, resulting in all the tests from the base class being executed twice. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1280379/+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 1276772] [NEW] Instance deletion fails due to race condition on Hyper-V
Public bug reported: A recently merge patch separates the lock required to delete an instance from the one used during instance creation and other operations. This leads to race conditions in the Hyper-V driver, as the spawn and destroy methods have been written considering that locking already occurs at the compute manager level. This patch has already been committed, reverted and committed again: https://review.openstack.org/#/c/55444/ https://review.openstack.org/#/c/69987/ https://review.openstack.org/#/c/70187/ ** Affects: nova Importance: Undecided Status: New ** Tags: hyper-v ** Tags added: hyper-v -- 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/1276772 Title: Instance deletion fails due to race condition on Hyper-V Status in OpenStack Compute (Nova): New Bug description: A recently merge patch separates the lock required to delete an instance from the one used during instance creation and other operations. This leads to race conditions in the Hyper-V driver, as the spawn and destroy methods have been written considering that locking already occurs at the compute manager level. This patch has already been committed, reverted and committed again: https://review.openstack.org/#/c/55444/ https://review.openstack.org/#/c/69987/ https://review.openstack.org/#/c/70187/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1276772/+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 1275772] [NEW] Missing raise statement in the Hyper-V driver when checking the config driver format
Public bug reported: There's a missing raise statement when checking the ConfigDrive format: https://github.com/openstack/nova/blob/master/nova/virt/hyperv/vmops.py#L283 ** Affects: nova Importance: Undecided Status: New ** Tags: havana-backport-potential hyper-v ** Tags added: hyper-v ** Tags added: havana-backport-potential -- 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/1275772 Title: Missing raise statement in the Hyper-V driver when checking the config driver format Status in OpenStack Compute (Nova): New Bug description: There's a missing raise statement when checking the ConfigDrive format: https://github.com/openstack/nova/blob/master/nova/virt/hyperv/vmops.py#L283 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1275772/+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 1275802] [NEW] Wrong variable name in debug statement in the Hyper-V driver
Public bug reported: Here's a minor issue in the naming of a variable in a debug statement formatting: https://github.com/openstack/nova/blob/8f28ddd13a91eb25f0f2f3a312068223500ded97/nova/virt/hyperv/snapshotops.py#L107 ** Affects: nova Importance: Undecided Status: New ** Tags: havana-backport-potential hyper-v ** Tags added: havana-backport-potential hyper-v -- 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/1275802 Title: Wrong variable name in debug statement in the Hyper-V driver Status in OpenStack Compute (Nova): New Bug description: Here's a minor issue in the naming of a variable in a debug statement formatting: https://github.com/openstack/nova/blob/8f28ddd13a91eb25f0f2f3a312068223500ded97/nova/virt/hyperv/snapshotops.py#L107 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1275802/+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 1275805] [NEW] Wrong variable used in log statement in the HYper-V driver
Public bug reported: This patch includes some improved logging during resizes in the Hyper-V driver: https://review.openstack.org/#/c/51129/ There's a small issue in the variable used: root_vhd should be replaced with root_vhd_internal_size ** Affects: nova Importance: Undecided Status: New ** Tags: havana-backport-potential hyper-v ** Tags added: havana-backport-potential hyper-v -- 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/1275805 Title: Wrong variable used in log statement in the HYper-V driver Status in OpenStack Compute (Nova): New Bug description: This patch includes some improved logging during resizes in the Hyper-V driver: https://review.openstack.org/#/c/51129/ There's a small issue in the variable used: root_vhd should be replaced with root_vhd_internal_size To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1275805/+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 1266794] [NEW] Neutron install fails on Windows
Public bug reported: python setup.py install fails on Windows due to this patch: https://review.openstack.org/#/c/64747/ with the following error: setup.py install now fails on Windows due to this patch with the following error: error: can't copy 'etc\neutron\plugins\nicira\nvp.ini': doesn't exist or not a regular file The issue is related to the usage of symlinks which are not supported on Windows in: etc/neutron/plugins/nicira ** 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/1266794 Title: Neutron install fails on Windows Status in OpenStack Neutron (virtual network service): New Bug description: python setup.py install fails on Windows due to this patch: https://review.openstack.org/#/c/64747/ with the following error: setup.py install now fails on Windows due to this patch with the following error: error: can't copy 'etc\neutron\plugins\nicira\nvp.ini': doesn't exist or not a regular file The issue is related to the usage of symlinks which are not supported on Windows in: etc/neutron/plugins/nicira To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1266794/+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 1263766] [NEW] Hyper-V agent fails when ceilometer ACLs are already applied
Public bug reported: The Hyper-V agent fails when the restarted after the ceilometer ACLs have been already applied. ** Affects: neutron Importance: Undecided Status: New ** Tags: havana-backport-potential hyper-v ** Tags added: hyper-v ** Tags added: havana-backport-potential -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1263766 Title: Hyper-V agent fails when ceilometer ACLs are already applied Status in OpenStack Neutron (virtual network service): New Bug description: The Hyper-V agent fails when the restarted after the ceilometer ACLs have been already applied. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1263766/+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 1252476] Re: hyper-v : Havana-fails to spawn an instance - InstanceInfoCache version incompatiblity
*** This bug is a duplicate of bug 1239709 *** https://bugs.launchpad.net/bugs/1239709 ** This bug has been marked a duplicate of bug 1239709 NovaObject does not properly honor VERSION -- 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/1252476 Title: hyper-v : Havana-fails to spawn an instance - InstanceInfoCache version incompatiblity Status in OpenStack Compute (Nova): New Bug description: Using Havana version of openstack controller node Network node (ovs/flat) Compute node: Windows server eval version/Hyper V /nova-compute (havana beta openstack nova-compute from cloudbase)/neutron hyperv agent. Launched a windows server image (vhd image). Spawing fails with InstanceInfoCache version 1.4 incompatible error Here is the nova-compute log on windows compute node detail: 2013-11-18 11:59:32.118 888 ERROR nova.network.api [req-0ee0e33d-271b-4d18-870c-44d560ff5624 dee0091feba94eb688eda0966425aff9 599959b0a6eb4fbc9b2b19ead1cde4f9] [instance: aed01180-abf1-407d-a5d2-74d15c4e0d22] Failed storing info cache 2013-11-18 11:59:32.118 888 TRACE nova.network.api [instance: aed01180-abf1-407d-a5d2-74d15c4e0d22] Traceback (most recent call last): 2013-11-18 11:59:32.118 888 TRACE nova.network.api [instance: aed01180-abf1-407d-a5d2-74d15c4e0d22] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\network\api.py, line 81, in update_instance_cache_with_nw_info 2013-11-18 11:59:32.118 888 TRACE nova.network.api [instance: aed01180-abf1-407d-a5d2-74d15c4e0d22] ic.save(update_cells=update_cells) 2013-11-18 11:59:32.118 888 TRACE nova.network.api [instance: aed01180-abf1-407d-a5d2-74d15c4e0d22] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\objects\base.py, line 141, in wrapper 2013-11-18 11:59:32.118 888 TRACE nova.network.api [instance: aed01180-abf1-407d-a5d2-74d15c4e0d22] ctxt, self, fn.__name__, args, kwargs) 2013-11-18 11:59:32.118 888 TRACE nova.network.api [instance: aed01180-abf1-407d-a5d2-74d15c4e0d22] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\conductor\rpcapi.py, line 483, in object_action 2013-11-18 11:59:32.118 888 TRACE nova.network.api [instance: aed01180-abf1-407d-a5d2-74d15c4e0d22] objmethod=objmethod, args=args, kwargs=kwargs) 2013-11-18 11:59:32.118 888 TRACE nova.network.api [instance: aed01180-abf1-407d-a5d2-74d15c4e0d22] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\rpcclient.py, line 85, in call 2013-11-18 11:59:32.118 888 TRACE nova.network.api [instance: aed01180-abf1-407d-a5d2-74d15c4e0d22] return self._invoke(self.proxy.call, ctxt, method, **kwargs) 2013-11-18 11:59:32.118 888 TRACE nova.network.api [instance: aed01180-abf1-407d-a5d2-74d15c4e0d22] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\rpcclient.py, line 63, in _invoke 2013-11-18 11:59:32.118 888 TRACE nova.network.api [instance: aed01180-abf1-407d-a5d2-74d15c4e0d22] return cast_or_call(ctxt, msg, **self.kwargs) 2013-11-18 11:59:32.118 888 TRACE nova.network.api [instance: aed01180-abf1-407d-a5d2-74d15c4e0d22] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\openstack\common\rpc\proxy.py, line 126, in call 2013-11-18 11:59:32.118 888 TRACE nova.network.api [instance: aed01180-abf1-407d-a5d2-74d15c4e0d22] result = rpc.call(context, real_topic, msg, timeout) 2013-11-18 11:59:32.118 888 TRACE nova.network.api [instance: aed01180-abf1-407d-a5d2-74d15c4e0d22] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\openstack\common\rpc\__init__.py, line 139, in call 2013-11-18 11:59:32.118 888 TRACE nova.network.api [instance: aed01180-abf1-407d-a5d2-74d15c4e0d22] return _get_impl().call(CONF, context, topic, msg, timeout) 2013-11-18 11:59:32.118 888 TRACE nova.network.api [instance: aed01180-abf1-407d-a5d2-74d15c4e0d22] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\openstack\common\rpc\impl_kombu.py, line 816, in call 2013-11-18 11:59:32.118 888 TRACE nova.network.api [instance: aed01180-abf1-407d-a5d2-74d15c4e0d22] rpc_amqp.get_connection_pool(conf, Connection)) 2013-11-18 11:59:32.118 888 TRACE nova.network.api [instance: aed01180-abf1-407d-a5d2-74d15c4e0d22] File C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\nova\openstack\common\rpc\amqp.py, line 574, in call 2013-11-18 11:59:32.118 888 TRACE nova.network.api [instance: aed01180-abf1-407d-a5d2-74d15c4e0d22] rv = list(rv) 2013-11-18 11:59:32.118 888 TRACE nova.network.api [instance:
[Yahoo-eng-team] [Bug 1261585] [NEW] ConfigDrive metadata is incorrectly generated on Windows
Public bug reported: Files must be written with wb instead of w in order to support multiple platforms: https://github.com/openstack/nova/blob/b823db737855149ba847e5b19df9232f109f6001/nova/virt/configdrive.py#L92 ** Affects: nova Importance: Undecided Status: New ** Tags: hyper-v ** Tags added: hyper-v -- 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/1261585 Title: ConfigDrive metadata is incorrectly generated on Windows Status in OpenStack Compute (Nova): New Bug description: Files must be written with wb instead of w in order to support multiple platforms: https://github.com/openstack/nova/blob/b823db737855149ba847e5b19df9232f109f6001/nova/virt/configdrive.py#L92 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1261585/+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 1177708] Re: Resize instance fails on Hyper-V due to my_ip set to 127.0.0.1 when routing to 8.8.8.8 fails
** Changed in: nova Status: Triaged = 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/1177708 Title: Resize instance fails on Hyper-V due to my_ip set to 127.0.0.1 when routing to 8.8.8.8 fails Status in OpenStack Compute (Nova): Invalid Bug description: Hyper-V driver gets host_ip from https://github.com/openstack/nova/blob/master/nova/virt/hyperv/hostops.py#L169 , will use my_ip got from https://github.com/openstack/nova/blob/master/nova/netconf.py firstly. If it raise a execption without my_ip set in nova.conf and can't connect to Google DNS server , my_ip will be '127.0.0.1'. In this situation will report Hyper-V host 's ip '127.0.0.1' to control node . It raise IO exception during resize To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1177708/+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 1153966] Re: Fix locking issues in Windows
** 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 Compute (nova). https://bugs.launchpad.net/bugs/1153966 Title: Fix locking issues in Windows Status in Cinder: Fix Released Status in OpenStack Compute (Nova): Fix Released Status in Oslo - a Library of Common OpenStack Code: Fix Released Bug description: When attaching a volume the next error is occurred: 2013-03-11 21:43:29.921 ERROR cinder.openstack.common.rpc.common [req-946e0c80-f48a-431d-8848-997d993f4fce 4353ebfbc4764cd1882c0f336f73ae72 be2150f90f034291b2bbfcd72d7e4884] Returning exception an integer is required to caller 2013-03-11 21:43:29.921 ERROR cinder.openstack.common.rpc.common [req-946e0c80-f48a-431d-8848-997d993f4fce 4353ebfbc4764cd1882c0f336f73ae72 be2150f90f034291b2bbfcd72d7e4884] ['Traceback (most recent call last):\n', ' File C:\\dev\\openstack\\cinder\\cinder\\openstack\\common\\rpc\\amqp.py, line 430, in _process_data\nrval = self.proxy.dispatch(ctxt, version, method, **args)\n', ' File C:\\dev\\openstack\\cinder\\cinder\\openstack\\common\\rpc\\dispatcher.py, line 133, in dispatch\nreturn getattr(proxyobj, method)(ctxt, **kwargs)\n', ' File C:\\dev\\openstack\\cinder\\cinder\\volume\\manager.py, line 536, in attach_volume\nreturn do_attach()\n', ' File C:\\dev\\openstack\\cinder\\cinder\\openstack\\common\\lockutils.py, line 214, in inner\nwith lock:\n', ' File C:\\dev\\openstack\\cinder\\cinder\\openstack\\common\\lockutils.py, line 82, in __enter__\nself.trylock()\n', ' File C:\\dev\\openstack\\cinder\\cinder\\openstack\\common\\lockutils.py, line 109, in trylock\nmsvcrt.locking(self.lockfile, msvcrt.LK_NBLCK, 1)\n', 'TypeError: an integer is required\n'] 2013-03-11 21:43:32.229 ERROR cinder.openstack.common.rpc.amqp [req-c4c420ae-df17-4009-aae3-bc6a7e9729b4 4353ebfbc4764cd1882c0f336f73ae72 be2150f90f034291b2bbfcd72d7e4884] Exception during message handling 2013-03-11 21:43:32.229 236 TRACE cinder.openstack.common.rpc.amqp Traceback (most recent call last): 2013-03-11 21:43:32.229 236 TRACE cinder.openstack.common.rpc.amqp File C:\dev\openstack\cinder\cinder\openstack\common\rpc\amqp.py, line 430, in _process_data 2013-03-11 21:43:32.229 236 TRACE cinder.openstack.common.rpc.amqp rval = self.proxy.dispatch(ctxt, version, method, **args) 2013-03-11 21:43:32.229 236 TRACE cinder.openstack.common.rpc.amqp File C:\dev\openstack\cinder\cinder\openstack\common\rpc\dispatcher.py, line 133, in dispatch 2013-03-11 21:43:32.229 236 TRACE cinder.openstack.common.rpc.amqp return getattr(proxyobj, method)(ctxt, **kwargs) 2013-03-11 21:43:32.229 236 TRACE cinder.openstack.common.rpc.amqp File C:\dev\openstack\cinder\cinder\volume\manager.py, line 536, in attach_volume 2013-03-11 21:43:32.229 236 TRACE cinder.openstack.common.rpc.amqp return do_attach() 2013-03-11 21:43:32.229 236 TRACE cinder.openstack.common.rpc.amqp File C:\dev\openstack\cinder\cinder\openstack\common\lockutils.py, line 214, in inner 2013-03-11 21:43:32.229 236 TRACE cinder.openstack.common.rpc.amqp with lock: 2013-03-11 21:43:32.229 236 TRACE cinder.openstack.common.rpc.amqp File C:\dev\openstack\cinder\cinder\openstack\common\lockutils.py, line 82, in __enter__ 2013-03-11 21:43:32.229 236 TRACE cinder.openstack.common.rpc.amqp self.trylock() 2013-03-11 21:43:32.229 236 TRACE cinder.openstack.common.rpc.amqp File C:\dev\openstack\cinder\cinder\openstack\common\lockutils.py, line 109, in trylock 2013-03-11 21:43:32.229 236 TRACE cinder.openstack.common.rpc.amqp msvcrt.locking(self.lockfile, msvcrt.LK_NBLCK, 1) 2013-03-11 21:43:32.229 236 TRACE cinder.openstack.common.rpc.amqp TypeError: an integer is required To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1153966/+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 1053540] Re: Hyper-V test_live_migration_with_target_failure unit test is broken
This bug refers to the unit testing infrastructure used before the Grizzly
refactory.
It doesn't apply to the current codebase.
** Changed in: nova
Status: Confirmed = 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/1053540
Title:
Hyper-V test_live_migration_with_target_failure unit test is broken
Status in OpenStack Compute (Nova):
Invalid
Bug description:
I've been going through the unit tests and auditing uses of 'except
Exception' to see if they are buggy since they are often too liberal
with the exceptions they catch and hide real bugs.
The test_live_migration_with_target_failure unit test is obfuscating
either a real bug or a testing bug.
Removing the try/except block ends up with this confusing set of
exceptions:
==
ERROR: test_live_migration_with_target_failure
(nova.tests.test_hypervapi.HyperVAPITestCase)
--
Traceback (most recent call last):
File /home/johannes/openstack/nova/trunk/nova/tests/test_hypervapi.py,
line 299, in test_live_migration_with_target_failure
self._live_migration(dest_server)
File /home/johannes/openstack/nova/trunk/nova/tests/test_hypervapi.py,
line 321, in _live_migration
dest_server, fake_post_method, fake_recover_method)
File /home/johannes/openstack/nova/trunk/nova/virt/hyperv/driver.py, line
166, in live_migration
post_method, recover_method, block_migration)
File
/home/johannes/openstack/nova/trunk/nova/virt/hyperv/livemigrationops.py,
line 131, in live_migration
recover_method(context, instance_ref, dest, block_migration)
File /usr/lib/python2.6/contextlib.py, line 23, in __exit__
self.gen.next()
File
/home/johannes/openstack/nova/trunk/nova/virt/hyperv/livemigrationops.py,
line 97, in live_migration
moniker='//' + dest + '/root/virtualization/v2')
File /home/johannes/openstack/nova/trunk/nova/tests/hyperv/mockproxy.py,
line 88, in newfunc
return self._get_next_ret_value(name, params)
File /home/johannes/openstack/nova/trunk/nova/tests/hyperv/mockproxy.py,
line 72, in _get_next_ret_value
return self._values[name][params][c]
KeyError: '\'(\\\'(\\\'()\\\', {\\\'moniker\\\':
\\\'//nonexistingserver/root/virtualization/v2\\\'})\\\',
\\\'{}\\\')\'\n begin captured logging
\nnova.virt.hyperv.vmops: INFO: Created disk for
openstack_unit_test_vm_f2e6c57f-64d1-4a6c-823f-276a8bdcc16d\nnova.virt.hyperv.vmops:
INFO: Created nic for
openstack_unit_test_vm_f2e6c57f-64d1-4a6c-823f-276a8bdcc16d
\nnova.virt.hyperv.vmops: INFO: Successfully changed vm state of
openstack_unit_test_vm_f2e6c57f-64d1-4a6c-823f-276a8bdcc16d to
Enabled\nnova.virt.hyperv.vmops: INFO: Started VM
openstack_unit_test_vm_f2e6c57f-64d1-4a6c-823f-276a8bdcc16d
\n- end captured logging -'
==
ERROR: test_live_migration_with_target_failure
(nova.tests.test_hypervapi.HyperVAPITestCase)
--
Traceback (most recent call last):
File /home/johannes/openstack/nova/trunk/nova/tests/test_hypervapi.py,
line 139, in tearDown
self._hypervutils.remove_vm(self._instance_data[name])
File
/home/johannes/openstack/nova/trunk/nova/tests/hyperv/hypervutils.py, line
176, in remove_vm
self._remove_vm(vm_name, self._conn, self._conn_cimv2)
File
/home/johannes/openstack/nova/trunk/nova/tests/hyperv/hypervutils.py, line
179, in _remove_vm
vm = self._get_vm(vm_name, conn)
File
/home/johannes/openstack/nova/trunk/nova/tests/hyperv/hypervutils.py, line
96, in _get_vm
return vml[0]
File /home/johannes/openstack/nova/trunk/nova/tests/hyperv/mockproxy.py,
line 103, in __getitem__
return self._get_next_ret_value('__getitem__', str(key))
File /home/johannes/openstack/nova/trunk/nova/tests/hyperv/mockproxy.py,
line 72, in _get_next_ret_value
return self._values[name][params][c]
KeyError: '__getitem__'\n begin captured logging
\nnova.virt.hyperv.vmops: INFO: Created disk for
openstack_unit_test_vm_f2e6c57f-64d1-4a6c-823f-276a8bdcc16d\nnova.virt.hyperv.vmops:
INFO: Created nic for
openstack_unit_test_vm_f2e6c57f-64d1-4a6c-823f-276a8bdcc16d
\nnova.virt.hyperv.vmops: INFO: Successfully changed vm state of
openstack_unit_test_vm_f2e6c57f-64d1-4a6c-823f-276a8bdcc16d to
Enabled\nnova.virt.hyperv.vmops: INFO: Started VM
openstack_unit_test_vm_f2e6c57f-64d1-4a6c-823f-276a8bdcc16d
\n- end captured logging -
The 'except Exception' was
