[
https://issues.apache.org/jira/browse/CLOUDSTACK-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13694402#comment-13694402
]
Thomas O'Dowd commented on CLOUDSTACK-3205:
-------------------------------------------
> From you point of view, do you see admin will delete/add S3 often?
I can imagine wanting to change vendors perhaps? Maybe, move off to swift to s3
or vice versa, or even within s3 to move to a different vendor. It won't happen
often I guess...
How can I delete the S3 store manually? I looked at the templates and I can't
delete the other two templates using the GUI. I'm trying to test 2 different
stores (Amazon and Cloudian) and don't want the other store available while I'm
checking either one of them. Only way I can do it now is to redo my database
and redeploy which takes a lot of time but at least I get a clean state.
> Object_Store_Refactor - unable to delete S3 Secondary Storage
> -------------------------------------------------------------
>
> Key: CLOUDSTACK-3205
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3205
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.2.0
> Environment: chrome on linux
> devcloud
> Reporter: Thomas O'Dowd
>
> 1. Navigate to infrastructure, secondary storage.
> 2. Delete the NFS secondary storage
> 3. Add an S3 Object Storage
> 4. Navigate to Templates
> 5. Register a new Template
> 6. Remove the template
> 7. Navigate to infrastructure, secondary storage
> 8. try remove the S3 storage.
> I get a pop up which tells me I can't remove it. I haven't got the error in
> front of me now as unfortunately started to deploy a new one so that I could
> do more testing. I think I'm out of time today, but I'll find the error again
> tomorrow and update this bug. It was something about not being able to delete
> a storage with active templates. However, I deleted the template updated in
> step 5 in step 6. I could remove the NFS secondary storage, so I'm curious
> why I couldn't remove the S3 one.
> In the meantime, is this expected behaviour and if so how do I remove the S3
> storage and use a different one instead. I also tried adding another S3 store
> and then removing this one but the same error happens.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
