[jira] [Reopened] (CLOUDSTACK-3014) unable to start instance because ssh to router is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kiran Koneti reopened CLOUDSTACK-3014:
--
Facing the same problem with the setup when we run the cloudstack-setup-
database,.What are we supposed to do in the case 1.
> unable to start instance because ssh to router is failing
> -
>
> Key: CLOUDSTACK-3014
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3014
> 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: esx 5.1 , master build
>Reporter: Srikanteswararao Talluri
>Assignee: Jayapal Reddy
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: management-server.log.zip
>
>
> 1. deploy an advanced zone with vmware esx 5.1
> 2. try to deploy a VM
> Following exception is encountered:
> Failed to authentication SSH user root on host 10.147.40.164
> 2013-06-15 01:36:13,977 ERROR [vmware.resource.VmwareResource]
> (DirectAgent-18:10.147.40.30) Unable to execute NetworkUsage command on DomR
> (10.147.40.164), domR may not be ready yet. failure due to Exception:
> java.lang.Exception
> Message: Failed to authentication SSH user root on host 10.147.40.164
> java.lang.Exception: Failed to authentication SSH user root on host
> 10.147.40.164
> at com.cloud.utils.ssh.SshHelper.sshExecute(SshHelper.java:144)
> at com.cloud.utils.ssh.SshHelper.sshExecute(SshHelper.java:37)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.networkUsage(VmwareResource.java:5451)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2301)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:480)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
> 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.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
> 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-06-15 01:36:13,980 DEBUG [vmware.resource.VmwareResource]
> (DirectAgent-18:10.147.40.30) Executing resource GetDomRVersionCmd:
> {"accessDetails":{"router.ip":"10.147.40.164","router.name":"r-8-VM"},"wait":0}
> 2013-06-15 01:36:13,980 DEBUG [vmware.resource.VmwareResource]
> (DirectAgent-18:10.147.40.30) Run command on domR 10.147.40.164,
> /opt/cloud/bin/get_template_version.sh
> 2013-06-15 01:36:13,981 DEBUG [vmware.resource.VmwareResource]
> (DirectAgent-18:10.147.40.30) Use router's private IP for SSH control. IP :
> 10.147.40.164
> 2013-06-15 01:36:14,081 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null)
> ===START=== 10.101.255.119 -- GET
> command=queryAsyncJobResult&jobId=43dde7f6-fb5d-4ead-8691-5071feb44dfd&response=json&sessionkey=tN07%2BJ4GVSCHGNV%2FPjdO3V%2Bs3Tg%3D&_=1371220848020
> 2013-06-15 01:36:14,163 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null)
> ===END=== 10.101.255.119 -- GET
> command=queryAsyncJobResult&jobId=43dde7f6-fb5d-4ead-8691-5071feb44dfd&response=json&sessionkey=tN07%2BJ4GVSCHGNV%2FPjdO3V%2Bs3Tg%3D&_=1371220848020
> 2013-06-15 01:36:14,231 ERROR [utils.ssh.SshHelper]
> (DirectAgent-18:10.147.40.30) Failed to authentication SSH user root on host
> 10.147.40.164
> 2013-06-15 01:36:14,235 ERROR [vmware.resource.VmwareResource]
> (DirectAgent-18:10.147.40.30) GetDomRVersionCmd failed due to Exception:
> java.lang.Exception
> Message: Failed to authentication SSH user root on host 10.147.40.164
> java.lang.Exception: Failed to authentication SSH user root on host
> 10.147.40.164
> at com.cloud.utils.ssh.SshHelper.sshExecute(SshHelper.java:144)
> at com.cloud.utils.ssh.SshHelper.sshExecute(SshHelper.java:37)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2143)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:488)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at
[jira] [Updated] (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:all-tabpanel ] Kiran Koneti updated CLOUDSTACK-5434: - Priority: Blocker (was: Major) > 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] [Created] (CLOUDSTACK-5457) DBHA features is broken in the latest 4.3 Build.
Kiran Koneti created CLOUDSTACK-5457: Summary: 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 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-5527) No option to create non-Ldap users through the UI when the LDAP integration is done.
Kiran Koneti created CLOUDSTACK-5527: Summary: No option to create non-Ldap users through the UI when the LDAP integration is done. Key: CLOUDSTACK-5527 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5527 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 Priority: Critical Fix For: 4.3.0 Created a CS setup and integrated the same with an Ldap server and tried to import some users from the Ldapthe users in the Ldap are imported successfully,but there is no option to create non-ldap users in the UI. Eg: if i want to create a User/account in the CS which is non Ldap user then there is no option for that through the UI i can do it through the API call. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Created] (CLOUDSTACK-5529) Users/Accounts created through the API are not displayed in the UI after the Ldap integration is done.
Kiran Koneti created CLOUDSTACK-5529: Summary: Users/Accounts created through the API are not displayed in the UI after the Ldap integration is done. Key: CLOUDSTACK-5529 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5529 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 Priority: Critical Fix For: 4.3.0 Created a CS setup and integrated the same with an Ldap server and tried to import some users from the Ldapthe users in the Ldap are imported successfully,and when i created a USer through the API call the user is created successfully,but the user is not displyed in the UI .When checked in the DB the user is listed. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Reopened] (CLOUDSTACK-5529) Users/Accounts created through the API are not displayed in the UI after the Ldap integration is done.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti reopened CLOUDSTACK-5529: -- I can still reproduce this issue in the latest build.The api call used is as below http://10.147.38.142:8096/client/api?command=createUser&account=admin&email=fchri...@royalnavy.mod.uk&firstname=Fletcher&lastname=Christian&password=pass&username=fchristi1 The Db details are as follows mysql> select * from user where username='fchristi1'\G *** 1. row *** id: 11 uuid: a38409ab-24d0-4522-abbb-96f7f523114a username: fchristi1 password: /4ND5DnRIgM0SjkPIt93puXxSsl08a+/ylVjE83y3AU=:ah1zExG8jyLUYmAYUR69DZXpgmkLVDzWXq7XyhXFXUI= account_id: 2 firstname: Fletcher lastname: Christian email: fchri...@royalnavy.mod.uk state: enabled api_key: NULL secret_key: NULL created: 2013-12-18 15:57:05 removed: NULL timezone: NULL registration_token: NULL is_registered: 0 incorrect_login_attempts: 0 default: 0 1 row in set (0.00 sec) But the user is not displayed in the UI will attach the screen shot. > Users/Accounts created through the API are not displayed in the UI after the > Ldap integration is done. > -- > > Key: CLOUDSTACK-5529 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5529 > 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: Rajani Karuturi >Priority: Critical > Fix For: 4.3.0 > > > Created a CS setup and integrated the same with an Ldap server and tried to > import some users from the Ldapthe users in the Ldap are imported > successfully,and when i created a USer through the API call the user is > created successfully,but the user is not displyed in the UI .When checked in > the DB the user is listed. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (CLOUDSTACK-5529) Users/Accounts created through the API are not displayed in the UI after the Ldap integration is done.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti updated CLOUDSTACK-5529: - Attachment: User.jpg The user fchristi1 is not seen in the screen > Users/Accounts created through the API are not displayed in the UI after the > Ldap integration is done. > -- > > Key: CLOUDSTACK-5529 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5529 > 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: Rajani Karuturi >Priority: Critical > Fix For: 4.3.0 > > Attachments: User.jpg > > > Created a CS setup and integrated the same with an Ldap server and tried to > import some users from the Ldapthe users in the Ldap are imported > successfully,and when i created a USer through the API call the user is > created successfully,but the user is not displyed in the UI .When checked in > the DB the user is listed. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Comment Edited] (CLOUDSTACK-5529) Users/Accounts created through the API are not displayed in the UI after the Ldap integration is done.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13851570#comment-13851570 ] Kiran Koneti edited comment on CLOUDSTACK-5529 at 12/18/13 10:54 AM: - I can still reproduce this issue in the latest build.The api call used is as below http://10.147.38.142:8096/client/api?command=createUser&account=admin&email=fchri...@royalnavy.mod.uk&firstname=Fletcher&lastname=Christian&password=pass&username=fchristi1 The Db details are as follows mysql> select * from user where username='fchristi1'\G id: 11 uuid: a38409ab-24d0-4522-abbb-96f7f523114a username: fchristi1 password: /4ND5DnRIgM0SjkPIt93puXxSsl08a+/ylVjE83y3AU=:ah1zExG8jyLUYmAYUR69DZXpgmkLVDzWXq7XyhXFXUI= account_id: 2 firstname: Fletcher lastname: Christian email: fchri...@royalnavy.mod.uk state: enabled api_key: NULL secret_key: NULL created: 2013-12-18 15:57:05 removed: NULL timezone: NULL registration_token: NULL is_registered: 0 incorrect_login_attempts: 0 default: 0 1 row in set (0.00 sec) But the user is not displayed in the UI will attach the screen shot. was (Author: kiran_koneti): I can still reproduce this issue in the latest build.The api call used is as below http://10.147.38.142:8096/client/api?command=createUser&account=admin&email=fchri...@royalnavy.mod.uk&firstname=Fletcher&lastname=Christian&password=pass&username=fchristi1 The Db details are as follows mysql> select * from user where username='fchristi1'\G *** 1. row *** id: 11 uuid: a38409ab-24d0-4522-abbb-96f7f523114a username: fchristi1 password: /4ND5DnRIgM0SjkPIt93puXxSsl08a+/ylVjE83y3AU=:ah1zExG8jyLUYmAYUR69DZXpgmkLVDzWXq7XyhXFXUI= account_id: 2 firstname: Fletcher lastname: Christian email: fchri...@royalnavy.mod.uk state: enabled api_key: NULL secret_key: NULL created: 2013-12-18 15:57:05 removed: NULL timezone: NULL registration_token: NULL is_registered: 0 incorrect_login_attempts: 0 default: 0 1 row in set (0.00 sec) But the user is not displayed in the UI will attach the screen shot. > Users/Accounts created through the API are not displayed in the UI after the > Ldap integration is done. > -- > > Key: CLOUDSTACK-5529 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5529 > 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: Rajani Karuturi >Priority: Critical > Fix For: 4.3.0 > > Attachments: User.jpg > > > Created a CS setup and integrated the same with an Ldap server and tried to > import some users from the Ldapthe users in the Ldap are imported > successfully,and when i created a USer through the API call the user is > created successfully,but the user is not displyed in the UI .When checked in > the DB the user is listed. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Comment Edited] (CLOUDSTACK-5529) Users/Accounts created through the API are not displayed in the UI after the Ldap integration is done.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13851570#comment-13851570 ] Kiran Koneti edited comment on CLOUDSTACK-5529 at 12/18/13 10:53 AM: - I can still reproduce this issue in the latest build.The api call used is as below http://10.147.38.142:8096/client/api?command=createUser&account=admin&email=fchri...@royalnavy.mod.uk&firstname=Fletcher&lastname=Christian&password=pass&username=fchristi1 The Db details are as follows mysql> select * from user where username='fchristi1'\G *** 1. row *** id: 11 uuid: a38409ab-24d0-4522-abbb-96f7f523114a username: fchristi1 password: /4ND5DnRIgM0SjkPIt93puXxSsl08a+/ylVjE83y3AU=:ah1zExG8jyLUYmAYUR69DZXpgmkLVDzWXq7XyhXFXUI= account_id: 2 firstname: Fletcher lastname: Christian email: fchri...@royalnavy.mod.uk state: enabled api_key: NULL secret_key: NULL created: 2013-12-18 15:57:05 removed: NULL timezone: NULL registration_token: NULL is_registered: 0 incorrect_login_attempts: 0 default: 0 1 row in set (0.00 sec) But the user is not displayed in the UI will attach the screen shot. was (Author: kiran_koneti): I can still reproduce this issue in the latest build.The api call used is as below http://10.147.38.142:8096/client/api?command=createUser&account=admin&email=fchri...@royalnavy.mod.uk&firstname=Fletcher&lastname=Christian&password=pass&username=fchristi1 The Db details are as follows mysql> select * from user where username='fchristi1'\G *** 1. row *** id: 11 uuid: a38409ab-24d0-4522-abbb-96f7f523114a username: fchristi1 password: /4ND5DnRIgM0SjkPIt93puXxSsl08a+/ylVjE83y3AU=:ah1zExG8jyLUYmAYUR69DZXpgmkLVDzWXq7XyhXFXUI= account_id: 2 firstname: Fletcher lastname: Christian email: fchri...@royalnavy.mod.uk state: enabled api_key: NULL secret_key: NULL created: 2013-12-18 15:57:05 removed: NULL timezone: NULL registration_token: NULL is_registered: 0 incorrect_login_attempts: 0 default: 0 1 row in set (0.00 sec) But the user is not displayed in the UI will attach the screen shot. > Users/Accounts created through the API are not displayed in the UI after the > Ldap integration is done. > -- > > Key: CLOUDSTACK-5529 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5529 > 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: Rajani Karuturi >Priority: Critical > Fix For: 4.3.0 > > Attachments: User.jpg > > > Created a CS setup and integrated the same with an Ldap server and tried to > import some users from the Ldapthe users in the Ldap are imported > successfully,and when i created a USer through the API call the user is > created successfully,but the user is not displyed in the UI .When checked in > the DB the user is listed. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Closed] (CLOUDSTACK-5200) UI displays wrong values for the socket information and number of hosts.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-5200. This works fine with the new build > UI displays wrong values for the socket information and number of hosts. > > > Key: CLOUDSTACK-5200 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5200 > 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: Kiran Koneti >Assignee: Jessica Wang >Priority: Critical > Fix For: 4.3.0 > > Attachments: Socket_info.jpg > > > In the infrastructure tab view of the CS when we click the Sockets tab it > always displays a constant value of 3 for all the hosts and unknown under the > sockets value.In my current setup i have only one Xen server with single > socket but it still shows the same value. > The api output displays the correct value but the UI has the different value. > The API output is as below: > " > 1 > > b7d32c8c-9872-4b74-864b-665e65d46442 > Rack1Pod1Host9 > Up > Routing > 10.147.40.9 > ff337566-43f4-4caf-99a4-79808d3bdef1 > Z1 > 72a86797-7aa8-413d-9a81-f52b0907cf28 > Pod1 > 4.3.0-SNAPSHOT > XenServer > 1 > 4 > 2394 > 0% > 0.06% > 9576.0 > 3976 > 24403 > 16001266176 > 2550136832 > 3687684 > > xen-3.0-x86_64 , xen-3.0-x86_32p , hvm-3.0-x86_32 , hvm-3.0-x86_32p , > hvm-3.0-x86_64 > > 1970-01-16T21:08:33+0530 > 7614406590488 > 83d22057-ddaf-44f3-a90b-c64237d49521 > C1 > CloudManaged > false > 2013-11-18T15:34:31+0530 > > AgentConnected; HostDown; AgentDisconnected; PingTimeout; > StartAgentRebalance; ShutdownRequested; Remove; ManagementServerDown; Ping > > Enabled > 6.2.0 > false > > " > Attaching the UI screen shot for the same. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Closed] (CLOUDSTACK-5222) UI:Sockets: Sockets feature does not report data correctly
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kiran Koneti closed CLOUDSTACK-5222.
This works fine with the new build
> UI:Sockets: Sockets feature does not report data correctly
> --
>
> Key: CLOUDSTACK-5222
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5222
> 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: 4.3.0
>Reporter: Parth Jagirdar
>Assignee: Jessica Wang
>Priority: Critical
> Fix For: 4.3.0
>
>
> Hosts listed on UI for each hyper visor type is not correct.
> also Sockets are listed as unknown.
> listHosts API is fired 7 times.
> Please refer to screen.
> http://10.223.49.195:8080/client/api?command=listHosts&response=json&sessionkey=lT1Ho7%2FPALRbpGLmZIAPvJsT05M%3D&hypervisortype=LXC&page=1&pagesize=20&_=1384985524749
> { "listhostsresponse" : { "count":7 ,"host" : [
> {"id":"3374c430-0369-4711-b668-f83c8a4ae1ef","name":"v-83-QA","state":"Up","type":"ConsoleProxy","ipaddress":"10.223.50.96","zoneid":"98a9e393-508c-497b-bbad-e62acfaebecd","zonename":"Adv-KVM-Zone1","podid":"7e31616e-beb8-430b-a7ef-180f7205eb33","podname":"POD01","version":"4.3.0-SNAPSHOT","lastpinged":"1970-01-16T07:41:17-0800","managementserverid":29066118877352,"islocalstorageactive":false,"created":"2013-11-19T23:37:24-0800","events":"StartAgentRebalance;
> AgentConnected; ShutdownRequested; Remove; Ping; AgentDisconnected;
> PingTimeout; ManagementServerDown; HostDown","resourcestate":"Enabled"},
> {"id":"28db1c98-fe41-4c24-add7-083f31784918","name":"s-82-QA","state":"Up","type":"SecondaryStorageVM","ipaddress":"10.223.50.92","zoneid":"98a9e393-508c-497b-bbad-e62acfaebecd","zonename":"Adv-KVM-Zone1","podid":"7e31616e-beb8-430b-a7ef-180f7205eb33","podname":"POD01","version":"4.3.0-SNAPSHOT","lastpinged":"1970-01-16T07:41:41-0800","managementserverid":29066118877352,"islocalstorageactive":false,"created":"2013-11-19T23:34:35-0800","events":"StartAgentRebalance;
> AgentConnected; ShutdownRequested; Remove; Ping; AgentDisconnected;
> PingTimeout; ManagementServerDown; HostDown","resourcestate":"Enabled"},
> {"id":"11825ddb-b469-4e83-a12a-4f395b479f5b","name":"s-4-VM","state":"Up","disconnected":"2013-11-19T22:37:23-0800","type":"SecondaryStorageVM","ipaddress":"10.223.49.140","zoneid":"53fec071-f7f0-4fd0-ae2f-4c86b7d751ce","zonename":"Adv-KVM-Zone2","podid":"e57ed7ec-4df0-4a64-86bd-5456fd93b7bc","podname":"POD02","version":"4.3.0-SNAPSHOT","lastpinged":"1970-01-16T07:41:10-0800","managementserverid":29066118877352,"islocalstorageactive":false,"created":"2013-11-19T22:31:41-0800","events":"StartAgentRebalance;
> AgentConnected; ShutdownRequested; Remove; Ping; AgentDisconnected;
> PingTimeout; ManagementServerDown; HostDown","resourcestate":"Enabled"},
> {"id":"4d44a45b-f1db-4e57-bdce-abc469b55bba","name":"v-3-VM","state":"Up","disconnected":"2013-11-19T22:37:23-0800","type":"ConsoleProxy","ipaddress":"10.223.49.178","zoneid":"53fec071-f7f0-4fd0-ae2f-4c86b7d751ce","zonename":"Adv-KVM-Zone2","podid":"e57ed7ec-4df0-4a64-86bd-5456fd93b7bc","podname":"POD02","version":"4.3.0-SNAPSHOT","lastpinged":"1970-01-16T07:41:10-0800","managementserverid":29066118877352,"islocalstorageactive":false,"created":"2013-11-19T22:31:31-0800","events":"StartAgentRebalance;
> AgentConnected; ShutdownRequested; Remove; Ping; AgentDisconnected;
> PingTimeout; ManagementServerDown; HostDown","resourcestate":"Enabled"},
> {"id":"eb6895a1-f255-41ed-94d6-12c0bf4b8dca","name":"Rack2Host7.lab.vmops.com","state":"Up","disconnected":"2013-11-19T22:37:23-0800","type":"Routing","ipaddress":"10.223.49.130","zoneid":"53fec071-f7f0-4fd0-ae2f-4c86b7d751ce","zonename":"Adv-KVM-Zone2","podid":"e57ed7ec-4df0-4a64-86bd-5456fd93b7bc","podname":"POD02","version":"4.3.0-SNAPSHOT","hypervisor":"KVM","cpusockets":1,"cpunumber":4,"cpuspeed":2261,"cpuallocated":"0%","cpuused":"0.5%","cpuwithoverprovisioning":"9044.0","networkkbsread":632234,"networkkbswrite":828621,"memorytotal":16713302016,"memoryallocated":1342177280,"memoryused":1210920,"capabilities":"hvm,snapshot","lastpinged":"1970-01-16T07:41:10-0800","managementserverid":29066118877352,"clusterid":"8a9bff62-4f8e-42c8-a4d4-ee65ffafe4dd","clustername":"KVM_Cluster2","clustertype":"CloudManaged","islocalstorageactive":false,"created":"2013-11-19T22:28:48-0800","events":"StartAgentRebalance;
> AgentConnected; ShutdownRequested; Remove; Ping; AgentDisconnected;
> PingTimeout; ManagementServerDown;
> HostDown","resourcestate":"Enabled","hahost":false},
> {"id":"a9830098-1cbc-4873-858d-c23b1ca1f823","name":"Rack2Host12.lab.vmops.com","state":"Up","disconnected":"2013-11-19T2
[jira] [Closed] (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:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-5434. This works fine with the new build > 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] [Closed] (CLOUDSTACK-5375) ldap:ldapconfig and ldapRemove api's are not working
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-5375. This is working fine with the new build > ldap:ldapconfig and ldapRemove api's are not working > > > Key: CLOUDSTACK-5375 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5375 > 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: sadhu suresh >Assignee: Rajani Karuturi >Priority: Critical > Fix For: Future, 4.3.0 > > > In 4.3 When ldapConfig and ldapRemove APIs are fired, it shows error as > "Unknown API command". API compatibility is broken due to adding of new API. > expected result:existing API 's should work. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Closed] (CLOUDSTACK-5529) Users/Accounts created through the API are not displayed in the UI after the Ldap integration is done.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-5529. closing this as we can see the users under the users tab of the particular account. > Users/Accounts created through the API are not displayed in the UI after the > Ldap integration is done. > -- > > Key: CLOUDSTACK-5529 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5529 > 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: Rajani Karuturi >Priority: Critical > Fix For: 4.3.0 > > Attachments: User.jpg > > > Created a CS setup and integrated the same with an Ldap server and tried to > import some users from the Ldapthe users in the Ldap are imported > successfully,and when i created a USer through the API call the user is > created successfully,but the user is not displyed in the UI .When checked in > the DB the user is listed. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Closed] (CLOUDSTACK-4938) Add account password confirmation broken
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-4938. now the validation is fine for the confirm password it is working fine hence closing the defect. > 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] [Closed] (CLOUDSTACK-5188) Password reset of vm on Xen and VMware does not work on first reboot
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-5188. Verified this in the Xen and Vmware setup both are working fine in the latest 4.3 hence closing the defect. > Password reset of vm on Xen and VMware does not work on first reboot > > > Key: CLOUDSTACK-5188 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5188 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Test >Affects Versions: 4.2.1, 4.3.0 > Environment: VMware and Xen >Reporter: Girish Shilamkar >Assignee: Jayapal Reddy >Priority: Blocker > > The issue was uncovered as test_vm_passwdenabled.py was consistently failing > on Vmware and Xen. Note this issue is not seen on KVM. > Procedure: > 1. Create a vm > 2. Enable password management. In vm do following: > $ cd /etc/init.d > $ wget http://people.apache.org/~tsp/cloud-set-guest-password > $ chmod +x /etc/init.d/cloud-set-guest-password > $ chkconfig --add cloud-set-guest-password > 3. Stop vm > 4. Create template from vm's volume > 5. Delete vm > 6. Create new vm from template created in step 4 > 7. Stop vm > 8. Reset password > 9. Start vm > 10. Ssh to vm using password obtained in step 8 > The ssh to vm using new password will fail but ssh with old password works > Now if vm is stopped and started again, the new password will work. Thus > password is reset only on the second boot. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Created] (CLOUDSTACK-5591) Public network is not reachable by the System Vm's.
Kiran Koneti created CLOUDSTACK-5591: Summary: Public network is not reachable by the System Vm's. Key: CLOUDSTACK-5591 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5591 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 Priority: Blocker Fix For: 4.3.0 The setup details are as follows: 1)Installed the CS setup and changed the global setting to allow the download from the internal sites. 2)Created a Advanced Zone setup with Vmware 5.5 where the system Vm's came up. 3)Then added one more cluster for the KVm and added a KVM host. 4)After adding the KVM ost the system Vm template for the KVM was not ready and it shows as connection timed out. 5)Then logged into the SSVM and tried to ping the public network then the network was not reachable,even the default gateway was not pingable. 6)When stopped the IP tables the gateway was pingable. 7)When tried to check the arp of the gw using "arping the gatewayIP" it says the eth0 is down and when eth0 is made up the ping was successful and the public network was reachable. 8)Then tried to restart the SSVM again the situation is same that the public network is not reachable. 9)If we leave the stup for longer time without making any changes the Public network will be reachable and when rebooted again the network will not be reached again. The Iptables details are as below: "iptables -L -nv Chain INPUT (policy DROP 4 packets, 312 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT tcp -- eth2 * 0.0.0.0/00.0.0.0/0 state NEW tcp dpt:443 0 0 ACCEPT tcp -- eth2 * 0.0.0.0/00.0.0.0/0 state NEW tcp dpt:80 160 ACCEPT tcp -- eth1 * 0.0.0.0/00.0.0.0/0 state NEW tcp dpt:3922 0 0 ACCEPT all -- eth0 * 0.0.0.0/00.0.0.0/0 state RELATED,ESTABLISHED 547 95190 ACCEPT all -- eth1 * 0.0.0.0/00.0.0.0/0 state RELATED,ESTABLISHED 2 262 ACCEPT all -- eth2 * 0.0.0.0/00.0.0.0/0 state RELATED,ESTABLISHED 0 0 ACCEPT all -- eth3 * 0.0.0.0/00.0.0.0/0 state RELATED,ESTABLISHED 10 588 ACCEPT all -- lo * 0.0.0.0/00.0.0.0/0 0 0 DROP icmp -- * * 0.0.0.0/00.0.0.0/0 icmptype 13 0 0 ACCEPT icmp -- * * 0.0.0.0/00.0.0.0/0 0 0 ACCEPT tcp -- eth1 * 0.0.0.0/00.0.0.0/0 state NEW tcp dpt:3922 Chain FORWARD (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination Chain OUTPUT (policy ACCEPT 493 packets, 76135 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT tcp -- * eth10.0.0.0/0 10.147.28.0/24 state NEW tcp 0 0 REJECT tcp -- * eth10.0.0.0/00.0.0.0/0 state NEW tcp dpt:80 reject-with icmp-port-unreachable 0 0 REJECT tcp -- * eth10.0.0.0/00.0.0.0/0 state NEW tcp dpt:443 reject-with icmp-port-unreachable Chain HTTP (0 references) pkts bytes target prot opt in out source destination" The arping request is as below: arping 10.147.X.X Interface "eth0" is down -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-5591) Public network is not reachable by the System Vm's.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13853856#comment-13853856 ] Kiran Koneti commented on CLOUDSTACK-5591: -- Used 64 bit systemVM template for the VMware while creating the Zone. > Public network is not reachable by the System Vm's. > --- > > Key: CLOUDSTACK-5591 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5591 > 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 >Priority: Blocker > Fix For: 4.3.0 > > > The setup details are as follows: > 1)Installed the CS setup and changed the global setting to allow the download > from the internal sites. > 2)Created a Advanced Zone setup with Vmware 5.5 where the system Vm's came up. > 3)Then added one more cluster for the KVm and added a KVM host. > 4)After adding the KVM ost the system Vm template for the KVM was not ready > and it shows as connection timed out. > 5)Then logged into the SSVM and tried to ping the public network then the > network was not reachable,even the default gateway was not pingable. > 6)When stopped the IP tables the gateway was pingable. > 7)When tried to check the arp of the gw using "arping the gatewayIP" it says > the eth0 is down and when eth0 is made up the ping was successful and the > public network was reachable. > 8)Then tried to restart the SSVM again the situation is same that the public > network is not reachable. > 9)If we leave the stup for longer time without making any changes the Public > network will be reachable and when rebooted again the network will not be > reached again. > The Iptables details are as below: > "iptables -L -nv > Chain INPUT (policy DROP 4 packets, 312 bytes) > pkts bytes target prot opt in out source > destination > 0 0 ACCEPT tcp -- eth2 * 0.0.0.0/00.0.0.0/0 >state NEW tcp dpt:443 > 0 0 ACCEPT tcp -- eth2 * 0.0.0.0/00.0.0.0/0 >state NEW tcp dpt:80 > 160 ACCEPT tcp -- eth1 * 0.0.0.0/00.0.0.0/0 >state NEW tcp dpt:3922 > 0 0 ACCEPT all -- eth0 * 0.0.0.0/00.0.0.0/0 >state RELATED,ESTABLISHED > 547 95190 ACCEPT all -- eth1 * 0.0.0.0/00.0.0.0/0 >state RELATED,ESTABLISHED > 2 262 ACCEPT all -- eth2 * 0.0.0.0/00.0.0.0/0 >state RELATED,ESTABLISHED > 0 0 ACCEPT all -- eth3 * 0.0.0.0/00.0.0.0/0 >state RELATED,ESTABLISHED >10 588 ACCEPT all -- lo * 0.0.0.0/00.0.0.0/0 > 0 0 DROP icmp -- * * 0.0.0.0/00.0.0.0/0 >icmptype 13 > 0 0 ACCEPT icmp -- * * 0.0.0.0/00.0.0.0/0 > 0 0 ACCEPT tcp -- eth1 * 0.0.0.0/00.0.0.0/0 >state NEW tcp dpt:3922 > Chain FORWARD (policy DROP 0 packets, 0 bytes) > pkts bytes target prot opt in out source > destination > Chain OUTPUT (policy ACCEPT 493 packets, 76135 bytes) > pkts bytes target prot opt in out source > destination > 0 0 ACCEPT tcp -- * eth10.0.0.0/0 > 10.147.28.0/24 state NEW tcp > 0 0 REJECT tcp -- * eth10.0.0.0/00.0.0.0/0 >state NEW tcp dpt:80 reject-with icmp-port-unreachable > 0 0 REJECT tcp -- * eth10.0.0.0/00.0.0.0/0 >state NEW tcp dpt:443 reject-with icmp-port-unreachable > Chain HTTP (0 references) > pkts bytes target prot opt in out source > destination" > The arping request is as below: > arping 10.147.X.X > Interface "eth0" is down -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-5527) [UI] : No option to create non-Ldap users through the UI when the LDAP integration is done.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13855400#comment-13855400 ] Kiran Koneti commented on CLOUDSTACK-5527: -- Jessica/rajani, I have sent the details in the mail with the Ldap Details. > [UI] : No option to create non-Ldap users through the UI when the LDAP > integration is done. > --- > > Key: CLOUDSTACK-5527 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5527 > 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: Kiran Koneti >Assignee: Kiran Koneti >Priority: Critical > Fix For: 4.3.0 > > Attachments: jessica_2013_12_20_AccountsPage_AddAccountButton.PNG > > > Created a CS setup and integrated the same with an Ldap server and tried to > import some users from the Ldapthe users in the Ldap are imported > successfully,but there is no option to create non-ldap users in the UI. > Eg: if i want to create a User/account in the CS which is non Ldap user then > there is no option for that through the UI i can do it through the API call. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Reopened] (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 ] Kiran Koneti reopened CLOUDSTACK-5457: -- Observe this in the latest build(on 23rd dec). hence reopening this issue. > 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.5#6160)
[jira] [Closed] (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 ] Kiran Koneti closed CLOUDSTACK-5457. fixed in the latest version hence closing the defect > 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.5#6160)
[jira] [Updated] (CLOUDSTACK-5609) [DBHA]:UI hangs when the M1 goes down while creating the zone.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti updated CLOUDSTACK-5609: - Attachment: UIStruck.jpg > [DBHA]:UI hangs when the M1 goes down while creating the zone. > -- > > Key: CLOUDSTACK-5609 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5609 > 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 >Priority: Critical > Fix For: 4.3.0 > > Attachments: UIStruck.jpg > > > 1)Make a CS setup enabling the DBHA,and try to create a Zone say Z1. > 2)While the Zone creation is in progress disable the M1(master 1). > 3)The Zone creation fails as expected but the UI just hangs and doesn't pop > any error messages . > 4)We don't even have a cancel button to cancel the setup. > Expected Result:The UI should pop up an error message saying the Zone > creation failed as the M1 connection is lost. > Attaching the Screen shot. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5609) [DBHA]:UI hangs when the M1 goes down while creating the zone.
Kiran Koneti created CLOUDSTACK-5609: Summary: [DBHA]:UI hangs when the M1 goes down while creating the zone. Key: CLOUDSTACK-5609 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5609 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 Priority: Critical Fix For: 4.3.0 1)Make a CS setup enabling the DBHA,and try to create a Zone say Z1. 2)While the Zone creation is in progress disable the M1(master 1). 3)The Zone creation fails as expected but the UI just hangs and doesn't pop any error messages . 4)We don't even have a cancel button to cancel the setup. Expected Result:The UI should pop up an error message saying the Zone creation failed as the M1 connection is lost. Attaching the Screen shot. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5614) UI improvements for Report Sockets
Kiran Koneti created CLOUDSTACK-5614: Summary: UI improvements for Report Sockets Key: CLOUDSTACK-5614 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5614 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: Kiran Koneti Fix For: 4.3.0 The below mentioned improvements are requested for the report sockets. 1)UI Icon in the infrastructure tab. The current implementation of the Infrastructure tab is attached as screenshot InfraTab.jpg whcih shows that all the other tab links has some image in the box related to it ,So please add some image to the sockets which would make the UI look good. 2)number of sockets in the Sockets tab. The current implementation of number of sockets is attached as the screen shot Number_of_sockets.jpg in which the number of sockets for all the hosts is listed as 0 for the hosts which are not added and also not supported.in th egiven screenshot you can see the number of hypervisor hosts are 2 and the sockets number is 0.It is listed so because the number of sockets for the hyper-V is not yet implemented.So the number of sockets should be either N/A of just -(hyphen) for the hypervisors which we doesn't support. 3)Seperate List should be maintained for Xenserver 6.2 version and versions prior to that. We support the Report sockets only for the Xen 6.2 version and not for the versions prior to that.So we have to have 2 columns one for Xenserver 6.2 for which we can list number of hosts and number of sockets and other one saying just Xenserver where we report only the number of hosts and the number of sockets should be either N/A or -(hyphen). 4)Report the socket information in the Host information UI also. When we navigate to the Infrastructure-->Hosts -->(hostname/IP) for the host details we don't have a UI column for the Number of sockets this info is displayed in the API output ,So fetch the data fro the api and display it in the UI. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5614) UI improvements for Report Sockets
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti updated CLOUDSTACK-5614: - Attachment: Number_of_sockets.jpg Number_of_sockets.jpg > UI improvements for Report Sockets > -- > > Key: CLOUDSTACK-5614 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5614 > 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: Kiran Koneti > Fix For: 4.3.0 > > Attachments: Number_of_sockets.jpg > > > The below mentioned improvements are requested for the report sockets. > 1)UI Icon in the infrastructure tab. > The current implementation of the Infrastructure tab is attached as > screenshot InfraTab.jpg whcih shows that all the other tab links has some > image in the box related to it ,So please add some image to the sockets which > would make the UI look good. > 2)number of sockets in the Sockets tab. > The current implementation of number of sockets is attached as the screen > shot Number_of_sockets.jpg in which the number of sockets for all the hosts > is listed as 0 for the hosts which are not added and also not supported.in th > egiven screenshot you can see the number of hypervisor hosts are 2 and the > sockets number is 0.It is listed so because the number of sockets for the > hyper-V is not yet implemented.So the number of sockets should be either N/A > of just -(hyphen) for the hypervisors which we doesn't support. > 3)Seperate List should be maintained for Xenserver 6.2 version and versions > prior to that. > We support the Report sockets only for the Xen 6.2 version and not for the > versions prior to that.So we have to have 2 columns one for Xenserver 6.2 for > which we can list number of hosts and number of sockets and other one saying > just Xenserver where we report only the number of hosts and the number of > sockets should be either N/A or -(hyphen). > 4)Report the socket information in the Host information UI also. > When we navigate to the Infrastructure-->Hosts -->(hostname/IP) for the host > details we don't have a UI column for the Number of sockets this info is > displayed in the API output ,So fetch the data fro the api and display it in > the UI. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5614) UI improvements for Report Sockets
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti updated CLOUDSTACK-5614: - Attachment: (was: Number_of_sockets.jpg) > UI improvements for Report Sockets > -- > > Key: CLOUDSTACK-5614 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5614 > 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: Kiran Koneti > Fix For: 4.3.0 > > Attachments: Number_of_sockets.jpg > > > The below mentioned improvements are requested for the report sockets. > 1)UI Icon in the infrastructure tab. > The current implementation of the Infrastructure tab is attached as > screenshot InfraTab.jpg whcih shows that all the other tab links has some > image in the box related to it ,So please add some image to the sockets which > would make the UI look good. > 2)number of sockets in the Sockets tab. > The current implementation of number of sockets is attached as the screen > shot Number_of_sockets.jpg in which the number of sockets for all the hosts > is listed as 0 for the hosts which are not added and also not supported.in th > egiven screenshot you can see the number of hypervisor hosts are 2 and the > sockets number is 0.It is listed so because the number of sockets for the > hyper-V is not yet implemented.So the number of sockets should be either N/A > of just -(hyphen) for the hypervisors which we doesn't support. > 3)Seperate List should be maintained for Xenserver 6.2 version and versions > prior to that. > We support the Report sockets only for the Xen 6.2 version and not for the > versions prior to that.So we have to have 2 columns one for Xenserver 6.2 for > which we can list number of hosts and number of sockets and other one saying > just Xenserver where we report only the number of hosts and the number of > sockets should be either N/A or -(hyphen). > 4)Report the socket information in the Host information UI also. > When we navigate to the Infrastructure-->Hosts -->(hostname/IP) for the host > details we don't have a UI column for the Number of sockets this info is > displayed in the API output ,So fetch the data fro the api and display it in > the UI. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5614) UI improvements for Report Sockets
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti updated CLOUDSTACK-5614: - Attachment: InfraTab.jpg > UI improvements for Report Sockets > -- > > Key: CLOUDSTACK-5614 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5614 > 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: Kiran Koneti > Fix For: 4.3.0 > > Attachments: InfraTab.jpg, Number_of_sockets.jpg > > > The below mentioned improvements are requested for the report sockets. > 1)UI Icon in the infrastructure tab. > The current implementation of the Infrastructure tab is attached as > screenshot InfraTab.jpg whcih shows that all the other tab links has some > image in the box related to it ,So please add some image to the sockets which > would make the UI look good. > 2)number of sockets in the Sockets tab. > The current implementation of number of sockets is attached as the screen > shot Number_of_sockets.jpg in which the number of sockets for all the hosts > is listed as 0 for the hosts which are not added and also not supported.in th > egiven screenshot you can see the number of hypervisor hosts are 2 and the > sockets number is 0.It is listed so because the number of sockets for the > hyper-V is not yet implemented.So the number of sockets should be either N/A > of just -(hyphen) for the hypervisors which we doesn't support. > 3)Seperate List should be maintained for Xenserver 6.2 version and versions > prior to that. > We support the Report sockets only for the Xen 6.2 version and not for the > versions prior to that.So we have to have 2 columns one for Xenserver 6.2 for > which we can list number of hosts and number of sockets and other one saying > just Xenserver where we report only the number of hosts and the number of > sockets should be either N/A or -(hyphen). > 4)Report the socket information in the Host information UI also. > When we navigate to the Infrastructure-->Hosts -->(hostname/IP) for the host > details we don't have a UI column for the Number of sockets this info is > displayed in the API output ,So fetch the data fro the api and display it in > the UI. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (CLOUDSTACK-5207) jdbc.exceptions are observed when both Master 1 and master 2 goes down and comes back.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-5207. Closing the issue as the Design is changed that when both the DB servers are down the CS goes to shutdown. > jdbc.exceptions are observed when both Master 1 and master 2 goes down and > comes back. > -- > > Key: CLOUDSTACK-5207 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5207 > 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: 4.3.0 > > > 1)I have created a replication db with 2 masters say M1 and M2. > 2)The CS setup came up and both the db's are in sync. > 3)now i made the M1 down and the M2 was made the master and the operations of > CS were normal. > 4)Now i made the M2 also down and the db of the CS could not be accessed. > 5)Later i made the M1 up and then M2.The data sync happened properly but > there is an error message which is constantly shown in the MS log and it is > as below: > "2013-11-20 11:34:50,938 ERROR [c.c.u.d.ConnectionConcierge] > (ConnectionConcierge-1:ctx-7c449525) Unable to keep the db connection for > LockMaster1 > com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: No > operations allowed after connection closed. Connection closed after > inability to pick valid new connection during fail-over. > at sun.reflect.GeneratedConstructorAccessor25.newInstance(Unknown > Source) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:532) > at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) > at com.mysql.jdbc.Util.getInstance(Util.java:386) > at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1014) > at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:988) > at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:974) > at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:919) > at > com.mysql.jdbc.LoadBalancingConnectionProxy.invoke(LoadBalancingConnectionProxy.java:532) > at > com.mysql.jdbc.FailoverConnectionProxy.invoke(FailoverConnectionProxy.java:136) > at $Proxy19.prepareStatement(Unknown Source) > at > org.apache.commons.dbcp.DelegatingConnection.prepareStatement(DelegatingConnection.java:281) > at > org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.prepareStatement(PoolingDataSource.java:313) > at > com.cloud.utils.db.ConnectionConcierge$ConnectionConciergeManager.testValidity(ConnectionConcierge.java:148) > at > com.cloud.utils.db.ConnectionConcierge$ConnectionConciergeManager$1.runInContext(ConnectionConcierge.java:211) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) > 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)" -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (CLOUDSTACK-5226) CS never goes down when both M1 and M2 are down in case of DB HA enabled.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-5226. Not reproduced in the latest builds hence closing the issue. > CS never goes down when both M1 and M2 are down in case of DB HA enabled. > - > > Key: CLOUDSTACK-5226 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5226 > 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: 4.3.0 > > > 1)I have created a DB replication with two masters M1 and M2 > 2)Have enabled the parameter db.ha.enabled=true and then made CS setup is up > with the db replication. > 3)Made the M1 down initially and the M2 down. > 4) CS tries to reconnect to the databases and never goes down. > 5)Tried with the db.ha.enabled=false and then made the M1 down. > 6)The CS goes to shutdown immediately. > Expected result is: > CS should retry for the DB's to come up for some fixed time(say 10 mins) and > then should go down. May be we need to add a parameter defining the number of > retries or number of secs to wait for either of Db's to come up. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5616) [DBHA]:There is no way to know to which DB is the CS writing in the case of DBHA.
Kiran Koneti created CLOUDSTACK-5616: Summary: [DBHA]:There is no way to know to which DB is the CS writing in the case of DBHA. Key: CLOUDSTACK-5616 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5616 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 Priority: Critical Fix For: 4.3.0 At any instance of time we never know to which database (either M1 or M2) is the CS writing the db changes changes. This creates some problems at the customer environment like 1)The customer doesn't have chance to go for maintenance or manual do a switch over from one db to other if he has some network maintenance to perform. 2)There is no chance to check whether the db switch over has happened from the slave to master after the db.cloud.secondsBeforeRetryMaster interval if the master comes back by this time. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5677) When split brain ocuurs DB replication fails in case of HA Enabled.
Kiran Koneti created CLOUDSTACK-5677: Summary: When split brain ocuurs DB replication fails in case of HA Enabled. Key: CLOUDSTACK-5677 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5677 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 Priority: Critical Fix For: 4.3.0 Setup and issue details: 1)Created a CS setup with multiple MS say MS1 and MS2 with DBHA enabled. 2)Created a DB replication has 2 db servers say DB1 and DB2. 3)Initially the setup was in such a way that both MS1 and MS2 are talking to the DB1 and DB2 was acting as a slave. 4)Then Blocked the communication from the MS2 to DB1 using the IPtables. 5)now the split brain scenario is created in such a way that MS1 talks to DB1 and MS2 talks to DB2. 6)Now tried to create an affinity group in both the MS at the same time say Aff1 though the MS1 and Aff2 from the MS2. 7)The affinity groups are created in both the MS i.e Aff1 is created in the MS1 and updated in the DB1 and Aff2 is created in the MS2 and update in the DB2 and the replication is broke between both the DB servers and the slave status in both the DB servers is shown as below. Error message shown is "Could not execute Write_rows event on table cloud.affinity_group; Duplicate entry '1' for key 'PRIMARY', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log mysql-bin.65, end_log_pos 2785854" in DB2. "Could not execute Write_rows event on table cloud.affinity_group; Duplicate entry '1' for key 'PRIMARY', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log mysql-bin.30, end_log_pos 392" in DB1. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5679) No Error message is shown when the Connection from the MS is lost Db server in case of multiple MS and DB HA enabled.
Kiran Koneti created CLOUDSTACK-5679: Summary: No Error message is shown when the Connection from the MS is lost Db server in case of multiple MS and DB HA enabled. Key: CLOUDSTACK-5679 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5679 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 Priority: Critical Fix For: 4.3.0 Setup and issue details: 1)Created a CS setup with multiple MS say MS1 and MS2 with DBHA enabled. 2)Created a DB replication has 2 db servers say DB1 and DB2. 3)Initially the setup was in such a way that both MS1 and MS2 are talking to the DB1 and DB2 was acting as a slave. 4)Then Blocked the communication from the MS2 to DB1 using the IPtables. 5)When the connection is blocked from the MS2 to DB1 there is no error message shown in the logs and it simply switches to the DB2 . -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (CLOUDSTACK-5591) [VMWare][64-bit template]Public network is not reachable by the System Vm's.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-5591. Not reproduced in the latest build.Hence closing the defect. > [VMWare][64-bit template]Public network is not reachable by the System Vm's. > > > Key: CLOUDSTACK-5591 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5591 > 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: Jayapal Reddy >Priority: Blocker > Fix For: 4.3.0 > > > The setup details are as follows: > 1)Installed the CS setup and changed the global setting to allow the download > from the internal sites. > 2)Created a Advanced Zone setup with Vmware 5.5 where the system Vm's came up. > 3)Then added one more cluster for the KVm and added a KVM host. > 4)After adding the KVM ost the system Vm template for the KVM was not ready > and it shows as connection timed out. > 5)Then logged into the SSVM and tried to ping the public network then the > network was not reachable,even the default gateway was not pingable. > 6)When stopped the IP tables the gateway was pingable. > 7)When tried to check the arp of the gw using "arping the gatewayIP" it says > the eth0 is down and when eth0 is made up the ping was successful and the > public network was reachable. > 8)Then tried to restart the SSVM again the situation is same that the public > network is not reachable. > 9)If we leave the stup for longer time without making any changes the Public > network will be reachable and when rebooted again the network will not be > reached again. > The Iptables details are as below: > "iptables -L -nv > Chain INPUT (policy DROP 4 packets, 312 bytes) > pkts bytes target prot opt in out source > destination > 0 0 ACCEPT tcp -- eth2 * 0.0.0.0/00.0.0.0/0 >state NEW tcp dpt:443 > 0 0 ACCEPT tcp -- eth2 * 0.0.0.0/00.0.0.0/0 >state NEW tcp dpt:80 > 160 ACCEPT tcp -- eth1 * 0.0.0.0/00.0.0.0/0 >state NEW tcp dpt:3922 > 0 0 ACCEPT all -- eth0 * 0.0.0.0/00.0.0.0/0 >state RELATED,ESTABLISHED > 547 95190 ACCEPT all -- eth1 * 0.0.0.0/00.0.0.0/0 >state RELATED,ESTABLISHED > 2 262 ACCEPT all -- eth2 * 0.0.0.0/00.0.0.0/0 >state RELATED,ESTABLISHED > 0 0 ACCEPT all -- eth3 * 0.0.0.0/00.0.0.0/0 >state RELATED,ESTABLISHED >10 588 ACCEPT all -- lo * 0.0.0.0/00.0.0.0/0 > 0 0 DROP icmp -- * * 0.0.0.0/00.0.0.0/0 >icmptype 13 > 0 0 ACCEPT icmp -- * * 0.0.0.0/00.0.0.0/0 > 0 0 ACCEPT tcp -- eth1 * 0.0.0.0/00.0.0.0/0 >state NEW tcp dpt:3922 > Chain FORWARD (policy DROP 0 packets, 0 bytes) > pkts bytes target prot opt in out source > destination > Chain OUTPUT (policy ACCEPT 493 packets, 76135 bytes) > pkts bytes target prot opt in out source > destination > 0 0 ACCEPT tcp -- * eth10.0.0.0/0 > 10.147.28.0/24 state NEW tcp > 0 0 REJECT tcp -- * eth10.0.0.0/00.0.0.0/0 >state NEW tcp dpt:80 reject-with icmp-port-unreachable > 0 0 REJECT tcp -- * eth10.0.0.0/00.0.0.0/0 >state NEW tcp dpt:443 reject-with icmp-port-unreachable > Chain HTTP (0 references) > pkts bytes target prot opt in out source > destination" > The arping request is as below: > arping 10.147.X.X > Interface "eth0" is down -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5614) [UI] improvements for Report Sockets
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866373#comment-13866373 ] Kiran Koneti commented on CLOUDSTACK-5614: -- HI Jessica, The current support is for Xen 6.2 ,KVM ,Vmware and Hyper-V,for BareMetal OVM LXC it is not yet implemented. Regards, Kiran > [UI] improvements for Report Sockets > > > Key: CLOUDSTACK-5614 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5614 > 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: Kiran Koneti >Assignee: Kiran Koneti >Priority: Critical > Fix For: 4.3.0 > > Attachments: InfraTab.jpg, Number_of_sockets.jpg > > > The below mentioned improvements are requested for the report sockets. > 1)UI Icon in the infrastructure tab. > The current implementation of the Infrastructure tab is attached as > screenshot InfraTab.jpg whcih shows that all the other tab links has some > image in the box related to it ,So please add some image to the sockets which > would make the UI look good. > 2)number of sockets in the Sockets tab. > The current implementation of number of sockets is attached as the screen > shot Number_of_sockets.jpg in which the number of sockets for all the hosts > is listed as 0 for the hosts which are not added and also not supported.in th > egiven screenshot you can see the number of hypervisor hosts are 2 and the > sockets number is 0.It is listed so because the number of sockets for the > hyper-V is not yet implemented.So the number of sockets should be either N/A > of just -(hyphen) for the hypervisors which we doesn't support. > 3)Seperate List should be maintained for Xenserver 6.2 version and versions > prior to that. > We support the Report sockets only for the Xen 6.2 version and not for the > versions prior to that.So we have to have 2 columns one for Xenserver 6.2 for > which we can list number of hosts and number of sockets and other one saying > just Xenserver where we report only the number of hosts and the number of > sockets should be either N/A or -(hyphen). > 4)Report the socket information in the Host information UI also. > When we navigate to the Infrastructure-->Hosts -->(hostname/IP) for the host > details we don't have a UI column for the Number of sockets this info is > displayed in the API output ,So fetch the data fro the api and display it in > the UI. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-4105) Vnet's from Phisical network's table are getting deleted even the Vnet is used by Phisical network.
Kiran Koneti created CLOUDSTACK-4105: Summary: Vnet's from Phisical network's table are getting deleted even the Vnet is used by Phisical network. Key: CLOUDSTACK-4105 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4105 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.2.0 Reporter: Kiran Koneti Priority: Critical Fix For: 4.2.0 Steps are as follows: 1)Created a Advance zone setup using the Vnet range 1100-1109. 2)Once the setup is up created a VM which intern created a Physical network with the Vnet 1106. 3)Then Suing the API update Physical network I tried to remove the Vlan range 1100-1109. 4)The Vlan range from the physical network table is removed without any error message. 5)but the op_dc_vnet_alloc table still has the entry for the Vlan associated with the Phisical network. The below two tables show the db entries: The Physical network table in the before deleting mysql> select * from physical_network; +-+--+++---+---+---++-+-+-+ | id | uuid | name | data_center_id | vnet | speed | domain_id | broadcast_domain_range | state | created | removed | +-+--+++---+---+---++-+-+-+ | 200 | 85b82257-fc88-4eec-bf31-8995a6d27535 | Physical Network 1 | 1 | 1100-1109 | NULL | NULL | ZONE | Enabled | 2013-08-06 14:38:00 | NULL| +-+--+++---+---+---++-+-+-+ 1 row in set (0.00 sec) The Phisical network tabble after the deletion mysql> select * from physical_network; +-+--+++--+---+---++-+-+-+ | id | uuid | name | data_center_id | vnet | speed | domain_id | broadcast_domain_range | state | created | removed | +-+--+++--+---+---++-+-+-+ | 200 | 85b82257-fc88-4eec-bf31-8995a6d27535 | Physical Network 1 | 1 | NULL | NULL | NULL | ZONE | Enabled | 2013-08-06 14:38:00 | NULL| +-+--+++--+---+---++-+-+-+ 1 row in set (0.00 sec) The op_dc_vnet_alloc table after deletion mysql> select * from op_dc_vnet_alloc; ++--+-++++---+-+ | id | vnet | physical_network_id | data_center_id | reservation_id | account_id | taken | account_vnet_map_id | ++--+-++++---+-+ | 12 | 1106 | 200 | 1 | NULL | NULL | NULL |NULL | ++--+-++++---+-+ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-4105) Vnet's from Phisical network's table are getting deleted even the Vnet is used by Phisical network.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-4105. Verified this in the Latest build and it works fine hence closing this issue. The UI seems to have some issue so raising another issue for the UI. > Vnet's from Phisical network's table are getting deleted even the Vnet is > used by Phisical network. > --- > > Key: CLOUDSTACK-4105 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4105 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.2.0 >Reporter: Kiran Koneti >Assignee: Bharat Kumar >Priority: Critical > Fix For: 4.2.0 > > > Steps are as follows: > 1)Created a Advance zone setup using the Vnet range 1100-1109. > 2)Once the setup is up created a VM which intern created a Physical network > with the Vnet 1106. > 3)Then Suing the API update Physical network I tried to remove the Vlan range > 1100-1109. > 4)The Vlan range from the physical network table is removed without any error > message. > 5)but the op_dc_vnet_alloc table still has the entry for the Vlan associated > with the Phisical network. > The below two tables show the db entries: > The Physical network table in the before deleting > mysql> select * from physical_network; > +-+--+++---+---+---++-+-+-+ > | id | uuid | name | > data_center_id | vnet | speed | domain_id | broadcast_domain_range | > state | created | removed | > +-+--+++---+---+---++-+-+-+ > | 200 | 85b82257-fc88-4eec-bf31-8995a6d27535 | Physical Network 1 | >1 | 1100-1109 | NULL | NULL | ZONE | Enabled | > 2013-08-06 14:38:00 | NULL| > +-+--+++---+---+---++-+-+-+ > 1 row in set (0.00 sec) > The Phisical network tabble after the deletion > mysql> select * from physical_network; > +-+--+++--+---+---++-+-+-+ > | id | uuid | name | > data_center_id | vnet | speed | domain_id | broadcast_domain_range | state > | created | removed | > +-+--+++--+---+---++-+-+-+ > | 200 | 85b82257-fc88-4eec-bf31-8995a6d27535 | Physical Network 1 | >1 | NULL | NULL | NULL | ZONE | Enabled | > 2013-08-06 14:38:00 | NULL| > +-+--+++--+---+---++-+-+-+ > 1 row in set (0.00 sec) > The op_dc_vnet_alloc table after deletion > mysql> select * from op_dc_vnet_alloc; > ++--+-++++---+-+ > | id | vnet | physical_network_id | data_center_id | reservation_id | > account_id | taken | account_vnet_map_id | > ++--+-++++---+-+ > | 12 | 1106 | 200 | 1 | NULL | > NULL | NULL |NULL | > ++--+-++++---+-+ > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-4134) UI dosent fire the API with the Vlan values if the Vlan range is blank.
Kiran Koneti created CLOUDSTACK-4134: Summary: UI dosent fire the API with the Vlan values if the Vlan range is blank. Key: CLOUDSTACK-4134 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4134 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: Kiran Koneti Priority: Critical Fix For: 4.2.0 When we try to edit the Vlan range from the UI and give blank values in the Vlan range box and try to update the page the API fried doesn't have any Vlan details as it is blank in the UI. Eg: I tried the below scenario: 1)Created a setup with the Vlan range 1100-1109. 2)Then created a network where the Vlan 1101 is associated with the network. 3)Now I tried to edit the Vlan range and gave the blank value in the UI and clicked update. The API fired is as below "10.147.38.237:8080/client/api?command=updatePhysicalNetwork&response=json&sessionkey=RRxhiAqmggnl%2F5oBGHNTm3DMj0M%3D&id=2409aeac-789a-4430-a9b7-fab66eb4b85c&_=1375867127326" Here the Vlan details are not fired in the API. Then I tried to edit it by giving the value 1102-1109 and the API fired was as below: "http://10.147.38.237:8080/client/api?command=updatePhysicalNetwork&response=json&sessionkey=RRxhiAqmggnl%2F5oBGHNTm3DMj0M%3D&id=2409aeac-789a-4430-a9b7-fab66eb4b85c&vlan=1102-1109&_=1375867287606"; The API was fired currently with the Vlan values and there was a error message as below "physicalnetwork 200 has allocated vnets in the range 1100-1101 " the below is the expected behaviour and the same should happen when we try to update the UI with Blank details. Note: Even the UI doesn't popup with any error message the Vlan range is not getting deleted and we can see the same vlan range once we refresh the page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-2150) DB table entries of phisical network is not proper.Shows Duplicate entries.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-2150. This is working fine as per the latest changes made to the feature hence closing the defect. > DB table entries of phisical network is not proper.Shows Duplicate entries. > - > > Key: CLOUDSTACK-2150 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2150 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 >Reporter: Kiran Koneti >Assignee: Bharat Kumar > Fix For: 4.2.0 > > > Created a network with the vlan range 921-925;then added a Vlan range from > 930-934; > The db table entries shows correctly. > Then added the IP range from 921-934; then the db entries show the same range > twice ,as shown below. > mysql> select * from physical_network; > +-+--+++-+---+---++-+-+-+ > | id | uuid | name | > data_center_id | vnet| speed | domain_id | broadcast_domain_range > | state | created | removed | > +-+--+++-+---+---++-+-+-+ > | 200 | b1dff739-f682-4678-a526-53bd9e4ce086 | Physical Network 1 | >1 | 921-934;921-934 | NULL | NULL | ZONE | Enabled > | 2013-04-19 18:14:14 | NULL| > +-+--+++-+---+---++-+-+-+ > 1 row in set (0.00 sec) > Then deleted the range from 926 -934;then one entry is deleted in the table > but the second entry still shows 921-934.The below table explains the same. > mysql> select * from physical_network; > +-+--+++-+---+---++-+-+-+ > | id | uuid | name | > data_center_id | vnet| speed | domain_id | broadcast_domain_range > | state | created | removed | > +-+--+++-+---+---++-+-+-+ > | 200 | b1dff739-f682-4678-a526-53bd9e4ce086 | Physical Network 1 | >1 | 921-925;921-934 | NULL | NULL | ZONE | Enabled > | 2013-04-19 18:14:14 | NULL| > +-+--+++-+---+---++-+-+-+ > 1 row in set (0.00 sec) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-3903) Snapshot Creation Fails in Vmware setup with permissions issue.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kiran Koneti closed CLOUDSTACK-3903.
Closing this as per dev Comments
> Snapshot Creation Fails in Vmware setup with permissions issue.
> ---
>
> Key: CLOUDSTACK-3903
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3903
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Snapshot
>Affects Versions: 4.2.0
> Environment: VMware.
>Reporter: Kiran Koneti
>Assignee: Koushik Das
>Priority: Blocker
> Fix For: 4.2.0
>
>
> Steps followed are as below:
> 1)Created an Advanced ZOne setup in the VMware.
> 2)Created a VM with root disk and Data disk,.
> 3)Once the VM is up tried to take the snapshot of the Root disk.
> 4)The snapshot creation was initiated but failed to create the snapshot as
> there are no permissions in the secondary storage to create directory for the
> snapshot.
> The error messages are as below:
> 2013-07-29 21:14:28,373 DEBUG [storage.resource.VmwareStorageProcessor]
> (DirectAgent-9:10.147.40.18) Exit value is 1
> 2013-07-29 21:14:28,384 DEBUG [storage.resource.VmwareStorageProcessor]
> (DirectAgent-9:10.147.40.18) mkdir: cannot create directory
> `/var/cloudstack/mnt/VM/6703101771911.e487dcd/snapshots': Permission denied
> 2013-07-29 21:15:03,574 ERROR [storage.resource.VmwareStorageProcessor]
> (DirectAgent-9:10.147.40.18) Unexpecpted exception
> java.lang.Exception: unable to prepare snapshot backup directory
> at
> com.cloud.storage.resource.VmwareStorageProcessor.exportVolumeToSecondaryStroage(VmwareStorageProcessor.java:960)
> at
> com.cloud.storage.resource.VmwareStorageProcessor.backupSnapshotToSecondaryStorage(VmwareStorageProcessor.java:999)
> at
> com.cloud.storage.resource.VmwareStorageProcessor.backupSnapshot(VmwareStorageProcessor.java:1072)
> at
> com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:84)
> at
> com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:49)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:562)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
> 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.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
> 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-07-29 21:15:03,609 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-9:null) Seq 1-1697251555: Response Received:
> 2013-07-29 21:15:03,610 DEBUG [agent.transport.Request] (DirectAgent-9:null)
> Seq 1-1697251555: Processing: { Ans: , MgmtId: 6703101771911, via: 1, Ver:
> v1, Flags: 10,
> [{"org.apache.cloudstack.storage.command.CopyCmdAnswer":{"result":false,"details":"BackupSnapshotCommand
> exception: java.lang.Exception: unable to prepare snapshot backup
> directory","wait":0}}] }
> 2013-07-29 21:15:03,610 DEBUG [agent.transport.Request]
> (Job-Executor-14:job-14 = [ 353da542-80f1-465b-ad37-65610a8caf4d ]) Seq
> 1-1697251555: Received: { Ans: , MgmtId: 6703101771911, via: 1, Ver: v1,
> Flags: 10, { CopyCmdAnswer } }
> 2013-07-29 21:15:03,699 DEBUG [storage.snapshot.SnapshotManagerImpl]
> (Job-Executor-14:job-14 = [ 353da542-80f1-465b-ad37-65610a8caf4d ]) Failed to
> create snapshot
> com.cloud.utils.exception.CloudRuntimeException: BackupSnapshotCommand
> exception: java.lang.Exception: unable to prepare snapshot backup directory
> at
> org.apache.cloudstack.storage.snapshot.SnapshotServiceImpl.backupSnapshot(SnapshotServiceImpl.java:286)
> at
> org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy.backupSnapshot(XenserverSnapshotStrategy.java:127)
> at
> org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy.takeSnapshot(XenserverSnapshotStrategy.java:219)
> at
> com.cloud.storage.snapshot.SnapshotManagerImpl.takeSnapshot(SnapshotManagerImpl.java:994)
> at
> org.
[jira] [Closed] (CLOUDSTACK-3501) Cannot create instances on XenServer with multiple cores per socket
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-3501. Completed the testing for the feature hence closing the issue related to the feature request. > Cannot create instances on XenServer with multiple cores per socket > --- > > Key: CLOUDSTACK-3501 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3501 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 >Reporter: Devdeep Singh >Assignee: Devdeep Singh >Priority: Critical > > It is possible to create vms on a hypervisor with multiple cores per socket. > However, right now we cannot do that with cloudstack. For example, on > XenServer if you choose a service offering with 4 cpus, an instance get > deployed with 4 vcpus. Cloudstack should let a user deploy an instance with > multiple cores in a socket. In this case it could be 4 cores in 1 socket. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-4134) UI dosent fire the API with the Vlan values if the Vlan range is blank.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733157#comment-13733157 ] Kiran Koneti commented on CLOUDSTACK-4134: -- Hi Alena, I haven't reported the second one as an issue. I was trying to explain the the API sends the Vlan list when we give some values rather than keeping it blank and that is the correct behavior we are expecting even in the case of the blank values. Regards, Kiran. > UI dosent fire the API with the Vlan values if the Vlan range is blank. > --- > > Key: CLOUDSTACK-4134 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4134 > 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: Kiran Koneti >Assignee: Bharat Kumar >Priority: Critical > Fix For: 4.2.0 > > > When we try to edit the Vlan range from the UI and give blank values in the > Vlan range box and try to update the page the API fried doesn't have any Vlan > details as it is blank in the UI. > Eg: > I tried the below scenario: > 1)Created a setup with the Vlan range 1100-1109. > 2)Then created a network where the Vlan 1101 is associated with the network. > 3)Now I tried to edit the Vlan range and gave the blank value in the UI and > clicked update. > The API fired is as below > "10.147.38.237:8080/client/api?command=updatePhysicalNetwork&response=json&sessionkey=RRxhiAqmggnl%2F5oBGHNTm3DMj0M%3D&id=2409aeac-789a-4430-a9b7-fab66eb4b85c&_=1375867127326" > Here the Vlan details are not fired in the API. > Then I tried to edit it by giving the value 1102-1109 and the API fired was > as below: > "http://10.147.38.237:8080/client/api?command=updatePhysicalNetwork&response=json&sessionkey=RRxhiAqmggnl%2F5oBGHNTm3DMj0M%3D&id=2409aeac-789a-4430-a9b7-fab66eb4b85c&vlan=1102-1109&_=1375867287606"; > The API was fired currently with the Vlan values and there was a error > message as below > "physicalnetwork 200 has allocated vnets in the range 1100-1101 " the below > is the expected behaviour and the same should happen when we try to update > the UI with Blank details. > Note: Even the UI doesn't popup with any error message the Vlan range is not > getting deleted and we can see the same vlan range once we refresh the page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3067) UI for Dedicating POD/Cluster/Host is misleading Icons should be changed.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti updated CLOUDSTACK-3067: - Attachment: ReleaseResource_current.jpg DedicateResource_Previous.jpg DedicateResource_current.jpg > UI for Dedicating POD/Cluster/Host is misleading Icons should be changed. > - > > Key: CLOUDSTACK-3067 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3067 > 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: Kiran Koneti > Fix For: 4.2.0 > > Attachments: DedicateResource_current.jpg, > DedicateResource_Previous.jpg, ReleaseResource_current.jpg > > > The UI Icons for dedicating the Pod/Cluster/Host are not proper.The Icons > resemble the Edit option and they are the same for dedicating the > Pod/Cluster/Host and also for releasing the same. > The UI should be changed to dedicating and releasing with the icons which are > used for dedicating the Zone and releasing the Zone. > The current UI looks like edit option and that is misleading as we see two > options side by side(i.e edit as well dedicating option). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3067) UI for Dedicating POD/Cluster/Host is misleading Icons should be changed.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti updated CLOUDSTACK-3067: - Attachment: ReleaseResource_expected.jpg > UI for Dedicating POD/Cluster/Host is misleading Icons should be changed. > - > > Key: CLOUDSTACK-3067 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3067 > 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: Kiran Koneti > Fix For: 4.2.0 > > Attachments: DedicateResource_current.jpg, > DedicateResource_Previous.jpg, ReleaseResource_current.jpg, > ReleaseResource_expected.jpg > > > The UI Icons for dedicating the Pod/Cluster/Host are not proper.The Icons > resemble the Edit option and they are the same for dedicating the > Pod/Cluster/Host and also for releasing the same. > The UI should be changed to dedicating and releasing with the icons which are > used for dedicating the Zone and releasing the Zone. > The current UI looks like edit option and that is misleading as we see two > options side by side(i.e edit as well dedicating option). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3067) UI for Dedicating POD/Cluster/Host is misleading Icons should be changed.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13735822#comment-13735822 ] Kiran Koneti commented on CLOUDSTACK-3067: -- Hi Animesh, I have attached four files, DedicatedResource_current.jpg is the current icon i see for the Dedicating the resource for which i have actually requested.The previous icon which was there when i raised the defect was like the one in the DedicateResource_Previous.jpg. But for the ReleaseResource i still don't see the change from the previous and current icon which is attached as ReleaseResource_current.The expected icon should resemble like the one in the 4th file i.e ReleaseResource_expected.jpg Regards, Kiran. > UI for Dedicating POD/Cluster/Host is misleading Icons should be changed. > - > > Key: CLOUDSTACK-3067 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3067 > 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: Kiran Koneti > Fix For: 4.2.0 > > Attachments: DedicateResource_current.jpg, > DedicateResource_Previous.jpg, ReleaseResource_current.jpg, > ReleaseResource_expected.jpg > > > The UI Icons for dedicating the Pod/Cluster/Host are not proper.The Icons > resemble the Edit option and they are the same for dedicating the > Pod/Cluster/Host and also for releasing the same. > The UI should be changed to dedicating and releasing with the icons which are > used for dedicating the Zone and releasing the Zone. > The current UI looks like edit option and that is misleading as we see two > options side by side(i.e edit as well dedicating option). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3839) add host is taking too long which causes createstorage pool to fail as the host is not up
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti updated CLOUDSTACK-3839: - Priority: Critical (was: Minor) it is reproduced every time we make setup in the HYD lab. Not sure with other locations. I actually fails initially to add the primary storage saying the host is not ready and if we wait for some time i.e around 2 minutes and re add the primary storage then the storage creations goes on well without any issues. This probably is the timing issue as the primary storage try's to add before the host status is UP in the CS. > add host is taking too long which causes createstorage pool to fail as the > host is not up > - > > Key: CLOUDSTACK-3839 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3839 > 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: Srikanteswararao Talluri >Assignee: Srikanteswararao Talluri >Priority: Critical > Fix For: 4.2.0 > > > Steps to reproduce: > == > Use zone create wizard to create a new zone. As the zone create process tries > to add primary storage, it finds that hosts are not ready yet. > Addition of primary storage succeeds after a while. > ===START=== 10.101.255.7 -- GET > command=createStoragePool&zoneid=ed246d25-b804-4b8d-a0b2-0ee9eb8fbb22&podId=6069566c-a491-4056-ad3d-67c9b83efc5b&clusterid=8f4faf37-46d7-42aa-97cd-df6d5166fff2&name=prim2&scope=cluster&url=nfs%3A%2F%2F10.147.28.8%2Fvol%2FdgVol%2Fautomation%2Fadv%2Fpri_2&response=json&sessionkey=9sDYqfDP16zFHMd0sNfNd4OnhlA%3D&_=1374805818616 > 2013-07-26 13:25:28,682 DEBUG > [datastore.lifecycle.CloudStackPrimaryDataStoreLifeCycleImpl] > (catalina-exec-1:null) createPool Params @ scheme - nfs storageHost - > 10.147.28.8 hostPath - /vol/dgVol/automation/adv/pri_2 port - -1 > 2013-07-26 13:25:28,721 DEBUG [cloud.storage.StorageManagerImpl] > (catalina-exec-1:null) Failed to add data store > com.cloud.utils.exception.CloudRuntimeException: No host up to associate a > storage pool with in cluster 2 > at > org.apache.cloudstack.storage.datastore.lifecycle.CloudStackPrimaryDataStoreLifeCycleImpl.attachCluster(CloudStackPrimaryDataStoreLifeCycleImpl.java:368) > at > com.cloud.storage.StorageManagerImpl.createPool(StorageManagerImpl.java:724) > at > com.cloud.storage.StorageManagerImpl.createPool(StorageManagerImpl.java:175) > at > org.apache.cloudstack.api.command.admin.storage.CreateStoragePoolCmd.execute(CreateStoragePoolCmd.java:168) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:514) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:372) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:305) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) > at > org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) > at > org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2274) > 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-07-26 13:25:28,729 INFO [cloud.api.ApiServer] (catalina-exec-1:null) > null > 2013-07-26 13:25:28,730 DEBUG [cloud.ap
[jira] [Comment Edited] (CLOUDSTACK-3839) add host is taking too long which causes createstorage pool to fail as the host is not up
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13736646#comment-13736646 ] Kiran Koneti edited comment on CLOUDSTACK-3839 at 8/12/13 7:08 AM: --- it is reproduced every time we make setup in the our location. Not sure with other locations. I actually fails initially to add the primary storage saying the host is not ready and if we wait for some time i.e around 2 minutes and re add the primary storage then the storage creations goes on well without any issues. This probably is the timing issue as the primary storage try's to add before the host status is UP in the CS. was (Author: kiran_koneti): it is reproduced every time we make setup in the HYD lab. Not sure with other locations. I actually fails initially to add the primary storage saying the host is not ready and if we wait for some time i.e around 2 minutes and re add the primary storage then the storage creations goes on well without any issues. This probably is the timing issue as the primary storage try's to add before the host status is UP in the CS. > add host is taking too long which causes createstorage pool to fail as the > host is not up > - > > Key: CLOUDSTACK-3839 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3839 > 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: Srikanteswararao Talluri >Priority: Critical > Fix For: 4.2.0 > > > Steps to reproduce: > == > Use zone create wizard to create a new zone. As the zone create process tries > to add primary storage, it finds that hosts are not ready yet. > Addition of primary storage succeeds after a while. > ===START=== 10.101.255.7 -- GET > command=createStoragePool&zoneid=ed246d25-b804-4b8d-a0b2-0ee9eb8fbb22&podId=6069566c-a491-4056-ad3d-67c9b83efc5b&clusterid=8f4faf37-46d7-42aa-97cd-df6d5166fff2&name=prim2&scope=cluster&url=nfs%3A%2F%2F10.147.28.8%2Fvol%2FdgVol%2Fautomation%2Fadv%2Fpri_2&response=json&sessionkey=9sDYqfDP16zFHMd0sNfNd4OnhlA%3D&_=1374805818616 > 2013-07-26 13:25:28,682 DEBUG > [datastore.lifecycle.CloudStackPrimaryDataStoreLifeCycleImpl] > (catalina-exec-1:null) createPool Params @ scheme - nfs storageHost - > 10.147.28.8 hostPath - /vol/dgVol/automation/adv/pri_2 port - -1 > 2013-07-26 13:25:28,721 DEBUG [cloud.storage.StorageManagerImpl] > (catalina-exec-1:null) Failed to add data store > com.cloud.utils.exception.CloudRuntimeException: No host up to associate a > storage pool with in cluster 2 > at > org.apache.cloudstack.storage.datastore.lifecycle.CloudStackPrimaryDataStoreLifeCycleImpl.attachCluster(CloudStackPrimaryDataStoreLifeCycleImpl.java:368) > at > com.cloud.storage.StorageManagerImpl.createPool(StorageManagerImpl.java:724) > at > com.cloud.storage.StorageManagerImpl.createPool(StorageManagerImpl.java:175) > at > org.apache.cloudstack.api.command.admin.storage.CreateStoragePoolCmd.execute(CreateStoragePoolCmd.java:168) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:514) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:372) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:305) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) > at > org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) > at > org.apache.coyote.http11.Http11NioProtocol$Http11Connectio
[jira] [Closed] (CLOUDSTACK-3778) [VMware] SSVM VM fails to create for the first time with message "specified key already exists".
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-3778. Closing this issue as it is not observed with the latest Build. > [VMware] SSVM VM fails to create for the first time with message "specified > key already exists". > - > > Key: CLOUDSTACK-3778 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3778 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.2.0 > Environment: VMware >Reporter: Kiran Koneti >Assignee: Kelven Yang >Priority: Critical > Fix For: 4.2.0 > > Attachments: management-server.zip > > > When we try to create a Advanced Zone setup when the first SSVM tries to come > up the Vcenter says 'The specified key, name, or identifier already exists." > and the SSVM creation fails for the first time and later then the SSVM comes > up with another name s-3-vm. > The steps are as follows: > 1)Installed the CS using the latest build. > 2)Added a host which is freshly installed to the cluster in the VCenter. > 3)Added the Vcenter details to the CS and the setup started creating the > system VM's. > 4)Once the root volume is created for the SSVM the VM named "s-1-vm" created. > 5)Then the VM gets deleted before it is powered on throwing the error message > as below > "2013-07-24 20:26:51,680 WARN [vmware.resource.VmwareResource] > (DirectAgent-8:10.147.40.18) StartCommand failed due to Exception: > com.vmware.vim25.AlreadyExists > message: [] > com.vmware.vim25.AlreadyExistsFaultMsg: The specified key, name, or > identifier already exists. > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:532) > at > com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:130) > at > com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:108) > 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:107) > at $Proxy90.addPortGroup(Unknown Source) > at > com.cloud.hypervisor.vmware.mo.HostNetworkSystemMO.addPortGroup(HostNetworkSystemMO.java:38) > at > com.cloud.hypervisor.vmware.mo.HostMO.createPortGroup(HostMO.java:389) > at > com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.prepareNetwork(HypervisorHostHelper.java:961) > at > com.cloud.hypervisor.vmware.resource.VmwareResource.prepareNetworkFromNicInfo(VmwareResource.java:3149) > at > com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2775) > at > com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:520) > at > com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)" > 6)Later it creates the root volume for one more SSVM and then the s-3-vm > comes up without any issues. > 7)all the system VM functionalities are normal. > Attaching the Management server Logs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-4287) Builtin template Ready Status is No even after the Status is downlaod complete
Kiran Koneti created CLOUDSTACK-4287: Summary: Builtin template Ready Status is No even after the Status is downlaod complete Key: CLOUDSTACK-4287 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4287 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Template Affects Versions: 4.2.0 Reporter: Kiran Koneti Priority: Critical Fix For: 4.2.0 1)Created a VMware setup and once the System Vm's are up waited for the Built-in template to download. 2)The logs show the template is downloaded and even the UI shows the same ,i.e the download status is download complete but the Ready status is NO. 3)tried to add another template manually then the the template status is shown as ready Yes after the status is download complete. The DB details: mysql> select * from vm_template where id=7\G; *** 1. row *** id: 7 unique_name: centos53-x64 name: CentOS 5.3(64-bit) no GUI (vSphere) uuid: 76ec5290-0421-11e3-bff1-06ecde18 public: 1 featured: 1 type: BUILTIN hvm: 0 bits: 64 url: http://10.147.28.7/releases/2.2.0/CentOS5.3-x86_64.ova format: OVA created: 2013-08-13 19:35:52 removed: NULL account_id: 1 checksum: f6f881b7f2292948d8494db837fe0f47 display_text: CentOS 5.3(64-bit) no GUI (vSphere) enable_password: 0 enable_sshkey: 0 guest_os_id: 12 bootable: 1 prepopulate: 0 cross_zones: 1 extractable: 1 hypervisor_type: VMware source_template_id: NULL template_tag: NULL sort_key: 0 size: 2147483648 state: Allocated update_count: 0 updated: NULL mysql> select * from template_spool_ref\G; *** 1. row *** id: 1 pool_id: 1 template_id: 8 created: 2013-08-13 14:13:09 last_updated: NULL job_id: NULL download_pct: 100 download_state: DOWNLOADED error_str: NULL local_path: 403b81265a9635c791f583145591c126 install_path: 403b81265a9635c791f583145591c126 template_size: 0 marked_for_gc: 0 state: Ready update_count: 2 updated: 2013-08-13 14:14:30 1 row in set (0.00 sec) --- mysql> select * from template_store_ref\G; *** 1. row *** id: 3 store_id: 1 template_id: 8 created: 2013-08-13 14:12:40 last_updated: 2013-08-13 14:21:37 job_id: NULL download_pct: 100 size: 2097152000 store_role: Image physical_size: 283761664 download_state: DOWNLOADED error_str: NULL local_path: NULL install_path: template/tmpl/1/8/8b563cb6-dab7-402a-8c13-3bc16d95328d.ova url: http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova download_url: NULL download_url_created: NULL state: Ready destroyed: 0 is_copy: 0 update_count: 0 ref_cnt: 0 updated: NULL *** 2. row *** id: 7 store_id: 1 template_id: 7 created: 2013-08-13 14:21:37 last_updated: 2013-08-13 14:23:33 job_id: 8ea28f5a-8009-4f87-82d1-d914f3a14a63 download_pct: 100 size: 2147483648 store_role: Image physical_size: 459320832 download_state: DOWNLOADED error_str: Install completed successfully at 8/13/13 8:58 AM local_path: /mnt/SecStorage/ec67adf1-b86c-3674-ad7f-46ddd34d104f/template/tmpl/1/7/dnld5471335544861721884tmp_ install_path: template/tmpl/1/7/ab2e2080-408e-3453-acb9-4265a6126be7.ova url: NULL download_url: NULL download_url_created: NULL state: Allocated destroyed: 0 is_copy: 0 update_count: 2 ref_cnt: 0 updated: 2013-08-13 14:22:26 2 rows in set (0.00 sec) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-4287) Builtin template Ready Status is No even after the Status is downlaod complete
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti updated CLOUDSTACK-4287: - Attachment: Builin_readyno.jpg > Builtin template Ready Status is No even after the Status is downlaod complete > -- > > Key: CLOUDSTACK-4287 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4287 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Template >Affects Versions: 4.2.0 >Reporter: Kiran Koneti >Priority: Critical > Fix For: 4.2.0 > > Attachments: Builin_readyno.jpg > > > 1)Created a VMware setup and once the System Vm's are up waited for the > Built-in template to download. > 2)The logs show the template is downloaded and even the UI shows the same > ,i.e the download status is download complete but the Ready status is NO. > 3)tried to add another template manually then the the template status is > shown as ready Yes after the status is download complete. > The DB details: > mysql> select * from vm_template where id=7\G; > *** 1. row *** > id: 7 > unique_name: centos53-x64 > name: CentOS 5.3(64-bit) no GUI (vSphere) > uuid: 76ec5290-0421-11e3-bff1-06ecde18 > public: 1 > featured: 1 > type: BUILTIN > hvm: 0 > bits: 64 > url: http://10.147.28.7/releases/2.2.0/CentOS5.3-x86_64.ova > format: OVA > created: 2013-08-13 19:35:52 > removed: NULL > account_id: 1 > checksum: f6f881b7f2292948d8494db837fe0f47 > display_text: CentOS 5.3(64-bit) no GUI (vSphere) > enable_password: 0 >enable_sshkey: 0 > guest_os_id: 12 > bootable: 1 > prepopulate: 0 > cross_zones: 1 > extractable: 1 > hypervisor_type: VMware > source_template_id: NULL > template_tag: NULL > sort_key: 0 > size: 2147483648 >state: Allocated > update_count: 0 > updated: NULL > > mysql> select * from template_spool_ref\G; > *** 1. row *** > id: 1 >pool_id: 1 >template_id: 8 >created: 2013-08-13 14:13:09 > last_updated: NULL > job_id: NULL > download_pct: 100 > download_state: DOWNLOADED > error_str: NULL > local_path: 403b81265a9635c791f583145591c126 > install_path: 403b81265a9635c791f583145591c126 > template_size: 0 > marked_for_gc: 0 > state: Ready > update_count: 2 >updated: 2013-08-13 14:14:30 > 1 row in set (0.00 sec) > --- > mysql> select * from template_store_ref\G; > *** 1. row *** > id: 3 > store_id: 1 > template_id: 8 > created: 2013-08-13 14:12:40 > last_updated: 2013-08-13 14:21:37 > job_id: NULL > download_pct: 100 > size: 2097152000 > store_role: Image >physical_size: 283761664 > download_state: DOWNLOADED >error_str: NULL > local_path: NULL > install_path: > template/tmpl/1/8/8b563cb6-dab7-402a-8c13-3bc16d95328d.ova > url: > http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova > download_url: NULL > download_url_created: NULL >state: Ready >destroyed: 0 > is_copy: 0 > update_count: 0 > ref_cnt: 0 > updated: NULL > *** 2. row *** > id: 7 > store_id: 1 > template_id: 7 > created: 2013-08-13 14:21:37 > last_updated: 2013-08-13 14:23:33 > job_id: 8ea28f5a-8009-4f87-82d1-d914f3a14a63 > download_pct: 100 > size: 2147483648 > store_role: Image >physical_size: 459320832 > download_state: DOWNLOADED >error_str: Install completed successfully at 8/13/13 8:58 AM > local_path: > /mnt/SecStorage/ec67adf1-b86c-3674-ad7f-46ddd34d104f/template/tmpl/1/7/dnld5471335544861721884tmp_ > install_path: > template/tmpl/1/7/ab2e2080-408e-3453-acb9-4265a612
[jira] [Commented] (CLOUDSTACK-4287) Builtin template Ready Status is No even after the Status is downlaod complete
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13738056#comment-13738056 ] Kiran Koneti commented on CLOUDSTACK-4287: -- After few minutes my management server got hanged and when i tried to restart the MS i see the below error messages "2013-08-13 20:54:08,104 DEBUG [agent.manager.AgentManagerImpl] (AgentTaskPool-1:null) Sending Connect to listener: UploadListener 2013-08-13 20:54:08,105 DEBUG [agent.manager.AgentManagerImpl] (AgentTaskPool-1:null) Sending Connect to listener: DownloadListener 2013-08-13 20:54:08,205 DEBUG [storage.image.TemplateDataFactoryImpl] (AgentTaskPool-1:null) template 7 is already in store:1, type:Image 2013-08-13 20:54:08,260 DEBUG [storage.image.TemplateDataFactoryImpl] (AgentTaskPool-1:null) template 7 is already in store:1, type:Image 2013-08-13 20:54:08,291 DEBUG [storage.image.BaseImageStoreDriverImpl] (AgentTaskPool-1:null) Downloading template to data store 1 2013-08-13 20:54:08,298 INFO [storage.download.DownloadMonitorImpl] (AgentTaskPool-1:null) Template download is already in progress or already downloaded 2013-08-13 20:54:08,299 DEBUG [storage.image.BaseImageStoreDriverImpl] (AgentTaskPool-1:null) Performing image store createTemplate async callback 2013-08-13 20:54:08,370 ERROR [agent.manager.AgentManagerImpl] (AgentTaskPool-1:null) Monitor DownloadListener says there is an error in the connect process for 1 due to InvocationTargetException when invoking RPC callback for command: createTemplateAsyncCallback java.lang.RuntimeException: InvocationTargetException when invoking RPC callback for command: createTemplateAsyncCallback at org.apache.cloudstack.framework.async.AsyncCallbackDispatcher.dispatch(AsyncCallbackDispatcher.java:148) at org.apache.cloudstack.framework.async.InplaceAsyncCallbackDriver.performCompletionCallback(InplaceAsyncCallbackDriver.java:26) at org.apache.cloudstack.framework.async.AsyncCallbackDispatcher.complete(AsyncCallbackDispatcher.java:120) at com.cloud.storage.download.DownloadMonitorImpl.downloadTemplateToStorage(DownloadMonitorImpl.java:214) at org.apache.cloudstack.storage.image.BaseImageStoreDriverImpl.createAsync(BaseImageStoreDriverImpl.java:120) at org.apache.cloudstack.storage.image.TemplateServiceImpl.createTemplateAsync(TemplateServiceImpl.java:173) at org.apache.cloudstack.storage.image.TemplateServiceImpl.handleSysTemplateDownload(TemplateServiceImpl.java:242) at com.cloud.storage.download.DownloadListener.processConnect(DownloadListener.java:291) at com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:587) at com.cloud.agent.manager.AgentManagerImpl.handleDirectConnectAgent(AgentManagerImpl.java:1479) at com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1739) at com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1901) at com.cloud.agent.manager.AgentManagerImpl$SimulateStartTask.run(AgentManagerImpl.java:1130) 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) Caused by: java.lang.reflect.InvocationTargetException 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.apache.cloudstack.framework.async.AsyncCallbackDispatcher.dispatch(AsyncCallbackDispatcher.java:142) ... 15 more Caused by: java.lang.RuntimeException: InvocationTargetException when invoking RPC callback for command: createTemplateCallback at org.apache.cloudstack.framework.async.AsyncCallbackDispatcher.dispatch(AsyncCallbackDispatcher.java:148) at org.apache.cloudstack.framework.async.InplaceAsyncCallbackDriver.performCompletionCallback(InplaceAsyncCallbackDriver.java:26) at org.apache.cloudstack.framework.async.AsyncCallbackDispatcher.complete(AsyncCallbackDispatcher.java:120) at org.apache.cloudstack.storage.image.BaseImageStoreDriverImpl.createTemplateAsyncCallback(BaseImageStoreDriverImpl.java:172) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ... 19 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.
[jira] [Created] (CLOUDSTACK-4288) Management server is hanging quite often and in indefinite time intervals.
Kiran Koneti created CLOUDSTACK-4288: Summary: Management server is hanging quite often and in indefinite time intervals. Key: CLOUDSTACK-4288 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4288 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.2.0 Reporter: Kiran Koneti Priority: Blocker Fix For: 4.2.0 I have created a Advanced Zone setup using the latest rhel63 399 build which is generated around 12:08 PM IST.I see the management server hanging quite few often for few minutes and restores again after some time on its own. At that time all the all teh CS operations are halted even the Management server logs also halt and once it starts the hosts go into alert state and comes up later. This is observed quite often and when i took the thread dump it shows the below messages ""SecGrp-Worker-1" prio=10 tid=0x7f86bc1de000 nid=0x28b waiting on condition [0x7f86b7cfb000] java.lang.Thread.State: WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0x00077b193618> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043) at com.cloud.network.security.LocalSecurityGroupWorkQueue.getWork(LocalSecurityGroupWorkQueue.java:152) at com.cloud.network.security.SecurityGroupManagerImpl2.work(SecurityGroupManagerImpl2.java:136) at com.cloud.network.security.SecurityGroupManagerImpl2$WorkerThread.run(SecurityGroupManagerImpl2.java:71) "SecGrp-Worker-0" prio=10 tid=0x7f86bc1dc000 nid=0x28a waiting on condition [0x7f86b7dfc000] java.lang.Thread.State: WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0x00077b193618> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043) at com.cloud.network.security.LocalSecurityGroupWorkQueue.getWork(LocalSecurityGroupWorkQueue.java:152) at com.cloud.network.security.SecurityGroupManagerImpl2.work(SecurityGroupManagerImpl2.java:136) at com.cloud.network.security.SecurityGroupManagerImpl2$WorkerThread.run(SecurityGroupManagerImpl2.java:71) "HA-2" prio=10 tid=0x7f86bc1da000 nid=0x289 waiting on condition [0x7f86b7efd000] java.lang.Thread.State: TIMED_WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0x00077dc218b0> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2081) at java.util.concurrent.DelayQueue.take(DelayQueue.java:193) at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:688) at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:681) at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1043)" Attaching the catalina.out as well as the management server logs. This issue is observed in two different setups i.e with rhel 63 build in my environment and also rhel62 environment which manasa is using. During the hang period when i did top the cpu% goes down to very low values. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-4288) Management server is hanging quite often and in indefinite time intervals.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti updated CLOUDSTACK-4288: - Attachment: management-server.zip catalina.zip > Management server is hanging quite often and in indefinite time intervals. > > > Key: CLOUDSTACK-4288 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4288 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.2.0 >Reporter: Kiran Koneti >Priority: Blocker > Fix For: 4.2.0 > > Attachments: catalina.zip, management-server.zip > > > I have created a Advanced Zone setup using the latest rhel63 399 build which > is generated around 12:08 PM IST.I see the management server hanging quite > few often for few minutes and restores again after some time on its own. > At that time all the all teh CS operations are halted even the Management > server logs also halt and once it starts the hosts go into alert state and > comes up later. > This is observed quite often and when i took the thread dump it shows the > below messages > ""SecGrp-Worker-1" prio=10 tid=0x7f86bc1de000 nid=0x28b waiting on > condition [0x7f86b7cfb000] >java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00077b193618> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043) > at > com.cloud.network.security.LocalSecurityGroupWorkQueue.getWork(LocalSecurityGroupWorkQueue.java:152) > at > com.cloud.network.security.SecurityGroupManagerImpl2.work(SecurityGroupManagerImpl2.java:136) > at > com.cloud.network.security.SecurityGroupManagerImpl2$WorkerThread.run(SecurityGroupManagerImpl2.java:71) > "SecGrp-Worker-0" prio=10 tid=0x7f86bc1dc000 nid=0x28a waiting on > condition [0x7f86b7dfc000] >java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00077b193618> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043) > at > com.cloud.network.security.LocalSecurityGroupWorkQueue.getWork(LocalSecurityGroupWorkQueue.java:152) > at > com.cloud.network.security.SecurityGroupManagerImpl2.work(SecurityGroupManagerImpl2.java:136) > at > com.cloud.network.security.SecurityGroupManagerImpl2$WorkerThread.run(SecurityGroupManagerImpl2.java:71) > "HA-2" prio=10 tid=0x7f86bc1da000 nid=0x289 waiting on condition > [0x7f86b7efd000] >java.lang.Thread.State: TIMED_WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00077dc218b0> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at > java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2081) > at java.util.concurrent.DelayQueue.take(DelayQueue.java:193) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:688) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:681) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1043)" > Attaching the catalina.out as well as the management server logs. > This issue is observed in two different setups i.e with rhel 63 build in my > environment and also rhel62 environment which manasa is using. > During the hang period when i did top the cpu% goes down to very low values. > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (CLOUDSTACK-4287) Builtin template Ready Status is No even after the Status is downlaod complete
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti reopened CLOUDSTACK-4287: -- This issue is observed in Xen and VMware setups.Hence reopening the setup. > Builtin template Ready Status is No even after the Status is downlaod complete > -- > > Key: CLOUDSTACK-4287 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4287 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Template >Affects Versions: 4.2.0 >Reporter: Kiran Koneti >Assignee: Min Chen >Priority: Blocker > Fix For: 4.2.0 > > Attachments: Builin_readyno.jpg > > > 1)Created a VMware setup and once the System Vm's are up waited for the > Built-in template to download. > 2)The logs show the template is downloaded and even the UI shows the same > ,i.e the download status is download complete but the Ready status is NO. > 3)tried to add another template manually then the the template status is > shown as ready Yes after the status is download complete. > The DB details: > mysql> select * from vm_template where id=7\G; > *** 1. row *** > id: 7 > unique_name: centos53-x64 > name: CentOS 5.3(64-bit) no GUI (vSphere) > uuid: 76ec5290-0421-11e3-bff1-06ecde18 > public: 1 > featured: 1 > type: BUILTIN > hvm: 0 > bits: 64 > url: http://10.147.28.7/releases/2.2.0/CentOS5.3-x86_64.ova > format: OVA > created: 2013-08-13 19:35:52 > removed: NULL > account_id: 1 > checksum: f6f881b7f2292948d8494db837fe0f47 > display_text: CentOS 5.3(64-bit) no GUI (vSphere) > enable_password: 0 >enable_sshkey: 0 > guest_os_id: 12 > bootable: 1 > prepopulate: 0 > cross_zones: 1 > extractable: 1 > hypervisor_type: VMware > source_template_id: NULL > template_tag: NULL > sort_key: 0 > size: 2147483648 >state: Allocated > update_count: 0 > updated: NULL > > mysql> select * from template_spool_ref\G; > *** 1. row *** > id: 1 >pool_id: 1 >template_id: 8 >created: 2013-08-13 14:13:09 > last_updated: NULL > job_id: NULL > download_pct: 100 > download_state: DOWNLOADED > error_str: NULL > local_path: 403b81265a9635c791f583145591c126 > install_path: 403b81265a9635c791f583145591c126 > template_size: 0 > marked_for_gc: 0 > state: Ready > update_count: 2 >updated: 2013-08-13 14:14:30 > 1 row in set (0.00 sec) > --- > mysql> select * from template_store_ref\G; > *** 1. row *** > id: 3 > store_id: 1 > template_id: 8 > created: 2013-08-13 14:12:40 > last_updated: 2013-08-13 14:21:37 > job_id: NULL > download_pct: 100 > size: 2097152000 > store_role: Image >physical_size: 283761664 > download_state: DOWNLOADED >error_str: NULL > local_path: NULL > install_path: > template/tmpl/1/8/8b563cb6-dab7-402a-8c13-3bc16d95328d.ova > url: > http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova > download_url: NULL > download_url_created: NULL >state: Ready >destroyed: 0 > is_copy: 0 > update_count: 0 > ref_cnt: 0 > updated: NULL > *** 2. row *** > id: 7 > store_id: 1 > template_id: 7 > created: 2013-08-13 14:21:37 > last_updated: 2013-08-13 14:23:33 > job_id: 8ea28f5a-8009-4f87-82d1-d914f3a14a63 > download_pct: 100 > size: 2147483648 > store_role: Image >physical_size: 459320832 > download_state: DOWNLOADED >error_str: Install completed successfully at 8/13/13 8:58 AM > local_path: > /mnt/SecStorage/ec67adf1-b86c-3674-ad7f-46ddd34d104f/template/tmpl/1/7/dnld547133554486172
[jira] [Commented] (CLOUDSTACK-4287) Builtin template Ready Status is No even after the Status is downlaod complete
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739308#comment-13739308 ] Kiran Koneti commented on CLOUDSTACK-4287: -- I am attaching the logs of the setup. > Builtin template Ready Status is No even after the Status is downlaod complete > -- > > Key: CLOUDSTACK-4287 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4287 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Template >Affects Versions: 4.2.0 >Reporter: Kiran Koneti >Assignee: Min Chen >Priority: Blocker > Fix For: 4.2.0 > > Attachments: Builin_readyno.jpg > > > 1)Created a VMware setup and once the System Vm's are up waited for the > Built-in template to download. > 2)The logs show the template is downloaded and even the UI shows the same > ,i.e the download status is download complete but the Ready status is NO. > 3)tried to add another template manually then the the template status is > shown as ready Yes after the status is download complete. > The DB details: > mysql> select * from vm_template where id=7\G; > *** 1. row *** > id: 7 > unique_name: centos53-x64 > name: CentOS 5.3(64-bit) no GUI (vSphere) > uuid: 76ec5290-0421-11e3-bff1-06ecde18 > public: 1 > featured: 1 > type: BUILTIN > hvm: 0 > bits: 64 > url: http://10.147.28.7/releases/2.2.0/CentOS5.3-x86_64.ova > format: OVA > created: 2013-08-13 19:35:52 > removed: NULL > account_id: 1 > checksum: f6f881b7f2292948d8494db837fe0f47 > display_text: CentOS 5.3(64-bit) no GUI (vSphere) > enable_password: 0 >enable_sshkey: 0 > guest_os_id: 12 > bootable: 1 > prepopulate: 0 > cross_zones: 1 > extractable: 1 > hypervisor_type: VMware > source_template_id: NULL > template_tag: NULL > sort_key: 0 > size: 2147483648 >state: Allocated > update_count: 0 > updated: NULL > > mysql> select * from template_spool_ref\G; > *** 1. row *** > id: 1 >pool_id: 1 >template_id: 8 >created: 2013-08-13 14:13:09 > last_updated: NULL > job_id: NULL > download_pct: 100 > download_state: DOWNLOADED > error_str: NULL > local_path: 403b81265a9635c791f583145591c126 > install_path: 403b81265a9635c791f583145591c126 > template_size: 0 > marked_for_gc: 0 > state: Ready > update_count: 2 >updated: 2013-08-13 14:14:30 > 1 row in set (0.00 sec) > --- > mysql> select * from template_store_ref\G; > *** 1. row *** > id: 3 > store_id: 1 > template_id: 8 > created: 2013-08-13 14:12:40 > last_updated: 2013-08-13 14:21:37 > job_id: NULL > download_pct: 100 > size: 2097152000 > store_role: Image >physical_size: 283761664 > download_state: DOWNLOADED >error_str: NULL > local_path: NULL > install_path: > template/tmpl/1/8/8b563cb6-dab7-402a-8c13-3bc16d95328d.ova > url: > http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova > download_url: NULL > download_url_created: NULL >state: Ready >destroyed: 0 > is_copy: 0 > update_count: 0 > ref_cnt: 0 > updated: NULL > *** 2. row *** > id: 7 > store_id: 1 > template_id: 7 > created: 2013-08-13 14:21:37 > last_updated: 2013-08-13 14:23:33 > job_id: 8ea28f5a-8009-4f87-82d1-d914f3a14a63 > download_pct: 100 > size: 2147483648 > store_role: Image >physical_size: 459320832 > download_state: DOWNLOADED >error_str: Install completed successfully at 8/13/13 8:58 AM > local_path: > /mnt/SecStorage/ec67adf1-b86c-3674-ad7f-46ddd34d104f/template/tmpl/1/7/d
[jira] [Updated] (CLOUDSTACK-4287) Builtin template Ready Status is No even after the Status is downlaod complete
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti updated CLOUDSTACK-4287: - Attachment: management-server.zip > Builtin template Ready Status is No even after the Status is downlaod complete > -- > > Key: CLOUDSTACK-4287 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4287 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Template >Affects Versions: 4.2.0 >Reporter: Kiran Koneti >Assignee: Min Chen >Priority: Blocker > Fix For: 4.2.0 > > Attachments: Builin_readyno.jpg, management-server.zip > > > 1)Created a VMware setup and once the System Vm's are up waited for the > Built-in template to download. > 2)The logs show the template is downloaded and even the UI shows the same > ,i.e the download status is download complete but the Ready status is NO. > 3)tried to add another template manually then the the template status is > shown as ready Yes after the status is download complete. > The DB details: > mysql> select * from vm_template where id=7\G; > *** 1. row *** > id: 7 > unique_name: centos53-x64 > name: CentOS 5.3(64-bit) no GUI (vSphere) > uuid: 76ec5290-0421-11e3-bff1-06ecde18 > public: 1 > featured: 1 > type: BUILTIN > hvm: 0 > bits: 64 > url: http://10.147.28.7/releases/2.2.0/CentOS5.3-x86_64.ova > format: OVA > created: 2013-08-13 19:35:52 > removed: NULL > account_id: 1 > checksum: f6f881b7f2292948d8494db837fe0f47 > display_text: CentOS 5.3(64-bit) no GUI (vSphere) > enable_password: 0 >enable_sshkey: 0 > guest_os_id: 12 > bootable: 1 > prepopulate: 0 > cross_zones: 1 > extractable: 1 > hypervisor_type: VMware > source_template_id: NULL > template_tag: NULL > sort_key: 0 > size: 2147483648 >state: Allocated > update_count: 0 > updated: NULL > > mysql> select * from template_spool_ref\G; > *** 1. row *** > id: 1 >pool_id: 1 >template_id: 8 >created: 2013-08-13 14:13:09 > last_updated: NULL > job_id: NULL > download_pct: 100 > download_state: DOWNLOADED > error_str: NULL > local_path: 403b81265a9635c791f583145591c126 > install_path: 403b81265a9635c791f583145591c126 > template_size: 0 > marked_for_gc: 0 > state: Ready > update_count: 2 >updated: 2013-08-13 14:14:30 > 1 row in set (0.00 sec) > --- > mysql> select * from template_store_ref\G; > *** 1. row *** > id: 3 > store_id: 1 > template_id: 8 > created: 2013-08-13 14:12:40 > last_updated: 2013-08-13 14:21:37 > job_id: NULL > download_pct: 100 > size: 2097152000 > store_role: Image >physical_size: 283761664 > download_state: DOWNLOADED >error_str: NULL > local_path: NULL > install_path: > template/tmpl/1/8/8b563cb6-dab7-402a-8c13-3bc16d95328d.ova > url: > http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova > download_url: NULL > download_url_created: NULL >state: Ready >destroyed: 0 > is_copy: 0 > update_count: 0 > ref_cnt: 0 > updated: NULL > *** 2. row *** > id: 7 > store_id: 1 > template_id: 7 > created: 2013-08-13 14:21:37 > last_updated: 2013-08-13 14:23:33 > job_id: 8ea28f5a-8009-4f87-82d1-d914f3a14a63 > download_pct: 100 > size: 2147483648 > store_role: Image >physical_size: 459320832 > download_state: DOWNLOADED >error_str: Install completed successfully at 8/13/13 8:58 AM > local_path: > /mnt/SecStorage/ec67adf1-b86c-3674-ad7f-46ddd34d104f/template/tmpl/1/7/dnld5471335544861721884tmp_ > install_pa
[jira] [Created] (CLOUDSTACK-4319) Able to Create A VM on a Dedciated Zone without using the affinity group.
Kiran Koneti created CLOUDSTACK-4319: Summary: Able to Create A VM on a Dedciated Zone without using the affinity group. Key: CLOUDSTACK-4319 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4319 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.2.0 Reporter: Kiran Koneti Priority: Critical Fix For: 4.2.0 Created a setup in the below mentioned way: Zone-->POD-->Cluster-->2Hosts. 1)I created 2 domains apart from the Root Domain having two accounts for each domain. 2)Dedicated the Zone to non root domain. 3)Dedicated the one host to account in the same domain. 4)Observed that 2 affinity groups are created and the while deploying the VM i haven't selected any of the affinity groups and the VM creation was Successful. The expected Result is the VM creation should be failed as the Zone is dedicated and no affinity group is selected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-4287) Builtin template Ready Status is No even after the Status is downlaod complete
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti updated CLOUDSTACK-4287: - Attachment: managemntLog_Latest.zip > Builtin template Ready Status is No even after the Status is downlaod complete > -- > > Key: CLOUDSTACK-4287 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4287 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Template >Affects Versions: 4.2.0 >Reporter: Kiran Koneti >Assignee: Nitin Mehta >Priority: Critical > Fix For: 4.2.0 > > Attachments: Builin_readyno.jpg, management-server.zip, > managemntLog_Latest.zip > > > 1)Created a VMware setup and once the System Vm's are up waited for the > Built-in template to download. > 2)The logs show the template is downloaded and even the UI shows the same > ,i.e the download status is download complete but the Ready status is NO. > 3)tried to add another template manually then the the template status is > shown as ready Yes after the status is download complete. > The DB details: > mysql> select * from vm_template where id=7\G; > *** 1. row *** > id: 7 > unique_name: centos53-x64 > name: CentOS 5.3(64-bit) no GUI (vSphere) > uuid: 76ec5290-0421-11e3-bff1-06ecde18 > public: 1 > featured: 1 > type: BUILTIN > hvm: 0 > bits: 64 > url: http://10.147.28.7/releases/2.2.0/CentOS5.3-x86_64.ova > format: OVA > created: 2013-08-13 19:35:52 > removed: NULL > account_id: 1 > checksum: f6f881b7f2292948d8494db837fe0f47 > display_text: CentOS 5.3(64-bit) no GUI (vSphere) > enable_password: 0 >enable_sshkey: 0 > guest_os_id: 12 > bootable: 1 > prepopulate: 0 > cross_zones: 1 > extractable: 1 > hypervisor_type: VMware > source_template_id: NULL > template_tag: NULL > sort_key: 0 > size: 2147483648 >state: Allocated > update_count: 0 > updated: NULL > > mysql> select * from template_spool_ref\G; > *** 1. row *** > id: 1 >pool_id: 1 >template_id: 8 >created: 2013-08-13 14:13:09 > last_updated: NULL > job_id: NULL > download_pct: 100 > download_state: DOWNLOADED > error_str: NULL > local_path: 403b81265a9635c791f583145591c126 > install_path: 403b81265a9635c791f583145591c126 > template_size: 0 > marked_for_gc: 0 > state: Ready > update_count: 2 >updated: 2013-08-13 14:14:30 > 1 row in set (0.00 sec) > --- > mysql> select * from template_store_ref\G; > *** 1. row *** > id: 3 > store_id: 1 > template_id: 8 > created: 2013-08-13 14:12:40 > last_updated: 2013-08-13 14:21:37 > job_id: NULL > download_pct: 100 > size: 2097152000 > store_role: Image >physical_size: 283761664 > download_state: DOWNLOADED >error_str: NULL > local_path: NULL > install_path: > template/tmpl/1/8/8b563cb6-dab7-402a-8c13-3bc16d95328d.ova > url: > http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova > download_url: NULL > download_url_created: NULL >state: Ready >destroyed: 0 > is_copy: 0 > update_count: 0 > ref_cnt: 0 > updated: NULL > *** 2. row *** > id: 7 > store_id: 1 > template_id: 7 > created: 2013-08-13 14:21:37 > last_updated: 2013-08-13 14:23:33 > job_id: 8ea28f5a-8009-4f87-82d1-d914f3a14a63 > download_pct: 100 > size: 2147483648 > store_role: Image >physical_size: 459320832 > download_state: DOWNLOADED >error_str: Install completed successfully at 8/13/13 8:58 AM > local_path: > /mnt/SecStorage/ec67adf1-b86c-3674-ad7f-46ddd34d104f/template/tmpl/1/7/dnld5471335544
[jira] [Commented] (CLOUDSTACK-4287) Builtin template Ready Status is No even after the Status is downlaod complete
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739492#comment-13739492 ] Kiran Koneti commented on CLOUDSTACK-4287: -- Nitin The repro steps are the same as which i have mentioned while creating the bug.Have attached the Latest Management logs from the 413 build. > Builtin template Ready Status is No even after the Status is downlaod complete > -- > > Key: CLOUDSTACK-4287 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4287 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Template >Affects Versions: 4.2.0 >Reporter: Kiran Koneti >Assignee: Nitin Mehta >Priority: Critical > Fix For: 4.2.0 > > Attachments: Builin_readyno.jpg, management-server.zip, > managemntLog_Latest.zip > > > 1)Created a VMware setup and once the System Vm's are up waited for the > Built-in template to download. > 2)The logs show the template is downloaded and even the UI shows the same > ,i.e the download status is download complete but the Ready status is NO. > 3)tried to add another template manually then the the template status is > shown as ready Yes after the status is download complete. > The DB details: > mysql> select * from vm_template where id=7\G; > *** 1. row *** > id: 7 > unique_name: centos53-x64 > name: CentOS 5.3(64-bit) no GUI (vSphere) > uuid: 76ec5290-0421-11e3-bff1-06ecde18 > public: 1 > featured: 1 > type: BUILTIN > hvm: 0 > bits: 64 > url: http://10.147.28.7/releases/2.2.0/CentOS5.3-x86_64.ova > format: OVA > created: 2013-08-13 19:35:52 > removed: NULL > account_id: 1 > checksum: f6f881b7f2292948d8494db837fe0f47 > display_text: CentOS 5.3(64-bit) no GUI (vSphere) > enable_password: 0 >enable_sshkey: 0 > guest_os_id: 12 > bootable: 1 > prepopulate: 0 > cross_zones: 1 > extractable: 1 > hypervisor_type: VMware > source_template_id: NULL > template_tag: NULL > sort_key: 0 > size: 2147483648 >state: Allocated > update_count: 0 > updated: NULL > > mysql> select * from template_spool_ref\G; > *** 1. row *** > id: 1 >pool_id: 1 >template_id: 8 >created: 2013-08-13 14:13:09 > last_updated: NULL > job_id: NULL > download_pct: 100 > download_state: DOWNLOADED > error_str: NULL > local_path: 403b81265a9635c791f583145591c126 > install_path: 403b81265a9635c791f583145591c126 > template_size: 0 > marked_for_gc: 0 > state: Ready > update_count: 2 >updated: 2013-08-13 14:14:30 > 1 row in set (0.00 sec) > --- > mysql> select * from template_store_ref\G; > *** 1. row *** > id: 3 > store_id: 1 > template_id: 8 > created: 2013-08-13 14:12:40 > last_updated: 2013-08-13 14:21:37 > job_id: NULL > download_pct: 100 > size: 2097152000 > store_role: Image >physical_size: 283761664 > download_state: DOWNLOADED >error_str: NULL > local_path: NULL > install_path: > template/tmpl/1/8/8b563cb6-dab7-402a-8c13-3bc16d95328d.ova > url: > http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova > download_url: NULL > download_url_created: NULL >state: Ready >destroyed: 0 > is_copy: 0 > update_count: 0 > ref_cnt: 0 > updated: NULL > *** 2. row *** > id: 7 > store_id: 1 > template_id: 7 > created: 2013-08-13 14:21:37 > last_updated: 2013-08-13 14:23:33 > job_id: 8ea28f5a-8009-4f87-82d1-d914f3a14a63 > download_pct: 100 > size: 2147483648 > store_role: Image >physical_size: 459320832 > download_state: DOWNLOADED >
[jira] [Created] (CLOUDSTACK-4321) Not able to deploy VM using the affinity groups.
Kiran Koneti created CLOUDSTACK-4321: Summary: Not able to deploy VM using the affinity groups. Key: CLOUDSTACK-4321 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4321 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.2.0 Reporter: Kiran Koneti Priority: Critical Fix For: 4.2.0 Created a setup in the below mentioned way: Zone-->POD-->Cluster-->2Hosts. 1)I created 2 domains apart from the Root Domain having two accounts for each domain. 2)Dedicated the Zone to non root domain. 3)Dedicated the one host to account in the same domain. 4)Observed that 2 affinity groups are created and the while deploying the VM i have selected both the affinity groups and the VM creation Failed. The expected Result is the VM creation should be successful as the Zone is dedicated and both affinity groups are selected. The MS log shows the permission is granted to the account but the UI throws an error message saying there is no way to detect the affinity group is related to the account. THE MS log is as below: "2013-08-14 21:33:06,152 DEBUG [cloud.user.AccountManagerImpl] (catalina-exec-20:null) Access granted to Acct[7d48a75d-4b99-4e89-8b17-a66a9aac3098-kiran1] to Domain:2/Kiran/ by DomainChecker_EnhancerByCloudStack_3d51253f 2013-08-14 21:33:06,155 DEBUG [cloud.user.AccountManagerImpl] (catalina-exec-20:null) Access to Acct[7d48a75d-4b99-4e89-8b17-a66a9aac3098-kiran1] granted to Acct[7d48a75d-4b99-4e89-8b17-a66a9aac3098-kiran1] by DomainChecker_EnhancerByCloudStack_3d51253f" The UI error message is as below: There's no way to confirm Acct[7d48a75d-4b99-4e89-8b17-a66a9aac3098-kiran1] has access to AffinityGroup[78de168c-aa92-4e72-8902-ff3c77ae8be8] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-4287) Builtin template Ready Status is No even after the Status is downlaod complete
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-4287. Closing this as it is not observed with the new Build. > Builtin template Ready Status is No even after the Status is downlaod complete > -- > > Key: CLOUDSTACK-4287 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4287 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Template >Affects Versions: 4.2.0 >Reporter: Kiran Koneti >Assignee: Nitin Mehta >Priority: Critical > Fix For: 4.2.0 > > Attachments: Builin_readyno.jpg, management-server.zip, > managemntLog_Latest.zip > > > 1)Created a VMware setup and once the System Vm's are up waited for the > Built-in template to download. > 2)The logs show the template is downloaded and even the UI shows the same > ,i.e the download status is download complete but the Ready status is NO. > 3)tried to add another template manually then the the template status is > shown as ready Yes after the status is download complete. > The DB details: > mysql> select * from vm_template where id=7\G; > *** 1. row *** > id: 7 > unique_name: centos53-x64 > name: CentOS 5.3(64-bit) no GUI (vSphere) > uuid: 76ec5290-0421-11e3-bff1-06ecde18 > public: 1 > featured: 1 > type: BUILTIN > hvm: 0 > bits: 64 > url: http://10.147.28.7/releases/2.2.0/CentOS5.3-x86_64.ova > format: OVA > created: 2013-08-13 19:35:52 > removed: NULL > account_id: 1 > checksum: f6f881b7f2292948d8494db837fe0f47 > display_text: CentOS 5.3(64-bit) no GUI (vSphere) > enable_password: 0 >enable_sshkey: 0 > guest_os_id: 12 > bootable: 1 > prepopulate: 0 > cross_zones: 1 > extractable: 1 > hypervisor_type: VMware > source_template_id: NULL > template_tag: NULL > sort_key: 0 > size: 2147483648 >state: Allocated > update_count: 0 > updated: NULL > > mysql> select * from template_spool_ref\G; > *** 1. row *** > id: 1 >pool_id: 1 >template_id: 8 >created: 2013-08-13 14:13:09 > last_updated: NULL > job_id: NULL > download_pct: 100 > download_state: DOWNLOADED > error_str: NULL > local_path: 403b81265a9635c791f583145591c126 > install_path: 403b81265a9635c791f583145591c126 > template_size: 0 > marked_for_gc: 0 > state: Ready > update_count: 2 >updated: 2013-08-13 14:14:30 > 1 row in set (0.00 sec) > --- > mysql> select * from template_store_ref\G; > *** 1. row *** > id: 3 > store_id: 1 > template_id: 8 > created: 2013-08-13 14:12:40 > last_updated: 2013-08-13 14:21:37 > job_id: NULL > download_pct: 100 > size: 2097152000 > store_role: Image >physical_size: 283761664 > download_state: DOWNLOADED >error_str: NULL > local_path: NULL > install_path: > template/tmpl/1/8/8b563cb6-dab7-402a-8c13-3bc16d95328d.ova > url: > http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova > download_url: NULL > download_url_created: NULL >state: Ready >destroyed: 0 > is_copy: 0 > update_count: 0 > ref_cnt: 0 > updated: NULL > *** 2. row *** > id: 7 > store_id: 1 > template_id: 7 > created: 2013-08-13 14:21:37 > last_updated: 2013-08-13 14:23:33 > job_id: 8ea28f5a-8009-4f87-82d1-d914f3a14a63 > download_pct: 100 > size: 2147483648 > store_role: Image >physical_size: 459320832 > download_state: DOWNLOADED >error_str: Install completed successfully at 8/13/13 8:58 AM > local_path: > /mnt/SecStorage/ec67adf1-b86c-3674-ad7f-46ddd34d104f/templa
[jira] [Created] (CLOUDSTACK-4375) VM Migration is failing from one cluster to another cluster.
Kiran Koneti created CLOUDSTACK-4375:
Summary: VM Migration is failing from one cluster to another
cluster.
Key: CLOUDSTACK-4375
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4375
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: Kiran Koneti
Priority: Critical
Fix For: 4.2.0
Steps followed are as below:
1)Created a Advanced Zone VMware setup with two clusters C1 & c2.
2)C1 having 2 hosts H1 and H2 and C2 having single host H3.
3)Dedicated the Zone to Domain D1 having Account A1 and A2.
4)Dedicated the Host H2 to Account A1, where H1 has the system Vm's in it.
5)Created a VM not using the affinity group for the host,the Router VM came up
on the host H1and the VM is created on host H3 of the cluster C2.
6)Now tried to migrate the VM from H3 to H1 the migration was successful.
7)Now tried to migrate the VM from H1 to H3 again the VM migration failed with
the below error message
"2013-08-17 03:13:59,447 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null)
===START=== 10.101.255.76 -- GET
command=migrateVirtualMachine&hostid=49537136-d44f-439a-937c-442ed74bd697&virtualmachineid=385b5edb-b6b2-4931-a4ab-8f9bd96acd14&response=json&sessionkey=3O%2FKhJ6pMFCAfLTZtIqQOY6R6%2F4%3D&_=1376669973550
2013-08-17 03:13:59,488 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-2:null) submit async job-178 = [
b9d65e31-7cdf-4ce5-b93c-440287d8523f ], details: AsyncJobVO {id:178, userId: 2,
accountId: 2, sessionKey: null, instanceType: None, instanceId: null, cmd:
org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdOriginator: null,
cmdInfo:
{"response":"json","sessionkey":"3O/KhJ6pMFCAfLTZtIqQOY6R6/4\u003d","virtualmachineid":"385b5edb-b6b2-4931-a4ab-8f9bd96acd14","cmdEventType":"VM.MIGRATE","hostid":"49537136-d44f-439a-937c-442ed74bd697","ctxUserId":"2","httpmethod":"GET","_":"1376669973550","ctxAccountId":"2","ctxStartEventId":"618"},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 6703101771911,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-08-17 03:13:59,489 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null)
===END=== 10.101.255.76 -- GET
command=migrateVirtualMachine&hostid=49537136-d44f-439a-937c-442ed74bd697&virtualmachineid=385b5edb-b6b2-4931-a4ab-8f9bd96acd14&response=json&sessionkey=3O%2FKhJ6pMFCAfLTZtIqQOY6R6%2F4%3D&_=1376669973550
2013-08-17 03:13:59,491 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-119:job-178 = [ b9d65e31-7cdf-4ce5-b93c-440287d8523f ]) Executing
org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd for job-178 = [
b9d65e31-7cdf-4ce5-b93c-440287d8523f ]
2013-08-17 03:13:59,528 INFO [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-119:job-178 = [ b9d65e31-7cdf-4ce5-b93c-440287d8523f ]) Migrating
VM[User|kiran14] to
Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))]
: Dest[Zone(3)-Pod(3)-Cluster(6)-Host(11)-Storage()]
2013-08-17 03:13:59,529 INFO [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-119:job-178 = [ b9d65e31-7cdf-4ce5-b93c-440287d8523f ]) Source
and destination host are not in same cluster, unable to migrate to host: 11
2013-08-17 03:13:59,536 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-119:job-178 = [ b9d65e31-7cdf-4ce5-b93c-440287d8523f ])
Unexpected exception while executing
org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd
com.cloud.utils.exception.CloudRuntimeException: Source and destination host
are not in same cluster, unable to migrate to host: 11
at
com.cloud.vm.VirtualMachineManagerImpl.migrate(VirtualMachineManagerImpl.java:1452)
at
com.cloud.vm.UserVmManagerImpl.migrateVirtualMachine(UserVmManagerImpl.java:3981)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd.execute(MigrateVMCmd.java:147)
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:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)"
Expected result:The VM migration should be successful.
Note:The Vmotion on the VMwar
[jira] [Updated] (CLOUDSTACK-4375) VM Migration is failing from one cluster to another cluster.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kiran Koneti updated CLOUDSTACK-4375:
-
Attachment: management-server.zip
Attaching management server logs
> VM Migration is failing from one cluster to another cluster.
>
>
> Key: CLOUDSTACK-4375
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4375
> 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: Kiran Koneti
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.zip
>
>
> Steps followed are as below:
> 1)Created a Advanced Zone VMware setup with two clusters C1 & c2.
> 2)C1 having 2 hosts H1 and H2 and C2 having single host H3.
> 3)Dedicated the Zone to Domain D1 having Account A1 and A2.
> 4)Dedicated the Host H2 to Account A1, where H1 has the system Vm's in it.
> 5)Created a VM not using the affinity group for the host,the Router VM came
> up on the host H1and the VM is created on host H3 of the cluster C2.
> 6)Now tried to migrate the VM from H3 to H1 the migration was successful.
> 7)Now tried to migrate the VM from H1 to H3 again the VM migration failed
> with the below error message
> "2013-08-17 03:13:59,447 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null)
> ===START=== 10.101.255.76 -- GET
> command=migrateVirtualMachine&hostid=49537136-d44f-439a-937c-442ed74bd697&virtualmachineid=385b5edb-b6b2-4931-a4ab-8f9bd96acd14&response=json&sessionkey=3O%2FKhJ6pMFCAfLTZtIqQOY6R6%2F4%3D&_=1376669973550
> 2013-08-17 03:13:59,488 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-2:null) submit async job-178 = [
> b9d65e31-7cdf-4ce5-b93c-440287d8523f ], details: AsyncJobVO {id:178, userId:
> 2, accountId: 2, sessionKey: null, instanceType: None, instanceId: null, cmd:
> org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdOriginator: null,
> cmdInfo:
> {"response":"json","sessionkey":"3O/KhJ6pMFCAfLTZtIqQOY6R6/4\u003d","virtualmachineid":"385b5edb-b6b2-4931-a4ab-8f9bd96acd14","cmdEventType":"VM.MIGRATE","hostid":"49537136-d44f-439a-937c-442ed74bd697","ctxUserId":"2","httpmethod":"GET","_":"1376669973550","ctxAccountId":"2","ctxStartEventId":"618"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 6703101771911,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-08-17 03:13:59,489 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null)
> ===END=== 10.101.255.76 -- GET
> command=migrateVirtualMachine&hostid=49537136-d44f-439a-937c-442ed74bd697&virtualmachineid=385b5edb-b6b2-4931-a4ab-8f9bd96acd14&response=json&sessionkey=3O%2FKhJ6pMFCAfLTZtIqQOY6R6%2F4%3D&_=1376669973550
> 2013-08-17 03:13:59,491 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-119:job-178 = [ b9d65e31-7cdf-4ce5-b93c-440287d8523f ])
> Executing org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd for job-178
> = [ b9d65e31-7cdf-4ce5-b93c-440287d8523f ]
> 2013-08-17 03:13:59,528 INFO [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-119:job-178 = [ b9d65e31-7cdf-4ce5-b93c-440287d8523f ])
> Migrating VM[User|kiran14] to
> Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))]
> : Dest[Zone(3)-Pod(3)-Cluster(6)-Host(11)-Storage()]
> 2013-08-17 03:13:59,529 INFO [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-119:job-178 = [ b9d65e31-7cdf-4ce5-b93c-440287d8523f ]) Source
> and destination host are not in same cluster, unable to migrate to host: 11
> 2013-08-17 03:13:59,536 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-119:job-178 = [ b9d65e31-7cdf-4ce5-b93c-440287d8523f ])
> Unexpected exception while executing
> org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd
> com.cloud.utils.exception.CloudRuntimeException: Source and destination host
> are not in same cluster, unable to migrate to host: 11
> at
> com.cloud.vm.VirtualMachineManagerImpl.migrate(VirtualMachineManagerImpl.java:1452)
> at
> com.cloud.vm.UserVmManagerImpl.migrateVirtualMachine(UserVmManagerImpl.java:3981)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd.execute(MigrateVMCmd.java:147)
> 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.concu
[jira] [Closed] (CLOUDSTACK-4319) Able to Create A VM on a Dedciated Zone without using the affinity group.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-4319. Closing this as not a bug as this is last minute feature change. > Able to Create A VM on a Dedciated Zone without using the affinity group. > - > > Key: CLOUDSTACK-4319 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4319 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.2.0 >Reporter: Kiran Koneti >Assignee: Prachi Damle >Priority: Critical > Fix For: 4.2.0 > > > Created a setup in the below mentioned way: > Zone-->POD-->Cluster-->2Hosts. > 1)I created 2 domains apart from the Root Domain having two accounts for each > domain. > 2)Dedicated the Zone to non root domain. > 3)Dedicated the one host to account in the same domain. > 4)Observed that 2 affinity groups are created and the while deploying the VM > i haven't selected any of the affinity groups and the VM creation was > Successful. > The expected Result is the VM creation should be failed as the Zone is > dedicated and no affinity group is selected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-4288) Management server is hanging quite often and in indefinite time intervals.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-4288. Closing this as it is not reproduced with the latest build. > Management server is hanging quite often and in indefinite time intervals. > > > Key: CLOUDSTACK-4288 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4288 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.2.0 >Reporter: Kiran Koneti >Assignee: Kelven Yang >Priority: Blocker > Fix For: 4.2.0 > > Attachments: catalina.zip, management-server.zip > > > I have created a Advanced Zone setup using the latest rhel63 399 build which > is generated around 12:08 PM IST.I see the management server hanging quite > few often for few minutes and restores again after some time on its own. > At that time all the all teh CS operations are halted even the Management > server logs also halt and once it starts the hosts go into alert state and > comes up later. > This is observed quite often and when i took the thread dump it shows the > below messages > ""SecGrp-Worker-1" prio=10 tid=0x7f86bc1de000 nid=0x28b waiting on > condition [0x7f86b7cfb000] >java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00077b193618> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043) > at > com.cloud.network.security.LocalSecurityGroupWorkQueue.getWork(LocalSecurityGroupWorkQueue.java:152) > at > com.cloud.network.security.SecurityGroupManagerImpl2.work(SecurityGroupManagerImpl2.java:136) > at > com.cloud.network.security.SecurityGroupManagerImpl2$WorkerThread.run(SecurityGroupManagerImpl2.java:71) > "SecGrp-Worker-0" prio=10 tid=0x7f86bc1dc000 nid=0x28a waiting on > condition [0x7f86b7dfc000] >java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00077b193618> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043) > at > com.cloud.network.security.LocalSecurityGroupWorkQueue.getWork(LocalSecurityGroupWorkQueue.java:152) > at > com.cloud.network.security.SecurityGroupManagerImpl2.work(SecurityGroupManagerImpl2.java:136) > at > com.cloud.network.security.SecurityGroupManagerImpl2$WorkerThread.run(SecurityGroupManagerImpl2.java:71) > "HA-2" prio=10 tid=0x7f86bc1da000 nid=0x289 waiting on condition > [0x7f86b7efd000] >java.lang.Thread.State: TIMED_WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00077dc218b0> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at > java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2081) > at java.util.concurrent.DelayQueue.take(DelayQueue.java:193) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:688) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:681) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1043)" > Attaching the catalina.out as well as the management server logs. > This issue is observed in two different setups i.e with rhel 63 build in my > environment and also rhel62 environment which manasa is using. > During the hang period when i did top the cpu% goes down to very low values. > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-4321) Not able to deploy VM using the affinity groups.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-4321. Tested it with the latest build and the issue is resolved. > Not able to deploy VM using the affinity groups. > > > Key: CLOUDSTACK-4321 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4321 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.2.0 >Reporter: Kiran Koneti >Assignee: Prachi Damle >Priority: Critical > Fix For: 4.2.0 > > > Created a setup in the below mentioned way: > Zone-->POD-->Cluster-->2Hosts. > 1)I created 2 domains apart from the Root Domain having two accounts for each > domain. > 2)Dedicated the Zone to non root domain. > 3)Dedicated the one host to account in the same domain. > 4)Observed that 2 affinity groups are created and the while deploying the VM > i have selected both the affinity groups and the VM creation Failed. > The expected Result is the VM creation should be successful as the Zone is > dedicated and both affinity groups are selected. > The MS log shows the permission is granted to the account but the UI throws > an error message saying there is no way to detect the affinity group is > related to the account. > THE MS log is as below: > "2013-08-14 21:33:06,152 DEBUG [cloud.user.AccountManagerImpl] > (catalina-exec-20:null) Access granted to > Acct[7d48a75d-4b99-4e89-8b17-a66a9aac3098-kiran1] to Domain:2/Kiran/ by > DomainChecker_EnhancerByCloudStack_3d51253f > 2013-08-14 21:33:06,155 DEBUG [cloud.user.AccountManagerImpl] > (catalina-exec-20:null) Access to > Acct[7d48a75d-4b99-4e89-8b17-a66a9aac3098-kiran1] granted to > Acct[7d48a75d-4b99-4e89-8b17-a66a9aac3098-kiran1] by > DomainChecker_EnhancerByCloudStack_3d51253f" > The UI error message is as below: > There's no way to confirm Acct[7d48a75d-4b99-4e89-8b17-a66a9aac3098-kiran1] > has access to AffinityGroup[78de168c-aa92-4e72-8902-ff3c77ae8be8] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-4134) UI dosent fire the API with the Vlan values if the Vlan range is blank.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-4134. Fixed with the latest build hence closing the defect. > UI dosent fire the API with the Vlan values if the Vlan range is blank. > --- > > Key: CLOUDSTACK-4134 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4134 > 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: Kiran Koneti >Assignee: Jessica Wang >Priority: Critical > Fix For: 4.2.0 > > > When we try to edit the Vlan range from the UI and give blank values in the > Vlan range box and try to update the page the API fried doesn't have any Vlan > details as it is blank in the UI. > Eg: > I tried the below scenario: > 1)Created a setup with the Vlan range 1100-1109. > 2)Then created a network where the Vlan 1101 is associated with the network. > 3)Now I tried to edit the Vlan range and gave the blank value in the UI and > clicked update. > The API fired is as below > "10.147.38.237:8080/client/api?command=updatePhysicalNetwork&response=json&sessionkey=RRxhiAqmggnl%2F5oBGHNTm3DMj0M%3D&id=2409aeac-789a-4430-a9b7-fab66eb4b85c&_=1375867127326" > Here the Vlan details are not fired in the API. > Then I tried to edit it by giving the value 1102-1109 and the API fired was > as below: > "http://10.147.38.237:8080/client/api?command=updatePhysicalNetwork&response=json&sessionkey=RRxhiAqmggnl%2F5oBGHNTm3DMj0M%3D&id=2409aeac-789a-4430-a9b7-fab66eb4b85c&vlan=1102-1109&_=1375867287606"; > The API was fired currently with the Vlan values and there was a error > message as below > "physicalnetwork 200 has allocated vnets in the range 1100-1101 " the below > is the expected behaviour and the same should happen when we try to update > the UI with Blank details. > Note: Even the UI doesn't popup with any error message the Vlan range is not > getting deleted and we can see the same vlan range once we refresh the page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-3525) Documentation dosent point to the cloud-set-guest-password script link for Linux
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-3525. Closing this as dup for 1316 > Documentation dosent point to the cloud-set-guest-password script link for > Linux > > > Key: CLOUDSTACK-3525 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3525 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Kiran Koneti >Assignee: Radhika Nair > Fix For: Future > > > The Admin Guide for the Adding Password Management to Your Templates point a > link for the cloud-set-guest-password script for Linux.When tried to click on > the link it says oops cannot find the page. > The link provided in the doc is > http://cloudstack.org/dl/cloud-set-guest-password. > Please update the correct Link which would help in downloading the script > directly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-4375) VM Migration is failing from one cluster to another cluster.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kiran Koneti closed CLOUDSTACK-4375.
Verified this in the latest build and the issue is not observed hence closing
the issue.
> VM Migration is failing from one cluster to another cluster.
>
>
> Key: CLOUDSTACK-4375
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4375
> 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: Kiran Koneti
>Assignee: Sateesh Chodapuneedi
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.zip
>
>
> Steps followed are as below:
> 1)Created a Advanced Zone VMware setup with two clusters C1 & c2.
> 2)C1 having 2 hosts H1 and H2 and C2 having single host H3.
> 3)Dedicated the Zone to Domain D1 having Account A1 and A2.
> 4)Dedicated the Host H2 to Account A1, where H1 has the system Vm's in it.
> 5)Created a VM not using the affinity group for the host,the Router VM came
> up on the host H1and the VM is created on host H3 of the cluster C2.
> 6)Now tried to migrate the VM from H3 to H1 the migration was successful.
> 7)Now tried to migrate the VM from H1 to H3 again the VM migration failed
> with the below error message
> "2013-08-17 03:13:59,447 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null)
> ===START=== 10.101.255.76 -- GET
> command=migrateVirtualMachine&hostid=49537136-d44f-439a-937c-442ed74bd697&virtualmachineid=385b5edb-b6b2-4931-a4ab-8f9bd96acd14&response=json&sessionkey=3O%2FKhJ6pMFCAfLTZtIqQOY6R6%2F4%3D&_=1376669973550
> 2013-08-17 03:13:59,488 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-2:null) submit async job-178 = [
> b9d65e31-7cdf-4ce5-b93c-440287d8523f ], details: AsyncJobVO {id:178, userId:
> 2, accountId: 2, sessionKey: null, instanceType: None, instanceId: null, cmd:
> org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdOriginator: null,
> cmdInfo:
> {"response":"json","sessionkey":"3O/KhJ6pMFCAfLTZtIqQOY6R6/4\u003d","virtualmachineid":"385b5edb-b6b2-4931-a4ab-8f9bd96acd14","cmdEventType":"VM.MIGRATE","hostid":"49537136-d44f-439a-937c-442ed74bd697","ctxUserId":"2","httpmethod":"GET","_":"1376669973550","ctxAccountId":"2","ctxStartEventId":"618"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 6703101771911,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-08-17 03:13:59,489 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null)
> ===END=== 10.101.255.76 -- GET
> command=migrateVirtualMachine&hostid=49537136-d44f-439a-937c-442ed74bd697&virtualmachineid=385b5edb-b6b2-4931-a4ab-8f9bd96acd14&response=json&sessionkey=3O%2FKhJ6pMFCAfLTZtIqQOY6R6%2F4%3D&_=1376669973550
> 2013-08-17 03:13:59,491 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-119:job-178 = [ b9d65e31-7cdf-4ce5-b93c-440287d8523f ])
> Executing org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd for job-178
> = [ b9d65e31-7cdf-4ce5-b93c-440287d8523f ]
> 2013-08-17 03:13:59,528 INFO [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-119:job-178 = [ b9d65e31-7cdf-4ce5-b93c-440287d8523f ])
> Migrating VM[User|kiran14] to
> Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))]
> : Dest[Zone(3)-Pod(3)-Cluster(6)-Host(11)-Storage()]
> 2013-08-17 03:13:59,529 INFO [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-119:job-178 = [ b9d65e31-7cdf-4ce5-b93c-440287d8523f ]) Source
> and destination host are not in same cluster, unable to migrate to host: 11
> 2013-08-17 03:13:59,536 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-119:job-178 = [ b9d65e31-7cdf-4ce5-b93c-440287d8523f ])
> Unexpected exception while executing
> org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd
> com.cloud.utils.exception.CloudRuntimeException: Source and destination host
> are not in same cluster, unable to migrate to host: 11
> at
> com.cloud.vm.VirtualMachineManagerImpl.migrate(VirtualMachineManagerImpl.java:1452)
> at
> com.cloud.vm.UserVmManagerImpl.migrateVirtualMachine(UserVmManagerImpl.java:3981)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd.execute(MigrateVMCmd.java:147)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at
> java.util.concurrent.Executors$Runnable
[jira] [Closed] (CLOUDSTACK-4337) Dedicated Resources: Zone dedicated to an account should only be visible and accessible to that account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-4337. Verified this changes hence closing the defect. > Dedicated Resources: Zone dedicated to an account should only be visible and > accessible to that account > --- > > Key: CLOUDSTACK-4337 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4337 > 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: Prachi Damle >Assignee: Prachi Damle >Priority: Critical > Fix For: 4.2.0 > > > A Zone can be dedicated to an account. Thus such a zone should be visible and > accessible to that account only. > Currently such a zone is listed for any account in that domain. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-4221) Dedicated Resources: changes to associate the dedicated resource with the 'ExplicitDedication' affinity group
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-4221. Verified this changes hence closing the defect. > Dedicated Resources: changes to associate the dedicated resource with the > 'ExplicitDedication' affinity group > - > > Key: CLOUDSTACK-4221 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4221 > 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: Prachi Damle >Assignee: Prachi Damle >Priority: Critical > Fix For: 4.2.0 > > > The dedicated resources feature does not establish the correct relation > between dedicated resources and the ExplicitDedication’ affinity group that > needs to be created to use the resources during VM deployment. > Changes are needed to associate dedication with the dedication affinity > group. Since the group is chosen during VM deployment, only the dedicated > resources associated to the group should be considered for deployment. > This will also provide a better user experience since the affinity group will > be created when the resources are dedicated by the admin, and this group will > be available to the users during VM deployment. Users will not create a group > themselves anymore. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-4259) Dedicated Resources: createAffinityGroup API should not allow admin to create the group of this type through API
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-4259. Verified this changes hence closing the defect. > Dedicated Resources: createAffinityGroup API should not allow admin to create > the group of this type through API > > > Key: CLOUDSTACK-4259 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4259 > 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: Prachi Damle >Assignee: Prachi Damle >Priority: Critical > Fix For: 4.2.0 > > > Since the group gets created internally when resources are dedicated, API > should not allow the creation for admin too. This is to be sure that no > multiple groups get created for an account/domain of this type. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-4234) Dedicated Resources: When multiple dedication groups are chosen for VM deployment, dedicated resources belonging to both groups should be considered
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-4234. Verified this changes hence closing the defect. > Dedicated Resources: When multiple dedication groups are chosen for VM > deployment, dedicated resources belonging to both groups should be considered > > > Key: CLOUDSTACK-4234 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4234 > 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: Prachi Damle >Assignee: Prachi Damle >Priority: Critical > Fix For: 4.2.0 > > > Steps to reproduce: > Setup: 1 Pod -> 1 cluster -> 2 hosts > - dedicated a host to a user account > - dedicate the pod of that host to the account's domain - > - During vm deployment by the user, choose both the dedication groups. > - The dedicated host gets added to avoidlist and deployment only considers > the other host > Both host should get considered for deployment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-4504) VM creation ISD fainling using the Ubuntu ISO.
Kiran Koneti created CLOUDSTACK-4504:
Summary: VM creation ISD fainling using the Ubuntu ISO.
Key: CLOUDSTACK-4504
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4504
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Install and Setup
Affects Versions: 4.2.1
Reporter: Kiran Koneti
Priority: Blocker
Fix For: 4.2.1
1)Registered a Ubuntu 10.04 32 bit in the CS.
2)Tried to create a VM using the ISO then observed the below error message
"2013-08-26 21:28:58,345 DEBUG [agent.transport.Request]
(AgentManager-Handler-14:null) Seq 3-347996257: Processing: { Ans: , MgmtId:
6703101771911, via: 3, Ver: v1, Flags: 10,
[{"com.cloud.agent.api.storage.DownloadAnswer":{"jobId":"565318cc-d0b4-4365-aea2-044dedb938ea","downloadPct":100,"errorString":"Download
success, starting install
","downloadStatus":"DOWNLOAD_IN_PROGRESS","downloadPath":"/mnt/SecStorage/ec67adf1-b86c-3674-ad7f-46ddd34d104f/template/tmpl/2/202/dnld2917500853441314915tmp_","installPath":"template/tmpl/2/202/202-2-c006beb1-8a48-3ac2-b4d5-af1b6c940b5e.iso","templateSize":0,"templatePhySicalSize":0,"checkSum":"27aa354b8088527ffcd32007b51b25bf","result":true,"details":"Download
success, starting install ","wait":0}}] }
2013-08-26 21:29:00,477 DEBUG [cloud.server.StatsCollector]
(StatsCollector-1:null) StorageCollector is running...
^C
[root@Kiran-RHEl631 setup]# vi
/var/log/cloudstack/management/management-server.log
status: failure
residentOn: com.xensource.xenapi.Host@e79e523d
progress: 1.0
type:
result:
errorInfo: [INTERNAL_ERROR, xenopsd internal error:
XenguestHelper.Xenctrl_dom_linux_build_failure(2, " elf_xen_note_check: ERROR:
Will only load images built \\\"")]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
com.cloud.utils.exception.CloudRuntimeException: Unable to start VM(i-2-3-VM)
on host(fe1fce23-4155-4831-b669-a99988cd3259) due to Task failed! Task record:
uuid: d7d77fe7-2d04-35a2-df1f-200ca1a80bbc
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Mon Aug 26 12:06:14 IST 2013
finished: Mon Aug 26 12:06:17 IST 2013
status: failure
residentOn: com.xensource.xenapi.Host@e79e523d
progress: 1.0
type:
result:
errorInfo: [INTERNAL_ERROR, xenopsd internal error:
XenguestHelper.Xenctrl_dom_linux_build_failure(2, " elf_xen_note_check: ERROR:
Will only load images built \\\"")]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.startVM(CitrixResourceBase.java:3717)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1636)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:553)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at
com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:104)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)"
Atatching the MS logs for additional debugging.
The DB table entries for the Ubuntu templates for the Xen are as below:
mysql> select * from guest_os_hypervisor where guest_os_id in (select id from
guest_os where display_name like '%ubu%');
+-+-+-+-+
| id | hypervisor_type | guest_os_name | guest_os_id |
+-+-+-+-+
| 79 | XenServer | Other install media | 59 |
| 80 | XenServer | Other install media | 100 |
| 83 | XenServer | Other install media | 121 |
| 84 | XenServer | Other install media | 126 |
| 85 | XenServer | Other install media | 122 |
| 86 | XenServer | Other install media | 127 |
| 87 | XenServer | Other install media | 123 |
| 88 | XenServer | Other install media | 128 |
| 89 | XenServer | Other install media | 124 |
| 90 | XenServer | Other install media | 129 |
| 91 | XenServer | Other install media | 125 |
| 92 | XenServer | Other install media | 130 |
| 174 | VmWare
[jira] [Updated] (CLOUDSTACK-4504) VM creation ISD fainling using the Ubuntu ISO.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kiran Koneti updated CLOUDSTACK-4504:
-
Attachment: management-server.zip
> VM creation ISD fainling using the Ubuntu ISO.
> --
>
> Key: CLOUDSTACK-4504
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4504
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup
>Affects Versions: 4.2.1
>Reporter: Kiran Koneti
>Priority: Blocker
> Fix For: 4.2.1
>
> Attachments: management-server.zip
>
>
> 1)Registered a Ubuntu 10.04 32 bit in the CS.
> 2)Tried to create a VM using the ISO then observed the below error message
> "2013-08-26 21:28:58,345 DEBUG [agent.transport.Request]
> (AgentManager-Handler-14:null) Seq 3-347996257: Processing: { Ans: , MgmtId:
> 6703101771911, via: 3, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.storage.DownloadAnswer":{"jobId":"565318cc-d0b4-4365-aea2-044dedb938ea","downloadPct":100,"errorString":"Download
> success, starting install
> ","downloadStatus":"DOWNLOAD_IN_PROGRESS","downloadPath":"/mnt/SecStorage/ec67adf1-b86c-3674-ad7f-46ddd34d104f/template/tmpl/2/202/dnld2917500853441314915tmp_","installPath":"template/tmpl/2/202/202-2-c006beb1-8a48-3ac2-b4d5-af1b6c940b5e.iso","templateSize":0,"templatePhySicalSize":0,"checkSum":"27aa354b8088527ffcd32007b51b25bf","result":true,"details":"Download
> success, starting install ","wait":0}}] }
> 2013-08-26 21:29:00,477 DEBUG [cloud.server.StatsCollector]
> (StatsCollector-1:null) StorageCollector is running...
> ^C
> [root@Kiran-RHEl631 setup]# vi
> /var/log/cloudstack/management/management-server.log
> status: failure
> residentOn: com.xensource.xenapi.Host@e79e523d
> progress: 1.0
> type:
> result:
>errorInfo: [INTERNAL_ERROR, xenopsd internal error:
> XenguestHelper.Xenctrl_dom_linux_build_failure(2, " elf_xen_note_check:
> ERROR: Will only load images built \\\"")]
> otherConfig: {}
>subtaskOf: com.xensource.xenapi.Task@aaf13f6f
> subtasks: []
> com.cloud.utils.exception.CloudRuntimeException: Unable to start VM(i-2-3-VM)
> on host(fe1fce23-4155-4831-b669-a99988cd3259) due to Task failed! Task
> record: uuid: d7d77fe7-2d04-35a2-df1f-200ca1a80bbc
>nameLabel: Async.VM.start_on
> nameDescription:
>allowedOperations: []
>currentOperations: {}
> created: Mon Aug 26 12:06:14 IST 2013
> finished: Mon Aug 26 12:06:17 IST 2013
> status: failure
> residentOn: com.xensource.xenapi.Host@e79e523d
> progress: 1.0
> type:
> result:
>errorInfo: [INTERNAL_ERROR, xenopsd internal error:
> XenguestHelper.Xenctrl_dom_linux_build_failure(2, " elf_xen_note_check:
> ERROR: Will only load images built \\\"")]
> otherConfig: {}
>subtaskOf: com.xensource.xenapi.Task@aaf13f6f
> subtasks: []
> at
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.startVM(CitrixResourceBase.java:3717)
> at
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1636)
> at
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:553)
> at
> com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
> at
> com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:104)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)"
> Atatching the MS logs for additional debugging.
> The DB table entries for the Ubuntu templates for the Xen are as below:
> mysql> select * from guest_os_hypervisor where guest_os_id in (select id from
> guest_os where display_name like '%ubu%');
> +-+-+-+-+
> | id | hypervisor_type | guest_os_name | guest_os_id |
> +-+-+-+-+
> | 79 | XenServer | Other install media | 59 |
> | 80 | XenServer | Other install media | 100 |
> | 83 | XenServer | Other install media | 121 |
> | 84 | XenServer | Other install media | 126 |
> | 85 | XenServer | Other install media | 122 |
> | 86 | XenServer | Other install media | 127 |
> | 87 | XenServer | Other
[jira] [Updated] (CLOUDSTACK-4504) VM creation Is failing using the Ubuntu ISO with Xen 6.1 and 6.2
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kiran Koneti updated CLOUDSTACK-4504:
-
Priority: Major (was: Blocker)
> VM creation Is failing using the Ubuntu ISO with Xen 6.1 and 6.2
>
>
> Key: CLOUDSTACK-4504
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4504
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup
>Affects Versions: 4.2.1
>Reporter: Kiran Koneti
> Fix For: 4.2.1
>
> Attachments: management-server.zip
>
>
> 1)Registered a Ubuntu 10.04 32 bit in the CS.
> 2)Tried to create a VM using the ISO then observed the below error message
> "2013-08-26 21:28:58,345 DEBUG [agent.transport.Request]
> (AgentManager-Handler-14:null) Seq 3-347996257: Processing: { Ans: , MgmtId:
> 6703101771911, via: 3, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.storage.DownloadAnswer":{"jobId":"565318cc-d0b4-4365-aea2-044dedb938ea","downloadPct":100,"errorString":"Download
> success, starting install
> ","downloadStatus":"DOWNLOAD_IN_PROGRESS","downloadPath":"/mnt/SecStorage/ec67adf1-b86c-3674-ad7f-46ddd34d104f/template/tmpl/2/202/dnld2917500853441314915tmp_","installPath":"template/tmpl/2/202/202-2-c006beb1-8a48-3ac2-b4d5-af1b6c940b5e.iso","templateSize":0,"templatePhySicalSize":0,"checkSum":"27aa354b8088527ffcd32007b51b25bf","result":true,"details":"Download
> success, starting install ","wait":0}}] }
> 2013-08-26 21:29:00,477 DEBUG [cloud.server.StatsCollector]
> (StatsCollector-1:null) StorageCollector is running...
> ^C
> [root@Kiran-RHEl631 setup]# vi
> /var/log/cloudstack/management/management-server.log
> status: failure
> residentOn: com.xensource.xenapi.Host@e79e523d
> progress: 1.0
> type:
> result:
>errorInfo: [INTERNAL_ERROR, xenopsd internal error:
> XenguestHelper.Xenctrl_dom_linux_build_failure(2, " elf_xen_note_check:
> ERROR: Will only load images built \\\"")]
> otherConfig: {}
>subtaskOf: com.xensource.xenapi.Task@aaf13f6f
> subtasks: []
> com.cloud.utils.exception.CloudRuntimeException: Unable to start VM(i-2-3-VM)
> on host(fe1fce23-4155-4831-b669-a99988cd3259) due to Task failed! Task
> record: uuid: d7d77fe7-2d04-35a2-df1f-200ca1a80bbc
>nameLabel: Async.VM.start_on
> nameDescription:
>allowedOperations: []
>currentOperations: {}
> created: Mon Aug 26 12:06:14 IST 2013
> finished: Mon Aug 26 12:06:17 IST 2013
> status: failure
> residentOn: com.xensource.xenapi.Host@e79e523d
> progress: 1.0
> type:
> result:
>errorInfo: [INTERNAL_ERROR, xenopsd internal error:
> XenguestHelper.Xenctrl_dom_linux_build_failure(2, " elf_xen_note_check:
> ERROR: Will only load images built \\\"")]
> otherConfig: {}
>subtaskOf: com.xensource.xenapi.Task@aaf13f6f
> subtasks: []
> at
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.startVM(CitrixResourceBase.java:3717)
> at
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1636)
> at
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:553)
> at
> com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
> at
> com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:104)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)"
> Atatching the MS logs for additional debugging.
> The DB table entries for the Ubuntu templates for the Xen are as below:
> mysql> select * from guest_os_hypervisor where guest_os_id in (select id from
> guest_os where display_name like '%ubu%');
> +-+-+-+-+
> | id | hypervisor_type | guest_os_name | guest_os_id |
> +-+-+-+-+
> | 79 | XenServer | Other install media | 59 |
> | 80 | XenServer | Other install media | 100 |
> | 83 | XenServer | Other install media | 121 |
> | 84 | XenServer | Other install media | 126 |
> | 85 | XenServer | Other install media | 122 |
> | 86 | XenServer | Other install media | 127 |
> | 87 | XenServer | Oth
[jira] [Updated] (CLOUDSTACK-4504) VM creation Is failing using the Ubuntu ISO with Xen 6.1 and 6.2
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kiran Koneti updated CLOUDSTACK-4504:
-
Summary: VM creation Is failing using the Ubuntu ISO with Xen 6.1 and 6.2
(was: VM creation ISD fainling using the Ubuntu ISO.)
> VM creation Is failing using the Ubuntu ISO with Xen 6.1 and 6.2
>
>
> Key: CLOUDSTACK-4504
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4504
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup
>Affects Versions: 4.2.1
>Reporter: Kiran Koneti
>Priority: Blocker
> Fix For: 4.2.1
>
> Attachments: management-server.zip
>
>
> 1)Registered a Ubuntu 10.04 32 bit in the CS.
> 2)Tried to create a VM using the ISO then observed the below error message
> "2013-08-26 21:28:58,345 DEBUG [agent.transport.Request]
> (AgentManager-Handler-14:null) Seq 3-347996257: Processing: { Ans: , MgmtId:
> 6703101771911, via: 3, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.storage.DownloadAnswer":{"jobId":"565318cc-d0b4-4365-aea2-044dedb938ea","downloadPct":100,"errorString":"Download
> success, starting install
> ","downloadStatus":"DOWNLOAD_IN_PROGRESS","downloadPath":"/mnt/SecStorage/ec67adf1-b86c-3674-ad7f-46ddd34d104f/template/tmpl/2/202/dnld2917500853441314915tmp_","installPath":"template/tmpl/2/202/202-2-c006beb1-8a48-3ac2-b4d5-af1b6c940b5e.iso","templateSize":0,"templatePhySicalSize":0,"checkSum":"27aa354b8088527ffcd32007b51b25bf","result":true,"details":"Download
> success, starting install ","wait":0}}] }
> 2013-08-26 21:29:00,477 DEBUG [cloud.server.StatsCollector]
> (StatsCollector-1:null) StorageCollector is running...
> ^C
> [root@Kiran-RHEl631 setup]# vi
> /var/log/cloudstack/management/management-server.log
> status: failure
> residentOn: com.xensource.xenapi.Host@e79e523d
> progress: 1.0
> type:
> result:
>errorInfo: [INTERNAL_ERROR, xenopsd internal error:
> XenguestHelper.Xenctrl_dom_linux_build_failure(2, " elf_xen_note_check:
> ERROR: Will only load images built \\\"")]
> otherConfig: {}
>subtaskOf: com.xensource.xenapi.Task@aaf13f6f
> subtasks: []
> com.cloud.utils.exception.CloudRuntimeException: Unable to start VM(i-2-3-VM)
> on host(fe1fce23-4155-4831-b669-a99988cd3259) due to Task failed! Task
> record: uuid: d7d77fe7-2d04-35a2-df1f-200ca1a80bbc
>nameLabel: Async.VM.start_on
> nameDescription:
>allowedOperations: []
>currentOperations: {}
> created: Mon Aug 26 12:06:14 IST 2013
> finished: Mon Aug 26 12:06:17 IST 2013
> status: failure
> residentOn: com.xensource.xenapi.Host@e79e523d
> progress: 1.0
> type:
> result:
>errorInfo: [INTERNAL_ERROR, xenopsd internal error:
> XenguestHelper.Xenctrl_dom_linux_build_failure(2, " elf_xen_note_check:
> ERROR: Will only load images built \\\"")]
> otherConfig: {}
>subtaskOf: com.xensource.xenapi.Task@aaf13f6f
> subtasks: []
> at
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.startVM(CitrixResourceBase.java:3717)
> at
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1636)
> at
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:553)
> at
> com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
> at
> com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:104)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)"
> Atatching the MS logs for additional debugging.
> The DB table entries for the Ubuntu templates for the Xen are as below:
> mysql> select * from guest_os_hypervisor where guest_os_id in (select id from
> guest_os where display_name like '%ubu%');
> +-+-+-+-+
> | id | hypervisor_type | guest_os_name | guest_os_id |
> +-+-+-+-+
> | 79 | XenServer | Other install media | 59 |
> | 80 | XenServer | Other install media | 100 |
> | 83 | XenServer | Other install media | 121 |
> | 84 | XenServer | Other install media | 126 |
> | 85 | XenServer | Other install medi
[jira] [Closed] (CLOUDSTACK-3851) [VMWare] VM start fails with NPE while trying to retrieve cores per socket
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kiran Koneti closed CLOUDSTACK-3851.
Steps of verification:
Added a cluster with ESX 4.1 added to Vcenter 5.1 to the CS and tried to deploy
VM and the VM deployment was successful hence closing the defect.
> [VMWare] VM start fails with NPE while trying to retrieve cores per socket
> --
>
> Key: CLOUDSTACK-3851
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3851
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.2.0
>Reporter: Likitha Shetty
>Assignee: Sateesh Chodapuneedi
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: Logs_DB.rar
>
>
> VM start failed multiple times with the below error,
> 2013-07-23 10:57:16,955 DEBUG [cloud.api.ApiServlet] (catalina-exec-9:null)
> ===START=== 10.252.192.53 -- GET
> command=queryAsyncJobResult&jobId=05569d7e-8630-4481-a7cf-2d4831ba38fe&response=json&sessionkey=F8Cw9e7dmEvSRFlZRi1DKxUgHPQ%3D&_=1374571983764
> 2013-07-23 10:57:17,023 DEBUG [cloud.api.ApiServlet] (catalina-exec-9:null)
> ===END=== 10.252.192.53 -- GET
> command=queryAsyncJobResult&jobId=05569d7e-8630-4481-a7cf-2d4831ba38fe&response=json&sessionkey=F8Cw9e7dmEvSRFlZRi1DKxUgHPQ%3D&_=1374571983764
> 2013-07-23 10:57:17,123 DEBUG [vmware.mo.HostMO] (DirectAgent-66:10.147.40.8)
> find VM i-2-13-VM on host
> 2013-07-23 10:57:17,123 DEBUG [vmware.mo.HostMO] (DirectAgent-66:10.147.40.8)
> load VM cache on host
> 2013-07-23 10:57:17,135 INFO [vmware.mo.HypervisorHostHelper]
> (DirectAgent-66:10.147.40.8) Blank VM: i-2-13-VM is ready for use
> 2013-07-23 10:57:17,135 DEBUG [vmware.mo.HostMO] (DirectAgent-66:10.147.40.8)
> find VM i-2-13-VM on host
> 2013-07-23 10:57:17,135 DEBUG [vmware.mo.HostMO] (DirectAgent-66:10.147.40.8)
> VM i-2-13-VM found in host cache
> 2013-07-23 10:57:17,408 WARN [vmware.resource.VmwareResource]
> (DirectAgent-66:10.147.40.8) StartCommand failed due to Exception:
> java.lang.NullPointerException
> Message: null
> java.lang.NullPointerException
> at
> com.cloud.hypervisor.vmware.mo.VirtualMachineMO.getCoresPerSocket(VirtualMachineMO.java:2203)
> at
> com.cloud.hypervisor.vmware.mo.VirtualMachineMO.isCpuHotAddSupported(VirtualMachineMO.java:2244)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2598)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:520)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
> 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.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
> 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-07-23 10:57:17,413 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-66:null) Seq 6-1231552610: Response Received:
> 2013-07-23 10:57:17,415 DEBUG [agent.transport.Request] (DirectAgent-66:null)
> Seq 6-1231552610: Processing: { Ans: , MgmtId: 7635042566263, via: 6, Ver:
> v1, Flags: 10,
> [{"com.cloud.agent.api.StartAnswer":{"vm":{"id":13,"name":"i-2-13-VM","bootloader":"HVM","type":"User","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":536870912,"maxRam":536870912,"arch":"x86_64","os":"CentOS
> 5.3
> (64-bit)","bootArgs":"","rebootOnCrash":false,"enableHA":false,"limitCpuUse":false,"enableDynamicallyScaleVm":false,"vncPassword":"1e2cc9569b294009","params":{"nicAdapter":"E1000","enable.dynamic.scaling":"false","nestedVirtualizationFlag":"false","rootDiskController":"ide"},"uuid":"a92658ea-5534-4b40-a066-9bc9b2a5a607","disks":[{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"a3ac26fc-92da-476c-8e45-c2421e24e041","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"bd186911-97af-371a-9b26-fac999fc98a4","id":2,"poolType":"NetworkFilesystem","host":"10.147.28.7","path":"/export/home/prashant/primary2","port":2049}},"name":"ROOT-13","size":0,"path":"ROOT-13-16","volumeId":16,"vmName":"i-2-13-VM","accountId":2,"format":"OVA","id":16}},"diskSeq":0,"type":"ROOT
[jira] [Closed] (CLOUDSTACK-3552) Domain/Account details are not displayed for the implicitly dedicated hosts neither in UI nor in DB.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-3552. Closing this as per Dev's comments. > Domain/Account details are not displayed for the implicitly dedicated hosts > neither in UI nor in DB. > > > Key: CLOUDSTACK-3552 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3552 > 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: Kiran Koneti >Assignee: Devdeep Singh >Priority: Critical > Fix For: 4.2.0 > > > When a host is implicitly dedicated to an domain/account then the dedication > details for that particular account is not recorded neither in DB nor in UI. > The op_host_planner_reservation; shows the details as of weather a host is > dedicated or not but it doesn't make a note of to which account it is > dedicated . > The op_host_planner_reservation; table details are as below: > mysql> select * from op_host_planner_reservation; > +++++-++ > | id | data_center_id | pod_id | cluster_id | host_id | resource_usage | > +++++-++ > | 1 | 1 | 1 | 1 | 1 | Shared | > +++++-++ > 1 row in set (0.00 sec) > This will be an issue when the number of accounts and hosts in the setup > increases. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-3188) Not able to add network to a VM after installing the Vmtools on a windows VM.(regression)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kiran Koneti closed CLOUDSTACK-3188.
Closing the issue as it is not reproduced with the latest build.
> Not able to add network to a VM after installing the Vmtools on a windows
> VM.(regression)
> -
>
> Key: CLOUDSTACK-3188
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3188
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Devices
>Affects Versions: 4.2.0
>Reporter: Kiran Koneti
>Assignee: Saksham Srivastava
>Priority: Critical
> Fix For: 4.2.0
>
>
> Steps followed are as below:
> 1)Installed a VMware Advanced Zone setup.
> 2)once the system VM's are up added a Windows template.
> 3)Created a Vm using the windows864 bit template.
> 4)Once the VM came up tried to add a network to the VM then the below error
> message is observed which says the VM tools is not installed
> "2013-06-25 15:29:36,780 DEBUG [agent.transport.Request]
> (Job-Executor-18:job-151) Seq 5-1148784739: Executing: { Cmd , MgmtId:
> 7159676928023, via: 5, Ver: v1, Flags: 100111,
> [{"PlugNicCommand":{"nic":{"deviceId":1,"networkRateMbps":200,"defaultNic":false,"uuid":"91a77dc9-9958-4e5d-8992-8e5a50e9e6db","ip":"10.1.4.218","netmask":"255.255.255.0","gateway":"10.1.4.1","mac":"02:00:3e:fb:00:09","dns1":"10.103.128.16","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://1057","isolationUri":"vlan://1057","isSecurityGroupEnabled":false},"instanceName":"i-8-51-VM","vmType":"User","wait":0}}]
> }
> 2013-06-25 15:29:36,781 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-250:null) Seq 5-1148784739: Executing request
> 2013-06-25 15:29:36,782 INFO [vmware.resource.VmwareResource]
> (DirectAgent-250:10.147.40.24) Executing resource PlugNicCommand
> {"nic":{"deviceId":1,"networkRateMbps":200,"defaultNic":false,"uuid":"91a77dc9-9958-4e5d-8992-8e5a50e9e6db","ip":"10.1.4.218","netmask":"255.255.255.0","gateway":"10.1.4.1","mac":"02:00:3e:fb:00:09","dns1":"10.103.128.16","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://1057","isolationUri":"vlan://1057","isSecurityGroupEnabled":false},"instanceName":"i-8-51-VM","vmType":"User","wait":0}
> 2013-06-25 15:29:36,783 DEBUG [vmware.mo.HostMO]
> (DirectAgent-250:10.147.40.24) find VM i-8-51-VM on host
> 2013-06-25 15:29:36,783 DEBUG [vmware.mo.HostMO]
> (DirectAgent-250:10.147.40.24) load VM cache on host
> 2013-06-25 15:29:36,802 DEBUG [vmware.resource.VmwareResource]
> (DirectAgent-250:10.147.40.24) vmware tools is not installed or not running,
> cannot add nic to vm i-8-51-VM
> 2013-06-25 15:29:36,803 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-250:null) Seq 5-1148784739: Response Received:
> 2013-06-25 15:29:36,803 DEBUG [agent.transport.Request]
> (DirectAgent-250:null) Seq 5-1148784739: Processing: { Ans: , MgmtId:
> 7159676928023, via: 5, Ver: v1, Flags: 110,
> [{"PlugNicAnswer":{"result":false,"details":"Unable to execute PlugNicCommand
> due to vmware tools is not installed or not running, cannot add nic to vm
> i-8-51-VM","wait":0}}] }
> 2013-06-25 15:29:36,804 DEBUG [agent.transport.Request]
> (Job-Executor-18:job-151) Seq 5-1148784739: Received: { Ans: , MgmtId:
> 7159676928023, via: 5, Ver: v1, Flags: 110, { PlugNicAnswer } }
> 2013-06-25 15:29:36,804 WARN [cloud.vm.UserVmManagerImpl]
> (Job-Executor-18:job-151) Unable to plug nic for VM[User|win864vmw] due to:
> due to: Unable to execute PlugNicCommand due to vmware tools is not installed
> or not running, cannot add nic to vm i-8-51-VM
> 2013-06-25 15:29:36,808 WARN [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-18:job-151) Failed to plug nic to the vm VM[User|win864vmw] in
> network Ntwk[226|Guest|8]
> 2013-06-25 15:29:36,806 DEBUG [agent.manager.AgentAttache]
> (DirectAgent-250:null) Seq 5-1148784739: No more commands found
> 2013-06-25 15:29:36,830 DEBUG [cloud.network.NetworkModelImpl]
> (Job-Executor-18:job-151) Service SecurityGroup is not supported in the
> network id=226
> 2013-06-25 15:29:36,854 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-18:job-151) Removed nic id=126
> 2013-06-25 15:29:36,857 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-18:job-151) Revoving nic secondary ip entry ...
> 2013-06-25 15:29:36,858 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-18:job-151) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd
> com.cloud.utils.exception.CloudRuntimeException: Unable to add NIC to
> VM[User|win864vmw]
> at
> com.cloud.vm.UserVmManagerImpl.addNicToVirtualMachine(UserV
[jira] [Updated] (CLOUDSTACK-3616) [VMware] Failed to create template from volume (volume is created from snapshot of data volume)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti updated CLOUDSTACK-3616: - Priority: Blocker (was: Critical) Changing this as blocker as it is blocking from testing the second Cycle validation of multiple features. > [VMware] Failed to create template from volume (volume is created from > snapshot of data volume) > --- > > Key: CLOUDSTACK-3616 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3616 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller, VMware >Affects Versions: 4.2.0 > Environment: VMware ESXi 5.0 > ACS master branch >Reporter: Sateesh Chodapuneedi >Assignee: edison su >Priority: Blocker > Fix For: 4.2.0 > > > When tried to created template from volume created from snapshot we see > following error in Cloudstack deployed over VMware. > 2013-07-18 00:02:52,273 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-28:job-65 = [ ababda19-bd16-4e7c-aa92-39b948ad120f ]) > Unexpected exception while executing > org.apache.cloudstack.api.command.user.template.CreateTemplateCmd > com.cloud.utils.exception.CloudRuntimeException: Failed to create template > at > com.cloud.template.TemplateManagerImpl.createPrivateTemplate(TemplateManagerImpl.java:1369) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.template.CreateTemplateCmd.execute(CreateTemplateCmd.java:258) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:538) > 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) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-3778) SSVM VM fails to create for the first time with message "specified key already exists".
Kiran Koneti created CLOUDSTACK-3778: Summary: SSVM VM fails to create for the first time with message "specified key already exists". Key: CLOUDSTACK-3778 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3778 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.2.0 Environment: VMware Reporter: Kiran Koneti Priority: Critical Fix For: 4.2.0 When we try to create a Advanced Zone setup when the first SSVM tries to come up the Vcenter says 'The specified key, name, or identifier already exists." and the SSVM creation fails for the first time and later then the SSVM comes up with another name s-3-vm. The steps are as follows: 1)Installed the CS using the latest build. 2)Added a host which is freshly installed to the cluster in the VCenter. 3)Added the Vcenter details to the CS and the setup started creating the system VM's. 4)Once the root volume is created for the SSVM the VM named "s-1-vm" created. 5)Then the VM gets deleted before it is powered on throwing the error message as below "2013-07-24 20:26:51,680 WARN [vmware.resource.VmwareResource] (DirectAgent-8:10.147.40.18) StartCommand failed due to Exception: com.vmware.vim25.AlreadyExists message: [] com.vmware.vim25.AlreadyExistsFaultMsg: The specified key, name, or identifier already exists. at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:532) at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:130) at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:108) 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:107) at $Proxy90.addPortGroup(Unknown Source) at com.cloud.hypervisor.vmware.mo.HostNetworkSystemMO.addPortGroup(HostNetworkSystemMO.java:38) at com.cloud.hypervisor.vmware.mo.HostMO.createPortGroup(HostMO.java:389) at com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.prepareNetwork(HypervisorHostHelper.java:961) at com.cloud.hypervisor.vmware.resource.VmwareResource.prepareNetworkFromNicInfo(VmwareResource.java:3149) at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2775) at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:520) at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)" 6)Later it creates the root volume for one more SSVM and then the s-3-vm comes up without any issues. 7)all the system VM functionalities are normal. Attaching the Management server Logs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3778) SSVM VM fails to create for the first time with message "specified key already exists".
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti updated CLOUDSTACK-3778: - Attachment: management-server.zip > SSVM VM fails to create for the first time with message "specified key > already exists". > --- > > Key: CLOUDSTACK-3778 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3778 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.2.0 > Environment: VMware >Reporter: Kiran Koneti >Priority: Critical > Fix For: 4.2.0 > > Attachments: management-server.zip > > > When we try to create a Advanced Zone setup when the first SSVM tries to come > up the Vcenter says 'The specified key, name, or identifier already exists." > and the SSVM creation fails for the first time and later then the SSVM comes > up with another name s-3-vm. > The steps are as follows: > 1)Installed the CS using the latest build. > 2)Added a host which is freshly installed to the cluster in the VCenter. > 3)Added the Vcenter details to the CS and the setup started creating the > system VM's. > 4)Once the root volume is created for the SSVM the VM named "s-1-vm" created. > 5)Then the VM gets deleted before it is powered on throwing the error message > as below > "2013-07-24 20:26:51,680 WARN [vmware.resource.VmwareResource] > (DirectAgent-8:10.147.40.18) StartCommand failed due to Exception: > com.vmware.vim25.AlreadyExists > message: [] > com.vmware.vim25.AlreadyExistsFaultMsg: The specified key, name, or > identifier already exists. > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:532) > at > com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:130) > at > com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:108) > 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:107) > at $Proxy90.addPortGroup(Unknown Source) > at > com.cloud.hypervisor.vmware.mo.HostNetworkSystemMO.addPortGroup(HostNetworkSystemMO.java:38) > at > com.cloud.hypervisor.vmware.mo.HostMO.createPortGroup(HostMO.java:389) > at > com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.prepareNetwork(HypervisorHostHelper.java:961) > at > com.cloud.hypervisor.vmware.resource.VmwareResource.prepareNetworkFromNicInfo(VmwareResource.java:3149) > at > com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2775) > at > com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:520) > at > com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)" > 6)Later it creates the root volume for one more SSVM and then the s-3-vm > comes up without any issues. > 7)all the system VM functionalities are normal. > Attaching the Management server Logs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-3382) Unable to Migrate VM's If the hosts are implicitly or explicitly dedicated.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-3382. working fine as per the FS hence closing the defect. > Unable to Migrate VM's If the hosts are implicitly or explicitly dedicated. > --- > > Key: CLOUDSTACK-3382 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3382 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.2.0 >Reporter: Kiran Koneti >Assignee: Saksham Srivastava >Priority: Blocker > Fix For: 4.2.0 > > > The details of the defect are as follows: > 1)I have created a Advanced Zone setup with two hosts. > 2)Then created a VM using the Strict Implicit for one account and created > another VM with different account without using any dedication. > 3)two VM's are created on two hosts available and one is implicitly dedicated > host and other one is a shared host. > 4)then tried to migrate the VM from one account to another and clicked on the > UI option available. > Observed that the there is a popup saying no suitable host found. > But according to the FS of the Dedicated resources Zone/pod/cluster/host it > says as below: > "Migration of VMs > 1.If VM to be migrated is non-dedicated: > a.if destination host is implicitly or explicitly dedicated, migrate it to > that host, but an alert is generated > b.if destination host is non-dedicated, migrate it to the destination host. > 2.If VM to be migrated is dedicated > a.if destination host is implicitly or explicitly dedicated to the same > account, migrate it to that host. > b.if destination host is implicitly or explicitly dedicated to different > account, migrate it to that host, but an alert is generated > c.if destination host is non-dedicated, migrate it to that host but an alert > is generated" > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-3903) Snapshot Creation Fails in Vmware setup with permissions issue.
Kiran Koneti created CLOUDSTACK-3903:
Summary: Snapshot Creation Fails in Vmware setup with permissions
issue.
Key: CLOUDSTACK-3903
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3903
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Snapshot
Affects Versions: 4.2.0
Environment: VMware.
Reporter: Kiran Koneti
Priority: Blocker
Fix For: 4.2.0
Steps followed are as below:
1)Created an Advanced ZOne setup in the VMware.
2)Created a VM with root disk and Data disk,.
3)Once the VM is up tried to take the snapshot of the Root disk.
4)The snapshot creation was initiated but failed to create the snapshot as
there are no permissions in the secondary storage to create directory for the
snapshot.
The error messages are as below:
2013-07-29 21:14:28,373 DEBUG [storage.resource.VmwareStorageProcessor]
(DirectAgent-9:10.147.40.18) Exit value is 1
2013-07-29 21:14:28,384 DEBUG [storage.resource.VmwareStorageProcessor]
(DirectAgent-9:10.147.40.18) mkdir: cannot create directory
`/var/cloudstack/mnt/VM/6703101771911.e487dcd/snapshots': Permission denied
2013-07-29 21:15:03,574 ERROR [storage.resource.VmwareStorageProcessor]
(DirectAgent-9:10.147.40.18) Unexpecpted exception
java.lang.Exception: unable to prepare snapshot backup directory
at
com.cloud.storage.resource.VmwareStorageProcessor.exportVolumeToSecondaryStroage(VmwareStorageProcessor.java:960)
at
com.cloud.storage.resource.VmwareStorageProcessor.backupSnapshotToSecondaryStorage(VmwareStorageProcessor.java:999)
at
com.cloud.storage.resource.VmwareStorageProcessor.backupSnapshot(VmwareStorageProcessor.java:1072)
at
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:84)
at
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:49)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:562)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
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.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
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-07-29 21:15:03,609 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-9:null) Seq 1-1697251555: Response Received:
2013-07-29 21:15:03,610 DEBUG [agent.transport.Request] (DirectAgent-9:null)
Seq 1-1697251555: Processing: { Ans: , MgmtId: 6703101771911, via: 1, Ver: v1,
Flags: 10,
[{"org.apache.cloudstack.storage.command.CopyCmdAnswer":{"result":false,"details":"BackupSnapshotCommand
exception: java.lang.Exception: unable to prepare snapshot backup
directory","wait":0}}] }
2013-07-29 21:15:03,610 DEBUG [agent.transport.Request] (Job-Executor-14:job-14
= [ 353da542-80f1-465b-ad37-65610a8caf4d ]) Seq 1-1697251555: Received: { Ans:
, MgmtId: 6703101771911, via: 1, Ver: v1, Flags: 10, { CopyCmdAnswer } }
2013-07-29 21:15:03,699 DEBUG [storage.snapshot.SnapshotManagerImpl]
(Job-Executor-14:job-14 = [ 353da542-80f1-465b-ad37-65610a8caf4d ]) Failed to
create snapshot
com.cloud.utils.exception.CloudRuntimeException: BackupSnapshotCommand
exception: java.lang.Exception: unable to prepare snapshot backup directory
at
org.apache.cloudstack.storage.snapshot.SnapshotServiceImpl.backupSnapshot(SnapshotServiceImpl.java:286)
at
org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy.backupSnapshot(XenserverSnapshotStrategy.java:127)
at
org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy.takeSnapshot(XenserverSnapshotStrategy.java:219)
at
com.cloud.storage.snapshot.SnapshotManagerImpl.takeSnapshot(SnapshotManagerImpl.java:994)
at
org.apache.cloudstack.storage.volume.VolumeServiceImpl.takeSnapshot(VolumeServiceImpl.java:1222)
at
com.cloud.storage.VolumeManagerImpl.takeSnapshot(VolumeManagerImpl.java:2680)
at
org.apache.cloudstack.api.command.user.snapshot.CreateSnapshotCmd.execute(CreateSnapshotCmd.java:170)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
at
com.cloud.async.AsyncJobManag
[jira] [Reopened] (CLOUDSTACK-2064) The Vmware template dosent have permissions to be copied from secondary storage.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti reopened CLOUDSTACK-2064: -- Re opening this as we still see the issue and was also observed in the customer environment. > The Vmware template dosent have permissions to be copied from secondary > storage. > > > Key: CLOUDSTACK-2064 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2064 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.1.0, 4.2.0 >Reporter: Kiran Koneti >Assignee: Hugo Trippaers >Priority: Critical > Fix For: 4.1.0, 4.2.0 > > > When the VMware template is seeded to the secondary storage and while trying > to create the system Vm's there is a error message saying no permission to > tar the routing-8.ova > The error message is as below. > "2013-04-17 11:33:18,074 ERROR [vmware.manager.VmwareStorageManagerImpl] > (DirectAgent-4:10.102.192.18) Unable to execute PrimaryStorageDownloadCommand > due to exception > java.io.FileNotFoundException: > /var/cloudstack/mnt/VM/73143235720.4a5f0cef/template/tmpl/1/8/systemvmtemplate-2013-04-15-master-vmware.ovf > (Permission denied) > > [root@rhel63 management]# ll /var/cloudstack/mnt/VM/ > total 20 > drwxrwxrwx. 2 cloud cloud 4096 Apr 17 10:34 73143235720.154199bd > drwxrwxrwx. 5 root bin 4096 Apr 17 11:35 73143235720.4a5f0cef > drwxrwxrwx. 2 cloud cloud 4096 Apr 16 11:29 73143235720.4c8848c4 > drwxrwxrwx. 2 cloud cloud 4096 Apr 16 11:54 73143235720.525f3d5f > drwxrwxrwx. 2 cloud cloud 4096 Apr 17 10:44 73143235720.526d73ac > [root@rhel63 management]# ll /var/cloudstack/mnt/VM/73143235720.4a5f0cef/ > drwxrwxr-x. 2 cloud cloud 4096 Apr 17 11:35 systemvm > drwxr-xr-x. 3 root root 4096 Apr 17 09:41 template > [root@rhel63 management]# ll > /var/cloudstack/mnt/VM/73143235720.4a5f0cef/template/ > drwxr-xr-x. 3 root root 4096 Apr 17 09:41 tmpl > -rw-r--r--. 1 root root 260070912 Apr 17 09:56 > 56058ae3-12ea-4bbc-838c-f2e25ceba314.ova > -rw---. 1 root root 260057600 Apr 16 09:49 > systemvmtemplate-2013-04-15-master-vmware-disk1.vmdk > -rw---. 1 root root 12178 Apr 16 09:49 > systemvmtemplate-2013-04-15-master-vmware.ovf > -rw-r--r--. 1 root root 283 Apr 17 10:00 template.properties" > There is a workaround for the same. > After seeding the template if we change the permissions of the template in > the secondary storage (i.e give read/write permission) then the template is > seeded properly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (CLOUDSTACK-3616) [VMware] Failed to create template from volume (volume is created from snapshot of data volume)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti reopened CLOUDSTACK-3616: -- Reopening this as i see the error message again with the latest Build. 2013-07-29 22:28:58,489 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-23:job-22 = [ 93a923d2-8b56-4a97-9d1b-7efc5d77a970 ]) Unexpected exception while executing org.apache.cloudstack.api.command.user.template.CreateTemplateCmd com.cloud.utils.exception.CloudRuntimeException: Failed to create template at com.cloud.template.TemplateManagerImpl.createPrivateTemplate(TemplateManagerImpl.java:1360) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.template.CreateTemplateCmd.execute(CreateTemplateCmd.java:263) 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:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) 2013-07-29 22:28:58,513 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-23:job-22 = [ 93a923d2-8b56-4a97-9d1b-7efc5d77a970 ]) Complete async job-22 = [ 93a923d2-8b56-4a97-9d1b-7efc5d77a970 ], jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Failed to create template This error message is observed when tried to create a template from the snapshot. > [VMware] Failed to create template from volume (volume is created from > snapshot of data volume) > --- > > Key: CLOUDSTACK-3616 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3616 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller, VMware >Affects Versions: 4.2.0 > Environment: VMware ESXi 5.0 > ACS master branch >Reporter: Sateesh Chodapuneedi >Assignee: edison su >Priority: Blocker > Fix For: 4.2.0 > > > When tried to created template from volume created from snapshot we see > following error in Cloudstack deployed over VMware. > 2013-07-18 00:02:52,273 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-28:job-65 = [ ababda19-bd16-4e7c-aa92-39b948ad120f ]) > Unexpected exception while executing > org.apache.cloudstack.api.command.user.template.CreateTemplateCmd > com.cloud.utils.exception.CloudRuntimeException: Failed to create template > at > com.cloud.template.TemplateManagerImpl.createPrivateTemplate(TemplateManagerImpl.java:1369) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.template.CreateTemplateCmd.execute(CreateTemplateCmd.java:258) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:538) > 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) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (CLOUDSTACK-3616) [VMware] Failed to create template from volume (volume is created from snapshot of data volume)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722369#comment-13722369 ] Kiran Koneti edited comment on CLOUDSTACK-3616 at 7/29/13 11:39 AM: Reopening this as i see the error message again with the latest Build. 2013-07-29 22:28:58,489 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-23:job-22 = [ 93a923d2-8b56-4a97-9d1b-7efc5d77a970 ]) Unexpected exception while executing org.apache.cloudstack.api.command.user.template.CreateTemplateCmd com.cloud.utils.exception.CloudRuntimeException: Failed to create template at com.cloud.template.TemplateManagerImpl.createPrivateTemplate(TemplateManagerImpl.java:1360) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.template.CreateTemplateCmd.execute(CreateTemplateCmd.java:263) 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:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) 2013-07-29 22:28:58,513 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-23:job-22 = [ 93a923d2-8b56-4a97-9d1b-7efc5d77a970 ]) Complete async job-22 = [ 93a923d2-8b56-4a97-9d1b-7efc5d77a970 ], jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Failed to create template This error message is observed when tried to create a template from the snapshot.Observed it in the VMware Setup. was (Author: kiran_koneti): Reopening this as i see the error message again with the latest Build. 2013-07-29 22:28:58,489 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-23:job-22 = [ 93a923d2-8b56-4a97-9d1b-7efc5d77a970 ]) Unexpected exception while executing org.apache.cloudstack.api.command.user.template.CreateTemplateCmd com.cloud.utils.exception.CloudRuntimeException: Failed to create template at com.cloud.template.TemplateManagerImpl.createPrivateTemplate(TemplateManagerImpl.java:1360) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.template.CreateTemplateCmd.execute(CreateTemplateCmd.java:263) 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:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) 2013-07-29 22:28:58,513 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-23:job-22 = [ 93a923d2-8b56-4a97-9d1b-7efc5d77a970 ]) Complete async job-22 = [ 93a923d2-8b56-4a97-9d1b-7efc5d77a970 ], jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Failed to create template This error message is observed when tried to create a template from the snapshot. > [VMware] Failed to create template from volume (volume is created from > snapshot of data volume) > --- > > Key: CLOUDSTACK-3616 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3616 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller, VMware >Affects Versions: 4.2.0 > Environment: VMware ESXi 5.0 > ACS master branch >Reporter: Sateesh Chodapuneedi >Assignee: edison su >Priority: Blocker > Fix For: 4.2.0 > > > When tried to created template from volume created from snapshot we see > following error in Cloudstack deployed over VMware. > 2013-07-18 00:02:52,273 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-28:job-65 = [ ababda19-bd16-4e7c-aa92-39b948ad120f ]) > Unexpected exception while executing > org.apache.cloud
[jira] [Reopened] (CLOUDSTACK-3616) [VMware] Failed to create template from volume (volume is created from snapshot of data volume)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti reopened CLOUDSTACK-3616: -- Hi Edison, The steps are as below: 1)Created a VM on the VMware and took the snapshot of the Root volume. 2)From the root volume tried to create a template and the template creation is failed with the below posted error message. 3)I have specified the same in the bottom line of my previous comment. Hence reopening the defect. > [VMware] Failed to create template from volume (volume is created from > snapshot of data volume) > --- > > Key: CLOUDSTACK-3616 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3616 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller, VMware >Affects Versions: 4.2.0 > Environment: VMware ESXi 5.0 > ACS master branch >Reporter: Sateesh Chodapuneedi >Assignee: edison su >Priority: Blocker > Fix For: 4.2.0 > > > When tried to created template from volume created from snapshot we see > following error in Cloudstack deployed over VMware. > 2013-07-18 00:02:52,273 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-28:job-65 = [ ababda19-bd16-4e7c-aa92-39b948ad120f ]) > Unexpected exception while executing > org.apache.cloudstack.api.command.user.template.CreateTemplateCmd > com.cloud.utils.exception.CloudRuntimeException: Failed to create template > at > com.cloud.template.TemplateManagerImpl.createPrivateTemplate(TemplateManagerImpl.java:1369) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.template.CreateTemplateCmd.execute(CreateTemplateCmd.java:258) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:538) > 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) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-3616) [VMware] Failed to create template from volume (volume is created from snapshot of data volume)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti resolved CLOUDSTACK-3616. -- Resolution: Fixed Sorry reopened a wrong issue as i found the error messages similar to the template creations failure.the issue for that is CS-2481 which is currently not reproduced in the latest build. > [VMware] Failed to create template from volume (volume is created from > snapshot of data volume) > --- > > Key: CLOUDSTACK-3616 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3616 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller, VMware >Affects Versions: 4.2.0 > Environment: VMware ESXi 5.0 > ACS master branch >Reporter: Sateesh Chodapuneedi >Assignee: edison su >Priority: Blocker > Fix For: 4.2.0 > > > When tried to created template from volume created from snapshot we see > following error in Cloudstack deployed over VMware. > 2013-07-18 00:02:52,273 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-28:job-65 = [ ababda19-bd16-4e7c-aa92-39b948ad120f ]) > Unexpected exception while executing > org.apache.cloudstack.api.command.user.template.CreateTemplateCmd > com.cloud.utils.exception.CloudRuntimeException: Failed to create template > at > com.cloud.template.TemplateManagerImpl.createPrivateTemplate(TemplateManagerImpl.java:1369) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.template.CreateTemplateCmd.execute(CreateTemplateCmd.java:258) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) > at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:538) > 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) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-2384) Template created from snapshot or root disk is not displayed in the templates view in VMware setup.
Kiran Koneti created CLOUDSTACK-2384: Summary: Template created from snapshot or root disk is not displayed in the templates view in VMware setup. Key: CLOUDSTACK-2384 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2384 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Snapshot Affects Versions: 4.2.0 Environment: Vmware Reporter: Kiran Koneti Priority: Critical Fix For: 4.2.0 The below are the steps followed. I created a VM with a root disk and data disk using the windows 2012 and windows 8 32bit ISO's. Case 1: In the case 1 stopped the windows 2012 machine and created the template the aysnc job shows completed for the same case but the template is not displayed in the UI. I waited for longer time i.e almost 1 day then I was able to see the same in the UI of the templates view. The DB details for the same still shows allocated and all the details are as below: *** 20. row *** id: 210 unique_name: 221a6cfd2-f609-3cb6-a879-afdc47ca2c43 name: Winserve8 uuid: 0efb17b3-13d0-4e25-bb9b-709a4e71f584 public: 1 featured: 1 type: USER hvm: 1 bits: 64 url: NULL format: OVA created: 2013-05-07 15:44:19 removed: NULL account_id: 2 checksum: 93418461b411aa5559bc978a9b0d73f3 display_text: Winserve8 enable_password: 0 enable_sshkey: 0 guest_os_id: 168 bootable: 1 prepopulate: 0 cross_zones: 0 extractable: 1 hypervisor_type: VMware source_template_id: 204 template_tag: NULL sort_key: 0 size: NULL state: Allocated update_count: 0 updated: NULL image_data_store_id: 1 I initially observed only the ovf file and later after a day I was able to see the .vmdk,.ova and also templates.properties file. Case2: In the case 2 I took a snapshot of the windows 2012 root disk. from this snapshot I tried to create a template then I observed the similar behaviour. investigating into deep I found that the secondary storage has only the .ovf file and the details of the snapshot are as below: "*** 21. row *** id: 211 unique_name: 272531697-0e83-3556-8a7f-346aa8d58beb name: CreatedfromSnapshot uuid: d110660c-48cf-4362-875a-e3ae068ef89d public: 1 featured: 0 type: USER hvm: 1 bits: 64 url: NULL format: RAW created: 2013-05-08 14:25:04 removed: NULL account_id: 2 checksum: NULL display_text: win8server enable_password: 0 enable_sshkey: 0 guest_os_id: 168 bootable: 1 prepopulate: 0 cross_zones: 0 extractable: 0 hypervisor_type: VMware source_template_id: 204 template_tag: NULL sort_key: 0 size: NULL state: Allocated update_count: 0 updated: NULL image_data_store_id: 1" I observed the same behaviour even with the centos VM . -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-2385) template download fails with Unexpected failure in Vmware.
Kiran Koneti created CLOUDSTACK-2385:
Summary: template download fails with Unexpected failure in Vmware.
Key: CLOUDSTACK-2385
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2385
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Template
Affects Versions: 4.2.0
Reporter: Kiran Koneti
Priority: Critical
Fix For: 4.2.0
I registered a template with the parameters extractable=yes,Public=yes and
Featured=yes.
Then later I tried to download the template from the UI.
It shows an error message in the UI as below:"PrepareExtractTemplate: Failed to
create OVA for template extraction"
and in the management server log below are the error messages observed.
"2013-05-08 17:03:14,828 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null)
===START=== 10.146.0.136 -- GET
command=extractTemplate&mode=HTTP_DOWNLOAD&id=21e135aa-4df9-4818-b89c-99c64de5ee70&zoneid=58e1ce4d-fb5c-48c4-948f-408c969deae0&response=json&sessionkey=xrRnNHcHp3bh6nKU0gggxWRiioQ%3D&_=1367993227024
2013-05-08 17:03:14,865 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-4:null) submit async job-78, details: AsyncJobVO {id:78, userId:
2, accountId: 2, sessionKey: null, instanceType: Template, instanceId: 206,
cmd: org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd,
cmdOriginator: null, cmdInfo:
{"response":"json","id":"21e135aa-4df9-4818-b89c-99c64de5ee70","sessionkey":"xrRnNHcHp3bh6nKU0gggxWRiioQ\u003d","ctxUserId":"2","zoneid":"58e1ce4d-fb5c-48c4-948f-408c969deae0","httpmethod":"GET","_":"1367993227024","ctxAccountId":"2","ctxStartEventId":"322","mode":"HTTP_DOWNLOAD"},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 6703101771911,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-05-08 17:03:14,868 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null)
===END=== 10.146.0.136 -- GET
command=extractTemplate&mode=HTTP_DOWNLOAD&id=21e135aa-4df9-4818-b89c-99c64de5ee70&zoneid=58e1ce4d-fb5c-48c4-948f-408c969deae0&response=json&sessionkey=xrRnNHcHp3bh6nKU0gggxWRiioQ%3D&_=1367993227024
2013-05-08 17:03:14,872 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-26:job-78) Executing
org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd for job-78
2013-05-08 17:03:14,894 DEBUG [cloud.template.HypervisorTemplateAdapter]
(Job-Executor-26:job-78) Failed to create OVA for template
Tmpl[206-OVA-206-2-70244819-a3df-3daf-882c-c05c22c9645a due to zone
non-existing.
2013-05-08 17:03:14,905 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-26:job-78) Unexpected exception while executing
org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd
com.cloud.utils.exception.CloudRuntimeException: PrepareExtractTemplate: Failed
to create OVA for template extraction.
at
com.cloud.template.HypervisorTemplateAdapter.prepareExtractTemplate(HypervisorTemplateAdapter.java:263)
at
com.cloud.template.TemplateManagerImpl.extract(TemplateManagerImpl.java:375)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.template.ExtractTemplateCmd.execute(ExtractTemplateCmd.java:128)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
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 17:03:14,907 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-26:job-78) Complete async job-78, jobStatus: 2, resultCode: 530,
result: Error Code: 530 Error text: PrepareExtractTemplate: Failed to create
OVA for template extraction.
2013-05-08 17:03:16,752 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-18:null) Ping from 5
2013-05-08 17:03:17,262 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-198:null) Ping from 1
2013-05-08 17:03:17,884 DEBUG [cloud.api.ApiServlet] (catalina-exec-16:null)
===START=== 10.146.0.136 -- GET
command=queryAsyncJobResult&jobId=847d337a-0f3c-4396-8d78-7efad2f9a7b2&response=json&sessionkey=xrRnNHcHp3bh6nKU0gggxWRiioQ%3D&_=1367993230129
2013-05-08 17:03:17,903 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-16:null) Async job-78 completed"
--
This message i
[jira] [Created] (CLOUDSTACK-2581) Not able to login to VM using the password dispalyed from passwordenabled tempalte.
Kiran Koneti created CLOUDSTACK-2581: Summary: Not able to login to VM using the password dispalyed from passwordenabled tempalte. Key: CLOUDSTACK-2581 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2581 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.2.0 Reporter: Kiran Koneti Priority: Critical Fix For: 4.2.0 1)Registered a template as a password enabled template. 2)Created a VM using the same template and the password is displayed once the VM is created. 3)Tried to login to the VM using the password. 4)the login failed saying wrong password. 5)Then tried to login with the default password the login was successful. 6)Then tried the password reset and new password is pooped up. 7)Tried logging with the new password but the login still fails with and login is successful with the default password. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-2619) Volume created from Snapshot does not attach to the VM.fails with NPE.
Kiran Koneti created CLOUDSTACK-2619:
Summary: Volume created from Snapshot does not attach to the
VM.fails with NPE.
Key: CLOUDSTACK-2619
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2619
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Volumes
Affects Versions: 4.2.0
Reporter: Kiran Koneti
Priority: Critical
Fix For: 4.2.0
1)Create a VMware Advanced Zone setup.
2)Once the Builtin template is downloaded then created a Vm and took snapshot
for the same.
3)Created a volume from the snapshot created in the step 2.
4) I see the volume creation was successful in the UI.
5)Tried to check the volume details but couldn't find it either in primary nor
in secondary storage.
6)Observed the Volumes details in the DB and it shows state as allocated and
the Location as Null.
"*** 6. row ***
id: 6
account_id: 2
domain_id: 1
pool_id: NULL
last_pool_id: NULL
instance_id: NULL
device_id: NULL
name: CreatedVolume
uuid: 858d9047-899b-4d2a-95fe-d1ac33154aa8
size: 2147483648
folder: NULL
path: c394b91e99774acd8e9c30f890d3
pod_id: NULL
data_center_id: 1
iscsi_name: NULL
host_ip: NULL
volume_type: DATADISK
pool_type: NULL
disk_offering_id: 2
template_id: 7
first_snapshot_backup_uuid: NULL
recreatable: 0
created: 2013-05-22 14:18:28
attached: NULL
updated: 2013-05-22 14:18:28
removed: NULL
state: Allocated
chain_info: NULL
update_count: 0
disk_type: NULL
display_volume: 1
6 rows in set (0.00 sec)"
Then I tried to attach this volume to a VM and it fails with an NPE as
mentioned below
"2013-05-22 20:16:02,983 DEBUG [agent.transport.Request] (DirectAgent-202:null)
Seq 1-1002242356: Processing: { Ans: , MgmtId: 6703101771911, via: 1, Ver: v1,
Flags: 110,
[{"storage.CreateAnswer":{"volume":{"id":6,"name":"CreatedVolume","mountPoint":"/export/home/kiran/p1","path":"a300f5598c63435c948deb4cc313a4b7","size":2147483648,"type":"DATADISK","storagePoolType":"NetworkFilesystem","storagePoolUuid":"b4825bd6-2b6d-33ef-b324-bfbbec982716","deviceId":0},"requestTemplateReload":false,"result":true,"wait":0}}]
}
2013-05-22 20:16:02,985 DEBUG [agent.transport.Request]
(Job-Executor-17:job-17) Seq 1-1002242356: Received: { Ans: , MgmtId:
6703101771911, via: 1, Ver: v1, Flags: 110, { CreateAnswer } }
2013-05-22 20:16:02,990 DEBUG [agent.manager.AgentAttache]
(DirectAgent-202:null) Seq 1-1002242356: No more commands found
2013-05-22 20:16:03,062 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-17:job-17) Unexpected exception while executing
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
java.lang.NullPointerException
at
com.cloud.storage.VolumeManagerImpl.needMoveVolume(VolumeManagerImpl.java:1500)
at
com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1730)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:122)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
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-22 20:16:03,065 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-17:job-17) Complete async job-17, jobStatus: 2, resultCode: 530,
result: Error Code: 530 Error text: null"
Attaching the management server logs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2619) Volume created from Snapshot does not attach to the VM.fails with NPE.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kiran Koneti updated CLOUDSTACK-2619:
-
Attachment: management-server.zip
> Volume created from Snapshot does not attach to the VM.fails with NPE.
> --
>
> Key: CLOUDSTACK-2619
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2619
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Volumes
>Affects Versions: 4.2.0
>Reporter: Kiran Koneti
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.zip
>
>
> 1)Create a VMware Advanced Zone setup.
> 2)Once the Builtin template is downloaded then created a Vm and took snapshot
> for the same.
> 3)Created a volume from the snapshot created in the step 2.
> 4) I see the volume creation was successful in the UI.
> 5)Tried to check the volume details but couldn't find it either in primary
> nor in secondary storage.
> 6)Observed the Volumes details in the DB and it shows state as allocated and
> the Location as Null.
> "*** 6. row ***
> id: 6
> account_id: 2
> domain_id: 1
>pool_id: NULL
> last_pool_id: NULL
>instance_id: NULL
> device_id: NULL
> name: CreatedVolume
> uuid: 858d9047-899b-4d2a-95fe-d1ac33154aa8
> size: 2147483648
> folder: NULL
> path: c394b91e99774acd8e9c30f890d3
> pod_id: NULL
> data_center_id: 1
> iscsi_name: NULL
>host_ip: NULL
>volume_type: DATADISK
> pool_type: NULL
> disk_offering_id: 2
>template_id: 7
> first_snapshot_backup_uuid: NULL
>recreatable: 0
>created: 2013-05-22 14:18:28
> attached: NULL
>updated: 2013-05-22 14:18:28
>removed: NULL
> state: Allocated
> chain_info: NULL
> update_count: 0
> disk_type: NULL
> display_volume: 1
> 6 rows in set (0.00 sec)"
> Then I tried to attach this volume to a VM and it fails with an NPE as
> mentioned below
> "2013-05-22 20:16:02,983 DEBUG [agent.transport.Request]
> (DirectAgent-202:null) Seq 1-1002242356: Processing: { Ans: , MgmtId:
> 6703101771911, via: 1, Ver: v1, Flags: 110,
> [{"storage.CreateAnswer":{"volume":{"id":6,"name":"CreatedVolume","mountPoint":"/export/home/kiran/p1","path":"a300f5598c63435c948deb4cc313a4b7","size":2147483648,"type":"DATADISK","storagePoolType":"NetworkFilesystem","storagePoolUuid":"b4825bd6-2b6d-33ef-b324-bfbbec982716","deviceId":0},"requestTemplateReload":false,"result":true,"wait":0}}]
> }
> 2013-05-22 20:16:02,985 DEBUG [agent.transport.Request]
> (Job-Executor-17:job-17) Seq 1-1002242356: Received: { Ans: , MgmtId:
> 6703101771911, via: 1, Ver: v1, Flags: 110, { CreateAnswer } }
> 2013-05-22 20:16:02,990 DEBUG [agent.manager.AgentAttache]
> (DirectAgent-202:null) Seq 1-1002242356: No more commands found
> 2013-05-22 20:16:03,062 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-17:job-17) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> java.lang.NullPointerException
> at
> com.cloud.storage.VolumeManagerImpl.needMoveVolume(VolumeManagerImpl.java:1500)
> at
> com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1730)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:122)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
> 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-22 20:16:03,065 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-17:job-17) Complete async
[jira] [Created] (CLOUDSTACK-2643) ImplicitDedicationPlanner is missing from the listDeploymentPlanner which blocks the implicit dedication.
Kiran Koneti created CLOUDSTACK-2643: Summary: ImplicitDedicationPlanner is missing from the listDeploymentPlanner which blocks the implicit dedication. Key: CLOUDSTACK-2643 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2643 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.2.0 Reporter: Kiran Koneti Priority: Blocker Fix For: 4.2.0 Tried to create a service offering for the Implicit dedication and the deployment planner dosen't have the ImplicitDedicationPlanner which is blocking me from creating the Service offering. Please add the same. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-2662) Preferred implicit dedication fails with insufficient capacity even if shared hosts are available.
Kiran Koneti created CLOUDSTACK-2662: Summary: Preferred implicit dedication fails with insufficient capacity even if shared hosts are available. Key: CLOUDSTACK-2662 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2662 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.2.0 Reporter: Kiran Koneti Priority: Blocker Fix For: 4.2.0 Below are the steps followed : 1)Created a Xen Advanced Zone setup with one cluster and hosts. 2)The host1 has the system VM's deployed and a VM with the root domain. 3)Then created two accounts kiran and kiran2 respectively. 4)Was able to deploy VM's using the preferred and strict implicit dedication for the Account kiran. 5)Then tried to deploy a VM fro the account kiran2 using the preferred implicit service offering. 6)The VM deployment fails saying insufficient resources even we have the host 1 in the shared state. the below error message is observed "2013-05-24 16:15:09,565 INFO [user.vm.DeployVMCmd] (Job-Executor-3:job-22) com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[U ser|win832pref2]Scope=interface com.cloud.dc.DataCenter; id=1 2013-05-24 16:15:09,565 INFO [user.vm.DeployVMCmd] (Job-Executor-3:job-22) Unable to create a deployment for VM[User|win832pref2] com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|win832pref2]Scope=interface com.cloud.dc.DataCenter; id=1 at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:212) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3206) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2745) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2731) 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:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) 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)" The op_host_planner_reservation shows the host dedication details as below: mysql> select * from op_host_planner_reservation; +++++-++ | id | data_center_id | pod_id | cluster_id | host_id | resource_usage | +++++-++ | 1 | 1 | 1 | 1 | 1 | Shared | | 2 | 1 | 1 | 1 | 5 | Dedicated | +++++-++ 2 rows in set (0.00 sec) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-2666) Host is getting dedicated to a Account even when preferred implicit dedication is used.
Kiran Koneti created CLOUDSTACK-2666: Summary: Host is getting dedicated to a Account even when preferred implicit dedication is used. Key: CLOUDSTACK-2666 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2666 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Kiran Koneti Priority: Blocker 1)Created a Xen Advanced Zone setup with one cluster and hosts. 2)The host1 has the system VM's deployed and a VM with the root domain. 3)Then created two accounts kiran and kiran2 respectively. 4)Deployed VM using the preferred implicit dedication for the Account kiran. 5)Then tried to deploy a VM fro the account kiran2 using the preferred implicit service offering. 6)The VM deployment fails saying insufficient resources The error message is as below "2013-05-24 17:49:33,285 INFO [user.vm.DeployVMCmd] (Job-Executor-7:job-26) com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|prefacc2]Scope=interface com.cloud.dc.DataCenter; id=1 2013-05-24 17:49:33,287 INFO [user.vm.DeployVMCmd] (Job-Executor-7:job-26) Unable to create a deployment for VM[User|prefacc2] com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|prefacc2]Scope=interface com.cloud.dc.DataCenter; id=1 at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:212) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3206) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2745) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2731) 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:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) 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)" Ideally saying the host should not be dedicated to the account kiran but this is getting dedicated which is causing the vm creation failure for the account kiran2. The db shows the host in dedicated state. "mysql> select * from op_host_planner_reservation; +++++-++ | id | data_center_id | pod_id | cluster_id | host_id | resource_usage | +++++-++ | 1 | 1 | 1 | 1 | 1 | Shared | | 2 | 1 | 1 | 1 | 5 | Dedicated | +++++-++ 2 rows in set (0.00 sec)" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-2735) Unable to Add two Xen hosts(6.1 with all updates) in a cluster.
Kiran Koneti created CLOUDSTACK-2735: Summary: Unable to Add two Xen hosts(6.1 with all updates) in a cluster. Key: CLOUDSTACK-2735 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2735 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.2.0 Reporter: Kiran Koneti Priority: Blocker Fix For: 4.2.0 Tried to add two Xen Hosts (6.1 hosts with all updates installed) to a single cluster and observed the below error message "2013-05-29 13:07:09,969 DEBUG [xen.resource.XenServerConnectionPool] (catalina-exec-18:null) Host(10.147.40.18) unable to Join the pool at 10.147.40.21 2013-05-29 13:07:09,969 WARN [xen.discoverer.XcpServerDiscoverer] (catalina-exec-18:null) Unable to join the pool 2013-05-29 13:07:09,970 INFO [utils.exception.CSExceptionErrorCode] (catalina-exec-18:null) Could not find exception: com.cloud.exception.DiscoveryException in error code list for exceptions 2013-05-29 13:07:09,970 DEBUG [xen.discoverer.XcpServerDiscoverer] (catalina-exec-18:null) other exceptions: com.cloud.exception.DiscoveryException: Unable to join the pool com.cloud.exception.DiscoveryException: Unable to join the pool at com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.addHostsToPool(XcpServerDiscoverer.java:411) at com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.find(XcpServerDiscoverer.java:207) at com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:847) at com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:658) at org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:143) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:527) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:370) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) at com.cloud.api.ApiServlet.doPost(ApiServlet.java:71) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2274) 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-05-29 13:07:09,971 WARN [cloud.resource.ResourceManagerImpl] (catalina-exec-18:null) Unable to find the server resources at http://10.147.40.18 2013-05-29 13:07:09,972 INFO [utils.exception.CSExceptionErrorCode] (catalina-exec-18:null) Could not find exception: com.cloud.exception.DiscoveryException in error code list for exceptions 2013-05-29 13:07:09,972 WARN [admin.host.AddHostCmd] (catalina-exec-18:null) Exception: com.cloud.exception.DiscoveryException: Unable to add the host at com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:913) at com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:658) at org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:143) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:527) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:370) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) at com.cloud.api.ApiServlet.doPost(ApiServlet.java:71) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637
[jira] [Commented] (CLOUDSTACK-2735) Unable to Add two Xen hosts(6.1 with all updates) in a cluster.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13669170#comment-13669170 ] Kiran Koneti commented on CLOUDSTACK-2735: -- Tried this in the latest Master Build(4.2) > Unable to Add two Xen hosts(6.1 with all updates) in a cluster. > --- > > Key: CLOUDSTACK-2735 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2735 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.2.0 >Reporter: Kiran Koneti >Priority: Blocker > Fix For: 4.2.0 > > Attachments: management-server.zip > > > Tried to add two Xen Hosts (6.1 hosts with all updates installed) to a single > cluster and observed the below error message > "2013-05-29 13:07:09,969 DEBUG [xen.resource.XenServerConnectionPool] > (catalina-exec-18:null) Host(10.147.40.18) unable to Join the pool at > 10.147.40.21 > 2013-05-29 13:07:09,969 WARN [xen.discoverer.XcpServerDiscoverer] > (catalina-exec-18:null) Unable to join the pool > 2013-05-29 13:07:09,970 INFO [utils.exception.CSExceptionErrorCode] > (catalina-exec-18:null) Could not find exception: > com.cloud.exception.DiscoveryException in error code list for exceptions > 2013-05-29 13:07:09,970 DEBUG [xen.discoverer.XcpServerDiscoverer] > (catalina-exec-18:null) other exceptions: > com.cloud.exception.DiscoveryException: Unable to join the pool > com.cloud.exception.DiscoveryException: Unable to join the pool > at > com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.addHostsToPool(XcpServerDiscoverer.java:411) > at > com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.find(XcpServerDiscoverer.java:207) > at > com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:847) > at > com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:658) > at > org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:143) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:527) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:370) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doPost(ApiServlet.java:71) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) > at > org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) > at > org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2274) > 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-05-29 13:07:09,971 WARN [cloud.resource.ResourceManagerImpl] > (catalina-exec-18:null) Unable to find the server resources at > http://10.147.40.18 > 2013-05-29 13:07:09,972 INFO [utils.exception.CSExceptionErrorCode] > (catalina-exec-18:null) Could not find exception: > com.cloud.exception.DiscoveryException in error code list for exceptions > 2013-05-29 13:07:09,972 WARN [admin.host.AddHostCmd] (catalina-exec-18:null) > Exception: com.cloud.exception.DiscoveryException: Unable to add the host > at > com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:913) > at > com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:658) > at
[jira] [Updated] (CLOUDSTACK-2735) Unable to Add two Xen hosts(6.1 with all updates) in a cluster.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti updated CLOUDSTACK-2735: - Attachment: management-server.zip > Unable to Add two Xen hosts(6.1 with all updates) in a cluster. > --- > > Key: CLOUDSTACK-2735 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2735 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.2.0 >Reporter: Kiran Koneti >Priority: Blocker > Fix For: 4.2.0 > > Attachments: management-server.zip > > > Tried to add two Xen Hosts (6.1 hosts with all updates installed) to a single > cluster and observed the below error message > "2013-05-29 13:07:09,969 DEBUG [xen.resource.XenServerConnectionPool] > (catalina-exec-18:null) Host(10.147.40.18) unable to Join the pool at > 10.147.40.21 > 2013-05-29 13:07:09,969 WARN [xen.discoverer.XcpServerDiscoverer] > (catalina-exec-18:null) Unable to join the pool > 2013-05-29 13:07:09,970 INFO [utils.exception.CSExceptionErrorCode] > (catalina-exec-18:null) Could not find exception: > com.cloud.exception.DiscoveryException in error code list for exceptions > 2013-05-29 13:07:09,970 DEBUG [xen.discoverer.XcpServerDiscoverer] > (catalina-exec-18:null) other exceptions: > com.cloud.exception.DiscoveryException: Unable to join the pool > com.cloud.exception.DiscoveryException: Unable to join the pool > at > com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.addHostsToPool(XcpServerDiscoverer.java:411) > at > com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.find(XcpServerDiscoverer.java:207) > at > com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:847) > at > com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:658) > at > org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:143) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:527) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:370) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doPost(ApiServlet.java:71) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) > at > org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) > at > org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2274) > 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-05-29 13:07:09,971 WARN [cloud.resource.ResourceManagerImpl] > (catalina-exec-18:null) Unable to find the server resources at > http://10.147.40.18 > 2013-05-29 13:07:09,972 INFO [utils.exception.CSExceptionErrorCode] > (catalina-exec-18:null) Could not find exception: > com.cloud.exception.DiscoveryException in error code list for exceptions > 2013-05-29 13:07:09,972 WARN [admin.host.AddHostCmd] (catalina-exec-18:null) > Exception: com.cloud.exception.DiscoveryException: Unable to add the host > at > com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:913) > at > com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:658) > at > org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHos
