You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by GitBox <gi...@apache.org> on 2019/05/10 14:40:34 UTC
[GitHub] [cloudstack] glennwagner opened a new issue #3327: Volume name for
failed and successful snapshots
glennwagner opened a new issue #3327: Volume name for failed and successful snapshots
URL: https://github.com/apache/cloudstack/issues/3327
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and master branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Feature Idea
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
API, UI
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on master branch.
-->
~~~
4.11.2
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network, advanced networking, etc. N/A otherwise
-->
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
##### SUMMARY
<!-- Explain the problem/feature briefly -->
We would like to see additional information such as Volume name, supplied for events related to failed/successful snapshots so that these messages are distinguishable.
e.g. the customer would like to see the Volume name for failed and successful snapshots:
+--------------------------------------------------------------------+
| description |
+--------------------------------------------------------------------+
| Successfully completed taking snapshot |
| Error while taking snapshot |
| creating snapshot for volume: fcc93103-605f-493a-882b-2d0fbd239a11 |
+--------------------------------------------------------------------+
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
Create a Volume Snapshot in the UI or API
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
e.g. the customer would like to see the Volume name for failed and successful snapshots:
+--------------------------------------------------------------------+
| description |
+--------------------------------------------------------------------+
| Successfully completed taking snapshot |
| Error while taking snapshot |
| creating snapshot for volume: fcc93103-605f-493a-882b-2d0fbd239a11 |
+--------------------------------------------------------------------+
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
~~~
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services