[
https://issues.apache.org/jira/browse/JCLOUDS-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16474409#comment-16474409
]
Felix Otto commented on JCLOUDS-1132:
-------------------------------------
Thanks for your email. I'm out of office from May 5th until May 27th.
I might not be able to read your emails during this days. They will not be
forwarded.
Best regards
Felix Otto
evosoft GmbH
Business Function Application & Platform Solutions
Marienbergstr. 76-82
90411 Nuernberg, Deutschland
Telefon: +49 (911) 53991-0
mailto:[email protected]<mailto:[email protected]>
www.evosoft.com<http://www.evosoft.com/>
evosoft GmbH: Sitz der Gesellschaft: Nürnberg
Handelsregister: HRB 13657 Amtsgericht Nürnberg
Geschäftsführer: Ekkehard Reuß, Marcus Bernatzky
Wichtiger Hinweis: Diese E-Mail und etwaige Anlagen enthalten
firmenvertrauliche Informationen. Sollten Sie diese E-Mail irrtümlich erhalten
haben, benachrichtigen Sie uns bitte durch Antwort-Mail und löschen Sie diese
E-Mail nebst Anlagen von Ihrem System. Vielen Dank.
> Amazon AWS - Create Volume - query params reported as unrecognized
> ------------------------------------------------------------------
>
> Key: JCLOUDS-1132
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1132
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-compute
> Affects Versions: 1.9.0, 1.9.2
> Environment: Amazon AWS EC2 management console
> Reporter: Tusa Mihail Cristian
> Priority: Major
>
> Let say that I want to create a Volume that is encrypted. So, I set the
> encrypted on "true"... in request query params apear "&Encrypted=true". In
> this case the error that I got is:
> <Response><Errors><Error><Code>UnknownParameter</Code><Message>The parameter
> Encrypted is not
> recognized</Message></Error></Errors><RequestID>c874434a-b00e-425d-baf4-18087441603a</RequestID></Response>
>
> instead it should be: "&Encrypted=1" as it is shown in Amazon docs:
> http://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateVolume.html
> in Example/Sample request. The problems are also related with Volume Type. If
> not specified than creates a standard volume but if anything specified (any
> of valid Values: standard | io1 | gp2 | sc1 | st1 ) the same error with
> unrecognized param is received.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)