Backend Cred Test of encrypted credential fails

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Visit /yabiadmin/admin/backend_cred_test/8/ for an encrypted credential
2. Internal Server Error
3.

We need to make this display a message explaining the inability to decrypt 
credential.

Original issue reported on code.google.com by amacgregor on 9 Sep 2011 at 1:58

[GoogleCodeExporter]

when going to that uri (with /backend_cred_test) get a 404 Page not found.

Can't replicate this.

Downgrading status from Accepted to New.

Original comment by retrogra...@gmail.com on 2 Nov 2011 at 3:51

• Changed state: New

[GoogleCodeExporter]

This is definitely valid.
1. Make sure you have an encrytped cred
2. Make sure that cred is purged from cache
3. Visit Admin->Users and click on Backends.
4. Click Test for the filesystem that uses that cred.

{{{
Exception Type: DecryptedCredentialNotAvailable
Exception Value:    
Credential for yabiuser: ************ id: ************ is not available in a 
decrypted form
Exception 
Location:   /usr/local/python/ccgapps/yabiadmin/snapshot/yabiadmin/yabi/models.py 
in get, line 519
}}} 

Original comment by amacgregor on 2 Nov 2011 at 5:31

• Changed state: Accepted

[GoogleCodeExporter]

It also fails if you try to test and the directory listed in the backend cred 
does not exist. It should return sensible error to (admin) user.

Original comment by amacgregor on 6 Feb 2012 at 7:07

[GoogleCodeExporter]

It would be helpful if this also would work if the creds are "protected". This 
would mean that when adding a user you can test their setup before they have 
logged in.

Original comment by amacgregor on 27 Feb 2012 at 3:03

[GoogleCodeExporter]

This last bit (part 4) of using protected creds when available is now 
implemented. But if we dont have a decrypted cred, theres nothing we can do! 
I've improved the error screen on the credential test section. This is about 
the most we can do. Gonna close this ticket. If more needs to be done, reopen.

relevant revs on next_release: fd018286b38f, c3b6293905c6, 03d2b820ca45 

Original comment by retrogra...@gmail.com on 29 May 2012 at 6:06

• Changed state: Fixed