Bug 1438418 - [REST] When setting network as management, the network becomes Non-operational
Summary: [REST] When setting network as management, the network becomes Non-operational
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: future
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ovirt-4.1.2
: 4.1.2
Assignee: Yevgeny Zaspitsky
QA Contact: Ori Ben Sasson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-03 12:05 UTC by Ori Ben Sasson
Modified: 2017-05-23 08:16 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-23 08:16:01 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.1+
rule-engine: ovirt-4.2+
rule-engine: blocker+


Attachments (Terms of Use)
logs (1.35 MB, application/zip)
2017-04-03 12:05 UTC, Ori Ben Sasson
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 75241 0 master MERGED engine: ignore NetworkCluster.status in the input 2017-04-20 13:04:23 UTC
oVirt gerrit 75826 0 ovirt-engine-4.1 MERGED engine: ignore NetworkCluster.status in the input 2017-04-23 13:22:54 UTC

Description Ori Ben Sasson 2017-04-03 12:05:53 UTC
Created attachment 1268354 [details]
logs

Description of problem:
Host should be Non-operational when ovirtmgmt isn't attach to host

Version-Release number of selected component (if applicable):
ovirt-engine-4.2.0-0.0.master.20170402072517.gitb0c121a.el7.centos.noarch
vdsm-4.20.0-577.git62a070c.el7.centos.x86_64


How reproducible:
100

Steps to Reproduce:
1. management_as_role/mgmt_net_role_test case 8 (install_host_with_new_management fixture)



Actual results:
Host is in up state .

Expected results:
Host should be Non-operational

Comment 1 Ori Ben Sasson 2017-04-03 13:28:59 UTC
We found the specific issue,
When setting network as a network management, the network becomes Non-operational.


Steps to Reproduce:
1. Create new DC,
2. Create new cluster .
3. Add new network to cluster
4. send in REST:
 PUT ovirt-engine/api/clusters/<CLUSTER-ID>/networks/<NETWORK-ID>
<network>
    <usages>
        <usage>management</usage>
    </usages>
</network>

Comment 2 Red Hat Bugzilla Rules Engine 2017-04-05 07:30:20 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 3 Yevgeny Zaspitsky 2017-04-05 07:39:29 UTC
The bug was found and opened on mater.
Is it proven to be on 4.1 too?

Comment 4 Yevgeny Zaspitsky 2017-04-05 17:52:05 UTC
The issue exists in 4.0 and might be even earlier, but didn't affected major flows.
Thus it isn't a regression.

Comment 5 Ori Ben Sasson 2017-04-18 13:42:34 UTC
(In reply to Yevgeny Zaspitsky from comment #3)
> The bug was found and opened on mater.
> Is it proven to be on 4.1 too?

Our automation test running from 3.6 without any issue,
This failed exist on master.

Comment 6 Yevgeny Zaspitsky 2017-04-18 21:16:56 UTC
IIUC:
* The initially reported bug was caused by improper cleanup you did on the VDSM side.
* The current $subject bug was never tested on previous versions (IMHO exists since ever), thus you cannot claim that as a regression.

Am I right?

Comment 7 Dan Kenigsberg 2017-04-20 13:53:30 UTC
Even not a regression, the fix seems simple enough, and worth getting into 4.1.

Comment 8 Ori Ben Sasson 2017-04-30 16:49:47 UTC
Verified on 
ovirt-engine-4.1.2-0.1.el7.noarch
 and 
ovirt-engine-4.2.0-0.0.master.20170429081602.gitb982df7.el7.centos.noarch


Note You need to log in before you can comment on or make changes to this bug.