[one-users] ec2 access problem after upgrading to ONE 3.0
Schwickerath Ulrich
ulrich.schwickerath at cern.ch
Tue Oct 11 00:10:49 PDT 2011
Some more information:
I've captured additional information from my customers client tools.
I see the problem for example if I call the describeImages method of the client object, with the following arguments:
$response = $self->{service}->describeImages($request);
where $self looks like
$VAR1 = bless( {
'service' => bless( {
'_config' => {
'ProxyPort' => -1,
'ProxyHost' => undef,
'ServiceURL' => 'https://mycloudentrypoint.cern.ch:8443/',
'UserAgent' => 'Amazon EC2 Perl Library',
'SignatureVersion' => 2,
'SignatureMethod' => 'HmacSHA256',
'MaxErrorRetry' => 3
},
'_xml_parser' => bless( {
'_State_' => 0,
'XML_LIBXML_PARSER_OPTIONS' => 528390
}, 'XML::LibXML' ),
'_xslt_parser' => bless( {}, 'XML::LibXSLT' ),
'_awsSecretAccessKey' => 'my ONE SHA1 access key',
'_awsAccessKeyId' => 'my ONE user name'
}, 'Amazon::EC2::Client' )
}, 'Cloud' );
and $request as mentioned earlier
$VAR1 = {
'Filter' => {
'FieldValue' => [],
'FieldType' => [
'Amazon::EC2::Model::Filter'
]
},
'Owner' => '392941794136',
'ImageId' => undef,
'ExecutableBy' => undef
};
(The owner looks odd to me. I tried to undefine it without success, and if I put my ONE user name there it does not change anything either)
Any idea ?
Thanks a lot!
More information about the Users
mailing list