Bug #10248

When cloning virtual machine from existing machine - Network Interface and Storage details are not propagated.

Added by Tomáš Strachota over 4 years ago. Updated about 1 year ago.

Compute resources
Target version:
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:


Cloned from
Description of problem:
Customer attempts to clone VM in the Setellite6 WebUI. Most of the settings are copied from original VM while Network interface and Storage information are default one.

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

How reproducible:

Steps to Reproduce:
1. In Sat6 clone machine from existing host

Actual results:
If source host has different Network and Storage settings to VMWare template then new host gets default Network and Storage settings from template

Expected results:
New host must get settings from cloned host rather than from VMware template

Additional info:

Related issues

Related to Foreman - Bug #19236: Unable to delete Host in Foreman which has been delete in RHV alreadyClosed2017-04-10

Associated revisions

Revision 4269abbd (diff)
Added by Tomáš Strachota about 4 years ago

Fixes #10248 - cloning volume information for virtual machines


#1 Updated by Tomáš Strachota over 4 years ago

  • Category set to Compute resources
  • Status changed from New to Assigned

#2 Updated by The Foreman Bot over 4 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request added
  • Pull request deleted ()

#3 Updated by Dominic Cleal about 4 years ago

  • Legacy Backlogs Release (now unused) set to 63

#4 Updated by Anonymous about 4 years ago

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

#5 Updated by Ivan Necas over 2 years ago

  • Related to Bug #19236: Unable to delete Host in Foreman which has been delete in RHV already added

Also available in: Atom PDF