weizhouapache commented on PR #13149:
URL: https://github.com/apache/cloudstack/pull/13149#issuecomment-4938415664

   > > @winterhazel @bernardodemarco @sureshanaparti is this a critical issue 
for 4.23 ?
   > 
   > @weizhouapache I don't think so, although it would be nice to fix it for 
4.23. I was only able to reproduce it by configuring valid username + password 
credentials for a profile in CMK, alongside an invalid API key.
   > 
   > ```sh
   > (test) 🐱 > set apikey 
WpsOEhOzpJHDlo-RM7yezDdj5I_0o10GsqwCa9SF8sW8VeGHXLUY0X2THwOHNR7mVWup02SpS6-7JdCJrGYtNw
   > Loaded in-built API cache. Failed to read API cache, please run 'sync'.
   > (test) 🐱 > set secretkey 
GRiS1DJ7ToI1r8bJ5VDdzCAx_KSrnfcr3GZeMLEm0bNdTSSOe852_wHW74YdER_7mbShn09D-E5NoYxejQ6t_Q
   > Loaded in-built API cache. Failed to read API cache, please run 'sync'.
   > (test) 🐱 > sync
   > Discovered 889 APIs
   > (test) 🐱 > set apikey 
WpsOEhOzpJHDlo-RM7yezDdj5I_0o10GsqwCa9SF8sW8VeGHXLUY0X2THwOHNR7mVWup02SpS6-7JdCJrGYtN
   > (test) 🐱 > sync
   > 🙈 Error: failed to authenticate, please check the credentials
   > (test) 🐱 > set username admin
   > (test) 🐱 > sync
   > 🙈 Error: failed to authenticate, please check the credentials
   > (test) 🐱 > set password password
   > (test) 🐱 > sync
   > 🙈 Error: (HTTP 530, error code 9999) Cannot invoke 
"org.apache.cloudstack.acl.apikeypair.ApiKeyPair.getAccountId()" because 
"apiKeyPair" is null
   > ```
   > 
   > Using either (1) only username + password, (2) only API key + secret key, 
(3) username + password + valid API key does not result in any exceptions.
   
   cool, thanks
   I actually tried these 3 cases but was not able to reproduce the issue.
   
   Since this is not a critical issue, 4.23 RC will not be blocked by it


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to