Don't specify ipv6 ranges for shared network#10746
Don't specify ipv6 ranges for shared network#10746weizhouapache merged 3 commits intoapache:4.19from
Conversation
|
@blueorangutan package |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## 4.19 #10746 +/- ##
=========================================
Coverage 15.17% 15.17%
- Complexity 11333 11334 +1
=========================================
Files 5415 5415
Lines 474911 474912 +1
Branches 57926 57926
=========================================
+ Hits 72050 72051 +1
+ Misses 394806 394804 -2
- Partials 8055 8057 +2
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:
|
weizhouapache
left a comment
There was a problem hiding this comment.
code lgtm
@DaanHoogland
can you remove the comment ?
alternatively, we can add a INFO message instead of throwing an exception
|
@blueorangutan package |
|
@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 13147 |
|
@blueorangutan test |
|
@weizhouapache a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
|
[SF] Trillian test result (tid-13107)
|
|
It seems one of the hosts is left in an undesired state by a prior test and so
@weizhouapache @Pearl1594 , I think we can call this success. |
agree. let's merge ? |
|
[SF] Trillian test result (tid-13122)
|
* assume SLAAC takes care * log info * Update server/src/main/java/com/cloud/network/NetworkServiceImpl.java --------- Co-authored-by: Wei Zhou <weizhou@apache.org>
Description
This PR... addresses the comments at https://github.com/apache/cloudstack/pull/10704/files#r2048392976
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?