Found it! these folks ran accross the same issue. Looks like taking SQL resource offline from cluster administrator first does the trick.
http://www.sqlservercentral.com/Forums/Topic485250-357-1.aspx#bm485257
Todd Carrier
MCITP - Database Administrator (SQL 2008)
MCSE: Data Platform (SQL 2012)