** Changed in: libvirt (Ubuntu)
Importance: Undecided => Low
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Triaged
** Also affects: libvirt via
https://bugzilla.redhat.com/show_bug.cgi?id=661262
Importance: Unknown
Status: Unknown
--
You received this bug notifica
https://bugzilla.redhat.com/show_bug.cgi?id=661262
** Bug watch added: Red Hat Bugzilla #661262
https://bugzilla.redhat.com/show_bug.cgi?id=661262
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
https://bugs.launc
Sure, will do.
For the record:
ebtables_cmd_path is set at start-up in ebiptablesDriverInit() and then checked
for null-ity before use in src/nwfilter/nwfilter_ebiptables_driver.c. An
indirection around ebtables_cmd_path would solve that. Alternatively, we could
restart libvirt when iptables/eb
I would assume this is also an issue with upstream libvirt. If so,
could you please open the task against upstream libvirt or raise the
issue there?
Either way, after you've figured that out, please report and set status
of the Ubuntu task appropriately.
** Changed in: libvirt (Ubuntu)
St
