[jira] [Commented] (CLOUDSTACK-5435) ldap params are not encrypted
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13847228#comment-13847228 ] ASF subversion and git services commented on CLOUDSTACK-5435: - Commit 24392c15f561fa07fd5f707bbfa6910d880c3a3b in branch refs/heads/4.3 from [~rajanik] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=24392c1 ] CLOUDSTACK-5435 enabled encryption for ldap params > ldap params are not encrypted > - > > Key: CLOUDSTACK-5435 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5435 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.0 >Reporter: Rajani Karuturi >Assignee: Rajani Karuturi > Labels: ldap > Fix For: Future, 4.3.0 > > > ldap global params in configuration table are not encrypted. These were > encrypted in 4.2 -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (CLOUDSTACK-5457) DBHA features is broken in the latest 4.3 Build.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-5457: --- Assignee: Kelven Yang (was: Damodar Reddy T) > DBHA features is broken in the latest 4.3 Build. > > > Key: CLOUDSTACK-5457 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5457 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.3.0 >Reporter: Kiran Koneti >Assignee: Kelven Yang >Priority: Blocker > Fix For: 4.3.0 > > > The DB HA feature is broken in the latest build.The DB switchover is not > happening from the M1 to M2 and it is shutting down once the M1 is down. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Created] (CLOUDSTACK-5488) KVM:agent is still in stopped state even after host recovered from sudddent power failures(powered off/powered on the kvm host)
sadhu suresh created CLOUDSTACK-5488: Summary: KVM:agent is still in stopped state even after host recovered from sudddent power failures(powered off/powered on the kvm host) Key: CLOUDSTACK-5488 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5488 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.3.0 Reporter: sadhu suresh power off and powered on the host and check the host/agent status after host comes up. Stepd: 1.create advance KVM zone with single cluster & with 2 hosts 2.create few vms 3. make sure agent is up and running on both hosts , select one host and powered off the host 4.after 10 min,powered-on the same host 5.check the agent status,host state actual result: host state is disconnected and agent is in stopped state even after host is up and running expected result: Agent should up and running even after hosts recovered form power failures.MS should intelligent enough to start the stopped agent due to any reason like in this case when host is up after power failures,MS should identify and check the state and update the state properly. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Resolved] (CLOUDSTACK-5439) CloudStack does not deal with existing Hyper-V System VMs
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh resolved CLOUDSTACK-5439.
---
Resolution: Won't Fix
It is expected that when a new hyperv host is added to clean cloudstack setup
managing hyperv, it is clean of any system vms. The user is expected to remove
the systemvms and then add the host. Resolving it as won't fix.
> CloudStack does not deal with existing Hyper-V System VMs
> -
>
> Key: CLOUDSTACK-5439
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5439
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Hypervisor Controller
>Affects Versions: 4.3.0
>Reporter: Donal Lafferty
>Assignee: Devdeep Singh
> Labels: hyper-v
>
> I started a Hyper-V zone, which deployed a secondary storage VM to my Hyper-V
> host.
> Later, I stopped the management server, deleted the database, and restarted
> the database server. I applied the same configuration script.
> This time, the management server seemed to get stuck trying to connect to the
> agent on the existing secondary storage. I saw the following message appear
> multiple times in vmops.log:
> 2013-12-10 13:15:26,997 DEBUG [c.c.s.StatsCollector]
> (StatsCollector-1:ctx-c483bea4) HostStatsCollector is running...
> 2013-12-10 13:15:26,999 DEBUG [c.c.s.StatsCollector]
> (StatsCollector-2:ctx-a2557e88) VmStatsCollector is running...
> 2013-12-10 13:15:27,005 DEBUG [c.c.s.StatsCollector]
> (StatsCollector-3:ctx-6520624e) StorageCollector is running...
> 2013-12-10 13:15:31,243 WARN [c.c.u.n.Link] (AgentManager-Selector:null)
> SSL: Fail to find the generated keystore. Loading fail-safe one to continue.
> 2013-12-10 13:15:32,129 DEBUG [c.c.a.t.Request] (AgentManager-Handler-7:null)
> Seq 0-0: Scheduling the first command { Cmd , MgmtId: -1, via: 0, Ver: v1,
> Flags: 101,
> [{"com.cloud.agent.api.StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCenter":"1","pod":"1","guid":"s-1-VM-NfsSecondaryStorageResource","name":"s-1-VM","id":0,"version":"4.3.0-SNAPSHOT","iqn":"NoIqn","publicIpAddress":"10.70.176.132","publicNetmask":"255.255.240.0","publicMacAddress":"06:56:a4:00:00:12","privateIpAddress":"10.70.176.93","privateMacAddress":"06:de:9a:00:00:04","privateNetmask":"255.255.240.0","storageIpAddress":"10.70.176.93","storageNetmask":"255.255.240.0","storageMacAddress":"06:de:9a:00:00:04","resourceName":"NfsSecondaryStorageResource","wait":0}}]
> }
> 2013-12-10 13:15:32,137 DEBUG [c.c.a.t.Request]
> (AgentConnectTaskPool-2:ctx-10fb889d) Seq 0-0: Processing the first command
> { Cmd , MgmtId: -1, via: 0, Ver: v1, Flags: 101,
> [{"com.cloud.agent.api.StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCenter":"1","pod":"1","guid":"s-1-VM-NfsSecondaryStorageResource","name":"s-1-VM","id":0,"version":"4.3.0-SNAPSHOT","iqn":"NoIqn","publicIpAddress":"10.70.176.132","publicNetmask":"255.255.240.0","publicMacAddress":"06:56:a4:00:00:12","privateIpAddress":"10.70.176.93","privateMacAddress":"06:de:9a:00:00:04","privateNetmask":"255.255.240.0","storageIpAddress":"10.70.176.93","storageNetmask":"255.255.240.0","storageMacAddress":"06:de:9a:00:00:04","resourceName":"NfsSecondaryStorageResource","wait":0}}]
> }
> 2013-12-10 13:15:32,144 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentConnectTaskPool-2:ctx-10fb889d) Failed to handle host connection:
> java.lang.IllegalArgumentException: Host 10.70.176.93 sent incorrect data
> center: 1
> 2013-12-10 13:15:32,149 WARN [c.c.a.m.AgentManagerImpl]
> (AgentConnectTaskPool-2:ctx-10fb889d) Unable to create attache for agent: Seq
> 0-0: { Cmd , MgmtId: -1, via: 0, Ver: v1, Flags: 101,
> [{"com.cloud.agent.api.StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCenter":"1","pod":"1","guid":"s-1-VM-NfsSecondaryStorageResource","name":"s-1-VM","id":0,"version":"4.3.0-SNAPSHOT","iqn":"NoIqn","publicIpAddress":"10.70.176.132","publicNetmask":"255.255.240.0","publicMacAddress":"06:56:a4:00:00:12","privateIpAddress":"10.70.176.93","privateMacAddress":"06:de:9a:00:00:04","privateNetmask":"255.255.240.0","storageIpAddress":"10.70.176.93","storageNetmask":"255.255.240.0","storageMacAddress":"06:de:9a:00:00:04","resourceName":"NfsSecondaryStorageResource","wait":0}}]
> }
> 2013-12-10 13:15:32,240 WARN [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-8:null) Throwing away a request because it came through
> as the first command on a connect: Seq 0--1: { Cmd , MgmtId: -1, via: 0,
> Ver: v1, Flags: 111,
> [{"com.cloud.agent.api.ShutdownCommand":{"reason":"sig.kill","wait":0}}] }
> 2013-12-10 13:15:32,247 WARN [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-9:null) Throwing away a request becaus
[jira] [Assigned] (CLOUDSTACK-4938) Add account password confirmation broken
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Duffy reassigned CLOUDSTACK-4938: - Assignee: Brian Federle (was: Ian Duffy) > Add account password confirmation broken > > > Key: CLOUDSTACK-4938 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4938 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.0 >Reporter: Brian Federle >Assignee: Brian Federle >Priority: Blocker > Fix For: 4.3.0 > > > Currently the password confirmation field is not validating, even if the > confirmation value is correct. The validation needs to be fixed, otherwise > the add account dialog will not execute. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Resolved] (CLOUDSTACK-5480) [UI] Unable to create account in sequence
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Duffy resolved CLOUDSTACK-5480. --- Resolution: Duplicate Duplicate issue: https://issues.apache.org/jira/browse/CLOUDSTACK-4938 Also unrelated to the changes made. Its due to the way the UI destroys the wizard boxes. It leaves them present within the DOM causing duplicate password fields. I do not have the UI knowledge to solve this and haven't heard back from Brian on my comment on the other ticket. > [UI] Unable to create account in sequence > - > > Key: CLOUDSTACK-5480 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5480 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 > Environment: UI > Branch : 4.3 >Reporter: Rayees Namathponnan >Assignee: Ian Duffy >Priority: Critical > Fix For: 4.3.0 > > > Steps to reproduce > Step 1 : Create account with > User name : a, password a: email a...@a.com type : admin > Step 2 : Without refreshing the page create another account > User name b : password b : email b...@b.com type : admin > Result > Failed to create second account, with error in password confirmation dialog > "Please enter the same value again". > You need to set password first account's password (here a) to create second > account > Looks like, it got broken as part of > commit 532e04db1a66f1f89bb940917928dfa97dd8748a > Author: Ian Duffy > Date: Fri Aug 2 09:27:38 2013 +0100 > Disable password changing when ldap is enabled > > Signed-off-by: Abhinandan Prateek > commit ec064b307734dcb1d4304454de466d6e70e019fb > Author: Ian Duffy > Date: Mon Jul 29 05:58:00 2013 -0400 > New LDAP UI > > Signed-off-by: Sebastien Goasguen > commit eaa41433715ba1a1137ad9f346ea8569e31e4560 > Author: Ian Duffy > Date: Thu Jul 25 10:24:13 2013 +0100 > Merge LDAPPlugin > > Signed-off-by: Abhinandan Prateek -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-4578) [vmware]SSVM is not getting created if one host down from a cluster
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13847186#comment-13847186 ] Damodar Reddy T commented on CLOUDSTACK-4578: - Hi Rayees, I observed this behaviour.. If we shutdown the host in vCenter on which SSVM is running it is showing the state of SSVM as disconnected in vCenter but in MS it is in RUNNING state. Is Kelven already working on vmSync part? Thanks & Regards Damoder > [vmware]SSVM is not getting created if one host down from a cluster > --- > > Key: CLOUDSTACK-4578 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4578 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VMware >Affects Versions: 4.2.0 > Environment: Vmware > 4.2.-forward >Reporter: Rayees Namathponnan >Assignee: Damodar Reddy T >Priority: Critical > Fix For: 4.3.0 > > Attachments: CLOUDSTACK-4578.rar > > > Steps to reproduce > Step 1 : Create vmware advanced zone with 2 host in a cluster (HA not > enabled ) > Step 2 : Check SSVM, in which host is running > Step 3 : Shutdown the host, in where SSVM is running > Expected Result > > New SSVM should be created on second host (Running Host) > Actual result > -- > SSVM is not getting created on second host; > Work around > -- > You need to force fully stop SSVM trough API, then new SSVM gets created on > second host > We need to document this -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Assigned] (CLOUDSTACK-5439) CloudStack does not deal with existing Hyper-V System VMs
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh reassigned CLOUDSTACK-5439:
-
Assignee: Devdeep Singh
> CloudStack does not deal with existing Hyper-V System VMs
> -
>
> Key: CLOUDSTACK-5439
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5439
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Hypervisor Controller
>Affects Versions: 4.3.0
>Reporter: Donal Lafferty
>Assignee: Devdeep Singh
> Labels: hyper-v
>
> I started a Hyper-V zone, which deployed a secondary storage VM to my Hyper-V
> host.
> Later, I stopped the management server, deleted the database, and restarted
> the database server. I applied the same configuration script.
> This time, the management server seemed to get stuck trying to connect to the
> agent on the existing secondary storage. I saw the following message appear
> multiple times in vmops.log:
> 2013-12-10 13:15:26,997 DEBUG [c.c.s.StatsCollector]
> (StatsCollector-1:ctx-c483bea4) HostStatsCollector is running...
> 2013-12-10 13:15:26,999 DEBUG [c.c.s.StatsCollector]
> (StatsCollector-2:ctx-a2557e88) VmStatsCollector is running...
> 2013-12-10 13:15:27,005 DEBUG [c.c.s.StatsCollector]
> (StatsCollector-3:ctx-6520624e) StorageCollector is running...
> 2013-12-10 13:15:31,243 WARN [c.c.u.n.Link] (AgentManager-Selector:null)
> SSL: Fail to find the generated keystore. Loading fail-safe one to continue.
> 2013-12-10 13:15:32,129 DEBUG [c.c.a.t.Request] (AgentManager-Handler-7:null)
> Seq 0-0: Scheduling the first command { Cmd , MgmtId: -1, via: 0, Ver: v1,
> Flags: 101,
> [{"com.cloud.agent.api.StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCenter":"1","pod":"1","guid":"s-1-VM-NfsSecondaryStorageResource","name":"s-1-VM","id":0,"version":"4.3.0-SNAPSHOT","iqn":"NoIqn","publicIpAddress":"10.70.176.132","publicNetmask":"255.255.240.0","publicMacAddress":"06:56:a4:00:00:12","privateIpAddress":"10.70.176.93","privateMacAddress":"06:de:9a:00:00:04","privateNetmask":"255.255.240.0","storageIpAddress":"10.70.176.93","storageNetmask":"255.255.240.0","storageMacAddress":"06:de:9a:00:00:04","resourceName":"NfsSecondaryStorageResource","wait":0}}]
> }
> 2013-12-10 13:15:32,137 DEBUG [c.c.a.t.Request]
> (AgentConnectTaskPool-2:ctx-10fb889d) Seq 0-0: Processing the first command
> { Cmd , MgmtId: -1, via: 0, Ver: v1, Flags: 101,
> [{"com.cloud.agent.api.StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCenter":"1","pod":"1","guid":"s-1-VM-NfsSecondaryStorageResource","name":"s-1-VM","id":0,"version":"4.3.0-SNAPSHOT","iqn":"NoIqn","publicIpAddress":"10.70.176.132","publicNetmask":"255.255.240.0","publicMacAddress":"06:56:a4:00:00:12","privateIpAddress":"10.70.176.93","privateMacAddress":"06:de:9a:00:00:04","privateNetmask":"255.255.240.0","storageIpAddress":"10.70.176.93","storageNetmask":"255.255.240.0","storageMacAddress":"06:de:9a:00:00:04","resourceName":"NfsSecondaryStorageResource","wait":0}}]
> }
> 2013-12-10 13:15:32,144 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentConnectTaskPool-2:ctx-10fb889d) Failed to handle host connection:
> java.lang.IllegalArgumentException: Host 10.70.176.93 sent incorrect data
> center: 1
> 2013-12-10 13:15:32,149 WARN [c.c.a.m.AgentManagerImpl]
> (AgentConnectTaskPool-2:ctx-10fb889d) Unable to create attache for agent: Seq
> 0-0: { Cmd , MgmtId: -1, via: 0, Ver: v1, Flags: 101,
> [{"com.cloud.agent.api.StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCenter":"1","pod":"1","guid":"s-1-VM-NfsSecondaryStorageResource","name":"s-1-VM","id":0,"version":"4.3.0-SNAPSHOT","iqn":"NoIqn","publicIpAddress":"10.70.176.132","publicNetmask":"255.255.240.0","publicMacAddress":"06:56:a4:00:00:12","privateIpAddress":"10.70.176.93","privateMacAddress":"06:de:9a:00:00:04","privateNetmask":"255.255.240.0","storageIpAddress":"10.70.176.93","storageNetmask":"255.255.240.0","storageMacAddress":"06:de:9a:00:00:04","resourceName":"NfsSecondaryStorageResource","wait":0}}]
> }
> 2013-12-10 13:15:32,240 WARN [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-8:null) Throwing away a request because it came through
> as the first command on a connect: Seq 0--1: { Cmd , MgmtId: -1, via: 0,
> Ver: v1, Flags: 111,
> [{"com.cloud.agent.api.ShutdownCommand":{"reason":"sig.kill","wait":0}}] }
> 2013-12-10 13:15:32,247 WARN [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-9:null) Throwing away a request because it came through
> as the first command on a connect: Seq 0-1: { Cmd , MgmtId: -1, via: 0, Ver:
> v1, Flags: 11,
> [{"com.cloud.agent.api.PingStorageCommand":{"changes":{},"hostType":"Storage","hostId":0,"wait":0}
[jira] [Created] (CLOUDSTACK-5487) Indentation issue in test_portable_ip.py
Gaurav Aradhye created CLOUDSTACK-5487: -- Summary: Indentation issue in test_portable_ip.py Key: CLOUDSTACK-5487 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5487 Project: CloudStack Issue Type: Test Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.3.0 Reporter: Gaurav Aradhye Assignee: Gaurav Aradhye Fix For: 4.3.0 There are indentation issues in 2 test cases which causing failure. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (CLOUDSTACK-5487) [Automation] Indentation issue in test_portable_ip.py
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Aradhye updated CLOUDSTACK-5487: --- Summary: [Automation] Indentation issue in test_portable_ip.py (was: Indentation issue in test_portable_ip.py) > [Automation] Indentation issue in test_portable_ip.py > - > > Key: CLOUDSTACK-5487 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5487 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.3.0 >Reporter: Gaurav Aradhye >Assignee: Gaurav Aradhye > Labels: automation > Fix For: 4.3.0 > > > There are indentation issues in 2 test cases which causing failure. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-5457) DBHA features is broken in the latest 4.3 Build.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13847177#comment-13847177 ] Damodar Reddy T commented on CLOUDSTACK-5457: - The commit "5a44de282b30f6dc34b8a36d8f664bd3a3b9408b" is started throwing exceptions from ManagementServerHostDaoImpl(especially update method) which is cauing the server to go down even If we enable DB HA. Waiting for reply from Kelven Yang to know the context behind this change. Will fix this once we get response from Kelven. > DBHA features is broken in the latest 4.3 Build. > > > Key: CLOUDSTACK-5457 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5457 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.3.0 >Reporter: Kiran Koneti >Assignee: Damodar Reddy T >Priority: Blocker > Fix For: 4.3.0 > > > The DB HA feature is broken in the latest build.The DB switchover is not > happening from the M1 to M2 and it is shutting down once the M1 is down. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (CLOUDSTACK-5209) No notification is given either in the UI nor in the MS logs if the Master 2 goes down for the DBHA.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-5209: --- Issue Type: Improvement (was: Bug) > No notification is given either in the UI nor in the MS logs if the Master 2 > goes down for the DBHA. > > > Key: CLOUDSTACK-5209 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5209 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.3.0 >Reporter: Kiran Koneti >Assignee: Damodar Reddy T > Fix For: Future > > > I have create a DB replication with 2 masters and the CS setup is up with the > same.Now when the M1 is up and the CS operations are running normally and if > the M2 goes down there is no chance to know that the M2 is gone.There are no > notifications either in the UI nor in the MS logs. > Note:Even when the M1 goes down there is a notification only in the logs and > no notification in the UI . It would be good to have an alert in the UI as > watching logs all the time may not be possible. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (CLOUDSTACK-5209) No notification is given either in the UI nor in the MS logs if the Master 2 goes down for the DBHA.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-5209: --- Fix Version/s: (was: 4.3.0) Future > No notification is given either in the UI nor in the MS logs if the Master 2 > goes down for the DBHA. > > > Key: CLOUDSTACK-5209 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5209 > 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 >Reporter: Kiran Koneti >Assignee: Damodar Reddy T >Priority: Critical > Fix For: Future > > > I have create a DB replication with 2 masters and the CS setup is up with the > same.Now when the M1 is up and the CS operations are running normally and if > the M2 goes down there is no chance to know that the M2 is gone.There are no > notifications either in the UI nor in the MS logs. > Note:Even when the M1 goes down there is a notification only in the logs and > no notification in the UI . It would be good to have an alert in the UI as > watching logs all the time may not be possible. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (CLOUDSTACK-5209) No notification is given either in the UI nor in the MS logs if the Master 2 goes down for the DBHA.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-5209: --- Priority: Major (was: Critical) > No notification is given either in the UI nor in the MS logs if the Master 2 > goes down for the DBHA. > > > Key: CLOUDSTACK-5209 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5209 > 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 >Reporter: Kiran Koneti >Assignee: Damodar Reddy T > Fix For: Future > > > I have create a DB replication with 2 masters and the CS setup is up with the > same.Now when the M1 is up and the CS operations are running normally and if > the M2 goes down there is no chance to know that the M2 is gone.There are no > notifications either in the UI nor in the MS logs. > Note:Even when the M1 goes down there is a notification only in the logs and > no notification in the UI . It would be good to have an alert in the UI as > watching logs all the time may not be possible. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-5342) Add NIC to virtual machine fails in KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13847173#comment-13847173
]
Gaurav Aradhye commented on CLOUDSTACK-5342:
Rayess,
The test script verifies the same thing, that adding same network multiple
times should fail. So there is no problem with the intent of the test. It might
be possible that failure in cleanup of some other test case (earlier nic not
getting removed) causing this. I was not able to check this issue yesterday
because of KVM setup being loaded heavily. I will check today if this is indeed
test script cleanup issue or something else.
> Add NIC to virtual machine fails in KVM
> ---
>
> Key: CLOUDSTACK-5342
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5342
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
>Affects Versions: 4.3.0
> Environment: KVM advanced
>Reporter: Gaurav Aradhye
>Assignee: Marcus Sorensen
>Priority: Blocker
> Fix For: 4.3.0
>
>
> Add network to VM test cases fail in KVM with following error.
> Execute cmd: asyncquery failed, due to: {errorcode : 530, errortext :
> u'Unable to add NIC to VM[User|VM-e9350ee5-bf2e-418c-91d6-1535dcb4d488]'}
> The same test cases execute successfully on XenServer. As per the feature
> specification (see
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Add+Remove+Networks+to+VMs),
> "Add network to VM" feature should be supported on KVM too.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-5311) [Hyper-V] Global settings missing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13847172#comment-13847172 ] ASF subversion and git services commented on CLOUDSTACK-5311: - Commit db2b8d9b0d61bf41fdaf838d2b9fbbadc023d1c2 in branch refs/heads/master from [~devdeep] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=db2b8d9 ] CLOUDSTACK-5311: Fix the host version reported by the hyper-v agent. Also updated the hypervisor capabilities for hyper-v. > [Hyper-V] Global settings missing > - > > Key: CLOUDSTACK-5311 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5311 > 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: 4.3, Hyper-V >Reporter: Abhinav Roy >Assignee: Devdeep Singh >Priority: Critical > Labels: hyper-V, > Fix For: 4.3.0 > > > 1. Hyper-v entry is missing from >Global Settings -> Hypervisor capabilities > 2. Hypervisor Version is not listed at > Infrastructure -> Hosts -> - Details -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-5012) Bad data inserted into physical network labels for Zone Create Wizard using VMWare
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13847169#comment-13847169 ] Damodar Reddy T commented on CLOUDSTACK-5012: - Hi Jim, I am closing this defect saying not a defect. If you are able to re produce it please re open and share the DB Dump and the Switches you have configured etc.. We are not doing any validation checks for the vSwitch Labels in MS as these names are generated by vmware internally while adding a network adapter in web sphere. Thanks & Regards Damoder > Bad data inserted into physical network labels for Zone Create Wizard using > VMWare > -- > > Key: CLOUDSTACK-5012 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5012 > 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: Jim Leary >Assignee: Damodar Reddy T >Priority: Critical > Fix For: 4.3.0 > > > When using the Zone create wizard and choosing VMWare, the physical network > labels contain additional data, rendering any attempt to create a VMWare > cluster unsuccessful. The Zone wizard must be cancelled and the physical > network labels corrected, then manually create the cluster, primary and > secondary storage for the Zone to function correctly. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Resolved] (CLOUDSTACK-5012) Bad data inserted into physical network labels for Zone Create Wizard using VMWare
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T resolved CLOUDSTACK-5012. - Resolution: Not A Problem > Bad data inserted into physical network labels for Zone Create Wizard using > VMWare > -- > > Key: CLOUDSTACK-5012 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5012 > 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: Jim Leary >Assignee: Damodar Reddy T >Priority: Critical > Fix For: 4.3.0 > > > When using the Zone create wizard and choosing VMWare, the physical network > labels contain additional data, rendering any attempt to create a VMWare > cluster unsuccessful. The Zone wizard must be cancelled and the physical > network labels corrected, then manually create the cluster, primary and > secondary storage for the Zone to function correctly. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (CLOUDSTACK-5361) Require UI changes,currently UI is not supporting custom system service offerings
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-5361: -- Attachment: screenshot-2.jpg > Require UI changes,currently UI is not supporting custom system service > offerings > -- > > Key: CLOUDSTACK-5361 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5361 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 >Reporter: prashant kumar mishra >Assignee: Jessica Wang > Attachments: screenshot-1.jpg, screenshot-2.jpg > > > Steps to reproduce > > 1-try to create a custom system service offering > Expected > > AS we have custom check box for compute offering , we should have same for > system SO > Actual > - > There are no custom check box -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-5361) Require UI changes,currently UI is not supporting custom system service offerings
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13847164#comment-13847164
]
prashant kumar mishra commented on CLOUDSTACK-5361:
---
As per FS
Changes to the APIs:
DeployVM , ScaleVM , ScaleSystemVM , UpgradeVM, UpgradeSysytemVM API.
The change is same in all the APIs. we added a map of custom parameters called
customparameters. all the custom values need to be specified using this map
parameter.
---> according to FS ,dynamic compute offering is supported for system vms
--->I was able to create SO and scaleup from api please check screen shot
API
http://10.147.38.177:8080/client/api?command=createServiceOffering&response=json&sessionkey=fe8%2FxjAL747WlIybIsdEOqFsc5w%3D&issystem=true&name=ssvm1&displaytext=ssvm1&systemvmtype=secondarystoragevm&storageType=shared&offerha=false&limitcpuuse=false&_=138690985
response:
{ "createserviceofferingresponse" : { "serviceoffering" :
{"id":"13f17709-fa95-41d2-88ca-67897c262ebe","name":"ssvm1","displaytext":"ssvm1","created":"2013-12-13T05:01:16-0500","storagetype":"shared","offerha":false,"limitcpuuse":false,"isvolatile":false,"issystem":true,"defaultuse":false,"systemvmtype":"secondarystoragevm","iscustomized":true}
} }
> Require UI changes,currently UI is not supporting custom system service
> offerings
> --
>
> Key: CLOUDSTACK-5361
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5361
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
>Affects Versions: 4.3.0
>Reporter: prashant kumar mishra
>Assignee: Jessica Wang
> Attachments: screenshot-1.jpg
>
>
> Steps to reproduce
>
> 1-try to create a custom system service offering
> Expected
>
> AS we have custom check box for compute offering , we should have same for
> system SO
> Actual
> -
> There are no custom check box
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Created] (CLOUDSTACK-5486) [UI] List Template for non root admin account does not display tags for pubic templates
Saksham Srivastava created CLOUDSTACK-5486:
--
Summary: [UI] List Template for non root admin account does not
display tags for pubic templates
Key: CLOUDSTACK-5486
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5486
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: UI
Affects Versions: 4.2.0, 4.2.1
Reporter: Saksham Srivastava
Steps to reproduce:
1. As a root admin register a public template
2. Add tags to the template
3. Log in as non root admin user
4. Template list will not have tags listeed those were created in step 2
List template response does contain tags :
{ "listtemplatesresponse" : { "count":1 ,"template" : [
{"id":"ba29b217-0284-4149-9348-54713ff2f20d","name":"template","displaytext":"template","ispublic":true,"created":"2013-12-12T19:01:17+0530","isready":true,"passwordenabled":false,"format":"VHD","isfeatured":false,"crossZones":true,"ostypeid":"faac95de-62f6-11e3-8a00-1a9dc5aab6d3","ostypename":"Other
(64-bit)","account":"admin","zoneid":"64d7a63c-05a5-4539-9560-e53eaff2b205","zonename":"zonez","size":52428800,"templatetype":"USER","hypervisor":"XenServer","domain":"ROOT","domainid":"fb94c872-62f6-11e3-8a00-1a9dc5aab6d3","isextractable":false,"checksum":"046e134e642e6d344b34648223ba4bc1","details":{"hypervisortoolsversion":"xenserver61"},
"tags":[{"key":"mytag","value":"tag-value","resourcetype":"Template","resourceid":"ba29b217-0284-4149-9348-54713ff2f20d","account":"admin","domainid":"fb94c872-62f6-11e3-8a00-1a9dc5aab6d3","domain":"ROOT"}],"sshkeyenabled":false,"isdynamicallyscalable":false}
] } }
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Updated] (CLOUDSTACK-5334) [Automation] Failed to create template from snapshot while executing copy command, observed NPE In SSVM log
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinandan Prateek updated CLOUDSTACK-5334:
---
Assignee: (was: Gaurav Aradhye)
> [Automation] Failed to create template from snapshot while executing copy
> command, observed NPE In SSVM log
> ---
>
> Key: CLOUDSTACK-5334
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5334
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Template
>Affects Versions: 4.3.0
> Environment: KVM
> Branch 4.3
>Reporter: Rayees Namathponnan
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: CLOUDSTACK-5334.rar
>
>
> Steps to reproduce
> Step 1 : snapshot root volume
> Step 2 : Create template from snapshot
> Result
> Failed to create template from snapshot, observed below "copy command failure
> and NPE" in MS log and SSVM log
> MS log
> 2013-12-02 08:28:49,406 DEBUG [o.a.c.s.m.AncientDataMotionStrategy]
> (Job-Executor-140:ctx-62f776d6 ctx-120aa5f1) copyAsync inspecting src type
> SNAPSHOT copy
> Async inspecting dest type TEMPLATE
> 2013-12-02 08:28:49,418 DEBUG [c.c.a.t.Request]
> (Job-Executor-140:ctx-62f776d6 ctx-120aa5f1) Seq 8-1124074796: Sending { Cmd
> , MgmtId: 29066118877352, via:
> 8(s-5-VM), Ver: v1, Flags: 100011,
> [{"org.apache.cloudstack.storage.command.CopyCommand":{"srcTO":{"org.apache.cloudstack.storage.to.SnapshotObjectTO":{"pa
> th":"snapshots/282/589/d2b20627-b60e-489b-9eee-9f4705331a72","dataStore":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.223.110.232:/export/home/rayees/S
> C_QA_AUTO4/secondary","_role":"Image"}},"name":"VM-f9e129c2-8d62-4b70-8105-abd304bf7605_ROOT-526_20131202080509","hypervisorType":"KVM","id":20,"quiescevm":
> false}},"destTO":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"path":"template/tmpl/282/236","uuid":"1e48c6bf-388e-4184-93f5-28a21b12329c","id":236
> ,"format":"RAW","accountId":282,"hvm":true,"displayText":"raytemp","imageDataStore":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.223.110.232:/export/ho
> me/rayees/SC_QA_AUTO4/secondary","_role":"Image"}},"name":"2c497573e-38cc-3f4d-a73a-49c7b63bbb6c","hypervisorType":"KVM"}},"executeInSequence":false,"wait":
> 10800}}] }
> 2013-12-02 08:28:49,655 DEBUG [c.c.a.t.Request]
> (AgentManager-Handler-14:null) Seq 8-1124074796: Processing: { Ans: ,
> MgmtId: 29066118877352, via: 8, Ver:
> v1, Flags: 10,
> [{"com.cloud.agent.api.Answer":{"result":false,"details":"java.lang.NullPointerException\n\tat
> org.apache.cloudstack.storage.resource.NfsSeco
> ndaryStorageResource.copySnapshotToTemplateFromNfsToNfs(NfsSecondaryStorageResource.java:449)\n\tat
> org.apache.cloudstack.storage.resource.NfsSecondaryStora
> geResource.createTemplateFromSnapshot(NfsSecondaryStorageResource.java:546)\n\tat
> org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.execute
> (NfsSecondaryStorageResource.java:625)\n\tat
> org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.executeRequest(NfsSecondaryStorageResource.j
> ava:236)\n\tat
> com.cloud.storage.resource.PremiumSecondaryStorageResource.defaultAction(PremiumSecondaryStorageResource.java:63)\n\tat
> com.cloud.storage.res
> ource.PremiumSecondaryStorageResource.executeRequest(PremiumSecondaryStorageResource.java:59)\n\tat
> com.cloud.agent.Agent.processRequest(Agent.java:498)\n\t
> at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:806)\n\tat
> com.cloud.utils.nio.Task.run(Task.java:83)\n\tat
> java.util.concurrent.ThreadPoolEx
> ecutor.runWorker(ThreadPoolExecutor.java:1146)\n\tat
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)\n\tat
> java.lang.Thread.
> run(Thread.java:679)\n","wait":0}}] }
> 2013-12-02 08:28:49,656 DEBUG [c.c.a.t.Request]
> (Job-Executor-140:ctx-62f776d6 ctx-120aa5f1) Seq 8-1124074796: Received: {
> Ans: , MgmtId: 29066118877352, v
> ia: 8, Ver: v1, Flags: 10, { Answer } }
> 2013-12-02 08:28:49,663 DEBUG [c.c.t.TemplateManagerImpl]
> (Job-Executor-140:ctx-62f776d6 ctx-120aa5f1) Failed to create
> templatejava.lang.NullPointerExcepti
> on
> at
> org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.copySnapshotToTemplateFromNfsToNfs(NfsSecondaryStorageResource.java:449)
> at
> org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.createTemplateFromSnapshot(NfsSecondaryStorageResource.java:546)
> at
> org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.execute(NfsSecondaryStorageResource.java:625)
> at
> org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.executeRequest(NfsSecon
[jira] [Updated] (CLOUDSTACK-5462) Hyper-V Agent confused by existing volume of different image type
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-5462: --- Assignee: Donal Lafferty > Hyper-V Agent confused by existing volume of different image type > - > > Key: CLOUDSTACK-5462 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5462 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller >Affects Versions: 4.3.0 >Reporter: Donal Lafferty >Assignee: Donal Lafferty > Labels: hyper-v > > VolumeObjectTO objects do not specify the image format. > Hyper-V infers the format from files with the same name as that specified in > the VolumeObjectTO.name field. This fails when a name is reused for a > different image type. > E.g. if the agent finds a ROOT2-1.vhd, it will assume that the VolumeObjectTO > is a VHD. However, if the VolumeObjectTO is actually a VHDX, then the disk > will appear to be corrupt to the hypervisor. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (CLOUDSTACK-5468) Configuration property should be optional
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-5468: --- Assignee: Mike Tutkowski > Configuration property should be optional > - > > Key: CLOUDSTACK-5468 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5468 > 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: Mac OS X 10.8.3 >Reporter: Mike Tutkowski >Assignee: Mike Tutkowski > Fix For: 4.3.0 > > > This is actually an issue with the SolidFire plug-in (as opposed to the > Management Server, which is the Component this is filed under). > The property "useMutualChapForVMware" should be optional. > We have already seen a customer have issues with this, so it is important to > fix in 4.3. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (CLOUDSTACK-5485) Vmware - Whe 10 hourly snapshots are scheduled at the same time , we see only 5 of them being processed actively at the same time.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan updated CLOUDSTACK-5485: Attachment: vmware.rar > Vmware - Whe 10 hourly snapshots are scheduled at the same time , we see only > 5 of them being processed actively at the same time. > --- > > Key: CLOUDSTACK-5485 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5485 > 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: Build from 4.3 >Reporter: Sangeetha Hariharan >Priority: Critical > Fix For: 4.3.0 > > Attachments: vmware.rar > > > Vmware - When 10 hourly snapshots are scheduled at the same time , we see > only 5 of them being processed actively at the same time. > Set up : > Advanced Zone with 2 5.1 ESXI hosts. > Steps to reproduce the problem: > 1. Deploy 5 Vms in each of the hosts , so we start with 10 Vms. > 2. Start concurrent snapshots for ROOT volumes of all the Vms. > Noticed that on the Vsphere client , only 5 of these snapshots gets executed > in parallel.Rest of them get picked up when the current snapshot jobs > complete. > Why cant we do more than 5 parallel tasks ? -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Created] (CLOUDSTACK-5485) Vmware - Whe 10 hourly snapshots are scheduled at the same time , we see only 5 of them being processed actively at the same time.
Sangeetha Hariharan created CLOUDSTACK-5485: --- Summary: Vmware - Whe 10 hourly snapshots are scheduled at the same time , we see only 5 of them being processed actively at the same time. Key: CLOUDSTACK-5485 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5485 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: Build from 4.3 Reporter: Sangeetha Hariharan Priority: Critical Fix For: 4.3.0 Vmware - When 10 hourly snapshots are scheduled at the same time , we see only 5 of them being processed actively at the same time. Set up : Advanced Zone with 2 5.1 ESXI hosts. Steps to reproduce the problem: 1. Deploy 5 Vms in each of the hosts , so we start with 10 Vms. 2. Start concurrent snapshots for ROOT volumes of all the Vms. Noticed that on the Vsphere client , only 5 of these snapshots gets executed in parallel.Rest of them get picked up when the current snapshot jobs complete. Why cant we do more than 5 parallel tasks ? -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (CLOUDSTACK-5482) Vmware - When nfs was down for about 1 hour , when snapshots were in progress , snapshot job failed when nfs was brought up leaving behind snaphots in "CreatedOnPri
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangeetha Hariharan updated CLOUDSTACK-5482:
Attachment: vmware.rar
> Vmware - When nfs was down for about 1 hour , when snapshots were in progress
> , snapshot job failed when nfs was brought up leaving behind snaphots in
> "CreatedOnPrimary" state.
> -
>
> Key: CLOUDSTACK-5482
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5482
> 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: Build from 4.3
>Reporter: Sangeetha Hariharan
> Fix For: 4.3.0
>
> Attachments: vmware.rar, vmware.rar
>
>
> Set up :
> Advanced Zone with 2 5.1 ESXI hosts.
> Steps to reproduce the problem:
> 1. Deploy 5 Vms in each of the hosts , so we start with 11 Vms.
> 2. Start concurrent snapshots for ROOT volumes of all the Vms.
> 3. Shutdown the Secondary storage server when the snapshots are in the
> progress.
> 4. Bring the Secondary storage server up after 1 hour.
> When the secondary storage was down , 2 of the snapshots were already
> completed. 5 of them were in progress and the other 4 had not started yet.
> Once the secondary store was brought up , I see the snapshots that were in
> progress actually continue to download to secondary and succeed. But the
> other 4 snapshots error out.
> mysql> select volume_id,status,created from snapshots;
> +---+--+-+
> | volume_id | status | created |
> +---+--+-+
> |22 | BackedUp | 2013-12-12 23:24:13 |
> |21 | Destroyed| 2013-12-12 23:24:13 |
> |20 | BackedUp | 2013-12-12 23:24:14 |
> |19 | Destroyed| 2013-12-12 23:24:14 |
> |18 | BackedUp | 2013-12-12 23:24:14 |
> |17 | BackedUp | 2013-12-12 23:24:14 |
> |16 | BackedUp | 2013-12-12 23:24:14 |
> |14 | BackedUp | 2013-12-12 23:24:15 |
> |25 | BackedUp | 2013-12-12 23:24:15 |
> |24 | BackedUp | 2013-12-12 23:24:15 |
> |23 | BackedUp | 2013-12-12 23:24:15 |
> |22 | CreatedOnPrimary | 2013-12-12 23:53:38 |
> |21 | BackedUp | 2013-12-12 23:53:38 |
> |20 | BackedUp | 2013-12-12 23:53:38 |
> |19 | BackedUp | 2013-12-12 23:53:39 |
> |18 | CreatedOnPrimary | 2013-12-12 23:53:39 |
> |17 | CreatedOnPrimary | 2013-12-12 23:53:40 |
> |16 | CreatedOnPrimary | 2013-12-12 23:53:40 |
> |14 | BackedUp | 2013-12-12 23:53:40 |
> |25 | BackedUp | 2013-12-12 23:53:41 |
> |24 | BackedUp | 2013-12-12 23:53:41 |
> |23 | BackedUp | 2013-12-12 23:53:42 |
> |21 | BackedUp | 2013-12-13 00:53:37 |
> |19 | BackedUp | 2013-12-13 00:53:38 |
> +---+--+-+
> 24 rows in set (0.00 sec)
> This leaves behind incomplete snapshots. The directory does not have a ovf
> file and has incomplete vmdk file.
> [root@Rack3Host8 18]# ls -ltR
> .:
> total 12
> drwxr-xr-x. 2 root root 4096 Dec 12 22:56 36d7964c-e545-41d7-b303-96359a88dcef
> drwxr-xr-x. 2 root root 4096 Dec 12 22:30 68802f5f-84b1-42ad-8dca-4de7e83324e2
> ./36d7964c-e545-41d7-b303-96359a88dcef:
> total 403256
> -rw-r--r--. 1 root root 412524288 Dec 13 00:20
> 36d7964c-e545-41d7-b303-96359a88dcef-disk0.vmdk
> ./68802f5f-84b1-42ad-8dca-4de7e83324e2:
> total 448860
> -rw-r--r--. 1 root root 459168256 Dec 12 22:30
> 68802f5f-84b1-42ad-8dca-4de7e83324e2-disk0.vmdk
> -rw-r--r--. 1 root root 6454 Dec 12 22:30
> 68802f5f-84b1-42ad-8dca-4de7e83324e2.ovf
> [root@Rack3Host8 18]#
> Following exception seen in the management server logs:
> 2013-12-12 20:23:13,021 DEBUG [c.c.a.t.Request] (AgentManager-Handler-2:null)
> Seq 5-813367309: Processing: { Ans: , MgmtId: 95307354844397, via: 5, Ver:
> v1, Flags: 10,
> [{"org.apache.cloudstack.storage.command.CopyCmdAnswer":{"result":false,"details":"backup
> snapshot exception: Exception: java.lang.Exception\nMessage: Unable to
> finish the whole process to package as a OVA file\n","wait":0}}] }
> 2013-12-12 20:23:13,022 DEBUG [c.c.a.t.Request] (Job-Executor-1:ctx-83fb69a5
> ctx-51e56052) Seq 5-813367309: Received: { Ans: , MgmtId: 95307354844397,
> via: 5, Ver: v1, Flags: 10, { CopyCmdAnswer } }
> 2013-12-12 20:23:13,041 DEBUG [c.c.s.s.SnapshotManagerImpl]
> (Job-Exe
[jira] [Updated] (CLOUDSTACK-5483) [Automation] Failed to start Management server with 4.3 build
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan updated CLOUDSTACK-5483: Attachment: CLOUDSTACK-5483.rar > [Automation] Failed to start Management server with 4.3 build > - > > Key: CLOUDSTACK-5483 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5483 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.3.0 > Environment: Management server > Branch 4.3 >Reporter: Rayees Namathponnan >Priority: Blocker > Fix For: 4.3.0 > > Attachments: CLOUDSTACK-5483.rar > > > Steps to reproduce > Step 1 : Create new build from 4.3 branch > https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=d5c2fabb5205916054207691b6e065a61bbddc2f > Step 2 : Start Management server > Management server failed to start with below error > 2013-12-12 17:23:03,721 INFO [c.c.u.c.ComponentContext] (main:null) > Configuring > com.cloud.bridge.persist.dao.OfferingDaoImpl_EnhancerByCloudStack_eef0a451 > 2013-12-12 17:23:03,721 INFO [c.c.u.c.ComponentContext] (main:null) > Configuring > com.cloud.bridge.persist.dao.SMetaDaoImpl_EnhancerByCloudStack_b979449 > 2013-12-12 17:23:03,721 INFO [c.c.u.c.ComponentContext] (main:null) > Configuring > com.cloud.bridge.persist.dao.MultipartMetaDaoImpl_EnhancerByCloudStack_f30 > 01708 > 2013-12-12 17:23:03,722 INFO [c.c.u.c.ComponentContext] (main:null) > Configuring > com.cloud.bridge.persist.dao.UserCredentialsDaoImpl_EnhancerByCloudStack_a > c995f68 > 2013-12-12 17:23:03,722 INFO [c.c.u.c.ComponentContext] (main:null) > Configuring > com.cloud.bridge.persist.dao.CloudStackConfigurationDaoImpl_EnhancerByClou > dStack_1acba726 > 2013-12-12 17:23:03,722 INFO [c.c.u.c.ComponentContext] (main:null) > Configuring > com.cloud.bridge.persist.dao.BucketPolicyDaoImpl_EnhancerByCloudStack_7266 > 10eb > 2013-12-12 17:23:03,727 INFO [c.c.u.c.ComponentContext] (main:null) > Configuring > com.cloud.bridge.persist.dao.SObjectItemDaoImpl_EnhancerByCloudStack_5678c > 8b4 > 2013-12-12 17:23:03,727 INFO [c.c.u.c.ComponentContext] (main:null) > Configuring > com.cloud.bridge.persist.dao.MHostMountDaoImpl_EnhancerByCloudStack_ab7bfc > c3 > 2013-12-12 17:23:03,727 INFO [c.c.u.c.ComponentContext] (main:null) > Configuring > com.cloud.bridge.persist.dao.MHostDaoImpl_EnhancerByCloudStack_1d641f04 > 2013-12-12 17:23:03,727 INFO [c.c.u.c.ComponentContext] (main:null) > Configuring > com.cloud.bridge.persist.dao.MultiPartUploadsDaoImpl_EnhancerByCloudStack_ > d8d8c431 > 2013-12-12 17:23:03,728 INFO [c.c.u.c.ComponentContext] (main:null) > Configuring > com.cloud.bridge.persist.dao.SBucketDaoImpl_EnhancerByCloudStack_aa1500fc > 2013-12-12 17:23:03,728 INFO [c.c.u.c.ComponentContext] (main:null) > Configuring > com.cloud.bridge.persist.dao.SAclDaoImpl_EnhancerByCloudStack_1d03d978 > 2013-12-12 17:23:03,728 INFO [c.c.u.c.ComponentContext] (main:null) > Configuring > com.cloud.bridge.persist.dao.CloudStackSvcOfferingDaoImpl_EnhancerByCloudS > tack_a428db16 > 2013-12-12 17:23:03,733 INFO [c.c.u.c.ComponentContext] (main:null) > Configuring > com.cloud.bridge.persist.dao.MultiPartPartsDaoImpl_EnhancerByCloudStack_a4 > d2eeb3 > 2013-12-12 17:23:03,733 INFO [c.c.u.c.ComponentContext] (main:null) > Configuring > com.cloud.bridge.persist.dao.SHostDaoImpl_EnhancerByCloudStack_45f6954e > 2013-12-12 17:23:03,733 INFO [c.c.u.c.ComponentContext] (main:null) > Configuring > com.cloud.bridge.persist.dao.SObjectDaoImpl_EnhancerByCloudStack_2cd1053f > 2013-12-12 17:23:03,733 INFO [c.c.u.c.ComponentContext] (main:null) > Configuring > com.cloud.bridge.persist.dao.CloudStackUserDaoImpl_EnhancerByCloudStack_28 > 1f8a99 > 2013-12-12 17:23:03,734 INFO [c.c.u.c.ComponentContext] (main:null) > Configuring > com.cloud.bridge.service.core.ec2.EC2Engine_EnhancerByCloudStack_7f5de9ef > 2013-12-12 17:23:03,825 INFO [c.c.u.c.ComponentContext] (main:null) > Configuring > com.cloud.bridge.service.controller.s3.ServiceProvider_EnhancerByCloudStack_aa8e8464 > ~ > ~ > ~ -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Created] (CLOUDSTACK-5484) Vmware - Not able to deploy Vm with template that is 20GB virtual size ( actual size ~5gb).
Sangeetha Hariharan created CLOUDSTACK-5484:
---
Summary: Vmware - Not able to deploy Vm with template that is 20GB
virtual size ( actual size ~5gb).
Key: CLOUDSTACK-5484
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5484
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: Build from 4.3
Reporter: Sangeetha Hariharan
Priority: Critical
Fix For: 4.3.0
Deploy a Vm from a template that is 20GB virtual size ( actual size ~5gb).
Vm deployment fails.
I see the following exception when executing “CopyCommand” :
2013-12-12 16:07:22,761 DEBUG [c.c.a.t.Request] (Job-Executor-27:ctx-df5f3257
ctx-31077a83) Seq 1-2076837799: Executing: { Cmd , Mgm
tId: 95307354844397, via: 1(10.223.57.3), Ver: v1, Flags: 100011,
[{"org.apache.cloudstack.storage.command.CopyCommand":{"srcTO":{"or
g.apache.cloudstack.storage.to.TemplateObjectTO":{"path":"a7ecc9e5798534608d3ae0dfe6da1c48","uuid":"0b5961cf-af11-4a19-a3d6-0858575ca
b40","id":205,"format":"OVA","accountId":2,"hvm":true,"displayText":"temp-10-gb-new","imageDataStore":{"org.apache.cloudstack.storage
.to.PrimaryDataStoreTO":{"uuid":"a0c555cc-695c-3343-bfa0-3413a91dbfed","id":1,"poolType":"NetworkFilesystem","host":"10.223.57.195","
path":"/export/home/vmware/primary","port":2049,"url":"NetworkFilesystem://10.223.57.195//export/home/vmware/primary/?ROLE=Primary&ST
OREUUID=a0c555cc-695c-3343-bfa0-3413a91dbfed"}},"name":"275bf1387-d37d-31a9-9c65-fedcc79fdaf3","hypervisorType":"VMware"}},"destTO":{
"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"0cd27f84-c3e7-44d1-b2f7-5ada6cd8f679","volumeType":"ROOT","dataStore":{"or
g.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"a0c555cc-695c-3343-bfa0-3413a91dbfed","id":1,"poolType":"NetworkFilesyste
m","host":"10.223.57.195","path":"/export/home/vmware/primary","port":2049,"url":"NetworkFilesystem://10.223.57.195//export/home/vmwa
re/primary/?ROLE=Primary&STOREUUID=a0c555cc-695c-3343-bfa0-3413a91dbfed"}},"name":"ROOT-12","size":21474836480,"volumeId":12,"vmName"
:"i-3-12-VM","accountId":3,"format":"OVA","id":12,"deviceId":0,"hypervisorType":"VMware"}},"executeInSequence":false,"wait":0}}]
}
……
2013-12-12 16:27:22,951 ERROR [c.c.s.r.VmwareStorageProcessor]
(DirectAgent-212:ctx-781beb3d 10.223.57.3) clone volume from base image fa
iled due to Exception: javax.xml.ws.WebServiceException
Message: java.net.SocketTimeoutException: Read timed out
javax.xml.ws.WebServiceException: java.net.SocketTimeoutException: Read timed
out
at
com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.readResponseCodeAndMessage(HttpClientTransport.java:196)
at
com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.createResponsePacket(HttpTransportPipe.java:212)
at
com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:203)
at
com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:122)
at
com.sun.xml.internal.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:95)
at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:626)
at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:585)
at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:570)
at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:467)
at com.sun.xml.internal.ws.client.Stub.process(Stub.java:308)
at
com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(SEIStub.java:146)
at
com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:98)
at
com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78)
at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:129)
at $Proxy386.waitForUpdates(Unknown Source)
at
com.cloud.hypervisor.vmware.util.VmwareClient.waitForValues(VmwareClient.java:382)
at
com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:324)
at
com.cloud.hypervisor.vmware.mo.VirtualMachineMO.createFullClone(VirtualMachineMO.java:606)
at
com.cloud.storage.resource.VmwareStorageProcessor.createVMFullClone(VmwareStorageProcessor.java:282)
at
com.cloud.storage.resource.VmwareStorageProcessor.cloneVolumeFromBaseTemplate(VmwareStorageProcessor.java:368)
at
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:78)
at
com.cloud.storage.resource.VmwareStorageSubsystemCommandHandler.execute(VmwareStorageSubsystemCommandHandler.java:155)
at
com.cloud.storage.resource.StorageSub
[jira] [Commented] (CLOUDSTACK-5483) [Automation] Failed to start Management server with 4.3 build
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13847061#comment-13847061 ] Rayees Namathponnan commented on CLOUDSTACK-5483: - Observed below error in host log SEVERE: Exception sending context initialized event to listener instance of class org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListener org.springframework.context.ApplicationContextException: Failed to start bean 'cloudStackLifeCycle'; nested exception is org.jasypt.exceptions.EncryptionOperationNotPossibleException at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:170) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51) at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:339) at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:143) at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:108) at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:945) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:482) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContext(DefaultModuleDefinitionSet.java:141) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$2.with(DefaultModuleDefinitionSet.java:119) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:239) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:244) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:244) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:227) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContexts(DefaultModuleDefinitionSet.java:115) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.load(DefaultModuleDefinitionSet.java:78) at org.apache.cloudstack.spring.module.factory.ModuleBasedContextFactory.loadModules(ModuleBasedContextFactory.java:37) at org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.init(CloudStackSpringContext.java:69) at org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.(CloudStackSpringContext.java:56) at org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.(CloudStackSpringContext.java:60) at org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListener.contextInitialized(CloudStackContextLoaderListener.java:51) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3972) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4467) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1041) at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:964) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1277) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:321) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:722) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:593) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.l
[jira] [Created] (CLOUDSTACK-5483) [Automation] Failed to start Management server with 4.3 build
Rayees Namathponnan created CLOUDSTACK-5483: --- Summary: [Automation] Failed to start Management server with 4.3 build Key: CLOUDSTACK-5483 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5483 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.3.0 Environment: Management server Branch 4.3 Reporter: Rayees Namathponnan Priority: Blocker Fix For: 4.3.0 Steps to reproduce Step 1 : Create new build from 4.3 branch https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=d5c2fabb5205916054207691b6e065a61bbddc2f Step 2 : Start Management server Management server failed to start with below error 2013-12-12 17:23:03,721 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.OfferingDaoImpl_EnhancerByCloudStack_eef0a451 2013-12-12 17:23:03,721 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.SMetaDaoImpl_EnhancerByCloudStack_b979449 2013-12-12 17:23:03,721 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.MultipartMetaDaoImpl_EnhancerByCloudStack_f30 01708 2013-12-12 17:23:03,722 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.UserCredentialsDaoImpl_EnhancerByCloudStack_a c995f68 2013-12-12 17:23:03,722 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.CloudStackConfigurationDaoImpl_EnhancerByClou dStack_1acba726 2013-12-12 17:23:03,722 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.BucketPolicyDaoImpl_EnhancerByCloudStack_7266 10eb 2013-12-12 17:23:03,727 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.SObjectItemDaoImpl_EnhancerByCloudStack_5678c 8b4 2013-12-12 17:23:03,727 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.MHostMountDaoImpl_EnhancerByCloudStack_ab7bfc c3 2013-12-12 17:23:03,727 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.MHostDaoImpl_EnhancerByCloudStack_1d641f04 2013-12-12 17:23:03,727 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.MultiPartUploadsDaoImpl_EnhancerByCloudStack_ d8d8c431 2013-12-12 17:23:03,728 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.SBucketDaoImpl_EnhancerByCloudStack_aa1500fc 2013-12-12 17:23:03,728 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.SAclDaoImpl_EnhancerByCloudStack_1d03d978 2013-12-12 17:23:03,728 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.CloudStackSvcOfferingDaoImpl_EnhancerByCloudS tack_a428db16 2013-12-12 17:23:03,733 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.MultiPartPartsDaoImpl_EnhancerByCloudStack_a4 d2eeb3 2013-12-12 17:23:03,733 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.SHostDaoImpl_EnhancerByCloudStack_45f6954e 2013-12-12 17:23:03,733 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.SObjectDaoImpl_EnhancerByCloudStack_2cd1053f 2013-12-12 17:23:03,733 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.CloudStackUserDaoImpl_EnhancerByCloudStack_28 1f8a99 2013-12-12 17:23:03,734 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.service.core.ec2.EC2Engine_EnhancerByCloudStack_7f5de9ef 2013-12-12 17:23:03,825 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.service.controller.s3.ServiceProvider_EnhancerByCloudStack_aa8e8464 ~ ~ ~ -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (CLOUDSTACK-5482) Vmware - When nfs was down for about 1 hour , when snapshots were in progress , snapshot job failed when nfs was brought up leaving behind snaphots in "CreatedOnPri
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangeetha Hariharan updated CLOUDSTACK-5482:
Attachment: vmware.rar
> Vmware - When nfs was down for about 1 hour , when snapshots were in progress
> , snapshot job failed when nfs was brought up leaving behind snaphots in
> "CreatedOnPrimary" state.
> -
>
> Key: CLOUDSTACK-5482
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5482
> 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: Build from 4.3
>Reporter: Sangeetha Hariharan
> Fix For: 4.3.0
>
> Attachments: vmware.rar
>
>
> Set up :
> Advanced Zone with 2 5.1 ESXI hosts.
> Steps to reproduce the problem:
> 1. Deploy 5 Vms in each of the hosts , so we start with 11 Vms.
> 2. Start concurrent snapshots for ROOT volumes of all the Vms.
> 3. Shutdown the Secondary storage server when the snapshots are in the
> progress.
> 4. Bring the Secondary storage server up after 1 hour.
> When the secondary storage was down , 2 of the snapshots were already
> completed. 5 of them were in progress and the other 4 had not started yet.
> Once the secondary store was brought up , I see the snapshots that were in
> progress actually continue to download to secondary and succeed. But the
> other 4 snapshots error out.
> mysql> select volume_id,status,created from snapshots;
> +---+--+-+
> | volume_id | status | created |
> +---+--+-+
> |22 | BackedUp | 2013-12-12 23:24:13 |
> |21 | Destroyed| 2013-12-12 23:24:13 |
> |20 | BackedUp | 2013-12-12 23:24:14 |
> |19 | Destroyed| 2013-12-12 23:24:14 |
> |18 | BackedUp | 2013-12-12 23:24:14 |
> |17 | BackedUp | 2013-12-12 23:24:14 |
> |16 | BackedUp | 2013-12-12 23:24:14 |
> |14 | BackedUp | 2013-12-12 23:24:15 |
> |25 | BackedUp | 2013-12-12 23:24:15 |
> |24 | BackedUp | 2013-12-12 23:24:15 |
> |23 | BackedUp | 2013-12-12 23:24:15 |
> |22 | CreatedOnPrimary | 2013-12-12 23:53:38 |
> |21 | BackedUp | 2013-12-12 23:53:38 |
> |20 | BackedUp | 2013-12-12 23:53:38 |
> |19 | BackedUp | 2013-12-12 23:53:39 |
> |18 | CreatedOnPrimary | 2013-12-12 23:53:39 |
> |17 | CreatedOnPrimary | 2013-12-12 23:53:40 |
> |16 | CreatedOnPrimary | 2013-12-12 23:53:40 |
> |14 | BackedUp | 2013-12-12 23:53:40 |
> |25 | BackedUp | 2013-12-12 23:53:41 |
> |24 | BackedUp | 2013-12-12 23:53:41 |
> |23 | BackedUp | 2013-12-12 23:53:42 |
> |21 | BackedUp | 2013-12-13 00:53:37 |
> |19 | BackedUp | 2013-12-13 00:53:38 |
> +---+--+-+
> 24 rows in set (0.00 sec)
> This leaves behind incomplete snapshots. The directory does not have a ovf
> file and has incomplete vmdk file.
> [root@Rack3Host8 18]# ls -ltR
> .:
> total 12
> drwxr-xr-x. 2 root root 4096 Dec 12 22:56 36d7964c-e545-41d7-b303-96359a88dcef
> drwxr-xr-x. 2 root root 4096 Dec 12 22:30 68802f5f-84b1-42ad-8dca-4de7e83324e2
> ./36d7964c-e545-41d7-b303-96359a88dcef:
> total 403256
> -rw-r--r--. 1 root root 412524288 Dec 13 00:20
> 36d7964c-e545-41d7-b303-96359a88dcef-disk0.vmdk
> ./68802f5f-84b1-42ad-8dca-4de7e83324e2:
> total 448860
> -rw-r--r--. 1 root root 459168256 Dec 12 22:30
> 68802f5f-84b1-42ad-8dca-4de7e83324e2-disk0.vmdk
> -rw-r--r--. 1 root root 6454 Dec 12 22:30
> 68802f5f-84b1-42ad-8dca-4de7e83324e2.ovf
> [root@Rack3Host8 18]#
> Following exception seen in the management server logs:
> 2013-12-12 20:23:13,021 DEBUG [c.c.a.t.Request] (AgentManager-Handler-2:null)
> Seq 5-813367309: Processing: { Ans: , MgmtId: 95307354844397, via: 5, Ver:
> v1, Flags: 10,
> [{"org.apache.cloudstack.storage.command.CopyCmdAnswer":{"result":false,"details":"backup
> snapshot exception: Exception: java.lang.Exception\nMessage: Unable to
> finish the whole process to package as a OVA file\n","wait":0}}] }
> 2013-12-12 20:23:13,022 DEBUG [c.c.a.t.Request] (Job-Executor-1:ctx-83fb69a5
> ctx-51e56052) Seq 5-813367309: Received: { Ans: , MgmtId: 95307354844397,
> via: 5, Ver: v1, Flags: 10, { CopyCmdAnswer } }
> 2013-12-12 20:23:13,041 DEBUG [c.c.s.s.SnapshotManagerImpl]
> (Job-Executor-1:ctx-
[jira] [Updated] (CLOUDSTACK-5482) Vmware - When nfs was down for about 1 hour , when snapshots were in progress , snapshot job failed when nfs was brought up leaving behind snaphots in "CreatedOnPri
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangeetha Hariharan updated CLOUDSTACK-5482:
Description:
Set up :
Advanced Zone with 2 5.1 ESXI hosts.
Steps to reproduce the problem:
1. Deploy 5 Vms in each of the hosts , so we start with 11 Vms.
2. Start concurrent snapshots for ROOT volumes of all the Vms.
3. Shutdown the Secondary storage server when the snapshots are in the progress.
4. Bring the Secondary storage server up after 1 hour.
When the secondary storage was down , 2 of the snapshots were already
completed. 5 of them were in progress and the other 4 had not started yet.
Once the secondary store was brought up , I see the snapshots that were in
progress actually continue to download to secondary and succeed. But the other
4 snapshots error out.
mysql> select volume_id,status,created from snapshots;
+---+--+-+
| volume_id | status | created |
+---+--+-+
|22 | BackedUp | 2013-12-12 23:24:13 |
|21 | Destroyed| 2013-12-12 23:24:13 |
|20 | BackedUp | 2013-12-12 23:24:14 |
|19 | Destroyed| 2013-12-12 23:24:14 |
|18 | BackedUp | 2013-12-12 23:24:14 |
|17 | BackedUp | 2013-12-12 23:24:14 |
|16 | BackedUp | 2013-12-12 23:24:14 |
|14 | BackedUp | 2013-12-12 23:24:15 |
|25 | BackedUp | 2013-12-12 23:24:15 |
|24 | BackedUp | 2013-12-12 23:24:15 |
|23 | BackedUp | 2013-12-12 23:24:15 |
|22 | CreatedOnPrimary | 2013-12-12 23:53:38 |
|21 | BackedUp | 2013-12-12 23:53:38 |
|20 | BackedUp | 2013-12-12 23:53:38 |
|19 | BackedUp | 2013-12-12 23:53:39 |
|18 | CreatedOnPrimary | 2013-12-12 23:53:39 |
|17 | CreatedOnPrimary | 2013-12-12 23:53:40 |
|16 | CreatedOnPrimary | 2013-12-12 23:53:40 |
|14 | BackedUp | 2013-12-12 23:53:40 |
|25 | BackedUp | 2013-12-12 23:53:41 |
|24 | BackedUp | 2013-12-12 23:53:41 |
|23 | BackedUp | 2013-12-12 23:53:42 |
|21 | BackedUp | 2013-12-13 00:53:37 |
|19 | BackedUp | 2013-12-13 00:53:38 |
+---+--+-+
24 rows in set (0.00 sec)
This leaves behind incomplete snapshots. The directory does not have a ovf file
and has incomplete vmdk file.
[root@Rack3Host8 18]# ls -ltR
.:
total 12
drwxr-xr-x. 2 root root 4096 Dec 12 22:56 36d7964c-e545-41d7-b303-96359a88dcef
drwxr-xr-x. 2 root root 4096 Dec 12 22:30 68802f5f-84b1-42ad-8dca-4de7e83324e2
./36d7964c-e545-41d7-b303-96359a88dcef:
total 403256
-rw-r--r--. 1 root root 412524288 Dec 13 00:20
36d7964c-e545-41d7-b303-96359a88dcef-disk0.vmdk
./68802f5f-84b1-42ad-8dca-4de7e83324e2:
total 448860
-rw-r--r--. 1 root root 459168256 Dec 12 22:30
68802f5f-84b1-42ad-8dca-4de7e83324e2-disk0.vmdk
-rw-r--r--. 1 root root 6454 Dec 12 22:30
68802f5f-84b1-42ad-8dca-4de7e83324e2.ovf
[root@Rack3Host8 18]#
Following exception seen in the management server logs:
2013-12-12 20:23:13,021 DEBUG [c.c.a.t.Request] (AgentManager-Handler-2:null)
Seq 5-813367309: Processing: { Ans: , MgmtId: 95307354844397, via: 5, Ver: v1,
Flags: 10,
[{"org.apache.cloudstack.storage.command.CopyCmdAnswer":{"result":false,"details":"backup
snapshot exception: Exception: java.lang.Exception\nMessage: Unable to finish
the whole process to package as a OVA file\n","wait":0}}] }
2013-12-12 20:23:13,022 DEBUG [c.c.a.t.Request] (Job-Executor-1:ctx-83fb69a5
ctx-51e56052) Seq 5-813367309: Received: { Ans: , MgmtId: 95307354844397, via:
5, Ver: v1, Flags: 10, { CopyCmdAnswer } }
2013-12-12 20:23:13,041 DEBUG [c.c.s.s.SnapshotManagerImpl]
(Job-Executor-1:ctx-83fb69a5 ctx-51e56052) Failed to create snapshot
com.cloud.utils.exception.CloudRuntimeException: backup snapshot exception:
Exception: java.lang.Exception
Message: Unable to finish the whole process to package as a OVA file
at
org.apache.cloudstack.storage.snapshot.SnapshotServiceImpl.backupSnapshot(SnapshotServiceImpl.java:275)
at
org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy.backupSnapshot(XenserverSnapshotStrategy.java:135)
at
org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy.takeSnapshot(XenserverSnapshotStrategy.java:294)
at
com.cloud.storage.snapshot.SnapshotManagerImpl.takeSnapshot(SnapshotManagerImpl.java:951)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.i
[jira] [Updated] (CLOUDSTACK-5482) Vmware - When nfs was down for about 1 hour , when snapshots were in progress , snapshot job failed when nfs was brought up leaving behind snaphots in "CreatedOnPri
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangeetha Hariharan updated CLOUDSTACK-5482:
Description:
Set up :
Advanced Zone with 2 5.1 ESXI hosts.
Steps to reproduce the problem:
1. Deploy 5 Vms in each of the hosts , so we start with 11 Vms.
2. Start concurrent snapshots for ROOT volumes of all the Vms.
3. Shutdown the Secondary storage server when the snapshots are in the progress.
4. Bring the Secondary storage server up after 1 hour.
When the secondary storage was down , 2 of the snapshots were already
completed. 5 of them were in progress and the other 4 had not started yet.
Once the secondary store was brought up , I see the snapshots that were in
progress actually continue to download to secondary and succeed. But the other
4 snapshots error out.
mysql> select volume_id,status,created from snapshots;
+---+--+-+
| volume_id | status | created |
+---+--+-+
|22 | BackedUp | 2013-12-12 23:24:13 |
|21 | Destroyed| 2013-12-12 23:24:13 |
|20 | BackedUp | 2013-12-12 23:24:14 |
|19 | Destroyed| 2013-12-12 23:24:14 |
|18 | BackedUp | 2013-12-12 23:24:14 |
|17 | BackedUp | 2013-12-12 23:24:14 |
|16 | BackedUp | 2013-12-12 23:24:14 |
|14 | BackedUp | 2013-12-12 23:24:15 |
|25 | BackedUp | 2013-12-12 23:24:15 |
|24 | BackedUp | 2013-12-12 23:24:15 |
|23 | BackedUp | 2013-12-12 23:24:15 |
|22 | CreatedOnPrimary | 2013-12-12 23:53:38 |
|21 | BackedUp | 2013-12-12 23:53:38 |
|20 | BackedUp | 2013-12-12 23:53:38 |
|19 | BackedUp | 2013-12-12 23:53:39 |
|18 | CreatedOnPrimary | 2013-12-12 23:53:39 |
|17 | CreatedOnPrimary | 2013-12-12 23:53:40 |
|16 | CreatedOnPrimary | 2013-12-12 23:53:40 |
|14 | BackedUp | 2013-12-12 23:53:40 |
|25 | BackedUp | 2013-12-12 23:53:41 |
|24 | BackedUp | 2013-12-12 23:53:41 |
|23 | BackedUp | 2013-12-12 23:53:42 |
|21 | BackedUp | 2013-12-13 00:53:37 |
|19 | BackedUp | 2013-12-13 00:53:38 |
+---+--+-+
24 rows in set (0.00 sec)
Following exception seen in the management server logs:
2013-12-12 20:23:13,021 DEBUG [c.c.a.t.Request] (AgentManager-Handler-2:null)
Seq 5-813367309: Processing: { Ans: , MgmtId: 95307354844397, via: 5, Ver: v1,
Flags: 10,
[{"org.apache.cloudstack.storage.command.CopyCmdAnswer":{"result":false,"details":"backup
snapshot exception: Exception: java.lang.Exception\nMessage: Unable to finish
the whole process to package as a OVA file\n","wait":0}}] }
2013-12-12 20:23:13,022 DEBUG [c.c.a.t.Request] (Job-Executor-1:ctx-83fb69a5
ctx-51e56052) Seq 5-813367309: Received: { Ans: , MgmtId: 95307354844397, via:
5, Ver: v1, Flags: 10, { CopyCmdAnswer } }
2013-12-12 20:23:13,041 DEBUG [c.c.s.s.SnapshotManagerImpl]
(Job-Executor-1:ctx-83fb69a5 ctx-51e56052) Failed to create snapshot
com.cloud.utils.exception.CloudRuntimeException: backup snapshot exception:
Exception: java.lang.Exception
Message: Unable to finish the whole process to package as a OVA file
at
org.apache.cloudstack.storage.snapshot.SnapshotServiceImpl.backupSnapshot(SnapshotServiceImpl.java:275)
at
org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy.backupSnapshot(XenserverSnapshotStrategy.java:135)
at
org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy.takeSnapshot(XenserverSnapshotStrategy.java:294)
at
com.cloud.storage.snapshot.SnapshotManagerImpl.takeSnapshot(SnapshotManagerImpl.java:951)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Prox
[jira] [Created] (CLOUDSTACK-5482) Vmware - When nfs was down for about 1 hour , when snapshots were in progress , snapshot job failed when nfs was brought up leaving behind snaphots in "CreatedOnPri
Sangeetha Hariharan created CLOUDSTACK-5482: --- Summary: Vmware - When nfs was down for about 1 hour , when snapshots were in progress , snapshot job failed when nfs was brought up leaving behind snaphots in "CreatedOnPrimary" state. Key: CLOUDSTACK-5482 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5482 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: Build from 4.3 Reporter: Sangeetha Hariharan Fix For: 4.3.0 Set up : Advanced Zone with 2 5.1 ESXI hosts. Steps to reproduce the problem: 1. Deploy 5 Vms in each of the hosts , so we start with 11 Vms. 2. Start concurrent snapshots for ROOT volumes of all the Vms. 3. Shutdown the Secondary storage server when the snapshots are in the progress. 4. Bring the Secondary storage server up after 1 hour. When the secondary storage was down , 2 of the snapshots were already completed. 5 of them were in progress and the other 4 had not started yet. Once the secondary store was brought up , I see the snapshots that were in progress actually continue to download to secondary and succeed. But the other 4 snapshots error out. mysql> select volume_id,status,created from snapshots; +---+--+-+ | volume_id | status | created | +---+--+-+ |22 | BackedUp | 2013-12-12 23:24:13 | |21 | Destroyed| 2013-12-12 23:24:13 | |20 | BackedUp | 2013-12-12 23:24:14 | |19 | Destroyed| 2013-12-12 23:24:14 | |18 | BackedUp | 2013-12-12 23:24:14 | |17 | BackedUp | 2013-12-12 23:24:14 | |16 | BackedUp | 2013-12-12 23:24:14 | |14 | BackedUp | 2013-12-12 23:24:15 | |25 | BackedUp | 2013-12-12 23:24:15 | |24 | BackedUp | 2013-12-12 23:24:15 | |23 | BackedUp | 2013-12-12 23:24:15 | |22 | CreatedOnPrimary | 2013-12-12 23:53:38 | |21 | BackedUp | 2013-12-12 23:53:38 | |20 | BackedUp | 2013-12-12 23:53:38 | |19 | BackedUp | 2013-12-12 23:53:39 | |18 | CreatedOnPrimary | 2013-12-12 23:53:39 | |17 | CreatedOnPrimary | 2013-12-12 23:53:40 | |16 | CreatedOnPrimary | 2013-12-12 23:53:40 | |14 | BackedUp | 2013-12-12 23:53:40 | |25 | BackedUp | 2013-12-12 23:53:41 | |24 | BackedUp | 2013-12-12 23:53:41 | |23 | BackedUp | 2013-12-12 23:53:42 | |21 | BackedUp | 2013-12-13 00:53:37 | |19 | BackedUp | 2013-12-13 00:53:38 | +---+--+-+ 24 rows in set (0.00 sec) -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-5481) Regular User is unable to use "Add Isolated Network" Button on the UI
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13847010#comment-13847010
]
Chandan Purushothama commented on CLOUDSTACK-5481:
--
Following are the Steps to Reproduce the Bug:
1. Create a Regular User Account in ROOT Domain.
2. Log off from the admin account and Log in as the regular user
3. Click on Network Button on the Left menu
4. Click on the "Add Isolated Network" Button
Observe the following Fired API Information from the Firebug Tool on Firefox:
http://10.223.130.79:8080/client/api?command=listDomains&listAll=true&response=json&sessionkey=0EMVwSj27GaGwGyPMOCnCPbCLRQ%3D&_=1386896472972
{ "errorresponse" :
{"uuidList":[],"errorcode":432,"cserrorcode":,"errortext":"The given
command does not exist or it is not available for user"} }
> Regular User is unable to use "Add Isolated Network" Button on the UI
> -
>
> Key: CLOUDSTACK-5481
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5481
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
>Affects Versions: 4.3.0
>Reporter: Chandan Purushothama
>Assignee: Wei Zhou
>Priority: Critical
> Fix For: 4.3.0
>
> Attachments: This_bug_was_produced_by_this_check_in.PNG,
> UICapture37.PNG
>
>
> The corresponding UI Bug screenshot has been attached to the bug report.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-1225) Storage System vm id keeps on increasing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846980#comment-13846980 ] Anthony Carter commented on CLOUDSTACK-1225: I got the same issue with Cloudstack. Found that it was because I hadn't given privileges to the xenserver hosts to access the secondary NFS. Once I did, the V-2-VM started without issue. Problem here is from the information and diagrams I was under the impression that Secondary was used by the POD, not the Cluster, and thus the hosts (in the cluster) should never actually be talking to the Secondary, only the Primary. Go figure. Maybe it is my misunderstanding of the architecture here, but it seems to be contrary to the information provided. > Storage System vm id keeps on increasing > - > > Key: CLOUDSTACK-1225 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1225 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.0.1 > Environment: Cloud Stack Mgmnt server 4.0.1 :XCP Virtual Machine > running with CentOS release 6.2 (Final)/ 2.6.32-220.el6.x86_64 > Mysql:5.1.67,Host: XCP Host 1.4.90-53341c,Storage: both primary and secondary > is on management server (/export/primary and /export/secondary),ip address: > Every machine is having public ip in the same CIDR. >Reporter: kevin parker >Priority: Minor > Labels: 4.0.1_Candidate > > Its been 3 weeks since i am working on Cloud Stack 4.0.1 > (http://jenkins.cloudstack.org/view/4.0.1/job/build-4.0.1-nonoss-rhel63/) > but couldn't even start system vms..In UI its showing "Creating system VMs > (this may take a while)" but nothing is happening and i also noticed that > select * from cloud.vm_instance\G; is increasing every minute. every > minute-two new id is getting generated with state Expunging. > But In UI it is still trying to create system VM but is actually failing but > there is no way to alert user about this.Will this ever stop? > sample error: > Exception while trying to start secondary storage vm > com.cloud.exception.InsufficientServerCapacityException: Unable to create a > deployment for VM[SecondaryStorageVm|s-91-VM]Scope=interface > com.cloud.dc.DataCenter; id=1 > 2013-02-11 08:15:59,375 WARN [cloud.api.ApiDispatcher] > (Job-Executor-8:job-8) class com.cloud.api.ServerApiException : Fail to start > system vm > this is the log:http://pastebin.com/fE5uUgZt -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (CLOUDSTACK-5481) Regular User is unable to use "Add Isolated Network" Button on the UI
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-5481: - Assignee: Wei Zhou > Regular User is unable to use "Add Isolated Network" Button on the UI > - > > Key: CLOUDSTACK-5481 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5481 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 >Reporter: Chandan Purushothama >Assignee: Wei Zhou >Priority: Critical > Fix For: 4.3.0 > > Attachments: This_bug_was_produced_by_this_check_in.PNG, > UICapture37.PNG > > > The corresponding UI Bug screenshot has been attached to the bug report. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (CLOUDSTACK-5481) Regular User is unable to use "Add Isolated Network" Button on the UI
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-5481: - Attachment: This_bug_was_produced_by_this_check_in.PNG > Regular User is unable to use "Add Isolated Network" Button on the UI > - > > Key: CLOUDSTACK-5481 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5481 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 >Reporter: Chandan Purushothama >Priority: Critical > Fix For: 4.3.0 > > Attachments: This_bug_was_produced_by_this_check_in.PNG, > UICapture37.PNG > > > The corresponding UI Bug screenshot has been attached to the bug report. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-5345) dont show upgrade router to new template if the router is already upgraded
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846946#comment-13846946 ] ASF subversion and git services commented on CLOUDSTACK-5345: - Commit d5fcc6ef5a75544e36cddc8f730fd61197fb324b in branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d5fcc6e ] CLOUDSTACK-5345: UI > Infrastructure > virtual routers > no grouping > hide Upgrade Router to Use Newer Template action when a router has latest version (i.e. does not require upgrade). > dont show upgrade router to new template if the router is already upgraded > -- > > Key: CLOUDSTACK-5345 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5345 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 >Reporter: shweta agarwal >Assignee: Jessica Wang > Fix For: 4.3.0 > > Attachments: upgrade router.jpg > > > Repro steps : > if routers are already upgraded to new system VM template don't show upgrade > router to new template action item. > Applicable for group by zone/pod cluster also. > i.e if all the VRs in a pod/cluster/zone are upgraded and requires upgrade > comes is no t hen don't show upgrade router to new template action button. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-5345) dont show upgrade router to new template if the router is already upgraded
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846944#comment-13846944 ] ASF subversion and git services commented on CLOUDSTACK-5345: - Commit d5c2fabb5205916054207691b6e065a61bbddc2f in branch refs/heads/4.3 from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d5c2fab ] CLOUDSTACK-5345: UI > Infrastructure > virtual routers > no grouping > hide Upgrade Router to Use Newer Template action when a router has latest version (i.e. does not require upgrade). > dont show upgrade router to new template if the router is already upgraded > -- > > Key: CLOUDSTACK-5345 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5345 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 >Reporter: shweta agarwal >Assignee: Jessica Wang > Fix For: 4.3.0 > > Attachments: upgrade router.jpg > > > Repro steps : > if routers are already upgraded to new system VM template don't show upgrade > router to new template action item. > Applicable for group by zone/pod cluster also. > i.e if all the VRs in a pod/cluster/zone are upgraded and requires upgrade > comes is no t hen don't show upgrade router to new template action button. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Created] (CLOUDSTACK-5481) Regular User is unable to use "Add Isolated Network" Button on the UI
Chandan Purushothama created CLOUDSTACK-5481: Summary: Regular User is unable to use "Add Isolated Network" Button on the UI Key: CLOUDSTACK-5481 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5481 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.3.0 Reporter: Chandan Purushothama Priority: Critical Fix For: 4.3.0 Attachments: UICapture37.PNG The corresponding UI Bug screenshot has been attached to the bug report. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (CLOUDSTACK-5481) Regular User is unable to use "Add Isolated Network" Button on the UI
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Purushothama updated CLOUDSTACK-5481: - Attachment: UICapture37.PNG > Regular User is unable to use "Add Isolated Network" Button on the UI > - > > Key: CLOUDSTACK-5481 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5481 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 >Reporter: Chandan Purushothama >Priority: Critical > Fix For: 4.3.0 > > Attachments: UICapture37.PNG > > > The corresponding UI Bug screenshot has been attached to the bug report. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Created] (CLOUDSTACK-5480) [UI] Unable to create account in sequence
Rayees Namathponnan created CLOUDSTACK-5480: --- Summary: [UI] Unable to create account in sequence Key: CLOUDSTACK-5480 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5480 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.3.0 Environment: UI Branch : 4.3 Reporter: Rayees Namathponnan Assignee: Ian Duffy Priority: Critical Fix For: 4.3.0 Steps to reproduce Step 1 : Create account with User name : a, password a: email a...@a.com type : admin Step 2 : Without refreshing the page create another account User name b : password b : email b...@b.com type : admin Result Failed to create second account, with error in password confirmation dialog "Please enter the same value again". You need to set password first account's password (here a) to create second account Looks like, it got broken as part of commit 532e04db1a66f1f89bb940917928dfa97dd8748a Author: Ian Duffy Date: Fri Aug 2 09:27:38 2013 +0100 Disable password changing when ldap is enabled Signed-off-by: Abhinandan Prateek commit ec064b307734dcb1d4304454de466d6e70e019fb Author: Ian Duffy Date: Mon Jul 29 05:58:00 2013 -0400 New LDAP UI Signed-off-by: Sebastien Goasguen commit eaa41433715ba1a1137ad9f346ea8569e31e4560 Author: Ian Duffy Date: Thu Jul 25 10:24:13 2013 +0100 Merge LDAPPlugin Signed-off-by: Abhinandan Prateek -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Resolved] (CLOUDSTACK-4850) [UCS] using template instead of cloning profile
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang resolved CLOUDSTACK-4850. -- Resolution: Fixed > [UCS] using template instead of cloning profile > --- > > Key: CLOUDSTACK-4850 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4850 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UCS >Affects Versions: 4.2.1 >Reporter: frank zhang >Assignee: Jessica Wang > Fix For: 4.3.0 > > -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Resolved] (CLOUDSTACK-3561) When inputting the nfs server in secondary storage, if once it's required, it always reports required
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang resolved CLOUDSTACK-3561. -- Resolution: Fixed This bug has been fixed by an another check-in. > When inputting the nfs server in secondary storage, if once it's required, it > always reports required > - > > Key: CLOUDSTACK-3561 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3561 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 >Reporter: Alex Huang >Assignee: Jessica Wang > Fix For: 4.3.0 > > > In Add Zone Wizard, Get to the Add Secondary Storage dialogue box, Click next > without filling in the NFS Server entry box, it says Required. That's > correct. However, after that, I filled in the entry box and clicked next > again and it still says required. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Assigned] (CLOUDSTACK-3111) [UI] Storage tab is not showing the Hypervisor column as 'KVM' if the (root/data)disk is attached to instance running in KVM Hypervisor.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang reassigned CLOUDSTACK-3111: Assignee: Abhinandan Prateek (was: Jessica Wang) Ahhinandan, This is an API bug, not UI bug. Please assign it to an API developer. Jessica > [UI] Storage tab is not showing the Hypervisor column as 'KVM' if the > (root/data)disk is attached to instance running in KVM Hypervisor. > > > Key: CLOUDSTACK-3111 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3111 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: 4.1.1, 4.2.0 >Reporter: Rajesh Battala >Assignee: Abhinandan Prateek > Fix For: 4.3.0 > > Attachments: screen1.png > > > Attaching the screenshot. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Assigned] (CLOUDSTACK-5393) [Automation] Failed to create snapshot from ROOT volume in KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Min Chen reassigned CLOUDSTACK-5393:
Assignee: Min Chen
> [Automation] Failed to create snapshot from ROOT volume in KVM
> --
>
> Key: CLOUDSTACK-5393
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5393
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Snapshot
>Affects Versions: 4.3.0
> Environment: KVM (RHEL 6.3)
> Branch : 4.3
>Reporter: Rayees Namathponnan
>Assignee: Min Chen
> Fix For: 4.3.0
>
> Attachments: agent1.rar, agent2.rar, management-server.rar, ssvm.rar
>
>
> Steps to reproduce
> 1) Create advanced zone in KVM
> 2) Deploy VM
> 3 ) Stop VM
> 4 ) Create snapshot from root volume
> Snapshot creation failed with below exception
> 2013-12-05 15:39:44,194 DEBUG [c.c.a.t.Request] (Job-Executor-64:ctx-1b710e00
> ctx-3cf3df4e) Seq 1-1244399478: Received: { Ans: , MgmtId: 29066118877352,
> via: 1, Ver: v1, Flags: 10, { CreateObjectAnswer } }
> 2013-12-05 15:39:44,284 DEBUG [o.a.c.s.m.AncientDataMotionStrategy]
> (Job-Executor-64:ctx-1b710e00 ctx-3cf3df4e) copyAsync inspecting src type
> SNAPSHOT copyAsync inspecting dest type SNAPSHOT
> 2013-12-05 15:39:44,332 DEBUG [c.c.a.t.Request] (Job-Executor-64:ctx-1b710e00
> ctx-3cf3df4e) Seq 2-332864214: Sending { Cmd , MgmtId: 29066118877352, via:
> 2(Rack2Host12.lab.vmops.com), Ver: v1, Flags: 100011, [{"org.apache.cl
> oudstack.storage.command.CopyCommand":{"srcTO":{"org.apache.cloudstack.storage.to.SnapshotObjectTO":{"path":"/mnt/fff90cb5-06dd-33b3-8815-d78c08ca01d9/a44ddf93-9fa2-497f-aff6-cf4951128215/8f7d268f-1a96-4d70-9c48-cb7f6cc935a8"
> ,"volume":{"uuid":"a44ddf93-9fa2-497f-aff6-cf4951128215","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"fff90cb5-06dd-33b3-8815-d78c08ca01d9","id":1,"poolType":"NetworkFilesyst
> em","host":"10.223.110.232","path":"/export/home/rayees/SC_QA_AUTO4/primary","port":2049,"url":"NetworkFilesystem://10.223.110.232//export/home/rayees/SC_QA_AUTO4/primary/?ROLE=Primary&STOREUUID=fff90cb5-06dd-33b3-8815-d78c08
> ca01d9"}},"name":"ROOT-919","size":8589934592,"path":"a44ddf93-9fa2-497f-aff6-cf4951128215","volumeId":988,"vmName":"i-2-919-QA","accountId":2,"format":"QCOW2","id":988,"deviceId":0,"hypervisorType":"KVM"},"parentSnapshotPath
> ":"/mnt/fff90cb5-06dd-33b3-8815-d78c08ca01d9/a44ddf93-9fa2-497f-aff6-cf4951128215/d43b61bc-4ade-4753-b1d9-c0398388147d","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"fff90cb5-06dd-33b3-8815-d78c08ca01d9","id":1,"poolType":"NetworkFilesystem","host":"10.223.110.232","path":"/export/home/rayees/SC_QA_AUTO4/primary","port":2049,"url":"NetworkFilesystem://10.223.110.232//export/home/rayees/SC_QA_AUTO4/primary/?ROLE=Primary&STOREUUID=fff90cb5-06dd-33b3-8815-d78c08ca01d9"}},"vmName":"i-2-919-QA","name":"QA-eb54bbfa-12d5-49b5-808f-864dddedc1fd_ROOT-919_20131205233943","hypervisorType":"KVM","id":54,"quiescevm":false}},"destTO":{"org.apache.cloudstack.storage.to.SnapshotObjectTO":{"path":"snapshots/2/988","volume":{"uuid":"a44ddf93-9fa2-497f-aff6-cf4951128215","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"fff90cb5-06dd-33b3-8815-d78c08ca01d9","id":1,"poolType":"NetworkFilesystem","host":"10.223.110.232","path":"/export/home/rayees/SC_QA_AUTO4/primary","port":2049,"url":"NetworkFilesystem://10.223.110.232//export/home/rayees/SC_QA_AUTO4/primary/?ROLE=Primary&STOREUUID=fff90cb5-06dd-33b3-8815-d78c08ca01d9"}},"name":"ROOT-919","size":8589934592,"path":"a44ddf93-9fa2-497f-aff6-cf4951128215","volumeId":988,"vmName":"i-2-919-QA","accountId":2,"format":"QCOW2","id":988,"deviceId":0,"hypervisorType":"KVM"},"dataStore":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.223.110.232:/export/home/rayees/SC_QA_AUTO4/secondary","_role":"Image"}},"vmName":"i-2-919-QA","name":"QA-eb54bbfa-12d5-49b5-808f-864dddedc1fd_ROOT-919_20131205233943","hypervisorType":"KVM","id":54,"quiescevm":false}},"executeInSequence":false,"wait":21600}}]
> }
> 2013-12-05 15:39:44,501 DEBUG [c.c.a.t.Request]
> (StatsCollector-3:ctx-3ac54662) Seq 1-1244399477: Received: { Ans: , MgmtId:
> 29066118877352, via: 1, Ver: v1, Flags: 10, { GetVmStatsAnswer } }
> 2013-12-05 15:39:44,900 DEBUG [c.c.a.t.Request] (AgentManager-Handler-1:null)
> Seq 2-332864214: Processing: { Ans: , MgmtId: 29066118877352, via: 2, Ver:
> v1, Flags: 10,
> [{"org.apache.cloudstack.storage.command.CopyCmdAnswer":{"result":false,"details":"/usr/share/cloudstack-common/scripts/storage/qcow2/managesnapshot.sh:
> line 178: 26840 Floating point exception(core dumped) $qemu_img convert -f
>
[jira] [Updated] (CLOUDSTACK-5469) Snapshot creation fails with following exception - "Failed to backup snapshot: qemu-img: Could not delete snapshot '89eced14-9121-44a7-bb97-26b567795726': -2 (No suc
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-5469: --- Assignee: edison su > Snapshot creation fails with following exception - "Failed to backup > snapshot: qemu-img: Could not delete snapshot > '89eced14-9121-44a7-bb97-26b567795726': -2 (No such file or directory)" > -- > > Key: CLOUDSTACK-5469 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5469 > 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: Build from 4.3 >Reporter: Sangeetha Hariharan >Assignee: edison su >Priority: Critical > Fix For: 4.3.0 > > Attachments: deletesnapshot.rar > > > Set up: > Advanced Zone with 2 KVM (RHEL 6.3) hosts. > 2 NFS secondary stores set up. > Steps to reproduce the problem: > 1. Deploy 5 Vms in each of the hosts with 10 GB ROOT volume size , so we > start with 10 Vms. > 2. Start concurrent snapshots for ROOT volumes of all the Vms. > 1 of the secondary store -ss1- had the nfs server down for 1 and 1/2 hours. > The other secondary store -ss2 - was always reachable. > Snapshot tasks that went to the ss1 , succeeded after the nfs server was > brought up (It temporarily halted when the the nfs server was down and > resumed when the nsf server was made available). > First set of snapshot tasks that went to the ss2 all succeeded. > But the next hourly snapshot tasks, few of them failed with following > exception: 2013-12-11 16:33:22,427 DEBUG [c.c.s.s.SnapshotManagerImpl] > (Job-Executor-64:ctx-9c70ad77 ctx-3d959fa6) Failed t o create snapshot > com.cloud.utils.exception.CloudRuntimeException: Failed to backup snapshot: > qemu-img: Could not delete snapshot '89eced14-9121-44a7-bb97-26b567795726': > -2 (No such file or directory)Failed to delete snapshot 89eced14-9121-44 > a7-bb97-26b567795726 for path > /mnt/c20ea198-e8ca-33c3-9f11-e361ec9b5532/71a5dce2-da7c-4692-8f25-ba37e5296886 > at > org.apache.cloudstack.storage.snapshot.SnapshotServiceImpl.backupSnapshot(SnapshotServiceImpl.java:27 > 5) at > org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy.backupSnapshot(XenserverSnapshotStra > tegy.java:135) at > org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy.takeSnapshot(XenserverSnapshotStrate > gy.java:294) at > com.cloud.storage.snapshot.SnapshotManagerImpl.takeSnapshot(SnapshotManagerImpl.java:951) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocati > on.java:183) at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java: > 150) at > org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.ja > va:91) at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java: > 172) at > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) > at $Proxy161.takeSnapshot(Unknown Source) at > org.apache.cloudstack.storage.volume.VolumeServiceImpl.takeSnapshot(VolumeServiceImpl.java:1341) > at > com.cloud.storage.VolumeApiServiceImpl.takeSnapshot(VolumeApiServiceImpl.java:1461) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) > Copy to the secondary has succeed. Failure happens after this. > [root@Rack3Host5 118]# ls -ltr > total 10002852 > -rw-r--r--. 1 root root 3637903360 Dec 11 20:33 > 89eced14-9121-44a7-bb97-26b567795726 > -rw-r--r--. 1 root root 3638755328 Dec 11 21:37 > b38d93db-4c14-45a7-9274-639ad95a3f29 > -rw-r--r--. 1 root root 2956619776 Dec 11 22:24 > 452c8841-2025-41da-b6ec-49cea2a49da8 > [root@Rack3Host5 118]# > Following are the volumes which are in "CreatedOnPrimary" stat
[jira] [Updated] (CLOUDSTACK-5452) KVM - Agent is not able to connect back if management server was restarted when there are pending tasks to this host.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-5452: --- Assignee: edison su > KVM - Agent is not able to connect back if management server was restarted > when there are pending tasks to this host. > - > > Key: CLOUDSTACK-5452 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5452 > 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: Build from 4.3 >Reporter: Sangeetha Hariharan >Assignee: edison su >Priority: Critical > Fix For: 4.3.0 > > > KVM - Agent is not able to connect back if management server was restarted > when there are pending tasks to this host. > Steps to reproduce the problem: > Set up - Advanced zone with 2 KVM ( RHEL 6.3) hosts. > Deployed few Vms. > Started snapshot for ROOT volume of the VMs. > When the snapshot processes are still in progress , restart management > server. > When the management sever started , the KVM hosts remain in disconnected > state. > Attempt to stop Vms /start Vms fails because of having no connection to the > host. > Following is seen in agent logs: > 2013-12-10 20:56:46,640 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:56:46,640 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:56:51,641 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:56:51,642 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:56:56,642 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:56:56,643 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:57:01,644 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:57:01,644 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:57:06,644 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:57:06,645 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:57:11,645 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:57:11,646 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:57:16,647 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:57:16,647 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:57:21,648 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:57:21,648 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:57:26,649 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:57:26,675 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:57:31,676 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:57:31,677 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:57:36,678 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > 2013-12-10 20:57:36,678 INFO [cloud.agent.Agent] (Agent-Handler-2:null) > Cannot connect because we still have 1 commands in progress. > 2013-12-10 20:57:41,678 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost > connection to the server. Dealing with the remaining commands... > : -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (CLOUDSTACK-5135) [Automation] install_path column in snapshot_store_ref table does not have the extension of the file
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan updated CLOUDSTACK-5135: Priority: Blocker (was: Critical) > [Automation] install_path column in snapshot_store_ref table does not have > the extension of the file > > > Key: CLOUDSTACK-5135 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5135 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Snapshot >Affects Versions: 4.3.0 > Environment: All 3 hypervisors >Reporter: Gaurav Aradhye >Assignee: Harikrishna Patnala >Priority: Blocker > Labels: automation > Fix For: 4.3.0 > > > login to mysql > fire command select * from snapshot_store_ref where store_role='Image' > Check the install_path column. > This does not have the extension for the file but if you check the same > snapshot on the nfs server, the same file will have the extension based on > from which hypervisor the snapshot is created. > This mismatch creates trouble while checking if the snapshot exists on the > nfs by mounting the nfs using the path obtained from the database. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-5135) [Automation] install_path column in snapshot_store_ref table does not have the extension of the file
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846769#comment-13846769 ] Rayees Namathponnan commented on CLOUDSTACK-5135: - This BVT blocker. marking blocker > [Automation] install_path column in snapshot_store_ref table does not have > the extension of the file > > > Key: CLOUDSTACK-5135 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5135 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Snapshot >Affects Versions: 4.3.0 > Environment: All 3 hypervisors >Reporter: Gaurav Aradhye >Assignee: Harikrishna Patnala >Priority: Blocker > Labels: automation > Fix For: 4.3.0 > > > login to mysql > fire command select * from snapshot_store_ref where store_role='Image' > Check the install_path column. > This does not have the extension for the file but if you check the same > snapshot on the nfs server, the same file will have the extension based on > from which hypervisor the snapshot is created. > This mismatch creates trouble while checking if the snapshot exists on the > nfs by mounting the nfs using the path obtained from the database. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Resolved] (CLOUDSTACK-5283) Not able to list snapshots when few snapshots are in "CreatedOnPrimary" state.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-5283. - Resolution: Fixed > Not able to list snapshots when few snapshots are in "CreatedOnPrimary" state. > -- > > Key: CLOUDSTACK-5283 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5283 > 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: Build frpm 4.3.0 >Reporter: Sangeetha Hariharan >Assignee: Nitin Mehta >Priority: Critical > Fix For: 4.3.0 > > Attachments: cloud.sql, management-server.log > > > Not able to list snapshots when few snapshots are in "CreatedOnPrimary" state. > Deploy 10 Vms in each of the hosts , so we start with 20 Vms. > We will be constantly writing to the ROOT volume ( print timestamp every 1 > minute). > Start concurrent snapshots for ROOT volumes for all the Vms by creating > "Hourly" snapshot policy at the same time. > Some of the snapshot creation fails , leaving behind Vms in > "CreatedOnPrimary" state. > When listing snapshot , we see the following error message: > http://10.223.49.6:8080/client/api?command=listSnapshots&response=json&sessionkey=elVWw%2Bt7r%2BIn8qoB0bx2S5G43gE%3D&listAll=true&page=1&pagesize=20&_=1385520897726 > Response: > "Unable to find info for image store snapshot with uuid > '3e1d21b4-35bc-4e8b-91d2-8321b19d7bcf'" > mysql> select * from snapshots where > uuid="3e1d21b4-35bc-4e8b-91d2-8321b19d7bcf"; > ++++---+---+--+--+--+-+--+---+--+-+-+-++--++--+-+-+---+ > | id | data_center_id | account_id | domain_id | volume_id | disk_offering_id > | status | path | name| > uuid | snapshot_type | type_description | > size| created | removed | backup_snap_id | swift_id | > sechost_id | prev_snap_id | hypervisor_type | version | s3_id | > ++++---+---+--+--+--+-+--+---+--+-+-+-++--++--+-+-+---+ > | 26 | 1 | 3 | 1 |26 | 14 > | CreatedOnPrimary | NULL | TestVM-tiny-host-1ps-0-5_ROOT-26_20131127004142 | > 3e1d21b4-35bc-4e8b-91d2-8321b19d7bcf | 3 | HOURLY | > 21474836480 | 2013-11-27 00:41:42 | NULL| NULL | NULL | > NULL | NULL | KVM | 2.2 | NULL | > ++++---+---+--+--+--+-+--+---+--+-+-+-++--++--+-+-+---+ > 1 row in set (0.00 sec) > mysql> select * from snapshot_store_ref where > snapshot_id="3e1d21b4-35bc-4e8b-91d2-8321b19d7bcf"; > Empty set, 1 warning (0.00 sec) -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-5283) Not able to list snapshots when few snapshots are in "CreatedOnPrimary" state.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846749#comment-13846749 ] ASF subversion and git services commented on CLOUDSTACK-5283: - Commit b084cc469a0b394178c33a8b1621a97879cc9f53 in branch refs/heads/master from [~nitinme] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b084cc4 ] CLOUDSTACK-5283: Not able to list snapshots when few snapshots are in "CreatedOnPrimary" state. Dont throw an exception when snapshot doesnt have an entry in the snapshot store ref for the snapshot in Image store because that fails to list all snapshots and also it can a perfect use case when the backup flag is not turned on. > Not able to list snapshots when few snapshots are in "CreatedOnPrimary" state. > -- > > Key: CLOUDSTACK-5283 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5283 > 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: Build frpm 4.3.0 >Reporter: Sangeetha Hariharan >Assignee: Nitin Mehta >Priority: Critical > Fix For: 4.3.0 > > Attachments: cloud.sql, management-server.log > > > Not able to list snapshots when few snapshots are in "CreatedOnPrimary" state. > Deploy 10 Vms in each of the hosts , so we start with 20 Vms. > We will be constantly writing to the ROOT volume ( print timestamp every 1 > minute). > Start concurrent snapshots for ROOT volumes for all the Vms by creating > "Hourly" snapshot policy at the same time. > Some of the snapshot creation fails , leaving behind Vms in > "CreatedOnPrimary" state. > When listing snapshot , we see the following error message: > http://10.223.49.6:8080/client/api?command=listSnapshots&response=json&sessionkey=elVWw%2Bt7r%2BIn8qoB0bx2S5G43gE%3D&listAll=true&page=1&pagesize=20&_=1385520897726 > Response: > "Unable to find info for image store snapshot with uuid > '3e1d21b4-35bc-4e8b-91d2-8321b19d7bcf'" > mysql> select * from snapshots where > uuid="3e1d21b4-35bc-4e8b-91d2-8321b19d7bcf"; > ++++---+---+--+--+--+-+--+---+--+-+-+-++--++--+-+-+---+ > | id | data_center_id | account_id | domain_id | volume_id | disk_offering_id > | status | path | name| > uuid | snapshot_type | type_description | > size| created | removed | backup_snap_id | swift_id | > sechost_id | prev_snap_id | hypervisor_type | version | s3_id | > ++++---+---+--+--+--+-+--+---+--+-+-+-++--++--+-+-+---+ > | 26 | 1 | 3 | 1 |26 | 14 > | CreatedOnPrimary | NULL | TestVM-tiny-host-1ps-0-5_ROOT-26_20131127004142 | > 3e1d21b4-35bc-4e8b-91d2-8321b19d7bcf | 3 | HOURLY | > 21474836480 | 2013-11-27 00:41:42 | NULL| NULL | NULL | > NULL | NULL | KVM | 2.2 | NULL | > ++++---+---+--+--+--+-+--+---+--+-+-+-++--++--+-+-+---+ > 1 row in set (0.00 sec) > mysql> select * from snapshot_store_ref where > snapshot_id="3e1d21b4-35bc-4e8b-91d2-8321b19d7bcf"; > Empty set, 1 warning (0.00 sec) -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-5283) Not able to list snapshots when few snapshots are in "CreatedOnPrimary" state.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846746#comment-13846746 ] ASF subversion and git services commented on CLOUDSTACK-5283: - Commit 67785c2ad683342ebe0622db955db505b499a6c7 in branch refs/heads/4.3 from [~nitinme] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=67785c2 ] CLOUDSTACK-5283: Not able to list snapshots when few snapshots are in "CreatedOnPrimary" state. Dont throw an exception when snapshot doesnt have an entry in the snapshot store ref for the snapshot in Image store because that fails to list all snapshots and also it can a perfect use case when the backup flag is not turned on. > Not able to list snapshots when few snapshots are in "CreatedOnPrimary" state. > -- > > Key: CLOUDSTACK-5283 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5283 > 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: Build frpm 4.3.0 >Reporter: Sangeetha Hariharan >Assignee: Nitin Mehta >Priority: Critical > Fix For: 4.3.0 > > Attachments: cloud.sql, management-server.log > > > Not able to list snapshots when few snapshots are in "CreatedOnPrimary" state. > Deploy 10 Vms in each of the hosts , so we start with 20 Vms. > We will be constantly writing to the ROOT volume ( print timestamp every 1 > minute). > Start concurrent snapshots for ROOT volumes for all the Vms by creating > "Hourly" snapshot policy at the same time. > Some of the snapshot creation fails , leaving behind Vms in > "CreatedOnPrimary" state. > When listing snapshot , we see the following error message: > http://10.223.49.6:8080/client/api?command=listSnapshots&response=json&sessionkey=elVWw%2Bt7r%2BIn8qoB0bx2S5G43gE%3D&listAll=true&page=1&pagesize=20&_=1385520897726 > Response: > "Unable to find info for image store snapshot with uuid > '3e1d21b4-35bc-4e8b-91d2-8321b19d7bcf'" > mysql> select * from snapshots where > uuid="3e1d21b4-35bc-4e8b-91d2-8321b19d7bcf"; > ++++---+---+--+--+--+-+--+---+--+-+-+-++--++--+-+-+---+ > | id | data_center_id | account_id | domain_id | volume_id | disk_offering_id > | status | path | name| > uuid | snapshot_type | type_description | > size| created | removed | backup_snap_id | swift_id | > sechost_id | prev_snap_id | hypervisor_type | version | s3_id | > ++++---+---+--+--+--+-+--+---+--+-+-+-++--++--+-+-+---+ > | 26 | 1 | 3 | 1 |26 | 14 > | CreatedOnPrimary | NULL | TestVM-tiny-host-1ps-0-5_ROOT-26_20131127004142 | > 3e1d21b4-35bc-4e8b-91d2-8321b19d7bcf | 3 | HOURLY | > 21474836480 | 2013-11-27 00:41:42 | NULL| NULL | NULL | > NULL | NULL | KVM | 2.2 | NULL | > ++++---+---+--+--+--+-+--+---+--+-+-+-++--++--+-+-+---+ > 1 row in set (0.00 sec) > mysql> select * from snapshot_store_ref where > snapshot_id="3e1d21b4-35bc-4e8b-91d2-8321b19d7bcf"; > Empty set, 1 warning (0.00 sec) -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Resolved] (CLOUDSTACK-5361) Require UI changes,currently UI is not supporting custom system service offerings
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang resolved CLOUDSTACK-5361. -- Resolution: Not A Problem prashant, > AS we have custom check box for compute offering , we should have same for > system SO Feature "Dynamic Compute Offering" is for UserVM only (NOT for SystemVM). (I just confirmed with PM Manan) Therefore, Add System Service Offering dialog doesn't have custom checkbox like Add Compute Offering Dialog. Jessica > Require UI changes,currently UI is not supporting custom system service > offerings > -- > > Key: CLOUDSTACK-5361 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5361 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 >Reporter: prashant kumar mishra >Assignee: Jessica Wang > Attachments: screenshot-1.jpg > > > Steps to reproduce > > 1-try to create a custom system service offering > Expected > > AS we have custom check box for compute offering , we should have same for > system SO > Actual > - > There are no custom check box -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (CLOUDSTACK-5407) site-to-site VPN VR-to-VR After VPN connection successfully established , site with passive mode remains in "Disconnected" state
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angeline shen updated CLOUDSTACK-5407:
--
Priority: Critical (was: Major)
> site-to-site VPN VR-to-VR After VPN connection successfully established ,
> site with passive mode remains in "Disconnected" state
>
>
> Key: CLOUDSTACK-5407
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5407
> 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: MSrhel 6.4 12/5/13 latest build 97
> host XS 6.2
>Reporter: angeline shen
>Priority: Critical
> Fix For: 4.3.0
>
> Attachments: v16.htm
>
>
> 1. admin creates vpc1, VPN customer gateway tovpc2
>d1user creates vpc2, VPN customer gateway toadmin
> 2. admincreates VPN connection to 'tovpc2'passive mode
> d1user creatses VPN connection to 'toadmin'
> 3. After VPN connection successful, d1user VPN connection shows "connected",
> but admin shows "Disconnected"
> http://10.223.130.107:8080/client/api?command=listVpnConnections&listAll=true&page=1&pagesize=20&response=json&sessionkey=b3xkTyC7CxDFKBCNY%2ByGqaoK4rk%3D&vpcid=b4bd8438-b17a-4bb3-9ff8-6b980e148cd8&_=1386373747078
> { "listvpnconnectionsresponse" : { "count":1 ,"vpnconnection" : [
> {"id":"6a56648a-78b3-4ab7-a709-42d1e291ef23","s2svpngatewayid":"95790330-3201-4f3f-b824-ab3efbef","publicip":"10.223.123.17","s2scustomergatewayid":"af688052-a2fd-44b2-8c07-cb6c938e5483","gateway":"10.223.123.53","cidrlist":"10.2.1.1/16","ipsecpsk":"123123","ikepolicy":"3des-md5","esppolicy":"3des-md5","ikelifetime":86400,"esplifetime":3600,"dpd":false,"state":"Disconnected","passive":true,"account":"admin","domainid":"31a9bc00-5de9-11e3-a6e9-06c6ac000773","domain":"ROOT","created":"2013-12-06T14:31:10-0800"}
> ] } }
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Updated] (CLOUDSTACK-5424) site-to-site VPN VR-to-VR shows 0 for user's network-VPC site-to-site VPN pane even when user has existent site-to-stie VPN
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angeline shen updated CLOUDSTACK-5424: -- Priority: Critical (was: Major) > site-to-site VPN VR-to-VRshows 0 for user's network-VPC site-to-site VPN > pane even when user has existent site-to-stie VPN > --- > > Key: CLOUDSTACK-5424 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5424 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Environment: MS rhel 6.4 12/5/13 latest build 97 > host XS 6.2 >Reporter: angeline shen >Priority: Critical > Attachments: v3.png, v4.png, v5.png, v6.png > > > 1. admin login, creates vpc1, Router site-to-site VPNS, create VPN customer > gateway >d1user login, creates vpc2, Router site-to-site VPNS, create VPN customer > gateway > 2. admin login, admin's vpc, networkRouter site-to-site VPNS pane shows '1' > for admin's existent site-to-site VPNS > admin login, d1user's vpc, networkRouter site-to-site VPNS pane shows '0' > for d1user's existent site-to-site VPNS -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Closed] (CLOUDSTACK-5448) site-to-site VPN VR-to-VR [KVM] Fail to establish VPN connections between two VPCs
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angeline shen closed CLOUDSTACK-5448.
-
> site-to-site VPN VR-to-VR [KVM] Fail to establish VPN connections between
> two VPCs
> ---
>
> Key: CLOUDSTACK-5448
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5448
> 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: MS10.223.130.59
> CloudPlatform-4.3-900-rhel6.3.tar.gz
> host KVM 10.223.51.3 10.223.51.4
>Reporter: angeline shen
>Assignee: Sheng Yang
>Priority: Critical
> Fix For: 4.3.0
>
>
> 1. admin login, creates vpc1 and vpc2, Router site-to-site VPNS, create VPN
> customer gateway
> 2. attempt to establish VPN connections between 2 VPCs failed with Null
> pointer exception:
> 2013-12-10 11:16:35,808 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-15:ctx-dc293bdb ctx-3213721c) ===END=== 10.215.3.21 -- GET
> command=createVpnConnection&response=json&sessionkey=M2eYCkq%2FsdqEc3dp3uvp7ke8jHg%3D&s2svpngatewayid=8bb2ebf0-11de-4fb3-bd86-438f7b6d4a87&s2scustomergatewayid=086f3de9-5f8c-4bcb-9c7a-0f097acea8f4&passive=true&_=1386703355792
> 2013-12-10 11:16:35,811 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Job-Executor-65:ctx-93679f8e) Add job-69 into job monitoring
> 2013-12-10 11:16:35,811 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-65:ctx-93679f8e) Executing AsyncJobVO {id:69, userId: 2,
> accountId: 2, instanceType: None, instanceId: 4, cmd:
> org.apache.cloudstack.api.command.user.vpn.CreateVpnConnectionCmd, cmdInfo:
> {"id":"4","response":"json","sessionkey":"M2eYCkq/sdqEc3dp3uvp7ke8jHg\u003d","s2scustomergatewayid":"086f3de9-5f8c-4bcb-9c7a-0f097acea8f4","cmdEventType":"VPN.S2S.CONNECTION.CREATE","ctxUserId":"2","s2svpngatewayid":"8bb2ebf0-11de-4fb3-bd86-438f7b6d4a87","passive":"true","httpmethod":"GET","_":"1386703355792","ctxAccountId":"2","ctxStartEventId":"253"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 7692017993539, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2013-12-10 11:16:35,863 DEBUG [c.c.a.t.Request] (Job-Executor-65:ctx-93679f8e
> ctx-3213721c) Seq 1-1648170383: Sending { Cmd , MgmtId: 7692017993539, via:
> 1(Rack2Host18.lab.vmops.com), Ver: v1, Flags: 100101,
> [{"com.cloud.agent.api.routing.Site2SiteVpnCfgCommand":{"create":true,"localPublicIp":"10.223.123.7","localGuestCidr":"10.1.1.1/16","localPublicGateway":"10.223.123.1","peerGatewayIp":"10.233.123.36","peerGuestCidrList":"10.3.1.1/16","ipsecPsk":"1237","ikePolicy":"3des-md5","espPolicy":"3des-md5","ikeLifetime":86400,"espLifetime":3600,"dpd":false,"passive":true,"accessDetails":{"zone.network.type":"Advanced","router.ip":"169.254.0.169","router.name":"r-3-VM"},"wait":0}}]
> }
> 2013-12-10 11:16:36,276 DEBUG [c.c.a.t.Request] (AgentManager-Handler-2:null)
> Seq 1-1648170383: Processing: { Ans: , MgmtId: 7692017993539, via: 1, Ver:
> v1, Flags: 100, [{"com.cloud.agent.api.Answer":{"result":true,"wait":0}}] }
> 2013-12-10 11:16:36,277 DEBUG [c.c.a.m.AgentAttache]
> (AgentManager-Handler-2:null) Seq 1-1648170383: No more commands found
> 2013-12-10 11:16:36,277 DEBUG [c.c.a.t.Request] (Job-Executor-65:ctx-93679f8e
> ctx-3213721c) Seq 1-1648170383: Received: { Ans: , MgmtId: 7692017993539,
> via: 1, Ver: v1, Flags: 100, { Answer } }
> 2013-12-10 11:16:36,295 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-65:ctx-93679f8e ctx-3213721c) Complete async job-69, jobStatus:
> SUCCEEDED, resultCode: 0, result:
> org.apache.cloudstack.api.response.Site2SiteVpnConnectionResponse/vpnconnection/{"id":"813b96bd-4fd4-4861-852d-9c93eb5d3076","s2svpngatewayid":"8bb2ebf0-11de-4fb3-bd86-438f7b6d4a87","publicip":"10.223.123.7","s2scustomergatewayid":"086f3de9-5f8c-4bcb-9c7a-0f097acea8f4","gateway":"10.233.123.36","cidrlist":"10.3.1.1/16","ipsecpsk":"1237","ikepolicy":"3des-md5","esppolicy":"3des-md5","ikelifetime":86400,"esplifetime":3600,"dpd":false,"state":"Disconnected","passive":true,"account":"admin","domainid":"500616b0-6124-11e3-8adc-06fef743","domain":"ROOT","created":"2013-12-10T11:16:35-0800"}
> 2013-12-10 11:16:36,304 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-65:ctx-93679f8e) Done executing
> org.apache.cloudstack.api.command.user.vpn.CreateVpnConnectionCmd for job-69
> 2013-12-10 11:16:36,309 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Job-Executor-65:ctx-93679f8e) Remove job-69 from job monitoring
> 2013-12-10 11:16:37,614 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-12:ctx-3db6f358) ===START=== 10.215.3.21 -- GET
> command
[jira] [Commented] (CLOUDSTACK-5448) site-to-site VPN VR-to-VR [KVM] Fail to establish VPN connections between two VPCs
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846678#comment-13846678
]
angeline shen commented on CLOUDSTACK-5448:
---
Verified CloudPlatform-4.3-914-rhel6.3.tar.gz
code fix to generate status dialog for invalid parameter specified in
createVPNconnection
> site-to-site VPN VR-to-VR [KVM] Fail to establish VPN connections between
> two VPCs
> ---
>
> Key: CLOUDSTACK-5448
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5448
> 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: MS10.223.130.59
> CloudPlatform-4.3-900-rhel6.3.tar.gz
> host KVM 10.223.51.3 10.223.51.4
>Reporter: angeline shen
>Assignee: Sheng Yang
>Priority: Critical
> Fix For: 4.3.0
>
>
> 1. admin login, creates vpc1 and vpc2, Router site-to-site VPNS, create VPN
> customer gateway
> 2. attempt to establish VPN connections between 2 VPCs failed with Null
> pointer exception:
> 2013-12-10 11:16:35,808 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-15:ctx-dc293bdb ctx-3213721c) ===END=== 10.215.3.21 -- GET
> command=createVpnConnection&response=json&sessionkey=M2eYCkq%2FsdqEc3dp3uvp7ke8jHg%3D&s2svpngatewayid=8bb2ebf0-11de-4fb3-bd86-438f7b6d4a87&s2scustomergatewayid=086f3de9-5f8c-4bcb-9c7a-0f097acea8f4&passive=true&_=1386703355792
> 2013-12-10 11:16:35,811 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Job-Executor-65:ctx-93679f8e) Add job-69 into job monitoring
> 2013-12-10 11:16:35,811 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-65:ctx-93679f8e) Executing AsyncJobVO {id:69, userId: 2,
> accountId: 2, instanceType: None, instanceId: 4, cmd:
> org.apache.cloudstack.api.command.user.vpn.CreateVpnConnectionCmd, cmdInfo:
> {"id":"4","response":"json","sessionkey":"M2eYCkq/sdqEc3dp3uvp7ke8jHg\u003d","s2scustomergatewayid":"086f3de9-5f8c-4bcb-9c7a-0f097acea8f4","cmdEventType":"VPN.S2S.CONNECTION.CREATE","ctxUserId":"2","s2svpngatewayid":"8bb2ebf0-11de-4fb3-bd86-438f7b6d4a87","passive":"true","httpmethod":"GET","_":"1386703355792","ctxAccountId":"2","ctxStartEventId":"253"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 7692017993539, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2013-12-10 11:16:35,863 DEBUG [c.c.a.t.Request] (Job-Executor-65:ctx-93679f8e
> ctx-3213721c) Seq 1-1648170383: Sending { Cmd , MgmtId: 7692017993539, via:
> 1(Rack2Host18.lab.vmops.com), Ver: v1, Flags: 100101,
> [{"com.cloud.agent.api.routing.Site2SiteVpnCfgCommand":{"create":true,"localPublicIp":"10.223.123.7","localGuestCidr":"10.1.1.1/16","localPublicGateway":"10.223.123.1","peerGatewayIp":"10.233.123.36","peerGuestCidrList":"10.3.1.1/16","ipsecPsk":"1237","ikePolicy":"3des-md5","espPolicy":"3des-md5","ikeLifetime":86400,"espLifetime":3600,"dpd":false,"passive":true,"accessDetails":{"zone.network.type":"Advanced","router.ip":"169.254.0.169","router.name":"r-3-VM"},"wait":0}}]
> }
> 2013-12-10 11:16:36,276 DEBUG [c.c.a.t.Request] (AgentManager-Handler-2:null)
> Seq 1-1648170383: Processing: { Ans: , MgmtId: 7692017993539, via: 1, Ver:
> v1, Flags: 100, [{"com.cloud.agent.api.Answer":{"result":true,"wait":0}}] }
> 2013-12-10 11:16:36,277 DEBUG [c.c.a.m.AgentAttache]
> (AgentManager-Handler-2:null) Seq 1-1648170383: No more commands found
> 2013-12-10 11:16:36,277 DEBUG [c.c.a.t.Request] (Job-Executor-65:ctx-93679f8e
> ctx-3213721c) Seq 1-1648170383: Received: { Ans: , MgmtId: 7692017993539,
> via: 1, Ver: v1, Flags: 100, { Answer } }
> 2013-12-10 11:16:36,295 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-65:ctx-93679f8e ctx-3213721c) Complete async job-69, jobStatus:
> SUCCEEDED, resultCode: 0, result:
> org.apache.cloudstack.api.response.Site2SiteVpnConnectionResponse/vpnconnection/{"id":"813b96bd-4fd4-4861-852d-9c93eb5d3076","s2svpngatewayid":"8bb2ebf0-11de-4fb3-bd86-438f7b6d4a87","publicip":"10.223.123.7","s2scustomergatewayid":"086f3de9-5f8c-4bcb-9c7a-0f097acea8f4","gateway":"10.233.123.36","cidrlist":"10.3.1.1/16","ipsecpsk":"1237","ikepolicy":"3des-md5","esppolicy":"3des-md5","ikelifetime":86400,"esplifetime":3600,"dpd":false,"state":"Disconnected","passive":true,"account":"admin","domainid":"500616b0-6124-11e3-8adc-06fef743","domain":"ROOT","created":"2013-12-10T11:16:35-0800"}
> 2013-12-10 11:16:36,304 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-65:ctx-93679f8e) Done executing
> org.apache.cloudstack.api.command.user.vpn.CreateVpnConnectionCmd for job-69
> 2013-12-10 11:16:36,309 INFO [o.a.c.f.j.i.AsyncJobMonito
[jira] [Assigned] (CLOUDSTACK-4852) Since upgrade to 4.2 only users at the zone-attached domain level can manipulate VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Damle reassigned CLOUDSTACK-4852: Assignee: Prachi Damle > Since upgrade to 4.2 only users at the zone-attached domain level can > manipulate VMs > > > Key: CLOUDSTACK-4852 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4852 > 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: ACS 4.2 > KVM > CentOS 6.4 >Reporter: kelcey damage >Assignee: Prachi Damle >Priority: Critical > Fix For: 4.3.0 > > > Since upgrade to 4.2 only users at the zone-attached domain level can > manipulate VMs in the zone. > Root-admin can no longer modify or provision VMs. Any VMs created by root > that are using the sub-domain zone are no longer operable as they do not > appear in the sub-domains login and root cannot operate on them. > Tree structure is: > ROOT > |_ Backbone Technology > |_ Development2013-10-10 15:54:45,584 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-7:job-554 = [ 6a86d3fc-ab02-4667-ae86-826b6e7003e9 ]) > Unexpected exception while executing > org.apache.cloudstack.api.command.user.vm.DeployVMCmd > com.cloud.utils.exception.CloudRuntimeException: Failed to deploy VM, Zone > Backbone Technology not available for the user domain > Acct[29b09a25-555a-4917-8cac-53fdf7f40589-kdamage] at > com.cloud.deploy.DeploymentPlanningManagerImpl.checkForNonDedicatedResources(DeploymentPlanningManagerImpl.java:479) > at > com.cloud.deploy.DeploymentPlanningManagerImpl.planDeployment(DeploymentPlanningManagerImpl.java:223) > at > org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:187) > at > org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3405) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor > .java:125) > at > org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:679) > 2013-10-10 15:51:43,566 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-5:job-552 = [ 2eeb7054-7b48-4b7c-8e8b-7f6d5eebf35c ]) > Unexpected exception while executing > org.apache.cloudstack.api.command.user.vm.DeployVMCmd > com.cloud.utils.exception.CloudRuntimeException: Failed to deploy VM, Zone > Backbone Technology not available for the user domain > Acct[f6dd36ea-e802-4f25-a848-b63f8556b057-admin] > at > com.cloud.deploy.DeploymentPlanningManagerImpl.checkForNonDedicatedResources(DeploymentPlanningManagerImpl.java:479) > at > com.cloud.deploy.DeploymentPlanningManagerImpl.planDeployment(DeploymentPlanningManagerImpl.java:223) > at > org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:187) > at > org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3405) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor > .java:125) > at > org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) > at com.clo
[jira] [Updated] (CLOUDSTACK-5361) Require UI changes,currently UI is not supporting custom system service offerings
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-5361: --- Assignee: Jessica Wang > Require UI changes,currently UI is not supporting custom system service > offerings > -- > > Key: CLOUDSTACK-5361 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5361 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 >Reporter: prashant kumar mishra >Assignee: Jessica Wang > Attachments: screenshot-1.jpg > > > Steps to reproduce > > 1-try to create a custom system service offering > Expected > > AS we have custom check box for compute offering , we should have same for > system SO > Actual > - > There are no custom check box -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-5433) Deleting Shared Network fails, throws NPE
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846611#comment-13846611 ] Alena Prokharchyk commented on CLOUDSTACK-5433: --- Sowmya, I can’t reproduce the bug with the db dump given. Also I can’t reproduce it in my environment. As its a really critical bug, I would need more help from you. I want you to test it on the latest build, and: take cloud db dump before the failure happened Take cloud db dump after the failure Mention network id that failed to remove Attach management server log file to the bug with the recent failure. Thank you in advance, -Alena. > Deleting Shared Network fails, throws NPE > - > > Key: CLOUDSTACK-5433 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5433 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.3.0 > Environment: Advanced zone, Shared N/w, Single zone >Reporter: Sowmya Krishnan >Assignee: Alena Prokharchyk >Priority: Critical > Fix For: 4.3.0 > > Attachments: cloud.dmp, sharednwerror.log.gz > > > Deleting a shared network with or without VR running fails and throws NPE. > Steps: > Create a shared network in Advanced zone > Deploy VMs > Destroy all VMs > Destroy the router (optional - issue exists even if this step isn't performed) > Delete network > Result: > Delete fails and raises the following exception: > 2013-12-10 13:37:07,088 DEBUG [c.c.u.d.T.Transaction] > (Job-Executor-13:ctx-41a21ece ctx-c209ccf2) Rolling back the transaction: > Time = 3 Name = Job-Executor-13; called by -TransactionLegac > y.rollback:896-TransactionLegacy.removeUpTo:839-TransactionLegacy.close:663-Transaction.execute:41-Transaction.execute:46-DirectNetworkGuru.trash:322-NetworkOrchestrator$10.doInTransactionW > ithoutResult:2161-TransactionCallbackNoReturn.doInTransaction:25-Transaction$2.doInTransaction:49-Transaction.execute:37-Transaction.execute:46-NetworkOrchestrator.destroyNetwork:2156 > 2013-12-10 13:37:07,097 ERROR [c.c.a.ApiAsyncJobDispatcher] > (Job-Executor-13:ctx-41a21ece) Unexpected exception while executing > org.apache.cloudstack.api.command.user.network.DeleteNetworkC > md > java.lang.NullPointerException > at > com.cloud.network.guru.DirectNetworkGuru$3.doInTransactionWithoutResult(DirectNetworkGuru.java:329) > at > com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java:25) > at > com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49) > at com.cloud.utils.db.Transaction.execute(Transaction.java:37) > at com.cloud.utils.db.Transaction.execute(Transaction.java:46) > at > com.cloud.network.guru.DirectNetworkGuru.trash(DirectNetworkGuru.java:322) > at > org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$10.doInTransactionWithoutResult(NetworkOrchestrator.java:2161) > at > com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java:25) > at > com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49) > at com.cloud.utils.db.Transaction.execute(Transaction.java:37) > at com.cloud.utils.db.Transaction.execute(Transaction.java:46) > at > org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.destroyNetwork(NetworkOrchestrator.java:2156) > at > com.cloud.network.NetworkServiceImpl.deleteNetwork(NetworkServiceImpl.java:1806) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) > at > com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) > at > org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) > at > org.springframework.aop
[jira] [Created] (CLOUDSTACK-5479) Upgrading service offering of stopped vm should release the reserved capacity of the vm
Nitin Mehta created CLOUDSTACK-5479: --- Summary: Upgrading service offering of stopped vm should release the reserved capacity of the vm Key: CLOUDSTACK-5479 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5479 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Nitin Mehta Upgrade a service offering of stopped vm should release the reserved capacity of the vm -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (CLOUDSTACK-5433) Deleting Shared Network fails, throws NPE
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sowmya Krishnan updated CLOUDSTACK-5433: Attachment: cloud.dmp Attached cloud DB dump with Hyper-V set up as requested > Deleting Shared Network fails, throws NPE > - > > Key: CLOUDSTACK-5433 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5433 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.3.0 > Environment: Advanced zone, Shared N/w, Single zone >Reporter: Sowmya Krishnan >Assignee: Alena Prokharchyk >Priority: Critical > Fix For: 4.3.0 > > Attachments: cloud.dmp, sharednwerror.log.gz > > > Deleting a shared network with or without VR running fails and throws NPE. > Steps: > Create a shared network in Advanced zone > Deploy VMs > Destroy all VMs > Destroy the router (optional - issue exists even if this step isn't performed) > Delete network > Result: > Delete fails and raises the following exception: > 2013-12-10 13:37:07,088 DEBUG [c.c.u.d.T.Transaction] > (Job-Executor-13:ctx-41a21ece ctx-c209ccf2) Rolling back the transaction: > Time = 3 Name = Job-Executor-13; called by -TransactionLegac > y.rollback:896-TransactionLegacy.removeUpTo:839-TransactionLegacy.close:663-Transaction.execute:41-Transaction.execute:46-DirectNetworkGuru.trash:322-NetworkOrchestrator$10.doInTransactionW > ithoutResult:2161-TransactionCallbackNoReturn.doInTransaction:25-Transaction$2.doInTransaction:49-Transaction.execute:37-Transaction.execute:46-NetworkOrchestrator.destroyNetwork:2156 > 2013-12-10 13:37:07,097 ERROR [c.c.a.ApiAsyncJobDispatcher] > (Job-Executor-13:ctx-41a21ece) Unexpected exception while executing > org.apache.cloudstack.api.command.user.network.DeleteNetworkC > md > java.lang.NullPointerException > at > com.cloud.network.guru.DirectNetworkGuru$3.doInTransactionWithoutResult(DirectNetworkGuru.java:329) > at > com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java:25) > at > com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49) > at com.cloud.utils.db.Transaction.execute(Transaction.java:37) > at com.cloud.utils.db.Transaction.execute(Transaction.java:46) > at > com.cloud.network.guru.DirectNetworkGuru.trash(DirectNetworkGuru.java:322) > at > org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$10.doInTransactionWithoutResult(NetworkOrchestrator.java:2161) > at > com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java:25) > at > com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49) > at com.cloud.utils.db.Transaction.execute(Transaction.java:37) > at com.cloud.utils.db.Transaction.execute(Transaction.java:46) > at > org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.destroyNetwork(NetworkOrchestrator.java:2156) > at > com.cloud.network.NetworkServiceImpl.deleteNetwork(NetworkServiceImpl.java:1806) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) > at > com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) > at > org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) > at > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) > at $Proxy193.deleteNetwork(Unknown Source) > at > org.apache.cloudstack.api.command.user.network.DeleteNetworkCmd.execute(DeleteNetworkCmd.java:71) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161) > at > com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109) > at >
[jira] [Commented] (CLOUDSTACK-5047) [Automation] KVM - Failed to add ACLlist to vpc network, observed NPE in agent
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846382#comment-13846382
]
Rayees Namathponnan commented on CLOUDSTACK-5047:
-
Is it fixed in master ?
> [Automation] KVM - Failed to add ACLlist to vpc network, observed NPE in
> agent
>
>
> Key: CLOUDSTACK-5047
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5047
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM, Network Controller
>Affects Versions: 4.3.0
> Environment: KVM
> Build : 4.3.0 master
>Reporter: Rayees Namathponnan
>Assignee: Jayapal Reddy
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: CLOUDSTACK-5047.rar, libvirtd.log
>
>
> BVT test case
> integration.smoke.test_privategw_acl.TestPrivateGwACL.test_privategw_acl
> failed with master build
> observed below error in MS log, while adding ACL list
> 2013-11-05 14:50:30,265 DEBUG [c.c.v.UserVmManagerImpl]
> (AccountChecker-1:ctx-c25f1452) Firewall rules are removed successfully as a
> part of vm id=6 expunge
> 2013-11-05 14:50:30,267 DEBUG [c.c.n.r.RulesManagerImpl]
> (AccountChecker-1:ctx-c25f1452) No port forwarding rules are found for vm id=6
> 2013-11-05 14:50:30,267 DEBUG [c.c.v.UserVmManagerImpl]
> (AccountChecker-1:ctx-c25f1452) Port forwarding rules are removed
> successfully as a part of vm id=6 exp
> unge
> 2013-11-05 14:50:30,271 DEBUG [c.c.n.l.LoadBalancingRulesManagerImpl]
> (AccountChecker-1:ctx-c25f1452) Set load balancer rule for revoke: rule id
> 49, vmId 6
> 2013-11-05 14:50:30,281 DEBUG [c.c.n.l.LoadBalancingRulesManagerImpl]
> (AccountChecker-1:ctx-c25f1452) Set load balancer rule for revoke: rule id
> 49, vmId 6
> 2013-11-05 14:50:30,288 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:ctx-0e021cd8) Found 2 routers to update status.
> 2013-11-05 14:50:30,289 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:ctx-0e021cd8) Found 0 networks to update RvR status.
> 2013-11-05 14:50:30,316 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (AccountChecker-1:ctx-c25f1452) Applying ip association in network
> Ntwk[208|Guest|8]
> 2013-11-05 14:50:30,332 DEBUG [c.c.a.t.Request]
> (AccountChecker-1:ctx-c25f1452) Seq 1-193922916: Sending { Cmd , MgmtId:
> 29066118877352, via: 1(Rack2Host11.la
> b.vmops.com), Ver: v1, Flags: 11,
> [{"com.cloud.agent.api.routing.IpAssocCommand":{"ipAddresses":[{"accountId":6,"publicIp":"10.223.122.68","sourceNat":true
> ,"add":true,"oneToOneNat":false,"firstIP":true,"broadcastUri":"vlan://1221","vlanGateway":"10.223.122.65","vlanNetmask":"255.255.255.192","vifMacAddress":"06:9
> 6:6a:00:00:3d","networkRate":200,"trafficType":"Public"},{"accountId":6,"publicIp":"10.223.122.76","sourceNat":false,"add":true,"oneToOneNat":false,"firstIP":f
> alse,"broadcastUri":"vlan://1221","vlanGateway":"10.223.122.65","vlanNetmask":"255.255.255.192","vifMacAddress":"06:c2:af:00:00:3d","networkRate":200,"trafficT
> ype":"Public"}],"accessDetails":{"router.guest.ip":"10.1.1.1","zone.network.type":"Advanced","router.ip":"169.254.3.181","router.name":"r-8-QA"},"wait":0}}]
> }
> 2013-11-05 14:50:30,627 DEBUG [c.c.a.t.Request]
> (AgentManager-Handler-11:null) Seq 1-193922916: Processing: { Ans: , MgmtId:
> 29066118877352, via: 1, Ver: v1,
> Flags: 0,
> [{"com.cloud.agent.api.Answer":{"result":false,"details":"java.lang.NullPointerException\n\tat
> com.cloud.agent.api.routing.IpAssocAnswer.(IpAss
> ocAnswer.java:34)\n\tat
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2062)\n\tat
> com.cloud.hypervisor.kvm.r
> esource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1278)\n\tat
> com.cloud.agent.Agent.processRequest(Agent.java:498)\n\tat com.cloud.
> agent.Agent$AgentRequestHandler.doTask(Agent.java:806)\n\tat
> com.cloud.utils.nio.Task.run(Task.java:83)\n\tat
> java.util.concurrent.ThreadPoolExecutor.runWorker
> (ThreadPoolExecutor.java:1110)\n\tat
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)\n\tat
> java.lang.Thread.run(Thread.java:679
> )\n","wait":0}}] }
> 2013-11-05 14:50:30,627 DEBUG [c.c.a.t.Request]
> (AccountChecker-1:ctx-c25f1452) Seq 1-193922916: Received: { Ans: , MgmtId:
> 29066118877352, via: 1, Ver: v1, F
> lags: 0, { Answer } }
> 2013-11-05 14:50:30,627 WARN [c.c.n.l.LoadBalancingRulesManagerImpl]
> (AccountChecker-1:ctx-c25f1452) Unable to apply the load balancer config
> because resource
> is unavaliable.
> com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is
> unrea
[jira] [Created] (CLOUDSTACK-5478) ActionEvents published on event bus should have Entity UUID and Type for all resources
David Grizzanti created CLOUDSTACK-5478: --- Summary: ActionEvents published on event bus should have Entity UUID and Type for all resources Key: CLOUDSTACK-5478 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5478 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: David Grizzanti This issue was originally reported/described in CLOUDSTACK-3190. However, that bug went in a different direction and was closed. Opening this bug to track the actual fix for supplying the UUID and type in all ActionEvents messages published to the event bus. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-5342) Add NIC to virtual machine fails in KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846355#comment-13846355
]
Rayees Namathponnan commented on CLOUDSTACK-5342:
-
Looks like in test case we are adding same network twice without adding
previous one, please see the code
389 # Adding network to vm for the first time
390 self.addNetworkToVm(network, self.virtual_machine)
391
392 # Trying to add same network to vm for the second time
393 with self.assertRaises(Exception) as e:
394 self.addNetworkToVm(network, self.virtual_machine)
395
396 self.debug("Adding same network again failed with exception: %s" %
e.exception)
397
398 return
> Add NIC to virtual machine fails in KVM
> ---
>
> Key: CLOUDSTACK-5342
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5342
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
>Affects Versions: 4.3.0
> Environment: KVM advanced
>Reporter: Gaurav Aradhye
>Assignee: Marcus Sorensen
>Priority: Blocker
> Fix For: 4.3.0
>
>
> Add network to VM test cases fail in KVM with following error.
> Execute cmd: asyncquery failed, due to: {errorcode : 530, errortext :
> u'Unable to add NIC to VM[User|VM-e9350ee5-bf2e-418c-91d6-1535dcb4d488]'}
> The same test cases execute successfully on XenServer. As per the feature
> specification (see
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Add+Remove+Networks+to+VMs),
> "Add network to VM" feature should be supported on KVM too.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Created] (CLOUDSTACK-5477) TypeError: args.context.snapshots is undefined url: createURL("listSnapshots&id=" + args.context.snapshots[0].id),
rashid created CLOUDSTACK-5477:
--
Summary: TypeError: args.context.snapshots is undefined url:
createURL("listSnapshots&id=" + args.context.snapshots[0].id),
Key: CLOUDSTACK-5477
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5477
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: UI
Affects Versions: 4.3.0
Environment: Storage,Volumes,
Reporter: rashid
Fix For: 4.3.0
It's a UI bug. Through api i am getting results.
Goto INSTANCE>(VMNAME)>view volumes>
ex: Home>Instances> win2012> Volumes>ROOT-10
After this
goto Storage>VOLUMES>select any volume
ex: Home> Storage - Volumes > ROOT-10
nothing is displayed.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-5449) [Automation] Marvin tests are failing because it failed to create log directory
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846258#comment-13846258
]
ASF subversion and git services commented on CLOUDSTACK-5449:
-
Commit 8374ff591d17466887db46ac39d71b8cb364c4c6 in branch refs/heads/master
from [~srikanti]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8374ff5 ]
CLOUDSTACK-5449: fixed pep8 errors
Signed-off-by: SrikanteswaraRao Talluri
> [Automation] Marvin tests are failing because it failed to create log
> directory
> ---
>
> Key: CLOUDSTACK-5449
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5449
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation, marvin
>Affects Versions: 4.3.0
>Reporter: Srikanteswararao Talluri
>Assignee: Srikanteswararao Talluri
>Priority: Critical
> Fix For: 4.3.0
>
>
> nosetests --with-xunit --xunit-file=test_loadbalance.xml --with-marvin
> --marvin-config=/hudson/scripts/nightly_asf_master.cfg
> /root/cloudstack/test//integration/smoke/test_loadbalance.py --load -a
> tags=advanced
> Exception Occurred Under __initLogging :[Errno 17] File exists:
> '/hudson/workspace/logs13867140921'
> Traceback (most recent call last):
> File "/usr/local/bin/nosetests", line 9, in
> load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
> File "/usr/local/lib/python2.7/site-packages/nose/core.py", line 118, in
> __init__
> **extra_args)
> File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
> self.runTests()
> File "/usr/local/lib/python2.7/site-packages/nose/core.py", line 197, in
> runTests
> result = self.testRunner.run(self.test)
> File "/usr/local/lib/python2.7/site-packages/nose/core.py", line 61, in run
> test(result)
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 176, in
> __call__
> return self.run(*arg, **kw)
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 223, in
> run
> test(orig)
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 176, in
> __call__
> return self.run(*arg, **kw)
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 223, in
> run
> test(orig)
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 176, in
> __call__
> return self.run(*arg, **kw)
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 223, in
> run
> test(orig)
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 176, in
> __call__
> return self.run(*arg, **kw)
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 223, in
> run
> test(orig)
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 176, in
> __call__
> return self.run(*arg, **kw)
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 223, in
> run
> test(orig)
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 176, in
> __call__
> return self.run(*arg, **kw)
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 223, in
> run
> test(orig)
> File "/usr/local/lib/python2.7/site-packages/nose/case.py", line 45, in
> __call__
> return self.run(*arg, **kwarg)
> File "/usr/local/lib/python2.7/site-packages/nose/case.py", line 138, in run
> result.addError(self, err)
> File "/usr/local/lib/python2.7/site-packages/nose/proxy.py", line 124, in
> addError
> plugin_handled = plugins.handleError(self.test, err)
> File "/usr/local/lib/python2.7/site-packages/nose/plugins/manager.py", line
> 99, in __call__
> return self.call(*arg, **kw)
> File "/usr/local/lib/python2.7/site-packages/nose/plugins/manager.py", line
> 167, in simple
> result = meth(*arg, **kw)
> File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py", line
> 146, in handleError
> self.tcRunLogger.fatal("%s: %s: %s" %
> AttributeError: 'NoneType' object has no attribute 'fatal'
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-5449) [Automation] Marvin tests are failing because it failed to create log directory
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846257#comment-13846257
]
ASF subversion and git services commented on CLOUDSTACK-5449:
-
Commit b52a641decfbf487bdf84b6037640aa42682c55b in branch refs/heads/4.3 from
[~srikanti]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b52a641 ]
CLOUDSTACK-5449: fixed pep8 errors
Signed-off-by: SrikanteswaraRao Talluri
> [Automation] Marvin tests are failing because it failed to create log
> directory
> ---
>
> Key: CLOUDSTACK-5449
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5449
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation, marvin
>Affects Versions: 4.3.0
>Reporter: Srikanteswararao Talluri
>Assignee: Srikanteswararao Talluri
>Priority: Critical
> Fix For: 4.3.0
>
>
> nosetests --with-xunit --xunit-file=test_loadbalance.xml --with-marvin
> --marvin-config=/hudson/scripts/nightly_asf_master.cfg
> /root/cloudstack/test//integration/smoke/test_loadbalance.py --load -a
> tags=advanced
> Exception Occurred Under __initLogging :[Errno 17] File exists:
> '/hudson/workspace/logs13867140921'
> Traceback (most recent call last):
> File "/usr/local/bin/nosetests", line 9, in
> load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')()
> File "/usr/local/lib/python2.7/site-packages/nose/core.py", line 118, in
> __init__
> **extra_args)
> File "/usr/local/lib/python2.7/unittest/main.py", line 95, in __init__
> self.runTests()
> File "/usr/local/lib/python2.7/site-packages/nose/core.py", line 197, in
> runTests
> result = self.testRunner.run(self.test)
> File "/usr/local/lib/python2.7/site-packages/nose/core.py", line 61, in run
> test(result)
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 176, in
> __call__
> return self.run(*arg, **kw)
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 223, in
> run
> test(orig)
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 176, in
> __call__
> return self.run(*arg, **kw)
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 223, in
> run
> test(orig)
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 176, in
> __call__
> return self.run(*arg, **kw)
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 223, in
> run
> test(orig)
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 176, in
> __call__
> return self.run(*arg, **kw)
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 223, in
> run
> test(orig)
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 176, in
> __call__
> return self.run(*arg, **kw)
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 223, in
> run
> test(orig)
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 176, in
> __call__
> return self.run(*arg, **kw)
> File "/usr/local/lib/python2.7/site-packages/nose/suite.py", line 223, in
> run
> test(orig)
> File "/usr/local/lib/python2.7/site-packages/nose/case.py", line 45, in
> __call__
> return self.run(*arg, **kwarg)
> File "/usr/local/lib/python2.7/site-packages/nose/case.py", line 138, in run
> result.addError(self, err)
> File "/usr/local/lib/python2.7/site-packages/nose/proxy.py", line 124, in
> addError
> plugin_handled = plugins.handleError(self.test, err)
> File "/usr/local/lib/python2.7/site-packages/nose/plugins/manager.py", line
> 99, in __call__
> return self.call(*arg, **kw)
> File "/usr/local/lib/python2.7/site-packages/nose/plugins/manager.py", line
> 167, in simple
> result = meth(*arg, **kw)
> File "/usr/local/lib/python2.7/site-packages/marvin/marvinPlugin.py", line
> 146, in handleError
> self.tcRunLogger.fatal("%s: %s: %s" %
> AttributeError: 'NoneType' object has no attribute 'fatal'
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Updated] (CLOUDSTACK-5476) zone level settings are missing from UI
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-5476: -- Attachment: 4.3 screenshot.jpg > zone level settings are missing from UI > > > Key: CLOUDSTACK-5476 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5476 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.0 >Reporter: prashant kumar mishra >Priority: Critical > Attachments: 4.3 screenshot.jpg > > > steps to repro > -- > 1-prepare a cs setup > 2- goto zone > 3-there should be a setting tab > actual > - > zone level setting tab is missing ;please check scareen shot -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Created] (CLOUDSTACK-5476) zone level settings are missing from UI
prashant kumar mishra created CLOUDSTACK-5476: - Summary: zone level settings are missing from UI Key: CLOUDSTACK-5476 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5476 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: prashant kumar mishra Priority: Critical steps to repro -- 1-prepare a cs setup 2- goto zone 3-there should be a setting tab actual - zone level setting tab is missing ;please check scareen shot -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Resolved] (CLOUDSTACK-5311) [Hyper-V] Global settings missing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-5311. --- Resolution: Fixed > [Hyper-V] Global settings missing > - > > Key: CLOUDSTACK-5311 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5311 > 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: 4.3, Hyper-V >Reporter: Abhinav Roy >Assignee: Devdeep Singh >Priority: Critical > Labels: hyper-V, > Fix For: 4.3.0 > > > 1. Hyper-v entry is missing from >Global Settings -> Hypervisor capabilities > 2. Hypervisor Version is not listed at > Infrastructure -> Hosts -> - Details -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-5311) [Hyper-V] Global settings missing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846250#comment-13846250 ] ASF subversion and git services commented on CLOUDSTACK-5311: - Commit 7151ec63fab820dbc6bbb35c62b27321c9e2499e in branch refs/heads/4.3 from [~devdeep] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7151ec6 ] CLOUDSTACK-5311: Fix the host version reported by the hyper-v agent. Also updated the hypervisor capabilities for hyper-v. > [Hyper-V] Global settings missing > - > > Key: CLOUDSTACK-5311 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5311 > 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: 4.3, Hyper-V >Reporter: Abhinav Roy >Assignee: Devdeep Singh >Priority: Critical > Labels: hyper-V, > Fix For: 4.3.0 > > > 1. Hyper-v entry is missing from >Global Settings -> Hypervisor capabilities > 2. Hypervisor Version is not listed at > Infrastructure -> Hosts -> - Details -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (CLOUDSTACK-2414) NPE while deleting Cisco VNMC provider
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das updated CLOUDSTACK-2414: Priority: Minor (was: Major) > NPE while deleting Cisco VNMC provider > -- > > Key: CLOUDSTACK-2414 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2414 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 >Reporter: Sailaja Mada >Assignee: Koushik Das >Priority: Minor > Fix For: 4.3.0 > > Attachments: apilog.log, failedmslog, management-server.log > > > Setup: Advanced Networking Zone with VMWARE Cluster > Steps : > 1. Configure VMWARE Cluster with Nexus 1000v > 2. Add Network Service provider CiscoVnmc and add Cisco VNMC device with > wrong credentials. > 3. Delete CiscoVnmc provider > Observation: > NPE during Cisco VNMC host disconnect > 2013-05-08 22:26:34,019 DEBUG [cloud.network.NetworkUsageManagerImpl] > (AgentTaskPool-2:null) Disconnected called on 3 with status Removed > 2013-05-08 22:26:34,019 DEBUG [agent.manager.AgentManagerImpl] > (AgentTaskPool-2:null) Sending Disconnect to listener: > com.cloud.consoleproxy.ConsoleProxyListener > 2013-05-08 22:26:34,019 DEBUG [cloud.host.Status] (AgentTaskPool-2:null) > Transition:[Resource state = Maintenance, Agent event = Remove, Host id = 3, > name = Cisco VNMC Controller - 10.102.192.81] > 2013-05-08 22:26:34,030 ERROR [agent.manager.AgentManagerImpl] > (AgentTaskPool-2:null) Exception caught while handling disconnect: > java.lang.NullPointerException > at com.cloud.host.dao.HostDaoImpl.updateState(HostDaoImpl.java:786) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at com.cloud.host.dao.HostDaoImpl.updateState(HostDaoImpl.java:67) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at com.cloud.utils.fsm.StateMachine2.transitTo(StateMachine2.java:111) > at > com.cloud.agent.manager.AgentManagerImpl.agentStatusTransitTo(AgentManagerImpl.java:1432) > at > com.cloud.agent.manager.AgentManagerImpl.disconnectAgent(AgentManagerImpl.java:1451) > at > com.cloud.agent.manager.AgentManagerImpl.handleDisconnectWithoutInvestigation(AgentManagerImpl.java:882) > at > com.cloud.agent.manager.ClusteredAgentManagerImpl.handleDisconnect(ClusteredAgentManagerImpl.java:291) > at > com.cloud.agent.manager.ClusteredAgentManagerImpl.handleDisconnectWithoutInvestigation(ClusteredAgentManagerImpl.java:280) > at > com.cloud.agent.manager.AgentManagerImpl$DisconnectTask.run(AgentManagerImpl.java:983) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2013-05-08 22:26:36,776 DEBUG [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Zone 1 is ready to launch secondary storage VM > 2013-05-08 22:26:37,223 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] > (consoleproxy-1:null) Zone 1 is ready to launch console proxy -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (CLOUDSTACK-5475) cluster.cpu/(memory).allocated.capacity.disablethreshold is getting displayed multiple time under cluster setting tab
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
prashant kumar mishra updated CLOUDSTACK-5475:
--
Attachment: screenshot-1.jpg
> cluster.cpu/(memory).allocated.capacity.disablethreshold is getting displayed
> multiple time under cluster setting tab
> --
>
> Key: CLOUDSTACK-5475
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5475
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
>Affects Versions: 4.3.0
>Reporter: prashant kumar mishra
> Attachments: screenshot-1.jpg
>
>
> Check cluster setting tab ,
> Expected
>
> it should list each parameter exactly once
> Actual
>
> parameters are getting listed multiple time
> API request and response
> --
> http://10.147.38.177:8080/client/api?command=listConfigurations&clusterid=2afd110b-d56c-46c1-b1fc-b75e444b8b10&response=json&sessionkey=WOFihQLyP9a4XnpkkgDjDea29rQ%3D&page=1&pageSize=20&listAll=true&_=1386843291786
> response:
>
> { "listconfigurationsresponse" : { "count":14 ,"configuration" : [
> {"category":"Advanced","name":"cpu.overprovisioning.factor","value":"1.0","scope":"cluster","description":"Used
> for CPU overprovisioning calculation; available CPU will be
> (actualCpuCapacity * cpu.overprovisioning.factor)"},
> {"category":"Advanced","name":"mem.overprovisioning.factor","value":"1.0","scope":"cluster","description":"Used
> for memory overprovisioning calculation"},
> {"category":"Alert","name":"cluster.cpu.allocated.capacity.notificationthreshold","value":"0.1","scope":"cluster","description":"Percentage
> (as a value between 0 and 1) of cpu utilization above which alerts will be
> sent about low cpu available."},
> {"category":"Alert","name":"cluster.memory.allocated.capacity.notificationthreshold","value":"0.1","scope":"cluster","description":"Percentage
> (as a value between 0 and 1) of memory utilization above which alerts will
> be sent about low memory available."},
> {"category":"Alert","name":"cluster.storage.allocated.capacity.notificationthreshold","value":"1.0","scope":"cluster","description":"Percentage
> (as a value between 0 and 1) of allocated storage utilization above which
> alerts will be sent about low storage available."},
> {"category":"Alert","name":"cluster.storage.capacity.notificationthreshold","value":"1.0","scope":"cluster","description":"Percentage
> (as a value between 0 and 1) of storage utilization above which alerts will
> be sent about low storage available."},
> {"category":"Alert","name":"cluster.cpu.allocated.capacity.disablethreshold","value":"0.1","scope":"cluster","description":"Percentage
> (as a value between 0 and 1) of cpu utilization above which allocators will
> disable using the cluster for low cpu available. Keep the corresponding
> notification threshold lower than this to be notified beforehand."},
> {"category":"Alert","name":"cluster.memory.allocated.capacity.disablethreshold","value":"0.1","scope":"cluster","description":"Percentage
> (as a value between 0 and 1) of memory utilization above which allocators
> will disable using the cluster for low memory available. Keep the
> corresponding notification threshold lower than this to be notified
> beforehand."},
> {"category":"Alert","name":"cluster.cpu.allocated.capacity.disablethreshold","value":"0.1","scope":"cluster","description":"Percentage
> (as a value between 0 and 1) of cpu utilization above which allocators will
> disable using the cluster for low cpu available. Keep the corresponding
> notification threshold lower than this to be notified beforehand."},
> {"category":"Alert","name":"cluster.memory.allocated.capacity.disablethreshold","value":"0.1","scope":"cluster","description":"Percentage
> (as a value between 0 and 1) of memory utilization above which allocators
> will disable using the cluster for low memory available. Keep the
> corresponding notification threshold lower than this to be notified
> beforehand."},
> {"category":"Alert","name":"cluster.cpu.allocated.capacity.disablethreshold","value":"0.1","scope":"cluster","description":"Percentage
> (as a value between 0 and 1) of cpu utilization above which allocators will
> disable using the cluster for low cpu available. Keep the corresponding
> notification threshold lower than this to be notified beforehand."},
> {"category":"Alert","name":"cluster.memory.allocated.capacity.disablethreshold","value":"0.1","scope":"cluster","description":"Percentage
> (as a value between 0 and 1) of memory utilization above which allocators
> will disable
[jira] [Updated] (CLOUDSTACK-5475) cluster.cpu/(memory).allocated.capacity.disablethreshold is getting displayed multiple time under cluster setting tab
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
prashant kumar mishra updated CLOUDSTACK-5475:
--
Affects Version/s: 4.3.0
> cluster.cpu/(memory).allocated.capacity.disablethreshold is getting displayed
> multiple time under cluster setting tab
> --
>
> Key: CLOUDSTACK-5475
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5475
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
>Affects Versions: 4.3.0
>Reporter: prashant kumar mishra
>
> Check cluster setting tab ,
> Expected
>
> it should list each parameter exactly once
> Actual
>
> parameters are getting listed multiple time
> API request and response
> --
> http://10.147.38.177:8080/client/api?command=listConfigurations&clusterid=2afd110b-d56c-46c1-b1fc-b75e444b8b10&response=json&sessionkey=WOFihQLyP9a4XnpkkgDjDea29rQ%3D&page=1&pageSize=20&listAll=true&_=1386843291786
> response:
>
> { "listconfigurationsresponse" : { "count":14 ,"configuration" : [
> {"category":"Advanced","name":"cpu.overprovisioning.factor","value":"1.0","scope":"cluster","description":"Used
> for CPU overprovisioning calculation; available CPU will be
> (actualCpuCapacity * cpu.overprovisioning.factor)"},
> {"category":"Advanced","name":"mem.overprovisioning.factor","value":"1.0","scope":"cluster","description":"Used
> for memory overprovisioning calculation"},
> {"category":"Alert","name":"cluster.cpu.allocated.capacity.notificationthreshold","value":"0.1","scope":"cluster","description":"Percentage
> (as a value between 0 and 1) of cpu utilization above which alerts will be
> sent about low cpu available."},
> {"category":"Alert","name":"cluster.memory.allocated.capacity.notificationthreshold","value":"0.1","scope":"cluster","description":"Percentage
> (as a value between 0 and 1) of memory utilization above which alerts will
> be sent about low memory available."},
> {"category":"Alert","name":"cluster.storage.allocated.capacity.notificationthreshold","value":"1.0","scope":"cluster","description":"Percentage
> (as a value between 0 and 1) of allocated storage utilization above which
> alerts will be sent about low storage available."},
> {"category":"Alert","name":"cluster.storage.capacity.notificationthreshold","value":"1.0","scope":"cluster","description":"Percentage
> (as a value between 0 and 1) of storage utilization above which alerts will
> be sent about low storage available."},
> {"category":"Alert","name":"cluster.cpu.allocated.capacity.disablethreshold","value":"0.1","scope":"cluster","description":"Percentage
> (as a value between 0 and 1) of cpu utilization above which allocators will
> disable using the cluster for low cpu available. Keep the corresponding
> notification threshold lower than this to be notified beforehand."},
> {"category":"Alert","name":"cluster.memory.allocated.capacity.disablethreshold","value":"0.1","scope":"cluster","description":"Percentage
> (as a value between 0 and 1) of memory utilization above which allocators
> will disable using the cluster for low memory available. Keep the
> corresponding notification threshold lower than this to be notified
> beforehand."},
> {"category":"Alert","name":"cluster.cpu.allocated.capacity.disablethreshold","value":"0.1","scope":"cluster","description":"Percentage
> (as a value between 0 and 1) of cpu utilization above which allocators will
> disable using the cluster for low cpu available. Keep the corresponding
> notification threshold lower than this to be notified beforehand."},
> {"category":"Alert","name":"cluster.memory.allocated.capacity.disablethreshold","value":"0.1","scope":"cluster","description":"Percentage
> (as a value between 0 and 1) of memory utilization above which allocators
> will disable using the cluster for low memory available. Keep the
> corresponding notification threshold lower than this to be notified
> beforehand."},
> {"category":"Alert","name":"cluster.cpu.allocated.capacity.disablethreshold","value":"0.1","scope":"cluster","description":"Percentage
> (as a value between 0 and 1) of cpu utilization above which allocators will
> disable using the cluster for low cpu available. Keep the corresponding
> notification threshold lower than this to be notified beforehand."},
> {"category":"Alert","name":"cluster.memory.allocated.capacity.disablethreshold","value":"0.1","scope":"cluster","description":"Percentage
> (as a value between 0 and 1) of memory utilization above which allocators
> will disable using the cluster for low memory available. Ke
[jira] [Created] (CLOUDSTACK-5475) cluster.cpu/(memory).allocated.capacity.disablethreshold is getting displayed multiple time under cluster setting tab
prashant kumar mishra created CLOUDSTACK-5475:
-
Summary: cluster.cpu/(memory).allocated.capacity.disablethreshold
is getting displayed multiple time under cluster setting tab
Key: CLOUDSTACK-5475
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5475
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: API
Reporter: prashant kumar mishra
Check cluster setting tab ,
Expected
it should list each parameter exactly once
Actual
parameters are getting listed multiple time
API request and response
--
http://10.147.38.177:8080/client/api?command=listConfigurations&clusterid=2afd110b-d56c-46c1-b1fc-b75e444b8b10&response=json&sessionkey=WOFihQLyP9a4XnpkkgDjDea29rQ%3D&page=1&pageSize=20&listAll=true&_=1386843291786
response:
{ "listconfigurationsresponse" : { "count":14 ,"configuration" : [
{"category":"Advanced","name":"cpu.overprovisioning.factor","value":"1.0","scope":"cluster","description":"Used
for CPU overprovisioning calculation; available CPU will be (actualCpuCapacity
* cpu.overprovisioning.factor)"},
{"category":"Advanced","name":"mem.overprovisioning.factor","value":"1.0","scope":"cluster","description":"Used
for memory overprovisioning calculation"},
{"category":"Alert","name":"cluster.cpu.allocated.capacity.notificationthreshold","value":"0.1","scope":"cluster","description":"Percentage
(as a value between 0 and 1) of cpu utilization above which alerts will be
sent about low cpu available."},
{"category":"Alert","name":"cluster.memory.allocated.capacity.notificationthreshold","value":"0.1","scope":"cluster","description":"Percentage
(as a value between 0 and 1) of memory utilization above which alerts will be
sent about low memory available."},
{"category":"Alert","name":"cluster.storage.allocated.capacity.notificationthreshold","value":"1.0","scope":"cluster","description":"Percentage
(as a value between 0 and 1) of allocated storage utilization above which
alerts will be sent about low storage available."},
{"category":"Alert","name":"cluster.storage.capacity.notificationthreshold","value":"1.0","scope":"cluster","description":"Percentage
(as a value between 0 and 1) of storage utilization above which alerts will be
sent about low storage available."},
{"category":"Alert","name":"cluster.cpu.allocated.capacity.disablethreshold","value":"0.1","scope":"cluster","description":"Percentage
(as a value between 0 and 1) of cpu utilization above which allocators will
disable using the cluster for low cpu available. Keep the corresponding
notification threshold lower than this to be notified beforehand."},
{"category":"Alert","name":"cluster.memory.allocated.capacity.disablethreshold","value":"0.1","scope":"cluster","description":"Percentage
(as a value between 0 and 1) of memory utilization above which allocators will
disable using the cluster for low memory available. Keep the corresponding
notification threshold lower than this to be notified beforehand."},
{"category":"Alert","name":"cluster.cpu.allocated.capacity.disablethreshold","value":"0.1","scope":"cluster","description":"Percentage
(as a value between 0 and 1) of cpu utilization above which allocators will
disable using the cluster for low cpu available. Keep the corresponding
notification threshold lower than this to be notified beforehand."},
{"category":"Alert","name":"cluster.memory.allocated.capacity.disablethreshold","value":"0.1","scope":"cluster","description":"Percentage
(as a value between 0 and 1) of memory utilization above which allocators will
disable using the cluster for low memory available. Keep the corresponding
notification threshold lower than this to be notified beforehand."},
{"category":"Alert","name":"cluster.cpu.allocated.capacity.disablethreshold","value":"0.1","scope":"cluster","description":"Percentage
(as a value between 0 and 1) of cpu utilization above which allocators will
disable using the cluster for low cpu available. Keep the corresponding
notification threshold lower than this to be notified beforehand."},
{"category":"Alert","name":"cluster.memory.allocated.capacity.disablethreshold","value":"0.1","scope":"cluster","description":"Percentage
(as a value between 0 and 1) of memory utilization above which allocators will
disable using the cluster for low memory available. Keep the corresponding
notification threshold lower than this to be notified beforehand."},
{"category":"Alert","name":"cluster.cpu.allocated.capacity.disablethreshold","value":"0.1","scope":"cluster","description":"Percentage
(as a value between 0 and 1) of cpu utilization above which allocators will
disable using the cluster for low cpu available. Keep the corresponding
notification threshold lower than
[jira] [Issue Comment Deleted] (CLOUDSTACK-5454) Deleting a snapshot from Secondary Staging store after migration returns SUCCESS
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinandan Prateek updated CLOUDSTACK-5454:
---
Comment: was deleted
(was: Commit ca1e10398d507193aa4d9964a6e6b37e9152449d in branch
refs/heads/master from [~rajanik]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ca1e103 ]
CLOUDSTACK-5454 added upgrade path from 4.2.1 to 4.3
Signed-off-by: Abhinandan Prateek
)
> Deleting a snapshot from Secondary Staging store after migration returns
> SUCCESS
>
>
> Key: CLOUDSTACK-5454
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5454
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Snapshot
>Affects Versions: 4.3.0
> Environment: Management Server: 4.3
> Host: kvm
>Reporter: Pavan Kumar Bandarupally
>Assignee: Min Chen
>Priority: Critical
> Fix For: 4.3.0
>
>
> After an NFS store has been migrated to Object store, it will be a read only
> store. Any entities ,snapshots or templates , on this store prior to
> migration should also be read only, which means user should not be able to
> delete them.
> Deletion for template works as expected but the same for snapshot doesn't
> work. In the UI user will be shown a successful task completion for snapshot
> deletion. In the MS logs an exception is thrown but the job is rendered
> SUCCESS. Job Trace below:
> 2013-12-11 18:06:57,128 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-25:ctx-08bb8b65) ===START=== 10.146.0.11 -- GET
> command=deleteSnapshot&id=d7a4b078-4fe7-4933-89b8-316c7c9be61c&response=json&sessionkey=u6C2YtXK2DU2l%2BSFpYbZ4wgNyww%3D&_=1386746147984
> 2013-12-11 18:06:56,591 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-7:null) SeqA 2-20435: Processing Seq 2-20435: { Cmd ,
> MgmtId: -1, via: 2, Ver: v1, Flags: 11,
> [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":1,"_loadInfo":"{\n
> \"connections\": []\n}","wait":0}}] }
> 2013-12-11 18:07:00,367 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-7a541b2c) Completed resetting hosts suitable for reconnect
> 2013-12-11 18:07:00,375 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-7a541b2c) Acquiring hosts for clusters already owned by this
> management server
> 2013-12-11 18:07:00,377 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-7a541b2c) Completed acquiring hosts for clusters already owned by
> this management server
> 2013-12-11 18:07:00,377 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-7a541b2c) Acquiring hosts for clusters not owned by any management
> server
> 2013-12-11 18:07:00,378 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-7a541b2c) Completed acquiring hosts for clusters not owned by any
> management server
> 2013-12-11 18:07:00,444 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-7:null) SeqA 2-20435: Sending Seq 2-20435: { Ans: ,
> MgmtId: 6915098673184, via: 2, Ver: v1, Flags: 100010,
> [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
> 2013-12-11 18:07:00,704 DEBUG [c.c.s.s.SecondaryStorageManagerImpl]
> (secstorage-1:ctx-d8b5b2d1) Zone 1 is ready to launch secondary storage VM
> 2013-12-11 18:07:00,712 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (catalina-exec-25:ctx-08bb8b65 ctx-62ca804c) submit async job-43, details:
> AsyncJobVO {id:43, userId: 2, accountId: 2, instanceType: Snapshot,
> instanceId: 1, cmd:
> org.apache.cloudstack.api.command.user.snapshot.DeleteSnapshotCmd, cmdInfo:
> {"id":"d7a4b078-4fe7-4933-89b8-316c7c9be61c","response":"json","sessionkey":"u6C2YtXK2DU2l+SFpYbZ4wgNyww\u003d","cmdEventType":"SNAPSHOT.DELETE","ctxUserId":"2","httpmethod":"GET","_":"1386746147984","ctxAccountId":"2","ctxStartEventId":"121"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 6915098673184, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2013-12-11 18:07:00,714 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-25:ctx-08bb8b65 ctx-62ca804c) ===END=== 10.146.0.11 -- GET
> command=deleteSnapshot&id=d7a4b078-4fe7-4933-89b8-316c7c9be61c&response=json&sessionkey=u6C2YtXK2DU2l%2BSFpYbZ4wgNyww%3D&_=1386746147984
> 2013-12-11 18:07:00,716 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Job-Executor-13:ctx-e02ea08a) Add job-43 into job monitoring
> 2013-12-11 18:07:00,716 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-13:ctx-e02ea08a) Executing AsyncJobVO {id:43, userId: 2,
> accountId: 2, instanceType: Snapshot, instanceId: 1, cmd:
> org.apache.cloudstack.api.command.user.snapshot.DeleteSnapshotCmd, cmdInfo:
> {"id":"d7a4b07
[jira] [Issue Comment Deleted] (CLOUDSTACK-5454) Deleting a snapshot from Secondary Staging store after migration returns SUCCESS
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinandan Prateek updated CLOUDSTACK-5454:
---
Comment: was deleted
(was: Commit 9992a6a6dc2877d350e027ecc1caf7aaac93da9a in branch refs/heads/4.3
from [~rajanik]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9992a6a ]
CLOUDSTACK-5454 added upgrade path from 4.2.1 to 4.3
Signed-off-by: Abhinandan Prateek
)
> Deleting a snapshot from Secondary Staging store after migration returns
> SUCCESS
>
>
> Key: CLOUDSTACK-5454
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5454
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Snapshot
>Affects Versions: 4.3.0
> Environment: Management Server: 4.3
> Host: kvm
>Reporter: Pavan Kumar Bandarupally
>Assignee: Min Chen
>Priority: Critical
> Fix For: 4.3.0
>
>
> After an NFS store has been migrated to Object store, it will be a read only
> store. Any entities ,snapshots or templates , on this store prior to
> migration should also be read only, which means user should not be able to
> delete them.
> Deletion for template works as expected but the same for snapshot doesn't
> work. In the UI user will be shown a successful task completion for snapshot
> deletion. In the MS logs an exception is thrown but the job is rendered
> SUCCESS. Job Trace below:
> 2013-12-11 18:06:57,128 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-25:ctx-08bb8b65) ===START=== 10.146.0.11 -- GET
> command=deleteSnapshot&id=d7a4b078-4fe7-4933-89b8-316c7c9be61c&response=json&sessionkey=u6C2YtXK2DU2l%2BSFpYbZ4wgNyww%3D&_=1386746147984
> 2013-12-11 18:06:56,591 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-7:null) SeqA 2-20435: Processing Seq 2-20435: { Cmd ,
> MgmtId: -1, via: 2, Ver: v1, Flags: 11,
> [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":1,"_loadInfo":"{\n
> \"connections\": []\n}","wait":0}}] }
> 2013-12-11 18:07:00,367 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-7a541b2c) Completed resetting hosts suitable for reconnect
> 2013-12-11 18:07:00,375 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-7a541b2c) Acquiring hosts for clusters already owned by this
> management server
> 2013-12-11 18:07:00,377 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-7a541b2c) Completed acquiring hosts for clusters already owned by
> this management server
> 2013-12-11 18:07:00,377 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-7a541b2c) Acquiring hosts for clusters not owned by any management
> server
> 2013-12-11 18:07:00,378 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-7a541b2c) Completed acquiring hosts for clusters not owned by any
> management server
> 2013-12-11 18:07:00,444 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-7:null) SeqA 2-20435: Sending Seq 2-20435: { Ans: ,
> MgmtId: 6915098673184, via: 2, Ver: v1, Flags: 100010,
> [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
> 2013-12-11 18:07:00,704 DEBUG [c.c.s.s.SecondaryStorageManagerImpl]
> (secstorage-1:ctx-d8b5b2d1) Zone 1 is ready to launch secondary storage VM
> 2013-12-11 18:07:00,712 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (catalina-exec-25:ctx-08bb8b65 ctx-62ca804c) submit async job-43, details:
> AsyncJobVO {id:43, userId: 2, accountId: 2, instanceType: Snapshot,
> instanceId: 1, cmd:
> org.apache.cloudstack.api.command.user.snapshot.DeleteSnapshotCmd, cmdInfo:
> {"id":"d7a4b078-4fe7-4933-89b8-316c7c9be61c","response":"json","sessionkey":"u6C2YtXK2DU2l+SFpYbZ4wgNyww\u003d","cmdEventType":"SNAPSHOT.DELETE","ctxUserId":"2","httpmethod":"GET","_":"1386746147984","ctxAccountId":"2","ctxStartEventId":"121"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 6915098673184, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2013-12-11 18:07:00,714 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-25:ctx-08bb8b65 ctx-62ca804c) ===END=== 10.146.0.11 -- GET
> command=deleteSnapshot&id=d7a4b078-4fe7-4933-89b8-316c7c9be61c&response=json&sessionkey=u6C2YtXK2DU2l%2BSFpYbZ4wgNyww%3D&_=1386746147984
> 2013-12-11 18:07:00,716 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Job-Executor-13:ctx-e02ea08a) Add job-43 into job monitoring
> 2013-12-11 18:07:00,716 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-13:ctx-e02ea08a) Executing AsyncJobVO {id:43, userId: 2,
> accountId: 2, instanceType: Snapshot, instanceId: 1, cmd:
> org.apache.cloudstack.api.command.user.snapshot.DeleteSnapshotCmd, cmdInfo:
> {"id":"d7a4b078-4
[jira] [Comment Edited] (CLOUDSTACK-5434) ldap configuration breaks on upgrade from 4.2 to 4.3
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846224#comment-13846224 ] Rajani Karuturi edited comment on CLOUDSTACK-5434 at 12/12/13 10:12 AM: Commit ca1e10398d507193aa4d9964a6e6b37e9152449d in branch refs/heads/master from Rajani Karuturi [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ca1e103 ] CLOUDSTACK-5434 added upgrade path from 4.2.1 to 4.3 Signed-off-by: Abhinandan Prateek was (Author: rajanik): Commit ca1e10398d507193aa4d9964a6e6b37e9152449d in branch refs/heads/master from Rajani Karuturi [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ca1e103 ] CLOUDSTACK-5454 added upgrade path from 4.2.1 to 4.3 Signed-off-by: Abhinandan Prateek > ldap configuration breaks on upgrade from 4.2 to 4.3 > > > Key: CLOUDSTACK-5434 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5434 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.0 >Reporter: Rajani Karuturi >Assignee: Rajani Karuturi >Priority: Blocker > Labels: ldap > Fix For: Future, 4.3.0 > > > if a user is on 4.2 and they have LDAP enabled, when they upgrade to 4.3, > unless they reconfigure again, the ldap authentication doesnt work. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-5434) ldap configuration breaks on upgrade from 4.2 to 4.3
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846223#comment-13846223 ] Rajani Karuturi commented on CLOUDSTACK-5434: - Commit 9992a6a6dc2877d350e027ecc1caf7aaac93da9a in branch refs/heads/4.3 from Rajani Karuturi [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9992a6a ] CLOUDSTACK-5454 added upgrade path from 4.2.1 to 4.3 Signed-off-by: Abhinandan Prateek > ldap configuration breaks on upgrade from 4.2 to 4.3 > > > Key: CLOUDSTACK-5434 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5434 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.0 >Reporter: Rajani Karuturi >Assignee: Rajani Karuturi >Priority: Blocker > Labels: ldap > Fix For: Future, 4.3.0 > > > if a user is on 4.2 and they have LDAP enabled, when they upgrade to 4.3, > unless they reconfigure again, the ldap authentication doesnt work. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-5434) ldap configuration breaks on upgrade from 4.2 to 4.3
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846224#comment-13846224 ] Rajani Karuturi commented on CLOUDSTACK-5434: - Commit ca1e10398d507193aa4d9964a6e6b37e9152449d in branch refs/heads/master from Rajani Karuturi [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ca1e103 ] CLOUDSTACK-5454 added upgrade path from 4.2.1 to 4.3 Signed-off-by: Abhinandan Prateek > ldap configuration breaks on upgrade from 4.2 to 4.3 > > > Key: CLOUDSTACK-5434 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5434 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.0 >Reporter: Rajani Karuturi >Assignee: Rajani Karuturi >Priority: Blocker > Labels: ldap > Fix For: Future, 4.3.0 > > > if a user is on 4.2 and they have LDAP enabled, when they upgrade to 4.3, > unless they reconfigure again, the ldap authentication doesnt work. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Comment Edited] (CLOUDSTACK-5434) ldap configuration breaks on upgrade from 4.2 to 4.3
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846223#comment-13846223 ] Rajani Karuturi edited comment on CLOUDSTACK-5434 at 12/12/13 10:12 AM: Commit 9992a6a6dc2877d350e027ecc1caf7aaac93da9a in branch refs/heads/4.3 from Rajani Karuturi [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9992a6a ] CLOUDSTACK-5434 added upgrade path from 4.2.1 to 4.3 Signed-off-by: Abhinandan Prateek was (Author: rajanik): Commit 9992a6a6dc2877d350e027ecc1caf7aaac93da9a in branch refs/heads/4.3 from Rajani Karuturi [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9992a6a ] CLOUDSTACK-5454 added upgrade path from 4.2.1 to 4.3 Signed-off-by: Abhinandan Prateek > ldap configuration breaks on upgrade from 4.2 to 4.3 > > > Key: CLOUDSTACK-5434 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5434 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.0 >Reporter: Rajani Karuturi >Assignee: Rajani Karuturi >Priority: Blocker > Labels: ldap > Fix For: Future, 4.3.0 > > > if a user is on 4.2 and they have LDAP enabled, when they upgrade to 4.3, > unless they reconfigure again, the ldap authentication doesnt work. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-5454) Deleting a snapshot from Secondary Staging store after migration returns SUCCESS
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846220#comment-13846220
]
ASF subversion and git services commented on CLOUDSTACK-5454:
-
Commit ca1e10398d507193aa4d9964a6e6b37e9152449d in branch refs/heads/master
from [~rajanik]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ca1e103 ]
CLOUDSTACK-5454 added upgrade path from 4.2.1 to 4.3
Signed-off-by: Abhinandan Prateek
> Deleting a snapshot from Secondary Staging store after migration returns
> SUCCESS
>
>
> Key: CLOUDSTACK-5454
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5454
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Snapshot
>Affects Versions: 4.3.0
> Environment: Management Server: 4.3
> Host: kvm
>Reporter: Pavan Kumar Bandarupally
>Assignee: Min Chen
>Priority: Critical
> Fix For: 4.3.0
>
>
> After an NFS store has been migrated to Object store, it will be a read only
> store. Any entities ,snapshots or templates , on this store prior to
> migration should also be read only, which means user should not be able to
> delete them.
> Deletion for template works as expected but the same for snapshot doesn't
> work. In the UI user will be shown a successful task completion for snapshot
> deletion. In the MS logs an exception is thrown but the job is rendered
> SUCCESS. Job Trace below:
> 2013-12-11 18:06:57,128 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-25:ctx-08bb8b65) ===START=== 10.146.0.11 -- GET
> command=deleteSnapshot&id=d7a4b078-4fe7-4933-89b8-316c7c9be61c&response=json&sessionkey=u6C2YtXK2DU2l%2BSFpYbZ4wgNyww%3D&_=1386746147984
> 2013-12-11 18:06:56,591 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-7:null) SeqA 2-20435: Processing Seq 2-20435: { Cmd ,
> MgmtId: -1, via: 2, Ver: v1, Flags: 11,
> [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":1,"_loadInfo":"{\n
> \"connections\": []\n}","wait":0}}] }
> 2013-12-11 18:07:00,367 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-7a541b2c) Completed resetting hosts suitable for reconnect
> 2013-12-11 18:07:00,375 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-7a541b2c) Acquiring hosts for clusters already owned by this
> management server
> 2013-12-11 18:07:00,377 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-7a541b2c) Completed acquiring hosts for clusters already owned by
> this management server
> 2013-12-11 18:07:00,377 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-7a541b2c) Acquiring hosts for clusters not owned by any management
> server
> 2013-12-11 18:07:00,378 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-7a541b2c) Completed acquiring hosts for clusters not owned by any
> management server
> 2013-12-11 18:07:00,444 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-7:null) SeqA 2-20435: Sending Seq 2-20435: { Ans: ,
> MgmtId: 6915098673184, via: 2, Ver: v1, Flags: 100010,
> [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
> 2013-12-11 18:07:00,704 DEBUG [c.c.s.s.SecondaryStorageManagerImpl]
> (secstorage-1:ctx-d8b5b2d1) Zone 1 is ready to launch secondary storage VM
> 2013-12-11 18:07:00,712 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (catalina-exec-25:ctx-08bb8b65 ctx-62ca804c) submit async job-43, details:
> AsyncJobVO {id:43, userId: 2, accountId: 2, instanceType: Snapshot,
> instanceId: 1, cmd:
> org.apache.cloudstack.api.command.user.snapshot.DeleteSnapshotCmd, cmdInfo:
> {"id":"d7a4b078-4fe7-4933-89b8-316c7c9be61c","response":"json","sessionkey":"u6C2YtXK2DU2l+SFpYbZ4wgNyww\u003d","cmdEventType":"SNAPSHOT.DELETE","ctxUserId":"2","httpmethod":"GET","_":"1386746147984","ctxAccountId":"2","ctxStartEventId":"121"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 6915098673184, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2013-12-11 18:07:00,714 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-25:ctx-08bb8b65 ctx-62ca804c) ===END=== 10.146.0.11 -- GET
> command=deleteSnapshot&id=d7a4b078-4fe7-4933-89b8-316c7c9be61c&response=json&sessionkey=u6C2YtXK2DU2l%2BSFpYbZ4wgNyww%3D&_=1386746147984
> 2013-12-11 18:07:00,716 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Job-Executor-13:ctx-e02ea08a) Add job-43 into job monitoring
> 2013-12-11 18:07:00,716 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-13:ctx-e02ea08a) Executing AsyncJobVO {id:43, userId: 2,
> accountId: 2, instanceType: Snapshot, instanceId: 1, cmd:
> org.apache.cloudstack.api.command.user.snap
[jira] [Commented] (CLOUDSTACK-5454) Deleting a snapshot from Secondary Staging store after migration returns SUCCESS
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846218#comment-13846218
]
ASF subversion and git services commented on CLOUDSTACK-5454:
-
Commit 9992a6a6dc2877d350e027ecc1caf7aaac93da9a in branch refs/heads/4.3 from
[~rajanik]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9992a6a ]
CLOUDSTACK-5454 added upgrade path from 4.2.1 to 4.3
Signed-off-by: Abhinandan Prateek
> Deleting a snapshot from Secondary Staging store after migration returns
> SUCCESS
>
>
> Key: CLOUDSTACK-5454
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5454
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Snapshot
>Affects Versions: 4.3.0
> Environment: Management Server: 4.3
> Host: kvm
>Reporter: Pavan Kumar Bandarupally
>Assignee: Min Chen
>Priority: Critical
> Fix For: 4.3.0
>
>
> After an NFS store has been migrated to Object store, it will be a read only
> store. Any entities ,snapshots or templates , on this store prior to
> migration should also be read only, which means user should not be able to
> delete them.
> Deletion for template works as expected but the same for snapshot doesn't
> work. In the UI user will be shown a successful task completion for snapshot
> deletion. In the MS logs an exception is thrown but the job is rendered
> SUCCESS. Job Trace below:
> 2013-12-11 18:06:57,128 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-25:ctx-08bb8b65) ===START=== 10.146.0.11 -- GET
> command=deleteSnapshot&id=d7a4b078-4fe7-4933-89b8-316c7c9be61c&response=json&sessionkey=u6C2YtXK2DU2l%2BSFpYbZ4wgNyww%3D&_=1386746147984
> 2013-12-11 18:06:56,591 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-7:null) SeqA 2-20435: Processing Seq 2-20435: { Cmd ,
> MgmtId: -1, via: 2, Ver: v1, Flags: 11,
> [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":1,"_loadInfo":"{\n
> \"connections\": []\n}","wait":0}}] }
> 2013-12-11 18:07:00,367 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-7a541b2c) Completed resetting hosts suitable for reconnect
> 2013-12-11 18:07:00,375 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-7a541b2c) Acquiring hosts for clusters already owned by this
> management server
> 2013-12-11 18:07:00,377 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-7a541b2c) Completed acquiring hosts for clusters already owned by
> this management server
> 2013-12-11 18:07:00,377 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-7a541b2c) Acquiring hosts for clusters not owned by any management
> server
> 2013-12-11 18:07:00,378 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-7a541b2c) Completed acquiring hosts for clusters not owned by any
> management server
> 2013-12-11 18:07:00,444 DEBUG [c.c.a.m.AgentManagerImpl]
> (AgentManager-Handler-7:null) SeqA 2-20435: Sending Seq 2-20435: { Ans: ,
> MgmtId: 6915098673184, via: 2, Ver: v1, Flags: 100010,
> [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
> 2013-12-11 18:07:00,704 DEBUG [c.c.s.s.SecondaryStorageManagerImpl]
> (secstorage-1:ctx-d8b5b2d1) Zone 1 is ready to launch secondary storage VM
> 2013-12-11 18:07:00,712 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (catalina-exec-25:ctx-08bb8b65 ctx-62ca804c) submit async job-43, details:
> AsyncJobVO {id:43, userId: 2, accountId: 2, instanceType: Snapshot,
> instanceId: 1, cmd:
> org.apache.cloudstack.api.command.user.snapshot.DeleteSnapshotCmd, cmdInfo:
> {"id":"d7a4b078-4fe7-4933-89b8-316c7c9be61c","response":"json","sessionkey":"u6C2YtXK2DU2l+SFpYbZ4wgNyww\u003d","cmdEventType":"SNAPSHOT.DELETE","ctxUserId":"2","httpmethod":"GET","_":"1386746147984","ctxAccountId":"2","ctxStartEventId":"121"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 6915098673184, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2013-12-11 18:07:00,714 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-25:ctx-08bb8b65 ctx-62ca804c) ===END=== 10.146.0.11 -- GET
> command=deleteSnapshot&id=d7a4b078-4fe7-4933-89b8-316c7c9be61c&response=json&sessionkey=u6C2YtXK2DU2l%2BSFpYbZ4wgNyww%3D&_=1386746147984
> 2013-12-11 18:07:00,716 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Job-Executor-13:ctx-e02ea08a) Add job-43 into job monitoring
> 2013-12-11 18:07:00,716 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Job-Executor-13:ctx-e02ea08a) Executing AsyncJobVO {id:43, userId: 2,
> accountId: 2, instanceType: Snapshot, instanceId: 1, cmd:
> org.apache.cloudstack.api.command.user.snapsho
[jira] [Resolved] (CLOUDSTACK-5473) Hyper-v agent service name needs to be fixed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-5473. --- Resolution: Fixed > Hyper-v agent service name needs to be fixed > > > Key: CLOUDSTACK-5473 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5473 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller >Affects Versions: 4.3.0 > Environment: Hyperv >Reporter: Devdeep Singh >Assignee: Devdeep Singh > Labels: hyper-V, > Fix For: 4.3.0 > > > The cloudstack agent service gets installed with the name "CloudStack > ServerResource". It needs to be fixed and given a better name, e.g. > "CloudStack Hyper-V Agent" -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Resolved] (CLOUDSTACK-5462) Hyper-V Agent confused by existing volume of different image type
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-5462. --- Resolution: Fixed Reviewed and pushed the changes by Donal > Hyper-V Agent confused by existing volume of different image type > - > > Key: CLOUDSTACK-5462 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5462 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller >Affects Versions: 4.3.0 >Reporter: Donal Lafferty > Labels: hyper-v > > VolumeObjectTO objects do not specify the image format. > Hyper-V infers the format from files with the same name as that specified in > the VolumeObjectTO.name field. This fails when a name is reused for a > different image type. > E.g. if the agent finds a ROOT2-1.vhd, it will assume that the VolumeObjectTO > is a VHD. However, if the VolumeObjectTO is actually a VHDX, then the disk > will appear to be corrupt to the hypervisor. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-5462) Hyper-V Agent confused by existing volume of different image type
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846194#comment-13846194 ] ASF subversion and git services commented on CLOUDSTACK-5462: - Commit ffd1a078d49cb8491e29a881970077c682fd1cb0 in branch refs/heads/master from [~dlaffe...@gmail.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ffd1a07 ] CLOUDSTACK-5462: Hyperv agent confused by existing volume of different image type. Works by avoiding volume image format inference errors and removing existing files with same name, but different format. > Hyper-V Agent confused by existing volume of different image type > - > > Key: CLOUDSTACK-5462 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5462 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller >Affects Versions: 4.3.0 >Reporter: Donal Lafferty > Labels: hyper-v > > VolumeObjectTO objects do not specify the image format. > Hyper-V infers the format from files with the same name as that specified in > the VolumeObjectTO.name field. This fails when a name is reused for a > different image type. > E.g. if the agent finds a ROOT2-1.vhd, it will assume that the VolumeObjectTO > is a VHD. However, if the VolumeObjectTO is actually a VHDX, then the disk > will appear to be corrupt to the hypervisor. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-5473) Hyper-v agent service name needs to be fixed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846193#comment-13846193 ] ASF subversion and git services commented on CLOUDSTACK-5473: - Commit bdbc5f2ae395efbd8b4e8836418857e32dc333ed in branch refs/heads/master from [~devdeep] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=bdbc5f2 ] CLOUDSTACK-5473: Fixed the name with which the hyper-v agent gets installed as a service. > Hyper-v agent service name needs to be fixed > > > Key: CLOUDSTACK-5473 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5473 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller >Affects Versions: 4.3.0 > Environment: Hyperv >Reporter: Devdeep Singh >Assignee: Devdeep Singh > Labels: hyper-V, > Fix For: 4.3.0 > > > The cloudstack agent service gets installed with the name "CloudStack > ServerResource". It needs to be fixed and given a better name, e.g. > "CloudStack Hyper-V Agent" -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-5462) Hyper-V Agent confused by existing volume of different image type
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846189#comment-13846189 ] ASF subversion and git services commented on CLOUDSTACK-5462: - Commit 23bc02d12a0aa7941eec2a85d5bd785ebbb6d725 in branch refs/heads/4.3 from [~dlaffe...@gmail.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=23bc02d ] CLOUDSTACK-5462: Hyperv agent confused by existing volume of different image type. Works by avoiding volume image format inference errors and removing existing files with same name, but different format. > Hyper-V Agent confused by existing volume of different image type > - > > Key: CLOUDSTACK-5462 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5462 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller >Affects Versions: 4.3.0 >Reporter: Donal Lafferty > Labels: hyper-v > > VolumeObjectTO objects do not specify the image format. > Hyper-V infers the format from files with the same name as that specified in > the VolumeObjectTO.name field. This fails when a name is reused for a > different image type. > E.g. if the agent finds a ROOT2-1.vhd, it will assume that the VolumeObjectTO > is a VHD. However, if the VolumeObjectTO is actually a VHDX, then the disk > will appear to be corrupt to the hypervisor. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-5473) Hyper-v agent service name needs to be fixed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846188#comment-13846188 ] ASF subversion and git services commented on CLOUDSTACK-5473: - Commit 388510ff39981723b61092a5e48f8d699132fddb in branch refs/heads/4.3 from [~devdeep] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=388510f ] CLOUDSTACK-5473: Fixed the name with which the hyper-v agent gets installed as a service. > Hyper-v agent service name needs to be fixed > > > Key: CLOUDSTACK-5473 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5473 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller >Affects Versions: 4.3.0 > Environment: Hyperv >Reporter: Devdeep Singh >Assignee: Devdeep Singh > Labels: hyper-V, > Fix For: 4.3.0 > > > The cloudstack agent service gets installed with the name "CloudStack > ServerResource". It needs to be fixed and given a better name, e.g. > "CloudStack Hyper-V Agent" -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Resolved] (CLOUDSTACK-5259) Xenserver - Not able to create template from snapshot.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinandan Prateek resolved CLOUDSTACK-5259.
Resolution: Fixed
> Xenserver - Not able to create template from snapshot.
> ---
>
> Key: CLOUDSTACK-5259
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5259
> 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: Build from 4.3
>Reporter: Sangeetha Hariharan
>Assignee: Abhinandan Prateek
>Priority: Critical
> Fix For: 4.3.0
>
> Attachments: management-server.rar, xen1-2.rar, xen1.rar, xen2.rar
>
>
> Xenserver - Not able to create template from snapshot.
> Steps to reproduce the problem:
> Set up - Advanced zone with Xenserver 6.2
> Created hourly recurring snapshot.
> Create a template from snapshot.
> Template creation fails with the following exception:
> Failed to create
> template/usr/local/cloud/systemvm/scripts/storage/secondary/create_privatetemplate_from_snapshot_xen.sh:
> line 65: /bin/vhd-util: No such file or directory30#failed to query
> /mnt/SecStorage/8d6190f7-3fc3-3a66-8a8c-bd8e50f2bbc6/snapshots/9/89/a2c06f0c-92e4-41b2-a4cb-7d1675146111.vhd
> We see the following vhd file exist in the secondary store.
> root@nfs3 89]# pwd
> /export/home/sangeetha/felton/xen/secondary/snapshots/9/89
> [root@nfs3 89]# ls -ltr
> total 2579628
> -rw-r--r-- 1 root root 7186309632 Nov 22 15:42
> 8546a63f-dc01-4348-babc-c34c138579c7.vhd
> -rw-r--r-- 1 root root 155537920 Nov 22 16:36
> 9d1404ca-c97e-4f6b-a1a4-3bb5fb1d3900.vhd
> -rw-r--r-- 1 root root 229081600 Nov 24 18:52
> 0323b0cb-446e-4550-a443-d135c4a960b8.vhd
> -rw-r--r-- 1 root root 75690496 Nov 24 19:35
> e440d533-c5cf-464c-940a-505d5b0108c4.vhd
> -rw-r--r-- 1 root root 81994240 Nov 24 20:35
> 53f884fb-cd9c-4c35-bcf1-b90f3ce0ea5f.vhd
> -rw-r--r-- 1 root root 81994240 Nov 24 21:35
> 8ad156ad-e63f-44e1-a8ad-7bcc8acd0b26.vhd
> -rw-r--r-- 1 root root 79892992 Nov 24 22:35
> 2781b5af-7c92-482c-8775-f331c7df9b2b.vhd
> -rw-r--r-- 1 root root 75690496 Nov 24 23:35
> a2c06f0c-92e4-41b2-a4cb-7d1675146111.vhd
> -rw-r--r-- 1 root root 81994240 Nov 25 00:35
> 3bd9fe33-ce59-4148-825f-f9e75e56d088.vhd
> -rw-r--r-- 1 root root 81994240 Nov 25 01:35
> ab414c2b-ed16-4ee2-b3f8-d17b5075fe8d.vhd
> -rw-r--r-- 1 root root 81994240 Nov 25 02:35
> cdd97481-d32d-4350-aaae-0a2132c2d934.vhd
> -rw-r--r-- 1 root root 81994240 Nov 25 03:35
> 1d82a5a0-1a75-44f3-8a27-dffcf1127b62.vhd
> -rw-r--r-- 1 root root 81994240 Nov 25 04:35
> 061043e7-9c22-404c-88e5-183ab4590f5e.vhd
> -rw-r--r-- 1 root root 81994240 Nov 25 05:35
> f82e0d43-e83b-493b-b953-6f06a94a369b.vhd
> -rw-r--r-- 1 root root 84095488 Nov 25 06:35
> 6c0065ad-9fc0-4ce6-957c-0475153c2ed4.vhd
> [root@nfs3 89]#
> Management server logs:
> 2013-11-25 13:01:43,109 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (catalina-exec-15:ctx-8576afd8 ctx-2f9b87f6) submit async job-726, details:
> AsyncJobVO {id:726, userI
> d: 2, accountId: 2, instanceType: Template, instanceId: 204, cmd:
> org.apache.cloudstack.api.command.user.template.CreateTemplateCmd, cmdInfo:
> {"sessionkey":"2I2cmFDP
> FQyACWMGWW8h54MGdC0\u003d","cmdEventType":"TEMPLATE.CREATE","ctxUserId":"2","httpmethod":"GET","osTypeId":"e7460654-52fe-11e3-821d-665544288891","isPublic":"true","i
> sdynamicallyscalable":"false","response":"json","id":"204","displayText":"temp99","snapshotid":"b6e507c5-3758-458f-bc98-01e69e2402b0","passwordEnabled":"false","name
> ":"temp99","_":"1385402509285","ctxAccountId":"2","ctxStartEventId":"21369"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, init
> Msid: 112516401760401, completeMsid: null, lastUpdated: null, lastPolled:
> null, created: null}
> 2013-11-25 13:01:43,110 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-15:ctx-8576afd8 ctx-2f9b87f6) ===END=== 10.215.3.7 -- GET
> command=createTemplate&response=json&sess
> ionkey=2I2cmFDPFQyACWMGWW8h54MGdC0%3D&snapshotid=b6e507c5-3758-458f-bc98-01e69e2402b0&name=temp99&displayText=temp99&osTypeId=e7460654-52fe-11e3-821d-665544288891&is
> Public=true&passwordEnabled=false&isdynamicallyscalable=false&_=1385402509285
> 2013-11-25 13:01:43,127 DEBUG [o.a.c.s.i.TemplateDataFactoryImpl]
> (Job-Executor-105:ctx-d53e3263 ctx-2f9b87f6) template 204 is already in
> store:1, type:Image
> 2013-11-25 13:01:43,134 DEBUG [o.a.c.s.m.AncientDataMotionStrategy]
> (Job-Executor-105:ctx-d53e3263 ctx-2f9b87f6) copyAsync inspecting src type
> SNAPSHOT copyAsync ins
> pecting dest type TEMPLATE
> 2013-11-25 13:01:43,156 DEBUG [c.c.a.t.Request]
> (Job-Executor-105:ctx-d53e3263 ctx
[jira] [Commented] (CLOUDSTACK-5259) Xenserver - Not able to create template from snapshot.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846186#comment-13846186
]
ASF subversion and git services commented on CLOUDSTACK-5259:
-
Commit bbeb164abffb3d0a973229f53fe80c469c391219 in branch refs/heads/master
from [~aprateek]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=bbeb164 ]
CLOUDSTACK-5259: added 32 bit support for vhd-util
> Xenserver - Not able to create template from snapshot.
> ---
>
> Key: CLOUDSTACK-5259
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5259
> 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: Build from 4.3
>Reporter: Sangeetha Hariharan
>Assignee: Abhinandan Prateek
>Priority: Critical
> Fix For: 4.3.0
>
> Attachments: management-server.rar, xen1-2.rar, xen1.rar, xen2.rar
>
>
> Xenserver - Not able to create template from snapshot.
> Steps to reproduce the problem:
> Set up - Advanced zone with Xenserver 6.2
> Created hourly recurring snapshot.
> Create a template from snapshot.
> Template creation fails with the following exception:
> Failed to create
> template/usr/local/cloud/systemvm/scripts/storage/secondary/create_privatetemplate_from_snapshot_xen.sh:
> line 65: /bin/vhd-util: No such file or directory30#failed to query
> /mnt/SecStorage/8d6190f7-3fc3-3a66-8a8c-bd8e50f2bbc6/snapshots/9/89/a2c06f0c-92e4-41b2-a4cb-7d1675146111.vhd
> We see the following vhd file exist in the secondary store.
> root@nfs3 89]# pwd
> /export/home/sangeetha/felton/xen/secondary/snapshots/9/89
> [root@nfs3 89]# ls -ltr
> total 2579628
> -rw-r--r-- 1 root root 7186309632 Nov 22 15:42
> 8546a63f-dc01-4348-babc-c34c138579c7.vhd
> -rw-r--r-- 1 root root 155537920 Nov 22 16:36
> 9d1404ca-c97e-4f6b-a1a4-3bb5fb1d3900.vhd
> -rw-r--r-- 1 root root 229081600 Nov 24 18:52
> 0323b0cb-446e-4550-a443-d135c4a960b8.vhd
> -rw-r--r-- 1 root root 75690496 Nov 24 19:35
> e440d533-c5cf-464c-940a-505d5b0108c4.vhd
> -rw-r--r-- 1 root root 81994240 Nov 24 20:35
> 53f884fb-cd9c-4c35-bcf1-b90f3ce0ea5f.vhd
> -rw-r--r-- 1 root root 81994240 Nov 24 21:35
> 8ad156ad-e63f-44e1-a8ad-7bcc8acd0b26.vhd
> -rw-r--r-- 1 root root 79892992 Nov 24 22:35
> 2781b5af-7c92-482c-8775-f331c7df9b2b.vhd
> -rw-r--r-- 1 root root 75690496 Nov 24 23:35
> a2c06f0c-92e4-41b2-a4cb-7d1675146111.vhd
> -rw-r--r-- 1 root root 81994240 Nov 25 00:35
> 3bd9fe33-ce59-4148-825f-f9e75e56d088.vhd
> -rw-r--r-- 1 root root 81994240 Nov 25 01:35
> ab414c2b-ed16-4ee2-b3f8-d17b5075fe8d.vhd
> -rw-r--r-- 1 root root 81994240 Nov 25 02:35
> cdd97481-d32d-4350-aaae-0a2132c2d934.vhd
> -rw-r--r-- 1 root root 81994240 Nov 25 03:35
> 1d82a5a0-1a75-44f3-8a27-dffcf1127b62.vhd
> -rw-r--r-- 1 root root 81994240 Nov 25 04:35
> 061043e7-9c22-404c-88e5-183ab4590f5e.vhd
> -rw-r--r-- 1 root root 81994240 Nov 25 05:35
> f82e0d43-e83b-493b-b953-6f06a94a369b.vhd
> -rw-r--r-- 1 root root 84095488 Nov 25 06:35
> 6c0065ad-9fc0-4ce6-957c-0475153c2ed4.vhd
> [root@nfs3 89]#
> Management server logs:
> 2013-11-25 13:01:43,109 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (catalina-exec-15:ctx-8576afd8 ctx-2f9b87f6) submit async job-726, details:
> AsyncJobVO {id:726, userI
> d: 2, accountId: 2, instanceType: Template, instanceId: 204, cmd:
> org.apache.cloudstack.api.command.user.template.CreateTemplateCmd, cmdInfo:
> {"sessionkey":"2I2cmFDP
> FQyACWMGWW8h54MGdC0\u003d","cmdEventType":"TEMPLATE.CREATE","ctxUserId":"2","httpmethod":"GET","osTypeId":"e7460654-52fe-11e3-821d-665544288891","isPublic":"true","i
> sdynamicallyscalable":"false","response":"json","id":"204","displayText":"temp99","snapshotid":"b6e507c5-3758-458f-bc98-01e69e2402b0","passwordEnabled":"false","name
> ":"temp99","_":"1385402509285","ctxAccountId":"2","ctxStartEventId":"21369"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, init
> Msid: 112516401760401, completeMsid: null, lastUpdated: null, lastPolled:
> null, created: null}
> 2013-11-25 13:01:43,110 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-15:ctx-8576afd8 ctx-2f9b87f6) ===END=== 10.215.3.7 -- GET
> command=createTemplate&response=json&sess
> ionkey=2I2cmFDPFQyACWMGWW8h54MGdC0%3D&snapshotid=b6e507c5-3758-458f-bc98-01e69e2402b0&name=temp99&displayText=temp99&osTypeId=e7460654-52fe-11e3-821d-665544288891&is
> Public=true&passwordEnabled=false&isdynamicallyscalable=false&_=1385402509285
> 2013-11-25 13:01:43,127 DEBUG [o.a.c.s.i.TemplateDataFactoryImpl]
> (Job-Executor-105:ctx-d53e3263 ctx-2f9b87f6) template 204 is already in
> store:1, type:Image
> 2013-11-25
[jira] [Commented] (CLOUDSTACK-5259) Xenserver - Not able to create template from snapshot.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846185#comment-13846185
]
ASF subversion and git services commented on CLOUDSTACK-5259:
-
Commit 0887c739619cc816c8524990b7ee5c0b599dd6bc in branch refs/heads/4.3 from
[~aprateek]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0887c73 ]
CLOUDSTACK-5259: added 32 bit support for vhd-util
> Xenserver - Not able to create template from snapshot.
> ---
>
> Key: CLOUDSTACK-5259
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5259
> 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: Build from 4.3
>Reporter: Sangeetha Hariharan
>Assignee: Abhinandan Prateek
>Priority: Critical
> Fix For: 4.3.0
>
> Attachments: management-server.rar, xen1-2.rar, xen1.rar, xen2.rar
>
>
> Xenserver - Not able to create template from snapshot.
> Steps to reproduce the problem:
> Set up - Advanced zone with Xenserver 6.2
> Created hourly recurring snapshot.
> Create a template from snapshot.
> Template creation fails with the following exception:
> Failed to create
> template/usr/local/cloud/systemvm/scripts/storage/secondary/create_privatetemplate_from_snapshot_xen.sh:
> line 65: /bin/vhd-util: No such file or directory30#failed to query
> /mnt/SecStorage/8d6190f7-3fc3-3a66-8a8c-bd8e50f2bbc6/snapshots/9/89/a2c06f0c-92e4-41b2-a4cb-7d1675146111.vhd
> We see the following vhd file exist in the secondary store.
> root@nfs3 89]# pwd
> /export/home/sangeetha/felton/xen/secondary/snapshots/9/89
> [root@nfs3 89]# ls -ltr
> total 2579628
> -rw-r--r-- 1 root root 7186309632 Nov 22 15:42
> 8546a63f-dc01-4348-babc-c34c138579c7.vhd
> -rw-r--r-- 1 root root 155537920 Nov 22 16:36
> 9d1404ca-c97e-4f6b-a1a4-3bb5fb1d3900.vhd
> -rw-r--r-- 1 root root 229081600 Nov 24 18:52
> 0323b0cb-446e-4550-a443-d135c4a960b8.vhd
> -rw-r--r-- 1 root root 75690496 Nov 24 19:35
> e440d533-c5cf-464c-940a-505d5b0108c4.vhd
> -rw-r--r-- 1 root root 81994240 Nov 24 20:35
> 53f884fb-cd9c-4c35-bcf1-b90f3ce0ea5f.vhd
> -rw-r--r-- 1 root root 81994240 Nov 24 21:35
> 8ad156ad-e63f-44e1-a8ad-7bcc8acd0b26.vhd
> -rw-r--r-- 1 root root 79892992 Nov 24 22:35
> 2781b5af-7c92-482c-8775-f331c7df9b2b.vhd
> -rw-r--r-- 1 root root 75690496 Nov 24 23:35
> a2c06f0c-92e4-41b2-a4cb-7d1675146111.vhd
> -rw-r--r-- 1 root root 81994240 Nov 25 00:35
> 3bd9fe33-ce59-4148-825f-f9e75e56d088.vhd
> -rw-r--r-- 1 root root 81994240 Nov 25 01:35
> ab414c2b-ed16-4ee2-b3f8-d17b5075fe8d.vhd
> -rw-r--r-- 1 root root 81994240 Nov 25 02:35
> cdd97481-d32d-4350-aaae-0a2132c2d934.vhd
> -rw-r--r-- 1 root root 81994240 Nov 25 03:35
> 1d82a5a0-1a75-44f3-8a27-dffcf1127b62.vhd
> -rw-r--r-- 1 root root 81994240 Nov 25 04:35
> 061043e7-9c22-404c-88e5-183ab4590f5e.vhd
> -rw-r--r-- 1 root root 81994240 Nov 25 05:35
> f82e0d43-e83b-493b-b953-6f06a94a369b.vhd
> -rw-r--r-- 1 root root 84095488 Nov 25 06:35
> 6c0065ad-9fc0-4ce6-957c-0475153c2ed4.vhd
> [root@nfs3 89]#
> Management server logs:
> 2013-11-25 13:01:43,109 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (catalina-exec-15:ctx-8576afd8 ctx-2f9b87f6) submit async job-726, details:
> AsyncJobVO {id:726, userI
> d: 2, accountId: 2, instanceType: Template, instanceId: 204, cmd:
> org.apache.cloudstack.api.command.user.template.CreateTemplateCmd, cmdInfo:
> {"sessionkey":"2I2cmFDP
> FQyACWMGWW8h54MGdC0\u003d","cmdEventType":"TEMPLATE.CREATE","ctxUserId":"2","httpmethod":"GET","osTypeId":"e7460654-52fe-11e3-821d-665544288891","isPublic":"true","i
> sdynamicallyscalable":"false","response":"json","id":"204","displayText":"temp99","snapshotid":"b6e507c5-3758-458f-bc98-01e69e2402b0","passwordEnabled":"false","name
> ":"temp99","_":"1385402509285","ctxAccountId":"2","ctxStartEventId":"21369"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, init
> Msid: 112516401760401, completeMsid: null, lastUpdated: null, lastPolled:
> null, created: null}
> 2013-11-25 13:01:43,110 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-15:ctx-8576afd8 ctx-2f9b87f6) ===END=== 10.215.3.7 -- GET
> command=createTemplate&response=json&sess
> ionkey=2I2cmFDPFQyACWMGWW8h54MGdC0%3D&snapshotid=b6e507c5-3758-458f-bc98-01e69e2402b0&name=temp99&displayText=temp99&osTypeId=e7460654-52fe-11e3-821d-665544288891&is
> Public=true&passwordEnabled=false&isdynamicallyscalable=false&_=1385402509285
> 2013-11-25 13:01:43,127 DEBUG [o.a.c.s.i.TemplateDataFactoryImpl]
> (Job-Executor-105:ctx-d53e3263 ctx-2f9b87f6) template 204 is already in
> store:1, type:Image
> 2013-11-25 13:
[jira] [Commented] (CLOUDSTACK-5435) ldap params are not encrypted
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846181#comment-13846181 ] Rajani Karuturi commented on CLOUDSTACK-5435: - patch is on review board https://reviews.apache.org/r/16212/ > ldap params are not encrypted > - > > Key: CLOUDSTACK-5435 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5435 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.0 >Reporter: Rajani Karuturi >Assignee: Rajani Karuturi > Labels: ldap > Fix For: Future, 4.3.0 > > > ldap global params in configuration table are not encrypted. These were > encrypted in 4.2 -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Resolved] (CLOUDSTACK-5435) ldap params are not encrypted
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi resolved CLOUDSTACK-5435. - Resolution: Fixed > ldap params are not encrypted > - > > Key: CLOUDSTACK-5435 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5435 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.3.0 >Reporter: Rajani Karuturi >Assignee: Rajani Karuturi > Labels: ldap > Fix For: Future, 4.3.0 > > > ldap global params in configuration table are not encrypted. These were > encrypted in 4.2 -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-5342) Add NIC to virtual machine fails in KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846179#comment-13846179
]
Girish Shilamkar commented on CLOUDSTACK-5342:
--
Hi Saksham,
No we aren't adding a multiple nics to same network. The tests passes on Xen
and are failing only on KVM.
I think it would make sense check if in prior tests nics are not removed and
causing the problem.
> Add NIC to virtual machine fails in KVM
> ---
>
> Key: CLOUDSTACK-5342
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5342
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
>Affects Versions: 4.3.0
> Environment: KVM advanced
>Reporter: Gaurav Aradhye
>Assignee: Marcus Sorensen
>Priority: Blocker
> Fix For: 4.3.0
>
>
> Add network to VM test cases fail in KVM with following error.
> Execute cmd: asyncquery failed, due to: {errorcode : 530, errortext :
> u'Unable to add NIC to VM[User|VM-e9350ee5-bf2e-418c-91d6-1535dcb4d488]'}
> The same test cases execute successfully on XenServer. As per the feature
> specification (see
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Add+Remove+Networks+to+VMs),
> "Add network to VM" feature should be supported on KVM too.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Created] (CLOUDSTACK-5474) EventBus: RabbitMQ provider expects password to be stored in plain text.
Murali Reddy created CLOUDSTACK-5474: Summary: EventBus: RabbitMQ provider expects password to be stored in plain text. Key: CLOUDSTACK-5474 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5474 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.2.0, 4.1.0, 4.3.0 Reporter: Murali Reddy Assignee: Murali Reddy Fix For: 4.3.0 EventBus: RabbitMQ provider expects password to be stored in plain text. This is security concern. This bug is to support encrypted password in the RabbitMQ config file. Will update the bug with the details of the encryption algorithm after investigation. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
