© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
The proposed fix only partially solves the problem since. It does prevent the volume from entering the 'available' state but I notice that the volume now stays in 'creating' state indefinitely. I presume we would want the volume to go to 'error' after a finite number of re-schedules?