Bug #4928

Cannot import two vCenter networks with the same name in two clusters

Added by Miguel Ángel Álvarez Cabrerizo over 4 years ago. Updated over 4 years ago.

Status:ClosedStart date:11/17/2016
Priority:NormalDue date:
Assignee:Miguel Ángel Álvarez Cabrerizo% Done:


Target version:Release 5.2.1
Resolution: Pull request:
Affected Versions:OpenNebula 5.0, OpenNebula 5.2


When importing two networks with the same name which have been configured in different clusters should create two different OpenNebula networks when importing, however only the first network is imported.

Once the code has been fixed the two networks can be imported with the cluster name after a hyphen as it was designed:

  • Network found:
    - Name : Network_testrm - Test
    - Type : Port Group
    - Cluster : Test
    Import this Network [y/n]? y
    • Network found:
      - Name : Network_testrm - devel
      - Type : Port Group
      - Cluster : devel


#1 Updated by Ruben S. Montero over 4 years ago

  • Target version set to Release 5.4

#2 Updated by Tino Vázquez over 4 years ago

  • Target version changed from Release 5.4 to Release 5.2.1

Also available in: Atom PDF