[
https://issues.apache.org/jira/browse/CLOUDSTACK-691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13540325#comment-13540325
]
Pranav Saxena commented on CLOUDSTACK-691:
------------------------------------------
I also verified this issue on the latest asf/master branch and agree with Isaac
that this issue happens irrespective of the fact that you enable s3 or not . I
also realised that whatever I have stated in my previous comment is the reason
behind this issue. I think John is working on the backend code for S3 and he
needs to confirm on the listS3s API call behavior . Without the id not being
supplied in the API call , that error would throw up on the UI .
I am assigning this ticket to John for the meantime to have a look at the
behavior . Also John could you please confirm how would the S3s be listed on
the dashboard ? Do you plan to show it through Capacity Charts.
> A warning dialog box shows after reloading the welcome page
> -----------------------------------------------------------
>
> Key: CLOUDSTACK-691
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-691
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
> Environment: master branch
> Reporter: Isaac Chiang
> Assignee: Pranav Saxena
> Priority: Minor
> Labels: ui
> Attachments: screenshot-1.jpg
>
>
> Reproduce step:
> 1. Clean up the database and restart a new CloudStack
> 2. Login as the administrator
> 3. Reload the welcome page
> 4. A Warning dialog box shows with content "Unable to execute API command
> lists3s due to missing parameter id"
--
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
