Github user koushik-das commented on the issue:
https://github.com/apache/cloudstack/pull/1812
@rhtyd Sure will let you know if trillian tests are needed. In this case XS
test results were already there from @cloudmonger. I used the git-pr script but
not sure why the merge commit
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1812
@koushik-das You could have pinged me to run tests on Trillian with
xen/vmware/kvm to confirm that no regressions were made. Also when you use
git-pr, the git-merge commit does not have
Github user koushik-das commented on the issue:
https://github.com/apache/cloudstack/pull/1812
Looks like this is ready for merge. None of the test failures are related
to this PR.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user cloudmonger commented on the issue:
https://github.com/apache/cloudstack/pull/1812
### ACS CI BVT Run
**Sumarry:**
Build Number 202
Hypervisor xenserver
NetworkType Advanced
Passed=98
Failed=7
Skipped=7
_Link to logs Folder
Github user wido commented on the issue:
https://github.com/apache/cloudstack/pull/1812
Ok, understood. Get it.
Based on the code changes: LGTM
---
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
Github user koushik-das commented on the issue:
https://github.com/apache/cloudstack/pull/1812
OOM on HV won't happen, only cluster threshold check is skipped in case of
starting a stopped VM
---
If your project is set up for it, you can reply to this email and have your
reply
Github user wido commented on the issue:
https://github.com/apache/cloudstack/pull/1812
So to get this clear, you might OOM hypervisors due to this since you
allocate more memory on them?
Or is this just the cluster threshold and it still might not find a
suitable hypervisor
