locked
Wrong LeaseStatus with REST API RRS feed

  • Question

  • When using the REST API for blob Storage it seems that often it says the lease status on a block or page blob is 'locked' even though it really is (and behaves like it is) unlocked. For example, if it is saying it is unlocked, I aquire a lock and then release the lock... when I use the REST call to get the properties of the blob it still says locked. If I try to do something with the blob without using a lease ID it works fine, as it would when the blob is unlocked. This appears to be a bug in the Azure Server. Has anyone else seen this behavior? I can provide the URLs I am using to aquire and release the lock and populate the proeprties if that will help you, but I am quite sure there is nothing wrong with the URLs or how I am parsing the returned xml.

    Thanks in advance for your help!

    Thursday, August 26, 2010 9:41 PM

Answers

  • Brad Calder confirmed this to be a bug on a forum thread earlier this month.
    • Proposed as answer by Cybertron2008 Sunday, August 29, 2010 4:20 AM
    • Marked as answer by Mog Liang Friday, September 3, 2010 7:06 AM
    Thursday, August 26, 2010 10:05 PM
    Answerer

All replies

  • Brad Calder confirmed this to be a bug on a forum thread earlier this month.
    • Proposed as answer by Cybertron2008 Sunday, August 29, 2010 4:20 AM
    • Marked as answer by Mog Liang Friday, September 3, 2010 7:06 AM
    Thursday, August 26, 2010 10:05 PM
    Answerer
  • Great! Thanks for the link and your quick reply.
    Friday, August 27, 2010 3:57 AM