Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
net-event should not report unsuccessful event
Version-Release number of selected component (if applicable):
libvirt-1.2.8-6.el7.x86_64
How reproducible:
100%
Steps:
1.prepare a virtual network
# virsh net-list --all
Name State Autostart Persistent
----------------------------------------------------------
default active yes yes
2.# virsh net-event net4 lifecycle --loop
3.open another terminal
[root@localhost lhaung]# virsh net-start default
error: Failed to start network default
error: Requested operation is not valid: network is already active
[root@localhost lhaung]# virsh net-start default
error: Failed to start network default
error: Requested operation is not valid: network is already active
4.from the first terminal
event 'lifecycle' for network default: Started
event 'lifecycle' for network default: Started
Actual results:
net-event output a unsuccessful event
Expected results:
net-event should not report unsuccessful event
Additional info:
upstream patch:
commit 45d9ea5cddad5ed151db15362a881b730b8c88f1
Author: Luyao Huang <lhuang>
Date: Sat Nov 1 18:03:23 2014 +0800
network: fix call virNetworkEventLifecycleNew when networkStartNetwork fail
When start a network fail, libvirt still call virNetworkEventLifecycleNew
to send a event.
Signed-off-by: Luyao Huang <lhuang>
diff --git a/src/network/bridge_driver.c b/src/network/bridge_driver.c
index 10ded33..11e86e0 100644
--- a/src/network/bridge_driver.c
+++ b/src/network/bridge_driver.c
@@ -3253,7 +3253,8 @@ static int networkCreate(virNetworkPtr net)
if (virNetworkCreateEnsureACL(net->conn, network->def) < 0)
goto cleanup;
- ret = networkStartNetwork(driver, network);
+ if ((ret = networkStartNetwork(driver, network)) < 0)
+ goto cleanup;
event = virNetworkEventLifecycleNew(network->def->name,
network->def->uuid,
Verify this bug with libvirt-1.2.8-7.el7:
Steps:
1.do net-event infirst terminal:
# virsh net-event --event lifecycle --loop
2.open another terminal and do :
# virsh net-destroy default
Network default destroyed
# virsh net-start default
Network default started
# virsh net-start default
error: Failed to start network default
error: Requested operation is not valid: network is already active
# virsh net-start default
error: Failed to start network default
error: Requested operation is not valid: network is already active
3.check the first terminal and libvirt only output the success event:
# virsh net-event --event lifecycle --loop
event 'lifecycle' for network default: Stopped
event 'lifecycle' for network default: Started
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHSA-2015-0323.html
Description of problem: net-event should not report unsuccessful event Version-Release number of selected component (if applicable): libvirt-1.2.8-6.el7.x86_64 How reproducible: 100% Steps: 1.prepare a virtual network # virsh net-list --all Name State Autostart Persistent ---------------------------------------------------------- default active yes yes 2.# virsh net-event net4 lifecycle --loop 3.open another terminal [root@localhost lhaung]# virsh net-start default error: Failed to start network default error: Requested operation is not valid: network is already active [root@localhost lhaung]# virsh net-start default error: Failed to start network default error: Requested operation is not valid: network is already active 4.from the first terminal event 'lifecycle' for network default: Started event 'lifecycle' for network default: Started Actual results: net-event output a unsuccessful event Expected results: net-event should not report unsuccessful event Additional info: upstream patch: commit 45d9ea5cddad5ed151db15362a881b730b8c88f1 Author: Luyao Huang <lhuang> Date: Sat Nov 1 18:03:23 2014 +0800 network: fix call virNetworkEventLifecycleNew when networkStartNetwork fail When start a network fail, libvirt still call virNetworkEventLifecycleNew to send a event. Signed-off-by: Luyao Huang <lhuang> diff --git a/src/network/bridge_driver.c b/src/network/bridge_driver.c index 10ded33..11e86e0 100644 --- a/src/network/bridge_driver.c +++ b/src/network/bridge_driver.c @@ -3253,7 +3253,8 @@ static int networkCreate(virNetworkPtr net) if (virNetworkCreateEnsureACL(net->conn, network->def) < 0) goto cleanup; - ret = networkStartNetwork(driver, network); + if ((ret = networkStartNetwork(driver, network)) < 0) + goto cleanup; event = virNetworkEventLifecycleNew(network->def->name, network->def->uuid,