[Yahoo-eng-team] [Bug 1432373] [NEW] Horizon: port create missing options
Public bug reported:
nova-manage version: 2015.1
In Horizon, port create is missing options compared to CLI:
--tenant-id
--mac-address
--fixed-ip
--security-group
--no-security-groups
--extra-dhcp-opt
*
ubuntu@trusty1:~/devstack$ neutron help port-create
usage: neutron port-create [-h] [-f {html,json,shell,table,value,yaml}]
[-c COLUMN] [--max-width integer]
[--prefix PREFIX] [--request-format {json,xml}]
[--tenant-id TENANT_ID] [--name NAME]
[--admin-state-down] [--mac-address MAC_ADDRESS]
[--device-id DEVICE_ID]
[--fixed-ip subnet_id=SUBNET,ip_address=IP_ADDR]
[--security-group SECURITY_GROUP |
--no-security-groups]
[--extra-dhcp-opt EXTRA_DHCP_OPTS]
NETWORK
Create a port for a given tenant.
positional arguments:
NETWORK Network ID or name this port belongs to.
optional arguments:
-h, --helpshow this help message and exit
--request-format {json,xml}
The XML or JSON request format.
--tenant-id TENANT_ID
The owner tenant ID.
--name NAME Name of this port.
--admin-state-downSet admin state up to false.
--mac-address MAC_ADDRESS
MAC address of this port.
--device-id DEVICE_ID
Device ID of this port.
--fixed-ip subnet_id=SUBNET,ip_address=IP_ADDR
Desired IP and/or subnet for this port:
subnet_id=name_or_id,ip_address=ip.You can repeat
this option.
--security-group SECURITY_GROUP
Security group associated with the port. You can
repeat this option.
--no-security-groups Associate no security groups with the port.
--extra-dhcp-opt EXTRA_DHCP_OPTS
Extra dhcp options to be assigned to this port:
opt_name=dhcp_option_name,opt_value=value. You can
repeat this option.
*
Steps to repro:
1. Log in Horizon as admin.
2. At left panel, Admin-System-Networks.
3. Select a network by clicking on the Network Name.
4. Ports-Create Port
** Affects: horizon
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1432373
Title:
Horizon: port create missing options
Status in OpenStack Dashboard (Horizon):
New
Bug description:
nova-manage version: 2015.1
In Horizon, port create is missing options compared to CLI:
--tenant-id
--mac-address
--fixed-ip
--security-group
--no-security-groups
--extra-dhcp-opt
*
ubuntu@trusty1:~/devstack$ neutron help port-create
usage: neutron port-create [-h] [-f {html,json,shell,table,value,yaml}]
[-c COLUMN] [--max-width integer]
[--prefix PREFIX] [--request-format {json,xml}]
[--tenant-id TENANT_ID] [--name NAME]
[--admin-state-down] [--mac-address MAC_ADDRESS]
[--device-id DEVICE_ID]
[--fixed-ip subnet_id=SUBNET,ip_address=IP_ADDR]
[--security-group SECURITY_GROUP |
--no-security-groups]
[--extra-dhcp-opt EXTRA_DHCP_OPTS]
NETWORK
Create a port for a given tenant.
positional arguments:
NETWORK Network ID or name this port belongs to.
optional arguments:
-h, --helpshow this help message and exit
--request-format {json,xml}
The XML or JSON request format.
--tenant-id TENANT_ID
The owner tenant ID.
--name NAME Name of this port.
--admin-state-downSet admin state up to false.
--mac-address MAC_ADDRESS
MAC address of this port.
--device-id DEVICE_ID
Device ID of this port.
--fixed-ip subnet_id=SUBNET,ip_address=IP_ADDR
Desired IP and/or subnet for this port:
subnet_id=name_or_id,ip_address=ip.You can repeat
this option.
--security-group SECURITY_GROUP
Security group associated with the port. You can
repeat this option.
--no-security-groups Associate no security
[Yahoo-eng-team] [Bug 1430405] Re: Nova volume-delete does not accept display name as input to remove volume
Thanks for your remind.
** Changed in: nova
Assignee: ugvddm (271025598-9) = (unassigned)
** 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/1430405
Title:
Nova volume-delete does not accept display name as input to remove
volume
Status in OpenStack Compute (Nova):
Invalid
Bug description:
Issue: can not use the display name to delete a volume through the
nova volume-delete {display name}.
± nova volume-list
++--+--+---+-+---+
| ID
| Status | Display Name | Size | Volume Type | Attached to |
++--+-+-++---+
| dcc3c310-4187-49d7-b78e-3690b38bddb8 | available | test3a | 1
| dot3a | |
++--+-+-++---+
± nova volume-delete test3a
Delete for volume test3a failed: No volume with a name or ID of 'test3a'
exists.
± nova volume-delete dcc3c310-4187-49d7-b78e-3690b38bddb8
± nova volume-list
++--+-+--+-+---+
| ID | Status | Display Name | Size | Volume Type | Attached to |
++--+-+--+-+---+
++--+-+--+-+---+
Version; Kilo/trunk
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1430405/+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 1432401] [NEW] New Launch instance wizard should not display networks when neutron is not enabled.
Public bug reported: New Launch instance wizard should not display networks when neutron is not enabled. See: https://review.openstack.org/#/c/164359/ ** Affects: horizon Importance: Undecided Assignee: Travis Tripp (travis-tripp) Status: In Progress ** Changed in: horizon Status: New = In Progress ** Changed in: horizon Assignee: (unassigned) = Travis Tripp (travis-tripp) -- 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/1432401 Title: New Launch instance wizard should not display networks when neutron is not enabled. Status in OpenStack Dashboard (Horizon): In Progress Bug description: New Launch instance wizard should not display networks when neutron is not enabled. See: https://review.openstack.org/#/c/164359/ To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1432401/+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 1432393] [NEW] Neutron: port-create missing help info for the option: --binding
Public bug reported:
nova-manage version: 2015.1
Issue: Neutron port-create missing help info for the option: --binding:vnic-type
Valid inputs are 'normal', 'direct' and 'macvtap'.
ubuntu@trusty1:~/devstack$ neutron port-create --name sriov-mactap
--binding:vnic-type=mactap private
Invalid input for binding:vnic_type. Reason: 'mactap' is not in ['normal',
'direct', 'macvtap'].
ubuntu@trusty1:~/devstack$ neutron help port-create
usage: neutron port-create [-h] [-f {html,json,shell,table,value,yaml}]
[-c COLUMN] [--max-width integer]
[--prefix PREFIX] [--request-format {json,xml}]
[--tenant-id TENANT_ID] [--name NAME]
[--admin-state-down] [--mac-address MAC_ADDRESS]
[--device-id DEVICE_ID]
[--fixed-ip subnet_id=SUBNET,ip_address=IP_ADDR]
[--security-group SECURITY_GROUP |
--no-security-groups]
[--extra-dhcp-opt EXTRA_DHCP_OPTS]
NETWORK
** 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/1432393
Title:
Neutron: port-create missing help info for the option: --binding
Status in OpenStack Neutron (virtual network service):
New
Bug description:
nova-manage version: 2015.1
Issue: Neutron port-create missing help info for the option:
--binding:vnic-type
Valid inputs are 'normal', 'direct' and 'macvtap'.
ubuntu@trusty1:~/devstack$ neutron port-create --name sriov-mactap
--binding:vnic-type=mactap private
Invalid input for binding:vnic_type. Reason: 'mactap' is not in ['normal',
'direct', 'macvtap'].
ubuntu@trusty1:~/devstack$ neutron help port-create
usage: neutron port-create [-h] [-f {html,json,shell,table,value,yaml}]
[-c COLUMN] [--max-width integer]
[--prefix PREFIX] [--request-format {json,xml}]
[--tenant-id TENANT_ID] [--name NAME]
[--admin-state-down] [--mac-address MAC_ADDRESS]
[--device-id DEVICE_ID]
[--fixed-ip subnet_id=SUBNET,ip_address=IP_ADDR]
[--security-group SECURITY_GROUP |
--no-security-groups]
[--extra-dhcp-opt EXTRA_DHCP_OPTS]
NETWORK
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1432393/+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 1432441] [NEW] do away with PROTOCOL_SSLv3
Public bug reported: In Debian Testing, Python 2.7 does no longer include the symbols PROTOCOL_SSLv2 and PROTOCOL_SSLv3. The attached patch fixes this against Nova trunk. Unrelated: The following command, run from /opt/stack in a devstack environment, did not yield any call to the function validate_ssl_version(), which is the only user of the affected data structure: find . -name '*.py' -type f |xargs grep -nF validate_ssl_version The nova version, according to the PKG-INFO file, is 2015.1.dev70. ** Affects: nova Importance: Undecided Status: New ** Patch added: disarm old SSL protocol imports, and import new symbols https://bugs.launchpad.net/bugs/1432441/+attachment/4346561/+files/nova.openstack.common.sslutils.py.patch -- 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/1432441 Title: do away with PROTOCOL_SSLv3 Status in OpenStack Compute (Nova): New Bug description: In Debian Testing, Python 2.7 does no longer include the symbols PROTOCOL_SSLv2 and PROTOCOL_SSLv3. The attached patch fixes this against Nova trunk. Unrelated: The following command, run from /opt/stack in a devstack environment, did not yield any call to the function validate_ssl_version(), which is the only user of the affected data structure: find . -name '*.py' -type f |xargs grep -nF validate_ssl_version The nova version, according to the PKG-INFO file, is 2015.1.dev70. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1432441/+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 1432460] [NEW] neutron unit test fails with unexpected keyword retry_on_request
Public bug reported: Now(2015,03,16) all neutron unit test fails, and export the following error. === Failed to import test module: neutron.tests.unit.test_extension_extended_attribute Traceback (most recent call last): File /usr/local/lib/python2.7/dist-packages/unittest2/loader.py, line 445, in _find_test_path module = self._get_module_from_name(name) File /usr/local/lib/python2.7/dist-packages/unittest2/loader.py, line 384, in _get_module_from_name __import__(name) File /home/stack/neutron/neutron/tests/unit/test_extension_extended_attribute.py, line 29, in module from neutron.plugins.ml2 import plugin as ml2_plugin File /home/stack/neutron/neutron/plugins/ml2/plugin.py, line 89, in module extradhcpopt_db.ExtraDhcpOptMixin): File /home/stack/neutron/neutron/plugins/ml2/plugin.py, line 591, in Ml2Plugin retry_on_request=True) TypeError: __init__() got an unexpected keyword argument 'retry_on_request' == This is due to the following fix: https://review.openstack.org/#/c/149261/ In neutron/plugins/ml2/plugin.py Line 602 retry_on_request is added. ** Affects: neutron Importance: Undecided Assignee: watanabe.isao (watanabe.isao) Status: New ** Changed in: neutron Assignee: (unassigned) = watanabe.isao (watanabe.isao) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1432460 Title: neutron unit test fails with unexpected keyword retry_on_request Status in OpenStack Neutron (virtual network service): New Bug description: Now(2015,03,16) all neutron unit test fails, and export the following error. === Failed to import test module: neutron.tests.unit.test_extension_extended_attribute Traceback (most recent call last): File /usr/local/lib/python2.7/dist-packages/unittest2/loader.py, line 445, in _find_test_path module = self._get_module_from_name(name) File /usr/local/lib/python2.7/dist-packages/unittest2/loader.py, line 384, in _get_module_from_name __import__(name) File /home/stack/neutron/neutron/tests/unit/test_extension_extended_attribute.py, line 29, in module from neutron.plugins.ml2 import plugin as ml2_plugin File /home/stack/neutron/neutron/plugins/ml2/plugin.py, line 89, in module extradhcpopt_db.ExtraDhcpOptMixin): File /home/stack/neutron/neutron/plugins/ml2/plugin.py, line 591, in Ml2Plugin retry_on_request=True) TypeError: __init__() got an unexpected keyword argument 'retry_on_request' == This is due to the following fix: https://review.openstack.org/#/c/149261/ In neutron/plugins/ml2/plugin.py Line 602 retry_on_request is added. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1432460/+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 1432455] [NEW] non-admin user can't add new fixed ip to the VM by os-multinic api
Public bug reported: When non-admin user add new nic to the vm by: alex@hp-pc:/opt/stack/nova$ nova --debug add-fixed-ip vm1 12d4bedb-77fb- 44da-b6d6-6c52e7606c02 will get error as below: 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher Traceback (most recent call last): 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py, line 142, in _dispatch_and_reply 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher executor_callback)) 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py, line 186, in _dispatch 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher executor_callback) 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py, line 130, in _do_dispatch 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher result = func(ctxt, **new_args) 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher File /opt/stack/nova/nova/network/manager.py, line 778, in add_fixed_ip_to_instance 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher self._allocate_fixed_ips(context, instance_id, host, [network]) 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher File /opt/stack/nova/nova/network/manager.py, line 194, in _allocate_fixed_ips 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher vpn=vpn, address=address) 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher File /opt/stack/nova/nova/network/manager.py, line 1938, in allocate_fixed_ip 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher address = fip.address 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher File /opt/stack/nova/nova/objects/base.py, line 161, in wrapper 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher args, kwargs) 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher File /opt/stack/nova/nova/conductor/rpcapi.py, line 365, in object_class_action 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher objver=objver, args=args, kwargs=kwargs) 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/client.py, line 156, in call 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher retry=self.retry) 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo_messaging/transport.py, line 90, in _send 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher timeout=timeout, retry=retry) 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py, line 349, in send 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher retry=retry) 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher File /usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py, line 340, in _send 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher raise result 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher AdminRequired_Remote: User does not have admin privileges 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher Traceback (most recent call last): 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher File /opt/stack/nova/nova/conductor/manager.py, line 420, in _object_dispatch 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher Perform a classmethod action on an object. 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher File /opt/stack/nova/nova/objects/base.py, line 163, in wrapper 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher result = fn(cls, context, *args, **kwargs) 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher File /opt/stack/nova/nova/objects/fixed_ip.py, line 160, in associate_pool 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher host=host) 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher File /opt/stack/nova/nova/db/api.py, line 509, in fixed_ip_associate_pool 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher instance_uuid, host) 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher File /opt/stack/nova/nova/db/sqlalchemy/api.py, line 127, in wrapper 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher 2015-03-16 09:23:18.306 TRACE oslo_messaging.rpc.dispatcher File /opt/stack/nova/nova/context.py, line 235, in require_admin_context
[Yahoo-eng-team] [Bug 1432465] [NEW] nova detach interface will get inconsistent if hypervisor failed to detach a port
Public bug reported: Currently, in compute api, detach_interface will delete neutron port first then calls hypervisor driver to do detach_interface on the guest. If the driver does detach_interface failed, in case of the driver raise an exception.InterfaceDetachFailed or other NovaExcptions, there is no handler for them. Besides this is an asyn rpc call, so nova-api will not notice this exception. End user will find the port has been deleted in neutron side, but guest still can see this port on guest, this is inconsistent. ** Affects: nova Importance: Undecided Assignee: Eli Qiao (taget-9) Status: In Progress ** Changed in: nova Assignee: (unassigned) = Eli Qiao (taget-9) -- 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/1432465 Title: nova detach interface will get inconsistent if hypervisor failed to detach a port Status in OpenStack Compute (Nova): In Progress Bug description: Currently, in compute api, detach_interface will delete neutron port first then calls hypervisor driver to do detach_interface on the guest. If the driver does detach_interface failed, in case of the driver raise an exception.InterfaceDetachFailed or other NovaExcptions, there is no handler for them. Besides this is an asyn rpc call, so nova-api will not notice this exception. End user will find the port has been deleted in neutron side, but guest still can see this port on guest, this is inconsistent. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1432465/+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 1391806] Re: 'neutron port-list' is missing binding:vnic_type filter
** Changed in: neutron Assignee: Numan Siddique (numansiddique) = (unassigned) ** Changed in: neutron Status: In Progress = Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1391806 Title: 'neutron port-list' is missing binding:vnic_type filter Status in OpenStack Neutron (virtual network service): Opinion Bug description: An example usage would be to filter the ports that have binding:vnic_type=direct # neutron port-list --binding:vnic_type=direct To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1391806/+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 1391806] Re: 'neutron port-list' is missing binding:vnic_type filter
** Changed in: neutron Status: Opinion = Invalid ** Changed in: neutron Status: Invalid = 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/1391806 Title: 'neutron port-list' is missing binding:vnic_type filter Status in OpenStack Neutron (virtual network service): New Bug description: An example usage would be to filter the ports that have binding:vnic_type=direct # neutron port-list --binding:vnic_type=direct To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1391806/+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 1432490] [NEW] TestEncryptedCinderVolumes cryptsetup name is too long
Public bug reported:
When running Datera storage with Cinder and the following
TestEncryptedCinderVolumes tests:
{0}
tempest.scenario.test_encrypted_cinder_volumes.TestEncryptedCinderVolumes.test_encrypted_cinder_volumes_cryptsetup
{0}
tempest.scenario.test_encrypted_cinder_volumes.TestEncryptedCinderVolumes.test_encrypted_cinder_volumes_luks
cryptsetup complains about the name being too long:
http://paste.openstack.org/show/192537
Nova uses the device name that's in /dev/disk-by-path, which in this
case is the returned iqn from the backend:
ip-172.30.128.2:3260-iscsi-iqn.2013-05.com.daterainc:OpenStack-
TestEncryptedCinderVolumes-676292884:01:sn:aef6a6f1cd84768f-lun-0
Already started talking Matt Treinish about this on IRC last week.
Unsure where the fix should actual go into. While I understand this is
not reproducible with the reference implementation LVM, this seems like
a unknown limitation today since we're not enforcing any length on the
IQN or recommending anything.
** Affects: cinder
Importance: Undecided
Status: New
** Affects: nova
Importance: Undecided
Status: New
** Affects: tempest
Importance: Undecided
Status: New
** Also affects: cinder
Importance: Undecided
Status: New
** Also affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1432490
Title:
TestEncryptedCinderVolumes cryptsetup name is too long
Status in Cinder:
New
Status in OpenStack Compute (Nova):
New
Status in Tempest:
New
Bug description:
When running Datera storage with Cinder and the following
TestEncryptedCinderVolumes tests:
{0}
tempest.scenario.test_encrypted_cinder_volumes.TestEncryptedCinderVolumes.test_encrypted_cinder_volumes_cryptsetup
{0}
tempest.scenario.test_encrypted_cinder_volumes.TestEncryptedCinderVolumes.test_encrypted_cinder_volumes_luks
cryptsetup complains about the name being too long:
http://paste.openstack.org/show/192537
Nova uses the device name that's in /dev/disk-by-path, which in this
case is the returned iqn from the backend:
ip-172.30.128.2:3260-iscsi-iqn.2013-05.com.daterainc:OpenStack-
TestEncryptedCinderVolumes-676292884:01:sn:aef6a6f1cd84768f-lun-0
Already started talking Matt Treinish about this on IRC last week.
Unsure where the fix should actual go into. While I understand this is
not reproducible with the reference implementation LVM, this seems
like a unknown limitation today since we're not enforcing any length
on the IQN or recommending anything.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1432490/+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 1412930] Re: CPU feature request is not respected when create VM
from Daniel P.Berrange(berra...@redhat.com)
If you set 'cpu_mode=host-model' or 'cpu_mode=host-passthrough'
then it will take effect, as the guest will see the full CPU model
of the host that is picked. IMHO the capabilities:cpu_info:features
filter only makes sense when using those two cpu modes. If you
left the default cpu_mode=None or set cpu_mode=custom, then this
capabilities feature is meaningless from a conceptual POV. So the
fact that it has no effect on the guest CPU is not a bug it is
by design.
---
so this is not a bug it is by design. I will close it...
** 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/1412930
Title:
CPU feature request is not respected when create VM
Status in OpenStack Compute (Nova):
Invalid
Bug description:
When creating a VM requiring some specific CPU features, although the
guest will be scheduled to a host with the capability, but such
information is not always exposed to guest.
a) started devstack by default, (means nova configuration
libvirt.cpu_mode=none), the compute node has the SSE4.1 support
b) create flavor with {capabilities:cpu_info:features: in
sse4.1} extra spec, i.e. requiring SSE4.1.
c) launch an instance with the flavor.
d) ssh to instance and 'cat /proc/cpuinfo'.
The SSE4.1 is not presented in guest.
I think the reason is because when libvirt.cpu_mode is none, libvirt
will not specify the feature request in the guest vcpu config.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1412930/+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 1432460] Re: neutron unit test fails with unexpected keyword retry_on_request
sudo pip install oslo.db --upgrade After the above upgrade, oslo_db/api.py will be updated to the upstream. And the bug is no longer happened. ** 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/1432460 Title: neutron unit test fails with unexpected keyword retry_on_request Status in OpenStack Neutron (virtual network service): Invalid Bug description: Now(2015,03,16) all neutron unit test fails, and export the following error. === Failed to import test module: neutron.tests.unit.test_extension_extended_attribute Traceback (most recent call last): File /usr/local/lib/python2.7/dist-packages/unittest2/loader.py, line 445, in _find_test_path module = self._get_module_from_name(name) File /usr/local/lib/python2.7/dist-packages/unittest2/loader.py, line 384, in _get_module_from_name __import__(name) File /home/stack/neutron/neutron/tests/unit/test_extension_extended_attribute.py, line 29, in module from neutron.plugins.ml2 import plugin as ml2_plugin File /home/stack/neutron/neutron/plugins/ml2/plugin.py, line 89, in module extradhcpopt_db.ExtraDhcpOptMixin): File /home/stack/neutron/neutron/plugins/ml2/plugin.py, line 591, in Ml2Plugin retry_on_request=True) TypeError: __init__() got an unexpected keyword argument 'retry_on_request' == This is due to the following fix: https://review.openstack.org/#/c/149261/ In neutron/plugins/ml2/plugin.py Line 602 retry_on_request is added. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1432460/+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
