<fix>[flatNetwork]: delete namespace and dnsmasq when disabling DHCP (ZSTAC-78498)#3640
Open
ZStack-Robot wants to merge 1 commit into5.5.12from
Open
<fix>[flatNetwork]: delete namespace and dnsmasq when disabling DHCP (ZSTAC-78498)#3640ZStack-Robot wants to merge 1 commit into5.5.12from
ZStack-Robot wants to merge 1 commit into5.5.12from
Conversation
…without userdata service (ZSTAC-78498) When disabling DHCP service on an L3 network, if userdata service is not also enabled, the namespace and dnsmasq process should be deleted entirely. Previously the code always called flushDhcpConfig which only flushed DHCP config but kept the namespace alive (to avoid breaking shared userdata usage). Now it checks whether userdata is also enabled: if not, it calls deleteNameSpace to clean up dnsmasq and the network namespace completely.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: http://open.zstack.ai:20001/code-reviews/zstack-cloud.yaml (via .coderabbit.yaml) Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
功能概述
变更内容
代码审查难度评估🎯 3 (中等复杂) | ⏱️ ~20 分钟 庆贺诗
Important Pre-merge checks failedPlease resolve all errors before merging. Addressing warnings is optional. ❌ Failed checks (1 error, 1 warning)
✅ Passed checks (1 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
When DHCP service is disabled on an L3 network, the dnsmasq process and network namespace are not deleted. They remain running even after DHCP is disabled.
Root Cause
disableNetworkServiceinFlatDhcpBackendalways calledflushDhcpConfigwhich sends a "flush" command to kvmagent — this only clears DHCP config but intentionally keeps the namespace alive (to avoid breaking userdata if it shares the namespace). However, when userdata service is NOT enabled on the L3 network, there is no reason to keep the namespace, and it should be deleted.Fix
Check whether userdata service is also enabled on the L3 network before deciding what to do:
flushDhcpConfig(namespace shared with userdata, cannot delete)deleteNameSpace, which removes dnsmasq and the network namespaceFixes: ZSTAC-78498
sync from gitlab !9502