Project

General

Profile

Bug #10978

"No networks found." while creating oVirt Compute Profiles

Added by Sherif Nagy over 4 years ago. Updated over 1 year ago.

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

Description

The compute profiles that are assigned to oVirt compute resources are no longer able to view the oVirt network configurations and shows the following message:

Network interfaces
No networks found.

However while provisioning a VM from a configured host group the user must go to interfaces tab then edit the interface and assign a network Name and chose the network under the oVirt subsection.

Associated revisions

Revision 99069f53 (diff)
Added by Ivan Necas almost 4 years ago

Fixes #10978 - fix possibility to assign networks in compute profile for ovirt

Revision 2a1187d7 (diff)
Added by Ivan Necas almost 4 years ago

Fixes #10978 - fix possibility to assign networks in compute profile for ovirt

(cherry picked from commit 99069f530174a198e923295982aeb75159c1b364)

History

#1 Updated by Jesse Johnson over 4 years ago

I am currently experiencing this in 1.9.2 also.

Sherif Nagy wrote:

The compute profiles that are assigned to oVirt compute resources are no longer able to view the oVirt network configurations and shows the following message:

Network interfaces
No networks found.

However while provisioning a VM from a configured host group the user must go to interfaces tab then edit the interface and assign a network Name and chose the network under the oVirt subsection.

#2 Updated by Matthew Cillo about 4 years ago

I am seeing this as well, I'm using 1.10.1.

#3 Updated by Ivan Necas almost 4 years ago

  • Status changed from New to Assigned
  • Assignee set to Ivan Necas

#4 Updated by The Foreman Bot almost 4 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/3412 added

#5 Updated by Ivan Necas almost 4 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#6 Updated by Dominic Cleal almost 4 years ago

  • Legacy Backlogs Release (now unused) set to 141

Also available in: Atom PDF