Marking the horizon bug as Invalid due to lack of confirmation and low
probability that there is a bug in horizon
** Changed in: horizon
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
** Changed in: nova
Milestone: icehouse-1 => 2014.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245719
Title:
RBD backed instance can't shutdown and restart
To manage notifications about thi
Related to Horizon, does this bug still exist after nova patch is merged.
I don't have Ceph environment now and cannot check it.
Horizon team needs more information about the current status. Mark it
"Incomplete".
** Changed in: horizon
Status: New => Incomplete
--
You received this bug n
** Changed in: nova/havana
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245719
Title:
RBD backed instance can't shutdown and restart
To manage notific
** Changed in: nova/havana
Status: New => Fix Committed
** Changed in: nova/havana
Milestone: None => 2013.2.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245719
Title:
RBD backed ins
** Also affects: nova/havana
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245719
Title:
RBD backed instance can't shutdown and restart
To manage notifi
Reviewed: https://review.openstack.org/58102
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=dfde60b4bb05c45daedc2eaa98fcd772e647fba5
Submitter: Jenkins
Branch:stable/havana
commit dfde60b4bb05c45daedc2eaa98fcd772e647fba5
Author: Mike Perez
Date: Wed Nov 20 01:22:38 20
** Changed in: nova
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245719
Title:
RBD backed instance can't shutdown and restart
To manage notifications
** Changed in: nova
Milestone: None => icehouse-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245719
Title:
RBD backed instance can't shutdown and restart
To manage notifications about this
Reviewed: https://review.openstack.org/57406
Committed:
http://github.com/openstack/nova/commit/85d0ace169be513c30b09e13a35fa7d912f5b380
Submitter: Jenkins
Branch:master
commit 85d0ace169be513c30b09e13a35fa7d912f5b380
Author: Mike Perez
Date: Wed Nov 20 01:22:38 2013 -0800
Include im
I've acked the fix on the master branch - we need this on stable/havana
too. I can't seem to propose the bug, but will happily do the backport.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245719
Ti
** Changed in: nova
Status: New => Confirmed
** Changed in: nova
Status: Confirmed => In Progress
** Changed in: nova
Assignee: (unassigned) => Mike Perez (thingee)
** Tags added: havana-backport-potential
--
You received this bug notification because you are a member of Ubu
I'm also having the same problem. Using RBD for both Cinder and Glance
image backend. If I create an instance and select in horizon 'boot from
image (create new volume)', soft/hard reboot fails later.
I get the following error from the compute manager:
2013-11-19 09:56:26.036 ERROR nova.openstac
Hi Blane,
Sorry for my late reply, I'm using the ubuntu Havana with the latest
from "updates" repo.
Q
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245719
Title:
RBD backed instance can't shutdow
Hi Quenten, what version are you installing, and what error do you get?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245719
Title:
RBD backed instance can't shutdown and restart
To manage notific
I Tried to implement the patch from Blane however doesn't seem to work.
When trying to launch a instance it now fails when it try's to map the
block device.
Any ideas?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
The attachment "Work-around rather than fix" seems to be a patch. If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~
I believe this is a problem with the source_type being set to image and
the destination_type being set to volume which prevents the
DriverVolumeBlockDevice._transform code from firing. A work around is
attached that just detects the source_type as image and forces it to
volume for the check - a bet
This seems to be similar to Bug #1248695
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245719
Title:
RBD backed instance can't shutdown and restart
To manage notifications about this bug go to:
ht
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245719
Title:
RBD backed i
The 'Boot from image (creates a new volume)' code path uses the new
block_device_mapping_v2 api. This is most likely a bug in the
implementation of this in nova that affects all volumes backends, not
just rbd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I've found if i create the instance via horizon using the "Launch
Instance"
Using Instance Boot Source: Boot from image (creates a new volume)
Selecting Image etc,
when powered off and back on again the error happens every time.
However!
If I create the volume first and use a "Boot from Volume
22 matches
Mail list logo
