[jira] [Commented] (CLOUDSTACK-7536) user vm can get a gateway ip in case of shared network.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14173483#comment-14173483 ] Wei Zhou commented on CLOUDSTACK-7536: -- Should this fix also in 4.4 ? > user vm can get a gateway ip in case of shared network. > --- > > Key: CLOUDSTACK-7536 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7536 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.2.0 >Reporter: Bharat Kumar >Assignee: Bharat Kumar > Fix For: 4.5.0 > > > steps to reproduce. > 1.) create a shared network with the following details. > gateway 10.136.10.1 > netmask 255.255.255.0 > guest ip range 10.136.10.1 to 10.136.10.20 (note that the gateway ip is > a part of the guest ip range.) > 2.) deploy a vm > the gateway ip gets allocated to a uservm. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7333) [vGPU] Windows VM with GPU cards and PV drivers is going to repair state when deployed with "dynamic scaling enabled" option.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14173533#comment-14173533 ] Sanjay Tripathi commented on CLOUDSTACK-7333: - Verified using XenCenter, that this is a bug in XS 6.2.5. The issue is fixed in 6.5 as I am not able to reproduce this issue in 6.5. We need to document this limitation. I'll open a doc ticket to track this. > [vGPU] Windows VM with GPU cards and PV drivers is going to repair state when > deployed with "dynamic scaling enabled" option. > - > > Key: CLOUDSTACK-7333 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7333 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, Management Server, XenServer >Affects Versions: 4.5.0 > Environment: Xenserver 6.2.5 + PV drivers (up to date) >Reporter: Abhinav Roy >Assignee: Sanjay Tripathi >Priority: Blocker > Fix For: 4.5.0 > > Attachments: CS-7333.zip > > > There are 4 scenarios which i tried : > Setup : > = > CS 4.5 advanced zone with Xen 6.2.5 + PV drivers ( XS Tools) > Dynamic scaling is enabled on zone level. > Scenario 1 : > > 1. Register a windows 8 or windows 2012 template ( without dynamic scaling > enabled) and deploy a VM with vGPU service offering from it. > > -- Template is registered and VM is deployed. > 2. Install the PV drivers on the VM. > -- PV drivers are installed successfully (make sure they are latest) > 3. Now stop the VM, enable dynamic scaling and start the VM. > -- VM fails to start and goes into the repair state. > Scenario 2 : > > 1. Register a windows 8 or windows 2012 template ( with dynamic scaling > enabled) and deploy a VM with vGPU service offering from it. > > -- Template is registered and VM is deployed. > 2. Install the PV drivers on the VM. > -- PV drivers fail to install and VM goes to repair state. > Scenario 3 : > > 1. Register a windows 8 or windows 2012 template ( with dynamic scaling > enabled and PV drivers installed) and deploy a VM with vGPU service offering > from it. > > -- Template is registered and VM fails to deploy, it goes into repair > state. > Scenario 4 : > > 1. Register a windows 8 or windows 2012 template ( without dynamic scaling > enabled but PV drivers are installed) and deploy a VM with vGPU service > offering from it. > > -- Template is registered and VM is deployed. > 2. Now stop the VM, enable dynamic scaling and start the VM. > -- VM fails to start and goes into the repair state > Scenario 5 : > > 1. Register a windows 8 or windows 2012 ISO and deploy a VM with vGPU service > offering from it. > > -- ISO is registered and VM is deployed. > 2. Install the PV drivers on the VM. > -- PV drivers are installed successfully (make sure they are latest) > 3. Now stop the VM, enable dynamic scaling and start the VM. > -- VM fails to start and goes into the repair state -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7738) [Doc][Known Issue] PV tools are not getting installed on VGPU enabled Windows VMs when VM deployed with "dynamic scaling enabled" option.
Sanjay Tripathi created CLOUDSTACK-7738: --- Summary: [Doc][Known Issue] PV tools are not getting installed on VGPU enabled Windows VMs when VM deployed with "dynamic scaling enabled" option. Key: CLOUDSTACK-7738 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7738 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.5.0 Reporter: Sanjay Tripathi Assignee: Radhika Nair There are 4 scenarios which i tried : Setup : = CS 4.5 advanced zone with Xen 6.2.5 + PV drivers ( XS Tools) Dynamic scaling is enabled on zone level. Scenario 1 : 1. Register a windows 8 or windows 2012 template ( without dynamic scaling enabled) and deploy a VM with vGPU service offering from it. – Template is registered and VM is deployed. 2. Install the PV drivers on the VM. – PV drivers are installed successfully (make sure they are latest) 3. Now stop the VM, enable dynamic scaling and start the VM. – VM fails to start and goes into the repair state. Scenario 2 : 1. Register a windows 8 or windows 2012 template ( with dynamic scaling enabled) and deploy a VM with vGPU service offering from it. – Template is registered and VM is deployed. 2. Install the PV drivers on the VM. – PV drivers fail to install and VM goes to repair state. Scenario 3 : 1. Register a windows 8 or windows 2012 template ( with dynamic scaling enabled and PV drivers installed) and deploy a VM with vGPU service offering from it. – Template is registered and VM fails to deploy, it goes into repair state. Scenario 4 : 1. Register a windows 8 or windows 2012 template ( without dynamic scaling enabled but PV drivers are installed) and deploy a VM with vGPU service offering from it. – Template is registered and VM is deployed. 2. Now stop the VM, enable dynamic scaling and start the VM. – VM fails to start and goes into the repair state Scenario 5 : 1. Register a windows 8 or windows 2012 ISO and deploy a VM with vGPU service offering from it. – ISO is registered and VM is deployed. 2. Install the PV drivers on the VM. – PV drivers are installed successfully (make sure they are latest) 3. Now stop the VM, enable dynamic scaling and start the VM. – VM fails to start and goes into the repair state All the above mentioned scenarios are not supported/issue in XS 6.2.5. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7333) [vGPU] Windows VM with GPU cards and PV drivers is going to repair state when deployed with "dynamic scaling enabled" option.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Tripathi resolved CLOUDSTACK-7333. - Resolution: Won't Fix There is no need to fix anything in CloudStack as this is the issue in XS SP1 + patches. Also, the issue is fixed in XS 6.5 > [vGPU] Windows VM with GPU cards and PV drivers is going to repair state when > deployed with "dynamic scaling enabled" option. > - > > Key: CLOUDSTACK-7333 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7333 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, Management Server, XenServer >Affects Versions: 4.5.0 > Environment: Xenserver 6.2.5 + PV drivers (up to date) >Reporter: Abhinav Roy >Assignee: Sanjay Tripathi >Priority: Blocker > Fix For: 4.5.0 > > Attachments: CS-7333.zip > > > There are 4 scenarios which i tried : > Setup : > = > CS 4.5 advanced zone with Xen 6.2.5 + PV drivers ( XS Tools) > Dynamic scaling is enabled on zone level. > Scenario 1 : > > 1. Register a windows 8 or windows 2012 template ( without dynamic scaling > enabled) and deploy a VM with vGPU service offering from it. > > -- Template is registered and VM is deployed. > 2. Install the PV drivers on the VM. > -- PV drivers are installed successfully (make sure they are latest) > 3. Now stop the VM, enable dynamic scaling and start the VM. > -- VM fails to start and goes into the repair state. > Scenario 2 : > > 1. Register a windows 8 or windows 2012 template ( with dynamic scaling > enabled) and deploy a VM with vGPU service offering from it. > > -- Template is registered and VM is deployed. > 2. Install the PV drivers on the VM. > -- PV drivers fail to install and VM goes to repair state. > Scenario 3 : > > 1. Register a windows 8 or windows 2012 template ( with dynamic scaling > enabled and PV drivers installed) and deploy a VM with vGPU service offering > from it. > > -- Template is registered and VM fails to deploy, it goes into repair > state. > Scenario 4 : > > 1. Register a windows 8 or windows 2012 template ( without dynamic scaling > enabled but PV drivers are installed) and deploy a VM with vGPU service > offering from it. > > -- Template is registered and VM is deployed. > 2. Now stop the VM, enable dynamic scaling and start the VM. > -- VM fails to start and goes into the repair state > Scenario 5 : > > 1. Register a windows 8 or windows 2012 ISO and deploy a VM with vGPU service > offering from it. > > -- ISO is registered and VM is deployed. > 2. Install the PV drivers on the VM. > -- PV drivers are installed successfully (make sure they are latest) > 3. Now stop the VM, enable dynamic scaling and start the VM. > -- VM fails to start and goes into the repair state -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7739) Add new vGPU types K160Q, K180Q, K280Q to the Cloud Platform UI
Sanjay Tripathi created CLOUDSTACK-7739: --- Summary: Add new vGPU types K160Q, K180Q, K280Q to the Cloud Platform UI Key: CLOUDSTACK-7739 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7739 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Reporter: Sanjay Tripathi Assignee: Sanjay Tripathi Priority: Critical Fix For: 4.5.0 NVidia will be releasing a new vGPU driver, it will make new vGPU types available on both XS 6.2 SP1 and XS 6.5. Both the XenServer and the CloudStack API will pick these new types up, but CloudStack GUI need some changes as the vGPU types are hard-coded here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7739) Add new vGPU types K160Q, K180Q, K280Q to the CloudStack UI
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Tripathi updated CLOUDSTACK-7739: Summary: Add new vGPU types K160Q, K180Q, K280Q to the CloudStack UI (was: Add new vGPU types K160Q, K180Q, K280Q to the Cloud Platform UI) > Add new vGPU types K160Q, K180Q, K280Q to the CloudStack UI > --- > > Key: CLOUDSTACK-7739 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7739 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.5.0 >Reporter: Sanjay Tripathi >Assignee: Sanjay Tripathi >Priority: Critical > Fix For: 4.5.0 > > > NVidia will be releasing a new vGPU driver, it will make new vGPU types > available on both XS 6.2 SP1 and XS 6.5. > Both the XenServer and the CloudStack API will pick these new types up, but > CloudStack GUI need some changes as the vGPU types are hard-coded here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7739) Add new vGPU types K160Q, K180Q, K280Q to the CloudStack UI
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14173547#comment-14173547 ] ASF subversion and git services commented on CLOUDSTACK-7739: - Commit 420d4e0da0307a8e7b0e530da1a5aedcc209516e in cloudstack's branch refs/heads/4.5 from [~sanjay.tripathi] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=420d4e0 ] CLOUDSTACK-7739: Add new vGPU types K160Q, K180Q, K280Q to the CloudStack UI. > Add new vGPU types K160Q, K180Q, K280Q to the CloudStack UI > --- > > Key: CLOUDSTACK-7739 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7739 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.5.0 >Reporter: Sanjay Tripathi >Assignee: Sanjay Tripathi >Priority: Critical > Fix For: 4.5.0 > > > NVidia will be releasing a new vGPU driver, it will make new vGPU types > available on both XS 6.2 SP1 and XS 6.5. > Both the XenServer and the CloudStack API will pick these new types up, but > CloudStack GUI need some changes as the vGPU types are hard-coded here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7739) Add new vGPU types K160Q, K180Q, K280Q to the CloudStack UI
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14173571#comment-14173571 ] ASF subversion and git services commented on CLOUDSTACK-7739: - Commit 1f8cf0bee4f3fbe1c673dbc89c627f89d04da51f in cloudstack's branch refs/heads/master from [~sanjay.tripathi] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1f8cf0b ] CLOUDSTACK-7739: Add new vGPU types K160Q, K180Q, K280Q to the CloudStack UI. > Add new vGPU types K160Q, K180Q, K280Q to the CloudStack UI > --- > > Key: CLOUDSTACK-7739 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7739 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.5.0 >Reporter: Sanjay Tripathi >Assignee: Sanjay Tripathi >Priority: Critical > Fix For: 4.5.0 > > > NVidia will be releasing a new vGPU driver, it will make new vGPU types > available on both XS 6.2 SP1 and XS 6.5. > Both the XenServer and the CloudStack API will pick these new types up, but > CloudStack GUI need some changes as the vGPU types are hard-coded here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-7724) [Automation][HyperV] Unable to migrate VM due to JsonParseException: The JsonDeserializer EnumTypeAdapter failed to deserialize json object "Running"
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh reassigned CLOUDSTACK-7724:
-
Assignee: Devdeep Singh
> [Automation][HyperV] Unable to migrate VM due to JsonParseException: The
> JsonDeserializer EnumTypeAdapter failed to deserialize json object "Running"
> -
>
> Key: CLOUDSTACK-7724
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7724
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Affects Versions: 4.5.0
>Reporter: Chandan Purushothama
>Assignee: Devdeep Singh
>Priority: Critical
> Fix For: 4.5.0
>
>
> =
> JsonParseException: The JsonDeserializer EnumTypeAdapter failed to
> deserialize json object "Running"
> =
> 2014-10-14 19:34:47,983 DEBUG [c.c.a.t.Request]
> (Work-Job-Executor-65:ctx-81e9b15c job-191/job-192 ctx-b908f714) Seq
> 1-5051068457072722114: Sending { Cmd , MgmtId: 192182403311206, via:
> 1(10.81.56.124), Ver: v1, Flags: 100011,
> [{"com.cloud.agent.api.CheckVirtualMachineCommand":{"vmName":"i-16-36-VM","wait":20}}]
> }
> 2014-10-14 19:34:47,983 DEBUG [c.c.a.t.Request]
> (Work-Job-Executor-65:ctx-81e9b15c job-191/job-192 ctx-b908f714) Seq
> 1-5051068457072722114: Executing: { Cmd , MgmtId: 192182403311206, via:
> 1(10.81.56.124), Ver: v1, Flags: 100011,
> [{"com.cloud.agent.api.CheckVirtualMachineCommand":{"vmName":"i-16-36-VM","wait":20}}]
> }
> 2014-10-14 19:34:47,983 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-110:ctx-409b4476) Seq 1-5051068457072722114: Executing request
> 2014-10-14 19:34:47,984 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
> (DirectAgent-110:ctx-409b4476) POST request to
> https://10.81.56.124:8250/api/HypervResource/com.cloud.agent.api.CheckVirtualMachineCommand
> with contents
> {"vmName":"i-16-36-VM","contextMap":{"job":"job-191/job-192"},"wait":20}
> 2014-10-14 19:34:47,990 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
> (DirectAgent-110:ctx-409b4476) Sending cmd to
> https://10.81.56.124:8250/api/HypervResource/com.cloud.agent.api.CheckVirtualMachineCommand
> cmd
> data:{"vmName":"i-16-36-VM","contextMap":{"job":"job-191/job-192"},"wait":20}
> 2014-10-14 19:34:48,099 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
> (DirectAgent-110:ctx-409b4476) POST response is
> [{"com.cloud.agent.api.CheckVirtualMachineAnswer":{"result":true,"details":null,"state":"Running","contextMap":{}}}]
> 2014-10-14 19:34:48,148 WARN [c.c.a.m.DirectAgentAttache]
> (DirectAgent-110:ctx-409b4476) Seq 1-5051068457072722114: Throwable caught
> while executing command
> com.google.gson.JsonParseException: The JsonDeserializer EnumTypeAdapter
> failed to deserialize json object "Running" given the type class
> com.cloud.vm.VirtualMachine$PowerState
> at
> com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserializerExceptionWrapper.java:64)
> at
> com.google.gson.JsonDeserializationVisitor.invokeCustomDeserializer(JsonDeserializationVisitor.java:92)
> at
> com.google.gson.JsonObjectDeserializationVisitor.visitFieldUsingCustomHandler(JsonObjectDeserializationVisitor.java:117)
> at
> com.google.gson.ReflectingFieldNavigator.visitFieldsReflectively(ReflectingFieldNavigator.java:63)
> at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:120)
> at
> com.google.gson.JsonDeserializationContextDefault.fromJsonObject(JsonDeserializationContextDefault.java:76)
> at
> com.google.gson.JsonDeserializationContextDefault.deserialize(JsonDeserializationContextDefault.java:54)
> at com.google.gson.Gson.fromJson(Gson.java:551)
> at com.google.gson.Gson.fromJson(Gson.java:521)
> at
> com.cloud.agent.transport.ArrayTypeAdaptor.deserialize(ArrayTypeAdaptor.java:80)
> at
> com.cloud.agent.transport.ArrayTypeAdaptor.deserialize(ArrayTypeAdaptor.java:40)
> at
> com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserializerExceptionWrapper.java:51)
> at
> com.google.gson.JsonDeserializationVisitor.invokeCustomDeserializer(JsonDeserializationVisitor.java:92)
> at
> com.google.gson.JsonDeserializationVisitor.visitUsingCustomHandler(JsonDeserializationVisitor.java:80)
> at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:101)
> at
> com.google.gson.JsonDeserializationContextDefault.fromJsonArray(JsonDeserializationContextDefault.java:67)
> at
> com.google.gson.JsonDeserializationContextDefault.deserialize(
[jira] [Created] (CLOUDSTACK-7740) cloudstack-manager lacks dependency on cpu-checker
Marc Leeman created CLOUDSTACK-7740: --- Summary: cloudstack-manager lacks dependency on cpu-checker Key: CLOUDSTACK-7740 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7740 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Packaging Affects Versions: 4.3.0 Environment: Debian Wheezy Reporter: Marc Leeman Priority: Minor When installing on a Debian Wheezy system, we found out deep in the logging that a call was made to kvm-ok This is packaged in the cpu_utils This should be in the Dependencies of the package -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7219) Cannot display Cluster Settings after 4.4 Upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14173612#comment-14173612 ] Rohit Yadav commented on CLOUDSTACK-7219: - Upgraded from 4.3.1 to 4.4.1 using the docs: http://cloudstack-release-notes.readthedocs.org/en/latest/upgrade/upgrade-4.3.html Issue is not seen anymore. > Cannot display Cluster Settings after 4.4 Upgrade > - > > Key: CLOUDSTACK-7219 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7219 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, Management Server >Affects Versions: 4.4.0 > Environment: CentOS 6, KVM Hypervisor >Reporter: Prieur Leary >Priority: Blocker > Fix For: 4.4.1 > > Attachments: cluster.png > > > After upgrading MS to 4.4, when you to go: > Home -> Infrastructure -> Clusters -> Cluster 1 - > Settings > It does not display the settings underneath the column heading just, "ERROR". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6278) Baremetal Advanced Networking support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14173630#comment-14173630 ] ASF GitHub Bot commented on CLOUDSTACK-6278: Github user bhaisaab commented on the pull request: https://github.com/apache/cloudstack/pull/23#issuecomment-59347522 Mostly LGTM. I found a pattern that all the baremetal changes are causing issues, from the JIRA issue [1] this feature is in progress and I would only request @frank-zhang to: - Work in a separate feature branch and send a merge request when you think this feature is ready - Use better git commit messages as I'm unable to understand what Frank's is trying to do, all commits have CLOUDSTACK-6278 as short message which does not make sense to me - Avoid hardcoding stuff in the source code and avoid check in to master [1] https://issues.apache.org/jira/browse/CLOUDSTACK-6278 Thanks and regards. > Baremetal Advanced Networking support > - > > Key: CLOUDSTACK-6278 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6278 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Baremetal >Affects Versions: 4.5.0 >Reporter: frank zhang >Assignee: frank zhang > Fix For: 4.5.0 > > > functional spec link: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Baremetal+Advanced+Networking+Support -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7727) [Automation] [LXC] Various BVT test issues with LXC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14173653#comment-14173653 ] ASF subversion and git services commented on CLOUDSTACK-7727: - Commit 20d3cf1acc535c3380e52e92a4108444a0b593e3 in cloudstack's branch refs/heads/master from [~alexbre] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=20d3cf1 ] CLOUDSTACK-7727 Skip various BVT tests on LXC A number of BVT tests are not valid for LXC (e.g. migrating a VM), so this patch ensures they skip if LXC is in use. Signed-off-by: SrikanteswaraRao Talluri > [Automation] [LXC] Various BVT test issues with LXC > --- > > Key: CLOUDSTACK-7727 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7727 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.5.0 >Reporter: Alex Brett >Assignee: Alex Brett > Fix For: 4.5.0 > > > Various tests should skip when running with LXC due to the limitations it > imposes. The limitations list from > https://cwiki.apache.org/confluence/display/CLOUDSTACK/LXC+Enhancements is: > * No Console access > * No Live migration > * No migration across clusters > * No snapshot support > * No upload/download volume support > * No template creation from ROOT volume > * No ISO support for create Vm > This ticket is to modify the BVT tests to skip where appropriate. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7727) [Automation] [LXC] Various BVT test issues with LXC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14173652#comment-14173652 ] ASF subversion and git services commented on CLOUDSTACK-7727: - Commit d081efc647737d4fee106eda31767a061f885f69 in cloudstack's branch refs/heads/4.5 from [~alexbre] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d081efc ] CLOUDSTACK-7727 Skip various BVT tests on LXC A number of BVT tests are not valid for LXC (e.g. migrating a VM), so this patch ensures they skip if LXC is in use. Signed-off-by: SrikanteswaraRao Talluri > [Automation] [LXC] Various BVT test issues with LXC > --- > > Key: CLOUDSTACK-7727 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7727 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.5.0 >Reporter: Alex Brett >Assignee: Alex Brett > Fix For: 4.5.0 > > > Various tests should skip when running with LXC due to the limitations it > imposes. The limitations list from > https://cwiki.apache.org/confluence/display/CLOUDSTACK/LXC+Enhancements is: > * No Console access > * No Live migration > * No migration across clusters > * No snapshot support > * No upload/download volume support > * No template creation from ROOT volume > * No ISO support for create Vm > This ticket is to modify the BVT tests to skip where appropriate. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7741) UI login - 401 unable to verify user credentials
JF Vincent created CLOUDSTACK-7741: -- Summary: UI login - 401 unable to verify user credentials Key: CLOUDSTACK-7741 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7741 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Environment: Cloudstack CentOS installation - 2 management servers Reporter: JF Vincent Priority: Critical After a period of time (after the night, second occurence) , on one of our two servers, we're no more able to login. Google Chrome or Mozilla will hang after pressing the login button. After restarting the management server, problem disappear for many hours. Here is the only error log in the apiserver.log : 2014-10-16 14:46:04,181 INFO [a.c.c.a.ApiServer] (http-6443-exec-196:ctx-ad974072) 10.26.238.66 -- GET command=listCapabilities&response=json&sessionkey=null&_=1413463564799 401 unable to verify user credentials 2014-10-16 14:46:17,951 INFO [a.c.c.a.ApiServer] (http-6443-exec-198:ctx-d04a1fce) 10.26.238.66 -- GET command=listCapabilities&response=json&sessionkey=null&_=1413463578569 401 unable to verify user credentials 2014-10-16 14:49:10,622 INFO [a.c.c.a.ApiServer] (http-6443-exec-200:ctx-e0099661) 10.26.238.66 -- GET command=listCapabilities&response=json&sessionkey=null&_=1413463751221 401 unable to verify user credentials 2014-10-16 14:51:10,335 INFO [a.c.c.a.ApiServer] (http-6443-exec-204:ctx-a6f3bd15) 10.26.238.66 -- GET command=listCapabilities&response=json&sessionkey=null&_=1413463870965 401 unable to verify user credentials 2014-10-16 14:51:16,164 INFO [a.c.c.a.ApiServer] (http-6443-exec-203:ctx-624e7433) 10.26.238.66 -- GET command=listCapabilities&response=json&sessionkey=null&_=1413463876790 401 unable to verify user credentials while this server has the problem, on the other servr with is the backup we don't have the problem. The problem occurs for LDAP and local accounts. Regards. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7741) UI login - 401 unable to verify user credentials
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JF Vincent updated CLOUDSTACK-7741: --- Affects Version/s: (was: 4.2.0) 4.3.0 > UI login - 401 unable to verify user credentials > > > Key: CLOUDSTACK-7741 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7741 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.3.0 > Environment: Cloudstack CentOS installation - 2 management servers >Reporter: JF Vincent >Priority: Critical > > After a period of time (after the night, second occurence) , on one of our > two servers, we're no more able to login. Google Chrome or Mozilla will hang > after pressing the login button. > After restarting the management server, problem disappear for many hours. > Here is the only error log in the apiserver.log : > 2014-10-16 14:46:04,181 INFO [a.c.c.a.ApiServer] > (http-6443-exec-196:ctx-ad974072) 10.26.238.66 -- GET > command=listCapabilities&response=json&sessionkey=null&_=1413463564799 401 > unable to verify user credentials > 2014-10-16 14:46:17,951 INFO [a.c.c.a.ApiServer] > (http-6443-exec-198:ctx-d04a1fce) 10.26.238.66 -- GET > command=listCapabilities&response=json&sessionkey=null&_=1413463578569 401 > unable to verify user credentials > 2014-10-16 14:49:10,622 INFO [a.c.c.a.ApiServer] > (http-6443-exec-200:ctx-e0099661) 10.26.238.66 -- GET > command=listCapabilities&response=json&sessionkey=null&_=1413463751221 401 > unable to verify user credentials > 2014-10-16 14:51:10,335 INFO [a.c.c.a.ApiServer] > (http-6443-exec-204:ctx-a6f3bd15) 10.26.238.66 -- GET > command=listCapabilities&response=json&sessionkey=null&_=1413463870965 401 > unable to verify user credentials > 2014-10-16 14:51:16,164 INFO [a.c.c.a.ApiServer] > (http-6443-exec-203:ctx-624e7433) 10.26.238.66 -- GET > command=listCapabilities&response=json&sessionkey=null&_=1413463876790 401 > unable to verify user credentials > while this server has the problem, on the other servr with is the backup we > don't have the problem. > The problem occurs for LDAP and local accounts. > Regards. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7739) Add new vGPU types K160Q, K180Q, K280Q to the CloudStack UI
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14173734#comment-14173734 ] ASF subversion and git services commented on CLOUDSTACK-7739: - Commit 420d4e0da0307a8e7b0e530da1a5aedcc209516e in cloudstack's branch refs/heads/master from [~sanjay.tripathi] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=420d4e0 ] CLOUDSTACK-7739: Add new vGPU types K160Q, K180Q, K280Q to the CloudStack UI. > Add new vGPU types K160Q, K180Q, K280Q to the CloudStack UI > --- > > Key: CLOUDSTACK-7739 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7739 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.5.0 >Reporter: Sanjay Tripathi >Assignee: Sanjay Tripathi >Priority: Critical > Fix For: 4.5.0 > > > NVidia will be releasing a new vGPU driver, it will make new vGPU types > available on both XS 6.2 SP1 and XS 6.5. > Both the XenServer and the CloudStack API will pick these new types up, but > CloudStack GUI need some changes as the vGPU types are hard-coded here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7731) [UI] Improve VR groupby listing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174104#comment-14174104 ] ASF subversion and git services commented on CLOUDSTACK-7731: - Commit e225065ec2510a93a1f3f694050645687b2969d0 in cloudstack's branch refs/heads/4.5 from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e225065 ] CLOUDSTACK-7731: UI > Infrastructure > Virtual Routers > group by zone/pod/cluster view > listView > detailView > add View All link (i.e. "View all Virtual Routers"). > [UI] Improve VR groupby listing > --- > > Key: CLOUDSTACK-7731 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7731 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > > UI > Infrastructure -> Virtual Routers > group by view > (1) e.g. after selecting "group by zone",its lists only following fields: > Total of Virtual Router: > Upgrade is required: > Total of Virtual Routers that require upgrade: > People would like to see individual router details in select view also, > similar to the view without group by. > (2) Filtering also should be improved to allow search by version. Otherwise, > in large deployment it is hard to find routers which are not upgraded. > listRouters API already supports listing by version, zone, pod, cluster, > account and domain -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7731) [UI] Improve VR groupby listing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174105#comment-14174105 ] ASF subversion and git services commented on CLOUDSTACK-7731: - Commit c49a09fad0ad830a3ce56511da5cd568d56c594c in cloudstack's branch refs/heads/4.5 from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c49a09f ] CLOUDSTACK-7731: UI > Infrastructure > Virtual Routers > group by account view > listView > detailView > add View All link (i.e. "View all Virtual Routers"). > [UI] Improve VR groupby listing > --- > > Key: CLOUDSTACK-7731 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7731 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > > UI > Infrastructure -> Virtual Routers > group by view > (1) e.g. after selecting "group by zone",its lists only following fields: > Total of Virtual Router: > Upgrade is required: > Total of Virtual Routers that require upgrade: > People would like to see individual router details in select view also, > similar to the view without group by. > (2) Filtering also should be improved to allow search by version. Otherwise, > in large deployment it is hard to find routers which are not upgraded. > listRouters API already supports listing by version, zone, pod, cluster, > account and domain -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7736) UI - listView widget - select view dropdown on top of listView - prefilter() - include original args.context when passing it to prefilter().
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174108#comment-14174108 ] ASF subversion and git services commented on CLOUDSTACK-7736: - Commit f8cbd6ad46f5e75de3354ffe4dc646b819aa40a1 in cloudstack's branch refs/heads/4.5 from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f8cbd6a ] CLOUDSTACK-7736: UI - listView widget - select view dropdown on top of listView - prefilter() - include original args.context when passing it to prefilter(). > UI - listView widget - select view dropdown on top of listView - prefilter() > - include original args.context when passing it to prefilter(). > > > Key: CLOUDSTACK-7736 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7736 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7731) [UI] Improve VR groupby listing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174112#comment-14174112 ] ASF subversion and git services commented on CLOUDSTACK-7731: - Commit 5e165d499e5e81f6941e74a60b628a544523780a in cloudstack's branch refs/heads/4.5 from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5e165d4 ] CLOUDSTACK-7731: UI > Infrastructure > Virtual Routers > group by XXX view > listView > detailView > add View All link > not show "group by XXX" in select view dropdown. > [UI] Improve VR groupby listing > --- > > Key: CLOUDSTACK-7731 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7731 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > > UI > Infrastructure -> Virtual Routers > group by view > (1) e.g. after selecting "group by zone",its lists only following fields: > Total of Virtual Router: > Upgrade is required: > Total of Virtual Routers that require upgrade: > People would like to see individual router details in select view also, > similar to the view without group by. > (2) Filtering also should be improved to allow search by version. Otherwise, > in large deployment it is hard to find routers which are not upgraded. > listRouters API already supports listing by version, zone, pod, cluster, > account and domain -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7731) [UI] Improve VR groupby listing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174114#comment-14174114 ] ASF subversion and git services commented on CLOUDSTACK-7731: - Commit be60e46e1efad93cb3c26bcf9ec9ee501239ffdf in cloudstack's branch refs/heads/4.5 from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=be60e46 ] CLOUDSTACK-7731: UI > Infrastructure > Virtual Routers > group by XXX view > listView > detailView > add View All link > show read-only text "group by zone/pod/cluster/account" in select view area. > [UI] Improve VR groupby listing > --- > > Key: CLOUDSTACK-7731 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7731 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > > UI > Infrastructure -> Virtual Routers > group by view > (1) e.g. after selecting "group by zone",its lists only following fields: > Total of Virtual Router: > Upgrade is required: > Total of Virtual Routers that require upgrade: > People would like to see individual router details in select view also, > similar to the view without group by. > (2) Filtering also should be improved to allow search by version. Otherwise, > in large deployment it is hard to find routers which are not upgraded. > listRouters API already supports listing by version, zone, pod, cluster, > account and domain -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7742) Xenserver HA - SSVM failing to start since it is running out of management ip address
Sangeetha Hariharan created CLOUDSTACK-7742: --- Summary: Xenserver HA - SSVM failing to start since it is running out of management ip address Key: CLOUDSTACK-7742 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7742 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.5.0 Environment: Build from master Reporter: Sangeetha Hariharan HA - SSVM failing to start since it is running out of management ip address Set up: Cluster with 3 Xenserver hosts. I am executing host HA scenarios where host is being brought down ( or simulating contol path network failure / storage network failure). After couple of such scenarios , i see that the SSVM fails to start as part of HA the reason being running out of management nic: management server logs: 014-10-16 12:15:44,311 DEBUG [c.c.u.d.T.Transaction] (Work-Job-Executor-106:ctx-323991ca job-771/job-943 ctx-3a2e9ed6) Rolling back the transaction: Time = 1 Name = Work-Job-Executor-106; called by -TransactionLegacy.rollback:902-DataCenterIpAddressDaoImpl.takeIpAddress:61-GeneratedMethodAccessor493.invoke:-1-DelegatingMethodAccessorImpl.invoke:43-Method.invoke:606-AopUtils.invokeJoinpointUsingReflection:317-ReflectiveMethodInvocation.invokeJoinpoint:183-ReflectiveMethodInvocation.proceed:150-TransactionContextInterceptor.invoke:34-ReflectiveMethodInvocation.proceed:161-ExposeInvocationInterceptor.invoke:91-ReflectiveMethodInvocation.proceed:172 2014-10-16 12:15:44,312 INFO [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-106:ctx-323991ca job-771/job-943 ctx-3a2e9ed6) Insufficient capacity com.cloud.exception.InsufficientAddressCapacityException: Unable to get a management ip addressScope=interface com.cloud.dc.Pod; id=1 at com.cloud.network.guru.PodBasedNetworkGuru.reserve(PodBasedNetworkGuru.java:123) at com.cloud.network.guru.StorageNetworkGuru.reserve(StorageNetworkGuru.java:122) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepareNic(NetworkOrchestrator.java:1338) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepare(NetworkOrchestrator.java:1309) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:970) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:4590) at sun.reflect.GeneratedMethodAccessor210.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107) at com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:4746) at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:513) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:470) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) 2014-10-16 12:15:44,324 DEBUG [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-106:ctx-323991ca job-771/job-943 ctx-3a2e9ed6) Cleaning up resources for the vm VM[SecondaryStorageVm|s-115-VM] in Starting state There are 2 issues here: 1. Some of the SSVMs that are in destroyed state still have not released the management Ips back to the freepool. 2. Some of these destroyed SSVMs have 2 management ip addresses associated with it . why is this the case? 3. I still see 1 management ip address that is free , but SSVM is still not able to come up. mysql> select id,name,state from vm_instance where id in (1,7,18,71); ++-+---+ | id | name| state
[jira] [Updated] (CLOUDSTACK-7742) Xenserver HA - SSVM failing to start since it is running out of management ip address
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan updated CLOUDSTACK-7742: Attachment: ssvm-fail.rar > Xenserver HA - SSVM failing to start since it is running out of management ip > address > -- > > Key: CLOUDSTACK-7742 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7742 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.0 > Environment: Build from master >Reporter: Sangeetha Hariharan > Attachments: ssvm-fail.rar > > > HA - SSVM failing to start since it is running out of management ip address > Set up: > Cluster with 3 Xenserver hosts. > I am executing host HA scenarios where host is being brought down ( or > simulating contol path network failure / storage network failure). > After couple of such scenarios , i see that the SSVM fails to start as part > of HA the reason being running out of management nic: > management server logs: > 014-10-16 12:15:44,311 DEBUG [c.c.u.d.T.Transaction] > (Work-Job-Executor-106:ctx-323991ca job-771/job-943 ctx-3a2e9ed6) Rolling > back the transaction: Time = 1 Name = Work-Job-Executor-106; called by > -TransactionLegacy.rollback:902-DataCenterIpAddressDaoImpl.takeIpAddress:61-GeneratedMethodAccessor493.invoke:-1-DelegatingMethodAccessorImpl.invoke:43-Method.invoke:606-AopUtils.invokeJoinpointUsingReflection:317-ReflectiveMethodInvocation.invokeJoinpoint:183-ReflectiveMethodInvocation.proceed:150-TransactionContextInterceptor.invoke:34-ReflectiveMethodInvocation.proceed:161-ExposeInvocationInterceptor.invoke:91-ReflectiveMethodInvocation.proceed:172 > 2014-10-16 12:15:44,312 INFO [c.c.v.VirtualMachineManagerImpl] > (Work-Job-Executor-106:ctx-323991ca job-771/job-943 ctx-3a2e9ed6) > Insufficient capacity > com.cloud.exception.InsufficientAddressCapacityException: Unable to get a > management ip addressScope=interface com.cloud.dc.Pod; id=1 > at > com.cloud.network.guru.PodBasedNetworkGuru.reserve(PodBasedNetworkGuru.java:123) > at > com.cloud.network.guru.StorageNetworkGuru.reserve(StorageNetworkGuru.java:122) > at > org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepareNic(NetworkOrchestrator.java:1338) > at > org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepare(NetworkOrchestrator.java:1309) > at > com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:970) > at > com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:4590) > at sun.reflect.GeneratedMethodAccessor210.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107) > at > com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:4746) > at > com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102) > at > org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:513) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) > at > org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:470) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > 2014-10-16 12:15:44,324 DEBUG [c.c.v.VirtualMachineManagerImpl] > (Work-Job-Executor-106:ctx-323991ca job-771/job-943 ctx-3a2e9ed6) Cleaning up > resources for the vm VM[SecondaryStorageVm|s-115-VM] in Starting state > There are 2 issues here: > 1. Some of the SSVMs that are in destroyed
[jira] [Commented] (CLOUDSTACK-7731) [UI] Improve VR groupby listing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174131#comment-14174131 ] ASF subversion and git services commented on CLOUDSTACK-7731: - Commit 314a7fe62b626d79f612d70ccf56d692a92f5774 in cloudstack's branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=314a7fe ] CLOUDSTACK-7731: UI > Infrastructure > Virtual Routers > group by zone/pod/cluster view > listView > detailView > add View All link (i.e. "View all Virtual Routers"). > [UI] Improve VR groupby listing > --- > > Key: CLOUDSTACK-7731 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7731 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > > UI > Infrastructure -> Virtual Routers > group by view > (1) e.g. after selecting "group by zone",its lists only following fields: > Total of Virtual Router: > Upgrade is required: > Total of Virtual Routers that require upgrade: > People would like to see individual router details in select view also, > similar to the view without group by. > (2) Filtering also should be improved to allow search by version. Otherwise, > in large deployment it is hard to find routers which are not upgraded. > listRouters API already supports listing by version, zone, pod, cluster, > account and domain -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7731) [UI] Improve VR groupby listing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174134#comment-14174134 ] ASF subversion and git services commented on CLOUDSTACK-7731: - Commit 8fb7cfae0ce3d4908ad1d1da9072a2ed6585e68f in cloudstack's branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8fb7cfa ] CLOUDSTACK-7731: UI > Infrastructure > Virtual Routers > group by account view > listView > detailView > add View All link (i.e. "View all Virtual Routers"). > [UI] Improve VR groupby listing > --- > > Key: CLOUDSTACK-7731 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7731 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > > UI > Infrastructure -> Virtual Routers > group by view > (1) e.g. after selecting "group by zone",its lists only following fields: > Total of Virtual Router: > Upgrade is required: > Total of Virtual Routers that require upgrade: > People would like to see individual router details in select view also, > similar to the view without group by. > (2) Filtering also should be improved to allow search by version. Otherwise, > in large deployment it is hard to find routers which are not upgraded. > listRouters API already supports listing by version, zone, pod, cluster, > account and domain -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7736) UI - listView widget - select view dropdown on top of listView - prefilter() - include original args.context when passing it to prefilter().
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174135#comment-14174135 ] ASF subversion and git services commented on CLOUDSTACK-7736: - Commit a3eaff8bb689f6d41e85acf8c424a96606edbb05 in cloudstack's branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a3eaff8 ] CLOUDSTACK-7736: UI - listView widget - select view dropdown on top of listView - prefilter() - include original args.context when passing it to prefilter(). > UI - listView widget - select view dropdown on top of listView - prefilter() > - include original args.context when passing it to prefilter(). > > > Key: CLOUDSTACK-7736 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7736 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7731) [UI] Improve VR groupby listing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174136#comment-14174136 ] ASF subversion and git services commented on CLOUDSTACK-7731: - Commit 7004deb528657c7e5403118926836b7fd19717c0 in cloudstack's branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7004deb ] CLOUDSTACK-7731: UI > Infrastructure > Virtual Routers > group by XXX view > listView > detailView > add View All link > not show "group by XXX" in select view dropdown. > [UI] Improve VR groupby listing > --- > > Key: CLOUDSTACK-7731 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7731 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > > UI > Infrastructure -> Virtual Routers > group by view > (1) e.g. after selecting "group by zone",its lists only following fields: > Total of Virtual Router: > Upgrade is required: > Total of Virtual Routers that require upgrade: > People would like to see individual router details in select view also, > similar to the view without group by. > (2) Filtering also should be improved to allow search by version. Otherwise, > in large deployment it is hard to find routers which are not upgraded. > listRouters API already supports listing by version, zone, pod, cluster, > account and domain -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7731) [UI] Improve VR groupby listing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174138#comment-14174138 ] ASF subversion and git services commented on CLOUDSTACK-7731: - Commit 6239447f0538b9f0408afc19143c592ba37e6783 in cloudstack's branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6239447 ] CLOUDSTACK-7731: UI > Infrastructure > Virtual Routers > group by XXX view > listView > detailView > add View All link > show read-only text "group by zone/pod/cluster/account" in select view area. > [UI] Improve VR groupby listing > --- > > Key: CLOUDSTACK-7731 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7731 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > > UI > Infrastructure -> Virtual Routers > group by view > (1) e.g. after selecting "group by zone",its lists only following fields: > Total of Virtual Router: > Upgrade is required: > Total of Virtual Routers that require upgrade: > People would like to see individual router details in select view also, > similar to the view without group by. > (2) Filtering also should be improved to allow search by version. Otherwise, > in large deployment it is hard to find routers which are not upgraded. > listRouters API already supports listing by version, zone, pod, cluster, > account and domain -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7736) UI - listView widget - select view dropdown on top of listView - prefilter() - include original args.context when passing it to prefilter().
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang resolved CLOUDSTACK-7736. -- Resolution: Fixed > UI - listView widget - select view dropdown on top of listView - prefilter() > - include original args.context when passing it to prefilter(). > > > Key: CLOUDSTACK-7736 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7736 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-7736) UI - listView widget - select view dropdown on top of listView - prefilter() - include original args.context when passing it to prefilter().
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang closed CLOUDSTACK-7736. > UI - listView widget - select view dropdown on top of listView - prefilter() > - include original args.context when passing it to prefilter(). > > > Key: CLOUDSTACK-7736 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7736 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7742) Xenserver HA - SSVM failing to start since it is running out of management ip address
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan updated CLOUDSTACK-7742: Description: HA - SSVM failing to start since it is running out of management ip address Set up: Cluster with 3 Xenserver hosts. I am executing host HA scenarios where host is being brought down ( or simulating contol path network failure / storage network failure). After couple of such scenarios , i see that the SSVM fails to start as part of HA the reason being running out of management nic: management server logs: 014-10-16 12:15:44,311 DEBUG [c.c.u.d.T.Transaction] (Work-Job-Executor-106:ctx-323991ca job-771/job-943 ctx-3a2e9ed6) Rolling back the transaction: Time = 1 Name = Work-Job-Executor-106; called by -TransactionLegacy.rollback:902-DataCenterIpAddressDaoImpl.takeIpAddress:61-GeneratedMethodAccessor493.invoke:-1-DelegatingMethodAccessorImpl.invoke:43-Method.invoke:606-AopUtils.invokeJoinpointUsingReflection:317-ReflectiveMethodInvocation.invokeJoinpoint:183-ReflectiveMethodInvocation.proceed:150-TransactionContextInterceptor.invoke:34-ReflectiveMethodInvocation.proceed:161-ExposeInvocationInterceptor.invoke:91-ReflectiveMethodInvocation.proceed:172 2014-10-16 12:15:44,312 INFO [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-106:ctx-323991ca job-771/job-943 ctx-3a2e9ed6) Insufficient capacity com.cloud.exception.InsufficientAddressCapacityException: Unable to get a management ip addressScope=interface com.cloud.dc.Pod; id=1 at com.cloud.network.guru.PodBasedNetworkGuru.reserve(PodBasedNetworkGuru.java:123) at com.cloud.network.guru.StorageNetworkGuru.reserve(StorageNetworkGuru.java:122) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepareNic(NetworkOrchestrator.java:1338) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepare(NetworkOrchestrator.java:1309) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:970) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:4590) at sun.reflect.GeneratedMethodAccessor210.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107) at com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:4746) at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:513) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:470) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) 2014-10-16 12:15:44,324 DEBUG [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-106:ctx-323991ca job-771/job-943 ctx-3a2e9ed6) Cleaning up resources for the vm VM[SecondaryStorageVm|s-115-VM] in Starting state There are 2 issues here: 1. Some of the SSVMs that are in destroyed state still have not released the management Ips back to the freepool of management ip address. 2. When CPVM is stopped , seems like the ipaddress associated with it has not been released to the freepool of management ip address. mysql> select id,name,state from vm_instance where id in (1,7,18,71); ++-+---+ | id | name| state | ++-+---+ | 1 | v-1-VM | Running | | 7 | s-7-VM | Destroyed | | 18 | s-18-VM | Destroyed | | 71 | s-71-VM | Destroyed | ++-+---+ 4 rows in set (0.00 sec) mysql> select instance_id from nics where id in (select nic_id from op_dc_ip_address_alloc where taken is not null); +-+ | instance_id | +-+ | 1 | | 7 | |
[jira] [Updated] (CLOUDSTACK-7731) [UI] Improve VR groupby listing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-7731: - Description: UI > Infrastructure -> Virtual Routers > group by view e.g. after selecting "group by zone",its lists only following fields: Total of Virtual Router: Upgrade is required: Total of Virtual Routers that require upgrade: People would like to see individual router details in select view also, similar to the view without group by. was: UI > Infrastructure -> Virtual Routers > group by view (1) e.g. after selecting "group by zone",its lists only following fields: Total of Virtual Router: Upgrade is required: Total of Virtual Routers that require upgrade: People would like to see individual router details in select view also, similar to the view without group by. (2) Filtering also should be improved to allow search by version. Otherwise, in large deployment it is hard to find routers which are not upgraded. listRouters API already supports listing by version, zone, pod, cluster, account and domain > [UI] Improve VR groupby listing > --- > > Key: CLOUDSTACK-7731 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7731 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > > UI > Infrastructure -> Virtual Routers > group by view > e.g. after selecting "group by zone",its lists only following fields: > Total of Virtual Router: > Upgrade is required: > Total of Virtual Routers that require upgrade: > People would like to see individual router details in select view also, > similar to the view without group by. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7731) UI > Infrastructure > Virtual Routers > group by zone/pod/cluster/account view > listView > detailView > add View All link (i.e. "View all Virtual Routers").
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang resolved CLOUDSTACK-7731. -- Resolution: Fixed > UI > Infrastructure > Virtual Routers > group by zone/pod/cluster/account > view > listView > detailView > add View All link (i.e. "View all Virtual > Routers"). > - > > Key: CLOUDSTACK-7731 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7731 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > > UI > Infrastructure -> Virtual Routers > group by view > e.g. after selecting "group by zone",its lists only following fields: > Total of Virtual Router: > Upgrade is required: > Total of Virtual Routers that require upgrade: > People would like to see individual router details in select view also, > similar to the view without group by. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7731) UI > Infrastructure > Virtual Routers > group by zone/pod/cluster/account view > listView > detailView > add View All link (i.e. "View all Virtual Routers").
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-7731: - Summary: UI > Infrastructure > Virtual Routers > group by zone/pod/cluster/account view > listView > detailView > add View All link (i.e. "View all Virtual Routers"). (was: [UI] Improve VR groupby listing) > UI > Infrastructure > Virtual Routers > group by zone/pod/cluster/account > view > listView > detailView > add View All link (i.e. "View all Virtual > Routers"). > - > > Key: CLOUDSTACK-7731 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7731 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > > UI > Infrastructure -> Virtual Routers > group by view > e.g. after selecting "group by zone",its lists only following fields: > Total of Virtual Router: > Upgrade is required: > Total of Virtual Routers that require upgrade: > People would like to see individual router details in select view also, > similar to the view without group by. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-7731) UI > Infrastructure > Virtual Routers > group by zone/pod/cluster/account view > listView > detailView > add View All link (i.e. "View all Virtual Routers").
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang closed CLOUDSTACK-7731. > UI > Infrastructure > Virtual Routers > group by zone/pod/cluster/account > view > listView > detailView > add View All link (i.e. "View all Virtual > Routers"). > - > > Key: CLOUDSTACK-7731 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7731 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > > UI > Infrastructure -> Virtual Routers > group by view > e.g. after selecting "group by zone",its lists only following fields: > Total of Virtual Router: > Upgrade is required: > Total of Virtual Routers that require upgrade: > People would like to see individual router details in select view also, > similar to the view without group by. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7743) [Automation][KVM] Migration of VM failed due to LibvirtException: Cannot get interface MTU on 'breth0-3011': No such device"
Chandan Purushothama created CLOUDSTACK-7743:
Summary: [Automation][KVM] Migration of VM failed due to
LibvirtException: Cannot get interface MTU on 'breth0-3011': No such device"
Key: CLOUDSTACK-7743
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7743
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Automation, KVM
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: edison su
Priority: Critical
Fix For: 4.5.0
Use Case:
1. VM Migration from One Host to Another - Fails currently due to
LibvirtException
=
LibvirtException:
=
{noformat}
2014-10-13 19:26:36,930 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-65:ctx-3cedea49 job-197/job-198 ctx-066f6b6a) Seq
1-8599060538510540956: Sending { Cmd , MgmtId: 86095456037899, via:
1(cl07-11), Ver: v1, Flags: 100111,
[{"com.cloud.agent.api.PrepareForMigrationCommand":{"vm":{"id":32,"name":"i-13-32-VM","type":"User","cpus":1,"minSpeed":100,"maxSpeed":100,"minRam":268435456,"maxRam":268435456,"arch":"x86_64","os":"CentOS
5.5 (64-bit)","platformEmulator":"CentOS
5.5","bootArgs":"","enableHA":false,"limitCpuUse":false,"enableDynamicallyScaleVm":false,"vncPassword":"UgJEzSDcfsSllX2nVfeMqQ==","params":{},"uuid":"fe6ef18e-37da-4730-9794-03760f325082","disks":[{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"c031588c-51be-4be8-9c30-4535b3428d2f","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"e3ce1672-a3c4-3396-a86b-025c13ee2b8c","id":1,"poolType":"NetworkFilesystem","host":"10.220.128.55","path":"/vol/xenrtnfs/861825-jkTv6e","port":2049,"url":"NetworkFilesystem://10.220.128.55/vol/xenrtnfs/861825-jkTv6e/?ROLE=Primary&STOREUUID=e3ce1672-a3c4-3396-a86b-025c13ee2b8c"}},"name":"ROOT-32","size":8589934592,"path":"c031588c-51be-4be8-9c30-4535b3428d2f","volumeId":35,"vmName":"i-13-32-VM","accountId":13,"format":"QCOW2","provisioningType":"THIN","id":35,"deviceId":0,"hypervisorType":"KVM"}},"diskSeq":0,"path":"c031588c-51be-4be8-9c30-4535b3428d2f","type":"ROOT","_details":{"managed":"false","storagePort":"2049","storageHost":"10.220.128.55","volumeSize":"8589934592"}},{"data":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"id":0,"format":"ISO","accountId":0,"hvm":false}},"diskSeq":3,"type":"ISO"}],"nics":[{"deviceId":0,"networkRateMbps":200,"defaultNic":true,"pxeDisable":false,"nicUuid":"47696919-1d62-416f-9f2c-1bfa72ef2330","uuid":"85218f30-0f90-4d63-8553-b8431cdf60aa","ip":"192.168.200.220","netmask":"255.255.255.0","gateway":"192.168.200.1","mac":"02:00:7a:45:00:05","dns1":"10.220.128.11","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://3011","isolationUri":"vlan://3011","isSecurityGroupEnabled":false}]},"wait":0}}]
}
2014-10-13 19:26:36,993 DEBUG [c.c.a.t.Request] (AgentManager-Handler-19:null)
Seq 1-8599060538510540956: Processing: { Ans: , MgmtId: 86095456037899, via:
1, Ver: v1, Flags: 110,
[{"com.cloud.agent.api.PrepareForMigrationAnswer":{"result":true,"wait":0}}] }
2014-10-13 19:26:36,993 DEBUG [c.c.a.m.AgentAttache]
(AgentManager-Handler-19:null) Seq 1-8599060538510540956: No more commands found
2014-10-13 19:26:36,993 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-65:ctx-3cedea49 job-197/job-198 ctx-066f6b6a) Seq
1-8599060538510540956: Received: { Ans: , MgmtId: 86095456037899, via: 1, Ver:
v1, Flags: 110, { PrepareForMigrationAnswer } }
2014-10-13 19:26:37,000 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-65:ctx-3cedea49 job-197/job-198 ctx-066f6b6a) VM state
transitted from :Running to Migrating with event: MigrationRequestedvm's
original host id: 2 new host id: 1 host id before state transition: 2
2014-10-13 19:26:37,005 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-65:ctx-3cedea49 job-197/job-198 ctx-066f6b6a) Hosts's actual
total CPU: 38400 and CPU after applying overprovisioning: 38400
2014-10-13 19:26:37,005 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-65:ctx-3cedea49 job-197/job-198 ctx-066f6b6a) We are
allocating VM, increasing the used capacity of this host:1
2014-10-13 19:26:37,005 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-65:ctx-3cedea49 job-197/job-198 ctx-066f6b6a) Current Used
CPU: 2500 , Free CPU:35900 ,Requested CPU: 100
2014-10-13 19:26:37,005 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-65:ctx-3cedea49 job-197/job-198 ctx-066f6b6a) Current Used
RAM: 2818572288 , Free RAM:13891837952 ,Requested RAM: 268435456
2014-10-13 19:26:37,005 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-65:ctx-3cedea49 job-197/job-198 ctx-066f6b6a) CPU STATS
after allocation: for host: 1, old used: 2500, old reserved: 0, actual total:
38400, total with overprovisioning: 38400; new used:2600, reserved:0; requested
cp
[jira] [Updated] (CLOUDSTACK-7743) [Automation][KVM] Migration of VM failed due to LibvirtException: Cannot get interface MTU on 'breth0-3011': No such device"
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan Purushothama updated CLOUDSTACK-7743:
-
Attachment: management-server.zip
> [Automation][KVM] Migration of VM failed due to LibvirtException: Cannot get
> interface MTU on 'breth0-3011': No such device"
>
>
> Key: CLOUDSTACK-7743
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7743
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation, KVM
>Affects Versions: 4.5.0
>Reporter: Chandan Purushothama
>Assignee: edison su
>Priority: Critical
> Fix For: 4.5.0
>
> Attachments: management-server.zip
>
>
> Use Case:
> 1. VM Migration from One Host to Another - Fails currently due to
> LibvirtException
> =
> LibvirtException:
> =
> {noformat}
> 2014-10-13 19:26:36,930 DEBUG [c.c.a.t.Request]
> (Work-Job-Executor-65:ctx-3cedea49 job-197/job-198 ctx-066f6b6a) Seq
> 1-8599060538510540956: Sending { Cmd , MgmtId: 86095456037899, via:
> 1(cl07-11), Ver: v1, Flags: 100111,
> [{"com.cloud.agent.api.PrepareForMigrationCommand":{"vm":{"id":32,"name":"i-13-32-VM","type":"User","cpus":1,"minSpeed":100,"maxSpeed":100,"minRam":268435456,"maxRam":268435456,"arch":"x86_64","os":"CentOS
> 5.5 (64-bit)","platformEmulator":"CentOS
> 5.5","bootArgs":"","enableHA":false,"limitCpuUse":false,"enableDynamicallyScaleVm":false,"vncPassword":"UgJEzSDcfsSllX2nVfeMqQ==","params":{},"uuid":"fe6ef18e-37da-4730-9794-03760f325082","disks":[{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"c031588c-51be-4be8-9c30-4535b3428d2f","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"e3ce1672-a3c4-3396-a86b-025c13ee2b8c","id":1,"poolType":"NetworkFilesystem","host":"10.220.128.55","path":"/vol/xenrtnfs/861825-jkTv6e","port":2049,"url":"NetworkFilesystem://10.220.128.55/vol/xenrtnfs/861825-jkTv6e/?ROLE=Primary&STOREUUID=e3ce1672-a3c4-3396-a86b-025c13ee2b8c"}},"name":"ROOT-32","size":8589934592,"path":"c031588c-51be-4be8-9c30-4535b3428d2f","volumeId":35,"vmName":"i-13-32-VM","accountId":13,"format":"QCOW2","provisioningType":"THIN","id":35,"deviceId":0,"hypervisorType":"KVM"}},"diskSeq":0,"path":"c031588c-51be-4be8-9c30-4535b3428d2f","type":"ROOT","_details":{"managed":"false","storagePort":"2049","storageHost":"10.220.128.55","volumeSize":"8589934592"}},{"data":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"id":0,"format":"ISO","accountId":0,"hvm":false}},"diskSeq":3,"type":"ISO"}],"nics":[{"deviceId":0,"networkRateMbps":200,"defaultNic":true,"pxeDisable":false,"nicUuid":"47696919-1d62-416f-9f2c-1bfa72ef2330","uuid":"85218f30-0f90-4d63-8553-b8431cdf60aa","ip":"192.168.200.220","netmask":"255.255.255.0","gateway":"192.168.200.1","mac":"02:00:7a:45:00:05","dns1":"10.220.128.11","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://3011","isolationUri":"vlan://3011","isSecurityGroupEnabled":false}]},"wait":0}}]
> }
> 2014-10-13 19:26:36,993 DEBUG [c.c.a.t.Request]
> (AgentManager-Handler-19:null) Seq 1-8599060538510540956: Processing: { Ans:
> , MgmtId: 86095456037899, via: 1, Ver: v1, Flags: 110,
> [{"com.cloud.agent.api.PrepareForMigrationAnswer":{"result":true,"wait":0}}] }
> 2014-10-13 19:26:36,993 DEBUG [c.c.a.m.AgentAttache]
> (AgentManager-Handler-19:null) Seq 1-8599060538510540956: No more commands
> found
> 2014-10-13 19:26:36,993 DEBUG [c.c.a.t.Request]
> (Work-Job-Executor-65:ctx-3cedea49 job-197/job-198 ctx-066f6b6a) Seq
> 1-8599060538510540956: Received: { Ans: , MgmtId: 86095456037899, via: 1,
> Ver: v1, Flags: 110, { PrepareForMigrationAnswer } }
> 2014-10-13 19:26:37,000 DEBUG [c.c.c.CapacityManagerImpl]
> (Work-Job-Executor-65:ctx-3cedea49 job-197/job-198 ctx-066f6b6a) VM state
> transitted from :Running to Migrating with event: MigrationRequestedvm's
> original host id: 2 new host id: 1 host id before state transition: 2
> 2014-10-13 19:26:37,005 DEBUG [c.c.c.CapacityManagerImpl]
> (Work-Job-Executor-65:ctx-3cedea49 job-197/job-198 ctx-066f6b6a) Hosts's
> actual total CPU: 38400 and CPU after applying overprovisioning: 38400
> 2014-10-13 19:26:37,005 DEBUG [c.c.c.CapacityManagerImpl]
> (Work-Job-Executor-65:ctx-3cedea49 job-197/job-198 ctx-066f6b6a) We are
> allocating VM, increasing the used capacity of this host:1
> 2014-10-13 19:26:37,005 DEBUG [c.c.c.CapacityManagerImpl]
> (Work-Job-Executor-65:ctx-3cedea49 job-197/job-198 ctx-066f6b6a) Current Used
> CPU: 2500 , Free CPU:35900 ,Requested CPU: 100
> 2014-10-13 19:26:37,005 DEBUG [c.c.c.CapacityManagerImpl]
> (Work-Job-Executor-6
[jira] [Created] (CLOUDSTACK-7744) Changing Service Offering shows "Instance Scaled Up" even if offering scaled down
Jessica Wang created CLOUDSTACK-7744: Summary: Changing Service Offering shows "Instance Scaled Up" even if offering scaled down Key: CLOUDSTACK-7744 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7744 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang 1. Create a VM Instance; then make sure it is powered off. 2. View the VM Instance details, then press the "Change Service Offering" button. 3. Select a new service offering then press "OK". Expected: The notification should be generic, e.g. "Change Service Offering". Actual: The resulting notification shown upon completion is "Instance Scaled Up", even if the new service offering is smaller/weaker than what the VM previously had. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7744) Changing Service Offering incorretly shows "Instance Scaled Up" even if offering scaled down
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-7744: - Summary: Changing Service Offering incorretly shows "Instance Scaled Up" even if offering scaled down (was: Changing Service Offering shows "Instance Scaled Up" even if offering scaled down) > Changing Service Offering incorretly shows "Instance Scaled Up" even if > offering scaled down > > > Key: CLOUDSTACK-7744 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7744 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > > 1. Create a VM Instance; then make sure it is powered off. > 2. View the VM Instance details, then press the "Change Service Offering" > button. > 3. Select a new service offering then press "OK". > Expected: The notification should be generic, e.g. "Change Service Offering". > Actual: The resulting notification shown upon completion is "Instance Scaled > Up", even if the new service offering is smaller/weaker than what the VM > previously had. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7744) Changing Service Offering incorretly shows "Instance Scaled Up" even if offering scaled down
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174312#comment-14174312 ] ASF subversion and git services commented on CLOUDSTACK-7744: - Commit 13decd4c85e540337fdf1e46eb367f78d691b4ab in cloudstack's branch refs/heads/4.5 from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=13decd4 ] CLOUDSTACK-7744: UI > Instances > detailView > Change Service Offering > show generic notification. > Changing Service Offering incorretly shows "Instance Scaled Up" even if > offering scaled down > > > Key: CLOUDSTACK-7744 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7744 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > > 1. Create a VM Instance; then make sure it is powered off. > 2. View the VM Instance details, then press the "Change Service Offering" > button. > 3. Select a new service offering then press "OK". > Expected: The notification should be generic, e.g. "Change Service Offering". > Actual: The resulting notification shown upon completion is "Instance Scaled > Up", even if the new service offering is smaller/weaker than what the VM > previously had. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7744) Changing Service Offering incorretly shows "Instance Scaled Up" even if offering scaled down
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang resolved CLOUDSTACK-7744. -- Resolution: Fixed > Changing Service Offering incorretly shows "Instance Scaled Up" even if > offering scaled down > > > Key: CLOUDSTACK-7744 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7744 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > > 1. Create a VM Instance; then make sure it is powered off. > 2. View the VM Instance details, then press the "Change Service Offering" > button. > 3. Select a new service offering then press "OK". > Expected: The notification should be generic, e.g. "Change Service Offering". > Actual: The resulting notification shown upon completion is "Instance Scaled > Up", even if the new service offering is smaller/weaker than what the VM > previously had. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7744) Changing Service Offering incorretly shows "Instance Scaled Up" even if offering scaled down
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174314#comment-14174314 ] ASF subversion and git services commented on CLOUDSTACK-7744: - Commit c10f8a10efdbf479f2b8c9784d4976e3100b3cde in cloudstack's branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c10f8a1 ] CLOUDSTACK-7744: UI > Instances > detailView > Change Service Offering > show generic notification. > Changing Service Offering incorretly shows "Instance Scaled Up" even if > offering scaled down > > > Key: CLOUDSTACK-7744 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7744 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > > 1. Create a VM Instance; then make sure it is powered off. > 2. View the VM Instance details, then press the "Change Service Offering" > button. > 3. Select a new service offering then press "OK". > Expected: The notification should be generic, e.g. "Change Service Offering". > Actual: The resulting notification shown upon completion is "Instance Scaled > Up", even if the new service offering is smaller/weaker than what the VM > previously had. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7744) Changing Service Offering incorretly shows "Instance Scaled Up" even if offering scaled down
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-7744: - Affects Version/s: 4.5.0 > Changing Service Offering incorretly shows "Instance Scaled Up" even if > offering scaled down > > > Key: CLOUDSTACK-7744 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7744 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > Fix For: 4.5.0 > > > 1. Create a VM Instance; then make sure it is powered off. > 2. View the VM Instance details, then press the "Change Service Offering" > button. > 3. Select a new service offering then press "OK". > Expected: The notification should be generic, e.g. "Change Service Offering". > Actual: The resulting notification shown upon completion is "Instance Scaled > Up", even if the new service offering is smaller/weaker than what the VM > previously had. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7744) Changing Service Offering incorretly shows "Instance Scaled Up" even if offering scaled down
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-7744: - Affects Version/s: (was: 4.5.0) > Changing Service Offering incorretly shows "Instance Scaled Up" even if > offering scaled down > > > Key: CLOUDSTACK-7744 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7744 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > Fix For: 4.5.0 > > > 1. Create a VM Instance; then make sure it is powered off. > 2. View the VM Instance details, then press the "Change Service Offering" > button. > 3. Select a new service offering then press "OK". > Expected: The notification should be generic, e.g. "Change Service Offering". > Actual: The resulting notification shown upon completion is "Instance Scaled > Up", even if the new service offering is smaller/weaker than what the VM > previously had. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7744) Changing Service Offering incorretly shows "Instance Scaled Up" even if offering scaled down
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-7744: - Fix Version/s: 4.5.0 > Changing Service Offering incorretly shows "Instance Scaled Up" even if > offering scaled down > > > Key: CLOUDSTACK-7744 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7744 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > Fix For: 4.5.0 > > > 1. Create a VM Instance; then make sure it is powered off. > 2. View the VM Instance details, then press the "Change Service Offering" > button. > 3. Select a new service offering then press "OK". > Expected: The notification should be generic, e.g. "Change Service Offering". > Actual: The resulting notification shown upon completion is "Instance Scaled > Up", even if the new service offering is smaller/weaker than what the VM > previously had. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-7744) Changing Service Offering incorretly shows "Instance Scaled Up" even if offering scaled down
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang closed CLOUDSTACK-7744. > Changing Service Offering incorretly shows "Instance Scaled Up" even if > offering scaled down > > > Key: CLOUDSTACK-7744 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7744 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > Fix For: 4.5.0 > > > 1. Create a VM Instance; then make sure it is powered off. > 2. View the VM Instance details, then press the "Change Service Offering" > button. > 3. Select a new service offering then press "OK". > Expected: The notification should be generic, e.g. "Change Service Offering". > Actual: The resulting notification shown upon completion is "Instance Scaled > Up", even if the new service offering is smaller/weaker than what the VM > previously had. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7731) UI > Infrastructure > Virtual Routers > group by zone/pod/cluster/account view > listView > detailView > add View All link (i.e. "View all Virtual Routers").
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-7731: - Fix Version/s: 4.5.0 > UI > Infrastructure > Virtual Routers > group by zone/pod/cluster/account > view > listView > detailView > add View All link (i.e. "View all Virtual > Routers"). > - > > Key: CLOUDSTACK-7731 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7731 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > Fix For: 4.5.0 > > > UI > Infrastructure -> Virtual Routers > group by view > e.g. after selecting "group by zone",its lists only following fields: > Total of Virtual Router: > Upgrade is required: > Total of Virtual Routers that require upgrade: > People would like to see individual router details in select view also, > similar to the view without group by. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7736) UI - listView widget - select view dropdown on top of listView - prefilter() - include original args.context when passing it to prefilter().
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-7736: - Fix Version/s: 4.5.0 > UI - listView widget - select view dropdown on top of listView - prefilter() > - include original args.context when passing it to prefilter(). > > > Key: CLOUDSTACK-7736 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7736 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang > Fix For: 4.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-6718) [OVS][UI] Isolated network offering (non-vpc) creation page shows ovs as the service provider for services other than "VirtualNetworking"
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jessica Wang updated CLOUDSTACK-6718:
-
Component/s: (was: UI)
API
Assignee: (was: Jessica Wang)
This is an API bug, NOT UI bug.
Providers for each service come from listSupportedNetworkServices API response.
API developer,
Please remove "ovs" provider from services other than "VirtualNetworking":
http://10.215.3.26:8080/client/api?command=listSupportedNetworkServices&response=json&sessionkey=X5EtUEcmXix0ncGhSSvXyHGhNfU%3D&_=1413500449807
{
"listsupportednetworkservicesresponse": {
"count": 13,
"networkservice": [
{
"name": "Vpn",
"provider": [
{
"name": "VirtualRouter",
"canenableindividualservice": true
},
{
"name": "VpcVirtualRouter",
"canenableindividualservice": true
}
],
"capability": [
{
"name": "SupportedVpnTypes",
"canchooseservicecapability": false
},
{
"name": "VpnTypes",
"canchooseservicecapability": false
}
]
},
{
"name": "Dhcp",
"provider": [
{
"name": "JuniperContrailVpcRouter",
"canenableindividualservice": true
},
{
"name": "VirtualRouter",
"canenableindividualservice": true
},
{
"name": "BaremetalDhcpProvider",
"canenableindividualservice": false
},
{
"name": "MidoNet",
"canenableindividualservice": true
},
{
"name": "JuniperContrailRouter",
"canenableindividualservice": true
},
{
"name": "VpcVirtualRouter",
"canenableindividualservice": true
}
],
"capability": []
},
{
"name": "Dns",
"provider": [
{
"name": "GloboDns",
"canenableindividualservice": true
},
{
"name": "VirtualRouter",
"canenableindividualservice": true
},
{
"name": "VpcVirtualRouter",
"canenableindividualservice": true
}
],
"capability": [
{
"name": "AllowDnsSuffixModification",
"canchooseservicecapability": false
}
]
},
{
"name": "Firewall",
"provider": [
{
"name": "PaloAlto",
"canenableindividualservice": true
},
{
"name": "VirtualRouter",
"canenableindividualservice": true
}
],
"capability": [
{
"name": "SupportedProtocols",
"canchooseservicecapability": false
},
{
"name": "MultipleIps",
"canchooseservicecapability": false
},
{
"name": "TrafficStatistics",
"canchooseservicecapability": false
},
{
"name": "SupportedTrafficDirection",
"canchooseservicecapability": false
},
{
"name": "SupportedEgressProtocols",
"canchooseservicecapability": false
}
]
},
{
"name": "Lb",
"provider": [
{
"name": "Netscaler",
"canenableindividualservice": true
},
{
[jira] [Assigned] (CLOUDSTACK-6718) [OVS][UI] Isolated network offering (non-vpc) creation page shows ovs as the service provider for services other than "VirtualNetworking"
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jessica Wang reassigned CLOUDSTACK-6718:
Assignee: Animesh Chaturvedi
Animesh,
This is an API bug, NOT UI bug.
Providers for each service come from listSupportedNetworkServices API response.
API developer,
Please remove "ovs" provider from services other than "VirtualNetworking":
http://10.215.3.26:8080/client/api?command=listSupportedNetworkServices&response=json&sessionkey=X5EtUEcmXix0ncGhSSvXyHGhNfU%3D&_=1413500449807
{
"listsupportednetworkservicesresponse": {
"count": 13,
"networkservice": [
{
"name": "Vpn",
"provider": [
{
"name": "VirtualRouter",
"canenableindividualservice": true
},
{
"name": "VpcVirtualRouter",
"canenableindividualservice": true
}
],
"capability": [
{
"name": "SupportedVpnTypes",
"canchooseservicecapability": false
},
{
"name": "VpnTypes",
"canchooseservicecapability": false
}
]
},
{
"name": "Dhcp",
"provider": [
{
"name": "JuniperContrailVpcRouter",
"canenableindividualservice": true
},
{
"name": "VirtualRouter",
"canenableindividualservice": true
},
{
"name": "BaremetalDhcpProvider",
"canenableindividualservice": false
},
{
"name": "MidoNet",
"canenableindividualservice": true
},
{
"name": "JuniperContrailRouter",
"canenableindividualservice": true
},
{
"name": "VpcVirtualRouter",
"canenableindividualservice": true
}
],
"capability": []
},
{
"name": "Dns",
"provider": [
{
"name": "GloboDns",
"canenableindividualservice": true
},
{
"name": "VirtualRouter",
"canenableindividualservice": true
},
{
"name": "VpcVirtualRouter",
"canenableindividualservice": true
}
],
"capability": [
{
"name": "AllowDnsSuffixModification",
"canchooseservicecapability": false
}
]
},
{
"name": "Firewall",
"provider": [
{
"name": "PaloAlto",
"canenableindividualservice": true
},
{
"name": "VirtualRouter",
"canenableindividualservice": true
}
],
"capability": [
{
"name": "SupportedProtocols",
"canchooseservicecapability": false
},
{
"name": "MultipleIps",
"canchooseservicecapability": false
},
{
"name": "TrafficStatistics",
"canchooseservicecapability": false
},
{
"name": "SupportedTrafficDirection",
"canchooseservicecapability": false
},
{
"name": "SupportedEgressProtocols",
"canchooseservicecapability": false
}
]
},
{
"name": "Lb",
"provider": [
{
"name": "Netscaler",
"canenableindividualservice": true
},
{
"name": "VirtualRouter",
"canenableind
[jira] [Issue Comment Deleted] (CLOUDSTACK-6718) [OVS][UI] Isolated network offering (non-vpc) creation page shows ovs as the service provider for services other than "VirtualNetworking"
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jessica Wang updated CLOUDSTACK-6718:
-
Comment: was deleted
(was: This is an API bug, NOT UI bug.
Providers for each service come from listSupportedNetworkServices API response.
API developer,
Please remove "ovs" provider from services other than "VirtualNetworking":
http://10.215.3.26:8080/client/api?command=listSupportedNetworkServices&response=json&sessionkey=X5EtUEcmXix0ncGhSSvXyHGhNfU%3D&_=1413500449807
{
"listsupportednetworkservicesresponse": {
"count": 13,
"networkservice": [
{
"name": "Vpn",
"provider": [
{
"name": "VirtualRouter",
"canenableindividualservice": true
},
{
"name": "VpcVirtualRouter",
"canenableindividualservice": true
}
],
"capability": [
{
"name": "SupportedVpnTypes",
"canchooseservicecapability": false
},
{
"name": "VpnTypes",
"canchooseservicecapability": false
}
]
},
{
"name": "Dhcp",
"provider": [
{
"name": "JuniperContrailVpcRouter",
"canenableindividualservice": true
},
{
"name": "VirtualRouter",
"canenableindividualservice": true
},
{
"name": "BaremetalDhcpProvider",
"canenableindividualservice": false
},
{
"name": "MidoNet",
"canenableindividualservice": true
},
{
"name": "JuniperContrailRouter",
"canenableindividualservice": true
},
{
"name": "VpcVirtualRouter",
"canenableindividualservice": true
}
],
"capability": []
},
{
"name": "Dns",
"provider": [
{
"name": "GloboDns",
"canenableindividualservice": true
},
{
"name": "VirtualRouter",
"canenableindividualservice": true
},
{
"name": "VpcVirtualRouter",
"canenableindividualservice": true
}
],
"capability": [
{
"name": "AllowDnsSuffixModification",
"canchooseservicecapability": false
}
]
},
{
"name": "Firewall",
"provider": [
{
"name": "PaloAlto",
"canenableindividualservice": true
},
{
"name": "VirtualRouter",
"canenableindividualservice": true
}
],
"capability": [
{
"name": "SupportedProtocols",
"canchooseservicecapability": false
},
{
"name": "MultipleIps",
"canchooseservicecapability": false
},
{
"name": "TrafficStatistics",
"canchooseservicecapability": false
},
{
"name": "SupportedTrafficDirection",
"canchooseservicecapability": false
},
{
"name": "SupportedEgressProtocols",
"canchooseservicecapability": false
}
]
},
{
"name": "Lb",
"provider": [
{
"name": "Netscaler",
"canenableindividualservice": true
},
{
"name": "VirtualRouter",
"can
[jira] [Created] (CLOUDSTACK-7745) [Automation] Fix the script "test_ssvm.py" - Private IP of System VMs can change on systemVMs reboot
Chandan Purushothama created CLOUDSTACK-7745: Summary: [Automation] Fix the script "test_ssvm.py" - Private IP of System VMs can change on systemVMs reboot Key: CLOUDSTACK-7745 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7745 Project: CloudStack Issue Type: Test Security Level: Public (Anyone can view this level - this is the default.) Components: Automation, Test Affects Versions: 4.5.0 Reporter: Chandan Purushothama Assignee: Chandan Purushothama Priority: Critical Fix For: 4.5.0 Test Suite assumes that private ip of SSVM and CPVM cannot change after reboot. Fixing the test suite to allow private ip change. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7088) Snapshot manager should search for guest OS including deleted
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amogh Vasekar updated CLOUDSTACK-7088: -- Fix Version/s: (was: 4.5.0) (was: 4.4.0) 4.6.0 > Snapshot manager should search for guest OS including deleted > - > > Key: CLOUDSTACK-7088 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7088 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.4.0 >Reporter: Amogh Vasekar >Assignee: Amogh Vasekar > Fix For: 4.6.0 > > Original Estimate: 24h > Remaining Estimate: 24h > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7746) Baremetal related script erros seen on router console
Sangeetha Hariharan created CLOUDSTACK-7746: --- Summary: Baremetal related script erros seen on router console Key: CLOUDSTACK-7746 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7746 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.5.0 Environment: Build from master Reporter: Sangeetha Hariharan Priority: Critical Fix For: 4.5.0 Baremetal related script erros seen on router console. Advanced zone set up with 3 xenserver hosts in a cluster. When logging into the console view of router , following script errors are seen: /opt/cloud/bin/baremetal-vr.py:159: SyntaxWarning : name 'server' is assigned to before glocal declaration. .. Attached is the screen shot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7746) Baremetal related script erros seen on router console
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan updated CLOUDSTACK-7746: Attachment: router.png > Baremetal related script erros seen on router console > - > > Key: CLOUDSTACK-7746 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7746 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.0 > Environment: Build from master >Reporter: Sangeetha Hariharan >Priority: Critical > Fix For: 4.5.0 > > Attachments: router.png > > > Baremetal related script erros seen on router console. > Advanced zone set up with 3 xenserver hosts in a cluster. > When logging into the console view of router , following script errors are > seen: > /opt/cloud/bin/baremetal-vr.py:159: SyntaxWarning : name 'server' is assigned > to before glocal declaration. .. > Attached is the screen shot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
