| 2016-09-21 17:07:44 |
sryabin |
bug |
|
|
added bug |
| 2016-09-21 17:08:04 |
Vladimir Khlyunev |
fuel: importance |
Undecided |
High |
|
| 2016-09-21 21:27:14 |
Ilya Kharin |
fuel: status |
New |
Confirmed |
|
| 2016-09-22 00:25:27 |
Ilya Kharin |
summary |
[upgrade] after successfully MOS non-livemigration upgrade 7->9, nova can't boot vm |
[upgrade] after successfully MOS (non-)livemigration upgrade 7->9, nova can't boot vm |
|
| 2016-09-22 00:27:24 |
Ilya Kharin |
summary |
[upgrade] after successfully MOS (non-)livemigration upgrade 7->9, nova can't boot vm |
[upgrade] after successfully MOS upgrade 7->9, nova can't boot VMs |
|
| 2016-09-22 00:27:34 |
Ilya Kharin |
summary |
[upgrade] after successfully MOS upgrade 7->9, nova can't boot VMs |
After successfully MOS upgrade 7->9, nova can't boot VMs |
|
| 2016-09-22 00:28:04 |
Ilya Kharin |
summary |
After successfully MOS upgrade 7->9, nova can't boot VMs |
After successfully upgraded MOS 7->9, nova can't boot VMs |
|
| 2016-09-22 07:29:51 |
Roman Podoliaka |
summary |
After successfully upgraded MOS 7->9, nova can't boot VMs |
After successfully upgraded MOS 7->9, nova can't reboot VMs |
|
| 2016-09-22 08:17:40 |
Timofey Durakov |
fuel: assignee |
Ilya Kharin (akscram) |
Timofey Durakov (tdurakov) |
|
| 2016-09-22 08:23:55 |
Ilya Kharin |
description |
Steps to reproduce:
Upgrade cluster and master node from 7.0 up to 9.1
Expected results:
Nova have ability boot vm
Actual result:
Cannot reboot instance: [Errno 2] No such file or directory: '/var/lib/nova/instances/instance-0000004d/disk.config'
Reproducibility:
100%
Workaround:
#on master node
fuel nodes --env 2 | awk -F\| '/compute/ {print $5}' | xargs -I% ssh -q % 'find /var/lib/nova/instances -type d | grep -E "/var/lib/nova/instances/.{36}" | xargs -I{} bash -c "test -f {}/disk.config || (touch {}/disk.config && echo {})"'
#on controller
. openrc && nova list | awk '/SHUTOFF/ {print $2}' | xargs -I% nova start % |
Steps to reproduce:
1. Upgrade the Fuel Master node with the MOS cluster from 7.0 to 9.1
2. Perform `nova stop` and then `nova start` for some of old instances:
2.a nova stop 111d66d4-e3de-4335-bfa6-05a1bb76b1e5
Request to stop server 111d66d4-e3de-4335-bfa6-05a1bb76b1e5 has been accepted.
2.b nova start 111d66d4-e3de-4335-bfa6-05a1bb76b1e5
Request to start server 111d66d4-e3de-4335-bfa6-05a1bb76b1e5 has been accepted.
Expected results:
The instance is successfully started again.
Actual result:
Cannot reboot instance: [Errno 2] No such file or directory: '/var/lib/nova/instances/instance-0000004d/disk.config'
Reproducibility:
100%
Workaround:
#on master node
fuel nodes --env 2 | awk -F\| '/compute/ {print $5}' | xargs -I% ssh -q % 'find /var/lib/nova/instances -type d | grep -E "/var/lib/nova/instances/.{36}" | xargs -I{} bash -c "test -f {}/disk.config || (touch {}/disk.config && echo {})"'
#on controller
. openrc && nova list | awk '/SHUTOFF/ {print $2}' | xargs -I% nova start %
Information:
The traceback can be found here: http://paste.openstack.org/show/582524/ |
|
| 2016-09-22 10:20:14 |
Roman Podoliaka |
summary |
After successfully upgraded MOS 7->9, nova can't reboot VMs |
After live migrating a VM without a config drive to a node with force_config_drive=True Nova can't reboot it |
|
| 2016-09-22 10:20:45 |
Roman Podoliaka |
description |
Steps to reproduce:
1. Upgrade the Fuel Master node with the MOS cluster from 7.0 to 9.1
2. Perform `nova stop` and then `nova start` for some of old instances:
2.a nova stop 111d66d4-e3de-4335-bfa6-05a1bb76b1e5
Request to stop server 111d66d4-e3de-4335-bfa6-05a1bb76b1e5 has been accepted.
2.b nova start 111d66d4-e3de-4335-bfa6-05a1bb76b1e5
Request to start server 111d66d4-e3de-4335-bfa6-05a1bb76b1e5 has been accepted.
Expected results:
The instance is successfully started again.
Actual result:
Cannot reboot instance: [Errno 2] No such file or directory: '/var/lib/nova/instances/instance-0000004d/disk.config'
Reproducibility:
100%
Workaround:
#on master node
fuel nodes --env 2 | awk -F\| '/compute/ {print $5}' | xargs -I% ssh -q % 'find /var/lib/nova/instances -type d | grep -E "/var/lib/nova/instances/.{36}" | xargs -I{} bash -c "test -f {}/disk.config || (touch {}/disk.config && echo {})"'
#on controller
. openrc && nova list | awk '/SHUTOFF/ {print $2}' | xargs -I% nova start %
Information:
The traceback can be found here: http://paste.openstack.org/show/582524/ |
Steps to reproduce:
1. Upgrade the Fuel Master node with the MOS cluster from 7.0 to 9.1
2. Perform `nova stop` and then `nova start` for some of old instances:
2.a nova stop 111d66d4-e3de-4335-bfa6-05a1bb76b1e5
Request to stop server 111d66d4-e3de-4335-bfa6-05a1bb76b1e5 has been accepted.
2.b nova start 111d66d4-e3de-4335-bfa6-05a1bb76b1e5
Request to start server 111d66d4-e3de-4335-bfa6-05a1bb76b1e5 has been accepted.
Expected results:
The instance is successfully started again.
Actual result:
Cannot reboot instance: [Errno 2] No such file or directory: '/var/lib/nova/instances/instance-0000004d/disk.config'
Reproducibility:
100%
Workaround:
#on master node
fuel nodes --env 2 | awk -F\| '/compute/ {print $5}' | xargs -I% ssh -q % 'find /var/lib/nova/instances -type d | grep -E "/var/lib/nova/instances/.{36}" | xargs -I{} bash -c "test -f {}/disk.config || (touch {}/disk.config && echo {})"'
#on controller
. openrc && nova list | awk '/SHUTOFF/ {print $2}' | xargs -I% nova start %
Information:
The traceback can be found here: http://paste.openstack.org/show/582524/ |
|
| 2016-09-22 10:21:32 |
Roman Podoliaka |
tags |
team-upgrades |
area-nova team-upgrades |
|
| 2016-09-22 13:28:27 |
Ilya Kharin |
tags |
area-nova team-upgrades |
area-nova release-notes team-upgrades |
|
| 2016-09-22 14:47:57 |
Timofey Durakov |
summary |
After live migrating a VM without a config drive to a node with force_config_drive=True Nova can't reboot it |
After changing force_config_drive option to True instance fails to restart |
|
| 2016-09-22 14:51:25 |
Timofey Durakov |
description |
Steps to reproduce:
1. Upgrade the Fuel Master node with the MOS cluster from 7.0 to 9.1
2. Perform `nova stop` and then `nova start` for some of old instances:
2.a nova stop 111d66d4-e3de-4335-bfa6-05a1bb76b1e5
Request to stop server 111d66d4-e3de-4335-bfa6-05a1bb76b1e5 has been accepted.
2.b nova start 111d66d4-e3de-4335-bfa6-05a1bb76b1e5
Request to start server 111d66d4-e3de-4335-bfa6-05a1bb76b1e5 has been accepted.
Expected results:
The instance is successfully started again.
Actual result:
Cannot reboot instance: [Errno 2] No such file or directory: '/var/lib/nova/instances/instance-0000004d/disk.config'
Reproducibility:
100%
Workaround:
#on master node
fuel nodes --env 2 | awk -F\| '/compute/ {print $5}' | xargs -I% ssh -q % 'find /var/lib/nova/instances -type d | grep -E "/var/lib/nova/instances/.{36}" | xargs -I{} bash -c "test -f {}/disk.config || (touch {}/disk.config && echo {})"'
#on controller
. openrc && nova list | awk '/SHUTOFF/ {print $2}' | xargs -I% nova start %
Information:
The traceback can be found here: http://paste.openstack.org/show/582524/ |
Steps to reproduce:
1. Check that force_config_drive option is set to false
2. Boot instance
3. Set force_config_drive option to true
4. Restart nova services
5. Stop instance
6. Start instance
Expected results:
The instance is successfully started.
Actual result:
Cannot reboot instance: [Errno 2] No such file or directory: '/var/lib/nova/instances/instance-0000004d/disk.config'
Reproducibility:
100%
Workaround:
cold migrate instance after changing force_config_drive in nova.
Information:
The traceback can be found here: http://paste.openstack.org/show/582524/ |
|
| 2016-09-23 13:52:26 |
Anton Matveev |
fuel: milestone |
9.1 |
9.2 |
|
| 2016-09-26 10:48:15 |
Timofey Durakov |
description |
Steps to reproduce:
1. Check that force_config_drive option is set to false
2. Boot instance
3. Set force_config_drive option to true
4. Restart nova services
5. Stop instance
6. Start instance
Expected results:
The instance is successfully started.
Actual result:
Cannot reboot instance: [Errno 2] No such file or directory: '/var/lib/nova/instances/instance-0000004d/disk.config'
Reproducibility:
100%
Workaround:
cold migrate instance after changing force_config_drive in nova.
Information:
The traceback can be found here: http://paste.openstack.org/show/582524/ |
Upstream bug : https://bugs.launchpad.net/nova/+bug/1303714
Steps to reproduce:
1. Check that force_config_drive option is set to false
2. Boot instance
3. Set force_config_drive option to true
4. Restart nova services
5. Stop instance
6. Start instance
Expected results:
The instance is successfully started.
Actual result:
Cannot reboot instance: [Errno 2] No such file or directory: '/var/lib/nova/instances/instance-0000004d/disk.config'
Reproducibility:
100%
Workaround:
cold migrate instance after changing force_config_drive in nova.
Information:
The traceback can be found here: http://paste.openstack.org/show/582524/ |
|
| 2016-09-27 08:48:31 |
Maria Zlatkova |
tags |
area-nova release-notes team-upgrades |
area-nova release-notes-done team-upgrades |
|
| 2016-12-22 15:48:30 |
Alexey Shtokolov |
tags |
area-nova release-notes-done team-upgrades |
area-nova release-notes release-notes-done team-upgrades |
|
| 2017-01-11 09:08:32 |
Vitaly Sedelnik |
fuel: milestone |
9.2 |
9.3 |
|
| 2017-01-11 09:08:41 |
Vitaly Sedelnik |
tags |
area-nova release-notes release-notes-done team-upgrades |
area-nova move-to-9.3 release-notes release-notes-done team-upgrades |
|
| 2017-01-26 10:44:55 |
Maria Zlatkova |
tags |
area-nova move-to-9.3 release-notes release-notes-done team-upgrades |
area-nova move-to-9.3 release-notes-done team-upgrades |
|
