|Summary:||[RFE] cannot edit/create network on DC via left hand panel tree on DC which was recreated|
|Product:||Red Hat Enterprise Virtualization Manager||Reporter:||Martin Pavlik <mpavlik>|
|Status:||CLOSED ERRATA||QA Contact:||Martin Pavlik <mpavlik>|
|Version:||3.3.0||CC:||ecohen, gklein, iheim, lpeer, lvernia, masayag, mburman, mpavlik, myakove, nyechiel, oourfali, rbalakri, Rhev-m-bugs, yeylon|
|Target Milestone:||---||Keywords:||FutureFeature, Reopened|
|Fixed In Version:||Doc Type:||Enhancement|
|Doc Text:||Story Points:||---|
|Last Closed:||2015-02-11 17:54:42 UTC||Type:||Bug|
|oVirt Team:||Network||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
|Bug Depends On:||879077|
|Bug Blocks:||1142923, 1156165|
Description Martin Pavlik 2013-09-03 08:29:04 UTC
Created attachment 793065 [details] log_collector Description of problem: If user creates DC and then remove the DC and then create another DC with the same name you can't create/edit network from the DC tree > network tab . UI will give following error message: Error while executing action: Data Center doesn't exist. It seems to be consequence of bug 879077 , because there is no auto refresh, network cannot be created. If the tree is manually refreshed it is possible to create a new network. Version-Release number of selected component (if applicable): Red Hat Enterprise Virtualization Manager Version: 3.3.0-0.18.master.el6ev How reproducible: 100% Steps to Reproduce: 1. see first line of description Actual results: cannot edit/create network on DC via left hand pane tree on DC which was recreated Expected results: tree is auto refreshed, network can be created Additional info: 2013-09-03 10:19:32,301 WARN [org.ovirt.engine.core.bll.network.dc.AddNetworkCommand] (ajp-/127.0.0.1:8702-5) CanDoAction of action AddNetwork failed. Reasons:VAR__TYPE__NETWORK,VAR__ACTION__ADD,ACTION_TYPE_FAILED_STORAGE_POOL_NOT_EXIST
Comment 2 Moti Asayag 2013-09-03 14:18:42 UTC
There are more consequences to that action, e.g. inability to add cluster. I don't think that this scenario is that frequent and seems it would be resolved by fixing 879077.
Comment 3 Moti Asayag 2014-02-04 13:19:08 UTC
Closing this bug since it is depended on recently closed Bug 879077.
Comment 7 Nir Yechiel 2014-07-17 09:09:16 UTC
The fix itself is on BZ 879077. Setting this bug to ON_QA for verification of the network team against 3.5.
Comment 8 Meni Yakove 2014-07-17 13:46:29 UTC
Comment 9 Michael Burman 2014-07-20 06:16:45 UTC
Comment 11 errata-xmlrpc 2015-02-11 17:54:42 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, 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-0158.html