Bug 628956
Summary: | augeas crashes when trying to run libvirtd | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Richard Hughes <rhughes> |
Component: | augeas | Assignee: | David Lutterkort <lutter> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 14 | CC: | apevec, hbrock, laine, lutter, mbooth, satellitgo |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-08-16 22:06:17 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Richard Hughes
2010-08-31 14:07:19 UTC
I can't reproduce this on my F13 machine. I'll set up a F14 VM and see if I can reproduce it there. There's two things I don't quite understand from the stacktrace: (1) /proc/sys/net/bridge/bridge-nf-call-iptables must be set to 1, otherwise the code would never get there (2) in the stacktrace, the arguments for dict_pos are in the wrong order, though seem to have the right values - might be some gdb hickup This is just aside-issue, but I just updated my F14 box and noted that after a reboot, although /etc/sysctl.conf has: net.bridge.bridge-nf-call-iptables = 0 /proc/sys/net/bridge/bridge-nf-call-iptables contains "1". It appears some process is modifying this setting without updating /etc/sysctl.conf. (ncftool started successfully for me, at least on this first run). *** Bug 636595 has been marked as a duplicate of this bug. *** This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |