2014-10-03 15:07:41 |
Oleksii Aleksieiev |
bug |
|
|
added bug |
2014-10-03 15:58:02 |
Dmitry Mescheryakov |
nominated for series |
|
mos/5.0.x |
|
2014-10-03 15:58:02 |
Dmitry Mescheryakov |
bug task added |
|
mos/5.0.x |
|
2014-10-03 15:58:02 |
Dmitry Mescheryakov |
nominated for series |
|
mos/5.1.x |
|
2014-10-03 15:58:02 |
Dmitry Mescheryakov |
bug task added |
|
mos/5.1.x |
|
2014-10-03 15:58:19 |
Dmitry Mescheryakov |
mos: importance |
Undecided |
Medium |
|
2014-10-03 15:58:21 |
Dmitry Mescheryakov |
mos/5.0.x: importance |
Undecided |
Medium |
|
2014-10-03 15:58:24 |
Dmitry Mescheryakov |
mos/5.1.x: importance |
Undecided |
Medium |
|
2014-10-03 15:58:30 |
Dmitry Mescheryakov |
mos: assignee |
|
MOS Nova (mos-nova) |
|
2014-10-03 15:58:38 |
Dmitry Mescheryakov |
mos/5.0.x: assignee |
|
MOS Nova (mos-nova) |
|
2014-10-03 15:58:46 |
Dmitry Mescheryakov |
mos: status |
New |
Confirmed |
|
2014-10-03 15:58:48 |
Dmitry Mescheryakov |
mos/5.0.x: status |
New |
Confirmed |
|
2014-10-03 15:58:50 |
Dmitry Mescheryakov |
mos/5.1.x: status |
New |
Confirmed |
|
2014-10-03 15:58:54 |
Dmitry Mescheryakov |
mos: milestone |
|
5.1.1 |
|
2014-10-03 15:58:56 |
Dmitry Mescheryakov |
mos/5.0.x: milestone |
|
5.0.3 |
|
2014-10-03 15:58:58 |
Dmitry Mescheryakov |
mos/5.1.x: milestone |
|
5.1.1 |
|
2014-10-03 16:00:06 |
Dmitry Mescheryakov |
mos/5.1.x: assignee |
|
MOS Nova (mos-nova) |
|
2014-10-03 16:13:44 |
Dmitry Mescheryakov |
tags |
customer-found |
customer-found nova |
|
2014-10-17 16:40:59 |
Roman Podoliaka |
mos: assignee |
MOS Nova (mos-nova) |
Andrey Kurilin (akurilin) |
|
2014-10-17 16:41:05 |
Roman Podoliaka |
mos/5.0.x: assignee |
MOS Nova (mos-nova) |
Andrey Kurilin (akurilin) |
|
2014-10-17 16:41:10 |
Roman Podoliaka |
mos/5.1.x: assignee |
MOS Nova (mos-nova) |
Andrey Kurilin (akurilin) |
|
2014-10-29 17:15:33 |
Dmitry Mescheryakov |
bug task deleted |
mos/5.1.x |
|
|
2014-11-12 21:12:46 |
Dmitry Borodaenko |
mos: milestone |
5.1.1 |
6.0 |
|
2014-11-12 21:12:50 |
Dmitry Borodaenko |
mos/5.0.x: milestone |
5.0.3 |
5.1.1 |
|
2014-11-12 21:12:54 |
Dmitry Borodaenko |
mos/5.0.x: status |
Confirmed |
Won't Fix |
|
2014-12-01 13:39:02 |
Roman Podoliaka |
mos: milestone |
6.0 |
6.0.1 |
|
2014-12-22 22:30:31 |
Dmitry Mescheryakov |
nominated for series |
|
mos/6.0.x |
|
2014-12-22 22:30:31 |
Dmitry Mescheryakov |
bug task added |
|
mos/6.0.x |
|
2014-12-22 22:30:31 |
Dmitry Mescheryakov |
nominated for series |
|
mos/6.1.x |
|
2014-12-22 22:30:31 |
Dmitry Mescheryakov |
bug task added |
|
mos/6.1.x |
|
2014-12-22 22:30:38 |
Dmitry Mescheryakov |
mos/6.1.x: status |
New |
Confirmed |
|
2014-12-22 22:30:40 |
Dmitry Mescheryakov |
mos/6.1.x: importance |
Undecided |
Medium |
|
2014-12-22 22:30:46 |
Dmitry Mescheryakov |
mos/6.1.x: assignee |
|
Andrey Kurilin (akurilin) |
|
2014-12-22 22:30:48 |
Dmitry Mescheryakov |
mos/6.1.x: milestone |
|
6.1 |
|
2014-12-22 22:30:50 |
Dmitry Mescheryakov |
mos/6.0.x: status |
Confirmed |
Won't Fix |
|
2014-12-23 10:04:49 |
Dmitry Mescheryakov |
mos: status |
Confirmed |
Won't Fix |
|
2015-02-04 14:22:58 |
Miroslav Anashkin |
description |
Env:
MOS 5.1 on Centos.
Cepsh is used as backed for all images,volimes instances.
Environment have availability zones.
Volumes are also created in appropriate availability zones.
Cross zone volume usage is disabled (in nova conf cinder_cross_az_attach=false ).
Description.
When booting instance from image with creation of a volume and if availability zone is used, it fails because nova cannot access the new volume. The reason for this is volume is created in internal zone instead of the one where instance is created.
Step to reproduce.
boot an instance
nova boot test --flavor 1 --image Centos-6.5 --nic net-id=netid --availability-zone=az1 --key-name key-name --block-device "source=image,id=imageid,dest=volume,size=15,bootindex=1"
replace imageid, netid, key-name, image with real one present in your environment.
nova api error log:
HTTP exception thrown: Block Device Mapping is Invalid: failed to get volume VOLUMEID. |
Env:
MOS 5.1 on Centos.
Ceph is used as backed for all images,volimes instances.
Environment have availability zones.
Volumes are also created in appropriate availability zones.
Cross zone volume usage is disabled (in nova conf cinder_cross_az_attach=false ).
Description.
When booting instance from image with creation of a volume and if availability zone is used, it fails because nova cannot access the new volume. The reason for this is volume is created in internal zone instead of the one where instance is created.
Step to reproduce.
boot an instance
nova boot test --flavor 1 --image Centos-6.5 --nic net-id=netid --availability-zone=az1 --key-name key-name --block-device "source=image,id=imageid,dest=volume,size=15,bootindex=1"
replace imageid, netid, key-name, image with real one present in your environment.
nova api error log:
HTTP exception thrown: Block Device Mapping is Invalid: failed to get volume VOLUMEID. |
|
2015-02-04 14:23:36 |
Miroslav Anashkin |
description |
Env:
MOS 5.1 on Centos.
Ceph is used as backed for all images,volimes instances.
Environment have availability zones.
Volumes are also created in appropriate availability zones.
Cross zone volume usage is disabled (in nova conf cinder_cross_az_attach=false ).
Description.
When booting instance from image with creation of a volume and if availability zone is used, it fails because nova cannot access the new volume. The reason for this is volume is created in internal zone instead of the one where instance is created.
Step to reproduce.
boot an instance
nova boot test --flavor 1 --image Centos-6.5 --nic net-id=netid --availability-zone=az1 --key-name key-name --block-device "source=image,id=imageid,dest=volume,size=15,bootindex=1"
replace imageid, netid, key-name, image with real one present in your environment.
nova api error log:
HTTP exception thrown: Block Device Mapping is Invalid: failed to get volume VOLUMEID. |
Env:
MOS 5.1 on Centos.
Ceph is used as backend for all images,volumes, instances.
Environment have availability zones.
Volumes are also created in appropriate availability zones.
Cross zone volume usage is disabled (in nova conf cinder_cross_az_attach=false ).
Description.
When booting instance from image with creation of a volume and if availability zone is used, it fails because nova cannot access the new volume. The reason for this is volume is created in internal zone instead of the one where instance is created.
Step to reproduce.
boot an instance
nova boot test --flavor 1 --image Centos-6.5 --nic net-id=netid --availability-zone=az1 --key-name key-name --block-device "source=image,id=imageid,dest=volume,size=15,bootindex=1"
replace imageid, netid, key-name, image with real one present in your environment.
nova api error log:
HTTP exception thrown: Block Device Mapping is Invalid: failed to get volume VOLUMEID. |
|
2015-02-05 15:17:47 |
Denis Klepikov |
mos/5.0.x: importance |
Medium |
High |
|
2015-02-05 15:18:07 |
Denis Klepikov |
mos/5.0.x: importance |
High |
Medium |
|
2015-02-05 15:18:19 |
Denis Klepikov |
mos/5.0.x: importance |
Medium |
High |
|
2015-02-09 18:00:40 |
Dmitry Mescheryakov |
mos/5.0.x: importance |
High |
Medium |
|
2015-02-10 04:15:57 |
Alexander Bozhenko |
bug |
|
|
added subscriber Alexander Bozhenko |
2015-02-18 15:03:47 |
Andriy Kurilin |
mos/6.1.x: status |
Confirmed |
In Progress |
|
2015-02-18 17:32:01 |
Andriy Kurilin |
attachment added |
|
lp_1377196.patch https://bugs.launchpad.net/mos/+bug/1377196/+attachment/4321967/+files/lp_1377196.patch |
|
2015-02-19 10:16:54 |
Denis Meltsaykin |
nominated for series |
|
mos/5.1-updates |
|
2015-02-19 10:16:54 |
Denis Meltsaykin |
bug task added |
|
mos/5.1-updates |
|
2015-02-19 10:17:01 |
Denis Meltsaykin |
mos/5.1-updates: milestone |
|
5.1-updates |
|
2015-02-19 10:17:04 |
Denis Meltsaykin |
mos/5.1-updates: assignee |
|
Denis Meltsaykin (dmeltsaykin) |
|
2015-02-19 10:17:26 |
Denis Meltsaykin |
mos/5.1-updates: status |
New |
In Progress |
|
2015-02-19 10:17:42 |
Denis Meltsaykin |
mos/5.1-updates: importance |
Undecided |
High |
|
2015-02-22 22:08:18 |
Fuel Devops McRobotson |
bug task deleted |
mos/5.0.x |
|
|
2015-02-22 22:08:26 |
Fuel Devops McRobotson |
mos/5.1.1-updates: milestone |
|
5.1.1-updates |
|
2015-02-22 22:08:29 |
Fuel Devops McRobotson |
mos/6.0-updates: milestone |
|
6.0-updates |
|
2015-02-24 17:00:53 |
Denis Meltsaykin |
mos/5.1.x: milestone |
|
5.1.2 |
|
2015-02-24 17:01:05 |
Denis Meltsaykin |
mos/6.0-updates: status |
New |
Won't Fix |
|
2015-02-24 17:01:46 |
Denis Meltsaykin |
mos/6.0-updates: assignee |
|
MOS Sustaining (mos-sustaining) |
|
2015-02-24 17:02:33 |
Denis Meltsaykin |
mos/5.1.x: assignee |
|
Denis Meltsaykin (dmeltsaykin) |
|
2015-02-24 17:02:35 |
Denis Meltsaykin |
mos/5.1.1-updates: assignee |
|
Denis Meltsaykin (dmeltsaykin) |
|
2015-02-24 17:02:48 |
Denis Meltsaykin |
mos/5.1.1-updates: status |
New |
In Progress |
|
2015-02-24 17:02:53 |
Denis Meltsaykin |
mos/5.1.x: status |
New |
In Progress |
|
2015-02-24 17:02:57 |
Denis Meltsaykin |
mos/5.1.1-updates: importance |
Undecided |
Medium |
|
2015-02-24 17:03:00 |
Denis Meltsaykin |
mos/5.1.x: importance |
Undecided |
Medium |
|
2015-02-25 19:00:52 |
Alexander Bozhenko |
removed subscriber Alexander Bozhenko |
|
|
|
2015-03-03 16:37:17 |
Roman Podoliaka |
mos/6.1.x: status |
In Progress |
Fix Committed |
|
2015-03-03 16:37:19 |
Roman Podoliaka |
mos/6.0.x: status |
Won't Fix |
Fix Committed |
|
2015-03-03 16:37:29 |
Roman Podoliaka |
mos/5.1.x: status |
In Progress |
Won't Fix |
|
2015-03-04 10:23:53 |
Denis Meltsaykin |
mos/5.1-updates: importance |
High |
Medium |
|
2015-03-04 10:23:58 |
Denis Meltsaykin |
mos/5.1.1-updates: status |
In Progress |
Won't Fix |
|
2015-03-04 10:24:04 |
Denis Meltsaykin |
mos/5.1-updates: status |
In Progress |
Won't Fix |
|
2015-03-06 15:36:41 |
Alexander Gubanov |
mos/6.1.x: status |
Fix Committed |
Fix Released |
|
2015-03-07 18:37:04 |
Alexander Gubanov |
mos/6.0.x: status |
Fix Committed |
Fix Released |
|
2015-03-26 15:53:29 |
Vitaly Sedelnik |
mos/6.0-updates: milestone |
6.0-updates |
6.0-mu-1 |
|
2015-04-30 15:39:45 |
Vitaly Sedelnik |
mos/6.0-updates: milestone |
6.0-mu-1 |
6.0-updates |
|