-
Notifications
You must be signed in to change notification settings - Fork 1.3k
VR: fix dns list in redundant VPC VRs #12161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: 4.22
Are you sure you want to change the base?
VR: fix dns list in redundant VPC VRs #12161
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## 4.22 #12161 +/- ##
============================================
+ Coverage 17.59% 17.78% +0.18%
- Complexity 15601 15923 +322
============================================
Files 5910 5911 +1
Lines 529780 539168 +9388
Branches 64729 68896 +4167
============================================
+ Hits 93226 95873 +2647
- Misses 426060 432683 +6623
- Partials 10494 10612 +118
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 |
|
@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. |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 15857 |
|
@blueorangutan test |
|
@weizhouapache a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
|
This patch worked for me. |
|
@blueorangutan test |
|
@weizhouapache a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
f5b4060 to
e5d7cf2
Compare
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 15869 |
|
[SF] Trillian test result (tid-14892)
|
|
@weizhouapache , does this need testing for non-vpc non-redundant routers? cc @nvazquez @Pearl1594 . |
yes @DaanHoogland the change was introduced in #9102, but may be related to the Netris plugin too (#10458) |
|
I just hit the below error trying to deploy an instance with this fix in place. 169.254.39.227 is the current BACKUP VPC router. Will try to debug further. Upon second deployment attempt, it tried the PRIMARY router and also failed. hmm. |
@Jayd603 can you run the following commands inthe VPC VR ? |
I noticed I used tabs in the python file, durr, fixed that now other errors: I fixed the .py files and attempted router reboot - totally fails now. also - that file you pasted does not exist. I'm re-deploying fresh routers without your patch - after that, other than modifying the .py files on each router, what else do I need to do to test this? |
After deploying fresh routers, i was able to apply your patch and reboot them both, then was able to deploy with password functionality. Not sure what happened but seems ok now . I'm doing more testing and will report back if I notice anything. |
good, good to know it. |
|
@blueorangutan package |
|
verified by |
|
@blueorangutan package |
|
@Pearl1594 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 ✔️ el10 ✖️ debian ✔️ suse15. SL-JID 16537 |
Pearl1594
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It appears to work as intended, adding the VPC tier gateway to the DNS list in /etc/dnsmasq.d/cloud.conf for both standard and redundant VPC setups. However, for redundant VPCs, only the primary VR includes the tier gateway in the DNS line. When I stop the primary VR and the backup becomes primary, the VPC tier gateway is no longer present in the dhcp-option line for DNS. I'm not sure if that's expected behaviour.
Also, regarding a comment on this possibly impacting NSX - it may not, as we have a parameter when creating a VPC network using NSX provider - userouteripresolver - which when set to true, uses the VR IP as nameserver, otherwise uses DNS1 and DNS2" cc @nvazquez
|
can you have a look how to make it working with both nsx/netris and regular vpc ? I think the 4.19 code works for regular vpc cloudstack/systemvm/debian/opt/cloud/bin/cs/CsDhcp.py Lines 110 to 120 in a208db5
closing this PR |
|
this fix partly work @weizhouapache - I only had a confusion regarding redundant VRs - when the backup VR becomes the primary one, it doesn't have the tier gateway in the dns list. |
@Pearl1594 |
|
I think I made a mistake while testing - my bad, I had copied the cloud-scripts.tgz and agent.zip files to the hosts and tested it (on an existing env), while one of the VRs had the fix, the other didn't, leading the the discrepancy I observed. On testing on an env built from this PR - it works as expected. Apologies @weizhouapache. I'm re-opening this PR. |
Pearl1594
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tested - lgtm
|
@blueorangutan test |
|
@Pearl1594 a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
Description
This PR fixes: #12107 #11879
Step to reproduce the issue
expected: VPC tier gateway as the first option in the line for DNS
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?