© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
While I agree this may not be ideal, it does mean it breaks any APIs that expectt that fault name. I don't see any harm in just keeping it as is, and maybe in the next rev we can redo fault names if needed. The current OpenStack API implementation should keep it for backwards compatibility.