| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Congratulations on your first Pull Request and welcome to the Apache CloudStack community! If you have any issues or are unsure about any anything please check our Contribution Guide (https://github.com/apache/cloudstack/blob/main/CONTRIBUTING.md)
|
Sorry, something went wrong.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files @@ Coverage Diff @@
## main #9079 +/- ##
============================================
- Coverage 16.07% 4.01% -12.07%
============================================
Files 5642 394 -5248
Lines 494087 32406 -461681
Branches 59931 5726 -54205
============================================
- Hits 79425 1301 -78124
+ Misses 405844 30957 -374887
+ Partials 8818 148 -8670
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry.
|
Sorry, something went wrong.
There was a problem hiding this comment.
clgtm
Sorry, something went wrong.
|
Is there something I should do to get this progressed? If there are any concerns, please let me know. Thanks. |
Sorry, something went wrong.
|
@JSpon , well, you could find a 3rd party tester and a second reviewer. the rules are two reviews of which one did a test. I'll at least run some regression tests. also see https://github.com/apache/cloudstack/actions/runs/9072065551/job/25241922319?pr=9079#step:7:5497 |
Sorry, something went wrong.
|
@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. |
Sorry, something went wrong.
|
Packaging result [SF]: ✔️ el7 ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 9777 |
Sorry, something went wrong.
|
@DaanHoogland a [SL] Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
Sorry, something went wrong.
|
[SF] Trillian test result (tid-10344)
|
Sorry, something went wrong.
…d/kubernetes/cluster/actionworkers/KubernetesClusterActionWorker.java Co-authored-by: dahn <daan.hoogland@gmail.com>
|
@rohityadavcloud 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. |
Sorry, something went wrong.
|
Packaging result [SF]: ✖️ el8 ✖️ el9 ✖️ debian ✖️ suse15. SL-JID 10943 |
Sorry, something went wrong.
…d/kubernetes/cluster/actionworkers/KubernetesClusterActionWorker.java
|
@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. |
Sorry, something went wrong.
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 10949 |
Sorry, something went wrong.
… have the same primitive value
There was a problem hiding this comment.
What cerconstances are those @JSpon ? as both network.getVpcId() and address.getVpcId() return an object of type Long, this should work with the Long.equals() method.
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
It seems that the issue was already fixed on 4.20.0+ with #8906, but it wasn't ported to 4.19.
@JSpon, could you target 4.19 and backport the code from main?
@winterhazel that to me doesn't look like the code that is in this PR. I still think 4.20+ needs this change. Unless I'm looking at it wrong.
I'm basically just looking at this file, since this is the file I changed and re-compiled and deployed and it worked for me. plugins/integrations/kubernetes-service/src/main/java/com/cloud/kubernetes/cluster/actionworkers/KubernetesClusterActionWorker.java
#8906 shows these changes which is different from above.

Sorry, something went wrong.
There was a problem hiding this comment.
@CodeBleu network.getVpcId() == null || address.getVpcId() == null || network.getVpcId().longValue() != address.getVpcId().longValue() (the changes in this PR) and !Objects.equals(network.getVpcId(), address.getVpcId()) (the existing code in main and 4.20) will have the same result here.
See the code in the 4.19 branch, its comparing the Long objects instead, resulting in the issue that the comment mentions:
Sorry, something went wrong.
|
This pull request has merge conflicts. Dear author, please fix the conflicts and sync your branch with the base branch. |
Sorry, something went wrong.
|
@JSpon @DaanHoogland FYI - I was able to take this code change and build it into a .jar file and run it on the management server and was also able to successfully create the K8S cluster in the VPC |
Sorry, something went wrong.
I would say that sounds as a successful test ;) There is a conflict @JSpon , could you resolve that. Also de we feel this needs to go on another release branch than main? (i.e. 4.19 or 4.20?) |
Sorry, something went wrong.
if the issue exists in 4.19 or 4.20, it would be better to rebase with 4.19/4.20 |
Sorry, something went wrong.
|
hi @JSpon please resolve the conflicts. |
Sorry, something went wrong.
|
@JSpon can you address the conflicts on this please? @DaanHoogland what is the status of this. I was looking into creating CKS cluster in a VPC again and noticed this is now in Draft. Isn't this what is needed to be able to deploy a CKS cluster in a VPC? What is the minimum version of Cloudstack this will be in? CC: @harikrishna-patnala ( I see you changed the milestone on this, so maybe you have some insight into this as well? ) |
Sorry, something went wrong.
Depending on the branch the conflict will be resolved against?! I suppose 4.22 is good. It needs work though (hence the draft status)
@harikrishna-patnala changed the milestone to the minor version following the one that was just released, @CodeBleu . Just an administrative action on his part, no policy decision. |
Sorry, something went wrong.
|
@JSpon Since this is for the 4.22.1 release, could you retarget the PR to the 4.22 branch? |
Sorry, something went wrong.
|
@JSpon , it seems this never got the attention it needed. I am closing it. Can you re-evaluate and re-open if needed? |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Description
This PR...
fixes a bug that compares two Long objects, instead of their primitives. The comparison of two Long objects with the same underlying long value returned as not equal, throwing an error even though the public IP address was correctly assigned to the VPC associated with the guest network. This issue does not occur when comparing the primitives.
When this issue occurs, any cluster using a guest network in a particular VPC will always throw the error.
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
In a test environment, any attempt to create a CKS cluster on a specific VPC always returned the error "Public IP with ID: ... linked to the Kubernetes cluster: ... is not usable". The public IP address was correctly attached, and debugging showed that they had the same long value. The code was compiled with this update and put in a jar earlier in the classpath, and the CKS cluster was created successfully.
How did you try to break this feature and the system with this change?