resource limit: Fix resource limit check on VM start#5428
Conversation
|
@blueorangutan package |
|
@Pearl1594 a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 1195 |
|
@blueorangutan test |
|
@Pearl1594 a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
Trillian test result (tid-1999)
|
|
@blueorangutan package |
|
@Pearl1594 a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✖️ el7 ✖️ el8 ✖️ debian ✖️ suse15. SL-JID 1213 |
|
@blueorangutan package |
|
@Pearl1594 a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✖️ el7 ✖️ el8 ✖️ debian ✖️ suse15. SL-JID 1216 |
|
@Pearl1594 |
|
Thanks for the review @weizhouapache I'll address your comments and have a look at the component test. |
|
@blueorangutan package |
|
@Pearl1594 a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 1336 |
|
@blueorangutan test |
|
@sureshanaparti a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
@Pearl1594 the resource limit test in travis job 15 failed. I restarted it, can you keep an eye on it? |
|
Sure @DaanHoogland - will keep an eye on it - seems like the following set of tests from that job are failing across other PRs too |
@Pearl1594 |
|
Alright @DaanHoogland Thanks! |
|
@Pearl1594 |
|
|
Trillian test result (tid-2139)
|
|
@blueorangutan package |
|
@Pearl1594 a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 1369 |
|
@blueorangutan test |
|
@Pearl1594 a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
Trillian Build Failed (tid-2176) |
|
@blueorangutan test |
|
@sureshanaparti a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
Trillian test result (tid-2178)
|
Description
This PR addresses #4155 - wherein resource limits for an account aren't checked when a VM's settings i.e., cpuNumber / memory are updated i.e., VM deployed with custom constrained compute offering.
Types of changes
Feature/Enhancement Scale or Bug Severity
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
Set resource limit to a low value for domain admin:

Deployed a VM using custom constrained compute offering with cpuNumber = 1 and memory = 100MB

Updated VM settings with cpuNumber = 4 (max = 2) - Failed as expected:

Updated VM settings with memory = 1200 (max = 1000) - Failed as expected:

When VM settings for cpuNumber / memory is updated to a value exceeding the limit of the custom service offering used - Fails - check added to verify limits during vm update:
