Fix update resource count failure for domains#11138
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## 4.20 #11138 +/- ##
============================================
+ Coverage 16.16% 16.23% +0.07%
- Complexity 13278 13328 +50
============================================
Files 5657 5657
Lines 497969 498663 +694
Branches 60389 60650 +261
============================================
+ Hits 80472 80945 +473
- Misses 408531 408726 +195
- Partials 8966 8992 +26
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@blueorangutan package |
|
@DaanHoogland a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 14031 |
|
@DaanHoogland a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. |
|
UI build: ✔️ |
|
when updating resource count for a child domain it fails. I think this is not what solves the issue at hand/needs more investigation. |
|
The regression was introduced by commit a0080a0 as the Perhaps ensuring that |
no, I think an accountid should not be obligatory when updating limit counts on a domain. But a null check (and making the code you point to not be called if it is null) would seem in order. |
Yes, that's what I meant. My last comment was a bit ambiguous, sorry 😁 |
9d01e3b to
84577e8
Compare
| if (accountId != null) { | ||
| Account account = _entityMgr.findById(Account.class, accountId); | ||
| if (account == null) { | ||
| throw new InvalidParameterValueException("Unable to find account " + accountId); | ||
| } | ||
| _accountMgr.verifyCallerPrivilegeForUserOrAccountOperations(account); | ||
| } | ||
| _accountMgr.verifyCallerPrivilegeForUserOrAccountOperations(account); | ||
|
|
There was a problem hiding this comment.
this is the essential change. @Pearl1594 @hsato03 , can you have a look?
|
Pearl1594
left a comment
There was a problem hiding this comment.
lgtm. Tested fix. Works as expected. Thanks @DaanHoogland
|
hey @Pearl1594 , I believe I found a bug that is related to this one. Are you able to confirm if this fix resolves the issue below: On our NON-Prod environment environments that are on ACS 4.21.0, the following command works. But on our Prod environment, that is on ACS 4.20.1 the same command fails with the following output. |
Thanks @daviftorres - will check it out. This wasn't tested with the moveDomain API - something may have been overlooked. |


Description
This PR fixes: #11100
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
How did you try to break this feature and the system with this change?