server: apply network ACL even if there is no network ACLs rules in the ACL list#9374
Conversation
|
@blueorangutan package |
|
@weizhouapache 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. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## 4.19 #9374 +/- ##
============================================
- Coverage 15.07% 4.27% -10.81%
============================================
Files 5405 365 -5040
Lines 472672 29505 -443167
Branches 58189 5161 -53028
============================================
- Hits 71257 1261 -69996
+ Misses 393486 28101 -365385
+ Partials 7929 143 -7786
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
Packaging result [SF]: ✔️ el7 ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 10328 |
|
@blueorangutan test rocky8 kvm-rocky8 |
|
@weizhouapache a [SL] Trillian-Jenkins test job (rocky8 mgmt + kvm-rocky8) has been kicked to run smoke tests |
|
@weizhouapache there are unit test failures: https://github.com/apache/cloudstack/actions/runs/9893593560/job/27359418049?pr=9374#step:7:9300 can you have a look? |
|
[SF] Trillian test result (tid-10806)
|
kiranchavala
left a comment
There was a problem hiding this comment.
LGTM
- Create a vpc network
- Create a tier with default_deny acl rule
- create a new acl rule with no rules
- Replace the acl rule for the tier with the acl rule created in step 3
Before fix
2024-09-24T05:59:27,953 DEBUG [c.c.n.v.NetworkACLManagerImpl] (API-Job-Executor-36:[ctx-89b40bfe, job-46, ctx-65267911]) (logid:948cbd28) New network ACL is empty. Revoke existing rules before applying ACL
2024-09-24T05:59:27,957 DEBUG [c.c.n.v.NetworkACLManagerImpl] (API-Job-Executor-36:[ctx-89b40bfe, job-46, ctx-65267911]) (logid:948cbd28) Updated network: 205 with Network ACL Id: 4, Applying ACL items
2024-09-24T05:59:27,963 DEBUG [c.c.n.v.NetworkACLManagerImpl] (API-Job-Executor-36:[ctx-89b40bfe, job-46, ctx-65267911]) (logid:948cbd28) Applying NetworkACL for network: 205 with Network ACL service provider
2024-09-24T05:59:27,974 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-36:[ctx-89b40bfe, job-46, ctx-65267911]) (logid:948cbd28) Complete async job-46, jobStatus: SUCCEEDED, resultCode: 0, result: org.apache.cloudstack.api.response.SuccessResponse/null/{"success":"true"}
After fix
2024-09-24 05:53:06,552 DEBUG [c.c.n.v.NetworkACLManagerImpl] (API-Job-Executor-29:ctx-77843697 job-36 ctx-87af95cc) (logid:c829616e) New network ACL is empty. Revoke existing rules before applying ACL
2024-09-24 05:53:06,562 DEBUG [c.c.n.v.NetworkACLManagerImpl] (API-Job-Executor-29:ctx-77843697 job-36 ctx-87af95cc) (logid:c829616e) Releasing 2 Network ACL Items for network id=204
2024-09-24 05:53:06,564 DEBUG [c.c.n.v.NetworkACLManagerImpl] (API-Job-Executor-29:ctx-77843697 job-36 ctx-87af95cc) (logid:c829616e) Applying NetworkACL for network: 204 with Network ACL service provider
2024-09-24 05:53:06,586 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-29:ctx-77843697 job-36 ctx-87af95cc) (logid:c829616e) Complete async job-36, jobStatus: SUCCEEDED, resultCode: 0, result: org.apache.cloudstack.api.response.SuccessResponse/null/{"success":"true"}
Description
This PR fixes an issue with network ACL
expected:
default_deny)actual:
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?