please backport cinderclient 1.0.4 to raring
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| raring-backports |
Fix Released
|
Wishlist
|
Edward Hope-Morley | ||
Bug Description
The Cinder backup service was released in the Grizzly cycle and is supported in the Ubuntu Grizzly cloud archive but the corresponding cinderclient support did not make it into the archive. The cinderclient 1.0.4 which contains the backup support will be backported to the cloud archive to replace 1.0.3.
[Impact]
* This backport adds cinder backup support to the python-cinderclient used in
the Grizzly cloud archive.
[Test Case]
* 1. Fire up a devstack instance
2. Start cinder-backup service with Ceph or Swift as backend
3. Create a cinder volume 'cinder create 1'
4. Check status is available 'cinder list'
5. Create a backup 'cinder backup-create <volid>'
6. Check backup status is createing/available 'cinder backup-list'
* I have tested this on Raring using the above test.
[Regression Potential]
* This issue is not expected to introduce any regression. The test case above
has been tested.
Related branches
| tags: | added: cloud-archive |
| Seif Lotfy (seif) wrote | #1 |
| Tomokazu Hirai (tomokazu-hirai) wrote | #2 |
| Changed in python-cinderclient: | |
| assignee: | nobody → Edward Hope-Morley (hopem) |
| status: | New → Fix Committed |
| description: | updated |
| Changed in python-cinderclient: | |
| status: | Fix Committed → In Progress |
| Changed in python-cinderclient: | |
| status: | In Progress → Fix Committed |
| Changed in python-cinderclient: | |
| status: | Fix Committed → In Progress |
| affects: | ubuntu → python-cinderclient (Ubuntu) |
| Changed in python-cinderclient (Ubuntu): | |
| status: | New → In Progress |
| assignee: | nobody → Edward Hope-Morley (hopem) |
| Changed in python-cinderclient (Ubuntu): | |
| milestone: | none → raring-updates |
| Scott Kitterman (kitterman) wrote Re: [Bug 1191848] [NEW] cinder backup needs be backported to grizzly cinderclient | #3 |
| Edward Hope-Morley (hopem) wrote Re: cinder backup needs be backported to grizzly cinderclient | #4 |
| Changed in raring-backports: | |
| status: | New → In Progress |
| assignee: | nobody → Edward Hope-Morley (hopem) |
| no longer affects: | raring-backports |
| no longer affects: | python-cinderclient |
| summary: |
- cinder backup needs be backported to grizzly cinderclient + backport cinderclient 1.0.4 to raring |
| description: | updated |
| no longer affects: | python-cinderclient |
| Changed in raring-backports: | |
| assignee: | nobody → Edward Hope-Morley (hopem) |
| status: | New → In Progress |
| summary: |
- backport cinderclient 1.0.4 to raring + please backport cinderclient 1.0.4 to raring |
| Scott Kitterman (kitterman) wrote | #5 |
| Changed in python-cinderclient (Ubuntu): | |
| milestone: | raring-updates → none |
| no longer affects: | python-cinderclient (Ubuntu) |
| Changed in raring-backports: | |
| importance: | Undecided → Wishlist |
| status: | In Progress → New |
| Scott Kitterman (kitterman) wrote | #6 |
| Edward Hope-Morley (hopem) wrote | #7 |
| Changed in raring-backports: | |
| status: | New → Confirmed |
| Scott Kitterman (kitterman) wrote | #8 |
| Scott Kitterman (kitterman) wrote | #9 |
| Changed in raring-backports: | |
| status: | Confirmed → Fix Released |
I was able to backport it easily (applying only one commit from master is needed)... How do i proceed?