Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1070234

Summary:

[neutron integration] VM with vNIC connected to externally provided network is scheduled on host with no Neutron agent

Product:

[oVirt] ovirt-engine

Reporter:

GenadiC <gcheresh>

Component:

General

Assignee:

Barak <bazulay>

Status:

CLOSED EOL

QA Contact:

GenadiC <gcheresh>

Severity:

high

Docs Contact:

Priority:

high

Version:

---

CC:

bazulay, bugs, danken, gcheresh, gklein, masayag, oblaut, rbalakri, sbonazzo, yeylon, ylavi

Target Milestone:

---

Target Release:

---

Hardware:

x86_64

OS:

Linux

Whiteboard:

network

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2015-10-02 10:38:12 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:

Attachments:

Description	Flags
engine and vdsm log	none

Description GenadiC 2014-02-26 12:57:54 UTC

Created attachment 867983 [details]
engine and vdsm log

Description of problem:
If you have 2 Hosts on Cluster - one with external Provider installed and network 'red' and another one without external provider with network blue attached to it and you try to start VM with network blue and red an action of start VM fails after several seconds with Cannot get interface MTU on <network> error.
An action indeed should fail as there is no host that this VM can run on, but we expect the same behaviour as in Ovirt, meaning the VM should not start at all and there is an error message explaining the problem

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Install one host with Network provider with network red
2. Install another host without Network provider with network blue
3. Add VNIC profiles of both networks to VM and try to start VM

Actual results:
VM start and fails after several seconds with Cannot get interface MTU on <network> error

Expected results:
VM should not start and an error message with the reason should be displayed

Additional info:
Related to bug https://bugzilla.redhat.com/show_bug.cgi?id=1061611

Comment 1 Itamar Heim 2014-03-02 05:42:04 UTC

Setting target release to current version for consideration and review. please
do not push non-RFE bugs to an undefined target release to make sure bugs are
reviewed for relevancy, fix, closure, etc.

Comment 2 Sandro Bonazzola 2014-03-04 09:28:06 UTC

This is an automated message.
Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.

Comment 3 Moti Asayag 2014-06-23 13:53:54 UTC

Several approached to this bug should be considered:

1. Add the external network provider id to the host entity and store it on vds_static. If a scheduled vm is attached to a network, the engine will examine that the external network can be provisioned from the external network provider. If the network cannot be provisioned, the host will be filtered.

2. Set external provider on cluster level.

In order not to commit to any solution ATM, the recommendation is to have all of the hosts within a cluster installed/configured with the external network providers to avoid the scheduling miss.

Comment 4 Sandro Bonazzola 2015-09-04 09:01:12 UTC

This is an automated message.
This Bugzilla report has been opened on a version which is not maintained anymore.
Please check if this bug is still relevant in oVirt 3.5.4.
If it's not relevant anymore, please close it (you may use EOL or CURRENT RELEASE resolution)
If it's an RFE please update the version to 4.0 if still relevant.

Comment 5 Sandro Bonazzola 2015-10-02 10:38:12 UTC

This is an automated message.
This Bugzilla report has been opened on a version which is not maintained
anymore.
Please check if this bug is still relevant in oVirt 3.5.4 and reopen if still
an issue.