Bug 1358501

Summary: [RFE] multihost network change - notify when done
Product: Red Hat Enterprise Virtualization Manager Reporter: Marina Kalinin <mkalinin>
Component: ovirt-engineAssignee: eraviv
Status: CLOSED ERRATA QA Contact: Michael Burman <mburman>
Severity: high Docs Contact:
Priority: high    
Version: 3.6.7CC: danken, dholler, eraviv, lsurette, mburman, mtessun, pelauter, rdlugyhe, srevivo
Target Milestone: ovirt-4.4.0Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Network operations that span multiple hosts may take a long time. This enhancement shows you when these operations finish: It records start and end events in the Events Tab of the Administration Portal and engine.log. If you use the Administration Portal to trigger the network operation, the portal also displays a pop-up notification when the operation is complete.
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-08-04 13:16:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1193083    
Bug Blocks: 902971    

Description Marina Kalinin 2016-07-20 20:44:05 UTC
Because of bz#1300220, concurrent multi-host network changes are prone to fail. Until that bug is fixed, the labels should be added in a serial manner. However there is no notification of this reported to the user.

The suggestion is to provide the following messaging to the user:

1) After adding network:
"Please wait for the process to complete... this can take several minutes."
This should be a pop up message to the user.

2) After the operation has been completed for all the hosts, report:
"Completed".
This can be reported to the Events log.


Once the bug#1300220 is fixed, we can get rid of message #1.

Comment 7 Marina Kalinin 2018-02-21 04:57:03 UTC
Dan,
Do you know what is the status of this feature?
I see the main, concurrent multi-host operations, bug is targeted to 4.3.

Comment 14 Marina Kalinin 2019-04-02 22:12:19 UTC
Can this BZ be closed current release based on this comment?
https://bugzilla.redhat.com/show_bug.cgi?id=1300220#c55
And if yes - can someone please point me out how exactly would this work? OR actually add doc text to this bug.

Comment 15 Michael Burman 2019-04-03 08:04:54 UTC
The bug can't be closed as current release as it's not in current release. We don't notifying when done, so..
In comment 55 in BZ 1300220 we only say that operation is in progress.

Comment 16 Dominik Holler 2019-05-10 15:24:02 UTC
clear needinfo, since Michael replied already.

Comment 18 eraviv 2019-07-03 05:54:31 UTC
Multi-host network operations requiring end of operation notification:

1. label exists on nics in more than one host:
  - detach\attach labelled network to cluster
  - un\label network
2. network attached to more than one host:
  - change network property (e.g qos, mtu, vlan-id)
  - change network role
3. sync all networks in cluster


Notifications:
- webadmin invocation: log + events tab + popup
- REST API invocation: log + events tab


Please ack no more multi-host flows exist.
Thanks

Comment 19 Michael Burman 2019-07-03 10:48:03 UTC
(In reply to eraviv from comment #18)
> Multi-host network operations requiring end of operation notification:
> 
> 1. label exists on nics in more than one host:
>   - detach\attach labeled network to cluster
>   - un\label network
    - label already exist on networks and then label is attached to a nic/bond 
> 2. network attached to more than one host:
    - change network property (e.g qos, mtu, vlan-id, VM/non-VM, DNS name server)
>   - change network role
> 3. sync all networks in cluster
> 
> 
> Notifications:
> - webadmin invocation: log + events tab + popup
> - REST API invocation: log + events tab
> 
> 
> Please ack no more multi-host flows exist.
> Thanks

Comment 22 Dominik Holler 2019-08-23 11:47:40 UTC
Michael, is the implementation in the latest build (oVirt 4.3.6 Third Release Candidate) sufficient?

Comment 30 Michael Burman 2019-10-24 11:31:25 UTC
Verified on - 4.4.0-0.4.master.el7

Comment 32 RHV bug bot 2019-12-13 13:13:44 UTC
WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 33 RHV bug bot 2019-12-20 17:43:39 UTC
WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 34 RHV bug bot 2020-01-08 14:47:21 UTC
WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 35 RHV bug bot 2020-01-08 15:14:25 UTC
WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 36 RHV bug bot 2020-01-24 19:49:03 UTC
WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 40 errata-xmlrpc 2020-08-04 13:16:05 UTC
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 (Important: RHV Manager (ovirt-engine) 4.4 security, bug fix, and enhancement update), 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://access.redhat.com/errata/RHSA-2020:3247