| Summary: | My VM lost network connection after I stopped firewalld service on the host machine | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | lnie <lnie> | ||||
| Component: | firewalld | Assignee: | Rashid Khan <rkhan> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 24 | CC: | jpopelka, lnie, twoerner | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-08-08 13:58:55 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
There is not a lot of information in this bug. What kind of VM?. Is libvirt used or not? kvm based VM with qemu(qemu-2.3.1-6.fc22.x86_64) and libvirt(libvirt-1.2.13.2-2.fc22.x86_64)used. I can reproduce this bug on f24/f23 guest system,with f23/f22 host machine,and the guest can not get the network connection whether I stop or start the firewalld on the guest,if I stop the firewalld on the host. This bus is reproducible on RHL7 guest with RHL7 host machine. It seems that the problem is the host can receive the guest's packets but fails to transmit it somehow.FYI,I choose the default 'NAT' for the network selection libvirt is creating firewall rules to make the guest accessible. If libvirt detects firewalld while it is starting, it will use firewalld. If firewalld is not detected, it uses iptables. libvirt is not switching from firewalld to iptables or back if firewalld has been started or stopped. If you are stopping firewalld while libvirt is using it, there are no firewall rules of libvirt anymore and libvirt will not create new rules again till firewalld has been started again. I am sorry there is not a lot that can be done in firewalld to change the behaviour of libvirt. The only thing that could be done in firewalld is to turn off CleanupOnExit in the firewalld configuration. Then the rule set will stay as is when it has been stopped. But there will also not be any further change to the rule set by libvirt, till either firewalld is started again or till libvirt has been is restarted to switch to iptables use then. This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Created attachment 1137733 [details] video Description of problem: Version-Release number of selected component (if applicable): firewalld-0.3.14.2-4.fc22(23).noarch How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: