[GitHub] cloudstack issue #1949: Cruds2
Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/1949 Thank you @shwetaag can you please edit the PR description --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1949: Cruds2
Github user shwetaag commented on the issue: https://github.com/apache/cloudstack/pull/1949 @borisstoyanov This PR is about automating these 8 cloudstack bugs. automated these 8 test bugs 9277 9276 9275 9274 9273 9179 9178 9177 - Test to verify Scale CentOS7 VM does not fails with error "Cannot scale up the vm because of memory constraint violation" - Test to verify Private template is visible in project - Test to verify attaching 7th Disk to windows server 2012R2 instance - API listVMSnapshot returns value for tags âprojectâ and âprojectidâ when called with project id param - 'listProjects' doesn't return tags 'vmstopped' or 'vmrunning' when their value is zero - Verify register ssh key pair can not be used to register same ssh keys with different name - Verify correct Guest OS (RHEL 7) Mapping for vmware - Atomation of Usage events for "uploadedVolume" the details of these bugs can be seen in related bugs --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1949: Cruds2
Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/1949 @shwetaag Hi, I'm sorry but I don't get what is this PR for? Are these some internal issues that you're referring to? Each PR should start with an ACS JIRA ticket number and should be followed by a description of what it is about. I've noticed you're committing some tests, can you please give an overview what are they about. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
