date:20131009


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

shweta agarwal closed CLOUDSTACK-3397.
--


 When Template creation from a snapshot fails, the UI pop-up also displays the 
 API resonse 
 --

 Key: CLOUDSTACK-3397
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3397
 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: Abhinav Roy
Assignee: Jessica Wang
 Fix For: 4.2.1

 Attachments: fail-template.jpg


 Steps : 
 === 
 1. Deploy CS advanced zone setup . 
 2. Deploy a VM 
 3. Goto the root volume of the VM and take Snapshot 
 4. Go to that snapshot and try to create a template from the snapshot. 
 Observed behaviour : 
 === 
 The template creation fails and the response displayed in the UI pop-up in 
 same as the API response in the logs.
 Attaching screenshot for reference. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4300) [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4300:
---

Assignee: Abhinav Roy

 [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade
 

 Key: CLOUDSTACK-4300
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4300
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Doc, KVM, SystemVM, Upgrade
Affects Versions: 4.2.0
 Environment: Host : KVM [CentOS 6.1]
 MS : CentOS 6.1
 upgrade from 2.2.14 to 4.2
Reporter: Abhinav Roy
Assignee: Abhinav Roy
Priority: Blocker
 Fix For: 4.2.1

 Attachments: CS-4300.zip, re_CS-4300.zip


 Steps :
 
 1. Deploy a CS 2.2.14 advanced zone setup with KVM host.
 2. do some operations like create vm, snapshots, templates, domain, accounts 
 etc
 3. upgrade to 4.2
 Expected behaviour :
 ===
 Upgrade should go fine and new system vms should come up
 Observed behaviour :
 ==
 Upgrade went fine but system vms don't come up, they stay in the starting 
 state.
 Attaching management server logs, catalina logs, agent logs and DB dumps



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Closed] (CLOUDSTACK-4515) [UI] Missing 'Description' in Settings tab for zone/cluster/account/pool level configuration parameters


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

shweta agarwal closed CLOUDSTACK-4515.
--


Verified on 4.2.1 build. Passed

 [UI] Missing 'Description' in Settings tab for zone/cluster/account/pool 
 level configuration parameters
 ---

 Key: CLOUDSTACK-4515
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4515
 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: Harikrishna Patnala
Assignee: Jessica Wang
 Fix For: 4.2.1

 Attachments: Global configuration parameters.png, Scope level 
 configuration parameters.png


 'Description' is missing in Settings tab for zone/cluster/account/pool level 
 configuration.
 This should show the description of each configuration parameter like we show 
 for global parameters



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (CLOUDSTACK-4300) [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13790181#comment-13790181
 ] 

Abhinandan Prateek commented on CLOUDSTACK-4300:


Abhinav,
   Did we decide to document the upgrade for KVM, it seem that is already 
complete. If it is can you close this ticket.

 [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade
 

 Key: CLOUDSTACK-4300
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4300
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Doc, KVM, SystemVM, Upgrade
Affects Versions: 4.2.0
 Environment: Host : KVM [CentOS 6.1]
 MS : CentOS 6.1
 upgrade from 2.2.14 to 4.2
Reporter: Abhinav Roy
Assignee: Abhinav Roy
Priority: Blocker
 Fix For: 4.2.1

 Attachments: CS-4300.zip, re_CS-4300.zip


 Steps :
 
 1. Deploy a CS 2.2.14 advanced zone setup with KVM host.
 2. do some operations like create vm, snapshots, templates, domain, accounts 
 etc
 3. upgrade to 4.2
 Expected behaviour :
 ===
 Upgrade should go fine and new system vms should come up
 Observed behaviour :
 ==
 Upgrade went fine but system vms don't come up, they stay in the starting 
 state.
 Attaching management server logs, catalina logs, agent logs and DB dumps



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (CLOUDSTACK-4829) vnc access instance's console through apikey failed

2013-10-09 Thread shangxu (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13790183#comment-13790183
 ] 

shangxu commented on CLOUDSTACK-4829:
-

I have the same problem





 vnc access instance's console through apikey failed
 ---

 Key: CLOUDSTACK-4829
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4829
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: VNC Proxy
Affects Versions: 4.1.1
 Environment: windows 7 + cygwin + xenserver 6.1.0 + cloudstack 4.1.1
Reporter: huyao
Priority: Critical

 I compiled cloudstack 4.1.1 source code in cygwin, then test it using jetty, 
 it works fine. But, when I access instance's console through vnc using 
 apikey, it fails, the browser shows the follow message:
 Access denied. Invalid web session or API key in request
 my url:
 http://localhost:8080/client/console?cmd=accessvm=b194369f-e0d4-45d8-a50f-09ec51095e68apikey=fmS7oyThP6MGxN5X_CgeOCxQIqgTu5QFDz46r2Pv5kLp88EYYBquSu6_3s3d9MXdbUHPpxj5qDDy1jvhEpQWvQsignature=y3dNHn580NJiCVRGwrBTR4JHImo%3D
 I test the listAccounts api, it's ok.
 my url:
 http://localhost:8080/client/api?command=listAccountsapikey=fmS7oyThP6MGxN5X_CgeOCxQIqgTu5QFDz46r2Pv5kLp88EYYBquSu6_3s3d9MXdbUHPpxj5qDDy1jvhEpQWvQsignature=ALhJtw%2Bzi7Rcmo%2Bkk3xH3cTJgp4%3D
 then, I debug the source code, find where it fails.
 file: ConsoleProxyServlet.java 
 private boolean verifyRequest(MapString, Object[] requestParameters) {
   try {
   ...
   ...
   unsignedRequest = unsignedRequest.toLowerCase();
   Mac mac = Mac.getInstance(HmacSHA1);
   SecretKeySpec keySpec = new SecretKeySpec(secretKey.getBytes(), 
 HmacSHA1);
   mac.init(keySpec);
   mac.update(unsignedRequest.getBytes());
   byte[] encryptedBytes = mac.doFinal();
   String computedSignature = 
 Base64.encodeBase64URLSafeString(encryptedBytes);
   boolean equalSig = signature.equals(computedSignature);
   if (!equalSig) {
   s_logger.debug(User signature:  + signature +  is 
 not equaled to computed signature:  + computedSignature);
   }
   ...
   ...
   return equalSig;
   } catch (Exception ex) {
   s_logger.error(unable to verifty request signature, ex);
   }
   return false;
 }
 in this method, signature not equals to computedSignature, so it returns false
 then, I view ApiServer.java，the verifyRequest method:
 public boolean verifyRequest(MapString, Object[] requestParameters, Long 
 userId)  throws ServerApiException {
   try {
   ...
   ...
   unsignedRequest = unsignedRequest.toLowerCase();
   Mac mac = Mac.getInstance(HmacSHA1);
   SecretKeySpec keySpec = new SecretKeySpec(secretKey.getBytes(), 
 HmacSHA1);
   mac.init(keySpec);
   mac.update(unsignedRequest.getBytes());
   byte[] encryptedBytes = mac.doFinal();
   String computedSignature = 
 Base64.encodeBase64String(encryptedBytes);
   boolean equalSig = signature.equals(computedSignature);
   if (!equalSig) {
   s_logger.debug(User signature:  + signature +  is 
 not equaled to computed signature:  + computedSignature);
   }
   ...
   ...
   return equalSig;
   } catch (Exception ex) {
   s_logger.error(unable to verifty request signature, ex);
   }
   return false;
 }
 these two verifyRequest method produce different signature, because the 
 former use :
 String computedSignature = Base64.encodeBase64URLSafeString(encryptedBytes);
 while the later use:
 String computedSignature = Base64.encodeBase64String(encryptedBytes);
 this is why listAccouts works fine, but vnc console is failed.
 when I replace Base64.encodeBase64URLSafeString by Base64.encodeBase64String, 
 vnc console is ok too.
 so I am confused, why use different encode method? It is a bug?



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Closed] (CLOUDSTACK-4300) [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade

2013-10-09 Thread Abhinav Roy (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinav Roy closed CLOUDSTACK-4300.
---

Resolution: Fixed

closing the issue as it has already been documented

 [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade
 

 Key: CLOUDSTACK-4300
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4300
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Doc, KVM, SystemVM, Upgrade
Affects Versions: 4.2.0
 Environment: Host : KVM [CentOS 6.1]
 MS : CentOS 6.1
 upgrade from 2.2.14 to 4.2
Reporter: Abhinav Roy
Assignee: Abhinav Roy
Priority: Blocker
 Fix For: 4.2.1

 Attachments: CS-4300.zip, re_CS-4300.zip


 Steps :
 
 1. Deploy a CS 2.2.14 advanced zone setup with KVM host.
 2. do some operations like create vm, snapshots, templates, domain, accounts 
 etc
 3. upgrade to 4.2
 Expected behaviour :
 ===
 Upgrade should go fine and new system vms should come up
 Observed behaviour :
 ==
 Upgrade went fine but system vms don't come up, they stay in the starting 
 state.
 Attaching management server logs, catalina logs, agent logs and DB dumps



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (CLOUDSTACK-4707) sourcetemplateid field is not getting set for derived templates


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13790196#comment-13790196
 ] 

Abhinandan Prateek commented on CLOUDSTACK-4707:


Kishan, can you review the fix.

 sourcetemplateid field is not getting set for derived templates
 -

 Key: CLOUDSTACK-4707
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4707
 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: Harikrishna Patnala
Assignee: Harikrishna Patnala
Priority: Critical
 Fix For: 4.2.1


 Template created from a volume or snapshot did not have the sourcetemplateid 
 field set in vm_template table.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Resolved] (CLOUDSTACK-3608) guest_os_hypervisor table has repeated mappings of hypervisor and guest OS


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek resolved CLOUDSTACK-3608.


Resolution: Not A Problem

guest_os_hypervisor this table is not in use.

 guest_os_hypervisor table has repeated mappings of hypervisor and guest OS
 

 Key: CLOUDSTACK-3608
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3608
 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: Chandan Purushothama
Assignee: Sanjay Tripathi
Priority: Critical
 Fix For: 4.2.1


 mysql select hypervisor_type,guest_os_name,guest_os_id from 
 guest_os_hypervisor where guest_os_id in (165,166,167,168);
 +-+--+-+
 | hypervisor_type | guest_os_name| guest_os_id |
 +-+--+-+
 | XenServer   | Windows 8 (32-bit)   | 165 |
 | XenServer   | Windows 8 (64-bit)   | 166 |
 | XenServer   | Windows Server 2012 (64-bit) | 167 |
 | XenServer   | Windows Server 8 (64-bit)| 168 |
 | VmWare  | Windows 8 (32-bit)   | 165 |
 | VmWare  | Windows 8 (64-bit)   | 166 |
 | VmWare  | Windows Server 2012 (64-bit) | 167 |
 | VmWare  | Windows Server 8 (64-bit)| 168 |
 | VmWare  | Windows 8 (32-bit)   | 165 |
 | VmWare  | Windows 8 (64-bit)   | 166 |
 | VmWare  | Windows Server 2012 (64-bit) | 167 |
 | VmWare  | Windows Server 8 (64-bit)| 168 |
 | XenServer   | Windows 8 (32-bit)   | 165 |
 | XenServer   | Windows 8 (64-bit)   | 166 |
 | XenServer   | Windows Server 2012 (64-bit) | 167 |
 | XenServer   | Windows Server 8 (64-bit)| 168 |
 +-+--+-+
 16 rows in set (0.00 sec)



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Closed] (CLOUDSTACK-4704) DB upgrade bug caused by the new table vpc_service_map


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek closed CLOUDSTACK-4704.
--

Resolution: Fixed

 DB upgrade bug caused by the new table vpc_service_map
 

 Key: CLOUDSTACK-4704
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4704
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.2.0
Reporter: Alena Prokharchyk
Assignee: Kishan Kavala
Priority: Critical
 Fix For: 4.2.1


 As a part of the commit 836ce6c1, new table vpc_service_map was introduced. 
 Before Vpc code used to read services/providers combination from 
 vpc_service_offering_map, after the commit it reads from vpc_service_map (the 
 way we do for the networks).
 Bug: as a part of the DB upgrade, all existing VPCs are not updated with the 
 data in vpc_service_map table. It means existing VPC will never have any 
 Services/Providers to implement, and after the existing VR is gone (can 
 happen during the VPC restart, or VPC VR removal), it will never gonna get a 
 new VR again.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (CLOUDSTACK-4703) listHypervisors returns empty hypervisors when zoneId = -1 on a multi-zone setup with different hypervisors on each zone.


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13790197#comment-13790197
 ] 

Abhinandan Prateek commented on CLOUDSTACK-4703:


the API looks ok, the UI should not pass zoneid=-1, changing this to UI ticket.

 listHypervisors returns empty hypervisors when zoneId = -1 on a multi-zone 
 setup with different hypervisors on each zone.
 -

 Key: CLOUDSTACK-4703
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4703
 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: Min Chen
Priority: Critical
 Fix For: 4.2.1


 1. Setup two zones, one is XenServer, the other is Vmware. Both uses S3 as 
 secondary storage.
 2. Now register a template on zone 1.
 3. In the register template dialog, hypervisor dropdown shows empty list. The 
 API invoked from UI is listHypervisor with zoneId = -1.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Resolved] (CLOUDSTACK-4766) [Automation] test_reset_ssh_keypair executing in infinite loop and regression suite hang

2013-10-09 Thread Girish Shilamkar (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Girish Shilamkar resolved CLOUDSTACK-4766.
--

Resolution: Fixed

Patch added.

 [Automation] test_reset_ssh_keypair executing in infinite loop and regression 
 suite hang
 

 Key: CLOUDSTACK-4766
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4766
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.2.1
 Environment: Automation advanced zone 
Reporter: Rayees Namathponnan
Assignee: Girish Shilamkar
Priority: Blocker
 Fix For: 4.2.1


 Few test cases from test_reset_ssh_keypair.py suite executing infinite loop 
 hang automation 
 See the below code from test_reset_ssh_keypair.py,   here test case checking 
 VM's state in every 60 sec, due to some reason if this vm never comes to 
 running; this code will execute in a loop 
  578 while True:
  579 vms = VirtualMachine.list(
  580   self.apiclient,
  581   account=self.account.name,
  582   domainid=self.account.domainid,
  583   listall=True
  584   )
  585 if vms[0].state == Running:
  586 break
  587 self.debug(Vm not in Running state sleep 60s)
  588 time.sleep(60)



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (CLOUDSTACK-4766) [Automation] test_reset_ssh_keypair executing in infinite loop and regression suite hang

2013-10-09 Thread Girish Shilamkar (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13790199#comment-13790199
 ] 

Girish Shilamkar commented on CLOUDSTACK-4766:
--

https://reviews.apache.org/r/14556/

 [Automation] test_reset_ssh_keypair executing in infinite loop and regression 
 suite hang
 

 Key: CLOUDSTACK-4766
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4766
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.2.1
 Environment: Automation advanced zone 
Reporter: Rayees Namathponnan
Assignee: Girish Shilamkar
Priority: Blocker
 Fix For: 4.2.1


 Few test cases from test_reset_ssh_keypair.py suite executing infinite loop 
 hang automation 
 See the below code from test_reset_ssh_keypair.py,   here test case checking 
 VM's state in every 60 sec, due to some reason if this vm never comes to 
 running; this code will execute in a loop 
  578 while True:
  579 vms = VirtualMachine.list(
  580   self.apiclient,
  581   account=self.account.name,
  582   domainid=self.account.domainid,
  583   listall=True
  584   )
  585 if vms[0].state == Running:
  586 break
  587 self.debug(Vm not in Running state sleep 60s)
  588 time.sleep(60)



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4703) [UI]listHypervisors returns empty hypervisors when zoneId = -1 on a multi-zone setup with different hypervisors on each zone.


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4703:
---

Component/s: (was: API)
 UI
Summary: [UI]listHypervisors returns empty hypervisors when zoneId = -1 
on a multi-zone setup with different hypervisors on each zone.  (was: 
listHypervisors returns empty hypervisors when zoneId = -1 on a multi-zone 
setup with different hypervisors on each zone.)

 [UI]listHypervisors returns empty hypervisors when zoneId = -1 on a 
 multi-zone setup with different hypervisors on each zone.
 -

 Key: CLOUDSTACK-4703
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4703
 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: Min Chen
Priority: Critical
 Fix For: 4.2.1


 1. Setup two zones, one is XenServer, the other is Vmware. Both uses S3 as 
 secondary storage.
 2. Now register a template on zone 1.
 3. In the register template dialog, hypervisor dropdown shows empty list. The 
 API invoked from UI is listHypervisor with zoneId = -1.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4703) [UI] listHypervisors returns empty hypervisors when zoneId = -1 on a multi-zone setup with different hypervisors on each zone.


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4703:
---

Summary: [UI]  listHypervisors returns empty hypervisors when zoneId = -1 
on a multi-zone setup with different hypervisors on each zone.  (was: 
[UI]listHypervisors returns empty hypervisors when zoneId = -1 on a multi-zone 
setup with different hypervisors on each zone.)

 [UI]  listHypervisors returns empty hypervisors when zoneId = -1 on a 
 multi-zone setup with different hypervisors on each zone.
 ---

 Key: CLOUDSTACK-4703
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4703
 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: Min Chen
Priority: Critical
 Fix For: 4.2.1


 1. Setup two zones, one is XenServer, the other is Vmware. Both uses S3 as 
 secondary storage.
 2. Now register a template on zone 1.
 3. In the register template dialog, hypervisor dropdown shows empty list. The 
 API invoked from UI is listHypervisor with zoneId = -1.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Closed] (CLOUDSTACK-4816) provide configurable option to choose single vs multipart upload to S3 object storage


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

shweta agarwal closed CLOUDSTACK-4816.
--


Verified on 4.2.1 .Passed


 provide configurable option to choose single vs multipart upload to S3 object 
 storage 
 --

 Key: CLOUDSTACK-4816
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4816
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller
Affects Versions: 4.2.0
Reporter: Min Chen
Assignee: Min Chen
Priority: Critical
 Fix For: 4.2.1


 In 4.2, we only supports multipart upload for registering templates and 
 uploading volumes to object storage in secondary storage. The value of 
 multi-part is for network failure and throughput when you are going to a 
 remote storage. But with local storage (local to the DC) customers may prefer 
 single upload. Also, for templates you know the full size of the object 
 upfront and don't really need a multipart upload.
 Some object storage vendors may prefer that this can be configured.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Closed] (CLOUDSTACK-4701) Add guest network button should be disabled for basic zone


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

shweta agarwal closed CLOUDSTACK-4701.
--


Verified. 

 Add guest network button should be disabled for basic zone
 

 Key: CLOUDSTACK-4701
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4701
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.2.1
 Environment: UI
 Build from 4.2.1
 Basic zone with SG
Reporter: Rayees Namathponnan
 Fix For: 4.2.1


 Step 1 : Create Basic zone with EIP / ELB
 Step 2: Network - Add Guest Network
 If you click Add guest network button, below error gets displayed
 Unable to execute API command listnetworkofferings due to invalid value. 
 Invalid parameter zoneid value=null due to incorrect long value format, or 
 entity does not exist or due to incorrect parameter annotation for the field 
 in api cmd class
 Expected result
 Button  ( Add guest network) should be enabled, only if at least one Advanced 
 zone is configured 



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4621) Changing the management server's ethernet interface / mac address leaves the system in unstable state.


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4621:
---

Fix Version/s: (was: 4.2.1)
   Future

 Changing the management server's ethernet interface / mac address leaves the 
 system in unstable state.
 --

 Key: CLOUDSTACK-4621
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4621
 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: venkata swamybabu budumuru
Priority: Critical
 Fix For: Future

 Attachments: logs.tgz


 Steps to reproduce:
 1. Have latest CloudStack setup with 4.2 build.
 2. Have at least 1 advanced zone using Xen Cluster
 3. deploy VMs and make sure everything works fine.
 Note : In my case, the management server deployed on VMware.
 Before MAC changes on mgmt server :
 [root@Rhel63-Sanjeev ~]# cat ifconfig.output 
 eth1  Link encap:Ethernet  HWaddr 06:04:5A:00:00:66  
   inet addr:10.147.59.126  Bcast:10.147.59.255  Mask:255.255.255.0
   inet6 addr: fe80::404:5aff:fe00:66/64 Scope:Link
   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
   RX packets:35035311 errors:0 dropped:0 overruns:0 frame:0
   TX packets:31941744 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:1000 
   RX bytes:31951991629 (29.7 GiB)  TX bytes:17754778160 (16.5 GiB)
 mysql select * from mshost;
 ++---+---++---+-+---+--+-+-+-+
 | id | msid  | runid | name   | state | version | 
 service_ip| service_port | last_update | removed | alert_count |
 ++---+---++---+-+---+--+-+-+-+
 |  1 | 6615759585382 | 1378110990284 | Rhel63-Sanjeev | Up| 4.2.0   | 
 10.147.59.126 | 9090 | 2013-09-06 04:44:45 | NULL|   0 |
 4. I have manually logged into my vmware host and change the above MAC 
 address to 06:04:5A:00:00:68 and that resulted in a new interface.
 [root@Rhel63-Sanjeev ~]# ifconfig
 eth2  Link encap:Ethernet  HWaddr 06:04:5A:00:00:68  
   inet addr:10.147.59.126  Bcast:10.147.59.255  Mask:255.255.255.0
   inet6 addr: fe80::404:5aff:fe00:68/64 Scope:Link
   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
   RX packets:294927 errors:0 dropped:0 overruns:0 frame:0
   TX packets:475806 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:1000 
   RX bytes:22230231 (21.2 MiB)  TX bytes:392491450 (374.3 MiB)
 5. Restart the management server and verify the cloud.mshost table
 mysql select * from mshost;
 ++---+---++---+-+---+--+-+-+-+
 | id | msid  | runid | name   | state | version | 
 service_ip| service_port | last_update | removed | alert_count |
 ++---+---++---+-+---+--+-+-+-+
 |  1 | 6615759585382 | 1378110990284 | Rhel63-Sanjeev | Up| 4.2.0   | 
 10.147.59.126 | 9090 | 2013-09-06 04:44:45 | NULL|   0 |
 |  2 | 6615759585384 | 1378462772622 | Rhel63-Sanjeev | Up| 4.2.0   | 
 10.147.59.126 | 9090 | 2013-09-06 10:20:35 | NULL|   0 |
 ++---+---++---+-+---+--+-+-+-+
 Observations:
 i. Now it created a new entry for the mshost due to mac / interface changes
 ii. Both the above entries shows the status as UP and it assumes there are 
 two mgmt servers
 iii. All the system VMs have the mgmt_server_id set to the old which is not 
 infact up
 mysql select * from host where name like '%-VM%';

[jira] [Closed] (CLOUDSTACK-4822) Please add an icon for new action assignVmToAnotherAccount in Instance detailView


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

shweta agarwal closed CLOUDSTACK-4822.
--


Verify. Passed

 Please add an icon for new action assignVmToAnotherAccount in Instance 
 detailView
 ---

 Key: CLOUDSTACK-4822
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4822
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Brian Federle
 Fix For: 4.2.1

 Attachments: jessica_1.jpg, jessica_2.jpg






--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-2140) Host is still marked as being in Up state when the host is shutdown (when there are no more hosts in the cluster)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-2140:
---

Fix Version/s: (was: 4.2.1)
   Future

 Host is still marked as being in Up state when the host is shutdown (when 
 there are no more hosts in the cluster)
 ---

 Key: CLOUDSTACK-2140
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2140
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.2.0, 4.2.1
 Environment: build from master
Reporter: Sangeetha Hariharan
Assignee: Koushik Das
 Fix For: Future

 Attachments: management-server.rar


 Host is still marked as being in Up state when the host is shutdown (when 
 there are no more hosts in the cluster.
 Set up:
 Advanced zone.
 3 hosts in a cluster ( in my case host id - 7 ,8 ,9 ).
 I did not have any problems when host 8 and host 9 where shutdown.
 When I tried to shutdown host 7 , I see the host still being in Up state , 
 even after the management server detected that it is not able to connect with 
 this host.
 Following exception seen in management server logs:
 2013-04-22 14:48:18,350 DEBUG [xen.resource.XenServerConnectionPool] 
 (DirectAgent-350:null) localLogout has problem Failed to read server's 
 response: connect timed out
 2013-04-22 14:48:18,350 WARN  [xen.resource.CitrixResourceBase] 
 (DirectAgent-350:null) Unable to stop i-3-45-VM due to
 com.cloud.utils.exception.CloudRuntimeException: Unable to reset master of 
 slave 10.223.59.4 to 10.223.59.2 due to org.apache.xmlrpc.XmlRpcException: 
 Failed to read server's response: connect timed out
 at 
 com.cloud.hypervisor.xen.resource.XenServerConnectionPool.PoolEmergencyResetMaster(XenServerConnectionPool.java:443)
 at 
 com.cloud.hypervisor.xen.resource.XenServerConnectionPool.connect(XenServerConnectionPool.java:661)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.getConnection(CitrixResourceBase.java:5583)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:3728)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:474)
 at 
 com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
 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-04-22 14:48:18,364 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-350:null) Seq 9-72160431: Response Received:
 2013-04-22 14:48:18,370 DEBUG [agent.transport.Request] 
 (DirectAgent-350:null) Seq 9-72160431: Processing:  { Ans: , MgmtId: 
 7508777239729, via: 9, Ver: v1, Flags: 110, 
 [{StopAnswer:{result:false,details:Exception: 
 com.cloud.utils.exception.CloudRuntimeException\nMessage: Unable to reset 
 master of slave 10.223.59.4 to 10.223.59.2 due to 
 org.apache.xmlrpc.XmlRpcException: Failed to read server's response: connect 
 timed out\nStack: com.cloud.utils.exception.CloudRuntimeException: Unable to 
 reset master of slave 10.223.59.4 to 10.223.59.2 due to 
 org.apache.xmlrpc.XmlRpcException: Failed to read server's response: connect 
 timed out\n\tat 
 com.cloud.hypervisor.xen.resource.XenServerConnectionPool.PoolEmergencyResetMaster(XenServerConnectionPool.java:443)\n\tat
  
 com.cloud.hypervisor.xen.resource.XenServerConnectionPool.connect(XenServerConnectionPool.java:661)\n\tat
  
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.getConnection(CitrixResourceBase.java:5583)\n\tat
  
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:3728)\n\tat
  
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:474)\n\tat
  
 com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)\n\tat

[jira] [Closed] (CLOUDSTACK-4814) Managament server is not starting


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

shweta agarwal closed CLOUDSTACK-4814.
--


verified . Passed

 Managament server is not starting 
 --

 Key: CLOUDSTACK-4814
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4814
 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
 Environment: Build :
 CloudPlatform-4.2.1-707-rhel6.3
Reporter: shweta agarwal
Priority: Blocker
 Fix For: 4.2.1


 Install MS and start it.
 Wait for some time to properly start  MS
 BUG:
 MS fails with following  error
 2013-10-04 06:27:43,230 DEBUG [upgrade.dao.VersionDaoImpl] (Timer-2:null) 
 Checking to see if the database is at a version before it was the version 
 table is created
 2013-10-04 06:27:43,239 INFO  [cloud.upgrade.DatabaseUpgradeChecker] 
 (Timer-2:null) DB version = 4.0.0 Code Version = 4.2.1-SNAPSHOT
 2013-10-04 06:27:43,240 INFO  [cloud.upgrade.DatabaseUpgradeChecker] 
 (Timer-2:null) Database upgrade must be performed from 4.0.0 to 4.2.1-SNAPSHOT
 2013-10-04 06:27:43,240 ERROR [cloud.upgrade.DatabaseUpgradeChecker] 
 (Timer-2:null) The end upgrade version is actually at 4.2.0 but our 
 management server code version is at 4.2.1-SNAPSHOT
 2013-10-04 06:27:43,296 ERROR [utils.component.ComponentContext] 
 (Timer-2:null) System integrity check failed. Refuse to startup
 com.cloud.utils.exception.CloudRuntimeException: The end upgrade version is 
 actually at 4.2.0 but our management server code version is at 4.2.1-SNAPSHOT
 at 
 com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:228)
 at 
 com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:391)
 at 
 com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:90)
 at 
 com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54)
 at java.util.TimerThread.mainLoop(Timer.java:534)
 at java.util.TimerThread.run(Timer.java:484)
   
   



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (CLOUDSTACK-2140) Host is still marked as being in Up state when the host is shutdown (when there are no more hosts in the cluster)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13790215#comment-13790215
 ] 

Abhinandan Prateek commented on CLOUDSTACK-2140:


Changing the fixVersion to future.

 Host is still marked as being in Up state when the host is shutdown (when 
 there are no more hosts in the cluster)
 ---

 Key: CLOUDSTACK-2140
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2140
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.2.0, 4.2.1
 Environment: build from master
Reporter: Sangeetha Hariharan
Assignee: Koushik Das
 Fix For: Future

 Attachments: management-server.rar


 Host is still marked as being in Up state when the host is shutdown (when 
 there are no more hosts in the cluster.
 Set up:
 Advanced zone.
 3 hosts in a cluster ( in my case host id - 7 ,8 ,9 ).
 I did not have any problems when host 8 and host 9 where shutdown.
 When I tried to shutdown host 7 , I see the host still being in Up state , 
 even after the management server detected that it is not able to connect with 
 this host.
 Following exception seen in management server logs:
 2013-04-22 14:48:18,350 DEBUG [xen.resource.XenServerConnectionPool] 
 (DirectAgent-350:null) localLogout has problem Failed to read server's 
 response: connect timed out
 2013-04-22 14:48:18,350 WARN  [xen.resource.CitrixResourceBase] 
 (DirectAgent-350:null) Unable to stop i-3-45-VM due to
 com.cloud.utils.exception.CloudRuntimeException: Unable to reset master of 
 slave 10.223.59.4 to 10.223.59.2 due to org.apache.xmlrpc.XmlRpcException: 
 Failed to read server's response: connect timed out
 at 
 com.cloud.hypervisor.xen.resource.XenServerConnectionPool.PoolEmergencyResetMaster(XenServerConnectionPool.java:443)
 at 
 com.cloud.hypervisor.xen.resource.XenServerConnectionPool.connect(XenServerConnectionPool.java:661)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.getConnection(CitrixResourceBase.java:5583)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:3728)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:474)
 at 
 com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
 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-04-22 14:48:18,364 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-350:null) Seq 9-72160431: Response Received:
 2013-04-22 14:48:18,370 DEBUG [agent.transport.Request] 
 (DirectAgent-350:null) Seq 9-72160431: Processing:  { Ans: , MgmtId: 
 7508777239729, via: 9, Ver: v1, Flags: 110, 
 [{StopAnswer:{result:false,details:Exception: 
 com.cloud.utils.exception.CloudRuntimeException\nMessage: Unable to reset 
 master of slave 10.223.59.4 to 10.223.59.2 due to 
 org.apache.xmlrpc.XmlRpcException: Failed to read server's response: connect 
 timed out\nStack: com.cloud.utils.exception.CloudRuntimeException: Unable to 
 reset master of slave 10.223.59.4 to 10.223.59.2 due to 
 org.apache.xmlrpc.XmlRpcException: Failed to read server's response: connect 
 timed out\n\tat 
 com.cloud.hypervisor.xen.resource.XenServerConnectionPool.PoolEmergencyResetMaster(XenServerConnectionPool.java:443)\n\tat
  
 com.cloud.hypervisor.xen.resource.XenServerConnectionPool.connect(XenServerConnectionPool.java:661)\n\tat
  
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.getConnection(CitrixResourceBase.java:5583)\n\tat
  
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:3728)\n\tat
  
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:474)\n\tat
  
 com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)\n\tat

[jira] [Updated] (CLOUDSTACK-4681) data disk with local disk offering are geting created on shared storage .


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4681:
---

Assignee: Rajesh Battala

 data disk  with  local disk offering  are geting created on shared storage . 
 -

 Key: CLOUDSTACK-4681
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4681
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller
Affects Versions: 4.2.1
 Environment: hypervisor:KVM
Reporter: prashant kumar mishra
Assignee: Rajesh Battala
Priority: Critical
 Fix For: 4.2.1

 Attachments: Logs_DB.rar


 Steps to reproduce
 
 1-prapare a CS setup with kvm host +zone wide primary
 2-deploy a vm
 3-enable local storage at zone level(do not restart MS )
 4-create a local disk offering
 5-create a service offering with storage type local 
 6-deploy a vm with local SO and local disk offering  
 Expected
 --
 1-since local storage is not visible to MS(did not restart MS) vm deployment  
 should fail 
 Actual
 ---
 vm root and data disk are getting created on shared storage
 My observation
 --
 1-After MS restart root disk and data disk  are getting created on local 
 storage.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Closed] (CLOUDSTACK-3803) Unable to complete Add zone wizard.

[
https://issues.apache.org/jira/browse/CLOUDSTACK-3803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

shweta agarwal closed CLOUDSTACK-3803.
--

verified . Passed

Unable to complete Add zone wizard.
---

Key: CLOUDSTACK-3803
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3803
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: UI
Affects Versions: 4.2.0
Environment: Build: CloudPlatform-4.2-263-rhel6.3
Management Server is running on CentOS 6.3.
Reporter: Pradeep S
Assignee: Brian Federle
Fix For: 4.2.1

Attachments: add-zone1.swf

Steps to Reproduce:
---
1. Login to Management Server UI. http://MS-IP:8080/client
2. Navigate to Infrastructure-Zones-Add Zone wizard.
3. Continue with Basic Zone type.
4. Enter the details for zone, pod, cluster, host, primary storage.
5. Before entering the details of secondary storage, click next, so that it
shows the mandatory fields as required.
6. After that, enter the details in all the fields of secondary storage
configuration and click next.
Observation:

While entering the details of secondary storage, if we first click next in
that screen and then enter all the required values, it still shows the fields
marked with * as required and it is unable to proceed to the next step
and complete adding a new zone.
It that case, we should cancel the add zone wizard and should start from the
beginning by entering all details of zone, pod, cluster, host, primary and
secondary storage once again.
Expected behavior:
-
Even if we missed to enter the details in some mandatory fields of secondary
storage and then enter those details after system shows the fields as
required, it should be able to proceed and complete the add zone wizard.

--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (CLOUDSTACK-4681) data disk with local disk offering are geting created on shared storage .


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13790219#comment-13790219
 ] 

Abhinandan Prateek commented on CLOUDSTACK-4681:


Rajesh, Can you verify and fix this issue for KVM ?

 data disk  with  local disk offering  are geting created on shared storage . 
 -

 Key: CLOUDSTACK-4681
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4681
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller
Affects Versions: 4.2.1
 Environment: hypervisor:KVM
Reporter: prashant kumar mishra
Assignee: Rajesh Battala
Priority: Critical
 Fix For: 4.2.1

 Attachments: Logs_DB.rar


 Steps to reproduce
 
 1-prapare a CS setup with kvm host +zone wide primary
 2-deploy a vm
 3-enable local storage at zone level(do not restart MS )
 4-create a local disk offering
 5-create a service offering with storage type local 
 6-deploy a vm with local SO and local disk offering  
 Expected
 --
 1-since local storage is not visible to MS(did not restart MS) vm deployment  
 should fail 
 Actual
 ---
 vm root and data disk are getting created on shared storage
 My observation
 --
 1-After MS restart root disk and data disk  are getting created on local 
 storage.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4631) [Automation] Failed to create snapshot from volume due to storage pool missing error in libvirtd


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4631:
---

Fix Version/s: (was: 4.2.1)
   4.3.0

 [Automation] Failed to create snapshot from volume due to storage pool 
 missing error in libvirtd
 

 Key: CLOUDSTACK-4631
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4631
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM, Snapshot
Affects Versions: 4.2.1
 Environment: RHEL 6.3
 Automation env
 Branch : 4.2.0-forward 
Reporter: Rayees Namathponnan
Assignee: edison su
Priority: Critical
 Fix For: 4.3.0

 Attachments: CLOUDSTACK-4628.rar


 This issue found while running regression test case 
 integration.component.test_project_resources.TestSnapshots.test_06_create_snapshots_in_project
 Test case failing while creating snapshot, observed below error MS log; there 
 are some other snapshot test cases; its not effect; looks like its a 
 inconsistent issue 
 2013-09-09 10:45:47,445 DEBUG [agent.transport.Request] 
 (AgentManager-Handler-14:null) Seq 1-1436357958: Processing:  { Ans: , 
 MgmtId: 29066118877352, via: 1
 , Ver: v1, Flags: 110, 
 [{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:com.cloud.utils.exception.CloudRuntimeException:
  co
 m.cloud.utils.exception.CloudRuntimeException: org.libvirt.LibvirtException: 
 internal error Child process (/bin/umount 
 /mnt/fff90cb5-06dd-33b3-8815-d78c08ca0
 1d9) status unexpected: exit status 16,wait:0}}] }
 2013-09-09 10:45:47,446 DEBUG [agent.manager.AgentAttache] 
 (AgentManager-Handler-14:null) Seq 1-1436357970: Sending now.  is current 
 sequence.
 2013-09-09 10:45:47,446 DEBUG [agent.transport.Request] 
 (Job-Executor-146:job-1770 = [ 53db2ef6-6a92-4b69-bc5a-ea673814a4b9 ]) Seq 
 1-1436357958: Received:  {
  Ans: , MgmtId: 29066118877352, via: 1, Ver: v1, Flags: 110, { CopyCmdAnswer 
 } }
 2013-09-09 10:45:47,458 DEBUG [storage.snapshot.SnapshotManagerImpl] 
 (Job-Executor-146:job-1770 = [ 53db2ef6-6a92-4b69-bc5a-ea673814a4b9 ]) Failed 
 to create
 snapshot
 com.cloud.utils.exception.CloudRuntimeException: 
 com.cloud.utils.exception.CloudRuntimeException: 
 com.cloud.utils.exception.CloudRuntimeException: org.libvir
 t.LibvirtException: internal error Child process (/bin/umount 
 /mnt/fff90cb5-06dd-33b3-8815-d78c08ca01d9) status unexpected: exit status 16
 at 
 org.apache.cloudstack.storage.snapshot.SnapshotServiceImpl.backupSnapshot(SnapshotServiceImpl.java:280)
 at 
 org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy.backupSnapshot(XenserverSnapshotStrategy.java:138)
 at 
 org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy.takeSnapshot(XenserverSnapshotStrategy.java:264)
 at 
 com.cloud.storage.snapshot.SnapshotManagerImpl.takeSnapshot(SnapshotManagerImpl.java:1013)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.storage.volume.VolumeServiceImpl.takeSnapshot(VolumeServiceImpl.java:1307)
 at 
 com.cloud.storage.VolumeManagerImpl.takeSnapshot(VolumeManagerImpl.java:2738)
 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.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-09-09 10:45:47,465 DEBUG [storage.volume.VolumeServiceImpl] 
 (Job-Executor-146:job-1770 = [ 53db2ef6-6a92-4b69-bc5a-ea673814a4b9 ]) Take 
 snapshot: 498 fa
 iled
 com.cloud.utils.exception.CloudRuntimeException: Failed to create snapshot
 at 
 com.cloud.storage.snapshot.SnapshotManagerImpl.takeSnapshot(SnapshotManagerImpl.java:1040)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.storage.volume.VolumeServiceImpl.takeSnapshot(VolumeServiceImpl.java:1307)
 at

[jira] [Updated] (CLOUDSTACK-4139) [VMWARE][ZWPS] Failed to resize the volumes which are created from snapshot


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4139:
---

Fix Version/s: (was: 4.2.1)
   4.3.0

 [VMWARE][ZWPS] Failed to resize the volumes which are created from snapshot 
 

 Key: CLOUDSTACK-4139
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4139
 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
Reporter: Sailaja Mada
Assignee: Venkata Siva Vijayendra Bhamidipati
Priority: Critical
 Fix For: 4.3.0

 Attachments: apilog.log, management-server.log, newdb.sql


 Steps:
 1. Configure Adv zone with VMWARE cluster with Zone wide primary storage
 2.  Deploy instance 
 3. Create snapshot from ROOT volume
 4. Attach the volume to an instance 
 5. Tried to resize the volume from 2 GB to 5 GB .
 Observation:
 1. It  Failed to resize the volumes which are created from snapshot .
 2. Task notification says resize is completed from UI but it failed and no 
 resize happened for this volume
 3. I could resize the DATA volumes which are added by using the disk offering 
 and attached to the instance. 
 2013-08-07 16:37:31,370 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentManager-Handler-6:null) SeqA 3-785: Sending Seq 3-785:  { Ans: , 
 MgmtId: 187767034175903, via: 3, Ver: v1, Flags: 100010, 
 [{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
 2013-08-07 16:37:33,253 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null) 
 ===START===  10.144.6.19 -- GET  
 command=resizeVolumeid=480c853c-e70a-46a0-a6d6-ae74b416f318shrinkok=falsediskofferingid=34443d4d-f29c-4d3f-8bb6-f6ae76e34b0dresponse=jsonsessionkey=nmiUJgTgEEYHRt8hx5StkuJr5tA%3D_=1375873540089
 2013-08-07 16:37:33,296 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (catalina-exec-21:null) submit async job-49 = [ 
 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ], details: AsyncJobVO {id:49, userId: 
 3, accountId: 3, sessionKey: null, instanceType: Volume, instanceId: null, 
 cmd: org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd, 
 cmdOriginator: null, cmdInfo: 
 {id:480c853c-e70a-46a0-a6d6-ae74b416f318,response:json,sessionkey:nmiUJgTgEEYHRt8hx5StkuJr5tA\u003d,shrinkok:false,cmdEventType:VOLUME.RESIZE,ctxUserId:3,httpmethod:GET,_:1375873540089,ctxAccountId:3,diskofferingid:34443d4d-f29c-4d3f-8bb6-f6ae76e34b0d,ctxStartEventId:182},
  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
 processStatus: 0, resultCode: 0, result: null, initMsid: 187767034175903, 
 completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
 2013-08-07 16:37:33,301 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null) 
 ===END===  10.144.6.19 -- GET  
 command=resizeVolumeid=480c853c-e70a-46a0-a6d6-ae74b416f318shrinkok=falsediskofferingid=34443d4d-f29c-4d3f-8bb6-f6ae76e34b0dresponse=jsonsessionkey=nmiUJgTgEEYHRt8hx5StkuJr5tA%3D_=1375873540089
 2013-08-07 16:37:33,342 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-32:job-49 = [ 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]) Executing 
 org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd for job-49 = [ 
 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]
 2013-08-07 16:37:33,488 DEBUG [cloud.user.AccountManagerImpl] 
 (Job-Executor-32:job-49 = [ 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]) Access to 
 Vol[35|vm=16|DATADISK] granted to Acct[3-cdcuser1] by 
 DomainChecker_EnhancerByCloudStack_ccb7a71
 2013-08-07 16:37:33,534 DEBUG [agent.transport.Request] 
 (Job-Executor-32:job-49 = [ 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]) Seq 
 2-1287389738: Sending  { Cmd , MgmtId: 187767034175903, via: 2, Ver: v1, 
 Flags: 100011, 
 [{com.cloud.agent.api.storage.ResizeVolumeCommand:{path:e9166262ee514a398028c04bf21d80b7,pool:{id:2,uuid:004a6f4c-232c-3a09-9013-e47fe47da3fb,host:10.102.192.100,path:/cpg_vol/sailaja/finalps2,port:2049,type:NetworkFilesystem},vmInstance:i-3-16-VM,newSize:5368709120,currentSize:2147483648,shrinkOk:false,wait:0}}]
  }
 2013-08-07 16:37:33,534 DEBUG [agent.transport.Request] 
 (Job-Executor-32:job-49 = [ 40ec270a-a5ff-450d-9c5d-9ee3bfb87b98 ]) Seq 
 2-1287389738: Executing:  { Cmd , MgmtId: 187767034175903, via: 2, Ver: v1, 
 Flags: 100011, 
 [{com.cloud.agent.api.storage.ResizeVolumeCommand:{path:e9166262ee514a398028c04bf21d80b7,pool:{id:2,uuid:004a6f4c-232c-3a09-9013-e47fe47da3fb,host:10.102.192.100,path:/cpg_vol/sailaja/finalps2,port:2049,type:NetworkFilesystem},vmInstance:i-3-16-VM,newSize:5368709120,currentSize:2147483648,shrinkOk:false,wait:0}}]
  }
 2013-08-07 16:37:33,557 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-32:null) Seq 2-1287389738: Executing

[jira] [Updated] (CLOUDSTACK-4247) [VMWARE]Network read/write statistics is zero always


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4247:
---

Fix Version/s: (was: 4.2.1)
   4.3.0

 [VMWARE]Network read/write statistics is zero always
 

 Key: CLOUDSTACK-4247
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4247
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: VMware
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Assignee: Sateesh Chodapuneedi
Priority: Critical
 Fix For: 4.3.0

 Attachments: apilog.log, management-server.log, networkdb.sql, 
 networkstatistics.png


 Steps:
 1. Configure Adv Networking zone with ESXi server 
 2. Create a new account and deploy VM 
 3. Configure Rules ( LB and Firewall rules with 22 port)
 4.  SSH to VM and verify that it is reachable 
 5. Tried to view the network statistics of this instance
  Observation :
 1. Network read/write statistics is zero always



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4506) In a mixed hypervisor setup, destroying a VM whose host has been removed, throws a NPE and the ROOT volume of that VM also is not deleted from the primary.


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4506:
---

Fix Version/s: (was: 4.2.1)
   4.3.0

 In a mixed hypervisor setup, destroying a VM whose host has been removed, 
 throws a NPE and the ROOT volume of that VM also is not deleted from the 
 primary.
 ---

 Key: CLOUDSTACK-4506
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4506
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller
Affects Versions: 4.2.0
 Environment: Advanced zone setup having clusters of different 
 hypervisor types. Ex KVM and VMWARE
Reporter: Abhinav Roy
Priority: Critical
 Fix For: 4.3.0

 Attachments: CS-4506.zip


 Steps :
 =
 1. Deploy a CS 4.2 setup with KVM and VMWARE clusters having one host each.
 2. Create some VMs on KVM (ex- kvm1 and kvm2)
 3. Put the KVM host in maintenance mode and then remove the Host. Now kvm1 
 and kvm2 are in stopped state.
 4. Destroy kvm1 
 Observations :
 
 1. when kvm1 is destroyed it fails with the following exception 
 2013-08-26 13:10:09,205 DEBUG [cloud.api.ApiServlet] (catalina-exec-19:null) 
 ===START===  10.144.6.17 -- GET  
 command=destroyVirtualMachineid=d613f6e5-c53a-4f6b-be31-32f101eb6c99response=jsonsessionkey=bU49tWdfVUJUrq65PbMmzGbe0PE%3D_=1377502661180
 2013-08-26 13:10:09,242 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (catalina-exec-19:null) submit async job-78 = [ 
 8018e79c-a47e-4a54-b3a4-68963f3c11a9 ], details: AsyncJobVO {id:78, userId: 
 2, accountId: 2, sessionKey: null, instanceType: VirtualMachine, instanceId: 
 3, cmd: org.apache.cloudstack.api.command.user.vm.DestroyVMCmd, 
 cmdOriginator: null, cmdInfo: 
 {response:json,id:d613f6e5-c53a-4f6b-be31-32f101eb6c99,sessionkey:bU49tWdfVUJUrq65PbMmzGbe0PE\u003d,cmdEventType:VM.DESTROY,ctxUserId:2,httpmethod:GET,_:1377502661180,ctxAccountId:2,ctxStartEventId:245},
  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
 processStatus: 0, resultCode: 0, result: null, initMsid: 226870599129537, 
 completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
 2013-08-26 13:10:09,245 DEBUG [cloud.api.ApiServlet] (catalina-exec-19:null) 
 ===END===  10.144.6.17 -- GET  
 command=destroyVirtualMachineid=d613f6e5-c53a-4f6b-be31-32f101eb6c99response=jsonsessionkey=bU49tWdfVUJUrq65PbMmzGbe0PE%3D_=1377502661180
 2013-08-26 13:10:09,249 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-50:job-78 = [ 8018e79c-a47e-4a54-b3a4-68963f3c11a9 ]) Executing 
 org.apache.cloudstack.api.command.user.vm.DestroyVMCmd for job-78 = [ 
 8018e79c-a47e-4a54-b3a4-68963f3c11a9 ]
 2013-08-26 13:10:09,282 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-50:job-78 = [ 8018e79c-a47e-4a54-b3a4-68963f3c11a9 ]) 
 Destroying vm VM[User|v1]
 2013-08-26 13:10:09,282 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-50:job-78 = [ 8018e79c-a47e-4a54-b3a4-68963f3c11a9 ]) VM is 
 already stopped: VM[User|v1]
 2013-08-26 13:10:09,308 DEBUG [cloud.capacity.CapacityManagerImpl] 
 (Job-Executor-50:job-78 = [ 8018e79c-a47e-4a54-b3a4-68963f3c11a9 ]) VM state 
 transitted from :Stopped to Destroyed with event: DestroyRequestedvm's 
 original host id: 1 new host id: null host id before state transition: null
 2013-08-26 13:10:09,324 ERROR [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-50:job-78 = [ 8018e79c-a47e-4a54-b3a4-68963f3c11a9 ]) 
 Unexpected exception while executing 
 org.apache.cloudstack.api.command.user.vm.DestroyVMCmd
 java.lang.NullPointerException
 at 
 com.cloud.capacity.CapacityManagerImpl.releaseVmCapacity(CapacityManagerImpl.java:187)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.capacity.CapacityManagerImpl.postStateTransitionEvent(CapacityManagerImpl.java:718)
 at 
 com.cloud.capacity.CapacityManagerImpl.postStateTransitionEvent(CapacityManagerImpl.java:101)
 at com.cloud.utils.fsm.StateMachine2.transitTo(StateMachine2.java:117)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.stateTransitTo(VirtualMachineManagerImpl.java:1324)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.destroy(VirtualMachineManagerImpl.java:1355)
 at 
 org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.destroyVirtualMachine(VMEntityManagerImpl.java:259)
 at

[jira] [Updated] (CLOUDSTACK-4506) In a mixed hypervisor setup, destroying a VM whose host has been removed, throws a NPE and the ROOT volume of that VM also is not deleted from the primary.


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4506:
---

Assignee: (was: Nitin Mehta)

 In a mixed hypervisor setup, destroying a VM whose host has been removed, 
 throws a NPE and the ROOT volume of that VM also is not deleted from the 
 primary.
 ---

 Key: CLOUDSTACK-4506
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4506
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller
Affects Versions: 4.2.0
 Environment: Advanced zone setup having clusters of different 
 hypervisor types. Ex KVM and VMWARE
Reporter: Abhinav Roy
Priority: Critical
 Fix For: 4.3.0

 Attachments: CS-4506.zip


 Steps :
 =
 1. Deploy a CS 4.2 setup with KVM and VMWARE clusters having one host each.
 2. Create some VMs on KVM (ex- kvm1 and kvm2)
 3. Put the KVM host in maintenance mode and then remove the Host. Now kvm1 
 and kvm2 are in stopped state.
 4. Destroy kvm1 
 Observations :
 
 1. when kvm1 is destroyed it fails with the following exception 
 2013-08-26 13:10:09,205 DEBUG [cloud.api.ApiServlet] (catalina-exec-19:null) 
 ===START===  10.144.6.17 -- GET  
 command=destroyVirtualMachineid=d613f6e5-c53a-4f6b-be31-32f101eb6c99response=jsonsessionkey=bU49tWdfVUJUrq65PbMmzGbe0PE%3D_=1377502661180
 2013-08-26 13:10:09,242 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (catalina-exec-19:null) submit async job-78 = [ 
 8018e79c-a47e-4a54-b3a4-68963f3c11a9 ], details: AsyncJobVO {id:78, userId: 
 2, accountId: 2, sessionKey: null, instanceType: VirtualMachine, instanceId: 
 3, cmd: org.apache.cloudstack.api.command.user.vm.DestroyVMCmd, 
 cmdOriginator: null, cmdInfo: 
 {response:json,id:d613f6e5-c53a-4f6b-be31-32f101eb6c99,sessionkey:bU49tWdfVUJUrq65PbMmzGbe0PE\u003d,cmdEventType:VM.DESTROY,ctxUserId:2,httpmethod:GET,_:1377502661180,ctxAccountId:2,ctxStartEventId:245},
  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
 processStatus: 0, resultCode: 0, result: null, initMsid: 226870599129537, 
 completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
 2013-08-26 13:10:09,245 DEBUG [cloud.api.ApiServlet] (catalina-exec-19:null) 
 ===END===  10.144.6.17 -- GET  
 command=destroyVirtualMachineid=d613f6e5-c53a-4f6b-be31-32f101eb6c99response=jsonsessionkey=bU49tWdfVUJUrq65PbMmzGbe0PE%3D_=1377502661180
 2013-08-26 13:10:09,249 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-50:job-78 = [ 8018e79c-a47e-4a54-b3a4-68963f3c11a9 ]) Executing 
 org.apache.cloudstack.api.command.user.vm.DestroyVMCmd for job-78 = [ 
 8018e79c-a47e-4a54-b3a4-68963f3c11a9 ]
 2013-08-26 13:10:09,282 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-50:job-78 = [ 8018e79c-a47e-4a54-b3a4-68963f3c11a9 ]) 
 Destroying vm VM[User|v1]
 2013-08-26 13:10:09,282 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-50:job-78 = [ 8018e79c-a47e-4a54-b3a4-68963f3c11a9 ]) VM is 
 already stopped: VM[User|v1]
 2013-08-26 13:10:09,308 DEBUG [cloud.capacity.CapacityManagerImpl] 
 (Job-Executor-50:job-78 = [ 8018e79c-a47e-4a54-b3a4-68963f3c11a9 ]) VM state 
 transitted from :Stopped to Destroyed with event: DestroyRequestedvm's 
 original host id: 1 new host id: null host id before state transition: null
 2013-08-26 13:10:09,324 ERROR [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-50:job-78 = [ 8018e79c-a47e-4a54-b3a4-68963f3c11a9 ]) 
 Unexpected exception while executing 
 org.apache.cloudstack.api.command.user.vm.DestroyVMCmd
 java.lang.NullPointerException
 at 
 com.cloud.capacity.CapacityManagerImpl.releaseVmCapacity(CapacityManagerImpl.java:187)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.capacity.CapacityManagerImpl.postStateTransitionEvent(CapacityManagerImpl.java:718)
 at 
 com.cloud.capacity.CapacityManagerImpl.postStateTransitionEvent(CapacityManagerImpl.java:101)
 at com.cloud.utils.fsm.StateMachine2.transitTo(StateMachine2.java:117)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.stateTransitTo(VirtualMachineManagerImpl.java:1324)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.destroy(VirtualMachineManagerImpl.java:1355)
 at 
 org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.destroyVirtualMachine(VMEntityManagerImpl.java:259)
 at

[jira] [Updated] (CLOUDSTACK-4598) [Performance Testing] High delays during deployVM - both network delay and deployment planner delay


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4598:
---

Fix Version/s: (was: 4.2.1)
   4.3.0

 [Performance Testing] High delays during deployVM - both network delay and 
 deployment planner delay
 ---

 Key: CLOUDSTACK-4598
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4598
 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: Simulator environment with large scale set up
Reporter: Sowmya Krishnan
Assignee: Murali Reddy
Priority: Critical
 Fix For: 4.3.0

 Attachments: deployVMjob_999.log.gz


 This is mostly similar to CLOUDSTACK-3441 and CLOUDSTACK-4179. Both these 
 issues were fixed and verified in comparatively smaller environment with 4K 
 and 8K hosts and 12K VMs
 Now trying in much larger infrastructure with 20k hosts, 20K clusters and 2K 
 Pods. This is also a special case where we are trying to deploy one VM in 
 each host. 
 I am seeing delay both while acquiring network lock and during deployment 
 planning.
 (There was also an ERROR observed in the log during deployment)
 Log snippet:
 2013-09-02 22:40:52,335 DEBUG [cloud.deploy.FirstFitPlanner] 
 (Job-Executor-336:job-999 = [ f437e46a-dfa4-4cea-a518-7da2f5360a89 ]) Listing 
 clusters in order of aggregate capacity, that have (atleast one host with) 
 enough CPU and RAM capacity under this Zone: 1
 2013-09-02 22:40:57,544 DEBUG [cloud.deploy.FirstFitPlanner] 
 (Job-Executor-336:job-999 = [ f437e46a-dfa4-4cea-a518-7da2f5360a89 ]) 
 Removing from the clusterId list these clusters from avoid set: []
 ..
 ..
 2013-09-02 22:41:05,637 DEBUG [cloud.network.NetworkManagerImpl] 
 (Job-Executor-336:job-999 = [ f437e46a-dfa4-4cea-a518-7da2f5360a89 ]) 
 Changing active number
  of nics for network id=204 on 1
 2013-09-02 22:41:05,690 DEBUG [cloud.network.NetworkManagerImpl] 
 (Job-Executor-336:job-999 = [ f437e46a-dfa4-4cea-a518-7da2f5360a89 ]) Asking 
 VirtualRouter to prepare for 
 Nic[2246-1407-0d530dd3-3f25-4fde-b1fb-9ff9188f89e6-172.4.211.191]
 2013-09-02 22:51:04,680 ERROR [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-336:job-999 = [ f437e46a-dfa4-4cea-a518-7da2f5360a89 ]) Failed 
 to start instance VM[User|414aa09b-a38c-4b30-bf9c-f1d9fe51134f]
 2013-09-02 22:51:04,702 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-336:job-999 = [ f437e46a-dfa4-4cea-a518-7da2f5360a89 ]) 
 Cleaning up resources for the vm 
 VM[User|414aa09b-a38c-4b30-bf9c-f1d9fe51134f] in Starting state
 ..
 ..
 2013-09-02 22:51:17,018 DEBUG [cloud.network.NetworkManagerImpl] 
 (Job-Executor-336:job-999 = [ f437e46a-dfa4-4cea-a518-7da2f5360a89 ]) 
 Changing active number of nics for network id=204 on 1
 2013-09-02 22:51:17,074 DEBUG [cloud.network.NetworkManagerImpl] 
 (Job-Executor-336:job-999 = [ f437e46a-dfa4-4cea-a518-7da2f5360a89 ]) Asking 
 VirtualRouter to prepare for 
 Nic[2246-1407-159bacce-8663-477e-ab37-2d1081c0630b-172.4.211.191]
 2013-09-02 22:57:56,139 DEBUG 
 [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-336:job-999 
 = [ f437e46a-dfa4-4cea-a518-7da2f5360a89 ]) Lock is acquired for network id 
 204 as a part of router startup in 
 Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Pool(Id))]
  : 
 Dest[Zone(1)-Pod(975)-Cluster(9749)-Host(9750)-Storage(Volume(1407|ROOT--Pool(9749))]
 2013-09-02 22:57:56,144 DEBUG 
 [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-336:job-999 
 = [ f437e46a-dfa4-4cea-a518-7da2f5360a89 ]) Lock is released for network id 
 204 as a part of router startup in 
 Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Pool(Id))]
  : 
 Dest[Zone(1)-Pod(975)-Cluster(9749)-Host(9750)-Storage(Volume(1407|ROOT--Pool(9749))]
 ..
 ..



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (CLOUDSTACK-4533) permission issue in usage server and it failed to start after upgrade from 3.0.4 to 4.2


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13790232#comment-13790232
 ] 

Abhinandan Prateek commented on CLOUDSTACK-4533:


Wei Zhou, Can you close the ticket if it is fixed ?

 permission issue in usage server and it failed to start after upgrade from 
 3.0.4 to 4.2
 ---

 Key: CLOUDSTACK-4533
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4533
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Packaging, Upgrade, Usage
Affects Versions: 4.2.1
 Environment: 
Reporter: shweta agarwal
Assignee: frank zhang
Priority: Critical
  Labels: ReleaseNote
 Fix For: 4.2.1

 Attachments: cloudstack-usage.err, cloudstack-usage.err, 
 cloudstack-usage.out, cloudstack-usage.out, usage.log


 did an upgrade from 3.0.4 to 4.2  and then start usage server. 
 Usage server failed to start
 giving following exception :
 log4j:ERROR setFile(null,true) call failed.
 java.io.FileNotFoundException: /var/log/cloudstack/usage/usage.log 
 (Permission denied)
 at java.io.FileOutputStream.openAppend(Native Method)
 at java.io.FileOutputStream.init(FileOutputStream.java:207)
 at java.io.FileOutputStream.init(FileOutputStream.java:131)
 at org.apache.log4j.FileAppender.setFile(FileAppender.java:294)
 at 
 org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165)
 at 
 org.apache.log4j.rolling.RollingFileAppender.activateOptions(RollingFileAppender.java:179)
 at 
 org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307)
 at 
 org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:295)
 at 
 org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:176)
 at 
 org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:191)
 at 
 org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:523)
 at 
 org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:492)
 at 
 org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:1001)
 at 
 org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:867)
 at 
 org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:773)
 at 
 org.apache.log4j.xml.DOMConfigurator.configure(DOMConfigurator.java:901)
 at 
 org.springframework.util.Log4jConfigurer.initLogging(Log4jConfigurer.java:69)
 at com.cloud.usage.UsageServer.initLog4j(UsageServer.java:89)
 at com.cloud.usage.UsageServer.init(UsageServer.java:52)
 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.commons.daemon.support.DaemonLoader.load(DaemonLoader.java:207)
 log4j:ERROR setFile(null,true) call failed.
 java.io.FileNotFoundException: /var/log/cloudstack/usage/usage.log 
 (Permission denied)
 at java.io.FileOutputStream.openAppend(Native Method)
 at java.io.FileOutputStream.init(FileOutputStream.java:207)
 at java.io.FileOutputStream.init(FileOutputStream.java:131)
 at org.apache.log4j.FileAppender.setFile(FileAppender.java:294)
 at 
 org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165)
 at 
 org.apache.log4j.rolling.RollingFileAppender.activateOptions(RollingFileAppender.java:179)
 at 
 org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307)
 at 
 org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:295)
 at 
 org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:176)
 at 
 org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:191)
 at 
 org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:523)
 at 
 org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:492)
 at 
 org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:1001)
 at 
 org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:867)
 at 
 org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:755)
 Attaching full logs.

[jira] [Commented] (CLOUDSTACK-4598) [Performance Testing] High delays during deployVM - both network delay and deployment planner delay


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13790234#comment-13790234
 ] 

Abhinandan Prateek commented on CLOUDSTACK-4598:


Performance issue moving to 4.3

 [Performance Testing] High delays during deployVM - both network delay and 
 deployment planner delay
 ---

 Key: CLOUDSTACK-4598
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4598
 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: Simulator environment with large scale set up
Reporter: Sowmya Krishnan
Assignee: Murali Reddy
Priority: Critical
 Fix For: 4.3.0

 Attachments: deployVMjob_999.log.gz


 This is mostly similar to CLOUDSTACK-3441 and CLOUDSTACK-4179. Both these 
 issues were fixed and verified in comparatively smaller environment with 4K 
 and 8K hosts and 12K VMs
 Now trying in much larger infrastructure with 20k hosts, 20K clusters and 2K 
 Pods. This is also a special case where we are trying to deploy one VM in 
 each host. 
 I am seeing delay both while acquiring network lock and during deployment 
 planning.
 (There was also an ERROR observed in the log during deployment)
 Log snippet:
 2013-09-02 22:40:52,335 DEBUG [cloud.deploy.FirstFitPlanner] 
 (Job-Executor-336:job-999 = [ f437e46a-dfa4-4cea-a518-7da2f5360a89 ]) Listing 
 clusters in order of aggregate capacity, that have (atleast one host with) 
 enough CPU and RAM capacity under this Zone: 1
 2013-09-02 22:40:57,544 DEBUG [cloud.deploy.FirstFitPlanner] 
 (Job-Executor-336:job-999 = [ f437e46a-dfa4-4cea-a518-7da2f5360a89 ]) 
 Removing from the clusterId list these clusters from avoid set: []
 ..
 ..
 2013-09-02 22:41:05,637 DEBUG [cloud.network.NetworkManagerImpl] 
 (Job-Executor-336:job-999 = [ f437e46a-dfa4-4cea-a518-7da2f5360a89 ]) 
 Changing active number
  of nics for network id=204 on 1
 2013-09-02 22:41:05,690 DEBUG [cloud.network.NetworkManagerImpl] 
 (Job-Executor-336:job-999 = [ f437e46a-dfa4-4cea-a518-7da2f5360a89 ]) Asking 
 VirtualRouter to prepare for 
 Nic[2246-1407-0d530dd3-3f25-4fde-b1fb-9ff9188f89e6-172.4.211.191]
 2013-09-02 22:51:04,680 ERROR [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-336:job-999 = [ f437e46a-dfa4-4cea-a518-7da2f5360a89 ]) Failed 
 to start instance VM[User|414aa09b-a38c-4b30-bf9c-f1d9fe51134f]
 2013-09-02 22:51:04,702 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-336:job-999 = [ f437e46a-dfa4-4cea-a518-7da2f5360a89 ]) 
 Cleaning up resources for the vm 
 VM[User|414aa09b-a38c-4b30-bf9c-f1d9fe51134f] in Starting state
 ..
 ..
 2013-09-02 22:51:17,018 DEBUG [cloud.network.NetworkManagerImpl] 
 (Job-Executor-336:job-999 = [ f437e46a-dfa4-4cea-a518-7da2f5360a89 ]) 
 Changing active number of nics for network id=204 on 1
 2013-09-02 22:51:17,074 DEBUG [cloud.network.NetworkManagerImpl] 
 (Job-Executor-336:job-999 = [ f437e46a-dfa4-4cea-a518-7da2f5360a89 ]) Asking 
 VirtualRouter to prepare for 
 Nic[2246-1407-159bacce-8663-477e-ab37-2d1081c0630b-172.4.211.191]
 2013-09-02 22:57:56,139 DEBUG 
 [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-336:job-999 
 = [ f437e46a-dfa4-4cea-a518-7da2f5360a89 ]) Lock is acquired for network id 
 204 as a part of router startup in 
 Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Pool(Id))]
  : 
 Dest[Zone(1)-Pod(975)-Cluster(9749)-Host(9750)-Storage(Volume(1407|ROOT--Pool(9749))]
 2013-09-02 22:57:56,144 DEBUG 
 [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-336:job-999 
 = [ f437e46a-dfa4-4cea-a518-7da2f5360a89 ]) Lock is released for network id 
 204 as a part of router startup in 
 Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Pool(Id))]
  : 
 Dest[Zone(1)-Pod(975)-Cluster(9749)-Host(9750)-Storage(Volume(1407|ROOT--Pool(9749))]
 ..
 ..



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Closed] (CLOUDSTACK-4533) permission issue in usage server and it failed to start after upgrade from 3.0.4 to 4.2

2013-10-09 Thread Wei Zhou (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wei Zhou closed CLOUDSTACK-4533.


Resolution: Fixed
  Assignee: Wei Zhou  (was: frank zhang)

 permission issue in usage server and it failed to start after upgrade from 
 3.0.4 to 4.2
 ---

 Key: CLOUDSTACK-4533
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4533
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Packaging, Upgrade, Usage
Affects Versions: 4.2.1
 Environment: 
Reporter: shweta agarwal
Assignee: Wei Zhou
Priority: Critical
  Labels: ReleaseNote
 Fix For: 4.2.1

 Attachments: cloudstack-usage.err, cloudstack-usage.err, 
 cloudstack-usage.out, cloudstack-usage.out, usage.log


 did an upgrade from 3.0.4 to 4.2  and then start usage server. 
 Usage server failed to start
 giving following exception :
 log4j:ERROR setFile(null,true) call failed.
 java.io.FileNotFoundException: /var/log/cloudstack/usage/usage.log 
 (Permission denied)
 at java.io.FileOutputStream.openAppend(Native Method)
 at java.io.FileOutputStream.init(FileOutputStream.java:207)
 at java.io.FileOutputStream.init(FileOutputStream.java:131)
 at org.apache.log4j.FileAppender.setFile(FileAppender.java:294)
 at 
 org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165)
 at 
 org.apache.log4j.rolling.RollingFileAppender.activateOptions(RollingFileAppender.java:179)
 at 
 org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307)
 at 
 org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:295)
 at 
 org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:176)
 at 
 org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:191)
 at 
 org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:523)
 at 
 org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:492)
 at 
 org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:1001)
 at 
 org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:867)
 at 
 org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:773)
 at 
 org.apache.log4j.xml.DOMConfigurator.configure(DOMConfigurator.java:901)
 at 
 org.springframework.util.Log4jConfigurer.initLogging(Log4jConfigurer.java:69)
 at com.cloud.usage.UsageServer.initLog4j(UsageServer.java:89)
 at com.cloud.usage.UsageServer.init(UsageServer.java:52)
 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.commons.daemon.support.DaemonLoader.load(DaemonLoader.java:207)
 log4j:ERROR setFile(null,true) call failed.
 java.io.FileNotFoundException: /var/log/cloudstack/usage/usage.log 
 (Permission denied)
 at java.io.FileOutputStream.openAppend(Native Method)
 at java.io.FileOutputStream.init(FileOutputStream.java:207)
 at java.io.FileOutputStream.init(FileOutputStream.java:131)
 at org.apache.log4j.FileAppender.setFile(FileAppender.java:294)
 at 
 org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165)
 at 
 org.apache.log4j.rolling.RollingFileAppender.activateOptions(RollingFileAppender.java:179)
 at 
 org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307)
 at 
 org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:295)
 at 
 org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:176)
 at 
 org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:191)
 at 
 org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:523)
 at 
 org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:492)
 at 
 org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:1001)
 at 
 org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:867)
 at 
 org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:755)
 Attaching full logs.
   
   



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-3788) [KVM] Weekly Snapshot got stuck in Allocated State


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-3788:
---

Assignee: (was: Fang Wang)

 [KVM] Weekly Snapshot got stuck in Allocated State
 

 Key: CLOUDSTACK-3788
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3788
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Snapshot
Affects Versions: 4.2.0
Reporter: Chandan Purushothama
 Fix For: 4.2.1

 Attachments: management-server.log.2013-07-23.gz, 
 mysql_cloudstack_dump.zip


 Weekly Snapshot stuck in Allocated State:
 mysql select * from snapshots where name like 
 Atoms-VM-1_ROOT-6_20130723235146;
 ++++---+---+--+---+--+--+--+---+--++-+-++--++--+-+-+---+
 | id | data_center_id | account_id | domain_id | volume_id | disk_offering_id 
 | status| path | name | uuid  
| snapshot_type | type_description | size   | created  
| removed | backup_snap_id | swift_id | sechost_id | prev_snap_id | 
 hypervisor_type | version | s3_id |
 ++++---+---+--+---+--+--+--+---+--++-+-++--++--+-+-+---+
 | 24 |  1 |  3 | 1 | 6 |1 
 | Destroyed | NULL | Atoms-VM-1_ROOT-6_20130723235146 | 
 08a0d2aa-9635-41cd-ba54-5367303bceac | 3 | HOURLY   | 
 147456 | 2013-07-23 23:51:46 | NULL| NULL   | NULL |   
 NULL | NULL | KVM | 2.2 |  NULL |
 | 25 |  1 |  3 | 1 | 6 |1 
 | Allocated | NULL | Atoms-VM-1_ROOT-6_20130723235146 | 
 1e24a056-be38-4b55-845b-a5672b9fa93c | 5 | WEEKLY   | 
 147456 | 2013-07-23 23:51:46 | NULL| NULL   | NULL |   
 NULL | NULL | KVM | 2.2 |  NULL |
 ++++---+---+--+---+--+--+--+---+--++-+-++--++--+-+-+---+
 2 rows in set (0.04 sec)
 Attached Management Server logs and cloud database dump



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-3788) [KVM] Weekly Snapshot got stuck in Allocated State


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-3788:
---

Priority: Major  (was: Critical)

 [KVM] Weekly Snapshot got stuck in Allocated State
 

 Key: CLOUDSTACK-3788
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3788
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Snapshot
Affects Versions: 4.2.0
Reporter: Chandan Purushothama
Assignee: Fang Wang
 Fix For: 4.2.1

 Attachments: management-server.log.2013-07-23.gz, 
 mysql_cloudstack_dump.zip


 Weekly Snapshot stuck in Allocated State:
 mysql select * from snapshots where name like 
 Atoms-VM-1_ROOT-6_20130723235146;
 ++++---+---+--+---+--+--+--+---+--++-+-++--++--+-+-+---+
 | id | data_center_id | account_id | domain_id | volume_id | disk_offering_id 
 | status| path | name | uuid  
| snapshot_type | type_description | size   | created  
| removed | backup_snap_id | swift_id | sechost_id | prev_snap_id | 
 hypervisor_type | version | s3_id |
 ++++---+---+--+---+--+--+--+---+--++-+-++--++--+-+-+---+
 | 24 |  1 |  3 | 1 | 6 |1 
 | Destroyed | NULL | Atoms-VM-1_ROOT-6_20130723235146 | 
 08a0d2aa-9635-41cd-ba54-5367303bceac | 3 | HOURLY   | 
 147456 | 2013-07-23 23:51:46 | NULL| NULL   | NULL |   
 NULL | NULL | KVM | 2.2 |  NULL |
 | 25 |  1 |  3 | 1 | 6 |1 
 | Allocated | NULL | Atoms-VM-1_ROOT-6_20130723235146 | 
 1e24a056-be38-4b55-845b-a5672b9fa93c | 5 | WEEKLY   | 
 147456 | 2013-07-23 23:51:46 | NULL| NULL   | NULL |   
 NULL | NULL | KVM | 2.2 |  NULL |
 ++++---+---+--+---+--+--+--+---+--++-+-++--++--+-+-+---+
 2 rows in set (0.04 sec)
 Attached Management Server logs and cloud database dump



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4740) Some vSphere VMs are shutdown when ACS is restarted


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4740:
---

Fix Version/s: (was: 4.2.1)
   4.3.0

 Some vSphere VMs are shutdown when ACS is restarted
 ---

 Key: CLOUDSTACK-4740
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4740
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.1.0, 4.1.1, 4.2.0, Future
 Environment: I'm running ACS 4.1.1 with vSphere 5.1
Reporter: ilya musayev
Priority: Critical
  Labels: management, poweroff
 Fix For: 4.3.0


 If management server is restarted, when management server starts - it checks 
 whether the agentState for vSphere VMs and if it does not get a proper 
 response, it marks them as stopped.
 As the result, some of my virtual instances would shutdown.
 Attempting to analyze this issue further, here are my findings and errors 
 seen in the log.
 2013-09-25 14:35:49,928 DEBUG [vmware.resource.VmwareResource] 
 (AgentTaskPool-1:null) Detecting a new state but couldn't find a old state so 
 adding it to the changes: i-2-262-acs-docs-fc17
 2013-09-25 14:35:51,213 DEBUG [agent.transport.Request] 
 (AgentTaskPool-1:null) Seq -1--1: Startup request from directly connected 
 host:  { Cmd , MgmtId: -1, via: -1, Ver: v1, Flags: 11, 
 [{cpus:16,speed:2199,memory:68683468800,dom0MinMemory:0,poolSync:false,vms:{i-8-270-CLOUD411:{state:Running},r-15-CLOUD41-OLD:{state:Stopped},v-260-CLOUD411:{state:Running},i-2-283-vmbld01l-ops-08:{state:Running},i-2-104-ACS41VM:{state:Running},--s-1-CLOUD41-OLD:{state:Running},i-27-280-CLOUD411:{state:Running},i-2-285-ossec01l-ops-08:{state:Running},i-2-262-acs-docs-fc17:{state:Stopped},i-24-265-test3:{state:Running},cloud01l-ops-08.portal.webmd.com:{state:Running},i-2-278-demo01t-ops-08:{state:Running},s-63-CLOUD411:{state:Running},r-66-CLOUD411:{state:Running},i-2-281-acs-appliance:{state:Running}},caps:hvm,hypervisorType:VMware,hostDetails:{com.cloud.network.Networks.RouterPrivateIpStrategy:DcGlobal,NativeHA:true},hypervisorVersion:5.0,type:Routing,dataCenter:2,pod:2,cluster:3,guid:HostSystem:host-19...@vc00q-ops-08.portal.webmd.com,name:vmha62d-ops-08.portal.webmd.com,version:4.1.1-SNAPSHOT,privateIpAddress:172.25.243.31,privateMacAddress:68:b5:99:73:0b:c2,privateNetmask:255.255.255.0,storageIpAddress:172.25.243.31,storageNetmask:255.255.255.0,storageMacAddress:68:b5:99:73:0b:c2,wait:0},{totalSize:0,poolInfo:{uuid:72c8aedb-58c4-4569-ac51-adc5af770bf6,host:vmha62d-ops-08.portal.webmd.com,localPath:,hostPath:datastore-19718,poolType:LVM,capacityBytes:141465485312,availableBytes:140383354880},resourceType:STORAGE_POOL,hostDetails:{},type:Storage,dataCenter:2,pod:2,cluster:3,guid:72c8aedb-58c4-4569-ac51-adc5af770bf6,name:72c8aedb-58c4-4569-ac51-adc5af770bf6,wait:0}]
  }
 2013-09-25 14:35:53,614 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (AgentTaskPool-1:null) VM i-2-262-acs-docs-fc17: cs state = Running and 
 realState = Stopped
 2013-09-25 14:35:53,614 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (AgentTaskPool-1:null) VM i-2-262-acs-docs-fc17: cs state = Running and 
 realState = Stopped
 2013-09-25 14:35:53,614 INFO  [cloud.ha.HighAvailabilityManagerImpl] 
 (AgentTaskPool-1:null) Skip HA for VMware VM i-2-262-acs-docs-fc17
 2013-09-25 14:35:53,694 DEBUG [agent.transport.Request] 
 (AgentTaskPool-1:null) Seq 11-1418264581: Sending  { Cmd , MgmtId: 
 345049078181, via: 11, Ver: v1, Flags: 100101, 
 [{StopCommand:{isProxy:false,vmName:i-2-262-acs-docs-fc17,wait:0}},{StopCommand:{isProxy:false,vmName:i-2-278-demo01t-ops-08,wait:0}},{StopCommand:{isProxy:false,vmName:i-2-281-acs-appliance,wait:0}},{StopCommand:{isProxy:false,vmName:i-2-283-vmbld01l-ops-08,wait:0}},{StopCommand:{isProxy:false,vmName:i-2-285-ossec01l-ops-08,wait:0}}]
  }
 2013-09-25 14:35:53,695 DEBUG [agent.transport.Request] 
 (AgentTaskPool-1:null) Seq 11-1418264581: Executing:  { Cmd , MgmtId: 
 345049078181, via: 11, Ver: v1, Flags: 100101, 
 [{StopCommand:{isProxy:false,vmName:i-2-262-acs-docs-fc17,wait:0}},{StopCommand:{isProxy:false,vmName:i-2-278-demo01t-ops-08,wait:0}},{StopCommand:{isProxy:false,vmName:i-2-281-acs-appliance,wait:0}},{StopCommand:{isProxy:false,vmName:i-2-283-vmbld01l-ops-08,wait:0}},{StopCommand:{isProxy:false,vmName:i-2-285-ossec01l-ops-08,wait:0}}]
  }
 2013-09-25 14:35:53,702 INFO  [vmware.resource.VmwareResource] 
 (DirectAgent-3:vmha62d-ops-08.portal.webmd.com) Executing resource 
 StopCommand: {isProxy:false,vmName:i-2-262-acs-docs-fc17,wait:0}
 2013-09-25 14:35:53,703 DEBUG [vmware.mo.HostMO] 
 (DirectAgent-3:vmha62d-ops-08.portal.webmd.com) find VM

[jira] [Commented] (CLOUDSTACK-4740) Some vSphere VMs are shutdown when ACS is restarted


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13790239#comment-13790239
 ] 

Abhinandan Prateek commented on CLOUDSTACK-4740:


Moving it to Future as there is limited time for 4.2.1.

 Some vSphere VMs are shutdown when ACS is restarted
 ---

 Key: CLOUDSTACK-4740
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4740
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.1.0, 4.1.1, 4.2.0, Future
 Environment: I'm running ACS 4.1.1 with vSphere 5.1
Reporter: ilya musayev
Priority: Critical
  Labels: management, poweroff
 Fix For: 4.3.0


 If management server is restarted, when management server starts - it checks 
 whether the agentState for vSphere VMs and if it does not get a proper 
 response, it marks them as stopped.
 As the result, some of my virtual instances would shutdown.
 Attempting to analyze this issue further, here are my findings and errors 
 seen in the log.
 2013-09-25 14:35:49,928 DEBUG [vmware.resource.VmwareResource] 
 (AgentTaskPool-1:null) Detecting a new state but couldn't find a old state so 
 adding it to the changes: i-2-262-acs-docs-fc17
 2013-09-25 14:35:51,213 DEBUG [agent.transport.Request] 
 (AgentTaskPool-1:null) Seq -1--1: Startup request from directly connected 
 host:  { Cmd , MgmtId: -1, via: -1, Ver: v1, Flags: 11, 
 [{cpus:16,speed:2199,memory:68683468800,dom0MinMemory:0,poolSync:false,vms:{i-8-270-CLOUD411:{state:Running},r-15-CLOUD41-OLD:{state:Stopped},v-260-CLOUD411:{state:Running},i-2-283-vmbld01l-ops-08:{state:Running},i-2-104-ACS41VM:{state:Running},--s-1-CLOUD41-OLD:{state:Running},i-27-280-CLOUD411:{state:Running},i-2-285-ossec01l-ops-08:{state:Running},i-2-262-acs-docs-fc17:{state:Stopped},i-24-265-test3:{state:Running},cloud01l-ops-08.portal.webmd.com:{state:Running},i-2-278-demo01t-ops-08:{state:Running},s-63-CLOUD411:{state:Running},r-66-CLOUD411:{state:Running},i-2-281-acs-appliance:{state:Running}},caps:hvm,hypervisorType:VMware,hostDetails:{com.cloud.network.Networks.RouterPrivateIpStrategy:DcGlobal,NativeHA:true},hypervisorVersion:5.0,type:Routing,dataCenter:2,pod:2,cluster:3,guid:HostSystem:host-19...@vc00q-ops-08.portal.webmd.com,name:vmha62d-ops-08.portal.webmd.com,version:4.1.1-SNAPSHOT,privateIpAddress:172.25.243.31,privateMacAddress:68:b5:99:73:0b:c2,privateNetmask:255.255.255.0,storageIpAddress:172.25.243.31,storageNetmask:255.255.255.0,storageMacAddress:68:b5:99:73:0b:c2,wait:0},{totalSize:0,poolInfo:{uuid:72c8aedb-58c4-4569-ac51-adc5af770bf6,host:vmha62d-ops-08.portal.webmd.com,localPath:,hostPath:datastore-19718,poolType:LVM,capacityBytes:141465485312,availableBytes:140383354880},resourceType:STORAGE_POOL,hostDetails:{},type:Storage,dataCenter:2,pod:2,cluster:3,guid:72c8aedb-58c4-4569-ac51-adc5af770bf6,name:72c8aedb-58c4-4569-ac51-adc5af770bf6,wait:0}]
  }
 2013-09-25 14:35:53,614 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (AgentTaskPool-1:null) VM i-2-262-acs-docs-fc17: cs state = Running and 
 realState = Stopped
 2013-09-25 14:35:53,614 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (AgentTaskPool-1:null) VM i-2-262-acs-docs-fc17: cs state = Running and 
 realState = Stopped
 2013-09-25 14:35:53,614 INFO  [cloud.ha.HighAvailabilityManagerImpl] 
 (AgentTaskPool-1:null) Skip HA for VMware VM i-2-262-acs-docs-fc17
 2013-09-25 14:35:53,694 DEBUG [agent.transport.Request] 
 (AgentTaskPool-1:null) Seq 11-1418264581: Sending  { Cmd , MgmtId: 
 345049078181, via: 11, Ver: v1, Flags: 100101, 
 [{StopCommand:{isProxy:false,vmName:i-2-262-acs-docs-fc17,wait:0}},{StopCommand:{isProxy:false,vmName:i-2-278-demo01t-ops-08,wait:0}},{StopCommand:{isProxy:false,vmName:i-2-281-acs-appliance,wait:0}},{StopCommand:{isProxy:false,vmName:i-2-283-vmbld01l-ops-08,wait:0}},{StopCommand:{isProxy:false,vmName:i-2-285-ossec01l-ops-08,wait:0}}]
  }
 2013-09-25 14:35:53,695 DEBUG [agent.transport.Request] 
 (AgentTaskPool-1:null) Seq 11-1418264581: Executing:  { Cmd , MgmtId: 
 345049078181, via: 11, Ver: v1, Flags: 100101, 
 [{StopCommand:{isProxy:false,vmName:i-2-262-acs-docs-fc17,wait:0}},{StopCommand:{isProxy:false,vmName:i-2-278-demo01t-ops-08,wait:0}},{StopCommand:{isProxy:false,vmName:i-2-281-acs-appliance,wait:0}},{StopCommand:{isProxy:false,vmName:i-2-283-vmbld01l-ops-08,wait:0}},{StopCommand:{isProxy:false,vmName:i-2-285-ossec01l-ops-08,wait:0}}]
  }
 2013-09-25 14:35:53,702 INFO  [vmware.resource.VmwareResource] 
 (DirectAgent-3:vmha62d-ops-08.portal.webmd.com) Executing resource 
 StopCommand: {isProxy:false,vmName:i-2-262-acs-docs-fc17,wait:0}
 2013-09-25 14:35:53,703 DEBUG [vmware.mo.HostMO]

[jira] [Updated] (CLOUDSTACK-3715) Live Migration of Virtual instances operation is getting timedout


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-3715:
---

Assignee: Sateesh Chodapuneedi

 Live Migration of Virtual instances operation is getting timedout 
 --

 Key: CLOUDSTACK-3715
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3715
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server, VMware
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Assignee: Sateesh Chodapuneedi
Priority: Critical
 Fix For: 4.2.1

 Attachments: 195113management-server.log.gz, 
 195117management-server.log.gz, apilog.log, cloud-backup.dmp.gz, 
 cloud-backup.sql.gz, management-server.log, migrationlogs.rar


 Setup: Multinode Management setup. 
 Steps:
 1. Configure Adv Zone with 2 VMWARE clusters each with one hosts with Zone 
 wide primary storage ( Standard vSwitch cluster) 
 2. Deploy VM using User account 
 3. Tried to Live migrate VM from cluster1 (host 1)  to  Cluster 2 (host2 ) 
 Observation:
 1. Migration took very log time and finally failed saying operation timed out 
 :
 2013-07-22 17:46:06,288 DEBUG [cloud.capacity.CapacityManagerImpl] 
 (Job-Executor-40:job-133 = [ 4a2f6d84-236d-4bdd-a2e5-72fa336e0274 ]) VM state 
 transitted from :Migrating to Running with event: OperationFailedvm's 
 original host id: 4 new host id: 4 host id before state transition: 1
 2013-07-22 17:46:06,292 INFO  [vmware.resource.VmwareResource] 
 (DirectAgent-421:10.102.192.18) VM i-4-9-VM is no longer in vSphere
 2013-07-22 17:46:06,293 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-421:null) Seq 1-1311245319: Response Received:
 2013-07-22 17:46:06,294 DEBUG [agent.transport.Request] 
 (DirectAgent-421:null) Seq 1-1311245319: Processing:  { Ans: , MgmtId: 
 94838926819810, via: 1, Ver: v1, Flags: 10, 
 [{com.cloud.agent.api.StopAnswer:{vncPort:0,result:true,details:VM 
 i-4-9-VM is no longer in vSphere,wait:0}}] }
 2013-07-22 17:46:06,294 DEBUG [agent.manager.AgentAttache] 
 (DirectAgent-421:null) Seq 1-1311245319: Unable to find listener.
 2013-07-22 17:46:06,307 DEBUG [cloud.capacity.CapacityManagerImpl] 
 (Job-Executor-40:job-133 = [ 4a2f6d84-236d-4bdd-a2e5-72fa336e0274 ]) Hosts's 
 actual total CPU: 9572 and CPU after applying overprovisioning: 9572
 2013-07-22 17:46:06,307 DEBUG [cloud.capacity.CapacityManagerImpl] 
 (Job-Executor-40:job-133 = [ 4a2f6d84-236d-4bdd-a2e5-72fa336e0274 ]) Hosts's 
 actual total RAM: 17166258176 and RAM after applying overprovisioning: 
 17166258176
 2013-07-22 17:46:06,307 DEBUG [cloud.capacity.CapacityManagerImpl] 
 (Job-Executor-40:job-133 = [ 4a2f6d84-236d-4bdd-a2e5-72fa336e0274 ]) release 
 cpu from host: 1, old used: 2000,reserved: 0, actual total: 9572, total with 
 overprovisioning: 9572; new used: 200,reserved:0; movedfromreserved: 
 false,moveToReserveredfalse
 2013-07-22 17:46:06,307 DEBUG [cloud.capacity.CapacityManagerImpl] 
 (Job-Executor-40:job-133 = [ 4a2f6d84-236d-4bdd-a2e5-72fa336e0274 ]) release 
 mem from host: 1, old used: 2013265920,reserved: 0, total: 17166258176; new 
 used: 2013265920,reserved:0; movedfromreserved: false,moveToReserveredfalse
 2013-07-22 17:46:06,345 ERROR [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-40:job-133 = [ 4a2f6d84-236d-4bdd-a2e5-72fa336e0274 ]) 
 Unexpected exception while executing 
 org.apache.cloudstack.api.command.admin.vm.MigrateVirtualMachineWithVolumeCmd
 com.cloud.utils.exception.CloudRuntimeException: Failed to migrated vm 
 VM[User|newuser1i1] along with its volumes. 
 com.cloud.exception.AgentUnavailableException: Resource [Host:1] is 
 unreachable: Host 1: Operation timed out on storage motion for 
 VM[User|newuser1i1]
 at 
 com.cloud.storage.VolumeManagerImpl.migrateVolumes(VolumeManagerImpl.java:2263)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.migrateWithStorage(VirtualMachineManagerImpl.java:1780)
 at 
 com.cloud.vm.UserVmManagerImpl.migrateVirtualMachineWithVolume(UserVmManagerImpl.java:4046)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.api.command.admin.vm.MigrateVirtualMachineWithVolumeCmd.execute(MigrateVirtualMachineWithVolumeCmd.java:137)
 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

[jira] [Updated] (CLOUDSTACK-4148) usage:usage stats are not triggered for shared network


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4148:
---

Priority: Major  (was: Critical)

 usage:usage stats are not triggered for shared network
 --

 Key: CLOUDSTACK-4148
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4148
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Usage
Affects Versions: 4.2.0
Reporter: sadhu suresh
Assignee: Kishan Kavala
 Fix For: Future

 Attachments: management-server.rar


 steps:
 1.create network offering with SRX and F5 
 2.create a shared guestnetwork using above NO
 3.deploy a VM using abobve network
 4.generate the traffic and check the usage stats after 10 min
 actual:
 NetworkUsageCommand: is running only for isolated network and its not issuing 
 for  for sharednetwok.
 router-12 isbelongs to sharednetwork.
 r-4-0vm belongs to isloated network
 No query specified
 mysql select * from user_statistics;
 ++++---+---+--++++++++
 | id | data_center_id | account_id | public_ip_address | device_id | 
 device_type  | network_id | net_bytes_received | net_bytes_sent | 
 current_bytes_received | current_bytes_sent | agg_bytes_received | 
 agg_bytes_sent |
 ++++---+---+--++++++++
 |  1 |  1 |  2 | NULL  | 4 | 
 DomainRouter |204 |  0 |  0 | 
  0 | 401016 |  0 | 401016 |
 |  2 |  1 |  1 | NULL  |12 | 
 DomainRouter |206 |  0 |  0 | 
  0 |  0 |  0 |  0 |
 |  3 |  1 |  1 | NULL  |18 | 
 DomainRouter |209 |  0 |  0 | 
  0 |  0 |  0 |  0 |
 |  4 |  1 |  2 | 10.147.49.106 |21 | 
 DomainRouter |200 |  0 |  0 | 
4195797 | 148136 |4195797 | 148136 |
 |  5 |  1 |  2 | NULL  |21 | 
 DomainRouter |210 |  0 |  0 | 
  0 |  0 |  0 |  0 |
 ++++---+---+--++++++++
 5 rows in set (0.00 sec)



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4148) usage:usage stats are not triggered for shared network


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4148:
---

Fix Version/s: (was: 4.2.1)
   Future

 usage:usage stats are not triggered for shared network
 --

 Key: CLOUDSTACK-4148
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4148
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Usage
Affects Versions: 4.2.0
Reporter: sadhu suresh
Assignee: Kishan Kavala
 Fix For: Future

 Attachments: management-server.rar


 steps:
 1.create network offering with SRX and F5 
 2.create a shared guestnetwork using above NO
 3.deploy a VM using abobve network
 4.generate the traffic and check the usage stats after 10 min
 actual:
 NetworkUsageCommand: is running only for isolated network and its not issuing 
 for  for sharednetwok.
 router-12 isbelongs to sharednetwork.
 r-4-0vm belongs to isloated network
 No query specified
 mysql select * from user_statistics;
 ++++---+---+--++++++++
 | id | data_center_id | account_id | public_ip_address | device_id | 
 device_type  | network_id | net_bytes_received | net_bytes_sent | 
 current_bytes_received | current_bytes_sent | agg_bytes_received | 
 agg_bytes_sent |
 ++++---+---+--++++++++
 |  1 |  1 |  2 | NULL  | 4 | 
 DomainRouter |204 |  0 |  0 | 
  0 | 401016 |  0 | 401016 |
 |  2 |  1 |  1 | NULL  |12 | 
 DomainRouter |206 |  0 |  0 | 
  0 |  0 |  0 |  0 |
 |  3 |  1 |  1 | NULL  |18 | 
 DomainRouter |209 |  0 |  0 | 
  0 |  0 |  0 |  0 |
 |  4 |  1 |  2 | 10.147.49.106 |21 | 
 DomainRouter |200 |  0 |  0 | 
4195797 | 148136 |4195797 | 148136 |
 |  5 |  1 |  2 | NULL  |21 | 
 DomainRouter |210 |  0 |  0 | 
  0 |  0 |  0 |  0 |
 ++++---+---+--++++++++
 5 rows in set (0.00 sec)



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4351) 4.3.2. Host/Hypervisor System Requirements has misleading or premature note


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4351:
---

Priority: Major  (was: Critical)

 4.3.2. Host/Hypervisor System Requirements has misleading  or premature note
 

 Key: CLOUDSTACK-4351
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4351
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Doc
Affects Versions: 4.2.0
 Environment: All
Reporter: Ron Wheeler
 Fix For: 4.2.1


 Note
 If DHCP is used for hosts, ensure that no conflict occurs between DHCP server
 used for these hosts and the DHCP router created by CloudStack.
 How can you do this at this point?
 Cloudstack does not have a DHCP server at this point.
 There is nothing for the user to do at this point.
 It should be moved to closer to the point where the DHCP server addresses are 
 specified.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4351) [DOC] 4.3.2. Host/Hypervisor System Requirements has misleading or premature note


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4351:
---

Summary: [DOC] 4.3.2. Host/Hypervisor System Requirements has misleading  
or premature note  (was: 4.3.2. Host/Hypervisor System Requirements has 
misleading  or premature note)

 [DOC] 4.3.2. Host/Hypervisor System Requirements has misleading  or premature 
 note
 --

 Key: CLOUDSTACK-4351
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4351
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Doc
Affects Versions: 4.2.0
 Environment: All
Reporter: Ron Wheeler
 Fix For: 4.2.1


 Note
 If DHCP is used for hosts, ensure that no conflict occurs between DHCP server
 used for these hosts and the DHCP router created by CloudStack.
 How can you do this at this point?
 Cloudstack does not have a DHCP server at this point.
 There is nothing for the user to do at this point.
 It should be moved to closer to the point where the DHCP server addresses are 
 specified.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-732) Add back KVM snapshot support


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-732:
--

Assignee: (was: Fang Wang)

 Add back KVM snapshot support
 -

 Key: CLOUDSTACK-732
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-732
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM
Affects Versions: 4.0.0
 Environment: RHEL 6.3
Reporter: edison su
Priority: Critical
 Fix For: 4.2.1


 In the latest KVM(on both RHEL 6.3 and Ubuntu 12.04), it supports external 
 snapshot. We need to investigate the status of external snapshot, as far as I 
 know, it still doesn't support disk-only snapshot(taking snapshot will pause 
 VM for a long time, e.g. few minutes). 
 1. testing external snapshot: take an external snapshot instead of default 
 qcow2 internal snapshot, then back it up into backup storage. Only need to 
 test with libvirt snapshot API, if it works, then works, no need to hack on 
 the qemu-kvm.
 2. test how long it will pause a VM during taking snapshot. from link [2] and 
 [3], only qemu-kvm-rhev supports disk-only snapshot, not sure ubuntu 12.04 
 supports it or not. We need to investigate on the issue.
 If item 1 and item 2(disk-only snapshot) works, then we can support default 
 kvm qcow2 snapshot again.
 The link: 
 [1] 
 http://kashyapc.wordpress.com/2011/10/04/snapshotting-with-libvirt-for-qcow2-images/
 [2] 
 http://www.linux-kvm.com/content/first-look-virtual-machine-online-disk-snapshots-coming-fedora-18
 [3] http://www.redhat.com/archives/libvir-list/2012-July/msg00782.html



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4348) [UI] EN: Regression Truncation issues occurred when moving the cursor to the plus buttons.

[
https://issues.apache.org/jira/browse/CLOUDSTACK-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Abhinandan Prateek updated CLOUDSTACK-4348:
---

Summary: [UI] EN: Regression Truncation issues occurred when moving the
cursor to the plus buttons. (was: EN: Regression Truncation issues occurred
when moving the cursor to the plus buttons.)

[UI] EN: Regression Truncation issues occurred when moving the cursor to the
plus buttons.

Key: CLOUDSTACK-4348
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4348
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server, UI
Affects Versions: 4.2.0
Environment: Environment
Build#CloudPlatform-4.2-426(CloudPlatform-4.2-426-rhel6.3.tar.gz)
XenServer6.1 for Host Server
CentOS6.3 for NFS, CS-Mgr Servers.
Client Browser: Win7-Chrome, Win7-Firefox22.0, Mac-Safari, Win7-IE10
Reporter: Minying Bao
Assignee: Brian Federle
Priority: Critical
Fix For: 4.2.1

Attachments: 1.Instance_Truncation.jpg, Truncation Issues.zip

Prerequisite
Upload a Template/ISO. then created vm in instances tab.
Repro Steps
1. Open the browser and login to Web Portal.
2. Navigate the “instances” tab.
3. Click to the newly created vm.
4. Move the mouse cursor to “plus” button.
5. Observe the UI.
Expected Result
It should display as normal.
Actual Result
Truncation issue occurred.
Some other 'plus' buttons are all repro the truncations. Please refer to
attached screenshots for details.
Brower Info.
Mac-Safari - Fail
Win7-Firefox22.0 - Fail
Win7-Chrome - Fail
Win7-IE10 - Fail
Regression Info.
Build#CloudPlatform-4.2-373-Pass
Build#CloudPlatform-4.2-389-Fail
Build#CloudPlatform-4.2-426-Fail

--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4711) UCS:API: Premature API response prevent CS from syncing association status


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4711:
---

Assignee: frank zhang

 UCS:API: Premature API response prevent CS from syncing association status
 --

 Key: CLOUDSTACK-4711
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4711
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API, UCS
Affects Versions: 4.2.0
 Environment: UCS
Reporter: Parth Jagirdar
Assignee: frank zhang
Priority: Critical
 Fix For: 4.2.1


 We rely on association tag from UCS manager to determine the association 
 success.
 association=none 
 However UCS sometimes send this response prematurely in which case CS fails 
 the API and association is unsuccessful.
 Eventually UCS finishes association and CS and UCS are now out of sync.
 Now if admin attempts to re-associate this blade then it will error out 
 saying the Object already exists 
 We need to device another strategy for this to work flawlessly.
 2013-09-19 14:35:08,554 WARN  
 [commons.httpclient.SimpleHttpConnectionManager] (Job-Executor-19:job-19 = [ 
 561e963d-be42-418b-be73-dcb7abf98e08 ]) SimpleHttpConnectionManager being 
 used incorrectly.  Be sure that HttpMethod.releaseConnection() is always 
 called and that only one thread and/or method is using this connection 
 manager at a time.
 2013-09-19 14:35:08,563 DEBUG [ucs.manager.UcsManagerImpl] 
 (Job-Executor-19:job-19 = [ 561e963d-be42-418b-be73-dcb7abf98e08 ]) 
 association response is  configResolveDn dn=sys/chassis-1/blade-1 
 cookie=1379626356/ce72a30f-c52f-4772-a546-b2620243 response=yes 
 outConfig computeBlade adminPower=policy adminState=in-service 
 assignedToDn= association=none availability=available 
 availableMemory=65536 chassisId=1 checkPoint=discovered  connPath=A 
 connStatus=A descr= discovery=complete dn=sys/chassis-1/blade-1 
 fltAggr=0 fsmDescr= fsmFlags= fsmPrev=DisassociateSuccess 
 fsmProgr=100 fsmRmtInvErrCode=none fsmRmtInvErrDescr= fsmRmtInvRslt= 
 fsmStageDescr= fsmStamp=2013-09-19T14:35:06.906 fsmStatus=nop 
 fsmTry=0 intId=36071 lc=discovered lcTs=1969-12-31T16:00:00.000 
 lowVoltageMemory=low-voltage managingInst=A memorySpeed=1333 
 mfgTime=2012-10-14T01:00:00.000 model=UCSB-B200-M3 name= 
 numOfAdaptors=1 numOfCores=12 numOfCoresEnabled=12 numOfCpus=2 
 numOfEthHostIfs=0 numOfFcHostIfs=0 numOfThreads=24 operPower=off 
 operQualifier= operState=unassociated operability=operable 
 originalUuid=78eb1a7d-7665-4cdb-a995-e4953a63d1d7 partNumber=73-13217-08 
 presence=equipped revision=0  serial=FCH16407N8A serverId=1/1 
 slotId=1  totalMemory=65536 usrLbl= 
 uuid=78eb1a7d-7665-4cdb-a995-e4953a63d1d7 vendor=Cisco Systems Inc 
 vid=V03/ /outConfig /configResolveDn
 2013-09-19 14:35:08,563 WARN  [cloudstack.api.AssociateUcsProfileToBladeCmd] 
 (Job-Executor-19:job-19 = [ 561e963d-be42-418b-be73-dcb7abf98e08 ]) Exception:
 com.cloud.utils.exception.CloudRuntimeException: cannot associated a profile 
 to blade[dn:sys/chassis-1/blade-1]. please check your UCS manasger for 
 detailed error information
 at 
 com.cloud.ucs.manager.UcsManagerImpl.isBladeAssociated(UcsManagerImpl.java:351)
 at 
 com.cloud.ucs.manager.UcsManagerImpl.associateProfileToBlade(UcsManagerImpl.java:380)
 at 
 org.apache.cloudstack.api.AssociateUcsProfileToBladeCmd.execute(AssociateUcsProfileToBladeCmd.java:58)
 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-09-19 14:35:08,565 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-19:job-19 = [ 561e963d-be42-418b-be73-dcb7abf98e08 ]) Complete 
 async job-19 = [ 561e963d-be42-418b-be73-dcb7abf98e08 ], jobStatus: 2, 
 resultCode: 530, result: Error Code: 530 Error text: cannot associated a 
 profile to blade[dn:sys/chassis-1/blade-1]. please check your UCS manasger 
 for detailed error information
 2013-09-19 14:35:09,006 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null) 
 ===START===  10.252.113.141 -- GET

[jira] [Closed] (CLOUDSTACK-4672) [UI] Network detail list doesn't show PVLAN related items


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

shweta agarwal closed CLOUDSTACK-4672.
--


Verified . Passed


 [UI] Network detail list doesn't show PVLAN related items
 -

 Key: CLOUDSTACK-4672
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4672
 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: Sheng Yang
Assignee: Jessica Wang
 Fix For: 4.2.1

 Attachments: after_fix.jpg


 Primary VLAN ID and secondary VLAN ID is not shown in the network detail list.
 They're in the API:
 { listnetworksresponse : { count:1 ,network : [  
 {id:c6b9563d-8a8a-467b-bb5f-a97cf3128e7b,name:pvlan1610,displaytext:pvlan,broadcastdomaintype:Pvlan,traffictype:Guest,gateway:10.223.161.1,netmask:255.255.255.192,cidr:10.223.161.0/26,zoneid:ac87f0b9-84cf-4b48-9394-f966f0158926,zonename:zone-81,networkofferingid:e243e9f3-52cc-415f-a4c4-064cd3aa6555,networkofferingname:DefaultSharedNetworkOffering,networkofferingdisplaytext:Offering
  for Shared 
 networks,networkofferingconservemode:true,networkofferingavailability:Optional,issystem:false,state:Setup,related:c6b9563d-8a8a-467b-bb5f-a97cf3128e7b,broadcasturi:pvlan://1610-i999,dns1:8.8.8.8,type:Shared,vlan:N/A,acltype:Domain,subdomainaccess:true,domainid:b3e5278a-1c04-11e3-84fc-002219d77204,domain:ROOT,service:[{name:UserData},{name:Dns,capability:[{name:AllowDnsSuffixModification,value:true,canchooseservicecapability:false}]},{name:Dhcp,capability:[{name:DhcpAccrossMultipleSubnets,value:true,canchooseservicecapability:false}]}],networkdomain:cs1cloud.internal,physicalnetworkid:5de65b22-fa25-4f61-b09a-82934f0e9e04,restartrequired:false,specifyipranges:true,canusefordeploy:true,ispersistent:false,tags:[],displaynetwork:true}
  ] } }
 See the broadcasturi: pvlan://1610-i999.
 Primary VLAN is 1610, Secondary Isolated VLAN is 999. Formation is 
 pvlan://[primary]-i[secondary_isolated]



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Closed] (CLOUDSTACK-4700) UI Instances Reset VM action if the template from which vm is created is password-enabled, pop up Password has been reset to xxxxxxx dialog


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

shweta agarwal closed CLOUDSTACK-4700.
--


verified in 4.2.1.passed

 UI  Instances  Reset VM action  if the template from which vm is created 
 is password-enabled, pop up Password has been reset to xxx dialog
 ---

 Key: CLOUDSTACK-4700
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4700
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Jessica Wang

 This issue is a clone of http://bugs-ccp.citrix.com/browse/CS-18255



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Closed] (CLOUDSTACK-265) Optional Public IP assignment for EIP with Basic Zone


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sudha Ponnaganti closed CLOUDSTACK-265.
---


 Optional Public IP assignment for EIP with Basic Zone
 -

 Key: CLOUDSTACK-265
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-265
 Project: CloudStack
  Issue Type: New Feature
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Network Controller
Affects Versions: 4.0.0, 4.1.0
Reporter: Murali Reddy
Assignee: Murali Reddy
 Fix For: 4.2.0

 Attachments: management-server.log.gz, management-server.log.gz, 
 management-server.log.gz, Screenshot-CloudPlatform™ - Mozilla Firefox-1.png, 
 Screenshot-CloudPlatform™ - Mozilla Firefox-2.png, Screenshot-CloudPlatform™ 
 - Mozilla Firefox.png


 Current EIP in CloudStack has below semantics.
- When a user VM is deployed, a public ip is automatically acquired. This 
 IP is owned by the vm'saccount and is marked as 'system' in the db.
- When the user VM starts, static NAT is provisioned on the static NAT 
 provider between the public ip and the guest ip of the vm.
 Since public IP's can be scarce resource is some deployments, its not 
 desirable to allocate a public IP by default. This bug is to provide the 
 flexibility for cloud providers to enable/disable the ability to 
 automatically allocate public IP. 
 Release Planning:
 Dev List Discussion: http://markmail.org/message/b2h2cw62qnryk4qh
 Functional Spec: 
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/Optional+Public+IP+assignment+for+EIP+with+Basic+Zone?moved=true
 Feature Branch: master



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Closed] (CLOUDSTACK-312) enable L4-L7 network services in the shared network in the advanced zone


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sudha Ponnaganti closed CLOUDSTACK-312.
---


 enable L4-L7 network services in the shared network in the advanced zone
 

 Key: CLOUDSTACK-312
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-312
 Project: CloudStack
  Issue Type: New Feature
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Murali Reddy
Assignee: Murali Reddy
 Fix For: 4.2.0


 CloudStack today does not provide network services like firewall, load 
 balancing, NAT in the shared networks created in the advanced zone. This 
 feature will enable network services to be available in the shared network as 
 well.
 Release Planning:
 Dev List Discussion: http://markmail.org/message/m522lj7ud7heanlb
 Functional Spec: 
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/L4-L7+network+services+in+shared+network
 Feature Branch: master



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Closed] (CLOUDSTACK-509) S3-backed Secondary Storage


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sudha Ponnaganti closed CLOUDSTACK-509.
---


 S3-backed Secondary Storage
 ---

 Key: CLOUDSTACK-509
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-509
 Project: CloudStack
  Issue Type: New Feature
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: ISO, Management Server, Snapshot, Storage Controller, 
 Template, Xen, XenServer
Affects Versions: 4.1.0
Reporter: John Burwell
Assignee: John Burwell
  Labels: features, newbie, patch
 Fix For: 4.2.0


 Backs NFS-based secondary storage with an S3-compatible object store.  
 Periodically, a reaper thread synchronizes templates and ISOs stored on a NFS 
 secondary storage mount with a configured S3 object store.  It also pushes 
 snapshots to the object store when they are created and downloads them in 
 other zones on-demand. In addition to permitting the use of commodity or IaaS 
 storage solutions for static assets, it provides a means of automatically 
 synchronizing template and ISO assets across multiple zones.
 Release Planning:
 Dev list discussion: http://markmail.org/message/vrq4t3f2mdmyatef
 Functional Spec: 
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/S3-backed+Secondary+Storage
 Feature Branch: review board https://reviews.apache.org/r/8123/



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Closed] (CLOUDSTACK-2202) UI: password pop up required when restore vm API and reboot vm(volatile) API are called


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

shweta agarwal closed CLOUDSTACK-2202.
--


Verified on 4.2.1 .Passed

 UI: password pop up required when restore vm API and reboot vm(volatile) API 
 are called
 ---

 Key: CLOUDSTACK-2202
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2202
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.2.0
Reporter: Harikrishna Patnala
Assignee: Jessica Wang
 Fix For: 4.2.1






--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Closed] (CLOUDSTACK-24) Multiples IP's on Private LAN with Nat 1:1


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sudha Ponnaganti closed CLOUDSTACK-24.
--


 Multiples IP's on Private LAN with Nat 1:1
 --

 Key: CLOUDSTACK-24
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-24
 Project: CloudStack
  Issue Type: New Feature
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Network Controller
Reporter: Facundo Guerrero
Assignee: Jayapal Reddy
  Labels: features
 Fix For: 4.2.0


 I would be a great feature to have the possibility to add floating Ip's in 
 the private network and nat 1:1 to a public IP.
 It's not necessary to add a secondary network interface on the VM, in the OS 
 we add a virtual interface and assign the Private IP and NAT 1:1 with a 
 public IP.
 With this we can use the webserver's, postfix, and other software with 
 different public ip's
 Release Planning:
 Dev list Discussion: http://markmail.org/message/gyvoxr6ai2ozqe6k
 Functional Specification:  
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/Multiple+IP+address+per+NIC
 Feature Branch: Unknown



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Closed] (CLOUDSTACK-478) Clarify how to create a shared network


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sudha Ponnaganti closed CLOUDSTACK-478.
---


 Clarify how to create a shared network
 --

 Key: CLOUDSTACK-478
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-478
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Doc
Affects Versions: 4.0.0
Reporter: Jessica Tomechak
Assignee: Radhika Nair
 Fix For: 4.2.0

 Attachments: Apache_CloudStack-4.2.0-Admin_Guide-en-US.pdf


 Can we add content in our admin guide to tell the user where they need to go 
 to create a shared network and explain them that the Shared Network can be 
 created at different levels (ALL, Domain, Account, Project). 
 (Requested by Manan Shah)



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Created] (CLOUDSTACK-4840) Automation: multiple IPs on Private

Sudha Ponnaganti created CLOUDSTACK-4840:


 Summary: Automation: multiple IPs on Private 
 Key: CLOUDSTACK-4840
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4840
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.2.0
Reporter: Sudha Ponnaganti
 Fix For: 4.2.0






--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Closed] (CLOUDSTACK-4837) Unable to Login into UI

2013-10-09 Thread karthikeyan (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

karthikeyan closed CLOUDSTACK-4837.
---


 Unable to Login into UI
 ---

 Key: CLOUDSTACK-4837
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4837
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: karthikeyan
Priority: Blocker

 Hi,
 I have installed Cloudstack-4.2 in centOS-6.3. The installation went 
 successful. But after that i cannot able to LOGIN in UI.
 Username: admin
 Password: password
 When i click login button it throws this error,
 Invalid username or password
 If i click the Login button again, then it throws this error,
 Unable to reach management server
 The cloudstack-management service is getting stopped, whenever i try to login 
 into UI
 Log Entries:
 $ tail -f /var/log/cloudstack/management/management-server.log
 2013-10-09 02:22:40,672 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null) 
 ===START===  10.14.114.205 -- POST  
 2013-10-09 02:22:42,832 DEBUG [cloud.user.AccountManagerImpl] 
 (catalina-exec-2:null) Attempting to log in user: admin in domain 1
 2013-10-09 02:22:42,836 DEBUG [server.auth.SHA256SaltedUserAuthenticator] 
 (catalina-exec-2:null) Retrieving user: admin
 2013-10-09 02:22:44,011 WARN  [server.auth.SHA256SaltedUserAuthenticator] 
 (catalina-exec-2:null) The stored password for admin isn't in the right 
 format for this authenticator
 2013-10-09 02:22:49,397 DEBUG [server.auth.MD5UserAuthenticator] 
 (catalina-exec-2:null) Retrieving user: admin
 2013-10-09 02:22:51,501 DEBUG [server.auth.MD5UserAuthenticator] 
 (catalina-exec-2:null) Password does not match
 2013-10-09 02:22:51,612 DEBUG [server.auth.LDAPUserAuthenticator] 
 (catalina-exec-2:null) Retrieving user: admin
 2013-10-09 02:22:54,590 DEBUG [server.auth.LDAPUserAuthenticator] 
 (catalina-exec-2:null) LDAP authenticator is not configured.
 2013-10-09 02:22:54,632 DEBUG [server.auth.PlainTextUserAuthenticator] 
 (catalina-exec-2:null) Retrieving user: admin
 2013-10-09 02:22:55,698 DEBUG [server.auth.PlainTextUserAuthenticator] 
 (catalina-exec-2:null) Password does not match
 2013-10-09 02:22:55,717 DEBUG [cloud.user.AccountManagerImpl] 
 (catalina-exec-2:null) Unable to authenticate user with username admin in 
 domain 1
 2013-10-09 02:22:56,736 INFO  [cloud.user.AccountManagerImpl] 
 (catalina-exec-2:null) User admin is disabled/locked
 2013-10-09 02:22:56,741 DEBUG [cloud.user.AccountManagerImpl] 
 (catalina-exec-2:null) User: admin in domain 1 has failed to log in
 2013-10-09 02:22:57,036 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null) 
 ===END===  10.14.114.205 -- POST  
 In management database i found this info,
 mysql use cloud
 mysql select * from user;
 ++--+--+---++---+--+---+--+-++-+-+--++---+--+
 | id | uuid | username | password  | 
 account_id | firstname | lastname | email | state| api_key | secret_key | 
 created | removed | timezone | registration_token | is_registered 
 | incorrect_login_attempts |
 ++--+--+---++---+--+---+--+-++-+-+--++---+--+
 |  1 | aa8bcc98-3068-11e3-8747-000c2957f30f | system   | 0.910423140889428 |  
 1 | system| cloud| NULL  | enabled  | NULL| NULL   | 
 2013-10-09 03:56:24 | NULL| NULL | NULL   | 0 
 |0 |
 |  2 | aa8daff4-3068-11e3-8747-000c2957f30f | admin| 0.811178035858253 |  
 2 | admin | cloud| NULL  | disabled | NULL| NULL   | 
 2013-10-09 03:56:24 | NULL| NULL | NULL   | 0 
 |0 |
 ++--+--+---++---+--+---+--+-++-+-+--++---+--+
 For admin user, it is showing disabled state.
 -Karthikeyan



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (CLOUDSTACK-3364) [UI] normal users are not allowed to edit their own iso


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13790665#comment-13790665
 ] 

Jessica Wang commented on CLOUDSTACK-3364:
--

Nitin,

  At the moment, I think that for Isos we should allow to edit it so would 
 call it an API bug.
Thanks.

 Register Iso does provide an option to mark an ISO featured. I see that in 
 the latest master.
That only works for admin, but NOT normal user.

If you log in as a normal user, then pass “isfeatured=true” to registerIso API, 
API will ignore it. 
The newly registered template will have “isfeatured: false”. 

e.g. 
http://10.215.3.26:8080/client/api?command=registerIsoresponse=jsonsessionkey=u%2FVIHPJuPohidGKFd0lh6csG%2BfM%3Dname=normalUserIso1displayText=normalUserIso1url=http%3A%2F%2F10.223.110.231%2Fisos_64bit%2Fdummy.isozoneid=6bcd3bd9-591c-4d99-a164-d05b87df1b04isfeatured=trueisextractable=falsebootable=trueosTypeId=b8cbfd6c-2d40-11e3-86aa-3c970e739c3eispublic=false_=1381340961641
{
registerisoresponse: {
count: 1,
iso: [
{
id: 9b903876-f17c-4634-8463-8e3025259956,
name: normalUserIso1,
displaytext: normalUserIso1,
ispublic: false,
created: 2013-10-09T10:52:38-0700,
isready: false,
bootable: true,
isfeatured: false,
crossZones: false,
ostypeid: b8cbfd6c-2d40-11e3-86aa-3c970e739c3e,
ostypename: Apple Mac OS X 10.6 (32-bit),
account: aaa_user,
zoneid: 6bcd3bd9-591c-4d99-a164-d05b87df1b04,
zonename: jw-adv,
status: ,
domain: aaa,
domainid: 47b09d73-84ef-48dc-9b73-1720bad600cb,
isextractable: false,
tags: []
}
]
}
}

Jessica


 [UI] normal users are not allowed to edit their own iso
 ---

 Key: CLOUDSTACK-3364
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3364
 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: shweta agarwal
Assignee: Jessica Wang
 Fix For: 4.2.1


 Repro steps:
 1.Create a domain
 2.create a account under that domain
 3.create a ISO as a account under the non root domain
 4.Edit the ISO
 BUg :
 gets message: 
 Only ROOT admins are allowed to modify this attribute.
 API:
 http://10.147.38.141:8080/client/api?command=updateIsoPermissionsresponse=jsonsessionkey=8rczMjm4sfljFOEi6dL2xT631sc%3Did=2b8c87a0-4325-418d-80af-ce6f691edcd7zoneid=bfdf7ac5-16c3-491e-aabd-f7ad696612b8ispublic=falseisfeatured=falseisextractable=false_=1372941865923
 response:
 { updateisopermissionsresponse : 
 {uuidList:[],errorcode:431,cserrorcode:4350,errortext:Only ROOT 
 admins are allowed to modify this attribute.} }
 This may be because in case of edit ISO we show  extractable and featured 
 field as editable to normal user , which normal user is not allowed to do  
 and api passes these as parameters
 In case of template these fields are shown as non editable hence API passed 
 does not contain isfeatured and isextractable fields



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Resolved] (CLOUDSTACK-4703) [UI] listHypervisors returns empty hypervisors when zoneId = -1 on a multi-zone setup with different hypervisors on each zone.


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Wang resolved CLOUDSTACK-4703.
--

Resolution: Fixed

 [UI]  listHypervisors returns empty hypervisors when zoneId = -1 on a 
 multi-zone setup with different hypervisors on each zone.
 ---

 Key: CLOUDSTACK-4703
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4703
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
Reporter: Min Chen
Priority: Critical
 Fix For: 4.2.1


 1. Setup two zones, one is XenServer, the other is Vmware. Both uses S3 as 
 secondary storage.
 2. Now register a template on zone 1.
 3. In the register template dialog, hypervisor dropdown shows empty list. The 
 API invoked from UI is listHypervisor with zoneId = -1.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Closed] (CLOUDSTACK-4703) [UI] listHypervisors returns empty hypervisors when zoneId = -1 on a multi-zone setup with different hypervisors on each zone.


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Wang closed CLOUDSTACK-4703.



 [UI]  listHypervisors returns empty hypervisors when zoneId = -1 on a 
 multi-zone setup with different hypervisors on each zone.
 ---

 Key: CLOUDSTACK-4703
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4703
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
Reporter: Min Chen
Priority: Critical
 Fix For: 4.2.1


 1. Setup two zones, one is XenServer, the other is Vmware. Both uses S3 as 
 secondary storage.
 2. Now register a template on zone 1.
 3. In the register template dialog, hypervisor dropdown shows empty list. The 
 API invoked from UI is listHypervisor with zoneId = -1.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Created] (CLOUDSTACK-4842) Can't create a VM based on an ISO

2013-10-09 Thread Mike Tutkowski (JIRA)

Mike Tutkowski created CLOUDSTACK-4842:
--

 Summary: Can't create a VM based on an ISO
 Key: CLOUDSTACK-4842
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4842
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server
Affects Versions: Future
 Environment: Mac OS X 10.8.3
Reporter: Mike Tutkowski
 Fix For: Future


I am unable to create a VM instance based on an ISO due to the following error:

INFO  [c.c.a.ApiServer] (804219803@qtp-426122736-3:ctx-1b07f7ab ctx-8d5a64da) 
Unable to execute API command deployvirtualmachine due to invalid value. 
Invalid parameter diskofferingid value=ff31ad62-309a-11e3-b2be-01818516e022 due 
to incorrect long value format, or entity does not exist or due to incorrect 
parameter annotation for the field in api cmd class.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Resolved] (CLOUDSTACK-3016) remove zonetype parameter from list API commands


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Wang resolved CLOUDSTACK-3016.
--

Resolution: Fixed

 remove zonetype parameter from list API commands
 

 Key: CLOUDSTACK-3016
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3016
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Reporter: Jessica Wang
Assignee: Jessica Wang





--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Closed] (CLOUDSTACK-3016) remove zonetype parameter from list API commands

2013-10-09 Thread ASF subversion and git services (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Wang closed CLOUDSTACK-3016.



 remove zonetype parameter from list API commands
 

 Key: CLOUDSTACK-3016
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3016
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Reporter: Jessica Wang
Assignee: Jessica Wang





--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (CLOUDSTACK-3154) [UI] No task notification after successful removal of VMware DC from cloudstack zone.


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13790866#comment-13790866
 ] 

ASF subversion and git services commented on CLOUDSTACK-3154:
-

Commit b8ed87246f71c52481bd4fb8d3539f3de183dd20 in branch refs/heads/4.2 from 
[~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b8ed872 ]

CLOUDSTACK-3154: UI  Infrastructure  zone detail  remove VMware datacenter 
action  fix a bug that incorrect property name was used to retrieve embedded 
object in API response.


 [UI] No task notification after successful removal of VMware DC from 
 cloudstack zone.
 -

 Key: CLOUDSTACK-3154
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3154
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.2.0
 Environment: Cloudstack deployed over VMware ESXi 5.0 servers
Reporter: Sateesh Chodapuneedi
 Fix For: 4.2.1


 Steps to reproduce -
 1) Goto Infrastructure - click on zones
 2) Click on specific zone which is already added with Vmware DC
 3) Click on icon Remove VMware Datacenter
 4) Even after successful completion of the command, UI continues to show wait 
 image (circles in middle).
 Expected -
 UI should stop wait image  display successful or failure notification.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Assigned] (CLOUDSTACK-3154) [UI] No task notification after successful removal of VMware DC from cloudstack zone.

2013-10-09 Thread ASF subversion and git services (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Wang reassigned CLOUDSTACK-3154:


Assignee: Jessica Wang

 [UI] No task notification after successful removal of VMware DC from 
 cloudstack zone.
 -

 Key: CLOUDSTACK-3154
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3154
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.2.0
 Environment: Cloudstack deployed over VMware ESXi 5.0 servers
Reporter: Sateesh Chodapuneedi
Assignee: Jessica Wang
 Fix For: 4.2.1


 Steps to reproduce -
 1) Goto Infrastructure - click on zones
 2) Click on specific zone which is already added with Vmware DC
 3) Click on icon Remove VMware Datacenter
 4) Even after successful completion of the command, UI continues to show wait 
 image (circles in middle).
 Expected -
 UI should stop wait image  display successful or failure notification.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (CLOUDSTACK-3154) [UI] No task notification after successful removal of VMware DC from cloudstack zone.


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13790867#comment-13790867
 ] 

ASF subversion and git services commented on CLOUDSTACK-3154:
-

Commit 0b69e890e07cb788e8475cdbcf3bb50e54e6e869 in branch refs/heads/master 
from [~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0b69e89 ]

CLOUDSTACK-3154: UI  Infrastructure  zone detail  remove VMware datacenter 
action  fix a bug that incorrect property name was used to retrieve embedded 
object in API response.


 [UI] No task notification after successful removal of VMware DC from 
 cloudstack zone.
 -

 Key: CLOUDSTACK-3154
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3154
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.2.0
 Environment: Cloudstack deployed over VMware ESXi 5.0 servers
Reporter: Sateesh Chodapuneedi
 Fix For: 4.2.1


 Steps to reproduce -
 1) Goto Infrastructure - click on zones
 2) Click on specific zone which is already added with Vmware DC
 3) Click on icon Remove VMware Datacenter
 4) Even after successful completion of the command, UI continues to show wait 
 image (circles in middle).
 Expected -
 UI should stop wait image  display successful or failure notification.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4843) allow a normal user to specify “isfeatured” when registering ISO (API won’t ignore “isfeatured” parameter when a normal user passes it)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Wang updated CLOUDSTACK-4843:
-

Summary: allow a normal user to specify “isfeatured” when registering ISO 
(API won’t ignore “isfeatured” parameter when a normal user passes it)  (was: 
allow a normal user to specify “isfeatured” when registering ISO (API won’t 
ignore “isfeatured” parameter when a normal user passes it)))

 allow a normal user to specify “isfeatured” when registering ISO (API won’t 
 ignore “isfeatured” parameter when a normal user passes it)
 ---

 Key: CLOUDSTACK-4843
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4843
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Reporter: Jessica Wang
 Fix For: 4.2.1


 From: Nitin Mehta 
 Sent: Wednesday, October 09, 2013 2:08 PM
 To: Jessica Wang; d...@cloudstack.apache.org; Alena Prokharchyk
 Cc: Shweta Agarwal
 Subject: Re: questions about registerIso API and updateIsoPermissions API
 I think (1) is the right way to go.
 =
 From: Jessica Wang jessica.w...@citrix.com
 Date: Wednesday 9 October 2013 12:47 PM
 To: Nitin Mehta nitin.me...@citrix.com, d...@cloudstack.apache.org 
 d...@cloudstack.apache.org, Alena Prokharchyk alena.prokharc...@citrix.com
 Cc: Shweta Agarwal shweta.agar...@citrix.com
 Subject: RE: questions about registerIso API and updateIsoPermissions API
 Currently, at API level, a normal user is not allowed to specify “isfeatured” 
 when registering ISO (API will ignore “isfeatured” parameter when a normal 
 user passes it),
 but a normal user is allowed to specify “isfeatured” when updating ISO.
  
 Should we fix API to:
 (1) allow a normal user to specify “isfeatured” when registering ISO (API 
 won’t ignore “isfeatured” parameter when a normal user passes it)
 OR
 (2) disallow a normal user to specify “isfeatured” when updating ISO
 ? 



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-3111) [UI] Storage tab is not showing the Hypervisor column as 'KVM' if the (root/data)disk is attached to instance running in KVM Hypervisor.


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Wang updated CLOUDSTACK-3111:
-

Component/s: (was: UI)
 API

 [UI] Storage tab is not showing the Hypervisor column as 'KVM' if the 
 (root/data)disk is attached to instance running in KVM Hypervisor.
 

 Key: CLOUDSTACK-3111
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3111
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.1.1, 4.2.0
Reporter: Rajesh Battala
 Fix For: 4.2.1

 Attachments: screen1.png


 Attaching the screenshot.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (CLOUDSTACK-3111) [UI] Storage tab is not showing the Hypervisor column as 'KVM' if the (root/data)disk is attached to instance running in KVM Hypervisor.

2013-10-09 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13790886#comment-13790886
 ] 

Jessica Wang commented on CLOUDSTACK-3111:
--

This is an API bug, NOT UI bug.

Because listVolumes API doesn't return hypervisor property of volume that is 
attached to instance running in KVM.

I'll remove UI and add API to Component field.

When filing an UI or API bug next time, please provide API call info (which is 
very useful),
like this:
http://10.215.3.26:8080/client/api?command=listVolumesresponse=jsonsessionkey=IyFSzZzGCj1zlT%2FtDBRTkCLYjkk%3DlistAll=truepage=1pagesize=20_=1381354248647
{
listvolumesresponse: {
count: 3,
volume: [
{
id: 88fbcdc9-3b96-4589-b65a-66facfb78894,
name: ROOT-6,
zoneid: 6bcd3bd9-591c-4d99-a164-d05b87df1b04,
zonename: jw-adv,
type: ROOT,
deviceid: 0,
virtualmachineid: 0acb7fb8-2dba-4752-ab2c-8b5dbe133cd8,
vmname: bbb,
vmdisplayname: bbb,
vmstate: Running,
size: 21474836480,
created: 2013-10-08T15:18:03-0700,
state: Ready,
account: admin,
domainid: b99cd8ec-2d40-11e3-86aa-3c970e739c3e,
domain: ROOT,
storagetype: shared,
hypervisor: XenServer,
storage: jw-primary,
destroyed: false,
serviceofferingid: 7a48a248-5328-4e91-b7a4-2189a98e8e12,
serviceofferingname: Small Instance,
serviceofferingdisplaytext: Small Instance,
isextractable: true,
tags: [],
displayvolume: false
},
{
id: ef558c60-c0ca-415b-ba21-19f14959061d,
name: aaa,
zoneid: 6bcd3bd9-591c-4d99-a164-d05b87df1b04,
zonename: jw-adv,
type: DATADISK,
deviceid: 1,
virtualmachineid: 0acb7fb8-2dba-4752-ab2c-8b5dbe133cd8,
vmname: bbb,
vmdisplayname: bbb,
vmstate: Running,
size: 5368709120,
created: 2013-10-08T15:17:14-0700,
state: Ready,
account: admin,
domainid: b99cd8ec-2d40-11e3-86aa-3c970e739c3e,
domain: ROOT,
storagetype: shared,
hypervisor: XenServer,
diskofferingid: e1505081-c2d8-4102-8f2b-eecd1c889c05,
diskofferingname: Small,
diskofferingdisplaytext: Small Disk, 5 GB,
storage: jw-primary,
attached: 2013-10-08T15:28:56-0700,
destroyed: false,
isextractable: true,
tags: [],
displayvolume: true
},
{
id: 94dff3ee-8625-43df-a660-8ec1d30b092d,
name: ROOT-3,
zoneid: 6bcd3bd9-591c-4d99-a164-d05b87df1b04,
zonename: jw-adv,
type: ROOT,
deviceid: 0,
virtualmachineid: 29228971-e4a0-49d9-861f-6c0a4e1a0b08,
vmname: aaa,
vmdisplayname: aaa,
vmstate: Stopped,
size: 21474836480,
created: 2013-10-04T15:18:56-0700,
state: Ready,
account: bbb_user,
domainid: 478aa8f0-5b1c-4e69-ae28-31a78e59dba5,
domain: bbb,
storagetype: shared,
hypervisor: XenServer,
storage: jw-primary,
destroyed: false,
serviceofferingid: 7a48a248-5328-4e91-b7a4-2189a98e8e12,
serviceofferingname: Small Instance,
serviceofferingdisplaytext: Small Instance,
isextractable: true,
tags: [],
displayvolume: false
}
]
}
}


 [UI] Storage tab is not showing the Hypervisor column as 'KVM' if the 
 (root/data)disk is attached to instance running in KVM Hypervisor.
 

 Key: CLOUDSTACK-3111
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3111
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.1.1, 4.2.0
Reporter: Rajesh Battala
 Fix For: 4.2.1

 Attachments: screen1.png


 Attaching the screenshot.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (CLOUDSTACK-3105) UI- View Hosts option in Vm detail page lists all the hosts. listHosts call is made with hostid instead of id.


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13790912#comment-13790912
 ] 

ASF subversion and git services commented on CLOUDSTACK-3105:
-

Commit dc8f053d6aa1fb9ae58e8a238fcdaafdbfc8d972 in branch refs/heads/master 
from [~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=dc8f053 ]

CLOUDSTACK-3105: UI  Instances menu  Instance detailView  View Hosts  fix a 
bug that wrong parameter name is passed to listHosts API.


 UI- View Hosts option in Vm detail page lists all the hosts. listHosts call 
 is made with hostid instead of id.
 

 Key: CLOUDSTACK-3105
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3105
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.2.0
 Environment: Build from master
Reporter: Sangeetha Hariharan
Assignee: Brian Federle
 Fix For: 4.2.1


 UI- View Hosts option in Vm detail page lists all the hosts.
 Go to Instances list and select ant 1 instance , so that the detail view of 
 the instance is presented.
 Click on View Hosts option.
 All hosts are listed in this view.
 listHosts API call passes Vm's host uuid in hostid parameter instead of id. 
 2013-06-20 18:23:10,295 INFO  [cloud.api.ApiServer] (catalina-exec-5:null) 
 (userId=2 accountId=2 sessionId=7D5DEB7A62BBD2DE48298AAC7C351909) 
 10.252.120.103 -- GET 
 command=listHoststype=Routinghostid=7cdff16f-623e-40df-98f5-393d223fec52page=1pagesize=20response=jsonsessionkey=feUkuow%2BfRcVloUXlGs37A%2BWNjw%3D_=1371777803998
  200 { listhostsresponse : { count:2 ,host : [  
 {id:360a6630-600b-4472-803f-5958c1b71203,name:Rack3Host20.lab.vmops.com,state:Up,type:Routing,ipaddress:10.223.59.66,zoneid:c6fe9dd8-6b3f-4f4e-8f5c-1030b93208a6,zonename:ZONE-NTIER-AGN,zonetype:Advanced,podid:7b15cf66-8e01-459f-bd51-1bb382ab5ddb,podname:POD-1,version:4.2.0-SNAPSHOT,hypervisor:XenServer,cpunumber:4,cpuspeed:2261,cpuallocated:0%,cpuused:0.05%,cpuwithoverprovisioning:9044.0,networkkbsread:3521,networkkbswrite:10295,memorytotal:16190149248,memoryallocated:1073741824,memoryused:2168436,capabilities: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,lastpinged:1970-01-16T04:07:03-0800,managementserverid:7471666038533,clusterid:18fd96c3-1036-49ac-8291-63081b6cebc3,clustername:XenCluster1,clustertype:CloudManaged,islocalstorageactive:false,created:2013-06-20T17:34:14-0700,events:Ping;
  Remove; StartAgentRebalance; AgentDisconnected; ManagementServerDown; 
 HostDown; AgentConnected; ShutdownRequested; 
 PingTimeout,resourcestate:Enabled,hypervisorversion:6.1.0,hahost:false},
  
 {id:7cdff16f-623e-40df-98f5-393d223fec52,name:Rack3Host23.lab.vmops.com,state:Up,type:Routing,ipaddress:10.223.59.67,zoneid:c6fe9dd8-6b3f-4f4e-8f5c-1030b93208a6,zonename:ZONE-NTIER-AGN,zonetype:Advanced,podid:7b15cf66-8e01-459f-bd51-1bb382ab5ddb,podname:POD-1,version:4.2.0-SNAPSHOT,hypervisor:XenServer,cpunumber:4,cpuspeed:2261,cpuallocated:0%,cpuused:0.1%,cpuwithoverprovisioning:9044.0,networkkbsread:7193,networkkbswrite:30348,memorytotal:16190149248,memoryallocated:3355443200,memoryused:4580544,capabilities:xen-3.0-x86_64
  , 
 xen-3.0-x86_32p,lastpinged:1970-01-16T04:05:17-0800,managementserverid:7471666038533,clusterid:18fd96c3-1036-49ac-8291-63081b6cebc3,clustername:XenCluster1,clustertype:CloudManaged,islocalstorageactive:false,created:2013-06-19T11:30:41-0700,events:Ping;
  Remove; StartAgentRebalance; AgentDisconnected; ManagementServerDown; 
 HostDown; AgentConnected; ShutdownRequested; 
 PingTimeout,resourcestate:Enabled,hypervisorversion:6.1.0,hahost:false}
  ] } }
  



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (CLOUDSTACK-3105) UI- View Hosts option in Vm detail page lists all the hosts. listHosts call is made with hostid instead of id.

2013-10-09 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13790910#comment-13790910
 ] 

ASF subversion and git services commented on CLOUDSTACK-3105:
-

Commit efd6dd4947d930592c8dbd4804cedef0760dad58 in branch refs/heads/4.2 from 
[~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=efd6dd4 ]

CLOUDSTACK-3105: UI  Instances menu  Instance detailView  View Hosts  fix a 
bug that wrong parameter name is passed to listHosts API.


 UI- View Hosts option in Vm detail page lists all the hosts. listHosts call 
 is made with hostid instead of id.
 

 Key: CLOUDSTACK-3105
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3105
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.2.0
 Environment: Build from master
Reporter: Sangeetha Hariharan
Assignee: Brian Federle
 Fix For: 4.2.1


 UI- View Hosts option in Vm detail page lists all the hosts.
 Go to Instances list and select ant 1 instance , so that the detail view of 
 the instance is presented.
 Click on View Hosts option.
 All hosts are listed in this view.
 listHosts API call passes Vm's host uuid in hostid parameter instead of id. 
 2013-06-20 18:23:10,295 INFO  [cloud.api.ApiServer] (catalina-exec-5:null) 
 (userId=2 accountId=2 sessionId=7D5DEB7A62BBD2DE48298AAC7C351909) 
 10.252.120.103 -- GET 
 command=listHoststype=Routinghostid=7cdff16f-623e-40df-98f5-393d223fec52page=1pagesize=20response=jsonsessionkey=feUkuow%2BfRcVloUXlGs37A%2BWNjw%3D_=1371777803998
  200 { listhostsresponse : { count:2 ,host : [  
 {id:360a6630-600b-4472-803f-5958c1b71203,name:Rack3Host20.lab.vmops.com,state:Up,type:Routing,ipaddress:10.223.59.66,zoneid:c6fe9dd8-6b3f-4f4e-8f5c-1030b93208a6,zonename:ZONE-NTIER-AGN,zonetype:Advanced,podid:7b15cf66-8e01-459f-bd51-1bb382ab5ddb,podname:POD-1,version:4.2.0-SNAPSHOT,hypervisor:XenServer,cpunumber:4,cpuspeed:2261,cpuallocated:0%,cpuused:0.05%,cpuwithoverprovisioning:9044.0,networkkbsread:3521,networkkbswrite:10295,memorytotal:16190149248,memoryallocated:1073741824,memoryused:2168436,capabilities: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,lastpinged:1970-01-16T04:07:03-0800,managementserverid:7471666038533,clusterid:18fd96c3-1036-49ac-8291-63081b6cebc3,clustername:XenCluster1,clustertype:CloudManaged,islocalstorageactive:false,created:2013-06-20T17:34:14-0700,events:Ping;
  Remove; StartAgentRebalance; AgentDisconnected; ManagementServerDown; 
 HostDown; AgentConnected; ShutdownRequested; 
 PingTimeout,resourcestate:Enabled,hypervisorversion:6.1.0,hahost:false},
  
 {id:7cdff16f-623e-40df-98f5-393d223fec52,name:Rack3Host23.lab.vmops.com,state:Up,type:Routing,ipaddress:10.223.59.67,zoneid:c6fe9dd8-6b3f-4f4e-8f5c-1030b93208a6,zonename:ZONE-NTIER-AGN,zonetype:Advanced,podid:7b15cf66-8e01-459f-bd51-1bb382ab5ddb,podname:POD-1,version:4.2.0-SNAPSHOT,hypervisor:XenServer,cpunumber:4,cpuspeed:2261,cpuallocated:0%,cpuused:0.1%,cpuwithoverprovisioning:9044.0,networkkbsread:7193,networkkbswrite:30348,memorytotal:16190149248,memoryallocated:3355443200,memoryused:4580544,capabilities:xen-3.0-x86_64
  , 
 xen-3.0-x86_32p,lastpinged:1970-01-16T04:05:17-0800,managementserverid:7471666038533,clusterid:18fd96c3-1036-49ac-8291-63081b6cebc3,clustername:XenCluster1,clustertype:CloudManaged,islocalstorageactive:false,created:2013-06-19T11:30:41-0700,events:Ping;
  Remove; StartAgentRebalance; AgentDisconnected; ManagementServerDown; 
 HostDown; AgentConnected; ShutdownRequested; 
 PingTimeout,resourcestate:Enabled,hypervisorversion:6.1.0,hahost:false}
  ] } }
  



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Resolved] (CLOUDSTACK-3105) UI- View Hosts option in Vm detail page lists all the hosts. listHosts call is made with hostid instead of id.


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Wang resolved CLOUDSTACK-3105.
--

Resolution: Fixed

 UI- View Hosts option in Vm detail page lists all the hosts. listHosts call 
 is made with hostid instead of id.
 

 Key: CLOUDSTACK-3105
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3105
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.2.0
 Environment: Build from master
Reporter: Sangeetha Hariharan
Assignee: Jessica Wang
 Fix For: 4.2.1


 UI- View Hosts option in Vm detail page lists all the hosts.
 Go to Instances list and select ant 1 instance , so that the detail view of 
 the instance is presented.
 Click on View Hosts option.
 All hosts are listed in this view.
 listHosts API call passes Vm's host uuid in hostid parameter instead of id. 
 2013-06-20 18:23:10,295 INFO  [cloud.api.ApiServer] (catalina-exec-5:null) 
 (userId=2 accountId=2 sessionId=7D5DEB7A62BBD2DE48298AAC7C351909) 
 10.252.120.103 -- GET 
 command=listHoststype=Routinghostid=7cdff16f-623e-40df-98f5-393d223fec52page=1pagesize=20response=jsonsessionkey=feUkuow%2BfRcVloUXlGs37A%2BWNjw%3D_=1371777803998
  200 { listhostsresponse : { count:2 ,host : [  
 {id:360a6630-600b-4472-803f-5958c1b71203,name:Rack3Host20.lab.vmops.com,state:Up,type:Routing,ipaddress:10.223.59.66,zoneid:c6fe9dd8-6b3f-4f4e-8f5c-1030b93208a6,zonename:ZONE-NTIER-AGN,zonetype:Advanced,podid:7b15cf66-8e01-459f-bd51-1bb382ab5ddb,podname:POD-1,version:4.2.0-SNAPSHOT,hypervisor:XenServer,cpunumber:4,cpuspeed:2261,cpuallocated:0%,cpuused:0.05%,cpuwithoverprovisioning:9044.0,networkkbsread:3521,networkkbswrite:10295,memorytotal:16190149248,memoryallocated:1073741824,memoryused:2168436,capabilities: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,lastpinged:1970-01-16T04:07:03-0800,managementserverid:7471666038533,clusterid:18fd96c3-1036-49ac-8291-63081b6cebc3,clustername:XenCluster1,clustertype:CloudManaged,islocalstorageactive:false,created:2013-06-20T17:34:14-0700,events:Ping;
  Remove; StartAgentRebalance; AgentDisconnected; ManagementServerDown; 
 HostDown; AgentConnected; ShutdownRequested; 
 PingTimeout,resourcestate:Enabled,hypervisorversion:6.1.0,hahost:false},
  
 {id:7cdff16f-623e-40df-98f5-393d223fec52,name:Rack3Host23.lab.vmops.com,state:Up,type:Routing,ipaddress:10.223.59.67,zoneid:c6fe9dd8-6b3f-4f4e-8f5c-1030b93208a6,zonename:ZONE-NTIER-AGN,zonetype:Advanced,podid:7b15cf66-8e01-459f-bd51-1bb382ab5ddb,podname:POD-1,version:4.2.0-SNAPSHOT,hypervisor:XenServer,cpunumber:4,cpuspeed:2261,cpuallocated:0%,cpuused:0.1%,cpuwithoverprovisioning:9044.0,networkkbsread:7193,networkkbswrite:30348,memorytotal:16190149248,memoryallocated:3355443200,memoryused:4580544,capabilities:xen-3.0-x86_64
  , 
 xen-3.0-x86_32p,lastpinged:1970-01-16T04:05:17-0800,managementserverid:7471666038533,clusterid:18fd96c3-1036-49ac-8291-63081b6cebc3,clustername:XenCluster1,clustertype:CloudManaged,islocalstorageactive:false,created:2013-06-19T11:30:41-0700,events:Ping;
  Remove; StartAgentRebalance; AgentDisconnected; ManagementServerDown; 
 HostDown; AgentConnected; ShutdownRequested; 
 PingTimeout,resourcestate:Enabled,hypervisorversion:6.1.0,hahost:false}
  ] } }
  



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[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
 ]

Jessica Wang updated CLOUDSTACK-3067:
-

Assignee: Brian Federle

 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
Assignee: Brian Federle
 Fix For: 4.2.1

 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 was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-2767) There is no API/UI check on input parameters for Global settings,zone settings and account settings

2013-10-09 Thread ASF subversion and git services (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Wang updated CLOUDSTACK-2767:
-

Component/s: (was: UI)

 There is no API/UI check on input parameters for Global settings,zone 
 settings  and account  settings 
 --

 Key: CLOUDSTACK-2767
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2767
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API, Management Server
Affects Versions: 4.2.0
Reporter: prashant kumar mishra
 Fix For: 4.2.1






--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (CLOUDSTACK-4784) 2.2.x-4.x DB upgrade: network offerings with redundant router support, are missing certain services after the upgrade


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13790923#comment-13790923
 ] 

ASF subversion and git services commented on CLOUDSTACK-4784:
-

Commit 34fecbf5e2b8af9251e016df70fa4063c33fcbb3 in branch refs/heads/4.2 from 
[~alena1108]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=34fecbf ]

CLOUDSTACK-4784: 22x to 4.x upgrade - don't ignore redundant router network 
offering, when update ntwk_offering_serivce_map with PF/StaticNat/SourceNat 
services


 2.2.x-4.x DB upgrade: network offerings with redundant router support, are 
 missing certain services after the upgrade
 -

 Key: CLOUDSTACK-4784
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4784
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Install and Setup
Affects Versions: 4.0.0
Reporter: Alena Prokharchyk
Assignee: Alena Prokharchyk
 Fix For: Future


 Network offerings with redundant router support, are missing certain services 
 after the upgrade from 2.2.x to 4.x:
 PF/LB/StaticNat/SourceNat
 Workaround for existing customers who's upgraded:
 ==
 1) Fix network offering. First, get the network offering id:
 mysql select id from network_offerings where 
 name='DefaultIsolatedNetworkOfferingWithSourceNatService-redundant';
 id
 9
 Then update the ntwk_offering_service_map table with the missing services:
 insert into ntwk_offering_service_map (network_offering_id, service, 
 provider, created) values (9, 'SourceNat', 'VirtualRouter', now());
 insert into ntwk_offering_service_map (network_offering_id, service, 
 provider, created) values (9, 'StaticNat', 'VirtualRouter', now());
 insert into ntwk_offering_service_map (network_offering_id, service, 
 provider, created) values (9, 'PortForwarding', 'VirtualRouter', now());
 insert into ntwk_offering_service_map (network_offering_id, service, 
 provider, created) values (9, 'Lb', 'VirtualRouter', now());
 2) Then update the network with the services.
 First, get the ids of the network(s) to update
 mysql select id from networks where network_offering_id=9;
 id
 209
 Then insert the entries to ntwk_service_map table:
 insert into ntwk_service_map (network_id, service, provider, created) values 
 (209, 'SourceNat', 'VirtualRouter', now());
 insert into ntwk_service_map (network_id, service, provider, created) values 
 (209, 'StaticNat', 'VirtualRouter', now());
 insert into ntwk_service_map (network_id, service, provider, created) values 
 (209, 'PortForwarding', 'VirtualRouter', now());
 insert into ntwk_service_map (network_id, service, provider, created) values 
 (209, 'Lb', 'VirtualRouter', now());



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Resolved] (CLOUDSTACK-2393) PVLAN - UI - For networks created with private Vlan , in network detail page VLAN is shown as N/A.


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Wang resolved CLOUDSTACK-2393.
--

Resolution: Fixed

Author: Jessica Wang 
jessicaw...@apache.org#mailto:jessicaw...@apache.org
Date:   2 days ago (Mon Oct 07 11:30:31 2013)
Commit hash:90aa2f2e3fb544f45e192df533fa4c5a962dd28f

CLOUDSTACK-4672: UI  Network  details tab  add new field broadcasturi to 
show Primary VLAN, Secondary Isolated VLAN.

Contained in branches: 4.2
Contained in no tag

 PVLAN - UI - For networks created with private Vlan , in network detail page 
 VLAN is shown as N/A. 
 -

 Key: CLOUDSTACK-2393
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2393
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server, UI
Affects Versions: 4.2.0
 Environment: Branch from pvlan
Reporter: Sangeetha Hariharan
 Fix For: 4.2.1

 Attachments: valn-for-pvaln-networks.png


 PVLAN - UI - For networks created with private Vlan , in network detail page 
 VLAN is shown as N/A. 
 Steps to reproduce the problem:
 Create a shared network by passing Private vlan.
 From Network tab- network list - view details of all this network.
 Notice that the VLAN field shows up as N/A.
 API call returns broadcasturi:pvlan://1611-i998 .
 { listnetworksresponse : { count:1 ,network : [  
 {id:a2fb9fda-f6a1-4348-beb1-4e29367b3dbd,name:pvlan1,displaytext:pvlan1,broadcastdomaintype:Pvlan,traffictype:Guest,gateway:10.223.161.65,netmask:255.255.255.192,cidr:10.223.161.64/26,zoneid:b5b71f7b-19a4-4f32-9512-d9b0eac382f3,zonename:zone1,zonetype:Advanced,networkofferingid:9bb84f2a-a5d1-4db1-b52e-a1b72517863e,networkofferingname:DefaultSharedNetworkOffering,networkofferingdisplaytext:Offering
  for Shared 
 networks,networkofferingavailability:Optional,issystem:false,state:Setup,related:a2fb9fda-f6a1-4348-beb1-4e29367b3dbd,broadcasturi:pvlan://1611-i998,dns1:72.52.126.11,dns2:72.52.126.12,type:Shared,vlan:N/A,acltype:Domain,subdomainaccess:true,domainid:b7959800-b760-11e2-a38a-06f4b42b,domain:ROOT,service:[{name:Dns,capability:[{name:AllowDnsSuffixModification,value:true,canchooseservicecapability:false}]},{name:UserData},{name:Dhcp}],networkdomain:test-pvlan1,physicalnetworkid:2ddd2d19-d5af-49bd-a6fd-f1e41902bab7,restartrequired:false,specifyipranges:true,canusefordeploy:true,ispersistent:false,tags:[]}
  ] } }



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-375) Unable to delete physical network - because there are other networks attached


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Wang updated CLOUDSTACK-375:


Component/s: (was: UI)
 API

 Unable to delete physical network - because there are other networks attached
 -

 Key: CLOUDSTACK-375
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-375
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.0.0, 4.1.0, 4.2.0
 Environment: CS 4.1
 CentOS6.3
Reporter: ilya musayev
  Labels: Network
 Fix For: 4.2.1


 Unable to delete physical network - because there are other networks attached
 Attempted to do a complete cleanup of the setup and start fresh.. I was able 
 to delete hosts, cluster and pod but when i get to delete the Zone, i need to 
 first delete the Physical Network. The physical network has other networks 
 under L2/L3 switch (Guest, Management and Storage) with no IP addresses 
 assigned or visible.
 When i attempt to delete the Physical Network, i get the error The Physical 
 Network is not deletable because there are networks associated to this 
 physical network
 2012-10-18 18:40:56,824 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (catalina-exec-4:null) submit async job-21, details: AsyncJobVO {id:21, 
 userId: 2, accountId: 2, sessionKey: null, instanceType: PhysicalNetwork, 
 instanceId: null, cmd: com.cloud.api.commands.DeletePhysicalNetworkCmd, 
 cmdOriginator: null, cmdInfo: 
 {id:b44e7b2c-27bc-41c7-837c-f0c37a9a85d6,response:json,sessionkey:f8xnTzQ2eSRR33zf93kijnlDg+w\u003d,ctxUserId:2,_:1350600056737,ctxAccountId:2,ctxStartEventId:85},
  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
 processStatus: 0, resultCode: 0, result: null, initMsid: 345051904793, 
 completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
 2012-10-18 18:40:56,843 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-1:job-21) Executing 
 com.cloud.api.commands.DeletePhysicalNetworkCmd for job-21
 2012-10-18 18:40:56,923 ERROR [cloud.api.ApiDispatcher] 
 (Job-Executor-1:job-21) Exception while executing DeletePhysicalNetworkCmd:
 com.cloud.utils.exception.CloudRuntimeException: The Physical Network is not 
 deletable because there are networks associated to this physical network
 at 
 com.cloud.network.NetworkManagerImpl.checkIfPhysicalNetworkIsDeletable(NetworkManagerImpl.java:5541)
 at 
 com.cloud.network.NetworkManagerImpl.deletePhysicalNetwork(NetworkManagerImpl.java:5434)
 at 
 com.cloud.utils.component.ComponentLocator$InterceptorDispatcher.intercept(ComponentLocator.java:1231)
 at 
 com.cloud.api.commands.DeletePhysicalNetworkCmd.execute(DeletePhysicalNetworkCmd.java:74)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138)
 at 
 com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:432)
 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)
 I however cannot delete the other networks or anything underneath those 
 networks - nothing is available that can be deleted.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Created] (CLOUDSTACK-4844) Docs show incorrect URL for Windows password reset service download

2013-10-09 Thread Demetrius Tsitrelis (JIRA)

Demetrius Tsitrelis created CLOUDSTACK-4844:
---

 Summary: Docs show incorrect URL for Windows password reset 
service download
 Key: CLOUDSTACK-4844
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4844
 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: Demetrius Tsitrelis


In Section 12.13.2. Windows OS Installation of the admin guide, there is a link 
to the CloudInstanceManager.msi.  A slash is missing from the URL.  Even when 
the slash is added the referenced file does not seem to be in the indicated 
location.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4843) allow a normal user to specify “isfeatured” when registering ISO (API won’t ignore “isfeatured” parameter when a normal user passes it)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4843:
---

Assignee: Damodar Reddy T

 allow a normal user to specify “isfeatured” when registering ISO (API won’t 
 ignore “isfeatured” parameter when a normal user passes it)
 ---

 Key: CLOUDSTACK-4843
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4843
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Reporter: Jessica Wang
Assignee: Damodar Reddy T
 Fix For: 4.2.1


 From: Nitin Mehta 
 Sent: Wednesday, October 09, 2013 2:08 PM
 To: Jessica Wang; d...@cloudstack.apache.org; Alena Prokharchyk
 Cc: Shweta Agarwal
 Subject: Re: questions about registerIso API and updateIsoPermissions API
 I think (1) is the right way to go.
 =
 From: Jessica Wang jessica.w...@citrix.com
 Date: Wednesday 9 October 2013 12:47 PM
 To: Nitin Mehta nitin.me...@citrix.com, d...@cloudstack.apache.org 
 d...@cloudstack.apache.org, Alena Prokharchyk alena.prokharc...@citrix.com
 Cc: Shweta Agarwal shweta.agar...@citrix.com
 Subject: RE: questions about registerIso API and updateIsoPermissions API
 Currently, at API level, a normal user is not allowed to specify “isfeatured” 
 when registering ISO (API will ignore “isfeatured” parameter when a normal 
 user passes it),
 but a normal user is allowed to specify “isfeatured” when updating ISO.
  
 Should we fix API to:
 (1) allow a normal user to specify “isfeatured” when registering ISO (API 
 won’t ignore “isfeatured” parameter when a normal user passes it)
 OR
 (2) disallow a normal user to specify “isfeatured” when updating ISO
 ? 



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4817) Backup snapshot on Xen should take global setting s3.multipart.enabled.


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4817:
---

Priority: Critical  (was: Major)

 Backup snapshot on Xen should take global setting s3.multipart.enabled.
 ---

 Key: CLOUDSTACK-4817
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4817
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller
Affects Versions: 4.2.0
 Environment: XenServer
Reporter: Min Chen
Assignee: edison su
Priority: Critical
 Fix For: 4.2.1


 Currently backsnapshot to S3 on Xen only used single part upload in s3xen 
 plugin code, which will result in failure in case of snapshot is  5GB. We 
 need that plugin code to check the configuration setting s3.multipart.enabled 
 to choose multipart or singlepart upload.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4823) Please add an icon for new action assignVmToAnotherAccount in Instance detailView


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4823:
---

Priority: Critical  (was: Major)

 Please add an icon for new action assignVmToAnotherAccount in Instance 
 detailView
 ---

 Key: CLOUDSTACK-4823
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4823
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Reporter: Jessica Wang
Assignee: Brian Federle
Priority: Critical
 Fix For: 4.2.1

 Attachments: jessica_1.jpg, jessica_2.jpg






--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4786) Redundant router: the priority limitation

[
https://issues.apache.org/jira/browse/CLOUDSTACK-4786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Abhinandan Prateek updated CLOUDSTACK-4786:
---

Fix Version/s: (was: 4.2.1)
4.3.0

Redundant router: the priority limitation
-

Key: CLOUDSTACK-4786
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4786
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: Sheng Yang
Assignee: Sheng Yang
Fix For: 4.3.0

The limitation states that when using RVR, Network GC can run only 40 times
or RVR can only be restarted 40 times or Guest VM can only be restart 40
times before having the need to restart the network with cleanup=true
(downtime).
Example:
1. Let us say there is one VM in an account/network, VM1.
2. It is using 1 network, say N1 and it's created from a network offering that
has redundant router enabled.
3. When VM1 was launched, two RVRs were created, say R1 and R2.
4. At that time R1 has priority set to 100 and R2 99. This is the default
behavior.
5. Network GC is set to run every 30 minutes.
6. Let us draw a base line here, VM1 is running, R1 is running and has
priority set to 100, R2 is running as has priority set to 99.
7. Stop VM1.
8. Wait for 30+ minutes.
9. Check R1 and R2, they will be stopped.
10. Start VM1.
11. R1 and R2 will be started and their priorities will now be set to 99 and
98 resp.
12. If you repeat steps #7 through #10, you will observe that after 40 tries
priorities of R1 and R2 would be 20 and 19. You will observe that the RVR
won't start. It will complain about the priority being too low.
The only workaround now is to restart network with cleanup=true, basically
destroy old routers and create new ones.

--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4783) Unable to see a derieved template if the parent template is deleted


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4783:
---

Priority: Critical  (was: Major)

 Unable to see a derieved template if the parent template is deleted
 ---

 Key: CLOUDSTACK-4783
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4783
 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: Nitin Mehta
Priority: Critical
 Fix For: 4.2.1


 Functionality required/broken – For a template, if the parent template info
 (template Id) is provided in the listTemplates API then one should be able to
 query for the parent template id as well (whether existing/removed doesn't
 matter)



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4789) Fix ResourceMetaDataManagerTest


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4789:
---

Fix Version/s: (was: 4.2.1)
   4.3.0

 Fix ResourceMetaDataManagerTest
 ---

 Key: CLOUDSTACK-4789
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4789
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.2.1
Reporter: Nitin Mehta
Assignee: Nitin Mehta
 Fix For: 4.3.0






--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4811) Adding Incorrect CIDR in public ip range of zone create wizard is allowing


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4811:
---

Priority: Critical  (was: Major)

 Adding Incorrect CIDR in public ip range of zone create wizard is allowing
 --

 Key: CLOUDSTACK-4811
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4811
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Network Controller
Reporter: Jayapal Reddy
Assignee: Damodar Reddy T
Priority: Critical
 Fix For: 4.2.1


 1. Add a new zone from UI add zone wizard.
 2. Add incorrect cidr in in 3rd tab Setup network  PUBLIC TRAFFIC
 gateway   netmask   VLANStart IP End 
 IP 
 10.147.52.1 255.255.25.0   52  10.147.52.100  
 10.147.52.120
 3. UI is allowing the above config
 4. The zone will also get deployed.
 5. The problem is coming in creating the public interface in system vms. If 
 the interface got created problem in reaching the public network.
 6. This issue is pain to user because after deploying zone user need to 
 recreate zone again. Also some times user don't realise about the 
 misconfiguration.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4746) Allocation capacity of a cluster during HA


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4746:
---

Assignee: Prachi Damle

 Allocation capacity of a cluster during HA
 --

 Key: CLOUDSTACK-4746
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4746
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.2.0
Reporter: Nitin Mehta
Assignee: Prachi Damle
Priority: Critical
 Fix For: 4.2.1


 When the host goes down. Cloudstack will stop the VM's for which HA is not 
 enabled. Once cloudstack marks these VM's as stopped then the capacity of 
 these VM's is moved into the reserved capacity.
 If the VM's are HA enabled then cloudstack will stop and start the VM's on 
 another host. During this time the capacity of the VM's will be moved to 
 reserved capacity once the VM's are stopped, But when the Vm's are being 
 started cloudstack will try to calculate what will be total allocated 
 capacity if the VM is started again ( even though the CPU for the VM is 
 already reserved). This is a bug in cloudstack where the CPU required for the 
 VM is considered twice when calculating the allocated capacity.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4783) Unable to see a derieved template if the parent template is deleted


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4783:
---

Assignee: Harikrishna Patnala

 Unable to see a derieved template if the parent template is deleted
 ---

 Key: CLOUDSTACK-4783
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4783
 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: Nitin Mehta
Assignee: Harikrishna Patnala
Priority: Critical
 Fix For: 4.2.1


 Functionality required/broken – For a template, if the parent template info
 (template Id) is provided in the listTemplates API then one should be able to
 query for the parent template id as well (whether existing/removed doesn't
 matter)



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4768) [Automation] Race condition; delete the template and create VM at same time; deployment failed with libvirt error


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4768:
---

Fix Version/s: (was: 4.2.1)
   4.3.0

 [Automation] Race condition; delete the template and create VM at same time; 
 deployment failed with libvirt error 
 --

 Key: CLOUDSTACK-4768
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4768
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM
Affects Versions: 4.2.1
 Environment: KVM (RHEL 6.3)
 branch - 4.2-forward
Reporter: Rayees Namathponnan
Assignee: edison su
 Fix For: 4.3.0

 Attachments: Sep_30_KVM_Adv_Zone.rar


 This issue observed during regression automation run, few vm deployment 
 failed due to some race condition;  this issue observed while template delete 
 and deploy vm command issued at same time 
 Observed below error in MS log; attached full logs with this defect
 2013-09-27 19:39:36,490 DEBUG [agent.manager.AgentManagerImpl] 
 (AgentManager-Handler-4:null) Ping from 9
 2013-09-27 19:39:36,678 DEBUG [agent.transport.Request] 
 (AgentManager-Handler-10:null) Seq 2-1251542761: Processing:  { Ans: , 
 MgmtId: 29066118877352, via: 2, Ver: v1, Flags:
 110, 
 [{com.cloud.agent.api.StartAnswer:{vm:{id:247,name:i-192-247-QA,type:User,cpus:1,minSpeed:100,maxSpeed:100,minRam:134217728,maxRam:134217728,arch
 :x86_64,os:CentOS 5.5 
 (64-bit),bootArgs:,rebootOnCrash:false,enableHA:false,limitCpuUse:false,enableDynamicallyScaleVm:false,vncPassword:992293216169b56
 ,vncAddr:10.223.50.67,params:{Message.ReservedCapacityFreed.Flag:false},uuid:590048c7-682c-4dd5-be5e-b0ea9203d181,disks:[{data:{org.apache.cloudstack.storag
 e.to.VolumeObjectTO:{uuid:a7b372d9-8cb4-4549-9ce1-6b4b2b249472,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:41b632b5-40
 b3-3024-a38b-ea259c72579f,id:2,poolType:NetworkFilesystem,host:10.223.110.232,path:/export/home/rayees/SC_QA_AUTO4/primary2,port:2049}},name:ROOT-247,siz
 e:8589934592,path:35083f24-8882-4754-b29f-6ce8025df305,volumeId:271,vmName:i-192-247-QA,accountId:192,format:QCOW2,id:271,hypervisorType:KVM}},diskSeq
 :0,type:ROOT},{data:{org.apache.cloudstack.storage.to.TemplateObjectTO:{id:0,format:ISO,accountId:0,hvm:false}},diskSeq:3,type:ISO}],nics:[{deviceId
 :0,networkRateMbps:200,defaultNic:true,uuid:b10db69f-b7f6-419f-872a-feaa31cab581,ip:10.1.1.221,netmask:255.255.255.0,gateway:10.1.1.1,mac:02:00:5a:16:0
 0:02,dns1:8.8.8.8,broadcastType:Vlan,type:Guest,broadcastUri:vlan://2340,isolationUri:vlan://2340,isSecurityGroupEnabled:false}]},result:false,detail
 s:unable to set user and group to '0:0' on 
 '/mnt/41b632b5-40b3-3024-a38b-ea259c72579f/ddeac719-b362-4462-b905-6b07578108de':
  No such file or directory,wait:0}}] }
 2013-09-27 19:39:36,679 DEBUG [agent.manager.AgentAttache] 
 (AgentManager-Handler-10:null) Seq 2-1251542761: No more commands found
 2013-09-27 19:39:36,679 DEBUG [agent.transport.Request] 
 (Job-Executor-139:job-1077 = [ f7164e6a-544f-4c8d-8dc6-45d74ace2094 ]) Seq 
 2-1251542761: Received:  { Ans: , MgmtId: 29
 066118877352, via: 2, Ver: v1, Flags: 110, { StartAnswer } }
 2013-09-27 19:39:36,683 INFO  [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-139:job-1077 = [ f7164e6a-544f-4c8d-8dc6-45d74ace2094 ]) Unable 
 to start VM on Host[-2-Routing
 ] due to unable to set user and group to '0:0' on 
 '/mnt/41b632b5-40b3-3024-a38b-ea259c72579f/ddeac719-b362-4462-b905-6b07578108de':
  No such file or directory
 2013-09-27 19:39:36,686 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-139:job-1077 = [ f7164e6a-544f-4c8d-8dc6-45d74ace2094 ]) 
 Cleaning up resources for the vm VM[U
 ser|590048c7-682c-4dd5-be5e-b0ea9203d181] in Starting state
 2013-09-27 19:39:36,687 DEBUG [agent.transport.Request] 
 (Job-Executor-139:job-1077 = [ f7164e6a-544f-4c8d-8dc6-45d74ace2094 ]) Seq 
 2-1251542762: Sending  { Cmd , MgmtId: 29066
 118877352, via: 2, Ver: v1, Flags: 100111, 
 [{com.cloud.agent.api.StopCommand:{isProxy:false,executeInSequence:true,vmName:i-192-247-QA,wait:0}}]
  }
 2013-09-27 19:39:36,884 DEBUG [agent.transport.Request] 
 (AgentManager-Handler-11:null) Seq 2-1251542762: Processing:  { Ans: , 
 MgmtId: 29066118877352, via: 2, Ver: v1, Flags:
 110, 
 [{com.cloud.agent.api.StopAnswer:{vncPort:0,result:true,wait:0}}] }



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4746) Allocation capacity of a cluster during HA


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4746:
---

Priority: Critical  (was: Major)

 Allocation capacity of a cluster during HA
 --

 Key: CLOUDSTACK-4746
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4746
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.2.0
Reporter: Nitin Mehta
Priority: Critical
 Fix For: 4.2.1


 When the host goes down. Cloudstack will stop the VM's for which HA is not 
 enabled. Once cloudstack marks these VM's as stopped then the capacity of 
 these VM's is moved into the reserved capacity.
 If the VM's are HA enabled then cloudstack will stop and start the VM's on 
 another host. During this time the capacity of the VM's will be moved to 
 reserved capacity once the VM's are stopped, But when the Vm's are being 
 started cloudstack will try to calculate what will be total allocated 
 capacity if the VM is started again ( even though the CPU for the VM is 
 already reserved). This is a bug in cloudstack where the CPU required for the 
 VM is considered twice when calculating the allocated capacity.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4741) URL of ImageStore not in proper format for XenServer


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4741:
---

Fix Version/s: (was: 4.2.1)
   4.3.0

 URL of ImageStore not in proper format for XenServer
 

 Key: CLOUDSTACK-4741
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4741
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Snapshot
Affects Versions: 4.2.0
Reporter: Gaurav Aradhye
 Fix For: 4.3.0


 Steps:
 Hit listImageStores API.
 check the url attribute of any ImageStore.
 On KVM and VMWare, the format of url is as below and which is correct:
 nfs://x.x.x.x:/dir1/dir2/dir3/dir4
 While on XenServer, the format of url is as below:
 nfs://x.x.x.x/dir1/dir2/dir3/dir4
 See, the colon (:) is missing after IP address x.x.x.x in XenServer results.
 Snapshot test cases which test whether the snapshot is present on secondary 
 storage will fail on XenServer due to this formatting issue.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (CLOUDSTACK-4729) Document workaround for IPMI protocal type for specific hardware on baremetal


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13791166#comment-13791166
 ] 

Abhinandan Prateek commented on CLOUDSTACK-4729:


Frank, Can you answer Jessica and change the assignment to her.

 Document workaround for IPMI protocal type for specific hardware on baremetal
 -

 Key: CLOUDSTACK-4729
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4729
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Doc
Affects Versions: 4.2.1
Reporter: frank zhang
Assignee: frank zhang
 Fix For: 4.2.1


 We should mention to users that Baremetal uses ipmitool to control lifecycle 
 of baremetal host. ipmitool default uses interface 'lan' to issue ipmi 
 commands. Depending on your motherboard, the interface may need to be 
 'lanplus', in this case, user has to modify script
 /usr/lib64/cloud/agent/scripts/util/ipmi.py
 replace all lines calling ipmi tool for example:
 o = ipmitool(-H, hostname, -U, usrname, -P, password, chassis, 
 power, status)
 to
 o = ipmitool(-H, hostname, ,-I, lanplus, -U, usrname, -P, password, 
 chassis, power, status)
 this issue will be addressed in next release.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4729) Document workaround for IPMI protocal type for specific hardware on baremetal


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4729:
---

Assignee: frank zhang

 Document workaround for IPMI protocal type for specific hardware on baremetal
 -

 Key: CLOUDSTACK-4729
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4729
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Doc
Affects Versions: 4.2.1
Reporter: frank zhang
Assignee: frank zhang
 Fix For: 4.2.1


 We should mention to users that Baremetal uses ipmitool to control lifecycle 
 of baremetal host. ipmitool default uses interface 'lan' to issue ipmi 
 commands. Depending on your motherboard, the interface may need to be 
 'lanplus', in this case, user has to modify script
 /usr/lib64/cloud/agent/scripts/util/ipmi.py
 replace all lines calling ipmi tool for example:
 o = ipmitool(-H, hostname, -U, usrname, -P, password, chassis, 
 power, status)
 to
 o = ipmitool(-H, hostname, ,-I, lanplus, -U, usrname, -P, password, 
 chassis, power, status)
 this issue will be addressed in next release.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4734) Creating snapshot from ROOT volume fails with error message - Failed to create snapshot due to an internal error creating snapshot for volume 14”


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4734:
---

Fix Version/s: (was: 4.2.1)
   4.3.0

 Creating snapshot from ROOT volume fails with error message - Failed to 
 create snapshot due to an internal error creating snapshot for volume 14”
 --

 Key: CLOUDSTACK-4734
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4734
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Doc, Management Server
Affects Versions: 4.2.1
 Environment: Build from 4.2-forward
Reporter: Sangeetha Hariharan
Assignee: Kelven Yang
 Fix For: 4.3.0

 Attachments: temp.rar


 Set up:
 3.0.7 Advanced Zone setup with 2 Zones having Vmware EXSI 5.0 clusters on 
 Vcenter 5.0 .
 Upgraded to 4.2.0.
 Tried to take snapshot for ROOT volume of 2 existing Vms from 2 different 
 zones.
 Snapshots got created successfully.
 After few hours , when I tried to create snapshot from ROOT volume for a VM, 
 I was not able to create snapshots from ROOT volume.
 I get the following error – “Error Code: 530 Error text: Failed to create 
 snapshot due to an internal error creating snapshot for volume
 14”
  
 Following is the error message seen on management server logs:
  
 2013-09-21 06:56:13,573 DEBUG [agent.transport.Request] 
 (Job-Executor-36:job-88 = [ c7cbee54-930d-4020-ae02-4710806
 bdc00 ]) Seq 9-1758069619: Sending  { Cmd , MgmtId: 161197867246747, via: 9, 
 Ver: v1, Flags: 100111, [{org.apache.
 cloudstack.storage.command.CopyCommand:{srcTO:{org.apache.cloudstack.storage.to.SnapshotObjectTO:{path:9e8a
 10cf-7cbc-4bef-a57b-563edb6b62ed,volume:{uuid:05a6bdfd-e6a5-4ae5-9dab-d06ee40776e9,volumeType:ROOT,data
 Store:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:61e1621f-a1a8-336d-b18d-050586f19b09,id:2
 00,poolType:NetworkFilesystem,host:10.223.110.232,path:/export/home/sangeetha/campofinalga/primary,por
 t:2049}},name:ROOT-14,size:2147483648,path:ROOT-14-14,volumeId:14,vmName:i-3-14-VM,accountId:3,
 format:OVA,id:14,hypervisorType:VMware},dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO
 :{uuid:61e1621f-a1a8-336d-b18d-050586f19b09,id:200,poolType:NetworkFilesystem,host:10.223.110.232,pa
 th:/export/home/sangeetha/campofinalga/primary,port:2049}},vmName:i-3-14-VM,name:sangee-tier1-4_ROOT-14
 _20130921135613,hypervisorType:VMware,id:5}},destTO:{org.apache.cloudstack.storage.to.SnapshotObjectTO:{
 path:snapshots/3/14,volume:{uuid:05a6bdfd-e6a5-4ae5-9dab-d06ee40776e9,volumeType:ROOT,dataStore:{o
 rg.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:61e1621f-a1a8-336d-b18d-050586f19b09,id:200,poolTy
 pe:NetworkFilesystem,host:10.223.110.232,path:/export/home/sangeetha/campofinalga/primary,port:2049}},
 name:ROOT-14,size:2147483648,path:ROOT-14-14,volumeId:14,vmName:i-3-14-VM,accountId:3,format:O
 VA,id:14,hypervisorType:VMware},dataStore:{com.cloud.agent.api.to.NfsTO:{_url:nfs://10.223.110.232/ex
 port/home/sangeetha/campofinalga/secondary,_role:Image}},vmName:i-3-14-VM,name:sangee-tier1-4_ROOT-14_2
 0130921135613,hypervisorType:VMware,id:5}},executeInSequence:true,wait:21600}}]
  }
  
 2013-09-21 06:56:18,263 DEBUG [agent.transport.Request] 
 (AgentManager-Handler-14:null) Seq 9-1758069619: Processing
 :  { Ans: , MgmtId: 161197867246747, via: 9, Ver: v1, Flags: 110, 
 [{org.apache.cloudstack.storage.command.CopyCmdA
 nswer:{result:false,details:backup snapshot exception: Exception: 
 javax.xml.ws.soap.SOAPFaultException\nMessa
 ge: \nRequired property obj is missing from data object of type 
 ObjectSpec\n\nwhile parsing serialized DataObject o
 f type vmodl.query.PropertyCollector.ObjectSpec\nat line 1, column 
 305\n\nwhile parsing property \objectSet\ of s
 tatic type ArrayOfObjectSpec\n\nwhile parsing serialized DataObject of type 
 vmodl.query.PropertyCollector.FilterSpe
 c\nat line 1, column 205\n\nwhile parsing call information for method 
 RetrieveProperties\nat line 1, column 110\n\n
 while parsing SOAP body\nat line 1, column 102\n\nwhile parsing SOAP 
 envelope\nat line 1, column 38\n\nwhile parsin
 g HTTP request for method retrieveContents\non object of type 
 vmodl.query.PropertyCollector\nat line 1, column 0\n
 ,wait:0}}] }
  
 2013-09-21 06:56:18,264 DEBUG [agent.transport.Request] 
 (Job-Executor-36:job-88 = [ c7cbee54-930d-4020-ae02-4710806
 bdc00 ]) Seq 9-1758069619: Received:  { Ans: , MgmtId: 161197867246747, via: 
 9, Ver: v1, Flags: 110, { CopyCmdAnswe
 r } }
 2013-09-21 06:56:18,270 DEBUG [agent.manager.AgentAttache] 
 (AgentManager-Handler-14:null) Seq 9-1758069619:

[jira] [Updated] (CLOUDSTACK-4717) can not have LB service in shared network with out having source NAT service enabled in the network


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4717:
---

Priority: Critical  (was: Major)

 can not have LB service in shared network with out having source NAT service 
 enabled in the network
 ---

 Key: CLOUDSTACK-4717
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4717
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.2.0
Reporter: Murali Reddy
Assignee: Murali Reddy
Priority: Critical
 Fix For: 4.2.1


 'shared network' with only DNS, DHCP and LB service provided by CloudStack is 
 a valid service combination. in this case gateway is defined externally and 
 cloudstack does not provide any nat service. But currently there is 
 restriction that in order to acquire an IP to a network source nat service 
 should have been enabled on the network. So effectively IP can not be 
 acquired and no LB rules can be created.
 Fix should be relax the restriction the source nat ip to enabled on the 
 network on which ip is being acquired.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4697) Not able to delete Primary storage when there are no hosts in the cluster.


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4697:
---

Fix Version/s: (was: 4.2.1)
   4.3.0

 Not able to delete Primary storage when there are no hosts in the cluster.
 --

 Key: CLOUDSTACK-4697
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4697
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.2.1
 Environment: Build from 4.2-forward
Reporter: Sangeetha Hariharan
 Fix For: 4.3.0


 Not able to delete Primary storage when there are no hosts in the cluster.
 Steps to reproduce the problem:
 I had 1 cluster with 1 cluster-wide primary storage and 1 host.
 Put the host is maintenance mode and deleted the host successfully.
 Put the primary storage in maintenance mode.
 Try to delete the primary storage.
 Primary storage deletion fails with Failed to delete storage pool on host.
 Tried with forced option set to true. Same issue is seen.
 Following is the exception seen in management server logs:
 http://10.223.240.160:8080/client/api?command=deleteStoragePoolid=6aa75bda-523e-3a70-876a-551889baf1fbforced=trueresponse=jsonsessionkey=w5yXStAmUJHVfEBV5vAYnmtnKeI%3D_=1379455061206
  
 2013-09-17 14:47:14,109 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null) 
 ===START===  10.215.3.9 -- GET  
 command=deleteStoragePoolid=6aa75bda-523e-3a70-8
 76a-551889baf1fbforced=trueresponse=jsonsessionkey=w5yXStAmUJHVfEBV5vAYnmtnKeI%3D_=1379455061206
 2013-09-17 14:47:14,121 ERROR [cloud.api.ApiServer] (catalina-exec-2:null) 
 unhandled exception executing api command: deleteStoragePool
 com.cloud.utils.exception.CloudRuntimeException: Failed to delete storage 
 pool on host
 at 
 org.apache.cloudstack.storage.datastore.lifecycle.CloudStackPrimaryDataStoreLifeCycleImpl.deleteDataStore(CloudStackPrimaryDataStoreLifeCycleImpl.
 java:478)
 at 
 com.cloud.storage.StorageManagerImpl.deletePool(StorageManagerImpl.java:937)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.api.command.admin.storage.DeletePoolCmd.execute(DeletePoolCmd.java:78)
 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-09-17 14:47:14,124 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null) 
 ===END===  10.215.3.9 -- GET  
 command=deleteStoragePoolid=6aa75bda-523e-3a70-876
 a-551889baf1fbforced=trueresponse=jsonsessionkey=w5yXStAmUJHVfEBV5vAYnmtnKeI%3D_=1379455061206
  
  



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4644) Tool Tip information is not provided for the new fields which are added in 4.2 ( Ex: Register Template , Compute Offering, Network Offering UI )


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4644:
---

Fix Version/s: (was: 4.2.1)
   4.3.0

 Tool Tip information is not provided for the new fields which are added in 
 4.2 ( Ex: Register Template , Compute Offering, Network Offering UI )
 

 Key: CLOUDSTACK-4644
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4644
 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: Sailaja Mada
Assignee: Brian Federle
 Fix For: 4.3.0


 Observation: 
 Tool Tip information is not provided for the new fields which are added in 
 4.2 ( Ex: Register Template , Compute Offering, Network Offering UI )
 1. Register Template UI  :
 New Fields are : Dynamically Scalable , Routing  - There is no quick info 
 provided for these 
 2. Create Compute Offering UI :  isVolatile , Deployment Planner, Planner 
 mode 
 3. Create Network Offering UI :  Persistent , Default egress policy 
 4. Add Affinity Groups  : Name, Description 
 5. Add Guest Network : Secondary Isolated VLAN ID:
 6. Add Region : id, name, end point 
 7. Configure LDAP : All the fields, Except query filter 



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (CLOUDSTACK-4670) [Baremetal] Cloudplatform BareMetal installation guide for CP 4.2