[jira] [Commented] (CLOUDSTACK-8265) table guest_os_hypervisor is missing newer os types, results in bad vms

2015-02-23 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-8265:
---

Hi,

You'd simply need to do this for KVM, VMware and LXC :
INSERT IGNORE INTO `cloud`.`guest_os_hypervisor` (uuid,hypervisor_type, 
hypervisor_version, guest_os_name, guest_os_id, created, is_user_defined) 
VALUES (UUID(),'VMware', 'vmware version supporting this OS', 'vmware name 
for the OS', 'id of OS in guest_os table', now(), 0);

INSERT IGNORE INTO `cloud`.`guest_os_hypervisor` (uuid,hypervisor_type, 
hypervisor_version, guest_os_name, guest_os_id, created, is_user_defined) 
VALUES (UUID(),'KVM', 'default', 'KVM name for the OS', 'id of OS in 
guest_os table', now(), 0);

INSERT IGNORE INTO `cloud`.`guest_os_hypervisor` (uuid,hypervisor_type, 
hypervisor_version, guest_os_name, guest_os_id, created, is_user_defined) 
VALUES (UUID(),'LXC', 'default', 'LXC name for the OS', 'id of OS in 
guest_os table', now(), 0);


 table guest_os_hypervisor is missing newer os types, results in bad vms
 ---

 Key: CLOUDSTACK-8265
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8265
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.5.0
Reporter: Marcus Sorensen
Assignee: Anthony Xu
Priority: Blocker
 Fix For: 4.5.0


 During testing of 4.5 I noticed that 1)Someone has added new OS types for 
 templates (e.g. Ubuntu 14.04), and 2) these are missing, at least for KVM, 
 from table guest_os_hypervisor, which results in suboptimal hardware 
 selection for these types.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (CLOUDSTACK-7975) Add RHEL 6.5 support

2014-11-26 Thread Amogh Vasekar (JIRA)
Amogh Vasekar created CLOUDSTACK-7975:
-

 Summary: Add RHEL 6.5 support
 Key: CLOUDSTACK-7975
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7975
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.5.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
 Fix For: 4.6.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-7975) Add RHEL 6.5 support

2014-11-26 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-7975:
---

Fixed in commit 3d6635a537ca33e6d8d2643c768e31742c001f99

 Add RHEL 6.5 support
 

 Key: CLOUDSTACK-7975
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7975
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.5.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
 Fix For: 4.6.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (CLOUDSTACK-7975) Add RHEL 6.5 support

2014-11-26 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-7975.
---
Resolution: Fixed

 Add RHEL 6.5 support
 

 Key: CLOUDSTACK-7975
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7975
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.5.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
 Fix For: 4.6.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (CLOUDSTACK-7976) Add validation for global params consoleproxy.url.domain and secstorage.cert.domain

2014-11-26 Thread Amogh Vasekar (JIRA)
Amogh Vasekar created CLOUDSTACK-7976:
-

 Summary: Add validation for global params consoleproxy.url.domain 
and secstorage.cert.domain
 Key: CLOUDSTACK-7976
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7976
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.5.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
 Fix For: 4.6.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (CLOUDSTACK-7976) Add validation for global params consoleproxy.url.domain and secstorage.cert.domain

2014-11-26 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-7976.
---
Resolution: Fixed

 Add validation for global params consoleproxy.url.domain and 
 secstorage.cert.domain
 ---

 Key: CLOUDSTACK-7976
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7976
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.5.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
 Fix For: 4.6.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-7976) Add validation for global params consoleproxy.url.domain and secstorage.cert.domain

2014-11-26 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-7976:
---

Parent commit 86895ec13c11bdf4dc1feab0a3dfa003e02fde12

 Add validation for global params consoleproxy.url.domain and 
 secstorage.cert.domain
 ---

 Key: CLOUDSTACK-7976
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7976
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.5.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
 Fix For: 4.6.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (CLOUDSTACK-7977) Password generator adds 3 characters to length. Should also have minimum length

2014-11-26 Thread Amogh Vasekar (JIRA)
Amogh Vasekar created CLOUDSTACK-7977:
-

 Summary: Password generator adds 3 characters to length. Should 
also have minimum length
 Key: CLOUDSTACK-7977
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7977
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server
Affects Versions: 4.5.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
 Fix For: 4.6.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (CLOUDSTACK-7977) Password generator adds 3 characters to length. Should also have minimum length

2014-11-26 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-7977.
---
Resolution: Fixed

 Password generator adds 3 characters to length. Should also have minimum 
 length
 ---

 Key: CLOUDSTACK-7977
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7977
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.5.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
 Fix For: 4.6.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-6358) Remove hardcoded guest OS mappings

2014-11-25 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-6358:
---

This shouldnt be back-ported to 4.3. It needs DB changes.
It was not a blocker from 4.3.x releases

 Remove hardcoded guest OS mappings
 --

 Key: CLOUDSTACK-6358
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6358
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Blocker
 Fix For: 4.5.0, 4.4.1


 The guest OS to platform emulator mappings are hardcoded in the codebase.
 This needs to be removed so as to support dynamic addition of guest OS type



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-6358) Remove hardcoded guest OS mappings

2014-11-25 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-6358:
---

Hi,

That actually came in because of the move to DB. Shouldn't need to be in 4.3 :-)

 Remove hardcoded guest OS mappings
 --

 Key: CLOUDSTACK-6358
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6358
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Blocker
 Fix For: 4.5.0, 4.4.1


 The guest OS to platform emulator mappings are hardcoded in the codebase.
 This needs to be removed so as to support dynamic addition of guest OS type



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-3607) guest_os_hypervisor table has values that are not registered in guest_os table

2014-11-18 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-3607:
---

Fixed already as a part of guest OS changes.

mysql  select * from guest_os_hypervisor where guest_os_id not in (select id 
from guest_os);
Empty set (0.01 sec)
The table is now used for guest OS mappings coming from DB rather than hardcoded

 guest_os_hypervisor table has values that are not registered in guest_os 
 table
 --

 Key: CLOUDSTACK-3607
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3607
 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: Amogh Vasekar
 Fix For: 4.4.0, 4.5.0


 mysql select * from guest_os_hypervisor where guest_os_id not in (select id 
 from guest_os);
 +-+-++-+
 | id  | hypervisor_type | guest_os_name  | guest_os_id |
 +-+-++-+
 | 128 | VmWare  | Red Hat Enterprise Linux 6(32-bit) | 204 |
 | 129 | VmWare  | Red Hat Enterprise Linux 6(64-bit) | 205 |
 +-+-++-+
 2 rows in set (0.07 sec)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (CLOUDSTACK-3607) guest_os_hypervisor table has values that are not registered in guest_os table

2014-11-18 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-3607.
---
Resolution: Fixed

 guest_os_hypervisor table has values that are not registered in guest_os 
 table
 --

 Key: CLOUDSTACK-3607
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3607
 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: Amogh Vasekar
 Fix For: 4.4.0, 4.5.0


 mysql select * from guest_os_hypervisor where guest_os_id not in (select id 
 from guest_os);
 +-+-++-+
 | id  | hypervisor_type | guest_os_name  | guest_os_id |
 +-+-++-+
 | 128 | VmWare  | Red Hat Enterprise Linux 6(32-bit) | 204 |
 | 129 | VmWare  | Red Hat Enterprise Linux 6(64-bit) | 205 |
 +-+-++-+
 2 rows in set (0.07 sec)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


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

2014-11-03 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-3608.
---
   Resolution: Fixed
Fix Version/s: (was: 4.4.0)

 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: Amogh Vasekar
 Fix For: 4.5.0


 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.3.4#6332)


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

2014-11-03 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-3608:
---

Issue - 
Below query may help to verify :
select * from (select hypervisor_type, hypervisor_version, guest_os_id, 
guest_os_name, count(id) as counted from guest_os_hypervisor group by 
hypervisor_type, hypervisor_version, guest_os_id) as a where a.counted  1;

+-++-+--+-+
| hypervisor_type | hypervisor_version | guest_os_id | guest_os_name | counted |
+-++-+--+-+
| KVM | default | 15 | Debian GNU/Linux 5 | 2 |
| KVM | default | 72 | Debian GNU/Linux 5 | 2 |
| KVM | default | 162 | Ubuntu 10.04 | 2 |
| LXC | default | 15 | Debian GNU/Linux 5 | 2 |
| LXC | default | 72 | Debian GNU/Linux 5 | 2 |
| LXC | default | 162 | Ubuntu 10.04 | 2 |
| VmWare | default | 59 | Ubuntu 10.10 (32-bit) | 2 |
| VmWare | default | 100 | Ubuntu 10.10 (64-bit) | 2 |
| VmWare | default | 165 | Windows 8 (32-bit) | 2 |
| VmWare | default | 166 | Windows 8 (64-bit) | 2 |
| VmWare | default | 167 | Windows Server 2012 (64-bit) | 2 |
| Xenserver | 6.2.5 | 168 | Windows Server 2012 (64-bit) | 2 |
| XenServer | default | 111 | CentOS 5.5 (32-bit) | 2 |
| XenServer | default | 112 | CentOS 5.5 (64-bit) | 2 |
| XenServer | default | 141 | CentOS 5.6 (32-bit) | 2 |
| XenServer | default | 142 | CentOS 5.6 (64-bit) | 2 |
| XenServer | default | 143 | CentOS 6.0 (32-bit) | 2 |
| XenServer | default | 144 | CentOS 6.0 (64-bit) | 2 |
| XenServer | default | 161 | CentOS 5.7 (32-bit) | 2 |
| XenServer | default | 162 | CentOS 5.7 (64-bit) | 2 |
| XenServer | default | 165 | Windows 8 (32-bit) | 2 |
| XenServer | default | 166 | Windows 8 (64-bit) | 2 |
| XenServer | default | 167 | Windows Server 2012 (64-bit) | 2 |
| XenServer | default | 171 | CentOS 6.3 (32-bit) | 2 |
| XenServer | default | 172 | CentOS 6.3 (64-bit) | 2 |
| XenServer | default | 173 | CentOS 5.8 (32-bit) | 2 |
| XenServer | default | 174 | CentOS 5.8 (64-bit) | 2 |
| XenServer | default | 175 | CentOS 5.9 (32-bit) | 2 |
| XenServer | default | 176 | CentOS 5.9 (64-bit) | 2 |
| XenServer | default | 177 | CentOS 6.1 (32-bit) | 2 |
| XenServer | default | 178 | CentOS 6.1 (64-bit) | 2 |
| XenServer | default | 179 | CentOS 6.2 (32-bit) | 2 |
| XenServer | default | 180 | CentOS 6.2 (64-bit) | 2 |
| XenServer | default | 181 | CentOS 6.4 (32-bit) | 2 |
| XenServer | default | 182 | CentOS 6.4 (64-bit) | 2 |
+-++-+--+-+

RCA - Old entries existed in guest_os_hypervisor table. Though it is harmless, 
better to remove duplicate entries

Solution - Remove duplicate system-defined entries from table, keep the ones 
with older ID


 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: Amogh Vasekar
 Fix For: 4.5.0


 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 |
 

[jira] [Resolved] (CLOUDSTACK-6915) Deleting dynamically added OS results in NPE for existing instances using that os type

2014-10-31 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-6915.
---
Resolution: Fixed

 Deleting dynamically added OS results in NPE for existing instances using 
 that os type
 --

 Key: CLOUDSTACK-6915
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6915
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Hypervisor Controller
Affects Versions: 4.4.0, 4.5.0
 Environment: XenServer host 
 Cloudstack 4.4 , VmWare host , CloudStack 4.5
Reporter: Pavan Kumar Bandarupally
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.4.0, 4.5.0

 Attachments: VmWareMSLog.log, management-server.log


 A guest OS is dynamically added and an instance is deployed successfully 
 using that os type (ISO used to deploy instance was of that OS type). The 
 custom os added was deleted using removeGuestOS. After this the instance is 
 stopped and started again.
 This start operation resulted in Null Pointer Exception.
 2014-06-16 06:50:33,350 ERROR [c.c.v.VirtualMachineManagerImpl] 
 (Work-Job-Executor-35:ctx-dd77fc16 job-86/job-87 ctx-331dc1d9) Failed to 
 start instance VM[User|i-2-12-VM]
 java.lang.NullPointerException
 at com.cloud.hypervisor.XenServerGuru.implement(XenServerGuru.java:93)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:995)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5180)
 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:606)
 at 
 com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5325)
 at 
 com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:744)
 2014-06-16 06:50:33,359 DEBUG [c.c.v.VirtualMachineManagerImpl] 
 (Work-Job-Executor-35:ctx-dd77fc16 job-86/job-87 ctx-331dc1d9) Cleaning up 
 resources for the vm VM[User|i-2-12-VM] in Starting state
 PFA MS log.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-6915) Deleting dynamically added OS results in NPE for existing instances using that os type

2014-10-31 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-6915:
---

Pushed to master and 4.5 via commits : efc9632c1b64a953a95943a1bbfa68fa1a8fdd6d 
and 0c153966e6269249fa38ab7859ab8352747e73f4 respectively.

 Deleting dynamically added OS results in NPE for existing instances using 
 that os type
 --

 Key: CLOUDSTACK-6915
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6915
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Hypervisor Controller
Affects Versions: 4.4.0, 4.5.0
 Environment: XenServer host 
 Cloudstack 4.4 , VmWare host , CloudStack 4.5
Reporter: Pavan Kumar Bandarupally
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.4.0, 4.5.0

 Attachments: VmWareMSLog.log, management-server.log


 A guest OS is dynamically added and an instance is deployed successfully 
 using that os type (ISO used to deploy instance was of that OS type). The 
 custom os added was deleted using removeGuestOS. After this the instance is 
 stopped and started again.
 This start operation resulted in Null Pointer Exception.
 2014-06-16 06:50:33,350 ERROR [c.c.v.VirtualMachineManagerImpl] 
 (Work-Job-Executor-35:ctx-dd77fc16 job-86/job-87 ctx-331dc1d9) Failed to 
 start instance VM[User|i-2-12-VM]
 java.lang.NullPointerException
 at com.cloud.hypervisor.XenServerGuru.implement(XenServerGuru.java:93)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:995)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5180)
 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:606)
 at 
 com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5325)
 at 
 com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:744)
 2014-06-16 06:50:33,359 DEBUG [c.c.v.VirtualMachineManagerImpl] 
 (Work-Job-Executor-35:ctx-dd77fc16 job-86/job-87 ctx-331dc1d9) Cleaning up 
 resources for the vm VM[User|i-2-12-VM] in Starting state
 PFA MS log.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-6915) Deleting dynamically added OS results in NPE for existing instances using that os type

2014-10-31 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-6915:
---

Issue : Deleting guest OS after an instance is launched off it, would make 
restarting the instance to fal

RCA : Guest OS search did not include removed OS IDs

Solution : Search including removed when searching by guest OS id.

 Deleting dynamically added OS results in NPE for existing instances using 
 that os type
 --

 Key: CLOUDSTACK-6915
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6915
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Hypervisor Controller
Affects Versions: 4.4.0, 4.5.0
 Environment: XenServer host 
 Cloudstack 4.4 , VmWare host , CloudStack 4.5
Reporter: Pavan Kumar Bandarupally
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.4.0, 4.5.0

 Attachments: VmWareMSLog.log, management-server.log


 A guest OS is dynamically added and an instance is deployed successfully 
 using that os type (ISO used to deploy instance was of that OS type). The 
 custom os added was deleted using removeGuestOS. After this the instance is 
 stopped and started again.
 This start operation resulted in Null Pointer Exception.
 2014-06-16 06:50:33,350 ERROR [c.c.v.VirtualMachineManagerImpl] 
 (Work-Job-Executor-35:ctx-dd77fc16 job-86/job-87 ctx-331dc1d9) Failed to 
 start instance VM[User|i-2-12-VM]
 java.lang.NullPointerException
 at com.cloud.hypervisor.XenServerGuru.implement(XenServerGuru.java:93)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:995)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5180)
 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:606)
 at 
 com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5325)
 at 
 com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:744)
 2014-06-16 06:50:33,359 DEBUG [c.c.v.VirtualMachineManagerImpl] 
 (Work-Job-Executor-35:ctx-dd77fc16 job-86/job-87 ctx-331dc1d9) Cleaning up 
 resources for the vm VM[User|i-2-12-VM] in Starting state
 PFA MS log.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CLOUDSTACK-7674) Upgrade to 4.3.1 did not update broadcast_uri in networks table for basic zone type

2014-10-06 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar updated CLOUDSTACK-7674:
--
Priority: Critical  (was: Major)

 Upgrade to 4.3.1 did not update broadcast_uri in networks table for basic 
 zone type
 ---

 Key: CLOUDSTACK-7674
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7674
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server, Upgrade
Affects Versions: 4.3.1
 Environment: CS Manager on Ubuntu 12.04 from standard repo
 Hosts: XenServer 6.0.2
 Zone: Basic
 Network Offering: DefaultSharedNetworkOffering
Reporter: Carlos Reategui
Priority: Critical

 In previous versions, the broadcast_uri in the Networks table was NULL for 
 Guest network in a Basic Zone with a network offering of 
 DefaultSharedNetworkOffering.  From 4.3.1 (maybe 4.3.0 too but not sure) it 
 can not be NULL and must be set to vlan://untagged.  The upgrade scripts do 
 not do this and therefore one is unable to create new instances.  
 I don't know if this affect other hypervisors besides XenServer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-7422) [Automation] Attach volume test case failing with error Invalid configuration for device '0'

2014-09-03 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-7422:
---

Hi,

I suspect this is a test case issue. I tried the following manually on VMware 
set-up and it worked :
1. Create 5 volumes of random sizes
2. Create VM using centos 5.3 template
3. Attach 5 volumes
4. Detach a few volumes
5. Re-attach volumes
6. Attach and then detach ISO, check contents of ISO for sanity.

 [Automation] Attach volume test case failing with error Invalid 
 configuration for device '0'
 --

 Key: CLOUDSTACK-7422
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7422
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Volumes
Affects Versions: 4.5.0
 Environment: Vmware 5.0
 build 4.5
Reporter: Rayees Namathponnan
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.5.0


 Steps to reproduce the defect 
 Run the test 
 integration.component.test_volumes.TestAttachVolumeISO.test_01_volume_iso_attach
 This test case performing below steps 
  678 # Validate the following
  679 # 1. Create and attach 5 data volumes to VM
  680 # 2. Create an ISO. Attach it to VM instance
  681 # 3. Verify that attach ISO is successful
 Here attach volume fails with below error 
 {noformat}
 a5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1ldAASTGphdmEvbGFuZy9TdHJpbmc7eHAAAgACAZh0ABRWb2x1
 bWVBcGlTZXJ2aWNlSW1wbHNyAA5qYXZhLmxhbmcuTG9uZzuL5JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAACnNxAH4ABgHJ
 , cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, 
 result: null, initMsid: 90928106758026, completeMsid: null, lastUpdated:
 null, lastPolled: null, created: Sat Aug 23 14:45:42 PDT 2014}, job 
 origin:3043
 com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume 
 TestDiskServ to VM TestVM-24cfe95b-8976-48af-ba42-459b37cfb89c; AttachV
 olumeCommand failed due to Exception: java.lang.RuntimeException
 Message: Invalid configuration for device '0'.
 at 
 com.cloud.storage.VolumeApiServiceImpl.sendAttachVolumeCommand(VolumeApiServiceImpl.java:2248)
 at 
 com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1216)
 at 
 com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:2615)
 at sun.reflect.GeneratedMethodAccessor855.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at 
 com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
 at 
 com.cloud.storage.VolumeApiServiceImpl.handleVmWorkJob(VolumeApiServiceImpl.java:2654)
 at sun.reflect.GeneratedMethodAccessor568.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at com.sun.proxy.$Proxy184.handleVmWorkJob(Unknown Source)
 at 
 com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 

[jira] [Resolved] (CLOUDSTACK-7356) CLONE - NPE XenServerGuru.java:95 when remove the nic from the vm in Stopped state

2014-08-18 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-7356.
---

Resolution: Fixed

 CLONE - NPE XenServerGuru.java:95 when remove the nic from the vm in Stopped 
 state
 --

 Key: CLOUDSTACK-7356
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7356
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.4.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.4.1

   Original Estimate: 72h
  Remaining Estimate: 72h

 Steps to reproduce:
 1) deploy vm with 1 network in Xen environment. Stop it
 2) attach nic to the stopped vm from another network
 3) Try to delete the nic. Following NPE happens:
 java.lang.NullPointerException
 at com.cloud.hypervisor.XenServerGuru.implement(XenServerGuru.java:95)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateRemoveNicFromVm(VirtualMachineManagerImpl.java:3554)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateRemoveNicFromVm(VirtualMachineManagerImpl.java:5280)
 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:606)
 at 
 com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5325)
 at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:744)



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Resolved] (CLOUDSTACK-7357) CLONE - Failed to stop VPC router with NPE

2014-08-18 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-7357.
---

Resolution: Fixed

 CLONE - Failed to stop VPC router with NPE
 --

 Key: CLOUDSTACK-7357
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7357
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Virtual Router
Affects Versions: 4.4.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Blocker
 Fix For: 4.4.1


 There are many VPC router stop cases failing in automation runs,
 VPC router stop fails with below  NPE
 2014-08-08 10:30:01,087 DEBUG [c.c.n.v.NetworkACLManagerImpl] 
 (AccountChecker-1:ctx-13aaf529) Applying NetworkACL for network: 369 with 
 Network ACL service provider
 2014-08-08 10:30:01,090 DEBUG [c.c.n.e.VpcVirtualRouterElement] 
 (AccountChecker-1:ctx-13aaf529) Virtual router elemnt doesn't need to apply 
 firewall rules on the backend; virtual router doesn't exist in the network 369
 2014-08-08 10:30:01,091 DEBUG [c.c.n.v.NetworkACLManagerImpl] 
 (AccountChecker-1:ctx-13aaf529) Successfully released Network ACLs for 
 network id=369 and # of rules now = 3
 2014-08-08 10:30:01,092 DEBUG [c.c.n.r.RulesManagerImpl] 
 (AccountChecker-1:ctx-13aaf529) Found 0 static nat rules to apply for network 
 id 369
 2014-08-08 10:30:01,098 DEBUG [c.c.n.e.VpcVirtualRouterElement] 
 (AccountChecker-1:ctx-13aaf529) VpcVirtualRouter element doesn't need to 
 associate ip addresses on the backend; VPC virtual router doesn't exist in 
 the network 369
 2014-08-08 10:30:01,099 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
 (AccountChecker-1:ctx-13aaf529) Sending network shutdown to VpcVirtualRouter
 2014-08-08 10:30:01,110 DEBUG [c.c.n.NetworkModelImpl] 
 (AccountChecker-1:ctx-13aaf529) Service SecurityGroup is not supported in the 
 network id=369
 2014-08-08 10:30:01,110 DEBUG [c.c.n.r.VpcVirtualNetworkApplianceManagerImpl] 
 (AccountChecker-1:ctx-13aaf529) Router r-320-VM is in Stopped, so not sending 
 setup guest network command to the backend
 2014-08-08 10:30:01,115 WARN  [o.a.c.e.o.NetworkOrchestrator] 
 (AccountChecker-1:ctx-13aaf529) Unable to complete shutdown of the network 
 elements due to element: VpcVirtualRouter
 java.lang.NullPointerException
 at com.cloud.hypervisor.KVMGuru.implement(KVMGuru.java:63)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateRemoveVmFromNetwork(VirtualMachineManagerImpl.java:3024)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.removeVmFromNetwork(VirtualMachineManagerImpl.java:3009)
 at 
 com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.removeVpcRouterFromGuestNetwork(VpcVirtualNetworkApplianceManagerImpl.java:321)
 at sun.reflect.GeneratedMethodAccessor280.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at com.sun.proxy.$Proxy189.removeVpcRouterFromGuestNetwork(Unknown 
 Source)
 at 
 com.cloud.network.element.VpcVirtualRouterElement.shutdown(VpcVirtualRouterElement.java:261)
 at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.shutdownNetworkElementsAndResources(NetworkOrchestrator.java:2142)
 at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.shutdownNetwork(NetworkOrchestrator.java:2044)
 at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.destroyNetwork(NetworkOrchestrator.java:2202)
 at 
 com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:793)
 at 
 com.cloud.user.AccountManagerImpl$AccountCleanupTask.runInContext(AccountManagerImpl.java:1675)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 

[jira] [Updated] (CLOUDSTACK-7356) CLONE - NPE XenServerGuru.java:95 when remove the nic from the vm in Stopped state

2014-08-15 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar updated CLOUDSTACK-7356:
--

Fix Version/s: (was: 4.5.0)
   4.4.1

 CLONE - NPE XenServerGuru.java:95 when remove the nic from the vm in Stopped 
 state
 --

 Key: CLOUDSTACK-7356
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7356
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.4.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.4.1

   Original Estimate: 72h
  Remaining Estimate: 72h

 Steps to reproduce:
 1) deploy vm with 1 network in Xen environment. Stop it
 2) attach nic to the stopped vm from another network
 3) Try to delete the nic. Following NPE happens:
 java.lang.NullPointerException
 at com.cloud.hypervisor.XenServerGuru.implement(XenServerGuru.java:95)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateRemoveNicFromVm(VirtualMachineManagerImpl.java:3554)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateRemoveNicFromVm(VirtualMachineManagerImpl.java:5280)
 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:606)
 at 
 com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5325)
 at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:744)



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Created] (CLOUDSTACK-7357) CLONE - [Automation] Failed to stop VPC router with NPE

2014-08-15 Thread Amogh Vasekar (JIRA)
Amogh Vasekar created CLOUDSTACK-7357:
-

 Summary: CLONE - [Automation] Failed to stop VPC router with NPE
 Key: CLOUDSTACK-7357
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7357
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Virtual Router
Affects Versions: 4.5.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Blocker
 Fix For: 4.5.0


There are many VPC router stop cases failing in automation runs,

VPC router stop fails with below  NPE

2014-08-08 10:30:01,087 DEBUG [c.c.n.v.NetworkACLManagerImpl] 
(AccountChecker-1:ctx-13aaf529) Applying NetworkACL for network: 369 with 
Network ACL service provider
2014-08-08 10:30:01,090 DEBUG [c.c.n.e.VpcVirtualRouterElement] 
(AccountChecker-1:ctx-13aaf529) Virtual router elemnt doesn't need to apply 
firewall rules on the backend; virtual router doesn't exist in the network 369
2014-08-08 10:30:01,091 DEBUG [c.c.n.v.NetworkACLManagerImpl] 
(AccountChecker-1:ctx-13aaf529) Successfully released Network ACLs for network 
id=369 and # of rules now = 3
2014-08-08 10:30:01,092 DEBUG [c.c.n.r.RulesManagerImpl] 
(AccountChecker-1:ctx-13aaf529) Found 0 static nat rules to apply for network 
id 369
2014-08-08 10:30:01,098 DEBUG [c.c.n.e.VpcVirtualRouterElement] 
(AccountChecker-1:ctx-13aaf529) VpcVirtualRouter element doesn't need to 
associate ip addresses on the backend; VPC virtual router doesn't exist in the 
network 369
2014-08-08 10:30:01,099 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(AccountChecker-1:ctx-13aaf529) Sending network shutdown to VpcVirtualRouter
2014-08-08 10:30:01,110 DEBUG [c.c.n.NetworkModelImpl] 
(AccountChecker-1:ctx-13aaf529) Service SecurityGroup is not supported in the 
network id=369
2014-08-08 10:30:01,110 DEBUG [c.c.n.r.VpcVirtualNetworkApplianceManagerImpl] 
(AccountChecker-1:ctx-13aaf529) Router r-320-VM is in Stopped, so not sending 
setup guest network command to the backend
2014-08-08 10:30:01,115 WARN  [o.a.c.e.o.NetworkOrchestrator] 
(AccountChecker-1:ctx-13aaf529) Unable to complete shutdown of the network 
elements due to element: VpcVirtualRouter
java.lang.NullPointerException
at com.cloud.hypervisor.KVMGuru.implement(KVMGuru.java:63)
at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateRemoveVmFromNetwork(VirtualMachineManagerImpl.java:3024)
at 
com.cloud.vm.VirtualMachineManagerImpl.removeVmFromNetwork(VirtualMachineManagerImpl.java:3009)
at 
com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.removeVpcRouterFromGuestNetwork(VpcVirtualNetworkApplianceManagerImpl.java:321)
at sun.reflect.GeneratedMethodAccessor280.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at 
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at 
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at com.sun.proxy.$Proxy189.removeVpcRouterFromGuestNetwork(Unknown 
Source)
at 
com.cloud.network.element.VpcVirtualRouterElement.shutdown(VpcVirtualRouterElement.java:261)

at 
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.shutdownNetworkElementsAndResources(NetworkOrchestrator.java:2142)
at 
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.shutdownNetwork(NetworkOrchestrator.java:2044)
at 
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.destroyNetwork(NetworkOrchestrator.java:2202)
at 
com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:793)
at 
com.cloud.user.AccountManagerImpl$AccountCleanupTask.runInContext(AccountManagerImpl.java:1675)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at 

[jira] [Updated] (CLOUDSTACK-7357) CLONE - [Automation] Failed to stop VPC router with NPE

2014-08-15 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar updated CLOUDSTACK-7357:
--

Fix Version/s: (was: 4.5.0)
   4.4.1

 CLONE - [Automation] Failed to stop VPC router with NPE
 ---

 Key: CLOUDSTACK-7357
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7357
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Virtual Router
Affects Versions: 4.4.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Blocker
 Fix For: 4.4.1


 There are many VPC router stop cases failing in automation runs,
 VPC router stop fails with below  NPE
 2014-08-08 10:30:01,087 DEBUG [c.c.n.v.NetworkACLManagerImpl] 
 (AccountChecker-1:ctx-13aaf529) Applying NetworkACL for network: 369 with 
 Network ACL service provider
 2014-08-08 10:30:01,090 DEBUG [c.c.n.e.VpcVirtualRouterElement] 
 (AccountChecker-1:ctx-13aaf529) Virtual router elemnt doesn't need to apply 
 firewall rules on the backend; virtual router doesn't exist in the network 369
 2014-08-08 10:30:01,091 DEBUG [c.c.n.v.NetworkACLManagerImpl] 
 (AccountChecker-1:ctx-13aaf529) Successfully released Network ACLs for 
 network id=369 and # of rules now = 3
 2014-08-08 10:30:01,092 DEBUG [c.c.n.r.RulesManagerImpl] 
 (AccountChecker-1:ctx-13aaf529) Found 0 static nat rules to apply for network 
 id 369
 2014-08-08 10:30:01,098 DEBUG [c.c.n.e.VpcVirtualRouterElement] 
 (AccountChecker-1:ctx-13aaf529) VpcVirtualRouter element doesn't need to 
 associate ip addresses on the backend; VPC virtual router doesn't exist in 
 the network 369
 2014-08-08 10:30:01,099 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
 (AccountChecker-1:ctx-13aaf529) Sending network shutdown to VpcVirtualRouter
 2014-08-08 10:30:01,110 DEBUG [c.c.n.NetworkModelImpl] 
 (AccountChecker-1:ctx-13aaf529) Service SecurityGroup is not supported in the 
 network id=369
 2014-08-08 10:30:01,110 DEBUG [c.c.n.r.VpcVirtualNetworkApplianceManagerImpl] 
 (AccountChecker-1:ctx-13aaf529) Router r-320-VM is in Stopped, so not sending 
 setup guest network command to the backend
 2014-08-08 10:30:01,115 WARN  [o.a.c.e.o.NetworkOrchestrator] 
 (AccountChecker-1:ctx-13aaf529) Unable to complete shutdown of the network 
 elements due to element: VpcVirtualRouter
 java.lang.NullPointerException
 at com.cloud.hypervisor.KVMGuru.implement(KVMGuru.java:63)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateRemoveVmFromNetwork(VirtualMachineManagerImpl.java:3024)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.removeVmFromNetwork(VirtualMachineManagerImpl.java:3009)
 at 
 com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.removeVpcRouterFromGuestNetwork(VpcVirtualNetworkApplianceManagerImpl.java:321)
 at sun.reflect.GeneratedMethodAccessor280.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at com.sun.proxy.$Proxy189.removeVpcRouterFromGuestNetwork(Unknown 
 Source)
 at 
 com.cloud.network.element.VpcVirtualRouterElement.shutdown(VpcVirtualRouterElement.java:261)
 at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.shutdownNetworkElementsAndResources(NetworkOrchestrator.java:2142)
 at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.shutdownNetwork(NetworkOrchestrator.java:2044)
 at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.destroyNetwork(NetworkOrchestrator.java:2202)
 at 
 com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:793)
 at 
 com.cloud.user.AccountManagerImpl$AccountCleanupTask.runInContext(AccountManagerImpl.java:1675)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 

[jira] [Resolved] (CLOUDSTACK-6905) NPE XenServerGuru.java:95 when remove the nic from the vm in Stopped state

2014-08-15 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-6905.
---

Resolution: Fixed

 NPE XenServerGuru.java:95 when remove the nic from the vm in Stopped state
 --

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

   Original Estimate: 72h
  Remaining Estimate: 72h

 Steps to reproduce:
 1) deploy vm with 1 network in Xen environment. Stop it
 2) attach nic to the stopped vm from another network
 3) Try to delete the nic. Following NPE happens:
 java.lang.NullPointerException
 at com.cloud.hypervisor.XenServerGuru.implement(XenServerGuru.java:95)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateRemoveNicFromVm(VirtualMachineManagerImpl.java:3554)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateRemoveNicFromVm(VirtualMachineManagerImpl.java:5280)
 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:606)
 at 
 com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5325)
 at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:744)



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Created] (CLOUDSTACK-7356) CLONE - NPE XenServerGuru.java:95 when remove the nic from the vm in Stopped state

2014-08-15 Thread Amogh Vasekar (JIRA)
Amogh Vasekar created CLOUDSTACK-7356:
-

 Summary: CLONE - NPE XenServerGuru.java:95 when remove the nic 
from the vm in Stopped state
 Key: CLOUDSTACK-7356
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7356
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.4.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.5.0


Steps to reproduce:

1) deploy vm with 1 network in Xen environment. Stop it
2) attach nic to the stopped vm from another network
3) Try to delete the nic. Following NPE happens:

java.lang.NullPointerException
at com.cloud.hypervisor.XenServerGuru.implement(XenServerGuru.java:95)
at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateRemoveNicFromVm(VirtualMachineManagerImpl.java:3554)
at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateRemoveNicFromVm(VirtualMachineManagerImpl.java:5280)
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:606)
at 
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at 
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5325)
at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (CLOUDSTACK-7357) CLONE - Failed to stop VPC router with NPE

2014-08-15 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar updated CLOUDSTACK-7357:
--

Summary: CLONE - Failed to stop VPC router with NPE  (was: CLONE - 
[Automation] Failed to stop VPC router with NPE)

 CLONE - Failed to stop VPC router with NPE
 --

 Key: CLOUDSTACK-7357
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7357
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Virtual Router
Affects Versions: 4.4.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Blocker
 Fix For: 4.4.1


 There are many VPC router stop cases failing in automation runs,
 VPC router stop fails with below  NPE
 2014-08-08 10:30:01,087 DEBUG [c.c.n.v.NetworkACLManagerImpl] 
 (AccountChecker-1:ctx-13aaf529) Applying NetworkACL for network: 369 with 
 Network ACL service provider
 2014-08-08 10:30:01,090 DEBUG [c.c.n.e.VpcVirtualRouterElement] 
 (AccountChecker-1:ctx-13aaf529) Virtual router elemnt doesn't need to apply 
 firewall rules on the backend; virtual router doesn't exist in the network 369
 2014-08-08 10:30:01,091 DEBUG [c.c.n.v.NetworkACLManagerImpl] 
 (AccountChecker-1:ctx-13aaf529) Successfully released Network ACLs for 
 network id=369 and # of rules now = 3
 2014-08-08 10:30:01,092 DEBUG [c.c.n.r.RulesManagerImpl] 
 (AccountChecker-1:ctx-13aaf529) Found 0 static nat rules to apply for network 
 id 369
 2014-08-08 10:30:01,098 DEBUG [c.c.n.e.VpcVirtualRouterElement] 
 (AccountChecker-1:ctx-13aaf529) VpcVirtualRouter element doesn't need to 
 associate ip addresses on the backend; VPC virtual router doesn't exist in 
 the network 369
 2014-08-08 10:30:01,099 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
 (AccountChecker-1:ctx-13aaf529) Sending network shutdown to VpcVirtualRouter
 2014-08-08 10:30:01,110 DEBUG [c.c.n.NetworkModelImpl] 
 (AccountChecker-1:ctx-13aaf529) Service SecurityGroup is not supported in the 
 network id=369
 2014-08-08 10:30:01,110 DEBUG [c.c.n.r.VpcVirtualNetworkApplianceManagerImpl] 
 (AccountChecker-1:ctx-13aaf529) Router r-320-VM is in Stopped, so not sending 
 setup guest network command to the backend
 2014-08-08 10:30:01,115 WARN  [o.a.c.e.o.NetworkOrchestrator] 
 (AccountChecker-1:ctx-13aaf529) Unable to complete shutdown of the network 
 elements due to element: VpcVirtualRouter
 java.lang.NullPointerException
 at com.cloud.hypervisor.KVMGuru.implement(KVMGuru.java:63)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateRemoveVmFromNetwork(VirtualMachineManagerImpl.java:3024)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.removeVmFromNetwork(VirtualMachineManagerImpl.java:3009)
 at 
 com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.removeVpcRouterFromGuestNetwork(VpcVirtualNetworkApplianceManagerImpl.java:321)
 at sun.reflect.GeneratedMethodAccessor280.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at com.sun.proxy.$Proxy189.removeVpcRouterFromGuestNetwork(Unknown 
 Source)
 at 
 com.cloud.network.element.VpcVirtualRouterElement.shutdown(VpcVirtualRouterElement.java:261)
 at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.shutdownNetworkElementsAndResources(NetworkOrchestrator.java:2142)
 at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.shutdownNetwork(NetworkOrchestrator.java:2044)
 at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.destroyNetwork(NetworkOrchestrator.java:2202)
 at 
 com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:793)
 at 
 com.cloud.user.AccountManagerImpl$AccountCleanupTask.runInContext(AccountManagerImpl.java:1675)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 

[jira] [Updated] (CLOUDSTACK-7357) CLONE - [Automation] Failed to stop VPC router with NPE

2014-08-15 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar updated CLOUDSTACK-7357:
--

Affects Version/s: (was: 4.5.0)
   4.4.0

 CLONE - [Automation] Failed to stop VPC router with NPE
 ---

 Key: CLOUDSTACK-7357
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7357
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Virtual Router
Affects Versions: 4.4.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Blocker
 Fix For: 4.4.1


 There are many VPC router stop cases failing in automation runs,
 VPC router stop fails with below  NPE
 2014-08-08 10:30:01,087 DEBUG [c.c.n.v.NetworkACLManagerImpl] 
 (AccountChecker-1:ctx-13aaf529) Applying NetworkACL for network: 369 with 
 Network ACL service provider
 2014-08-08 10:30:01,090 DEBUG [c.c.n.e.VpcVirtualRouterElement] 
 (AccountChecker-1:ctx-13aaf529) Virtual router elemnt doesn't need to apply 
 firewall rules on the backend; virtual router doesn't exist in the network 369
 2014-08-08 10:30:01,091 DEBUG [c.c.n.v.NetworkACLManagerImpl] 
 (AccountChecker-1:ctx-13aaf529) Successfully released Network ACLs for 
 network id=369 and # of rules now = 3
 2014-08-08 10:30:01,092 DEBUG [c.c.n.r.RulesManagerImpl] 
 (AccountChecker-1:ctx-13aaf529) Found 0 static nat rules to apply for network 
 id 369
 2014-08-08 10:30:01,098 DEBUG [c.c.n.e.VpcVirtualRouterElement] 
 (AccountChecker-1:ctx-13aaf529) VpcVirtualRouter element doesn't need to 
 associate ip addresses on the backend; VPC virtual router doesn't exist in 
 the network 369
 2014-08-08 10:30:01,099 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
 (AccountChecker-1:ctx-13aaf529) Sending network shutdown to VpcVirtualRouter
 2014-08-08 10:30:01,110 DEBUG [c.c.n.NetworkModelImpl] 
 (AccountChecker-1:ctx-13aaf529) Service SecurityGroup is not supported in the 
 network id=369
 2014-08-08 10:30:01,110 DEBUG [c.c.n.r.VpcVirtualNetworkApplianceManagerImpl] 
 (AccountChecker-1:ctx-13aaf529) Router r-320-VM is in Stopped, so not sending 
 setup guest network command to the backend
 2014-08-08 10:30:01,115 WARN  [o.a.c.e.o.NetworkOrchestrator] 
 (AccountChecker-1:ctx-13aaf529) Unable to complete shutdown of the network 
 elements due to element: VpcVirtualRouter
 java.lang.NullPointerException
 at com.cloud.hypervisor.KVMGuru.implement(KVMGuru.java:63)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateRemoveVmFromNetwork(VirtualMachineManagerImpl.java:3024)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.removeVmFromNetwork(VirtualMachineManagerImpl.java:3009)
 at 
 com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.removeVpcRouterFromGuestNetwork(VpcVirtualNetworkApplianceManagerImpl.java:321)
 at sun.reflect.GeneratedMethodAccessor280.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at com.sun.proxy.$Proxy189.removeVpcRouterFromGuestNetwork(Unknown 
 Source)
 at 
 com.cloud.network.element.VpcVirtualRouterElement.shutdown(VpcVirtualRouterElement.java:261)
 at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.shutdownNetworkElementsAndResources(NetworkOrchestrator.java:2142)
 at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.shutdownNetwork(NetworkOrchestrator.java:2044)
 at 
 org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.destroyNetwork(NetworkOrchestrator.java:2202)
 at 
 com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:793)
 at 
 com.cloud.user.AccountManagerImpl$AccountCleanupTask.runInContext(AccountManagerImpl.java:1675)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 

[jira] [Commented] (CLOUDSTACK-6905) NPE XenServerGuru.java:95 when remove the nic from the vm in Stopped state

2014-08-15 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-6905:
---

Should be resolved in commit d1d722f9bde91ce36f494142f4651a22c6795d6b

 NPE XenServerGuru.java:95 when remove the nic from the vm in Stopped state
 --

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

   Original Estimate: 72h
  Remaining Estimate: 72h

 Steps to reproduce:
 1) deploy vm with 1 network in Xen environment. Stop it
 2) attach nic to the stopped vm from another network
 3) Try to delete the nic. Following NPE happens:
 java.lang.NullPointerException
 at com.cloud.hypervisor.XenServerGuru.implement(XenServerGuru.java:95)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateRemoveNicFromVm(VirtualMachineManagerImpl.java:3554)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateRemoveNicFromVm(VirtualMachineManagerImpl.java:5280)
 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:606)
 at 
 com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5325)
 at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:744)



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Resolved] (CLOUDSTACK-6358) Remove hardcoded guest OS mappings

2014-08-07 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-6358.
---

Resolution: Fixed

 Remove hardcoded guest OS mappings
 --

 Key: CLOUDSTACK-6358
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6358
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Blocker
 Fix For: 4.5.0, 4.4.1


 The guest OS to platform emulator mappings are hardcoded in the codebase.
 This needs to be removed so as to support dynamic addition of guest OS type



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-6358) Remove hardcoded guest OS mappings

2014-08-07 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-6358:
---

Hi,

Yes, was waiting for the hotfix branch merge to be done. Will resolve it.

Thanks,
Amogh

 Remove hardcoded guest OS mappings
 --

 Key: CLOUDSTACK-6358
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6358
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Blocker
 Fix For: 4.5.0, 4.4.1


 The guest OS to platform emulator mappings are hardcoded in the codebase.
 This needs to be removed so as to support dynamic addition of guest OS type



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-6793) [Automation] CreateTagsCmd fails with db exceptions

2014-08-06 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-6793:
---

3. I will log a separate bug to track the changes related to effective 
implementation of getDomainid with out adding columns altogether. Will close 
this bug for now. 
Can you please let us know if there is a separate bug for this? You should be 
able to change DB in master now

 [Automation] CreateTagsCmd fails with db exceptions 
 

 Key: CLOUDSTACK-6793
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6793
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.4.0
 Environment: KVM 
Reporter: Rayees Namathponnan
Assignee: Santhosh Kumar Edukulla
Priority: Blocker
 Fix For: 4.4.0

 Attachments: management-server.rar


 Steps to reproduce 
 Execute the test case integration.component.test_tags.TestResourceTags
 Test case perform below steps 
 # 1. Create a tag on template/ISO using createTags API
 # 2. Delete above created tag using deleteTags API
 2014-05-27 17:41:28,658 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-10:ctx-3b66377c ctx-fdaf9174 ctx-62d4b9d2) ===END===
   10.223.240.193 -- GET  
 apiKey=x3l3u2QJMKK5AzForI9MKkjNWb4V2ewV-UY6qSPZERrS49jXwUFn5WLvN-r_QJZ-z1t-oO1g9F4-EiUZx9Bd
 EQresourcetype=TemplateresourceIds=35e10eef-7980-4085-8b6c-c68174f1b529command=createTagssignature=pIJSk7ekg0Tlf
 RN%2FWfdp8U42Bgs%3Dtags%5B0%5D.key=OSresponse=jsontags%5B0%5D.value=CentOS
 2014-05-27 17:41:28,661 DEBUG [c.c.u.d.T.Transaction] 
 (API-Job-Executor-89:ctx-c924058c job-577 ctx-ec2f3eb8) Rollin
 g back the transaction: Time = 4 Name =  API-Job-Executor-89; called by 
 -TransactionLegacy.rollback:903-TransactionL
 egacy.removeUpTo:846-TransactionLegacy.close:670-TransactionContextInterceptor.invoke:36-ReflectiveMethodInvocation.
 proceed:161-ExposeInvocationInterceptor.invoke:91-ReflectiveMethodInvocation.proceed:172-JdkDynamicAopProxy.invoke:2
 04-$Proxy52.persist:-1-TaggedResourceManagerImpl$1.doInTransactionWithoutResult:245-TransactionCallbackNoReturn.doIn
 Transaction:25-Transaction$2.doInTransaction:49
 2014-05-27 17:41:28,662 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-22:ctx-dbbc3135) ===START===  10.223.240.193 -- GET
  
 jobid=776d2770-db0d-44c8-b2e0-bbe2a9621642apiKey=x3l3u2QJMKK5AzForI9MKkjNWb4V2ewV-UY6qSPZERrS49jXwUFn5WLvN-r_QJZ-z
 1t-oO1g9F4-EiUZx9BdEQcommand=queryAsyncJobResultresponse=jsonsignature=%2Bk9OtkKpdJkU%2BWI7GO48SOrpKf4%3D
 2014-05-27 17:41:28,672 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (API-Job-Executor-89:ctx-c924058c job-577) Unexpected exception while 
 executing org.apache.cloudstack.api.command.user.tag.CreateTagsCmd
 com.cloud.utils.exception.CloudRuntimeException: DB Exception on: 
 com.mysql.jdbc.JDBC4PreparedStatement@6a7f6c5: INSERT INTO resource_tags 
 (resource_tags.uuid, resource_tags.key, resource_tags.value, 
 resource_tags.domain_id, resource_tags.account_id, resource_tags.resource_id, 
 resource_tags.resource_uuid, resource_tags.resource_type, 
 resource_tags.customer) VALUES 
 (_binary'46408de5-040c-4858-8323-881c358bda20', _binary'OS', _binary'CentOS', 
 -1, 82, 217, _binary'35e10eef-7980-4085-8b6c-c68174f1b529', 'Template', null)
 at com.cloud.utils.db.GenericDaoBase.persist(GenericDaoBase.java:1400)
 at sun.reflect.GeneratedMethodAccessor98.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 at 
 com.cloud.utils.db.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:34)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
 at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at com.sun.proxy.$Proxy52.persist(Unknown Source)
 at 
 

[jira] [Resolved] (CLOUDSTACK-7211) system VM not coming up in LXC zone for rhel 6.x

2014-08-05 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-7211.
---

Resolution: Fixed

 system VM  not coming up in LXC zone for rhel 6.x 
 --

 Key: CLOUDSTACK-7211
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7211
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: Amogh Vasekar
Priority: Blocker
 Fix For: 4.5.0

 Attachments: MS.tar.gz, agent.tar.gz


 created a zone with LXC hypervisor on rhel 6.3 host
 Pre seeded the KVM  template as LXC
 On enabling zone Syemt VMs are not coming up
 Agent log shows :
 ttempting to create storage pool dfa2ec3c-d133-3284-8583-0a0845aa4424 
 (NetworkFilesystem) in libvirt
 2014-07-31 04:56:50,260 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-1:null) Attempting to create storage pool 
 4032a858-88b0-3c03-8477-8984eb6b390b (NetworkFilesystem) in libvirt
 2014-07-31 04:56:50,417 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-1:null) Attempting to create volume 
 1c123c1a-1873-11e4-87de-4524e40b898e (NetworkFilesystem) in pool 
 dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144
 2014-07-31 04:57:14,052 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-1:null) Attempting to remove storage pool 
 4032a858-88b0-3c03-8477-8984eb6b390b from libvirt
 2014-07-31 04:57:14,388 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-2:null) Creating volume 
 75d88b46-1b93-4065-a348-460b8d3911fb from template 
 1c123c1a-1873-11e4-87de-4524e40b898e in pool 
 dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0
 2014-07-31 04:57:14,389 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-2:null) Attempting to create volume 
 75d88b46-1b93-4065-a348-460b8d3911fb (NetworkFilesystem) in pool 
 dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144
 2014-07-31 04:57:14,948 WARN  [cloud.agent.Agent] 
 (agentRequest-Handler-3:null) Caught:
 java.lang.NullPointerException
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332)
 at com.cloud.agent.Agent.processRequest(Agent.java:501)
 at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
 at com.cloud.utils.nio.Task.run(Task.java:84)
 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:722)
 2014-07-31 04:57:15,700 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-5:null) Creating volume 
 cac2c108-9f11-4ad7-981e-92a4a0bd05d4 from template 
 1c123c1a-1873-11e4-87de-4524e40b898e in pool 
 dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0
 2014-07-31 04:57:15,701 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-5:null) Attempting to create volume 
 cac2c108-9f11-4ad7-981e-92a4a0bd05d4 (NetworkFilesystem) in pool 
 dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144
 2014-07-31 04:57:16,262 WARN  [cloud.agent.Agent] 
 (agentRequest-Handler-1:null) Caught:
 java.lang.NullPointerException
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332)
 at com.cloud.agent.Agent.processRequest(Agent.java:501)
 at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
 at com.cloud.utils.nio.Task.run(Task.java:84)
 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:722)



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Created] (CLOUDSTACK-7257) CLONE - system VM not coming up in LXC zone for rhel 6.x

2014-08-05 Thread Amogh Vasekar (JIRA)
Amogh Vasekar created CLOUDSTACK-7257:
-

 Summary: CLONE - system VM  not coming up in LXC zone for rhel 6.x 
 Key: CLOUDSTACK-7257
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7257
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: KVM
Affects Versions: 4.5.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Blocker
 Fix For: 4.5.0


created a zone with LXC hypervisor on rhel 6.3 host
Pre seeded the KVM  template as LXC
On enabling zone Syemt VMs are not coming up



Agent log shows :
ttempting to create storage pool dfa2ec3c-d133-3284-8583-0a0845aa4424 
(NetworkFilesystem) in libvirt
2014-07-31 04:56:50,260 INFO  [kvm.storage.LibvirtStorageAdaptor] 
(agentRequest-Handler-1:null) Attempting to create storage pool 
4032a858-88b0-3c03-8477-8984eb6b390b (NetworkFilesystem) in libvirt
2014-07-31 04:56:50,417 INFO  [kvm.storage.LibvirtStorageAdaptor] 
(agentRequest-Handler-1:null) Attempting to create volume 
1c123c1a-1873-11e4-87de-4524e40b898e (NetworkFilesystem) in pool 
dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144
2014-07-31 04:57:14,052 INFO  [kvm.storage.LibvirtStorageAdaptor] 
(agentRequest-Handler-1:null) Attempting to remove storage pool 
4032a858-88b0-3c03-8477-8984eb6b390b from libvirt
2014-07-31 04:57:14,388 INFO  [kvm.storage.LibvirtStorageAdaptor] 
(agentRequest-Handler-2:null) Creating volume 
75d88b46-1b93-4065-a348-460b8d3911fb from template 
1c123c1a-1873-11e4-87de-4524e40b898e in pool 
dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0
2014-07-31 04:57:14,389 INFO  [kvm.storage.LibvirtStorageAdaptor] 
(agentRequest-Handler-2:null) Attempting to create volume 
75d88b46-1b93-4065-a348-460b8d3911fb (NetworkFilesystem) in pool 
dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144
2014-07-31 04:57:14,948 WARN  [cloud.agent.Agent] (agentRequest-Handler-3:null) 
Caught:
java.lang.NullPointerException
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332)
at com.cloud.agent.Agent.processRequest(Agent.java:501)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
at com.cloud.utils.nio.Task.run(Task.java:84)
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:722)
2014-07-31 04:57:15,700 INFO  [kvm.storage.LibvirtStorageAdaptor] 
(agentRequest-Handler-5:null) Creating volume 
cac2c108-9f11-4ad7-981e-92a4a0bd05d4 from template 
1c123c1a-1873-11e4-87de-4524e40b898e in pool 
dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0
2014-07-31 04:57:15,701 INFO  [kvm.storage.LibvirtStorageAdaptor] 
(agentRequest-Handler-5:null) Attempting to create volume 
cac2c108-9f11-4ad7-981e-92a4a0bd05d4 (NetworkFilesystem) in pool 
dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144
2014-07-31 04:57:16,262 WARN  [cloud.agent.Agent] (agentRequest-Handler-1:null) 
Caught:
java.lang.NullPointerException
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332)
at com.cloud.agent.Agent.processRequest(Agent.java:501)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
at com.cloud.utils.nio.Task.run(Task.java:84)
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:722)





--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (CLOUDSTACK-7257) CLONE - system VM not coming up in LXC zone for rhel 6.x

2014-08-05 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar updated CLOUDSTACK-7257:
--

Affects Version/s: (was: 4.5.0)
   4.4.0

 CLONE - system VM  not coming up in LXC zone for rhel 6.x 
 --

 Key: CLOUDSTACK-7257
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7257
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM
Affects Versions: 4.4.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Blocker
 Fix For: 4.4.1


 created a zone with LXC hypervisor on rhel 6.3 host
 Pre seeded the KVM  template as LXC
 On enabling zone Syemt VMs are not coming up
 Agent log shows :
 ttempting to create storage pool dfa2ec3c-d133-3284-8583-0a0845aa4424 
 (NetworkFilesystem) in libvirt
 2014-07-31 04:56:50,260 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-1:null) Attempting to create storage pool 
 4032a858-88b0-3c03-8477-8984eb6b390b (NetworkFilesystem) in libvirt
 2014-07-31 04:56:50,417 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-1:null) Attempting to create volume 
 1c123c1a-1873-11e4-87de-4524e40b898e (NetworkFilesystem) in pool 
 dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144
 2014-07-31 04:57:14,052 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-1:null) Attempting to remove storage pool 
 4032a858-88b0-3c03-8477-8984eb6b390b from libvirt
 2014-07-31 04:57:14,388 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-2:null) Creating volume 
 75d88b46-1b93-4065-a348-460b8d3911fb from template 
 1c123c1a-1873-11e4-87de-4524e40b898e in pool 
 dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0
 2014-07-31 04:57:14,389 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-2:null) Attempting to create volume 
 75d88b46-1b93-4065-a348-460b8d3911fb (NetworkFilesystem) in pool 
 dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144
 2014-07-31 04:57:14,948 WARN  [cloud.agent.Agent] 
 (agentRequest-Handler-3:null) Caught:
 java.lang.NullPointerException
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332)
 at com.cloud.agent.Agent.processRequest(Agent.java:501)
 at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
 at com.cloud.utils.nio.Task.run(Task.java:84)
 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:722)
 2014-07-31 04:57:15,700 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-5:null) Creating volume 
 cac2c108-9f11-4ad7-981e-92a4a0bd05d4 from template 
 1c123c1a-1873-11e4-87de-4524e40b898e in pool 
 dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0
 2014-07-31 04:57:15,701 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-5:null) Attempting to create volume 
 cac2c108-9f11-4ad7-981e-92a4a0bd05d4 (NetworkFilesystem) in pool 
 dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144
 2014-07-31 04:57:16,262 WARN  [cloud.agent.Agent] 
 (agentRequest-Handler-1:null) Caught:
 java.lang.NullPointerException
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332)
 at com.cloud.agent.Agent.processRequest(Agent.java:501)
 at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
 at com.cloud.utils.nio.Task.run(Task.java:84)
 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:722)



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (CLOUDSTACK-7257) CLONE - system VM not coming up in LXC zone for rhel 6.x

2014-08-05 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar updated CLOUDSTACK-7257:
--

Fix Version/s: (was: 4.5.0)
   4.4.1

 CLONE - system VM  not coming up in LXC zone for rhel 6.x 
 --

 Key: CLOUDSTACK-7257
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7257
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM
Affects Versions: 4.4.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Blocker
 Fix For: 4.4.1


 created a zone with LXC hypervisor on rhel 6.3 host
 Pre seeded the KVM  template as LXC
 On enabling zone Syemt VMs are not coming up
 Agent log shows :
 ttempting to create storage pool dfa2ec3c-d133-3284-8583-0a0845aa4424 
 (NetworkFilesystem) in libvirt
 2014-07-31 04:56:50,260 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-1:null) Attempting to create storage pool 
 4032a858-88b0-3c03-8477-8984eb6b390b (NetworkFilesystem) in libvirt
 2014-07-31 04:56:50,417 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-1:null) Attempting to create volume 
 1c123c1a-1873-11e4-87de-4524e40b898e (NetworkFilesystem) in pool 
 dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144
 2014-07-31 04:57:14,052 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-1:null) Attempting to remove storage pool 
 4032a858-88b0-3c03-8477-8984eb6b390b from libvirt
 2014-07-31 04:57:14,388 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-2:null) Creating volume 
 75d88b46-1b93-4065-a348-460b8d3911fb from template 
 1c123c1a-1873-11e4-87de-4524e40b898e in pool 
 dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0
 2014-07-31 04:57:14,389 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-2:null) Attempting to create volume 
 75d88b46-1b93-4065-a348-460b8d3911fb (NetworkFilesystem) in pool 
 dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144
 2014-07-31 04:57:14,948 WARN  [cloud.agent.Agent] 
 (agentRequest-Handler-3:null) Caught:
 java.lang.NullPointerException
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332)
 at com.cloud.agent.Agent.processRequest(Agent.java:501)
 at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
 at com.cloud.utils.nio.Task.run(Task.java:84)
 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:722)
 2014-07-31 04:57:15,700 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-5:null) Creating volume 
 cac2c108-9f11-4ad7-981e-92a4a0bd05d4 from template 
 1c123c1a-1873-11e4-87de-4524e40b898e in pool 
 dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0
 2014-07-31 04:57:15,701 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-5:null) Attempting to create volume 
 cac2c108-9f11-4ad7-981e-92a4a0bd05d4 (NetworkFilesystem) in pool 
 dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144
 2014-07-31 04:57:16,262 WARN  [cloud.agent.Agent] 
 (agentRequest-Handler-1:null) Caught:
 java.lang.NullPointerException
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332)
 at com.cloud.agent.Agent.processRequest(Agent.java:501)
 at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
 at com.cloud.utils.nio.Task.run(Task.java:84)
 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:722)



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Resolved] (CLOUDSTACK-7257) CLONE - system VM not coming up in LXC zone for rhel 6.x

2014-08-05 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-7257.
---

Resolution: Fixed

 CLONE - system VM  not coming up in LXC zone for rhel 6.x 
 --

 Key: CLOUDSTACK-7257
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7257
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM
Affects Versions: 4.4.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Blocker
 Fix For: 4.4.1


 created a zone with LXC hypervisor on rhel 6.3 host
 Pre seeded the KVM  template as LXC
 On enabling zone Syemt VMs are not coming up
 Agent log shows :
 ttempting to create storage pool dfa2ec3c-d133-3284-8583-0a0845aa4424 
 (NetworkFilesystem) in libvirt
 2014-07-31 04:56:50,260 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-1:null) Attempting to create storage pool 
 4032a858-88b0-3c03-8477-8984eb6b390b (NetworkFilesystem) in libvirt
 2014-07-31 04:56:50,417 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-1:null) Attempting to create volume 
 1c123c1a-1873-11e4-87de-4524e40b898e (NetworkFilesystem) in pool 
 dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144
 2014-07-31 04:57:14,052 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-1:null) Attempting to remove storage pool 
 4032a858-88b0-3c03-8477-8984eb6b390b from libvirt
 2014-07-31 04:57:14,388 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-2:null) Creating volume 
 75d88b46-1b93-4065-a348-460b8d3911fb from template 
 1c123c1a-1873-11e4-87de-4524e40b898e in pool 
 dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0
 2014-07-31 04:57:14,389 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-2:null) Attempting to create volume 
 75d88b46-1b93-4065-a348-460b8d3911fb (NetworkFilesystem) in pool 
 dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144
 2014-07-31 04:57:14,948 WARN  [cloud.agent.Agent] 
 (agentRequest-Handler-3:null) Caught:
 java.lang.NullPointerException
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332)
 at com.cloud.agent.Agent.processRequest(Agent.java:501)
 at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
 at com.cloud.utils.nio.Task.run(Task.java:84)
 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:722)
 2014-07-31 04:57:15,700 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-5:null) Creating volume 
 cac2c108-9f11-4ad7-981e-92a4a0bd05d4 from template 
 1c123c1a-1873-11e4-87de-4524e40b898e in pool 
 dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0
 2014-07-31 04:57:15,701 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-5:null) Attempting to create volume 
 cac2c108-9f11-4ad7-981e-92a4a0bd05d4 (NetworkFilesystem) in pool 
 dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144
 2014-07-31 04:57:16,262 WARN  [cloud.agent.Agent] 
 (agentRequest-Handler-1:null) Caught:
 java.lang.NullPointerException
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332)
 at com.cloud.agent.Agent.processRequest(Agent.java:501)
 at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
 at com.cloud.utils.nio.Task.run(Task.java:84)
 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:722)



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Created] (CLOUDSTACK-7259) KVM mappings for CentOS 6.x and RHEL 6.x

2014-08-05 Thread Amogh Vasekar (JIRA)
Amogh Vasekar created CLOUDSTACK-7259:
-

 Summary: KVM mappings for CentOS 6.x and RHEL 6.x
 Key: CLOUDSTACK-7259
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7259
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server
Affects Versions: 4.4.0, 4.5.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Blocker
 Fix For: 4.4.0, 4.5.0


Add missing KVM mappings for CentOS 6 and RHEL 6



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Resolved] (CLOUDSTACK-7259) KVM mappings for CentOS 6.x and RHEL 6.x

2014-08-05 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-7259.
---

Resolution: Fixed

 KVM mappings for CentOS 6.x and RHEL 6.x
 

 Key: CLOUDSTACK-7259
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7259
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.4.0, 4.5.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Blocker
 Fix For: 4.4.0, 4.5.0


 Add missing KVM mappings for CentOS 6 and RHEL 6



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-7259) KVM mappings for CentOS 6.x and RHEL 6.x

2014-08-05 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-7259:
---

Fixed in cfcc4a076dd740d6deed48084132946a55ed08d1 in master
Fixed in d3e0ecd130dbdd196e71be1eb32f92d4be6fdd2e in 4.4

Thanks
Amogh

 KVM mappings for CentOS 6.x and RHEL 6.x
 

 Key: CLOUDSTACK-7259
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7259
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.4.0, 4.5.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Blocker
 Fix For: 4.4.0, 4.5.0


 Add missing KVM mappings for CentOS 6 and RHEL 6



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-7211) system VM not coming up in LXC zone for rhel 6.x

2014-07-31 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-7211:
---

Hi,

I am assuming the hypervisor_type for LXC host is recorded as LXC. Is that 
correct? If yes, we would need to add the mappings to the guest_os_hypervisor 
table as well.
If it was sharing the mappings from KVMGuestOsMapper, we can copy all the KVM 
related mappings in the DB.

Thanks!

 system VM  not coming up in LXC zone for rhel 6.x 
 --

 Key: CLOUDSTACK-7211
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7211
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM
Affects Versions: 4.5.0
Reporter: shweta agarwal
Assignee: Rohit Yadav
Priority: Blocker
 Fix For: 4.5.0

 Attachments: MS.tar.gz, agent.tar.gz


 created a zone with LXC hypervisor on rhel 6.3 host
 Pre seeded the KVM  template as LXC
 On enabling zone Syemt VMs are not coming up
 Agent log shows :
 ttempting to create storage pool dfa2ec3c-d133-3284-8583-0a0845aa4424 
 (NetworkFilesystem) in libvirt
 2014-07-31 04:56:50,260 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-1:null) Attempting to create storage pool 
 4032a858-88b0-3c03-8477-8984eb6b390b (NetworkFilesystem) in libvirt
 2014-07-31 04:56:50,417 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-1:null) Attempting to create volume 
 1c123c1a-1873-11e4-87de-4524e40b898e (NetworkFilesystem) in pool 
 dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144
 2014-07-31 04:57:14,052 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-1:null) Attempting to remove storage pool 
 4032a858-88b0-3c03-8477-8984eb6b390b from libvirt
 2014-07-31 04:57:14,388 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-2:null) Creating volume 
 75d88b46-1b93-4065-a348-460b8d3911fb from template 
 1c123c1a-1873-11e4-87de-4524e40b898e in pool 
 dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0
 2014-07-31 04:57:14,389 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-2:null) Attempting to create volume 
 75d88b46-1b93-4065-a348-460b8d3911fb (NetworkFilesystem) in pool 
 dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144
 2014-07-31 04:57:14,948 WARN  [cloud.agent.Agent] 
 (agentRequest-Handler-3:null) Caught:
 java.lang.NullPointerException
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332)
 at com.cloud.agent.Agent.processRequest(Agent.java:501)
 at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
 at com.cloud.utils.nio.Task.run(Task.java:84)
 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:722)
 2014-07-31 04:57:15,700 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-5:null) Creating volume 
 cac2c108-9f11-4ad7-981e-92a4a0bd05d4 from template 
 1c123c1a-1873-11e4-87de-4524e40b898e in pool 
 dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0
 2014-07-31 04:57:15,701 INFO  [kvm.storage.LibvirtStorageAdaptor] 
 (agentRequest-Handler-5:null) Attempting to create volume 
 cac2c108-9f11-4ad7-981e-92a4a0bd05d4 (NetworkFilesystem) in pool 
 dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144
 2014-07-31 04:57:16,262 WARN  [cloud.agent.Agent] 
 (agentRequest-Handler-1:null) Caught:
 java.lang.NullPointerException
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766)
 at 
 com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332)
 at com.cloud.agent.Agent.processRequest(Agent.java:501)
 at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
 at com.cloud.utils.nio.Task.run(Task.java:84)
 at 
 

[jira] [Resolved] (CLOUDSTACK-6358) Remove hardcoded guest OS mappings

2014-07-15 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-6358.
---

Resolution: Fixed

 Remove hardcoded guest OS mappings
 --

 Key: CLOUDSTACK-6358
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6358
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.4.0, 4.5.0


 The guest OS to platform emulator mappings are hardcoded in the codebase.
 This needs to be removed so as to support dynamic addition of guest OS type



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Reopened] (CLOUDSTACK-6358) Remove hardcoded guest OS mappings

2014-07-14 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar reopened CLOUDSTACK-6358:
---


 Remove hardcoded guest OS mappings
 --

 Key: CLOUDSTACK-6358
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6358
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.4.0, 4.5.0


 The guest OS to platform emulator mappings are hardcoded in the codebase.
 This needs to be removed so as to support dynamic addition of guest OS type



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (CLOUDSTACK-6358) Remove hardcoded guest OS mappings

2014-07-14 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar updated CLOUDSTACK-6358:
--

Fix Version/s: 4.5.0

 Remove hardcoded guest OS mappings
 --

 Key: CLOUDSTACK-6358
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6358
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.4.0, 4.5.0


 The guest OS to platform emulator mappings are hardcoded in the codebase.
 This needs to be removed so as to support dynamic addition of guest OS type



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Reopened] (CLOUDSTACK-6671) Failed to start instance VM java.lang.NullPointerException at com.cloud.hypervisor.KVMGuru.implement(KVMGuru.java:64)

2014-07-14 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar reopened CLOUDSTACK-6671:
---


 Failed to start instance VM java.lang.NullPointerException at 
 com.cloud.hypervisor.KVMGuru.implement(KVMGuru.java:64)
 -

 Key: CLOUDSTACK-6671
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6671
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Install and Setup, KVM
Affects Versions: 4.4.0
 Environment: Ubuntu 14.04 / KVM / CS 4.4.0 snapshot 20140513 / 
 20140516
Reporter: Milamber
Assignee: Amogh Vasekar
Priority: Critical
  Labels: KVM
 Attachments: extract-management.log


 Unable to create VM on a fresh CS 4.4.0 installation (branch 4.4). 
 SSVM, Console proxy and first virtual routeur are correctly created and UP.
 10 day ago, this issue isn't present.
 In attachment, full log.
 2014-05-14 15:46:33,085 ERROR [c.c.v.VirtualMachineManagerImpl] 
 (Work-Job-Executor-6:job-25/job-27 ctx-57c7f749) Failed to start instance 
 VM[User|i-2-5-VM]
 java.lang.NullPointerException
   at com.cloud.hypervisor.KVMGuru.implement(KVMGuru.java:64)
   at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:995)
   at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5180)
   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:606)
   at 
 com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
   at 
 com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5325)
   at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
   at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:496)
   at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
   at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
   at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
   at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
   at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
   at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:453)
   at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
   at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
   at java.lang.Thread.run(Thread.java:744)



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Resolved] (CLOUDSTACK-6671) Failed to start instance VM java.lang.NullPointerException at com.cloud.hypervisor.KVMGuru.implement(KVMGuru.java:64)

2014-07-14 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-6671.
---

Resolution: Fixed

 Failed to start instance VM java.lang.NullPointerException at 
 com.cloud.hypervisor.KVMGuru.implement(KVMGuru.java:64)
 -

 Key: CLOUDSTACK-6671
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6671
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Install and Setup, KVM
Affects Versions: 4.4.0
 Environment: Ubuntu 14.04 / KVM / CS 4.4.0 snapshot 20140513 / 
 20140516
Reporter: Milamber
Assignee: Amogh Vasekar
Priority: Critical
  Labels: KVM
 Attachments: extract-management.log


 Unable to create VM on a fresh CS 4.4.0 installation (branch 4.4). 
 SSVM, Console proxy and first virtual routeur are correctly created and UP.
 10 day ago, this issue isn't present.
 In attachment, full log.
 2014-05-14 15:46:33,085 ERROR [c.c.v.VirtualMachineManagerImpl] 
 (Work-Job-Executor-6:job-25/job-27 ctx-57c7f749) Failed to start instance 
 VM[User|i-2-5-VM]
 java.lang.NullPointerException
   at com.cloud.hypervisor.KVMGuru.implement(KVMGuru.java:64)
   at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:995)
   at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5180)
   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:606)
   at 
 com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
   at 
 com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5325)
   at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
   at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:496)
   at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
   at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
   at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
   at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
   at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
   at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:453)
   at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
   at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
   at java.lang.Thread.run(Thread.java:744)



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Created] (CLOUDSTACK-7088) Snapshot manager should search for guest OS including deleted

2014-07-09 Thread Amogh Vasekar (JIRA)
Amogh Vasekar created CLOUDSTACK-7088:
-

 Summary: Snapshot manager should search for guest OS including 
deleted
 Key: CLOUDSTACK-7088
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7088
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server
Affects Versions: 4.4.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
 Fix For: 4.4.0, 4.5.0






--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-6516) Default value of secstorage.encrypt.copy overridden

2014-07-09 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-6516:
---

Fixed in 05802004e27f91f4c23274ca123f1ecf9fde5ac2

 Default value of secstorage.encrypt.copy overridden
 ---

 Key: CLOUDSTACK-6516
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6516
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.5.0

   Original Estimate: 24h
  Remaining Estimate: 24h

 In 4.3, SSL was turned off by default.
 However, for SSVM, the value from configuration server overrides the default 
 in Config.java. Work around is to change in global properties.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Resolved] (CLOUDSTACK-6516) Default value of secstorage.encrypt.copy overridden

2014-07-09 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-6516.
---

Resolution: Fixed

 Default value of secstorage.encrypt.copy overridden
 ---

 Key: CLOUDSTACK-6516
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6516
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.5.0

   Original Estimate: 24h
  Remaining Estimate: 24h

 In 4.3, SSL was turned off by default.
 However, for SSVM, the value from configuration server overrides the default 
 in Config.java. Work around is to change in global properties.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (CLOUDSTACK-6516) Default value of secstorage.encrypt.copy overridden

2014-07-07 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar updated CLOUDSTACK-6516:
--

Fix Version/s: (was: 4.4.0)
   4.5.0

 Default value of secstorage.encrypt.copy overridden
 ---

 Key: CLOUDSTACK-6516
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6516
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
 Fix For: 4.5.0


 In 4.3, SSL was turned off by default.
 However, for SSVM, the value from configuration server overrides the default 
 in Config.java. Work around is to change in global properties.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (CLOUDSTACK-6516) Default value of secstorage.encrypt.copy overridden

2014-07-07 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar updated CLOUDSTACK-6516:
--

Priority: Critical  (was: Major)

 Default value of secstorage.encrypt.copy overridden
 ---

 Key: CLOUDSTACK-6516
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6516
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.5.0


 In 4.3, SSL was turned off by default.
 However, for SSVM, the value from configuration server overrides the default 
 in Config.java. Work around is to change in global properties.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (CLOUDSTACK-6516) Default value of secstorage.encrypt.copy overridden

2014-07-07 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar updated CLOUDSTACK-6516:
--

Remaining Estimate: 24h
 Original Estimate: 24h

 Default value of secstorage.encrypt.copy overridden
 ---

 Key: CLOUDSTACK-6516
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6516
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.5.0

   Original Estimate: 24h
  Remaining Estimate: 24h

 In 4.3, SSL was turned off by default.
 However, for SSVM, the value from configuration server overrides the default 
 in Config.java. Work around is to change in global properties.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (CLOUDSTACK-6905) NPE XenServerGuru.java:95 when remove the nic from the vm in Stopped state

2014-07-07 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar updated CLOUDSTACK-6905:
--

Remaining Estimate: 72h
 Original Estimate: 72h

 NPE XenServerGuru.java:95 when remove the nic from the vm in Stopped state
 --

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

   Original Estimate: 72h
  Remaining Estimate: 72h

 Steps to reproduce:
 1) deploy vm with 1 network in Xen environment. Stop it
 2) attach nic to the stopped vm from another network
 3) Try to delete the nic. Following NPE happens:
 java.lang.NullPointerException
 at com.cloud.hypervisor.XenServerGuru.implement(XenServerGuru.java:95)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateRemoveNicFromVm(VirtualMachineManagerImpl.java:3554)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateRemoveNicFromVm(VirtualMachineManagerImpl.java:5280)
 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:606)
 at 
 com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5325)
 at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:744)



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Resolved] (CLOUDSTACK-6915) Deleting dynamically added OS results in NPE for existing instances using that os type

2014-06-17 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-6915.
---

Resolution: Fixed

 Deleting dynamically added OS results in NPE for existing instances using 
 that os type
 --

 Key: CLOUDSTACK-6915
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6915
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Hypervisor Controller
Affects Versions: 4.4.0
 Environment: XenServer host 
 Cloudstack 4.4 
Reporter: Pavan Kumar Bandarupally
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.4.0

 Attachments: management-server.log


 A guest OS is dynamically added and an instance is deployed successfully 
 using that os type (ISO used to deploy instance was of that OS type). The 
 custom os added was deleted using removeGuestOS. After this the instance is 
 stopped and started again.
 This start operation resulted in Null Pointer Exception.
 2014-06-16 06:50:33,350 ERROR [c.c.v.VirtualMachineManagerImpl] 
 (Work-Job-Executor-35:ctx-dd77fc16 job-86/job-87 ctx-331dc1d9) Failed to 
 start instance VM[User|i-2-12-VM]
 java.lang.NullPointerException
 at com.cloud.hypervisor.XenServerGuru.implement(XenServerGuru.java:93)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:995)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5180)
 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:606)
 at 
 com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5325)
 at 
 com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:744)
 2014-06-16 06:50:33,359 DEBUG [c.c.v.VirtualMachineManagerImpl] 
 (Work-Job-Executor-35:ctx-dd77fc16 job-86/job-87 ctx-331dc1d9) Cleaning up 
 resources for the vm VM[User|i-2-12-VM] in Starting state
 PFA MS log.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Resolved] (CLOUDSTACK-6737) NPE when deploying user VM using a guest OS which is removed.

2014-06-17 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-6737.
---

Resolution: Fixed

Fixed in CLOUDSTACK-6915

 NPE when deploying user VM using a guest OS which is removed.
 -

 Key: CLOUDSTACK-6737
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6737
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: XenServer
Affects Versions: 4.4.0
Reporter: manasaveloori
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.4.0

 Attachments: management-server.rar


 1. Add a guest Os.
 2. Adding mapping for the guest Os to hypervisor.
 3. Register ISO/template using the above added OS type.
 4. Now remove the guest OS 
 mysql select * from guest_os where display_name=testcentos;
 +-+-+--+--+--+-+-+-+
 | id  | category_id | name | uuid | 
 display_name | created | removed | is_user_defined |
 +-+-+--+--+--+-+-+-+
 | 231 |   1 | test | 01670dea-fa05-4046-a068-88032b9a83ed | 
 testcentos   | 2014-05-20 19:59:35 | 2014-05-21 15:18:18 |   1 |
 +-+-+--+--+--+-+-+-+
 1 row in set (0.00 sec)
 5. Now deploy user VM using the above registered ISO/template.
 Observed NPE:
 2014-05-21 12:22:03,824 DEBUG [c.c.n.NetworkModelImpl] 
 (catalina-exec-18:ctx-88f453ca ctx-f7949c50) Service SecurityGroup is not 
 supported in the network id=206
 2014-05-21 12:22:03,834 DEBUG [c.c.u.d.T.Transaction] 
 (catalina-exec-18:ctx-88f453ca ctx-f7949c50) Rolling back the transaction: 
 Time = 1 Name =  catalina-exec-18; called by 
 -TransactionLegacy.rollback:903-TransactionLegacy.removeUpTo:846-TransactionLegacy.close:670-Transaction.execute:41-UserVmManagerImpl.commitUserVm:2902-UserVmManagerImpl.createVirtualMachine:2840-UserVmManagerImpl.createAdvancedVirtualMachine:2543-NativeMethodAccessorImpl.invoke0:-2-NativeMethodAccessorImpl.invoke:57-DelegatingMethodAccessorImpl.invoke:43-Method.invoke:606-AopUtils.invokeJoinpointUsingReflection:317
 2014-05-21 12:22:03,841 ERROR [c.c.a.ApiServer] 
 (catalina-exec-18:ctx-88f453ca ctx-f7949c50) unhandled exception executing 
 api command: [Ljava.lang.String;@6e401408
 java.lang.NullPointerException
 at 
 com.cloud.vm.UserVmManagerImpl$3.doInTransaction(UserVmManagerImpl.java:2969)
 at 
 com.cloud.vm.UserVmManagerImpl$3.doInTransaction(UserVmManagerImpl.java:2902)
 at com.cloud.utils.db.Transaction.execute(Transaction.java:37)
 at 
 com.cloud.vm.UserVmManagerImpl.commitUserVm(UserVmManagerImpl.java:2902)
 at 
 com.cloud.vm.UserVmManagerImpl.createVirtualMachine(UserVmManagerImpl.java:2840)
 at 
 com.cloud.vm.UserVmManagerImpl.createAdvancedVirtualMachine(UserVmManagerImpl.java:2543)
 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:606)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 at 
 org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
 at 
 com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
 at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at com.sun.proxy.$Proxy206.createAdvancedVirtualMachine(Unknown 

[jira] [Assigned] (CLOUDSTACK-6896) Dynamically added OS Type throws NoSuchElement Exception on Xen

2014-06-12 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar reassigned CLOUDSTACK-6896:
-

Assignee: Amogh Vasekar  (was: Santhosh Kumar Edukulla)

 Dynamically added OS Type throws NoSuchElement Exception on Xen
 ---

 Key: CLOUDSTACK-6896
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6896
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Hypervisor Controller
Affects Versions: 4.4.0
 Environment: Managment Server: 4.4.0
 Host: XenServer Hypervisor 6.2
Reporter: Pavan Kumar Bandarupally
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.4.0

 Attachments: management-server.log


 A dynamically added OS is used as OS type for an ISO registered in 
 cloudstack. An instance deployed using that ISO doesn't get created throwing 
 an exception.
 MS Exception trace excerpt:
 = 
 2014-06-12 02:03:45,707 DEBUG [c.c.a.m.DirectAgentAttache] 
 (DirectAgent-281:ctx-c47880f2) Seq 1-5437252125119752015: Executing request
 2014-06-12 02:03:45,720 DEBUG [c.c.h.x.r.CitrixResourceBase] 
 (DirectAgent-281:ctx-c47880f2) 1. The VM i-2-8-VM is in Starting state.
 2014-06-12 02:03:45,723 WARN  [c.c.h.x.r.XenServer620Resource] 
 (DirectAgent-281:ctx-c47880f2) XenServer 6.2.0 DOES NOT support Guest OS type 
 centospavan
 2014-06-12 02:03:45,726 DEBUG [c.c.h.x.r.CitrixResourceBase] 
 (DirectAgent-281:ctx-c47880f2) Cannot find template : null on XS version: 
 com.cloud.hypervisor.xen.resource.XenServer620Resource
 2014-06-12 02:03:45,727 WARN  [c.c.h.x.r.CitrixResourceBase] 
 (DirectAgent-281:ctx-c47880f2) Catch Exception: class 
 java.util.NoSuchElementException due to java.util.NoSuchElementException
 java.util.NoSuchElementException
 at 
 java.util.LinkedHashMap$LinkedHashIterator.nextEntry(LinkedHashMap.java:396)
 at java.util.LinkedHashMap$KeyIterator.next(LinkedHashMap.java:405)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.createVmFromTemplate(CitrixResourceBase.java:1359)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1787)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:504)
 at 
 com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:61)
 at 
 com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:102)
 at 
 com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:293)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:744)
 2014-06-12 02:03:45,729 WARN  [c.c.h.x.r.CitrixResourceBase] 
 (DirectAgent-281:ctx-c47880f2) Unable to start i-2-8-VM due to
 java.util.NoSuchElementException
 at 
 java.util.LinkedHashMap$LinkedHashIterator.nextEntry(LinkedHashMap.java:396)
 at java.util.LinkedHashMap$KeyIterator.next(LinkedHashMap.java:405)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.createVmFromTemplate(CitrixResourceBase.java:1359)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1787)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:504)
 at 
 com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:61)
 at 
 

[jira] [Resolved] (CLOUDSTACK-6896) Dynamically added OS Type throws NoSuchElement Exception on Xen

2014-06-12 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-6896.
---

Resolution: Won't Fix

 Dynamically added OS Type throws NoSuchElement Exception on Xen
 ---

 Key: CLOUDSTACK-6896
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6896
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Hypervisor Controller
Affects Versions: 4.4.0
 Environment: Managment Server: 4.4.0
 Host: XenServer Hypervisor 6.2
Reporter: Pavan Kumar Bandarupally
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.4.0

 Attachments: management-server.log


 A dynamically added OS is used as OS type for an ISO registered in 
 cloudstack. An instance deployed using that ISO doesn't get created throwing 
 an exception.
 MS Exception trace excerpt:
 = 
 2014-06-12 02:03:45,707 DEBUG [c.c.a.m.DirectAgentAttache] 
 (DirectAgent-281:ctx-c47880f2) Seq 1-5437252125119752015: Executing request
 2014-06-12 02:03:45,720 DEBUG [c.c.h.x.r.CitrixResourceBase] 
 (DirectAgent-281:ctx-c47880f2) 1. The VM i-2-8-VM is in Starting state.
 2014-06-12 02:03:45,723 WARN  [c.c.h.x.r.XenServer620Resource] 
 (DirectAgent-281:ctx-c47880f2) XenServer 6.2.0 DOES NOT support Guest OS type 
 centospavan
 2014-06-12 02:03:45,726 DEBUG [c.c.h.x.r.CitrixResourceBase] 
 (DirectAgent-281:ctx-c47880f2) Cannot find template : null on XS version: 
 com.cloud.hypervisor.xen.resource.XenServer620Resource
 2014-06-12 02:03:45,727 WARN  [c.c.h.x.r.CitrixResourceBase] 
 (DirectAgent-281:ctx-c47880f2) Catch Exception: class 
 java.util.NoSuchElementException due to java.util.NoSuchElementException
 java.util.NoSuchElementException
 at 
 java.util.LinkedHashMap$LinkedHashIterator.nextEntry(LinkedHashMap.java:396)
 at java.util.LinkedHashMap$KeyIterator.next(LinkedHashMap.java:405)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.createVmFromTemplate(CitrixResourceBase.java:1359)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1787)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:504)
 at 
 com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:61)
 at 
 com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:102)
 at 
 com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:293)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:744)
 2014-06-12 02:03:45,729 WARN  [c.c.h.x.r.CitrixResourceBase] 
 (DirectAgent-281:ctx-c47880f2) Unable to start i-2-8-VM due to
 java.util.NoSuchElementException
 at 
 java.util.LinkedHashMap$LinkedHashIterator.nextEntry(LinkedHashMap.java:396)
 at java.util.LinkedHashMap$KeyIterator.next(LinkedHashMap.java:405)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.createVmFromTemplate(CitrixResourceBase.java:1359)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1787)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:504)
 at 
 com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:61)
 at 
 

[jira] [Commented] (CLOUDSTACK-6896) Dynamically added OS Type throws NoSuchElement Exception on Xen

2014-06-12 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-6896:
---

Hi,

This is by design - as mentioned in the functional spec at 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal+-+Ability+to+add+new+guest+OS+mappings
the admin will be responsible for providing the mapping to hypervisor-specific 
platform names based on his knowledge, which may be enhanced in future

Thanks!

 Dynamically added OS Type throws NoSuchElement Exception on Xen
 ---

 Key: CLOUDSTACK-6896
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6896
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Hypervisor Controller
Affects Versions: 4.4.0
 Environment: Managment Server: 4.4.0
 Host: XenServer Hypervisor 6.2
Reporter: Pavan Kumar Bandarupally
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.4.0

 Attachments: management-server.log


 A dynamically added OS is used as OS type for an ISO registered in 
 cloudstack. An instance deployed using that ISO doesn't get created throwing 
 an exception.
 MS Exception trace excerpt:
 = 
 2014-06-12 02:03:45,707 DEBUG [c.c.a.m.DirectAgentAttache] 
 (DirectAgent-281:ctx-c47880f2) Seq 1-5437252125119752015: Executing request
 2014-06-12 02:03:45,720 DEBUG [c.c.h.x.r.CitrixResourceBase] 
 (DirectAgent-281:ctx-c47880f2) 1. The VM i-2-8-VM is in Starting state.
 2014-06-12 02:03:45,723 WARN  [c.c.h.x.r.XenServer620Resource] 
 (DirectAgent-281:ctx-c47880f2) XenServer 6.2.0 DOES NOT support Guest OS type 
 centospavan
 2014-06-12 02:03:45,726 DEBUG [c.c.h.x.r.CitrixResourceBase] 
 (DirectAgent-281:ctx-c47880f2) Cannot find template : null on XS version: 
 com.cloud.hypervisor.xen.resource.XenServer620Resource
 2014-06-12 02:03:45,727 WARN  [c.c.h.x.r.CitrixResourceBase] 
 (DirectAgent-281:ctx-c47880f2) Catch Exception: class 
 java.util.NoSuchElementException due to java.util.NoSuchElementException
 java.util.NoSuchElementException
 at 
 java.util.LinkedHashMap$LinkedHashIterator.nextEntry(LinkedHashMap.java:396)
 at java.util.LinkedHashMap$KeyIterator.next(LinkedHashMap.java:405)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.createVmFromTemplate(CitrixResourceBase.java:1359)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1787)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:504)
 at 
 com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:61)
 at 
 com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:102)
 at 
 com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:293)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:744)
 2014-06-12 02:03:45,729 WARN  [c.c.h.x.r.CitrixResourceBase] 
 (DirectAgent-281:ctx-c47880f2) Unable to start i-2-8-VM due to
 java.util.NoSuchElementException
 at 
 java.util.LinkedHashMap$LinkedHashIterator.nextEntry(LinkedHashMap.java:396)
 at java.util.LinkedHashMap$KeyIterator.next(LinkedHashMap.java:405)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.createVmFromTemplate(CitrixResourceBase.java:1359)
 at 
 

[jira] [Resolved] (CLOUDSTACK-6710) [Automation] VM snapshot failing with NPE in vmware

2014-06-10 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-6710.
---

Resolution: Fixed

 [Automation] VM snapshot failing with NPE in vmware
 ---

 Key: CLOUDSTACK-6710
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6710
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.4.0
 Environment: Vmware 5.0
 4.4-forward 
Reporter: Rayees Namathponnan
Assignee: Amogh Vasekar
Priority: Blocker
 Fix For: 4.4.0

 Attachments: management-server.rar


 Execute BVT 
 integration.smoke.test_vm_snapshots.TestVmSnapshot.test_01_create_vm_snapshots
 This test case creating VM snapshot in VMware; this is failing with below NPE 
 2014-05-19 13:12:00,378 DEBUG [c.c.v.VmWorkJobDispatcher] 
 (Work-Job-Executor-130:job-390/job-391) Run VM work job: 
 com.cloud.vm.snapshot.VmWorkCreateVMSn
 apshot for VM 62, job origin: 390
 2014-05-19 13:12:00,384 DEBUG [c.c.v.VmWorkJobHandlerProxy] 
 (Work-Job-Executor-130:job-390/job-391 ctx-538be870) Execute VM work job: 
 com.cloud.vm.snapsh
 ot.VmWorkCreateVMSnapshot{vmSnapshotId:1,quiesceVm:false,userId:2,accountId:2,vmId:62,handlerName:VMSnapshotManagerImpl}
 2014-05-19 13:12:00,517 DEBUG [c.c.v.s.VMSnapshotManagerImpl] 
 (Work-Job-Executor-130:job-390/job-391 ctx-538be870) Failed to create vm 
 snapshot: 1
 java.lang.NullPointerException
 at 
 org.apache.cloudstack.storage.vmsnapshot.DefaultVMSnapshotStrategy.takeVMSnapshot(DefaultVMSnapshotStrategy.java:139)
 at 
 com.cloud.vm.snapshot.VMSnapshotManagerImpl.orchestrateCreateVMSnapshot(VMSnapshotManagerImpl.java:422)
 at 
 com.cloud.vm.snapshot.VMSnapshotManagerImpl.orchestrateCreateVMSnapshot(VMSnapshotManagerImpl.java:1048)
 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:606)
 at 
 com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
 at 
 com.cloud.vm.snapshot.VMSnapshotManagerImpl.handleVmWorkJob(VMSnapshotManagerImpl.java:1072)
 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:606)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at com.sun.proxy.$Proxy182.handleVmWorkJob(Unknown Source)
 at 
 com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:496)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:453)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at 

[jira] [Resolved] (CLOUDSTACK-6358) Remove hardcoded guest OS mappings

2014-06-10 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-6358.
---

Resolution: Fixed

 Remove hardcoded guest OS mappings
 --

 Key: CLOUDSTACK-6358
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6358
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.4.0


 The guest OS to platform emulator mappings are hardcoded in the codebase.
 This needs to be removed so as to support dynamic addition of guest OS type



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-6793) [Automation] CreateTagsCmd fails with db exceptions

2014-06-06 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-6793:
---

Hi Santhosh,

If we are planning on adding the column in future release, why not address it 
now itself? I think the column was missing due to legacy reasons rather than by 
choice.
Additionally, I don't think a VO is allowed to refer to another VO / DAO in the 
current semantics, if I understood the point wrt changing interface for 
getDomainId.
As far as making use of proper relational mapping goes - the same holds true 
for other objects like Volume, VMInstance etc. Seems the reason to store it is 
avoiding search on account-domain relationship for every call.

Thanks,
Amogh

 [Automation] CreateTagsCmd fails with db exceptions 
 

 Key: CLOUDSTACK-6793
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6793
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.4.0
 Environment: KVM 
Reporter: Rayees Namathponnan
Assignee: Santhosh Kumar Edukulla
Priority: Blocker
 Fix For: 4.4.0

 Attachments: management-server.rar


 Steps to reproduce 
 Execute the test case integration.component.test_tags.TestResourceTags
 Test case perform below steps 
 # 1. Create a tag on template/ISO using createTags API
 # 2. Delete above created tag using deleteTags API
 2014-05-27 17:41:28,658 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-10:ctx-3b66377c ctx-fdaf9174 ctx-62d4b9d2) ===END===
   10.223.240.193 -- GET  
 apiKey=x3l3u2QJMKK5AzForI9MKkjNWb4V2ewV-UY6qSPZERrS49jXwUFn5WLvN-r_QJZ-z1t-oO1g9F4-EiUZx9Bd
 EQresourcetype=TemplateresourceIds=35e10eef-7980-4085-8b6c-c68174f1b529command=createTagssignature=pIJSk7ekg0Tlf
 RN%2FWfdp8U42Bgs%3Dtags%5B0%5D.key=OSresponse=jsontags%5B0%5D.value=CentOS
 2014-05-27 17:41:28,661 DEBUG [c.c.u.d.T.Transaction] 
 (API-Job-Executor-89:ctx-c924058c job-577 ctx-ec2f3eb8) Rollin
 g back the transaction: Time = 4 Name =  API-Job-Executor-89; called by 
 -TransactionLegacy.rollback:903-TransactionL
 egacy.removeUpTo:846-TransactionLegacy.close:670-TransactionContextInterceptor.invoke:36-ReflectiveMethodInvocation.
 proceed:161-ExposeInvocationInterceptor.invoke:91-ReflectiveMethodInvocation.proceed:172-JdkDynamicAopProxy.invoke:2
 04-$Proxy52.persist:-1-TaggedResourceManagerImpl$1.doInTransactionWithoutResult:245-TransactionCallbackNoReturn.doIn
 Transaction:25-Transaction$2.doInTransaction:49
 2014-05-27 17:41:28,662 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-22:ctx-dbbc3135) ===START===  10.223.240.193 -- GET
  
 jobid=776d2770-db0d-44c8-b2e0-bbe2a9621642apiKey=x3l3u2QJMKK5AzForI9MKkjNWb4V2ewV-UY6qSPZERrS49jXwUFn5WLvN-r_QJZ-z
 1t-oO1g9F4-EiUZx9BdEQcommand=queryAsyncJobResultresponse=jsonsignature=%2Bk9OtkKpdJkU%2BWI7GO48SOrpKf4%3D
 2014-05-27 17:41:28,672 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (API-Job-Executor-89:ctx-c924058c job-577) Unexpected exception while 
 executing org.apache.cloudstack.api.command.user.tag.CreateTagsCmd
 com.cloud.utils.exception.CloudRuntimeException: DB Exception on: 
 com.mysql.jdbc.JDBC4PreparedStatement@6a7f6c5: INSERT INTO resource_tags 
 (resource_tags.uuid, resource_tags.key, resource_tags.value, 
 resource_tags.domain_id, resource_tags.account_id, resource_tags.resource_id, 
 resource_tags.resource_uuid, resource_tags.resource_type, 
 resource_tags.customer) VALUES 
 (_binary'46408de5-040c-4858-8323-881c358bda20', _binary'OS', _binary'CentOS', 
 -1, 82, 217, _binary'35e10eef-7980-4085-8b6c-c68174f1b529', 'Template', null)
 at com.cloud.utils.db.GenericDaoBase.persist(GenericDaoBase.java:1400)
 at sun.reflect.GeneratedMethodAccessor98.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 at 
 com.cloud.utils.db.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:34)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
 at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
 at 
 

[jira] [Commented] (CLOUDSTACK-6710) [Automation] VM snapshot failing with NPE in vmware

2014-06-05 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-6710:
---

Hi,
I'm on it, will make the commit soon.

Thanks,
Amogh

 [Automation] VM snapshot failing with NPE in vmware
 ---

 Key: CLOUDSTACK-6710
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6710
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.4.0
 Environment: Vmware 5.0
 4.4-forward 
Reporter: Rayees Namathponnan
Assignee: Amogh Vasekar
Priority: Blocker
 Fix For: 4.4.0

 Attachments: management-server.rar


 Execute BVT 
 integration.smoke.test_vm_snapshots.TestVmSnapshot.test_01_create_vm_snapshots
 This test case creating VM snapshot in VMware; this is failing with below NPE 
 2014-05-19 13:12:00,378 DEBUG [c.c.v.VmWorkJobDispatcher] 
 (Work-Job-Executor-130:job-390/job-391) Run VM work job: 
 com.cloud.vm.snapshot.VmWorkCreateVMSn
 apshot for VM 62, job origin: 390
 2014-05-19 13:12:00,384 DEBUG [c.c.v.VmWorkJobHandlerProxy] 
 (Work-Job-Executor-130:job-390/job-391 ctx-538be870) Execute VM work job: 
 com.cloud.vm.snapsh
 ot.VmWorkCreateVMSnapshot{vmSnapshotId:1,quiesceVm:false,userId:2,accountId:2,vmId:62,handlerName:VMSnapshotManagerImpl}
 2014-05-19 13:12:00,517 DEBUG [c.c.v.s.VMSnapshotManagerImpl] 
 (Work-Job-Executor-130:job-390/job-391 ctx-538be870) Failed to create vm 
 snapshot: 1
 java.lang.NullPointerException
 at 
 org.apache.cloudstack.storage.vmsnapshot.DefaultVMSnapshotStrategy.takeVMSnapshot(DefaultVMSnapshotStrategy.java:139)
 at 
 com.cloud.vm.snapshot.VMSnapshotManagerImpl.orchestrateCreateVMSnapshot(VMSnapshotManagerImpl.java:422)
 at 
 com.cloud.vm.snapshot.VMSnapshotManagerImpl.orchestrateCreateVMSnapshot(VMSnapshotManagerImpl.java:1048)
 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:606)
 at 
 com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
 at 
 com.cloud.vm.snapshot.VMSnapshotManagerImpl.handleVmWorkJob(VMSnapshotManagerImpl.java:1072)
 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:606)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at com.sun.proxy.$Proxy182.handleVmWorkJob(Unknown Source)
 at 
 com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:496)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:453)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 

[jira] [Commented] (CLOUDSTACK-6793) [Automation] CreateTagsCmd fails with db exceptions

2014-06-05 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-6793:
---

Hi,

The commit that exposed this bug is : 68b8891c620e78009ec4dbcbd326e4bbfa79da4e
In essence, vm_template table does not store the domain_id. Previously, the 
following fragment of code masked this issue :
if (domainId == null) {
domainId = Domain.ROOT_DOMAIN;
}
This seems incorrect too, since a tag on ISO / Template registered by user not 
in ROOT domain, would be recorded in resource_tags table as belonging to root 
domain.

mysql select id, account_name, domain_id from account;
++--+---+
| id | account_name | domain_id |
++--+---+
|  2 | admin| 1 |
|  1 | system   | 1 |
|  3 | test | 2 |
++--+---+

mysql select id, resource_tags.key, resource_tags.value, resource_id, 
resource_type, account_id, domain_id from resource_tags;
++--+---+-+---++---+
| id | key  | value | resource_id | resource_type | account_id | domain_id |
++--+---+-+---++---+
|  1 | test | test  | 202 | ISO   |  3 | 1 |
++--+---+-+---++---+

The domain_id is 1, even though the account has domain id 2

 [Automation] CreateTagsCmd fails with db exceptions 
 

 Key: CLOUDSTACK-6793
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6793
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.4.0
 Environment: KVM 
Reporter: Rayees Namathponnan
Assignee: Santhosh Kumar Edukulla
Priority: Blocker
 Fix For: 4.4.0

 Attachments: management-server.rar


 Steps to reproduce 
 Execute the test case integration.component.test_tags.TestResourceTags
 Test case perform below steps 
 # 1. Create a tag on template/ISO using createTags API
 # 2. Delete above created tag using deleteTags API
 2014-05-27 17:41:28,658 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-10:ctx-3b66377c ctx-fdaf9174 ctx-62d4b9d2) ===END===
   10.223.240.193 -- GET  
 apiKey=x3l3u2QJMKK5AzForI9MKkjNWb4V2ewV-UY6qSPZERrS49jXwUFn5WLvN-r_QJZ-z1t-oO1g9F4-EiUZx9Bd
 EQresourcetype=TemplateresourceIds=35e10eef-7980-4085-8b6c-c68174f1b529command=createTagssignature=pIJSk7ekg0Tlf
 RN%2FWfdp8U42Bgs%3Dtags%5B0%5D.key=OSresponse=jsontags%5B0%5D.value=CentOS
 2014-05-27 17:41:28,661 DEBUG [c.c.u.d.T.Transaction] 
 (API-Job-Executor-89:ctx-c924058c job-577 ctx-ec2f3eb8) Rollin
 g back the transaction: Time = 4 Name =  API-Job-Executor-89; called by 
 -TransactionLegacy.rollback:903-TransactionL
 egacy.removeUpTo:846-TransactionLegacy.close:670-TransactionContextInterceptor.invoke:36-ReflectiveMethodInvocation.
 proceed:161-ExposeInvocationInterceptor.invoke:91-ReflectiveMethodInvocation.proceed:172-JdkDynamicAopProxy.invoke:2
 04-$Proxy52.persist:-1-TaggedResourceManagerImpl$1.doInTransactionWithoutResult:245-TransactionCallbackNoReturn.doIn
 Transaction:25-Transaction$2.doInTransaction:49
 2014-05-27 17:41:28,662 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-22:ctx-dbbc3135) ===START===  10.223.240.193 -- GET
  
 jobid=776d2770-db0d-44c8-b2e0-bbe2a9621642apiKey=x3l3u2QJMKK5AzForI9MKkjNWb4V2ewV-UY6qSPZERrS49jXwUFn5WLvN-r_QJZ-z
 1t-oO1g9F4-EiUZx9BdEQcommand=queryAsyncJobResultresponse=jsonsignature=%2Bk9OtkKpdJkU%2BWI7GO48SOrpKf4%3D
 2014-05-27 17:41:28,672 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (API-Job-Executor-89:ctx-c924058c job-577) Unexpected exception while 
 executing org.apache.cloudstack.api.command.user.tag.CreateTagsCmd
 com.cloud.utils.exception.CloudRuntimeException: DB Exception on: 
 com.mysql.jdbc.JDBC4PreparedStatement@6a7f6c5: INSERT INTO resource_tags 
 (resource_tags.uuid, resource_tags.key, resource_tags.value, 
 resource_tags.domain_id, resource_tags.account_id, resource_tags.resource_id, 
 resource_tags.resource_uuid, resource_tags.resource_type, 
 resource_tags.customer) VALUES 
 (_binary'46408de5-040c-4858-8323-881c358bda20', _binary'OS', _binary'CentOS', 
 -1, 82, 217, _binary'35e10eef-7980-4085-8b6c-c68174f1b529', 'Template', null)
 at com.cloud.utils.db.GenericDaoBase.persist(GenericDaoBase.java:1400)
 at sun.reflect.GeneratedMethodAccessor98.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at 
 

[jira] [Resolved] (CLOUDSTACK-6671) Failed to start instance VM java.lang.NullPointerException at com.cloud.hypervisor.KVMGuru.implement(KVMGuru.java:64)

2014-06-04 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-6671.
---

Resolution: Fixed

 Failed to start instance VM java.lang.NullPointerException at 
 com.cloud.hypervisor.KVMGuru.implement(KVMGuru.java:64)
 -

 Key: CLOUDSTACK-6671
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6671
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Install and Setup, KVM
Affects Versions: 4.4.0
 Environment: Ubuntu 14.04 / KVM / CS 4.4.0 snapshot 20140513 / 
 20140516
Reporter: Milamber
Assignee: Amogh Vasekar
Priority: Critical
  Labels: KVM
 Attachments: extract-management.log


 Unable to create VM on a fresh CS 4.4.0 installation (branch 4.4). 
 SSVM, Console proxy and first virtual routeur are correctly created and UP.
 10 day ago, this issue isn't present.
 In attachment, full log.
 2014-05-14 15:46:33,085 ERROR [c.c.v.VirtualMachineManagerImpl] 
 (Work-Job-Executor-6:job-25/job-27 ctx-57c7f749) Failed to start instance 
 VM[User|i-2-5-VM]
 java.lang.NullPointerException
   at com.cloud.hypervisor.KVMGuru.implement(KVMGuru.java:64)
   at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:995)
   at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5180)
   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:606)
   at 
 com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
   at 
 com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5325)
   at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
   at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:496)
   at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
   at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
   at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
   at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
   at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
   at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:453)
   at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
   at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
   at java.lang.Thread.run(Thread.java:744)



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-6793) [Automation] CreateTagsCmd fails with db exceptions

2014-06-03 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-6793:
---

Hi,

Seems like a test case issue. The test was not executed previously since a 
related test case was failing. Dont see any change in the codebase, and the 
functionality seems to be working in the UI.
The error here is attempting to insert record for tag for Template reosurce, 
and it is using the default -1 domain ID. 

Thanks!

 [Automation] CreateTagsCmd fails with db exceptions 
 

 Key: CLOUDSTACK-6793
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6793
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.4.0
 Environment: KVM 
Reporter: Rayees Namathponnan
Assignee: Amogh Vasekar
Priority: Blocker
 Fix For: 4.4.0

 Attachments: management-server.rar


 Steps to reproduce 
 Execute the test case integration.component.test_tags.TestResourceTags
 Test case perform below steps 
 # 1. Create a tag on template/ISO using createTags API
 # 2. Delete above created tag using deleteTags API
 2014-05-27 17:41:28,658 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-10:ctx-3b66377c ctx-fdaf9174 ctx-62d4b9d2) ===END===
   10.223.240.193 -- GET  
 apiKey=x3l3u2QJMKK5AzForI9MKkjNWb4V2ewV-UY6qSPZERrS49jXwUFn5WLvN-r_QJZ-z1t-oO1g9F4-EiUZx9Bd
 EQresourcetype=TemplateresourceIds=35e10eef-7980-4085-8b6c-c68174f1b529command=createTagssignature=pIJSk7ekg0Tlf
 RN%2FWfdp8U42Bgs%3Dtags%5B0%5D.key=OSresponse=jsontags%5B0%5D.value=CentOS
 2014-05-27 17:41:28,661 DEBUG [c.c.u.d.T.Transaction] 
 (API-Job-Executor-89:ctx-c924058c job-577 ctx-ec2f3eb8) Rollin
 g back the transaction: Time = 4 Name =  API-Job-Executor-89; called by 
 -TransactionLegacy.rollback:903-TransactionL
 egacy.removeUpTo:846-TransactionLegacy.close:670-TransactionContextInterceptor.invoke:36-ReflectiveMethodInvocation.
 proceed:161-ExposeInvocationInterceptor.invoke:91-ReflectiveMethodInvocation.proceed:172-JdkDynamicAopProxy.invoke:2
 04-$Proxy52.persist:-1-TaggedResourceManagerImpl$1.doInTransactionWithoutResult:245-TransactionCallbackNoReturn.doIn
 Transaction:25-Transaction$2.doInTransaction:49
 2014-05-27 17:41:28,662 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-22:ctx-dbbc3135) ===START===  10.223.240.193 -- GET
  
 jobid=776d2770-db0d-44c8-b2e0-bbe2a9621642apiKey=x3l3u2QJMKK5AzForI9MKkjNWb4V2ewV-UY6qSPZERrS49jXwUFn5WLvN-r_QJZ-z
 1t-oO1g9F4-EiUZx9BdEQcommand=queryAsyncJobResultresponse=jsonsignature=%2Bk9OtkKpdJkU%2BWI7GO48SOrpKf4%3D
 2014-05-27 17:41:28,672 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (API-Job-Executor-89:ctx-c924058c job-577) Unexpected exception while 
 executing org.apache.cloudstack.api.command.user.tag.CreateTagsCmd
 com.cloud.utils.exception.CloudRuntimeException: DB Exception on: 
 com.mysql.jdbc.JDBC4PreparedStatement@6a7f6c5: INSERT INTO resource_tags 
 (resource_tags.uuid, resource_tags.key, resource_tags.value, 
 resource_tags.domain_id, resource_tags.account_id, resource_tags.resource_id, 
 resource_tags.resource_uuid, resource_tags.resource_type, 
 resource_tags.customer) VALUES 
 (_binary'46408de5-040c-4858-8323-881c358bda20', _binary'OS', _binary'CentOS', 
 -1, 82, 217, _binary'35e10eef-7980-4085-8b6c-c68174f1b529', 'Template', null)
 at com.cloud.utils.db.GenericDaoBase.persist(GenericDaoBase.java:1400)
 at sun.reflect.GeneratedMethodAccessor98.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 at 
 com.cloud.utils.db.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:34)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
 at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at com.sun.proxy.$Proxy52.persist(Unknown Source)
 at 
 

[jira] [Updated] (CLOUDSTACK-6793) [Automation] CreateTagsCmd fails with db exceptions

2014-06-03 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar updated CLOUDSTACK-6793:
--

Issue Type: Test  (was: Bug)

 [Automation] CreateTagsCmd fails with db exceptions 
 

 Key: CLOUDSTACK-6793
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6793
 Project: CloudStack
  Issue Type: Test
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.4.0
 Environment: KVM 
Reporter: Rayees Namathponnan
Assignee: Amogh Vasekar
Priority: Blocker
 Fix For: 4.4.0

 Attachments: management-server.rar


 Steps to reproduce 
 Execute the test case integration.component.test_tags.TestResourceTags
 Test case perform below steps 
 # 1. Create a tag on template/ISO using createTags API
 # 2. Delete above created tag using deleteTags API
 2014-05-27 17:41:28,658 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-10:ctx-3b66377c ctx-fdaf9174 ctx-62d4b9d2) ===END===
   10.223.240.193 -- GET  
 apiKey=x3l3u2QJMKK5AzForI9MKkjNWb4V2ewV-UY6qSPZERrS49jXwUFn5WLvN-r_QJZ-z1t-oO1g9F4-EiUZx9Bd
 EQresourcetype=TemplateresourceIds=35e10eef-7980-4085-8b6c-c68174f1b529command=createTagssignature=pIJSk7ekg0Tlf
 RN%2FWfdp8U42Bgs%3Dtags%5B0%5D.key=OSresponse=jsontags%5B0%5D.value=CentOS
 2014-05-27 17:41:28,661 DEBUG [c.c.u.d.T.Transaction] 
 (API-Job-Executor-89:ctx-c924058c job-577 ctx-ec2f3eb8) Rollin
 g back the transaction: Time = 4 Name =  API-Job-Executor-89; called by 
 -TransactionLegacy.rollback:903-TransactionL
 egacy.removeUpTo:846-TransactionLegacy.close:670-TransactionContextInterceptor.invoke:36-ReflectiveMethodInvocation.
 proceed:161-ExposeInvocationInterceptor.invoke:91-ReflectiveMethodInvocation.proceed:172-JdkDynamicAopProxy.invoke:2
 04-$Proxy52.persist:-1-TaggedResourceManagerImpl$1.doInTransactionWithoutResult:245-TransactionCallbackNoReturn.doIn
 Transaction:25-Transaction$2.doInTransaction:49
 2014-05-27 17:41:28,662 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-22:ctx-dbbc3135) ===START===  10.223.240.193 -- GET
  
 jobid=776d2770-db0d-44c8-b2e0-bbe2a9621642apiKey=x3l3u2QJMKK5AzForI9MKkjNWb4V2ewV-UY6qSPZERrS49jXwUFn5WLvN-r_QJZ-z
 1t-oO1g9F4-EiUZx9BdEQcommand=queryAsyncJobResultresponse=jsonsignature=%2Bk9OtkKpdJkU%2BWI7GO48SOrpKf4%3D
 2014-05-27 17:41:28,672 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (API-Job-Executor-89:ctx-c924058c job-577) Unexpected exception while 
 executing org.apache.cloudstack.api.command.user.tag.CreateTagsCmd
 com.cloud.utils.exception.CloudRuntimeException: DB Exception on: 
 com.mysql.jdbc.JDBC4PreparedStatement@6a7f6c5: INSERT INTO resource_tags 
 (resource_tags.uuid, resource_tags.key, resource_tags.value, 
 resource_tags.domain_id, resource_tags.account_id, resource_tags.resource_id, 
 resource_tags.resource_uuid, resource_tags.resource_type, 
 resource_tags.customer) VALUES 
 (_binary'46408de5-040c-4858-8323-881c358bda20', _binary'OS', _binary'CentOS', 
 -1, 82, 217, _binary'35e10eef-7980-4085-8b6c-c68174f1b529', 'Template', null)
 at com.cloud.utils.db.GenericDaoBase.persist(GenericDaoBase.java:1400)
 at sun.reflect.GeneratedMethodAccessor98.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 at 
 com.cloud.utils.db.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:34)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
 at 
 org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at com.sun.proxy.$Proxy52.persist(Unknown Source)
 at 
 com.cloud.tags.TaggedResourceManagerImpl$1.doInTransactionWithoutResult(TaggedResourceManagerImpl.java:245)
 at 
 com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java:25)
 at 
 com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49)
 at com.cloud.utils.db.Transaction.execute(Transaction.java:37)
 at 

[jira] [Commented] (CLOUDSTACK-6723) [DynamicallyAddingGuestOs]Observed NPE when VM is deployed using the guest OS which has no mapping to any hypervisor

2014-05-28 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-6723:
---

Was fixed as a part of https://reviews.apache.org/r/21673/

Thanks,
Amogh

 [DynamicallyAddingGuestOs]Observed NPE when VM is deployed using the guest OS 
 which has no mapping to any hypervisor
 

 Key: CLOUDSTACK-6723
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6723
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: XenServer
Affects Versions: 4.4.0
 Environment: [root@RHEL63test ~]# cloudstack-sccs
 813ada1f691b146c368d25777185cac40958a892
Reporter: manasaveloori
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.4.0

 Attachments: management-server.rar, mysqldump44.dmp


 1. Add a guest os using API
 I added it using cloudmonkey:
  add guestos name=test oscategoryid=11 osdisplayname=test1centos
 mysql select category_id,name,uuid,display_name from guest_os where 
 display_name=test1centos;
 +-+--+--+--+
 | category_id | name | uuid | display_name |
 +-+--+--+--+
 |  11 | test | 8c413100-8b68-49c3-b81c-372c3ba8f998 | test1centos  |
 +-+--+--+--+
 1 row in set (0.00 sec)
 2. did not create any mapping for this OS to hypervisor.
 mysql select hypervisor_type ,guest_os_name,hypervisor_version from 
 guest_os_hypervisor where guest_os_name=test1centos;
 Empty set (0.00 sec)
 3. Registered the template using the above created OS type.
 4. Now deploy a VM using the template.
 Observation:
 Observed NPE in Ms logs and deploy VM is failing.
 2014-05-20 17:08:53,747 DEBUG [c.c.n.NetworkModelImpl] 
 (Work-Job-Executor-23:job-61/job-63 ctx-0477ee48) Service SecurityGroup is 
 not supported in the network id=206
 2014-05-20 17:08:53,749 DEBUG [o.a.c.e.o.VolumeOrchestrator] 
 (Work-Job-Executor-23:job-61/job-63 ctx-0477ee48) Checking if we need to 
 prepare 1 volumes for VM[User|i-2-13-VM]
 2014-05-20 17:08:53,750 DEBUG [o.a.c.e.o.VolumeOrchestrator] 
 (Work-Job-Executor-23:job-61/job-63 ctx-0477ee48) No need to recreate the 
 volume: Vol[13|vm=13|ROOT], since it already has a pool assigned: 1, adding 
 disk to VM
 2014-05-20 17:08:53,773 ERROR [c.c.v.VirtualMachineManagerImpl] 
 (Work-Job-Executor-23:job-61/job-63 ctx-0477ee48) Failed to start instance 
 VM[User|i-2-13-VM]
 java.lang.NullPointerException
 at com.cloud.hypervisor.XenServerGuru.implement(XenServerGuru.java:96)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:995)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5180)
 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:606)
 at 
 com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5325)
 at 
 com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:496)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:453)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 

[jira] [Resolved] (CLOUDSTACK-6723) [DynamicallyAddingGuestOs]Observed NPE when VM is deployed using the guest OS which has no mapping to any hypervisor

2014-05-28 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-6723.
---

Resolution: Fixed

 [DynamicallyAddingGuestOs]Observed NPE when VM is deployed using the guest OS 
 which has no mapping to any hypervisor
 

 Key: CLOUDSTACK-6723
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6723
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: XenServer
Affects Versions: 4.4.0
 Environment: [root@RHEL63test ~]# cloudstack-sccs
 813ada1f691b146c368d25777185cac40958a892
Reporter: manasaveloori
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.4.0

 Attachments: management-server.rar, mysqldump44.dmp


 1. Add a guest os using API
 I added it using cloudmonkey:
  add guestos name=test oscategoryid=11 osdisplayname=test1centos
 mysql select category_id,name,uuid,display_name from guest_os where 
 display_name=test1centos;
 +-+--+--+--+
 | category_id | name | uuid | display_name |
 +-+--+--+--+
 |  11 | test | 8c413100-8b68-49c3-b81c-372c3ba8f998 | test1centos  |
 +-+--+--+--+
 1 row in set (0.00 sec)
 2. did not create any mapping for this OS to hypervisor.
 mysql select hypervisor_type ,guest_os_name,hypervisor_version from 
 guest_os_hypervisor where guest_os_name=test1centos;
 Empty set (0.00 sec)
 3. Registered the template using the above created OS type.
 4. Now deploy a VM using the template.
 Observation:
 Observed NPE in Ms logs and deploy VM is failing.
 2014-05-20 17:08:53,747 DEBUG [c.c.n.NetworkModelImpl] 
 (Work-Job-Executor-23:job-61/job-63 ctx-0477ee48) Service SecurityGroup is 
 not supported in the network id=206
 2014-05-20 17:08:53,749 DEBUG [o.a.c.e.o.VolumeOrchestrator] 
 (Work-Job-Executor-23:job-61/job-63 ctx-0477ee48) Checking if we need to 
 prepare 1 volumes for VM[User|i-2-13-VM]
 2014-05-20 17:08:53,750 DEBUG [o.a.c.e.o.VolumeOrchestrator] 
 (Work-Job-Executor-23:job-61/job-63 ctx-0477ee48) No need to recreate the 
 volume: Vol[13|vm=13|ROOT], since it already has a pool assigned: 1, adding 
 disk to VM
 2014-05-20 17:08:53,773 ERROR [c.c.v.VirtualMachineManagerImpl] 
 (Work-Job-Executor-23:job-61/job-63 ctx-0477ee48) Failed to start instance 
 VM[User|i-2-13-VM]
 java.lang.NullPointerException
 at com.cloud.hypervisor.XenServerGuru.implement(XenServerGuru.java:96)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:995)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5180)
 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:606)
 at 
 com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
 at 
 com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5325)
 at 
 com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:496)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:453)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:744)
 

[jira] [Updated] (CLOUDSTACK-6358) Remove hardcoded guest OS mappings

2014-05-22 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar updated CLOUDSTACK-6358:
--

Priority: Critical  (was: Major)

 Remove hardcoded guest OS mappings
 --

 Key: CLOUDSTACK-6358
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6358
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.3.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.4.0


 The guest OS to platform emulator mappings are hardcoded in the codebase.
 This needs to be removed so as to support dynamic addition of guest OS type



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Assigned] (CLOUDSTACK-6671) Failed to start instance VM java.lang.NullPointerException at com.cloud.hypervisor.KVMGuru.implement(KVMGuru.java:64)

2014-05-19 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar reassigned CLOUDSTACK-6671:
-

Assignee: Amogh Vasekar

 Failed to start instance VM java.lang.NullPointerException at 
 com.cloud.hypervisor.KVMGuru.implement(KVMGuru.java:64)
 -

 Key: CLOUDSTACK-6671
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6671
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Install and Setup, KVM
Affects Versions: 4.4.0
 Environment: Ubuntu 14.04 / KVM / CS 4.4.0 snapshot 20140513 / 
 20140516
Reporter: Milamber
Assignee: Amogh Vasekar
Priority: Critical
  Labels: KVM
 Attachments: extract-management.log


 Unable to create VM on a fresh CS 4.4.0 installation (branch 4.4). 
 SSVM, Console proxy and first virtual routeur are correctly created and UP.
 10 day ago, this issue isn't present.
 In attachment, full log.
 2014-05-14 15:46:33,085 ERROR [c.c.v.VirtualMachineManagerImpl] 
 (Work-Job-Executor-6:job-25/job-27 ctx-57c7f749) Failed to start instance 
 VM[User|i-2-5-VM]
 java.lang.NullPointerException
   at com.cloud.hypervisor.KVMGuru.implement(KVMGuru.java:64)
   at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:995)
   at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5180)
   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:606)
   at 
 com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
   at 
 com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5325)
   at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
   at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:496)
   at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
   at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
   at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
   at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
   at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
   at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:453)
   at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
   at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
   at java.lang.Thread.run(Thread.java:744)



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-6671) Failed to start instance VM java.lang.NullPointerException at com.cloud.hypervisor.KVMGuru.implement(KVMGuru.java:64)

2014-05-19 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-6671:
---

This issue arises due to a missing Debian mapping in the table.
Fixing via https://reviews.apache.org/r/21673/

 Failed to start instance VM java.lang.NullPointerException at 
 com.cloud.hypervisor.KVMGuru.implement(KVMGuru.java:64)
 -

 Key: CLOUDSTACK-6671
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6671
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Install and Setup, KVM
Affects Versions: 4.4.0
 Environment: Ubuntu 14.04 / KVM / CS 4.4.0 snapshot 20140513 / 
 20140516
Reporter: Milamber
Assignee: Amogh Vasekar
Priority: Critical
  Labels: KVM
 Attachments: extract-management.log


 Unable to create VM on a fresh CS 4.4.0 installation (branch 4.4). 
 SSVM, Console proxy and first virtual routeur are correctly created and UP.
 10 day ago, this issue isn't present.
 In attachment, full log.
 2014-05-14 15:46:33,085 ERROR [c.c.v.VirtualMachineManagerImpl] 
 (Work-Job-Executor-6:job-25/job-27 ctx-57c7f749) Failed to start instance 
 VM[User|i-2-5-VM]
 java.lang.NullPointerException
   at com.cloud.hypervisor.KVMGuru.implement(KVMGuru.java:64)
   at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:995)
   at 
 com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5180)
   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:606)
   at 
 com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
   at 
 com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5325)
   at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
   at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:496)
   at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
   at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
   at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
   at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
   at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
   at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:453)
   at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
   at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
   at java.lang.Thread.run(Thread.java:744)



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Created] (CLOUDSTACK-6695) UI should allow uploading chained SSL certificates

2014-05-16 Thread Amogh Vasekar (JIRA)
Amogh Vasekar created CLOUDSTACK-6695:
-

 Summary: UI  should allow uploading chained SSL certificates
 Key: CLOUDSTACK-6695
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6695
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: UI
Affects Versions: 4.3.0
Reporter: Amogh Vasekar
Priority: Critical
 Fix For: Future, 4.4.0


Currently, to upload chained certificates into CloudStack for SSVM / CPVM 
requires making API calls with right id and alias parameter.
The UI only supports adding the server certificate, and should be enhanced to 
support adding the whole chain.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Resolved] (CLOUDSTACK-6437) Ability to differentiate user and system guest OS and mappings

2014-05-13 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-6437.
---

Resolution: Fixed

 Ability to differentiate user and system guest OS and mappings
 --

 Key: CLOUDSTACK-6437
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6437
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.4.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.4.0


 During upgrades, we need a way to distinguish between user defined and system 
 defined guest OS and mappings. If not, using same names etc might overwrite 
 changes



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Created] (CLOUDSTACK-6516) Default value of secstorage.encrypt.copy overridden

2014-04-25 Thread Amogh Vasekar (JIRA)
Amogh Vasekar created CLOUDSTACK-6516:
-

 Summary: Default value of secstorage.encrypt.copy overridden
 Key: CLOUDSTACK-6516
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6516
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server
Affects Versions: 4.3.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
 Fix For: 4.4.0


In 4.3, SSL was turned off by default.
However, for SSVM, the value from configuration server overrides the default in 
Config.java. Work around is to change in global properties.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Created] (CLOUDSTACK-6437) Ability to differentiate user and system guest OS and mappings

2014-04-17 Thread Amogh Vasekar (JIRA)
Amogh Vasekar created CLOUDSTACK-6437:
-

 Summary: Ability to differentiate user and system guest OS and 
mappings
 Key: CLOUDSTACK-6437
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6437
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server
Affects Versions: 4.4.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.4.0


During upgrades, we need a way to distinguish between user defined and system 
defined guest OS and mappings. If not, using same names etc might overwrite 
changes



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Created] (CLOUDSTACK-6358) Remove hardcoded guest OS mappings

2014-04-08 Thread Amogh Vasekar (JIRA)
Amogh Vasekar created CLOUDSTACK-6358:
-

 Summary: Remove hardcoded guest OS mappings
 Key: CLOUDSTACK-6358
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6358
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server
Affects Versions: 4.3.0
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
 Fix For: 4.4.0


The guest OS to platform emulator mappings are hardcoded in the codebase.
This needs to be removed so as to support dynamic addition of guest OS type



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Resolved] (CLOUDSTACK-6217) CRUD APIs for guest os and guest os mappings

2014-04-08 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-6217.
---

Resolution: Fixed

 CRUD APIs for guest os and guest os mappings
 

 Key: CLOUDSTACK-6217
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6217
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
 Fix For: 4.4.0


 Add APIs to be able to add new guest OS types, and their hypervisor specific 
 mappings



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-6293) Custom SSL certificate for console proxy does not work after upgrade 4.2.1 - 4.3

2014-03-27 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-6293:
---

Seems the file ConsoleProxyInfo is missing from the commit for 4.3, though it 
made it to master / 4.4
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ec4db7b [4.3]
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=09c3753 [master]



 Custom SSL certificate for console proxy does not work after upgrade 4.2.1 - 
 4.3
 -

 Key: CLOUDSTACK-6293
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6293
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Upgrade
Affects Versions: 4.3.0
Reporter: Remi Bergsma

 We use a custom SSL certificate that had been installed before the upgrade.
 After upgrading from 4.2.1 to 4.3 the console proxy did not work due to a 
 wrong SSL url being generated:
 https://1-2-3-4.*.ssl.example.com instead of https://1-2-3-4.ssl.example.com
 We fixed this by altering these settings to remove *.
 secstorage.ssl.cert.domain
 consoleproxy.url.domain
 These settings were altered during the upgrade, and they actually break it.
 2014-03-27 14:46:45,429 DEBUG [utils.db.ScriptRunner] (main:null) UPDATE 
 `cloud`.`configuration` SET value = CONCAT(*.,(SELECT `temptable`.`value` 
 FROM (SELECT * FROM `cloud`.`configuration` WHERE 
 `name`=consoleproxy.url.domain) AS `temptable` WHERE 
 `temptable`.`name`=consoleproxy.url.domain)) WHERE 
 `name`=consoleproxy.url.domain 
 2014-03-27 14:46:45,441 DEBUG [utils.db.ScriptRunner] (main:null) UPDATE 
 `cloud`.`configuration` SET `value` = CONCAT(*.,(SELECT `temptable`.`value` 
 FROM (SELECT * FROM `cloud`.`configuration` WHERE 
 `name`=secstorage.ssl.cert.domain) AS `temptable` WHERE 
 `temptable`.`name`=secstorage.ssl.cert.domain)) WHERE 
 `name`=secstorage.ssl.cert.domain
 The SQL can be found in this file:
 /usr/share/cloudstack-management/setup/db/schema-421to430.sql
 Please fix this!
 Thanks,
 Remi



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Created] (CLOUDSTACK-6217) CRUD APIs for guest os and guest os mappings

2014-03-10 Thread Amogh Vasekar (JIRA)
Amogh Vasekar created CLOUDSTACK-6217:
-

 Summary: CRUD APIs for guest os and guest os mappings
 Key: CLOUDSTACK-6217
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6217
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
 Fix For: 4.4.0


Add APIs to be able to add new guest OS types, and their hypervisor specific 
mappings



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Created] (CLOUDSTACK-6204) HTTP support for CPVM, as part of realhostip changes

2014-03-05 Thread Amogh Vasekar (JIRA)
Amogh Vasekar created CLOUDSTACK-6204:
-

 Summary: HTTP support for CPVM, as part of realhostip changes
 Key: CLOUDSTACK-6204
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6204
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server
Reporter: Amogh Vasekar
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: Future


Details can be found here 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Realhost+IP+changes





--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-3285) UCS: Need support for HTTP redirects and HTTPS Certificate handling

2013-10-21 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-3285:
---

Fixed in commit : c4905eafd55f7b5171ef5f089d33f94e8db1a09f
For future reference - it broke due to the move to springframework.http from 
apache http.

 UCS: Need support for HTTP redirects and HTTPS Certificate handling
 ---

 Key: CLOUDSTACK-3285
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3285
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UCS
Affects Versions: 4.2.0
 Environment: Master; Basic Bare-metal and UCS
Reporter: Parth Jagirdar
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.2.1


 By default UCS has HTTP to HTTPs redirect enabled.
 At which point, addUcsManager fails with following error.
 2013-06-28 14:19:57,020 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null) 
 ===START===  10.217.252.127 -- GET  
 command=addUcsManagerzoneid=d92cc843-8c50-4f57-9c07-1041bf859f8dname=ucsmanagerurl=10.223.184.2username=adminresponse=jsonsessionkey=NiAtOI4sZHTkTJ37Y4jz0ntaeYg%3D_=1372454390205
 2013-06-28 14:19:57,256 WARN  [cloudstack.api.AddUcsManagerCmd] 
 (catalina-exec-20:null) Exception:
 com.cloud.utils.exception.CloudRuntimeException: Cannot get cookie
 at 
 com.cloud.ucs.manager.UcsManagerImpl.getCookie(UcsManagerImpl.java:174)
 at 
 com.cloud.ucs.manager.UcsManagerImpl.listBlades(UcsManagerImpl.java:179)
 at 
 com.cloud.ucs.manager.UcsManagerImpl.discoverBlades(UcsManagerImpl.java:123)
 at 
 com.cloud.ucs.manager.UcsManagerImpl.addUcsManager(UcsManagerImpl.java:154)
 at 
 org.apache.cloudstack.api.AddUcsManagerCmd.execute(AddUcsManagerCmd.java:68)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371)
 at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304)
 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:2268)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:679)
 Caused by: com.cloud.utils.exception.CloudRuntimeException: Call failed: 
 !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN
 htmlhead
 title302 Found/title
 /headbody
 h1Found/h1
 pThe document has moved a href=https://10.223.184.2/nuova;here/a./p
 /body/html
 at com.cloud.ucs.manager.UcsHttpClient.call(UcsHttpClient.java:50)
 at 
 com.cloud.ucs.manager.UcsManagerImpl.getCookie(UcsManagerImpl.java:166)
 ... 26 more
 Caused by: com.cloud.utils.exception.CloudRuntimeException: Call failed: 
 !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN
 htmlhead
 title302 Found/title
 /headbody
 h1Found/h1
 pThe document has moved a href=https://10.223.184.2/nuova;here/a./p
 /body/html
 at com.cloud.ucs.manager.UcsHttpClient.call(UcsHttpClient.java:41)
 ... 27 more
 2013-06-28 14:19:57,257 INFO  [cloud.api.ApiServer] (catalina-exec-20:null) 
 Cannot get cookie
 2013-06-28 14:19:57,258 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null) 
 ===END===  10.217.252.127 -- GET  

[jira] [Resolved] (CLOUDSTACK-3285) UCS: Need support for HTTP redirects and HTTPS Certificate handling

2013-10-18 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-3285.
---

   Resolution: Fixed
Fix Version/s: 4.2.1

Committed to 4.2 branch 

 UCS: Need support for HTTP redirects and HTTPS Certificate handling
 ---

 Key: CLOUDSTACK-3285
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3285
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UCS
Affects Versions: 4.2.0
 Environment: Master; Basic Bare-metal and UCS
Reporter: Parth Jagirdar
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.2.1


 By default UCS has HTTP to HTTPs redirect enabled.
 At which point, addUcsManager fails with following error.
 2013-06-28 14:19:57,020 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null) 
 ===START===  10.217.252.127 -- GET  
 command=addUcsManagerzoneid=d92cc843-8c50-4f57-9c07-1041bf859f8dname=ucsmanagerurl=10.223.184.2username=adminresponse=jsonsessionkey=NiAtOI4sZHTkTJ37Y4jz0ntaeYg%3D_=1372454390205
 2013-06-28 14:19:57,256 WARN  [cloudstack.api.AddUcsManagerCmd] 
 (catalina-exec-20:null) Exception:
 com.cloud.utils.exception.CloudRuntimeException: Cannot get cookie
 at 
 com.cloud.ucs.manager.UcsManagerImpl.getCookie(UcsManagerImpl.java:174)
 at 
 com.cloud.ucs.manager.UcsManagerImpl.listBlades(UcsManagerImpl.java:179)
 at 
 com.cloud.ucs.manager.UcsManagerImpl.discoverBlades(UcsManagerImpl.java:123)
 at 
 com.cloud.ucs.manager.UcsManagerImpl.addUcsManager(UcsManagerImpl.java:154)
 at 
 org.apache.cloudstack.api.AddUcsManagerCmd.execute(AddUcsManagerCmd.java:68)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371)
 at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304)
 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:2268)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:679)
 Caused by: com.cloud.utils.exception.CloudRuntimeException: Call failed: 
 !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN
 htmlhead
 title302 Found/title
 /headbody
 h1Found/h1
 pThe document has moved a href=https://10.223.184.2/nuova;here/a./p
 /body/html
 at com.cloud.ucs.manager.UcsHttpClient.call(UcsHttpClient.java:50)
 at 
 com.cloud.ucs.manager.UcsManagerImpl.getCookie(UcsManagerImpl.java:166)
 ... 26 more
 Caused by: com.cloud.utils.exception.CloudRuntimeException: Call failed: 
 !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN
 htmlhead
 title302 Found/title
 /headbody
 h1Found/h1
 pThe document has moved a href=https://10.223.184.2/nuova;here/a./p
 /body/html
 at com.cloud.ucs.manager.UcsHttpClient.call(UcsHttpClient.java:41)
 ... 27 more
 2013-06-28 14:19:57,257 INFO  [cloud.api.ApiServer] (catalina-exec-20:null) 
 Cannot get cookie
 2013-06-28 14:19:57,258 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null) 
 ===END===  10.217.252.127 -- GET  
 

[jira] [Commented] (CLOUDSTACK-3647) 3.0.6 to ASF 4.2 Upgrade: guest_os table has duplicate Windows 8 64-bit OS mappings on the Upgraded Setup

2013-08-01 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-3647:
---

Sorry, it seems the commit hasn't gone in yet. Let me follow up on it.

 3.0.6 to ASF 4.2 Upgrade: guest_os table has duplicate Windows 8 64-bit OS 
 mappings on the Upgraded Setup
 ---

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


 mysql select * from guest_os where display_name like Windows 8%;
 +-+-+--+--++
 | id  | category_id | name | uuid | 
 display_name   |
 +-+-+--+--++
 | 165 |   6 | NULL | 67b38d28-ed85-11e2-a76b-0649e40006c6 | Windows 8 
 (32-bit) |
 | 166 |   6 | NULL | 67b3a362-ed85-11e2-a76b-0649e40006c6 | Windows 8 
 (64-bit) |
 | 206 |   6 | NULL | 206  | Windows 
 8(64-bit)  |
 +-+-+--+--++
 3 rows in set (0.00 sec)
 mysql

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CLOUDSTACK-3432) UCS:API: associatesUscProfileToBlade fails with authentication error.

2013-08-01 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-3432:
---

Hi,
The response suggests a profile by the name profile-for-blade-4 already 
exists in the UCS. Can you please try after deleting the profile from the UI?

 UCS:API: associatesUscProfileToBlade fails with authentication error.
 -

 Key: CLOUDSTACK-3432
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3432
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
 Environment: Master with UCS and Baremetal
Reporter: Parth Jagirdar
Assignee: Amogh Vasekar
Priority: Blocker

 associatesUscProfileToBlade fails with authentication error.
 Refer to request and response below.
 Request is 
 http://10.223.132.160:8080/client/api?command=associatesUcsProfileToBladeucsmanagerid=14profiledn=org-root/ls-UCS_Testingbladeid=26response=jsonsessionkey=AgmkzfbrMK3YEVyj1qPahEtaPk4%3DfetchLatest=falsesortBy=usagepage=0pagesize=8_=1373411256093
 Response is
 { associateucsprofiletobladeresponse : 
 {uuidList:[],errorcode:530,cserrorcode:,errortext:ucs call 
 failed:\nsubmitted doc:configConfMos 
 inHierarchical=\true\inConfigspair 
 key=\org-root/ls-profile-for-blade-26\lsServer 
 statsPolicyName=\default\ mgmtFwPolicyName=\\ status=\\ 
 dynamicConPolicyName=\\ usrLbl=\\ hostFwPolicyName=\\ 
 vconProfileName=\\ agentPolicyName=\\ biosProfileName=\\ 
 powerPolicyName=\\ extIPState=\none\ scrubPolicyName=\\ 
 localDiskPolicyName=\\ mgmtAccessPolicyName=\\ identPoolName=\\ 
 solPolicyName=\\ bootPolicyName=\\ srcTemplName=\\ uuid=\\ 
 dn=\org-root/ls-profile-for-blade-26\ descr=\\ 
 maintPolicyName=\\lsBinding rn=\pn\ restrictMigration=\no\ 
 pnDn=\sys/chassis-1/blade-2\ 
 //lsServer/pair/inConfigs/configConfMos\nresponse: configConfMos 
 cookie=\\ response=\yes\ errorCode=\552\ 
 invocationResult=\service-unavailable\ errorDescr=\Authorization 
 required\ /configConfMos\n} }
 is cookie missing?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CLOUDSTACK-3591) No usage recording for VM snapshots

2013-07-29 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-3591:
---

Hi Mice,
No worries :-) . I was comparing with my (partial) implementation, and I think 
the check for adding Memory Size to ROOT disk only when type==MemoryDisk is 
missing?
I have created a patch for it, and will send you a review request.
Thanks!

 No usage recording for VM snapshots
 ---

 Key: CLOUDSTACK-3591
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3591
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Usage
Affects Versions: 4.2.0
 Environment: build:
 CloudPlatform-4.2-216-rhel6.3
Reporter: shweta agarwal
Assignee: Amogh Vasekar
Priority: Critical
 Fix For: 4.2.0


 Repro steps;
 Create a VM
 Create VM  snapshot
 Bug:
 Notice no usage events is recorded for VM  snapshot  created in step 2
 Expected result:
 We should have usage events for VM  snapshots creation and deletion

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Resolved] (CLOUDSTACK-3647) 3.0.6 to ASF 4.2 Upgrade: guest_os table has duplicate Windows 8 64-bit OS mappings on the Upgraded Setup

2013-07-26 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-3647.
---

Resolution: Fixed

Removed row in 410to420 schema update file. 

 3.0.6 to ASF 4.2 Upgrade: guest_os table has duplicate Windows 8 64-bit OS 
 mappings on the Upgraded Setup
 ---

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


 mysql select * from guest_os where display_name like Windows 8%;
 +-+-+--+--++
 | id  | category_id | name | uuid | 
 display_name   |
 +-+-+--+--++
 | 165 |   6 | NULL | 67b38d28-ed85-11e2-a76b-0649e40006c6 | Windows 8 
 (32-bit) |
 | 166 |   6 | NULL | 67b3a362-ed85-11e2-a76b-0649e40006c6 | Windows 8 
 (64-bit) |
 | 206 |   6 | NULL | 206  | Windows 
 8(64-bit)  |
 +-+-+--+--++
 3 rows in set (0.00 sec)
 mysql

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Resolved] (CLOUDSTACK-3285) UCS: Need support for HTTP redirects and HTTPS Certificate handling

2013-07-23 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-3285.
---

Resolution: Fixed

The redirect now works, using EasySSLProtocolFactory. Note that it accepts 
self-signed certificates.
Multiple level of redirects are currently disallowed

 UCS: Need support for HTTP redirects and HTTPS Certificate handling
 ---

 Key: CLOUDSTACK-3285
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3285
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UCS
Affects Versions: 4.2.0
 Environment: Master; Basic Bare-metal and UCS
Reporter: Parth Jagirdar
Assignee: Amogh Vasekar
Priority: Critical

 By default UCS has HTTP to HTTPs redirect enabled.
 At which point, addUcsManager fails with following error.
 2013-06-28 14:19:57,020 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null) 
 ===START===  10.217.252.127 -- GET  
 command=addUcsManagerzoneid=d92cc843-8c50-4f57-9c07-1041bf859f8dname=ucsmanagerurl=10.223.184.2username=adminresponse=jsonsessionkey=NiAtOI4sZHTkTJ37Y4jz0ntaeYg%3D_=1372454390205
 2013-06-28 14:19:57,256 WARN  [cloudstack.api.AddUcsManagerCmd] 
 (catalina-exec-20:null) Exception:
 com.cloud.utils.exception.CloudRuntimeException: Cannot get cookie
 at 
 com.cloud.ucs.manager.UcsManagerImpl.getCookie(UcsManagerImpl.java:174)
 at 
 com.cloud.ucs.manager.UcsManagerImpl.listBlades(UcsManagerImpl.java:179)
 at 
 com.cloud.ucs.manager.UcsManagerImpl.discoverBlades(UcsManagerImpl.java:123)
 at 
 com.cloud.ucs.manager.UcsManagerImpl.addUcsManager(UcsManagerImpl.java:154)
 at 
 org.apache.cloudstack.api.AddUcsManagerCmd.execute(AddUcsManagerCmd.java:68)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371)
 at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304)
 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:2268)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:679)
 Caused by: com.cloud.utils.exception.CloudRuntimeException: Call failed: 
 !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN
 htmlhead
 title302 Found/title
 /headbody
 h1Found/h1
 pThe document has moved a href=https://10.223.184.2/nuova;here/a./p
 /body/html
 at com.cloud.ucs.manager.UcsHttpClient.call(UcsHttpClient.java:50)
 at 
 com.cloud.ucs.manager.UcsManagerImpl.getCookie(UcsManagerImpl.java:166)
 ... 26 more
 Caused by: com.cloud.utils.exception.CloudRuntimeException: Call failed: 
 !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN
 htmlhead
 title302 Found/title
 /headbody
 h1Found/h1
 pThe document has moved a href=https://10.223.184.2/nuova;here/a./p
 /body/html
 at com.cloud.ucs.manager.UcsHttpClient.call(UcsHttpClient.java:41)
 ... 27 more
 2013-06-28 14:19:57,257 INFO  [cloud.api.ApiServer] (catalina-exec-20:null) 
 Cannot get cookie
 2013-06-28 14:19:57,258 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null) 
 ===END===  10.217.252.127 -- GET  
 

[jira] [Commented] (CLOUDSTACK-3308) UCS:DB: UCS Manager password should not get stored in plain text.

2013-07-19 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-3308:
---

Here is the way it is stored after the fix : 
++--+-++--+--+--+
| id | uuid | zone_id | name   | url
  | username | password |
++--+-++--+--+--+
|  1 | c898782c-fa71-48e1-946c-272a7775 |   2 | ucsmanager | 
10.223.184.2 | admin| lxdJ+Q2+TpGdTWyo3yWCfQFWq31fn49x |
++--+-++--+--+--+

Please note that you will need to set-up encryption for this to work (which is 
a process in itself for dev set-ups)

 UCS:DB: UCS Manager password should not get stored in plain text.
 -

 Key: CLOUDSTACK-3308
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3308
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UCS
Affects Versions: 4.2.0
 Environment: Master with UCS and Basic Baremetal
Reporter: Parth Jagirdar
Assignee: Amogh Vasekar
Priority: Blocker
 Fix For: 4.2.0


 Observe the table below.
 UCS manager password gets stored in plain text.
 mysql select * from ucs_manager;
 ++--+-++--+--++
 | id | uuid | zone_id | name   | url  
 | username | password   |
 ++--+-++--+--++
 |  1 | ec179fa5-a38c-4df0-a688-b89c29764b1d |   2 | ucsmanager | 
 10.223.184.2 | admin| C1tr1x99   |
 |  2 | c14c6917-274b-47f1-b2f8-e7af767fe5c6 |   2 | ucsmanager | 
 10.223.184.2 | admin| C1tr1x99   |
 |  3 | 10e7ef23-f9b9-49f4-aac5-8508eb882a52 |   2 | ucsmanager | 
 10.223.184.2 | admin| C1tr1x99   |
 |  4 | be42a44f-4ae6-41ba-9e13-76a7707dcf5e |   2 | ucsmanager | 
 10.223.184.2 | admin| C1tr1x99   |
 |  5 | b464511b-e961-4b65-9c9c-9cf5974f5cd1 |   2 | ucsmanager | 
 10.223.184.2 | admin| C1tr1x99   |
 |  6 | dd669374-27f8-49d3-9425-498af6bbc16e |   2 | ucsmanager | 
 10.223.184.2 | admin| C1tr1x99   |
 |  7 | 7e902e15-e634-41a9-9bed-d6134bb7a377 |   2 | ucsmanager | 
 10.223.184.2 | admin| C1tr1x99   |
 |  8 | 1d6775c8-270a-461c-9b28-7b1b2acbbd5e |   2 | ucsmanager | 
 10.223.184.2 | aa   | C1tr1x99   |
 |  9 | 4da9accc-eb7c-42fb-a23c-3c45716db1f5 |   2 | ucsmanager | 
 10.223.184.2 | admin| C1tr1x99   |
 | 10 | 55023c65-4470-4ee7-b264-f19cd4065c75 |   2 | ucsmanager | 
 10.223.184.2 | admin| wrong-password |
 ++--+-++--+--++
 10 rows in set (0.00 sec)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Resolved] (CLOUDSTACK-3308) UCS:DB: UCS Manager password should not get stored in plain text.

2013-07-19 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-3308.
---

Resolution: Fixed

 UCS:DB: UCS Manager password should not get stored in plain text.
 -

 Key: CLOUDSTACK-3308
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3308
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UCS
Affects Versions: 4.2.0
 Environment: Master with UCS and Basic Baremetal
Reporter: Parth Jagirdar
Assignee: Amogh Vasekar
Priority: Blocker
 Fix For: 4.2.0


 Observe the table below.
 UCS manager password gets stored in plain text.
 mysql select * from ucs_manager;
 ++--+-++--+--++
 | id | uuid | zone_id | name   | url  
 | username | password   |
 ++--+-++--+--++
 |  1 | ec179fa5-a38c-4df0-a688-b89c29764b1d |   2 | ucsmanager | 
 10.223.184.2 | admin| C1tr1x99   |
 |  2 | c14c6917-274b-47f1-b2f8-e7af767fe5c6 |   2 | ucsmanager | 
 10.223.184.2 | admin| C1tr1x99   |
 |  3 | 10e7ef23-f9b9-49f4-aac5-8508eb882a52 |   2 | ucsmanager | 
 10.223.184.2 | admin| C1tr1x99   |
 |  4 | be42a44f-4ae6-41ba-9e13-76a7707dcf5e |   2 | ucsmanager | 
 10.223.184.2 | admin| C1tr1x99   |
 |  5 | b464511b-e961-4b65-9c9c-9cf5974f5cd1 |   2 | ucsmanager | 
 10.223.184.2 | admin| C1tr1x99   |
 |  6 | dd669374-27f8-49d3-9425-498af6bbc16e |   2 | ucsmanager | 
 10.223.184.2 | admin| C1tr1x99   |
 |  7 | 7e902e15-e634-41a9-9bed-d6134bb7a377 |   2 | ucsmanager | 
 10.223.184.2 | admin| C1tr1x99   |
 |  8 | 1d6775c8-270a-461c-9b28-7b1b2acbbd5e |   2 | ucsmanager | 
 10.223.184.2 | aa   | C1tr1x99   |
 |  9 | 4da9accc-eb7c-42fb-a23c-3c45716db1f5 |   2 | ucsmanager | 
 10.223.184.2 | admin| C1tr1x99   |
 | 10 | 55023c65-4470-4ee7-b264-f19cd4065c75 |   2 | ucsmanager | 
 10.223.184.2 | admin| wrong-password |
 ++--+-++--+--++
 10 rows in set (0.00 sec)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Resolved] (CLOUDSTACK-3426) UCS: Session cookie refresh must be supported.

2013-07-16 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-3426.
---

Resolution: Fixed

 UCS: Session cookie refresh must be supported.
 --

 Key: CLOUDSTACK-3426
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3426
 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
 Environment: Master with UCS and Baremetal
Reporter: Parth Jagirdar
Assignee: Amogh Vasekar
Priority: Blocker

 A stale cookie will raise authentication error and subsequent API calls will 
 fail.
 We need a mechanism to refresh cookie based on recommendations below.
 While executing listUCSProfiles::
 { listucsprofileresponse : 
 {uuidList:[],errorcode:530,cserrorcode:,errortext:ucs call 
 failed:\nsubmitted doc:configFindDnsByClassId 
 cookie=\1372458054/13f7441f-5f86-4668-911f-8cad3f9be693\ 
 classId=\lsServer\ /\nresponse: configFindDnsByClassId 
 cookie=\1372458054/13f7441f-5f86-4668-911f-8cad3f9be693\ response=\yes\ 
 errorCode=\552\ invocationResult=\service-unavailable\ 
 errorDescr=\Authorization required\ /configFindDnsByClassId\n} }
 Here is the description from UCS API programming guide. (Full version here:: 
 http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/api/overview.html#wp1127584)
 Failed Requests
 The response to a failed request includes XML attributes for errorCode and 
 errorDescr. The following is an example of a response to a failed request:
 configConfMo dn=fabric/server
   cookie=real_cookie
   response=yes
   errorCode=103
   invocationResult=unidentified-fail
   errorDescr=can't create; object already exists.
 /configConfMo
 From forums 
 (http://developer.cisco.com/web/unifiedcomputing/community/-/message_boards/message/2774526?p_p_auth=iBnpvD2j)
 And from here 
 (http://developer.cisco.com/web/unifiedcomputing/blogroll/-/blogs/ucs-xml-api-hello-world)
 We have an authentication cookie but this cookie will expire in two hours, 
 the output from the aaaLogin recommends a cookie refresh every 10 minutes. To 
 refresh the authentication cookie use the aaaRefresh method.
 So basically we need a mechanism for cookie refresh. Which we do not have for 
 now.
 When I tried to add a new manager (so that cookie is fresh ??) ListProfiles 
 succeeded. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CLOUDSTACK-3426) UCS: Session cookie refresh must be supported.

2013-07-16 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-3426:
---

Added refresh mechanism.
Current timeouts for cookie refresh are 10 mins, and maximum TTL of cookie is 
100 mins

 UCS: Session cookie refresh must be supported.
 --

 Key: CLOUDSTACK-3426
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3426
 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
 Environment: Master with UCS and Baremetal
Reporter: Parth Jagirdar
Assignee: Amogh Vasekar
Priority: Blocker

 A stale cookie will raise authentication error and subsequent API calls will 
 fail.
 We need a mechanism to refresh cookie based on recommendations below.
 While executing listUCSProfiles::
 { listucsprofileresponse : 
 {uuidList:[],errorcode:530,cserrorcode:,errortext:ucs call 
 failed:\nsubmitted doc:configFindDnsByClassId 
 cookie=\1372458054/13f7441f-5f86-4668-911f-8cad3f9be693\ 
 classId=\lsServer\ /\nresponse: configFindDnsByClassId 
 cookie=\1372458054/13f7441f-5f86-4668-911f-8cad3f9be693\ response=\yes\ 
 errorCode=\552\ invocationResult=\service-unavailable\ 
 errorDescr=\Authorization required\ /configFindDnsByClassId\n} }
 Here is the description from UCS API programming guide. (Full version here:: 
 http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/api/overview.html#wp1127584)
 Failed Requests
 The response to a failed request includes XML attributes for errorCode and 
 errorDescr. The following is an example of a response to a failed request:
 configConfMo dn=fabric/server
   cookie=real_cookie
   response=yes
   errorCode=103
   invocationResult=unidentified-fail
   errorDescr=can't create; object already exists.
 /configConfMo
 From forums 
 (http://developer.cisco.com/web/unifiedcomputing/community/-/message_boards/message/2774526?p_p_auth=iBnpvD2j)
 And from here 
 (http://developer.cisco.com/web/unifiedcomputing/blogroll/-/blogs/ucs-xml-api-hello-world)
 We have an authentication cookie but this cookie will expire in two hours, 
 the output from the aaaLogin recommends a cookie refresh every 10 minutes. To 
 refresh the authentication cookie use the aaaRefresh method.
 So basically we need a mechanism for cookie refresh. Which we do not have for 
 now.
 When I tried to add a new manager (so that cookie is fresh ??) ListProfiles 
 succeeded. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Assigned] (CLOUDSTACK-3308) UCS:DB: UCS Manager password should not get stored in plain text.

2013-07-15 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar reassigned CLOUDSTACK-3308:
-

Assignee: Amogh Vasekar

 UCS:DB: UCS Manager password should not get stored in plain text.
 -

 Key: CLOUDSTACK-3308
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3308
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UCS
Affects Versions: 4.2.0
 Environment: Master with UCS and Basic Baremetal
Reporter: Parth Jagirdar
Assignee: Amogh Vasekar
Priority: Blocker
 Fix For: 4.2.0


 Observe the table below.
 UCS manager password gets stored in plain text.
 mysql select * from ucs_manager;
 ++--+-++--+--++
 | id | uuid | zone_id | name   | url  
 | username | password   |
 ++--+-++--+--++
 |  1 | ec179fa5-a38c-4df0-a688-b89c29764b1d |   2 | ucsmanager | 
 10.223.184.2 | admin| C1tr1x99   |
 |  2 | c14c6917-274b-47f1-b2f8-e7af767fe5c6 |   2 | ucsmanager | 
 10.223.184.2 | admin| C1tr1x99   |
 |  3 | 10e7ef23-f9b9-49f4-aac5-8508eb882a52 |   2 | ucsmanager | 
 10.223.184.2 | admin| C1tr1x99   |
 |  4 | be42a44f-4ae6-41ba-9e13-76a7707dcf5e |   2 | ucsmanager | 
 10.223.184.2 | admin| C1tr1x99   |
 |  5 | b464511b-e961-4b65-9c9c-9cf5974f5cd1 |   2 | ucsmanager | 
 10.223.184.2 | admin| C1tr1x99   |
 |  6 | dd669374-27f8-49d3-9425-498af6bbc16e |   2 | ucsmanager | 
 10.223.184.2 | admin| C1tr1x99   |
 |  7 | 7e902e15-e634-41a9-9bed-d6134bb7a377 |   2 | ucsmanager | 
 10.223.184.2 | admin| C1tr1x99   |
 |  8 | 1d6775c8-270a-461c-9b28-7b1b2acbbd5e |   2 | ucsmanager | 
 10.223.184.2 | aa   | C1tr1x99   |
 |  9 | 4da9accc-eb7c-42fb-a23c-3c45716db1f5 |   2 | ucsmanager | 
 10.223.184.2 | admin| C1tr1x99   |
 | 10 | 55023c65-4470-4ee7-b264-f19cd4065c75 |   2 | ucsmanager | 
 10.223.184.2 | admin| wrong-password |
 ++--+-++--+--++
 10 rows in set (0.00 sec)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Assigned] (CLOUDSTACK-3426) UCS: Session cookie refresh must be supported.

2013-07-11 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar reassigned CLOUDSTACK-3426:
-

Assignee: Amogh Vasekar

 UCS: Session cookie refresh must be supported.
 --

 Key: CLOUDSTACK-3426
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3426
 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
 Environment: Master with UCS and Baremetal
Reporter: Parth Jagirdar
Assignee: Amogh Vasekar
Priority: Blocker

 A stale cookie will raise authentication error and subsequent API calls will 
 fail.
 We need a mechanism to refresh cookie based on recommendations below.
 While executing listUCSProfiles::
 { listucsprofileresponse : 
 {uuidList:[],errorcode:530,cserrorcode:,errortext:ucs call 
 failed:\nsubmitted doc:configFindDnsByClassId 
 cookie=\1372458054/13f7441f-5f86-4668-911f-8cad3f9be693\ 
 classId=\lsServer\ /\nresponse: configFindDnsByClassId 
 cookie=\1372458054/13f7441f-5f86-4668-911f-8cad3f9be693\ response=\yes\ 
 errorCode=\552\ invocationResult=\service-unavailable\ 
 errorDescr=\Authorization required\ /configFindDnsByClassId\n} }
 Here is the description from UCS API programming guide. (Full version here:: 
 http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/api/overview.html#wp1127584)
 Failed Requests
 The response to a failed request includes XML attributes for errorCode and 
 errorDescr. The following is an example of a response to a failed request:
 configConfMo dn=fabric/server
   cookie=real_cookie
   response=yes
   errorCode=103
   invocationResult=unidentified-fail
   errorDescr=can't create; object already exists.
 /configConfMo
 From forums 
 (http://developer.cisco.com/web/unifiedcomputing/community/-/message_boards/message/2774526?p_p_auth=iBnpvD2j)
 And from here 
 (http://developer.cisco.com/web/unifiedcomputing/blogroll/-/blogs/ucs-xml-api-hello-world)
 We have an authentication cookie but this cookie will expire in two hours, 
 the output from the aaaLogin recommends a cookie refresh every 10 minutes. To 
 refresh the authentication cookie use the aaaRefresh method.
 So basically we need a mechanism for cookie refresh. Which we do not have for 
 now.
 When I tried to add a new manager (so that cookie is fresh ??) ListProfiles 
 succeeded. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Resolved] (CLOUDSTACK-3432) UCS:API: associatesUscProfileToBlade fails with authentication error.

2013-07-11 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar resolved CLOUDSTACK-3432.
---

Resolution: Fixed

 UCS:API: associatesUscProfileToBlade fails with authentication error.
 -

 Key: CLOUDSTACK-3432
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3432
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
 Environment: Master with UCS and Baremetal
Reporter: Parth Jagirdar
Assignee: Amogh Vasekar
Priority: Blocker

 associatesUscProfileToBlade fails with authentication error.
 Refer to request and response below.
 Request is 
 http://10.223.132.160:8080/client/api?command=associatesUcsProfileToBladeucsmanagerid=14profiledn=org-root/ls-UCS_Testingbladeid=26response=jsonsessionkey=AgmkzfbrMK3YEVyj1qPahEtaPk4%3DfetchLatest=falsesortBy=usagepage=0pagesize=8_=1373411256093
 Response is
 { associateucsprofiletobladeresponse : 
 {uuidList:[],errorcode:530,cserrorcode:,errortext:ucs call 
 failed:\nsubmitted doc:configConfMos 
 inHierarchical=\true\inConfigspair 
 key=\org-root/ls-profile-for-blade-26\lsServer 
 statsPolicyName=\default\ mgmtFwPolicyName=\\ status=\\ 
 dynamicConPolicyName=\\ usrLbl=\\ hostFwPolicyName=\\ 
 vconProfileName=\\ agentPolicyName=\\ biosProfileName=\\ 
 powerPolicyName=\\ extIPState=\none\ scrubPolicyName=\\ 
 localDiskPolicyName=\\ mgmtAccessPolicyName=\\ identPoolName=\\ 
 solPolicyName=\\ bootPolicyName=\\ srcTemplName=\\ uuid=\\ 
 dn=\org-root/ls-profile-for-blade-26\ descr=\\ 
 maintPolicyName=\\lsBinding rn=\pn\ restrictMigration=\no\ 
 pnDn=\sys/chassis-1/blade-2\ 
 //lsServer/pair/inConfigs/configConfMos\nresponse: configConfMos 
 cookie=\\ response=\yes\ errorCode=\552\ 
 invocationResult=\service-unavailable\ errorDescr=\Authorization 
 required\ /configConfMos\n} }
 is cookie missing?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CLOUDSTACK-3432) UCS:API: associatesUscProfileToBlade fails with authentication error.

2013-07-11 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar commented on CLOUDSTACK-3432:
---

Works now. Sample response

?xml version=1.0 encoding=UTF-8?associateucsprofiletobladeresponse 
cloud-stack-version=4.2.0-SNAPSHOTucsbladeid/iducsmanagerid/ucsmanageridbladedn/bladedn/ucsblade/associateucsprofiletobladeresponse

 UCS:API: associatesUscProfileToBlade fails with authentication error.
 -

 Key: CLOUDSTACK-3432
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3432
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
 Environment: Master with UCS and Baremetal
Reporter: Parth Jagirdar
Assignee: Amogh Vasekar
Priority: Blocker

 associatesUscProfileToBlade fails with authentication error.
 Refer to request and response below.
 Request is 
 http://10.223.132.160:8080/client/api?command=associatesUcsProfileToBladeucsmanagerid=14profiledn=org-root/ls-UCS_Testingbladeid=26response=jsonsessionkey=AgmkzfbrMK3YEVyj1qPahEtaPk4%3DfetchLatest=falsesortBy=usagepage=0pagesize=8_=1373411256093
 Response is
 { associateucsprofiletobladeresponse : 
 {uuidList:[],errorcode:530,cserrorcode:,errortext:ucs call 
 failed:\nsubmitted doc:configConfMos 
 inHierarchical=\true\inConfigspair 
 key=\org-root/ls-profile-for-blade-26\lsServer 
 statsPolicyName=\default\ mgmtFwPolicyName=\\ status=\\ 
 dynamicConPolicyName=\\ usrLbl=\\ hostFwPolicyName=\\ 
 vconProfileName=\\ agentPolicyName=\\ biosProfileName=\\ 
 powerPolicyName=\\ extIPState=\none\ scrubPolicyName=\\ 
 localDiskPolicyName=\\ mgmtAccessPolicyName=\\ identPoolName=\\ 
 solPolicyName=\\ bootPolicyName=\\ srcTemplName=\\ uuid=\\ 
 dn=\org-root/ls-profile-for-blade-26\ descr=\\ 
 maintPolicyName=\\lsBinding rn=\pn\ restrictMigration=\no\ 
 pnDn=\sys/chassis-1/blade-2\ 
 //lsServer/pair/inConfigs/configConfMos\nresponse: configConfMos 
 cookie=\\ response=\yes\ errorCode=\552\ 
 invocationResult=\service-unavailable\ errorDescr=\Authorization 
 required\ /configConfMos\n} }
 is cookie missing?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Assigned] (CLOUDSTACK-3432) UCS:API: associatesUscProfileToBlade fails with authentication error.

2013-07-09 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar reassigned CLOUDSTACK-3432:
-

Assignee: Amogh Vasekar

 UCS:API: associatesUscProfileToBlade fails with authentication error.
 -

 Key: CLOUDSTACK-3432
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3432
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
 Environment: Master with UCS and Baremetal
Reporter: Parth Jagirdar
Assignee: Amogh Vasekar
Priority: Blocker

 associatesUscProfileToBlade fails with authentication error.
 Refer to request and response below.
 Request is 
 http://10.223.132.160:8080/client/api?command=associatesUcsProfileToBladeucsmanagerid=14profiledn=org-root/ls-UCS_Testingbladeid=26response=jsonsessionkey=AgmkzfbrMK3YEVyj1qPahEtaPk4%3DfetchLatest=falsesortBy=usagepage=0pagesize=8_=1373411256093
 Response is
 { associateucsprofiletobladeresponse : 
 {uuidList:[],errorcode:530,cserrorcode:,errortext:ucs call 
 failed:\nsubmitted doc:configConfMos 
 inHierarchical=\true\inConfigspair 
 key=\org-root/ls-profile-for-blade-26\lsServer 
 statsPolicyName=\default\ mgmtFwPolicyName=\\ status=\\ 
 dynamicConPolicyName=\\ usrLbl=\\ hostFwPolicyName=\\ 
 vconProfileName=\\ agentPolicyName=\\ biosProfileName=\\ 
 powerPolicyName=\\ extIPState=\none\ scrubPolicyName=\\ 
 localDiskPolicyName=\\ mgmtAccessPolicyName=\\ identPoolName=\\ 
 solPolicyName=\\ bootPolicyName=\\ srcTemplName=\\ uuid=\\ 
 dn=\org-root/ls-profile-for-blade-26\ descr=\\ 
 maintPolicyName=\\lsBinding rn=\pn\ restrictMigration=\no\ 
 pnDn=\sys/chassis-1/blade-2\ 
 //lsServer/pair/inConfigs/configConfMos\nresponse: configConfMos 
 cookie=\\ response=\yes\ errorCode=\552\ 
 invocationResult=\service-unavailable\ errorDescr=\Authorization 
 required\ /configConfMos\n} }
 is cookie missing?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (CLOUDSTACK-3432) UCS:API: associatesUscProfileToBlade fails with authentication error.

2013-07-09 Thread Amogh Vasekar (JIRA)

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

Amogh Vasekar updated CLOUDSTACK-3432:
--

Status: Ready To Review  (was: In Progress)

 UCS:API: associatesUscProfileToBlade fails with authentication error.
 -

 Key: CLOUDSTACK-3432
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3432
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
 Environment: Master with UCS and Baremetal
Reporter: Parth Jagirdar
Assignee: Amogh Vasekar
Priority: Blocker

 associatesUscProfileToBlade fails with authentication error.
 Refer to request and response below.
 Request is 
 http://10.223.132.160:8080/client/api?command=associatesUcsProfileToBladeucsmanagerid=14profiledn=org-root/ls-UCS_Testingbladeid=26response=jsonsessionkey=AgmkzfbrMK3YEVyj1qPahEtaPk4%3DfetchLatest=falsesortBy=usagepage=0pagesize=8_=1373411256093
 Response is
 { associateucsprofiletobladeresponse : 
 {uuidList:[],errorcode:530,cserrorcode:,errortext:ucs call 
 failed:\nsubmitted doc:configConfMos 
 inHierarchical=\true\inConfigspair 
 key=\org-root/ls-profile-for-blade-26\lsServer 
 statsPolicyName=\default\ mgmtFwPolicyName=\\ status=\\ 
 dynamicConPolicyName=\\ usrLbl=\\ hostFwPolicyName=\\ 
 vconProfileName=\\ agentPolicyName=\\ biosProfileName=\\ 
 powerPolicyName=\\ extIPState=\none\ scrubPolicyName=\\ 
 localDiskPolicyName=\\ mgmtAccessPolicyName=\\ identPoolName=\\ 
 solPolicyName=\\ bootPolicyName=\\ srcTemplName=\\ uuid=\\ 
 dn=\org-root/ls-profile-for-blade-26\ descr=\\ 
 maintPolicyName=\\lsBinding rn=\pn\ restrictMigration=\no\ 
 pnDn=\sys/chassis-1/blade-2\ 
 //lsServer/pair/inConfigs/configConfMos\nresponse: configConfMos 
 cookie=\\ response=\yes\ errorCode=\552\ 
 invocationResult=\service-unavailable\ errorDescr=\Authorization 
 required\ /configConfMos\n} }
 is cookie missing?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira