** Changed in: cloud-archive
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer access
** Changed in: cloud-archive
Status: Confirmed = 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/1065702
Title:
After folsom upgrade, instances can no longer access existing
** Changed in: cinder
Milestone: grizzly-1 = 2013.1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer access existing
** Changed in: cinder
Milestone: grizzly-1 = 2013.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer access existing volumes.
To
This bug was fixed in the package cinder - 2012.2.1-0ubuntu1
---
cinder (2012.2.1-0ubuntu1) quantal-proposed; urgency=low
* Ubuntu updates:
- Cinder should suggest ceph-common, not python-ceph (LP: #1065901):
- debian/control: cinder-volume Suggests: python-ceph -
This bug was fixed in the package nova - 2012.2.1+stable-20121212
-a99a802e-0ubuntu1
---
nova (2012.2.1+stable-20121212-a99a802e-0ubuntu1) quantal-proposed; urgency=low
* Ubuntu updates:
- debian/control: Ensure novaclient is upgraded with nova,
require
This bug was fixed in the package cinder - 2012.2.1-0ubuntu1
---
cinder (2012.2.1-0ubuntu1) quantal-proposed; urgency=low
* Ubuntu updates:
- Cinder should suggest ceph-common, not python-ceph (LP: #1065901):
- debian/control: cinder-volume Suggests: python-ceph -
This bug was fixed in the package nova - 2012.2.1+stable-20121212
-a99a802e-0ubuntu1
---
nova (2012.2.1+stable-20121212-a99a802e-0ubuntu1) quantal-proposed; urgency=low
* Ubuntu updates:
- debian/control: Ensure novaclient is upgraded with nova,
require
** Tags removed: in-stable-folsom
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer access existing volumes.
To manage
** Tags removed: in-stable-folsom
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer access existing volumes.
To manage notifications about
** Branch linked: lp:ubuntu/quantal-proposed/nova
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer access existing volumes.
** Branch linked: lp:ubuntu/quantal-proposed/nova
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer access existing volumes.
To manage
Hello Adam, or anyone else affected,
Accepted nova into quantal-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/nova/2012.2.1+stable-20121212
-a99a802e-0ubuntu1 in a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello Adam, or anyone else affected,
Accepted nova into quantal-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/nova/2012.2.1+stable-20121212
-a99a802e-0ubuntu1 in a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello Adam, or anyone else affected,
Accepted cinder into quantal-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/cinder/2012.2.1-0ubuntu1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Branch linked: lp:ubuntu/quantal-proposed/cinder
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer access existing
Hello Adam, or anyone else affected,
Accepted cinder into quantal-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/cinder/2012.2.1-0ubuntu1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Branch linked: lp:ubuntu/quantal-proposed/cinder
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer access existing volumes.
To manage
** Changed in: nova (Ubuntu Raring)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer
** Changed in: nova (Ubuntu Raring)
Status: Confirmed = 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/1065702
Title:
After folsom upgrade, instances can no longer access
** Changed in: cinder/folsom
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer
** Changed in: nova/folsom
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer
** Changed in: cinder/folsom
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/1065702
Title:
After folsom upgrade, instances can no longer access existing
** Changed in: nova/folsom
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/1065702
Title:
After folsom upgrade, instances can no longer access existing
** Branch linked: lp:~openstack-ubuntu-testing/nova/precise-folsom
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer access
** Branch linked: lp:~openstack-ubuntu-testing/nova/precise-folsom
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer access existing
** Changed in: cinder
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer access
** Branch linked: lp:~openstack-ubuntu-testing/cinder/precise-folsom
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer access
** Changed in: cinder
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/1065702
Title:
After folsom upgrade, instances can no longer access existing volumes.
** Branch linked: lp:~openstack-ubuntu-testing/cinder/precise-folsom
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer access existing
** Changed in: nova/folsom
Milestone: None = 2012.2.1
** Changed in: cinder/folsom
Milestone: None = 2012.2.1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
** Changed in: nova/folsom
Milestone: None = 2012.2.1
** Changed in: cinder/folsom
Milestone: None = 2012.2.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom
** Also affects: cloud-archive
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer
** Changed in: cloud-archive
Importance: Undecided = High
** Changed in: cloud-archive
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
** Also affects: cloud-archive
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/1065702
Title:
After folsom upgrade, instances can no longer access existing
** Changed in: cloud-archive
Importance: Undecided = High
** Changed in: cloud-archive
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/1065702
Title:
After folsom
** Changed in: nova (Ubuntu Quantal)
Status: New = Confirmed
** Tags added: cloud-archive
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade,
** Changed in: nova (Ubuntu Quantal)
Status: New = Confirmed
** Tags added: cloud-archive
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no
** Branch linked: lp:~openstack-ubuntu-testing/nova/quantal-folsom-
proposed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no
** Branch linked: lp:~openstack-ubuntu-testing/nova/precise-folsom-
proposed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no
** Branch linked: lp:~openstack-ubuntu-testing/nova/quantal-folsom-
proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer access
** Branch linked: lp:~openstack-ubuntu-testing/nova/precise-folsom-
proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer access
Reviewed: https://review.openstack.org/15157
Committed:
http://github.com/openstack/cinder/commit/7f34ba39abcaa4f885d7448b427148fab4e49892
Submitter: Jenkins
Branch:stable/folsom
commit 7f34ba39abcaa4f885d7448b427148fab4e49892
Author: John Griffith john.griff...@solidfire.com
Date: Wed
** Branch linked: lp:~openstack-ubuntu-testing/cinder/quantal-folsom-
proposed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no
** Also affects: nova (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: cinder (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: nova (Ubuntu Raring)
Importance: High
Status: Confirmed
** Also affects: cinder (Ubuntu Raring)
Cinder Fix in Raring as of 2013.1~g1~20121101.361-0ubuntu1
** Also affects: cinder (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cinder (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Also affects: nova/folsom
Importance: Undecided
Status: New
** Changed in: nova
Status: In Progress = Invalid
** Changed in: nova/folsom
Status: New = Fix Committed
** Changed in: nova/folsom
Importance: Undecided = High
** Changed in: nova/folsom
Assignee:
Reviewed: https://review.openstack.org/15157
Committed:
http://github.com/openstack/cinder/commit/7f34ba39abcaa4f885d7448b427148fab4e49892
Submitter: Jenkins
Branch:stable/folsom
commit 7f34ba39abcaa4f885d7448b427148fab4e49892
Author: John Griffith john.griff...@solidfire.com
Date: Wed
** Branch linked: lp:~openstack-ubuntu-testing/cinder/quantal-folsom-
proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer access
** Also affects: nova (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: cinder (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: nova (Ubuntu Raring)
Importance: High
Status: Confirmed
** Also affects: cinder (Ubuntu Raring)
Cinder Fix in Raring as of 2013.1~g1~20121101.361-0ubuntu1
** Also affects: cinder (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cinder (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: nova/folsom
Importance: Undecided
Status: New
** Changed in: nova
Status: In Progress = Invalid
** Changed in: nova/folsom
Status: New = Fix Committed
** Changed in: nova/folsom
Importance: Undecided = High
** Changed in: nova/folsom
Assignee:
Reviewed: https://review.openstack.org/14790
Committed:
http://github.com/openstack/cinder/commit/524c7fa6dfade6efcabda19b105d58cab8c434e2
Submitter: Jenkins
Branch:master
commit 524c7fa6dfade6efcabda19b105d58cab8c434e2
Author: John Griffith john.griff...@solidfire.com
Date: Wed Oct 24
Reviewed: https://review.openstack.org/14790
Committed:
http://github.com/openstack/cinder/commit/524c7fa6dfade6efcabda19b105d58cab8c434e2
Submitter: Jenkins
Branch:master
commit 524c7fa6dfade6efcabda19b105d58cab8c434e2
Author: John Griffith john.griff...@solidfire.com
Date: Wed Oct 24
** Changed in: cinder
Milestone: None = grizzly-1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer access existing
** Changed in: cinder
Milestone: None = grizzly-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer access existing volumes.
To manage
** Changed in: cinder
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer access existing
** Changed in: cinder
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer access existing volumes.
To manage
** Changed in: nova (Ubuntu)
Status: New = Confirmed
** Changed in: nova
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After
Fix proposed to branch: master
Review: https://review.openstack.org/14615
** Changed in: nova
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
** Changed in: nova (Ubuntu)
Status: New = Confirmed
** Changed in: nova
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/1065702
Title:
After folsom upgrade,
Fix proposed to branch: master
Review: https://review.openstack.org/14615
** Changed in: nova
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
I used the block_device_mapping table to figure out what to rename.
Just throwing that out there for people who need to change their
existing volumes before a fix is put out.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in
I used the block_device_mapping table to figure out what to rename.
Just throwing that out there for people who need to change their
existing volumes before a fix is put out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: cinder
Assignee: (unassigned) = John Griffith (john-griffith)
** Changed in: nova
Assignee: (unassigned) = John Griffith (john-griffith)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
** Changed in: cinder
Assignee: (unassigned) = John Griffith (john-griffith)
** Changed in: nova
Assignee: (unassigned) = John Griffith (john-griffith)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ugh, this is nasty. Looks like we need a migration for this. For
backport we could add a translation using the ec2_id table to convert
from the old name to the new one. Some testing needs to be done to
figure out if the new iqns are actually there in all cases or if there
is a case where the old
** Also affects: cinder
Importance: Undecided
Status: New
** Changed in: cinder
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
** Tags added: openstack-ubuntu-upgrade
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer access existing volumes.
To manage
Looks like migrations for block_device_mapping:connection_info and
volumes:provider_location are the two that are missing. Looking at a
possible solution.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
ugh, this is nasty. Looks like we need a migration for this. For
backport we could add a translation using the ec2_id table to convert
from the old name to the new one. Some testing needs to be done to
figure out if the new iqns are actually there in all cases or if there
is a case where the old
** Also affects: cinder
Importance: Undecided
Status: New
** Changed in: cinder
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom
** Tags added: openstack-ubuntu-upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065702
Title:
After folsom upgrade, instances can no longer access existing volumes.
To manage notifications
Looks like migrations for block_device_mapping:connection_info and
volumes:provider_location are the two that are missing. Looking at a
possible solution.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
74 matches
Mail list logo
