[Yahoo-eng-team] [Bug 1781368] Re: KeyError: 'flavor' when nova boot
** Changed in: nova
Assignee: zhaolihui (zhaolh) => (unassigned)
** No longer affects: nova
--
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/1781368
Title:
KeyError: 'flavor' when nova boot
Status in python-novaclient:
In Progress
Bug description:
It maybe occur KeyError flavor when nova boot vm
# nova --debug boot vm --image image-id --flavor flavor-id --nic net-
id=id
It will show vm's information, but it return Error like that:
DEBUG (session:419) RESP: [202] Content-Length: 462 Location:
controller:8774/v2.1/7fcede66893a4d179f3d37958a06d801/servers/c095438d-7a8a-4b00-a53d-882a1f988748
Content-Type: application/json Openstack-Api-Version: compute 2.60
X-Openstack-Nova-Api-Version: 2.60 Vary: OpenStack-API-Version,
X-OpenStack-Nova-API-Version X-Openstack-Request-Id:
req-07b4cdd4-2a22-4791-a6b1-7ea4b7628370 X-Compute-Request-Id:
req-07b4cdd4-2a22-4791-a6b1-7ea4b7628370 Date: Thu, 12 Jul 2018 06:34:49 GMT
RESP BODY: {"server": {"security_groups": [{"name": "default"}],
"OS-DCF:diskConfig": "MANUAL", "id": "c095438d-7a8a-4b00-a53d-882a1f988748",
"links": [{"href":
"controller:8774/v2.1/7fcede66893a4d179f3d37958a06d801/servers/c095438d-7a8a-4b00-a53d-882a1f988748",
"rel": "self"}, {"href":
"controller:8774/7fcede66893a4d179f3d37958a06d801/servers/c095438d-7a8a-4b00-a53d-882a1f988748",
"rel": "bookmark"}], "adminPass": "2oHes4hprNs8"}}
DEBUG (session:722) POST call to compute for
controller:8774/v2.1/7fcede66893a4d179f3d37958a06d801/servers used request id
req-07b4cdd4-2a22-4791-a6b1-7ea4b7628370
DEBUG (session:372) REQ: curl -g -i -X GET
controller:8774/v2.1/7fcede66893a4d179f3d37958a06d801/servers/c095438d-7a8a-4b00-a53d-882a1f988748
-H "OpenStack-API-Version: compute 2.60" -H "User-Agent: python-novaclient" -H
"Accept: application/json" -H "X-OpenStack-Nova-API-Version: 2.60" -H
"X-Auth-Token: {SHA1}4dc236317ec12f176dd4e844738ec85cee5c12df"
DEBUG (connectionpool:395) controller:8774 "GET
/v2.1/7fcede66893a4d179f3d37958a06d801/servers/c095438d-7a8a-4b00-a53d-882a1f988748
HTTP/1.1" 404 111
DEBUG (session:419) RESP: [404] Openstack-Api-Version: compute 2.60
X-Openstack-Nova-Api-Version: 2.60 Vary: OpenStack-API-Version,
X-OpenStack-Nova-API-Version Content-Type: application/json; charset=UTF-8
Content-Length: 111 X-Openstack-Request-Id:
req-10da61f5-3624-4b56-8c7b-849eb163b0fc X-Compute-Request-Id:
req-10da61f5-3624-4b56-8c7b-849eb163b0fc Date: Thu, 12 Jul 2018 06:34:49 GMT
RESP BODY: {"itemNotFound": {"message": "Instance
c095438d-7a8a-4b00-a53d-882a1f988748 could not be found.", "code": 404}}
DEBUG (session:722) GET call to compute for
controller:8774/v2.1/7fcede66893a4d179f3d37958a06d801/servers/c095438d-7a8a-4b00-a53d-882a1f988748
used request id req-10da61f5-3624-4b56-8c7b-849eb163b0fc
DEBUG (shell:793) 'flavor'
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/novaclient/shell.py", line 791, in
main
OpenStackComputeShell().main(argv)
File "/usr/lib/python2.7/site-packages/novaclient/shell.py", line 713, in
main
args.func(self.cs, args)
File "/usr/lib/python2.7/site-packages/novaclient/v2/shell.py", line 889,
in do_boot
_print_server(cs, args, server)
File "/usr/lib/python2.7/site-packages/novaclient/v2/shell.py", line 2240,
in _print_server
del info['flavor']
KeyError: 'flavor'
ERROR (KeyError): 'flavor'
Environment
===
openstack-nova-common-17.0.5-1.el7.noarch
python-nova-17.0.5-1.el7.noarch
openstack-nova-compute-17.0.5-1.el7.noarch
python2-novaclient-10.1.0-1.el7.noarch
To manage notifications about this bug go to:
https://bugs.launchpad.net/python-novaclient/+bug/1781368/+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 1781368] [NEW] KeyError: 'flavor' when nova boot
Public bug reported:
It maybe occur KeyError flavor when nova boot vm
# nova --debug boot vm --image image-id --flavor flavor-id --nic net-
id=id
It will show vm's information, but it return Error like that:
DEBUG (session:419) RESP: [202] Content-Length: 462 Location:
controller:8774/v2.1/7fcede66893a4d179f3d37958a06d801/servers/c095438d-7a8a-4b00-a53d-882a1f988748
Content-Type: application/json Openstack-Api-Version: compute 2.60
X-Openstack-Nova-Api-Version: 2.60 Vary: OpenStack-API-Version,
X-OpenStack-Nova-API-Version X-Openstack-Request-Id:
req-07b4cdd4-2a22-4791-a6b1-7ea4b7628370 X-Compute-Request-Id:
req-07b4cdd4-2a22-4791-a6b1-7ea4b7628370 Date: Thu, 12 Jul 2018 06:34:49 GMT
RESP BODY: {"server": {"security_groups": [{"name": "default"}],
"OS-DCF:diskConfig": "MANUAL", "id": "c095438d-7a8a-4b00-a53d-882a1f988748",
"links": [{"href":
"controller:8774/v2.1/7fcede66893a4d179f3d37958a06d801/servers/c095438d-7a8a-4b00-a53d-882a1f988748",
"rel": "self"}, {"href":
"controller:8774/7fcede66893a4d179f3d37958a06d801/servers/c095438d-7a8a-4b00-a53d-882a1f988748",
"rel": "bookmark"}], "adminPass": "2oHes4hprNs8"}}
DEBUG (session:722) POST call to compute for
controller:8774/v2.1/7fcede66893a4d179f3d37958a06d801/servers used request id
req-07b4cdd4-2a22-4791-a6b1-7ea4b7628370
DEBUG (session:372) REQ: curl -g -i -X GET
controller:8774/v2.1/7fcede66893a4d179f3d37958a06d801/servers/c095438d-7a8a-4b00-a53d-882a1f988748
-H "OpenStack-API-Version: compute 2.60" -H "User-Agent: python-novaclient" -H
"Accept: application/json" -H "X-OpenStack-Nova-API-Version: 2.60" -H
"X-Auth-Token: {SHA1}4dc236317ec12f176dd4e844738ec85cee5c12df"
DEBUG (connectionpool:395) controller:8774 "GET
/v2.1/7fcede66893a4d179f3d37958a06d801/servers/c095438d-7a8a-4b00-a53d-882a1f988748
HTTP/1.1" 404 111
DEBUG (session:419) RESP: [404] Openstack-Api-Version: compute 2.60
X-Openstack-Nova-Api-Version: 2.60 Vary: OpenStack-API-Version,
X-OpenStack-Nova-API-Version Content-Type: application/json; charset=UTF-8
Content-Length: 111 X-Openstack-Request-Id:
req-10da61f5-3624-4b56-8c7b-849eb163b0fc X-Compute-Request-Id:
req-10da61f5-3624-4b56-8c7b-849eb163b0fc Date: Thu, 12 Jul 2018 06:34:49 GMT
RESP BODY: {"itemNotFound": {"message": "Instance
c095438d-7a8a-4b00-a53d-882a1f988748 could not be found.", "code": 404}}
DEBUG (session:722) GET call to compute for
controller:8774/v2.1/7fcede66893a4d179f3d37958a06d801/servers/c095438d-7a8a-4b00-a53d-882a1f988748
used request id req-10da61f5-3624-4b56-8c7b-849eb163b0fc
DEBUG (shell:793) 'flavor'
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/novaclient/shell.py", line 791, in main
OpenStackComputeShell().main(argv)
File "/usr/lib/python2.7/site-packages/novaclient/shell.py", line 713, in main
args.func(self.cs, args)
File "/usr/lib/python2.7/site-packages/novaclient/v2/shell.py", line 889, in
do_boot
_print_server(cs, args, server)
File "/usr/lib/python2.7/site-packages/novaclient/v2/shell.py", line 2240, in
_print_server
del info['flavor']
KeyError: 'flavor'
ERROR (KeyError): 'flavor'
Environment
===
openstack-nova-common-17.0.5-1.el7.noarch
python-nova-17.0.5-1.el7.noarch
openstack-nova-compute-17.0.5-1.el7.noarch
python2-novaclient-10.1.0-1.el7.noarch
** Affects: nova
Importance: Undecided
Assignee: zhaolihui (zhaolh)
Status: New
** Changed in: nova
Assignee: (unassigned) => zhaolihui (zhaolh)
--
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/1781368
Title:
KeyError: 'flavor' when nova boot
Status in OpenStack Compute (nova):
New
Bug description:
It maybe occur KeyError flavor when nova boot vm
# nova --debug boot vm --image image-id --flavor flavor-id --nic net-
id=id
It will show vm's information, but it return Error like that:
DEBUG (session:419) RESP: [202] Content-Length: 462 Location:
controller:8774/v2.1/7fcede66893a4d179f3d37958a06d801/servers/c095438d-7a8a-4b00-a53d-882a1f988748
Content-Type: application/json Openstack-Api-Version: compute 2.60
X-Openstack-Nova-Api-Version: 2.60 Vary: OpenStack-API-Version,
X-OpenStack-Nova-API-Version X-Openstack-Request-Id:
req-07b4cdd4-2a22-4791-a6b1-7ea4b7628370 X-Compute-Request-Id:
req-07b4cdd4-2a22-4791-a6b1-7ea4b7628370 Date: Thu, 12 Jul 2018 06:34:49 GMT
RESP BODY: {"server": {"security_groups": [{"name": "default"}],
"OS-DCF:diskConfig": "MANUAL", "id": "
[Yahoo-eng-team] [Bug 1644457] [NEW] keypair quota error
Public bug reported: Description === The nova quota-show was error in key_pairs when add keypair. Steps to reproduce == 1.nova keypair-add k_001 2.nova keypair-list 3.nova quota-show --detail Expected result === It is correct with key_pairs in_use. Actual result = Follow command "nova keypair-add k_001", keypair-list display k_001, and "nova quota-show --detail" was correct with keypair in_use value. Environment === 1. Devstack with newton version ** Affects: nova Importance: Undecided Assignee: zhaolihui (zhaolh) 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/1644457 Title: keypair quota error Status in OpenStack Compute (nova): New Bug description: Description === The nova quota-show was error in key_pairs when add keypair. Steps to reproduce == 1.nova keypair-add k_001 2.nova keypair-list 3.nova quota-show --detail Expected result === It is correct with key_pairs in_use. Actual result = Follow command "nova keypair-add k_001", keypair-list display k_001, and "nova quota-show --detail" was correct with keypair in_use value. Environment === 1. Devstack with newton version To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1644457/+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 1643793] Re: Display incorrect flavor name in instance property after edit flavor
It affects not only horizon but also nova ** Also affects: nova Importance: Undecided Status: New ** Changed in: nova Assignee: (unassigned) => zhaolihui (zhaolh) ** Changed in: horizon Assignee: zhaolihui (zhaolh) => (unassigned) -- 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/1643793 Title: Display incorrect flavor name in instance property after edit flavor Status in OpenStack Dashboard (Horizon): New Status in OpenStack Compute (nova): New Bug description: Description === Display incorrect flavor name in instance property after edit flavor Steps to reproduce == All of the below steps are on the web page. 1.create a new flavor name is AAA 2.create vm with AAA flavor 3.check vm info that flavor name is AAA 4.edit the flavor, change flavor name AAA to BBB 5.check vm info again, the flavor name is not BBB Expected result === Display correct flavor name after edit flavor name. Actual result = The vm flavor name is not correct after edit flavor name. By the nova-api.log file, the edit flavor operation is that first to delete the origin flavor, second to create a new flavor. But vm flavor'id was original id, not the new id. Environment === 1. Devstack with newton version To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1643793/+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 1643793] [NEW] Display incorrect flavor name in instance property after edit flavor
Public bug reported: Description === Display incorrect flavor name in instance property after edit flavor Steps to reproduce == All of the below steps are on the web page. 1.create a new flavor name is AAA 2.create vm with AAA flavor 3.check vm info that flavor name is AAA 4.edit the flavor, change flavor name AAA to BBB 5.check vm info again, the flavor name is not BBB Expected result === Display correct flavor name after edit flavor name. Actual result = The vm flavor name is not correct after edit flavor name. By the nova-api.log file, the edit flavor operation is that first to delete the origin flavor, second to create a new flavor. But vm flavor'id was original id, not the new id. Environment === 1. Devstack with newton version ** Affects: nova Importance: Undecided Assignee: zhaolihui (zhaolh) Status: New ** Changed in: nova Assignee: (unassigned) => zhaolihui (zhaolh) -- 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/1643793 Title: Display incorrect flavor name in instance property after edit flavor Status in OpenStack Compute (nova): New Bug description: Description === Display incorrect flavor name in instance property after edit flavor Steps to reproduce == All of the below steps are on the web page. 1.create a new flavor name is AAA 2.create vm with AAA flavor 3.check vm info that flavor name is AAA 4.edit the flavor, change flavor name AAA to BBB 5.check vm info again, the flavor name is not BBB Expected result === Display correct flavor name after edit flavor name. Actual result = The vm flavor name is not correct after edit flavor name. By the nova-api.log file, the edit flavor operation is that first to delete the origin flavor, second to create a new flavor. But vm flavor'id was original id, not the new id. Environment === 1. Devstack with newton version To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1643793/+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 1640415] [NEW] rebuild vm not with the specified image
Public bug reported: Description === rebuild vm not with the specified image Steps to reproduce == 1.create volume with image cinder create --image cirros --name vol_image 1 follow command as above, the vol_image id is 469b36df-c8fe-40fc-aa6c-e973c27f2294 2.create vm from vol_image nova boot vm_name --boot-volume 469b36df-c8fe-40fc-aa6c-e973c27f2294 --flavor xx --nic net-name=xx login the vm and create some files. 3.rebuild vm with specified image nova rebuild vm_name new_image_id Expected result === There will be a vm with new image Actual result = The vm is still original vm, the image not changed,and the files are still there Environment === 1. Devstack with newton version ** Affects: nova Importance: Undecided Assignee: zhaolihui (zhaolh) Status: New ** Changed in: nova Assignee: (unassigned) => zhaolihui (zhaolh) -- 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/1640415 Title: rebuild vm not with the specified image Status in OpenStack Compute (nova): New Bug description: Description === rebuild vm not with the specified image Steps to reproduce == 1.create volume with image cinder create --image cirros --name vol_image 1 follow command as above, the vol_image id is 469b36df-c8fe-40fc-aa6c-e973c27f2294 2.create vm from vol_image nova boot vm_name --boot-volume 469b36df-c8fe-40fc-aa6c-e973c27f2294 --flavor xx --nic net-name=xx login the vm and create some files. 3.rebuild vm with specified image nova rebuild vm_name new_image_id Expected result === There will be a vm with new image Actual result = The vm is still original vm, the image not changed,and the files are still there Environment === 1. Devstack with newton version To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1640415/+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 1638200] [NEW] Failed to boot vm with pci_alias's name including space in nova.conf
[^[[01;36mreq-82f58a79-76b9-49e7-a8e9-44e8b43eaea4 ^[[00;36madmin
admin^[[00;36m] ^[[01;35m^[[00;36mHTTP exception thrown: Unexpected API Error.
Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API
log if possible.^[[00m
** Affects: nova
Importance: Undecided
Assignee: zhaolihui (zhaolh)
Status: New
** Changed in: nova
Assignee: (unassigned) => zhaolihui (zhaolh)
--
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/1638200
Title:
Failed to boot vm with pci_alias's name including space in nova.conf
Status in OpenStack Compute (nova):
New
Bug description:
Description
===
Failed to boot vm with pci_alias's name including space in nova.conf.
Steps to reproduce
==
1.modify the key pci_alias, pci_passthrough_whitelist and
scheduler_default_filters in /etc/nova/nova.conf
pci_alias = {"name": "Cirrus Logic", "product_id": "0ff2", "vendor_id":
"10de"}
pci_passthrough_whitelist = [{"product_id": "0ff2", "vendor_id": "10de"}]
scheduler_default_filters = ...,PciPassthroughFilter
2.restart nova-api, nova-scheduler, nova-conductor, nova-compute
serivces
3.update a flavor's metadata with command
nova flavor-key m1.tiny set "pci_passthrough:alias"="Cirrus Logic:1"
4.create instance with command
nova boot --flavor m1.tiny --image cirror --nic net-id=x vm_name
Expected result
===
There will be a vm with gpu passthrough.
Actual result
=
Failed to boot vm.
Error occurs in nova-api.log
Environment
===
1. Devstack with newton version
Logs
==
2016-11-01 12:13:27.523 ^[[01;31mERROR nova.api.openstack.extensions
[^[[01;36mreq-82f58a79-76b9-49e7-a8e9-44e8b43eaea4 ^[[00;36madmin
admin^[[01;31m] ^[[01;35m^[[01;31mUnexpected exception in API method^[[00m
^[[01;31m2016-11-01 12:13:27.523 TRACE nova.api.openstack.extensions
^[[01;35m^[[00mTraceback (most recent call last):
^[[01;31m2016-11-01 12:13:27.523 TRACE nova.api.openstack.extensions
^[[01;35m^[[00m File "/opt/stack/nova/nova/api/openstack/extensions.py", line
478, in wrapped
^[[01;31m2016-11-01 12:13:27.523 TRACE nova.api.openstack.extensions
^[[01;35m^[[00mreturn f(*args, **kwargs)
^[[01;31m2016-11-01 12:13:27.523 TRACE nova.api.openstack.extensions
^[[01;35m^[[00m File "/opt/stack/nova/nova/api/validation/__init__.py", line
73, in wrapper
^[[01;31m2016-11-01 12:13:27.523 TRACE nova.api.openstack.extensions
^[[01;35m^[[00mreturn func(*args, **kwargs)
^[[01;31m2016-11-01 12:13:27.523 TRACE nova.api.openstack.extensions
^[[01;35m^[[00m File "/opt/stack/nova/nova/api/validation/__init__.py", line
73, in wrapper
^[[01;31m2016-11-01 12:13:27.523 TRACE nova.api.openstack.extensions
^[[01;35m^[[00mreturn func(*args, **kwargs)
^[[01;31m2016-11-01 12:13:27.523 TRACE nova.api.openstack.extensions
^[[01;35m^[[00m File "/opt/stack/nova/nova/api/validation/__init__.py", line
73, in wrapper
^[[01;31m2016-11-01 12:13:27.523 TRACE nova.api.openstack.extensions
^[[01;35m^[[00mreturn func(*args, **kwargs)
^[[01;31m2016-11-01 12:13:27.523 TRACE nova.api.openstack.extensions
^[[01;35m^[[00m File "/opt/stack/nova/nova/api/openstack/compute/servers.py",
line 629, in create
^[[01;31m2016-11-01 12:13:27.523 TRACE nova.api.openstack.extensions
^[[01;35m^[[00m**create_kwargs)
^[[01;31m2016-11-01 12:13:27.523 TRACE nova.api.openstack.extensions
^[[01;35m^[[00m File "/opt/stack/nova/nova/hooks.py", line 154, in inner
^[[01;31m2016-11-01 12:13:27.523 TRACE nova.api.openstack.extensions
^[[01;35m^[[00mrv = f(*args, **kwargs)
^[[01;31m2016-11-01 12:13:27.523 TRACE nova.api.openstack.extensions
^[[01;35m^[[00m File "/opt/stack/nova/nova/compute/api.py", line 1563, in
create
^[[01;31m2016-11-01 12:13:27.523 TRACE nova.api.openstack.extensions
^[[01;35m^[[00mcheck_server_group_quota=check_server_group_quota)
^[[01;31m2016-11-01 12:13:27.523 TRACE nova.api.openstack.extensions
^[[01;35m^[[00m File "/opt/stack/nova/nova/compute/api.py", line 1146, in
_create_instance
^[[01;31m2016-11-01 12:13:27.523 TRACE nova.api.openstack.extensions
^[[01;35m^[[00mreservation_id, max_count)
^[[01;31m2016-11-01 12:13:27.523 TRACE nova.api.openstack.extensions
^[[01;35m^[[00m File "/opt/stack/nova/nova/compute/api.py", line 871, in
_validate_and_build_base_options
^[[01;31m2016-11-01 12:13:27.523 TRACE nova.api.openstack.extensions
^[[01;35m^[[00minstance_type)
^[[01;31m2016-11-01 12:13:27.523 TRACE nova.api.openstack.extensions
^[[01;35m^[[00m File "/opt/stack/nova/no
[Yahoo-eng-team] [Bug 1594702] [NEW] The ConsumerBase should be changed into Consumer in trace log
Public bug reported: The ConsumerBase should be changed into Consumer in trace log ** Affects: oslo.messaging Importance: Undecided Assignee: zhaolihui (zhaolh) Status: New ** Project changed: nova => oslo.messaging ** Changed in: oslo.messaging Assignee: (unassigned) => zhaolihui (zhaolh) -- 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/1594702 Title: The ConsumerBase should be changed into Consumer in trace log Status in oslo.messaging: New Bug description: The ConsumerBase should be changed into Consumer in trace log To manage notifications about this bug go to: https://bugs.launchpad.net/oslo.messaging/+bug/1594702/+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 1593119] [NEW] The _wrn_threshold should be removed
Public bug reported: The data member _wrn_threshold of oslo_messaging._driver.amqpdriver.ReplyWaiters should be removed. ** Affects: oslo.messaging Importance: Undecided Assignee: zhaolihui (zhaolh) Status: New ** Project changed: nova => oslo.messaging ** Changed in: oslo.messaging Assignee: (unassigned) => zhaolihui (zhaolh) -- 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/1593119 Title: The _wrn_threshold should be removed Status in oslo.messaging: New Bug description: The data member _wrn_threshold of oslo_messaging._driver.amqpdriver.ReplyWaiters should be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/oslo.messaging/+bug/1593119/+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 1592654] [NEW] Make sure vmware resize on the same host
Public bug reported: Make sure vmware resize on the same host ** Affects: nova Importance: Undecided Assignee: zhaolihui (zhaolh) Status: New ** Changed in: nova Assignee: (unassigned) => zhaolihui (zhaolh) -- 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/1592654 Title: Make sure vmware resize on the same host Status in OpenStack Compute (nova): New Bug description: Make sure vmware resize on the same host To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1592654/+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 1592283] [NEW] openstack-db not drop nova_api database
Public bug reported: Description === When use openstack-db script to drop nova service, the nova database was dropped, but the nova_api database wasn't dropped. Steps to reproduce == /usr/bin/openstack-db --service nova --drop Expected result === Command 'mysql -uroot -p' to login mysql, the nova and nova_api database should be dropped. Actual result = The nova database was dropped, but the nova_api database wasn't dropped. Environment === openstack mitaka version. openstack-nova-common-13.0.0-1.el7.noarch openstack-nova-api-13.0.0-1.el7.noarch ** Affects: nova Importance: Undecided Assignee: zhaolihui (zhaolh) Status: New ** Changed in: nova Assignee: (unassigned) => zhaolihui (zhaolh) -- 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/1592283 Title: openstack-db not drop nova_api database Status in OpenStack Compute (nova): New Bug description: Description === When use openstack-db script to drop nova service, the nova database was dropped, but the nova_api database wasn't dropped. Steps to reproduce == /usr/bin/openstack-db --service nova --drop Expected result === Command 'mysql -uroot -p' to login mysql, the nova and nova_api database should be dropped. Actual result = The nova database was dropped, but the nova_api database wasn't dropped. Environment === openstack mitaka version. openstack-nova-common-13.0.0-1.el7.noarch openstack-nova-api-13.0.0-1.el7.noarch To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1592283/+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 1569779] Re: allow to investigate instance actions after instance deletion
In mitaka, create instance, command 'nova list' to view instance's uuid. +--+---+++-++ | ID | Name | Status | Task State | Power State | Networks | +--+---+++-++ | 738c80f1-03d0-4a93-844b-bee22b3654de | first | ACTIVE | - | Running | private=fd33:f306:b926:0:f816:3eff:fed8:34b5, 10.0.0.3 | +--+---+++-++ command 'nova instance-action-list 738c80f1-03d0-4a93-844b-bee22b3654de ' was returned: ++--+-++ | Action | Request_ID | Message | Start_Time | ++--+-++ | create | req-e5c1d5b4-590e-4f7f-ab2b-025302998bff | - | 2016-04-14T03:06:46.00 | ++--+-++ delete instance, command 'nova instance-action-list 738c80f1-03d0-4a93-844b-bee22b3654de ' was returned: ++--+-++ | Action | Request_ID | Message | Start_Time | ++--+-++ | create | req-e5c1d5b4-590e-4f7f-ab2b-025302998bff | - | 2016-04-14T03:06:46.00 | | delete | req-16e7dc74-1449-4e4a-a662-a0279c88620f | - | 2016-04-14T03:18:34.00 | ++--+-++ there is no 404 error. ** Changed in: nova Status: New => Invalid ** Changed in: nova Assignee: zhaolihui (zhaolh) => (unassigned) -- 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/1569779 Title: allow to investigate instance actions after instance deletion Status in OpenStack Compute (nova): Invalid Bug description: Right now if instance has been deleted, 'nova instance-action-list' returns 404. Due to very specific nature of 'action list' is is very nice to have ability to see action lists for deleted instances, especially deletion request. Can this feature be added to nova? Al least, for administrators. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1569779/+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 1567024] Re: updated VM name leaves libvirt domain behind after deletion
When created vm, the libvirt driver created vm on compute node.
When updated vm name, the vm name updated in the database, the vm name didn't
update on the compute node by libvirt.xml, this means that instance.name would
not changed.
When deleted vm, the function call 'self._get_domain_by_name(instance.name) '
would get the right domain by name, so it is correct to delete vm.
By the way, I tested it in liberty version.
** Changed in: nova
Status: New => Invalid
** Changed in: nova
Assignee: zhaolihui (zhaolh) => (unassigned)
--
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/1567024
Title:
updated VM name leaves libvirt domain behind after deletion
Status in OpenStack Compute (nova):
Invalid
Bug description:
After successfully updating the name of an instance (from a libvirt/KVM
host), I proceeded to delete the instance.
The instance was successfully deleted. However, upon using "virsh list
--all", it can be seen that the domain has not been undefined.
Steps to Reproduce:
1. Setup instance with a libvirt/KVM host and SVC storage
2. Spawn a VM called "test-vm"
API --> POST https://:8774/v2.1/da0be0d560f541d7acccb66104ebe094/servers
3. Update the VM with a new name "new-name-vm"
API --> PUT
https://:8774/v2.1/da0be0d560f541d7acccb66104ebe094/servers/5334ead7-4bd7-4f81-8b41-d833ebf52a9b
body: {{'name': 'new-name-vm'}}
4. Delete the VM
API --> DELETE
https://:8774/v2.1/da0be0d560f541d7acccb66104ebe094/servers/5334ead7-4bd7-4f81-8b41-d833ebf52a9b
Expected Results:
The VM to be deleted and the libvirt domain to be destroyed and undefined.
"virsh list --all" should return:
virsh list --all
IdName State
Actual Results:
The VM is deleted but the domain was not undefined and still appears on the
KVM using "virsh list --all".
"virsh list --all" returned:
virsh list --all
IdNameState
---
22test-vm-5334ead7-0016 running
Version of libvirt: libvirtd (libvirt) 1.2.16
Version of Nova: 13.0.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1567024/+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 1549590] [NEW] the ram and disk should have a unit when display
Public bug reported: "ram:%s disk:%s" should with unit like that "ram:%smb disk:%smb" ** Affects: nova Importance: Undecided Assignee: zhaolihui (zhaolh) Status: New ** Changed in: nova Assignee: (unassigned) => zhaolihui (zhaolh) -- 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/1549590 Title: the ram and disk should have a unit when display Status in OpenStack Compute (nova): New Bug description: "ram:%s disk:%s" should with unit like that "ram:%smb disk:%smb" To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1549590/+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
