ABIQUO

  • Log In Access more options
    • Online Help
    • GreenHopper Help
    • Agile Answers
    • Use Agile By Default
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What’s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Agile Access more options
    • Planning Board
    • Task Board
    • Chart Board
    • Released Board
    • Rapid Board
    • Manage Rapid Boards
    • Getting Started
  • Abiquo
  • ABICLOUD-709

Same remote port assigned to all VM deployed in same VApp

  • Rapid Board
  • More Actions
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Cannot Reproduce
  • Affects Version/s: Abiquo-1.6.0
  • Fix Version/s: Abiquo 1.6.8
  • Component/s: Virtualization
  • Labels:
    None
  • Affect Build:
    3430

Description

This has been detected in xen, but should be verified in kvm, esxi and hyper-v

Steps to Reproduce
-enter as sysadmin
-go to virtual datacenter
-create a virtual appliance
-add several Virtual image to the template and deploy

Expected Results
-all virtual machines are deployed and each one has an incremented port

Real Results
-Virtual machines are deployed and its port are all the same.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Daniel Estevez added a comment - 30/Sep/10 6:39 PM
This can be reproduced in Accounting Environment adding XEN-Dev or XEN-QA as hypervisors.

VirtualFactory and port number assignment should be revised.
Show
Daniel Estevez added a comment - 30/Sep/10 6:39 PM This can be reproduced in Accounting Environment adding XEN-Dev or XEN-QA as hypervisors. VirtualFactory and port number assignment should be revised.
Hide
Permalink
Pedro Navarro Pérez added a comment - 05/Oct/10 2:41 PM
- The port decision algorithm was not managing the possibility to found a port -1 in Xen. This was causing to choose a used port.
Show
Pedro Navarro Pérez added a comment - 05/Oct/10 2:41 PM - The port decision algorithm was not managing the possibility to found a port -1 in Xen. This was causing to choose a used port.
Hide
Permalink
Valerie Kalusinski added a comment - 29/Oct/10 9:58 AM
This issue has not happened
Verified in 1.6.8 build 3829-2333
Show
Valerie Kalusinski added a comment - 29/Oct/10 9:58 AM This issue has not happened Verified in 1.6.8 build 3829-2333
Hide
Permalink
Valerie Kalusinski added a comment - 09/Jun/11 4:41 PM
This bug happened again in KVM.
Reopened on master 1.8
Show
Valerie Kalusinski added a comment - 09/Jun/11 4:41 PM This bug happened again in KVM. Reopened on master 1.8
Hide
Permalink
Sergi Castro added a comment - 17/Jun/11 12:03 PM
Not happened in 1.8
Show
Sergi Castro added a comment - 17/Jun/11 12:03 PM Not happened in 1.8
Hide
Permalink
Salvador Gironès Gil added a comment - 22/Jun/11 4:05 PM
Already fixed
Show
Salvador Gironès Gil added a comment - 22/Jun/11 4:05 PM Already fixed

People

  • Assignee:
    Sergi Castro
    Reporter:
    Valerie Kalusinski
Vote (0)
Watch (0)

Dates

  • Created:
    16/Sep/10 5:57 PM
    Updated:
    29/Mar/12 7:56 PM
    Resolved:
    17/Jun/11 12:03 PM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for abiquo. Try JIRA - bug tracking software for your team.