Project

General

Profile

Actions

Bug #13179

closed

oVirt Network selection doesn't select the right network during building host

Added by Diego Michelotto over 8 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Compute resources - oVirt
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Dear Foreman Team,

I have a problem during the building of an oVirt host from foreman web interface.

I have different network defined in my oVirt Datacenter as you can see in the next screenshot.

When I try to create a new host from Foreman, during the interface configuration I see all the networks, as you can see in the next screenshot.

If I select a network that aren't the first suggested (the first suggested is cloudadmin) for example ocpadmin and I save it, when I reopen the interface configuration form all is OK (is selected ocpadmin in the dropdown menu). After the other configuration I submit the host creation. The result is a new host created on oVirt with a network interface configured with cloudadmin network that are the first suggested in the network dropdown menu. As you can see in the next screenshot.

If I edit the new host and open the interface configuration form I found cloudadmin as selected item in the network dropdown menu as you can see in the next screenshot.

As test I tried to create a new host with the hammer cli and I can create a new host successfully with the correct network configuration.

For these reason I think there are some problems in the network configuration form.

Note: I have an old istance of Foreman (1.7.3) and I don't have this problem.

foreman 1.9.3 and 1.10
oVirt 3.5.5

Best regards.
Diego


Files

foreman_network_host.png View foreman_network_host.png 5.45 KB Diego Michelotto, 01/13/2016 09:15 AM
ovirt_network_host.png View ovirt_network_host.png 12.7 KB Diego Michelotto, 01/13/2016 09:15 AM
ovirt_networks.png View ovirt_networks.png 25.4 KB Diego Michelotto, 01/13/2016 09:15 AM
foreman_networks.png View foreman_networks.png 14.9 KB Diego Michelotto, 01/13/2016 09:15 AM

Related issues 1 (0 open1 closed)

Copied to Foreman - Bug #13591: oVirt Network selection doesn't select the right network during building hostDuplicate01/13/2016Actions
Actions #1

Updated by Dominic Cleal over 8 years ago

  • Category changed from Web Interface to Compute resources - oVirt
  • Priority changed from Urgent to Normal
Actions #2

Updated by Diego Michelotto about 8 years ago

Any news about this bug, for us is critical.

Best regards
Diego

Actions #3

Updated by Diego Michelotto about 8 years ago

  • Copied to Bug #13591: oVirt Network selection doesn't select the right network during building host added
Actions #4

Updated by Diego Michelotto about 8 years ago

The bug still exist in the 1.10.1 release.

Regards
Diego

Actions #5

Updated by Doina Cristina Aiftimiei about 8 years ago

Would it be possible to have an assessment of when the issue could be solved?
Is critical for us ... and even a surprise as older version was not affected.

Actions #6

Updated by Diego Michelotto about 8 years ago

The bug still exist in the 1.10.2 release.

Regards
Diego

Actions #7

Updated by Diego Michelotto about 8 years ago

The bug still exist in the 1.10.3 and 1.11.0 releases.

Please have a look, for us is critical this bug.

Regards
Diego

Actions #8

Updated by Diego Michelotto about 8 years ago

Hi,

any news about this bug?

Best regards
Diego

Actions #9

Updated by Angelo Lisco almost 8 years ago

Hi Diego, take a look at the patch attached to this bug and check if it fixes your issue:
http://projects.theforeman.org/issues/15020

Actions #10

Updated by Diego Michelotto almost 8 years ago

Hi Angelo,

this patch doesn't fix my bug, the nic_info script isn't loaded at the creation of new oVirt Host. This script is used for select the correct oVirt Network when the host is already created.

Best regards
Diego.

Actions #11

Updated by Angelo Lisco almost 8 years ago

Whoops...sorry for the noise :(

Actions #12

Updated by Diego Michelotto over 7 years ago

Bug still present in 1.12.4

Actions #13

Updated by Diego Michelotto about 7 years ago

After upgrade of our instance of oVirt to oVirt 4.0 the bug is gone.

Actions #14

Updated by Shira Maximov almost 6 years ago

  • Status changed from New to Closed

The bug is gone after upgrading Ovirt.

Actions

Also available in: Atom PDF