[jira] [Updated] (CLOUDSTACK-7948) [Automation] Two VOLUME.DELETE Events are being registered instead of one - On Destroying a User VM belonging to a Project
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damodar Reddy T updated CLOUDSTACK-7948:
Status: Reviewable (was: In Progress)
[Automation] Two VOLUME.DELETE Events are being registered instead of one -
On Destroying a User VM belonging to a Project
Key: CLOUDSTACK-7948
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7948
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Damodar Reddy T
Fix For: 4.5.0
==
User VM in Project Events Information in the Database:
==
{noformat}
mysql select * from usage_event where account_id=6;
++-++-+-+-++-+-+-++---+--+
| id | type| account_id | created | zone_id |
resource_id | resource_name | offering_id | template_id | size|
resource_type | processed | virtual_size |
++-++-+-+-++-+-+-++---+--+
| 19 | TEMPLATE.CREATE | 6 | 2014-11-19 21:28:14 | 1 |
202 | TestTemplate-1 |NULL |NULL | 1708331520 | NULL
| 0 | 8589934592 |
| 20 | VOLUME.CREATE | 6 | 2014-11-19 21:32:23 | 1 |
9 | ROOT-9 | 1 | 5 | 21474836480 | NULL
| 0 | NULL |
| 21 | VM.CREATE | 6 | 2014-11-19 21:32:23 | 1 |
9 | Project-VM-1 | 1 | 5 |NULL |
XenServer | 0 | NULL |
| 22 | NET.IPASSIGN| 6 | 2014-11-19 21:32:25 | 1 |
6 | 10.219.196.151 |NULL | 0 | 0 |
DirectAttached | 0 | NULL |
| 23 | NETWORK.OFFERING.ASSIGN | 6 | 2014-11-19 21:32:33 | 1 |
9 | 19 | 6 |NULL | 1 | NULL
| 0 | NULL |
| 24 | SG.ASSIGN | 6 | 2014-11-19 21:32:33 | 1 |
9 | NULL | 4 |NULL |NULL | NULL
| 0 | NULL |
| 25 | VM.START| 6 | 2014-11-19 21:32:33 | 1 |
9 | Project-VM-1 | 1 | 5 |NULL |
XenServer | 0 | NULL |
| 26 | SG.REMOVE | 6 | 2014-11-19 21:33:10 | 1 |
9 | NULL | 4 |NULL |NULL | NULL
| 0 | NULL |
| 27 | VM.STOP | 6 | 2014-11-19 21:33:10 | 1 |
9 | Project-VM-1 | 1 | 5 |NULL |
XenServer | 0 | NULL |
| 28 | NETWORK.OFFERING.REMOVE | 6 | 2014-11-19 21:33:10 | 1 |
9 | 19 | 6 |NULL | 0 | NULL
| 0 | NULL |
| 31 | VM.DESTROY | 6 | 2014-11-20 00:08:37 | 1 |
9 | Project-VM-1 | 1 | 5 |NULL |
XenServer | 0 | NULL |
| 32 | VOLUME.DELETE | 6 | 2014-11-20 00:08:37 | 1 |
9 | ROOT-9 |NULL |NULL |NULL | NULL
| 0 | NULL |
| 33 | NET.IPRELEASE | 6 | 2014-11-20 00:08:39 | 1 |
6 | 10.219.196.151 |NULL | 0 | 0 |
DirectAttached | 0 | NULL |
| 34 | VOLUME.DELETE | 6 | 2014-11-20 00:08:39 | 1 |
9 | ROOT-9 |NULL |NULL |NULL | NULL
| 0 | NULL |
++-++-+-+-++-+-+-++---+--+
14 rows in set (0.00 sec)
{noformat}
=
Destroy VM Job Log:
=
{noformat}
2014-11-20 00:08:35,021 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(catalina-exec-11:ctx-fb3a3d80 ctx-67753d29) submit async job-50, details:
[jira] [Updated] (CLOUDSTACK-7948) [Automation] Two VOLUME.DELETE Events are being registered instead of one - On Destroying a User VM belonging to a Project
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damodar Reddy T updated CLOUDSTACK-7948:
Assignee: Kishan Kavala (was: Damodar Reddy T)
[Automation] Two VOLUME.DELETE Events are being registered instead of one -
On Destroying a User VM belonging to a Project
Key: CLOUDSTACK-7948
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7948
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Kishan Kavala
Fix For: 4.5.0
==
User VM in Project Events Information in the Database:
==
{noformat}
mysql select * from usage_event where account_id=6;
++-++-+-+-++-+-+-++---+--+
| id | type| account_id | created | zone_id |
resource_id | resource_name | offering_id | template_id | size|
resource_type | processed | virtual_size |
++-++-+-+-++-+-+-++---+--+
| 19 | TEMPLATE.CREATE | 6 | 2014-11-19 21:28:14 | 1 |
202 | TestTemplate-1 |NULL |NULL | 1708331520 | NULL
| 0 | 8589934592 |
| 20 | VOLUME.CREATE | 6 | 2014-11-19 21:32:23 | 1 |
9 | ROOT-9 | 1 | 5 | 21474836480 | NULL
| 0 | NULL |
| 21 | VM.CREATE | 6 | 2014-11-19 21:32:23 | 1 |
9 | Project-VM-1 | 1 | 5 |NULL |
XenServer | 0 | NULL |
| 22 | NET.IPASSIGN| 6 | 2014-11-19 21:32:25 | 1 |
6 | 10.219.196.151 |NULL | 0 | 0 |
DirectAttached | 0 | NULL |
| 23 | NETWORK.OFFERING.ASSIGN | 6 | 2014-11-19 21:32:33 | 1 |
9 | 19 | 6 |NULL | 1 | NULL
| 0 | NULL |
| 24 | SG.ASSIGN | 6 | 2014-11-19 21:32:33 | 1 |
9 | NULL | 4 |NULL |NULL | NULL
| 0 | NULL |
| 25 | VM.START| 6 | 2014-11-19 21:32:33 | 1 |
9 | Project-VM-1 | 1 | 5 |NULL |
XenServer | 0 | NULL |
| 26 | SG.REMOVE | 6 | 2014-11-19 21:33:10 | 1 |
9 | NULL | 4 |NULL |NULL | NULL
| 0 | NULL |
| 27 | VM.STOP | 6 | 2014-11-19 21:33:10 | 1 |
9 | Project-VM-1 | 1 | 5 |NULL |
XenServer | 0 | NULL |
| 28 | NETWORK.OFFERING.REMOVE | 6 | 2014-11-19 21:33:10 | 1 |
9 | 19 | 6 |NULL | 0 | NULL
| 0 | NULL |
| 31 | VM.DESTROY | 6 | 2014-11-20 00:08:37 | 1 |
9 | Project-VM-1 | 1 | 5 |NULL |
XenServer | 0 | NULL |
| 32 | VOLUME.DELETE | 6 | 2014-11-20 00:08:37 | 1 |
9 | ROOT-9 |NULL |NULL |NULL | NULL
| 0 | NULL |
| 33 | NET.IPRELEASE | 6 | 2014-11-20 00:08:39 | 1 |
6 | 10.219.196.151 |NULL | 0 | 0 |
DirectAttached | 0 | NULL |
| 34 | VOLUME.DELETE | 6 | 2014-11-20 00:08:39 | 1 |
9 | ROOT-9 |NULL |NULL |NULL | NULL
| 0 | NULL |
++-++-+-+-++-+-+-++---+--+
14 rows in set (0.00 sec)
{noformat}
=
Destroy VM Job Log:
=
{noformat}
2014-11-20 00:08:35,021 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(catalina-exec-11:ctx-fb3a3d80 ctx-67753d29) submit async job-50,
[jira] [Updated] (CLOUDSTACK-7460) [LXC][RHEl7] Agent installaion fails if Management server is already installed on the same machine
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T updated CLOUDSTACK-7460: Priority: Minor (was: Major) [LXC][RHEl7] Agent installaion fails if Management server is already installed on the same machine -- Key: CLOUDSTACK-7460 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7460 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.5.0 Reporter: shweta agarwal Assignee: Damodar Reddy T Priority: Minor Fix For: Future Repro steps: on rhel 7 Machine. First install MS and try installing Agent on the same machine Bug: Agent installation will fail with following error : Transaction check error: file /var/log/cloudstack/agent from install of cloudstack-agent-4.5.0-SNAPSHOT.el7.x86_64 conflicts with file from package cloudstack-management-4.5.0-SNAPSHOT.el7.x86_64 Error Summary - Done -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7923) RabbitMQ integration, make SSL protocol configurable rather than hard coded
Damodar Reddy T created CLOUDSTACK-7923: --- Summary: RabbitMQ integration, make SSL protocol configurable rather than hard coded Key: CLOUDSTACK-7923 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7923 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: Damodar Reddy T Assignee: Damodar Reddy T Fix For: 4.5.0 In the current RabbitMQ integration implementation we are using default SSL Context which uses SSLv3 by default. Make it configurable so that let the users decide which protocol to be used. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7877) The NET.IPRELEASE events are not added to usage_event on IP range deletion from Physical Networks
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damodar Reddy T resolved CLOUDSTACK-7877.
-
Resolution: Fixed
The NET.IPRELEASE events are not added to usage_event on IP range deletion
from Physical Networks
-
Key: CLOUDSTACK-7877
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7877
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, 4.3.1
Reporter: Damodar Reddy T
Assignee: Damodar Reddy T
Fix For: 4.5.0
The NET.IPRELEASE events are not added to usage_event on IP range deletion
from Physical Networks
Repro steps:
===
- Create a zone with Advanced Networking (non Basic)
- Navigate to Physical Networks
- Created an IP Range for a physical network and before clicking “Add”,
choose to “Add Account”.
- The range was created and in the cloud database, in the cloud.usage_event
table the following events are created:
{noformat}
mysql select id,type,account_id,created,resource_name from cloud.usage_event;
++-++-+---+
| id | type| account_id | created |
resource_name |
++-++-+---+
(...)
| 19 | NET.IPASSIGN| 4| 2014-09-12 07:57:36 |
91.198.163.10 |
| 20 | NET.IPASSIGN| 4 | 2014-09-12 07:57:36 |
91.198.163.11 |
| 21 | NET.IPASSIGN| 4 | 2014-09-12 07:57:36 |
91.198.163.12 |
| 22 | NET.IPASSIGN| 4 | 2014-09-12 07:57:36 |
91.198.163.13 |
| 23 | NET.IPASSIGN| 4 | 2014-09-12 07:57:36 |
91.198.163.14 |
| 24 | NET.IPASSIGN| 4 | 2014-09-12 07:57:36 |
91.198.163.15 |
| 25 | NET.IPASSIGN| 4 | 2014-09-12 07:57:36 |
91.198.163.16 |
| 26 | NET.IPASSIGN| 4| 2014-09-12 07:57:36 |
91.198.163.17 |
| 27 | NET.IPASSIGN| 4 | 2014-09-12 07:57:36 |
91.198.163.18 |
| 28 | NET.IPASSIGN| 4 | 2014-09-12 07:57:36 |
91.198.163.19 |
| 29 | NET.IPASSIGN| 4 | 2014-09-12 07:57:36 |
91.198.163.20 |
++-++-+---+
{noformat}
- As you can see it’s assigned to the account_id=4
- Now, I’ve removed the IP range from the UI and checked the database again.
- noticed that no records have been added to the table, whereas I’d expect
NET.IPRELEASE to have been inserted there for each IP address.
As a result, the Usage doesn't release the IP in the usage_ip_address
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7877) The NET.IPRELEASE events are not added to usage_event on IP range deletion from Physical Networks
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damodar Reddy T updated CLOUDSTACK-7877:
Status: Reviewable (was: In Progress)
The NET.IPRELEASE events are not added to usage_event on IP range deletion
from Physical Networks
-
Key: CLOUDSTACK-7877
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7877
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, 4.3.1
Reporter: Damodar Reddy T
Assignee: Damodar Reddy T
Fix For: 4.5.0
The NET.IPRELEASE events are not added to usage_event on IP range deletion
from Physical Networks
Repro steps:
===
- Create a zone with Advanced Networking (non Basic)
- Navigate to Physical Networks
- Created an IP Range for a physical network and before clicking “Add”,
choose to “Add Account”.
- The range was created and in the cloud database, in the cloud.usage_event
table the following events are created:
{noformat}
mysql select id,type,account_id,created,resource_name from cloud.usage_event;
++-++-+---+
| id | type| account_id | created |
resource_name |
++-++-+---+
(...)
| 19 | NET.IPASSIGN| 4| 2014-09-12 07:57:36 |
91.198.163.10 |
| 20 | NET.IPASSIGN| 4 | 2014-09-12 07:57:36 |
91.198.163.11 |
| 21 | NET.IPASSIGN| 4 | 2014-09-12 07:57:36 |
91.198.163.12 |
| 22 | NET.IPASSIGN| 4 | 2014-09-12 07:57:36 |
91.198.163.13 |
| 23 | NET.IPASSIGN| 4 | 2014-09-12 07:57:36 |
91.198.163.14 |
| 24 | NET.IPASSIGN| 4 | 2014-09-12 07:57:36 |
91.198.163.15 |
| 25 | NET.IPASSIGN| 4 | 2014-09-12 07:57:36 |
91.198.163.16 |
| 26 | NET.IPASSIGN| 4| 2014-09-12 07:57:36 |
91.198.163.17 |
| 27 | NET.IPASSIGN| 4 | 2014-09-12 07:57:36 |
91.198.163.18 |
| 28 | NET.IPASSIGN| 4 | 2014-09-12 07:57:36 |
91.198.163.19 |
| 29 | NET.IPASSIGN| 4 | 2014-09-12 07:57:36 |
91.198.163.20 |
++-++-+---+
{noformat}
- As you can see it’s assigned to the account_id=4
- Now, I’ve removed the IP range from the UI and checked the database again.
- noticed that no records have been added to the table, whereas I’d expect
NET.IPRELEASE to have been inserted there for each IP address.
As a result, the Usage doesn't release the IP in the usage_ip_address
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7886) cs:rabbitMQ:cloudstackoperations like deployvm,deleteNW are failing if CS fail to contact rabbit mq server
Damodar Reddy T created CLOUDSTACK-7886: --- Summary: cs:rabbitMQ:cloudstackoperations like deployvm,deleteNW are failing if CS fail to contact rabbit mq server Key: CLOUDSTACK-7886 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7886 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: Damodar Reddy T Assignee: Damodar Reddy T Priority: Critical Fix For: 4.5.0 Enable RabbitMQ Event Bus configuration to publish events from CS. Once management server is started stop the Rabbit MQ server which is interacting by management server and try to do async API operations like deployVm delete NW and these operations are failing as it is not able to publish events to Rabbit MQ. Where as in all other cases the operations get succeeded. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7886) cs:rabbitMQ:cloudstackoperations like deployvm,deleteNW are failing if CS fail to contact rabbit mq server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T resolved CLOUDSTACK-7886. - Resolution: Fixed cs:rabbitMQ:cloudstackoperations like deployvm,deleteNW are failing if CS fail to contact rabbit mq server --- Key: CLOUDSTACK-7886 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7886 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: Damodar Reddy T Assignee: Damodar Reddy T Priority: Critical Fix For: 4.5.0 Enable RabbitMQ Event Bus configuration to publish events from CS. Once management server is started stop the Rabbit MQ server which is interacting by management server and try to do async API operations like deployVm delete NW and these operations are failing as it is not able to publish events to Rabbit MQ. Where as in all other cases the operations get succeeded. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7792) Usage Events to be captured based on Volume State Machine
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T resolved CLOUDSTACK-7792. - Resolution: Fixed Usage Events to be captured based on Volume State Machine - Key: CLOUDSTACK-7792 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7792 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Usage Reporter: Damodar Reddy T Assignee: Damodar Reddy T Fix For: 4.6.0 Currently in CloudStack the Usage Events for Volume related actions are captured directly at various places. But actually Volume has a State Machine which can be used to capture Usage Events for volume similar to VM Usage Events -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7830) Usage Job fails with Data too long for column 'user_name'
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damodar Reddy T resolved CLOUDSTACK-7830.
-
Resolution: Fixed
Fix Version/s: (was: Future)
Usage Job fails with Data too long for column 'user_name'
Key: CLOUDSTACK-7830
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7830
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Usage
Affects Versions: 4.4.0
Reporter: Damodar Reddy T
Assignee: Damodar Reddy T
Fix For: 4.5.0
ISSUE:
==
Usage Job is failing with the following exception in the logs
{noformat}
2014-03-25 00:15:00,239 DEBUG [cloud.usage.UsageManagerImpl]
(Usage-Job-1:null) Creating VPN user: 4 for account: 13
2014-03-25 00:15:00,240 DEBUG [db.Transaction.Transaction] (Usage-Job-1:null)
Rolling back the transaction: Time = 2 Name =
-UsageEventDaoImpl.getRecentEvents:93-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-UsageManagerImpl.parse:541-UsageManagerImpl.run:334-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRunAndReset:351-FutureTask.runAndReset:178-ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201:165-ScheduledThreadPoolExecutor$ScheduledFutureTask.run:267-ThreadPoolExecutor.runWorker:1146-ThreadPoolExecutor$Worker.run:615-Thread.run:701;
called by
-Transaction.rollback:897-Transaction.removeUpTo:840-Transaction.close:664-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:133-UsageManagerImpl.createVPNUserEvent:1583-UsageManagerImpl.createHelperRecord:893-UsageManagerImpl.parse:562-UsageManagerImpl.run:334-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRunAndReset:351-FutureTask.runAndReset:178
2014-03-25 00:15:00,252 ERROR [cloud.usage.UsageManagerImpl]
(Usage-Job-1:null) Exception in usage manager
com.cloud.utils.exception.CloudRuntimeException: DB Exception on:
com.mysql.jdbc.JDBC4PreparedStatement@74b4624e: INSERT INTO usage_vpn_user
(usage_vpn_user.zone_id, usage_vpn_user.account_id, usage_vpn_user.domain_id,
usage_vpn_user.user_id, usage_vpn_user.user_name, usage_vpn_user.created,
usage_vpn_user.deleted) VALUES (0, 13, 14, 4,
_binary'timothy.lother...@dcxclouddemo.co.za', '2014-03-11 14:36:50', null)
at com.cloud.utils.db.GenericDaoBase.persist(GenericDaoBase.java:1348)
at
com.cloud.usage.dao.UsageVPNUserDaoImpl_EnhancerByCloudStack_60ddd7cc.CGLIB$persist$45(generated)
at
com.cloud.usage.dao.UsageVPNUserDaoImpl_EnhancerByCloudStack_60ddd7cc_FastClassByCloudStack_d13d3284.invoke(generated)
at net.sf.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
com.cloud.usage.dao.UsageVPNUserDaoImpl_EnhancerByCloudStack_60ddd7cc.persist(generated)
at
com.cloud.usage.UsageManagerImpl.createVPNUserEvent(UsageManagerImpl.java:1583)
at
com.cloud.usage.UsageManagerImpl.createHelperRecord(UsageManagerImpl.java:893)
at com.cloud.usage.UsageManagerImpl.parse(UsageManagerImpl.java:562)
at com.cloud.usage.UsageManagerImpl.run(UsageManagerImpl.java:334)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:701)
Caused by: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long
for column 'user_name' at row 1
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4072)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7792) Usage Events to be captured based on Volume State Machine
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T updated CLOUDSTACK-7792: Fix Version/s: (was: 4.5.0) 4.6.0 Usage Events to be captured based on Volume State Machine - Key: CLOUDSTACK-7792 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7792 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Usage Reporter: Damodar Reddy T Assignee: Damodar Reddy T Fix For: 4.6.0 Currently in CloudStack the Usage Events for Volume related actions are captured directly at various places. But actually Volume has a State Machine which can be used to capture Usage Events for volume similar to VM Usage Events -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7851) MS does not start after the VM it is running on is rebooted
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T resolved CLOUDSTACK-7851. - Resolution: Fixed MS does not start after the VM it is running on is rebooted --- Key: CLOUDSTACK-7851 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7851 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Environment: Centos OS Reporter: Damodar Reddy T Assignee: Damodar Reddy T Priority: Critical Fix For: 4.5.0 After installing management server on centos and try to reboot the machine. It will not start the management server automatically. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7843) sync Job Failures always reported as success on Event Bus
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damodar Reddy T resolved CLOUDSTACK-7843.
-
Resolution: Fixed
sync Job Failures always reported as success on Event Bus
--
Key: CLOUDSTACK-7843
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7843
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.4.0
Reporter: Damodar Reddy T
Assignee: Damodar Reddy T
Fix For: 4.5.0
For example, addition of nic to a VM is failed. Management log files show
this as failed.
{ queryasyncjobresultresponse :
{accountid:eddeb7f4-dbc5-11e3-b9c8-9e300504069a,userid:eddf0399-dbc5-11e3-b9c8-9e300504069a,cmd:org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd,jobstatus:2,jobprocstatus:0,jobresultcode:530,jobresulttype:object,jobresult:{errorcode:530,errortext:A
NIC already exists for VM:i-615-879-VM in network:
fe60e938-c186-4dda-a37c-732ac66fd381},created:2014-09-15T16:06:48-0400,jobid:34dd7fb6-d350-430d-ae35-5f63d0986d4a}
}
But in event bus it shows as the job is success.
management-server.AsyncJobEvent.complete.None.*
{\instanceType\:\None\,\jobId\:\34dd7fb6-d350-430d-ae35-5f63d0986d4a\,\processStatus\:\0\,\commandEventType\:\NIC.CREATE\,\resultCode\:\0\,\command\:\org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd\,\account\:\eddeb7f4-dbc5-11e3-b9c8-9e300504069a\,\user\:\eddf0399-dbc5-11e3-b9c8-9e300504069a\}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7877) The NET.IPRELEASE events are not added to usage_event on IP range deletion from Physical Networks
Damodar Reddy T created CLOUDSTACK-7877:
---
Summary: The NET.IPRELEASE events are not added to usage_event on
IP range deletion from Physical Networks
Key: CLOUDSTACK-7877
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7877
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, 4.3.1
Reporter: Damodar Reddy T
Assignee: Damodar Reddy T
Fix For: 4.5.0
The NET.IPRELEASE events are not added to usage_event on IP range deletion from
Physical Networks
Repro steps:
===
- Create a zone with Advanced Networking (non Basic)
- Navigate to Physical Networks
- Created an IP Range for a physical network and before clicking “Add”, choose
to “Add Account”.
- The range was created and in the cloud database, in the cloud.usage_event
table the following events are created:
{noformat}
mysql select id,type,account_id,created,resource_name from cloud.usage_event;
++-++-+---+
| id | type| account_id | created |
resource_name |
++-++-+---+
(...)
| 19 | NET.IPASSIGN| 4| 2014-09-12 07:57:36 |
91.198.163.10 |
| 20 | NET.IPASSIGN| 4 | 2014-09-12 07:57:36 |
91.198.163.11 |
| 21 | NET.IPASSIGN| 4 | 2014-09-12 07:57:36 |
91.198.163.12 |
| 22 | NET.IPASSIGN| 4 | 2014-09-12 07:57:36 |
91.198.163.13 |
| 23 | NET.IPASSIGN| 4 | 2014-09-12 07:57:36 |
91.198.163.14 |
| 24 | NET.IPASSIGN| 4 | 2014-09-12 07:57:36 |
91.198.163.15 |
| 25 | NET.IPASSIGN| 4 | 2014-09-12 07:57:36 |
91.198.163.16 |
| 26 | NET.IPASSIGN| 4| 2014-09-12 07:57:36 |
91.198.163.17 |
| 27 | NET.IPASSIGN| 4 | 2014-09-12 07:57:36 |
91.198.163.18 |
| 28 | NET.IPASSIGN| 4 | 2014-09-12 07:57:36 |
91.198.163.19 |
| 29 | NET.IPASSIGN| 4 | 2014-09-12 07:57:36 |
91.198.163.20 |
++-++-+---+
{noformat}
- As you can see it’s assigned to the account_id=4
- Now, I’ve removed the IP range from the UI and checked the database again.
- noticed that no records have been added to the table, whereas I’d expect
NET.IPRELEASE to have been inserted there for each IP address.
As a result, the Usage doesn't release the IP in the usage_ip_address
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7460) [LXC][RHEl7] Agent installaion fails if Management server is already installed on the same machine
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T updated CLOUDSTACK-7460: Fix Version/s: (was: 4.5.0) [LXC][RHEl7] Agent installaion fails if Management server is already installed on the same machine -- Key: CLOUDSTACK-7460 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7460 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.5.0 Reporter: shweta agarwal Assignee: Damodar Reddy T Repro steps: on rhel 7 Machine. First install MS and try installing Agent on the same machine Bug: Agent installation will fail with following error : Transaction check error: file /var/log/cloudstack/agent from install of cloudstack-agent-4.5.0-SNAPSHOT.el7.x86_64 conflicts with file from package cloudstack-management-4.5.0-SNAPSHOT.el7.x86_64 Error Summary - Done -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7249) Enable Password Strength check for all users
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T updated CLOUDSTACK-7249: Fix Version/s: (was: 4.5.0) Future Enable Password Strength check for all users Key: CLOUDSTACK-7249 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7249 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: Damodar Reddy T Assignee: Damodar Reddy T Fix For: Future Currently we do not show the password strength of a user for his chosen password int he API response. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-6834) [Windows] Feedback Items
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T updated CLOUDSTACK-6834: Fix Version/s: (was: 4.5.0) Future [Windows] Feedback Items Key: CLOUDSTACK-6834 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6834 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: Future Reporter: Damodar Reddy T Assignee: Damodar Reddy T Fix For: Future The feed back items received internally. 1. Need to add more fields to the database creation wizard 2. Remove Complete Option 3. Some description changes words like CloudStack etc 4. Change Default installation location if possible include version number 5. Mysql Connector Installer along with other dependecies 6. Add run Service Checkbox 7. Add ReadMe checkbox 8. If possible enable logs for Custom Actions that are executed as part of installation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7142) Coverity Issues fixes and better error messages
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T updated CLOUDSTACK-7142: Fix Version/s: (was: 4.5.0) Future Coverity Issues fixes and better error messages --- Key: CLOUDSTACK-7142 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7142 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: Damodar Reddy T Assignee: Damodar Reddy T Priority: Minor Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-6105) Windowsfication of CloudStack Management Server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T updated CLOUDSTACK-6105: Fix Version/s: (was: 4.5.0) Future Windowsfication of CloudStack Management Server --- Key: CLOUDSTACK-6105 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6105 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.3.0 Reporter: Damodar Reddy T Assignee: Damodar Reddy T Labels: features Fix For: Future Currently Management Server runs on Linux based operating systems. Though it runs on windows under cygwin terminal, there is a need to run it on windows without dependency on cygwin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-6703) [Windows] Try to install as a normal java service (Spawn a java thread)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T updated CLOUDSTACK-6703: Fix Version/s: (was: 4.5.0) Future [Windows] Try to install as a normal java service (Spawn a java thread) --- Key: CLOUDSTACK-6703 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6703 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.5.0 Reporter: Damodar Reddy T Assignee: Damodar Reddy T Fix For: Future 1, Currently it is started as s tomcat service. Instead of that try to spawn a java thread service 2. Try to add Cloud stack Version some where in the service name or in the registry keys -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-6704) [Windows] Localization of the windows installer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T updated CLOUDSTACK-6704: Fix Version/s: (was: 4.5.0) Future [Windows] Localization of the windows installer --- Key: CLOUDSTACK-6704 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6704 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Reporter: Damodar Reddy T Assignee: Damodar Reddy T Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-5616) [DBHA]:There is no way to know to which DB is the CS writing in the case of DBHA.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T updated CLOUDSTACK-5616: Fix Version/s: (was: 4.4.0) Future [DBHA]:There is no way to know to which DB is the CS writing in the case of DBHA. - Key: CLOUDSTACK-5616 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5616 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.3.0 Reporter: Kiran Koneti Assignee: Damodar Reddy T Fix For: Future At any instance of time we never know to which database (either M1 or M2) is the CS writing the db changes changes. This creates some problems at the customer environment like 1)The customer doesn't have chance to go for maintenance or manual do a switch over from one db to other if he has some network maintenance to perform. 2)There is no chance to check whether the db switch over has happened from the slave to master after the db.cloud.secondsBeforeRetryMaster interval if the master comes back by this time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7843) sync Job Failures always reported as success on Event Bus
Damodar Reddy T created CLOUDSTACK-7843:
---
Summary: sync Job Failures always reported as success on Event Bus
Key: CLOUDSTACK-7843
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7843
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.4.0
Reporter: Damodar Reddy T
Assignee: Damodar Reddy T
Fix For: 4.5.0
For example, addition of nic to a VM is failed. Management log files show this
as failed.
{ queryasyncjobresultresponse :
{accountid:eddeb7f4-dbc5-11e3-b9c8-9e300504069a,userid:eddf0399-dbc5-11e3-b9c8-9e300504069a,cmd:org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd,jobstatus:2,jobprocstatus:0,jobresultcode:530,jobresulttype:object,jobresult:{errorcode:530,errortext:A
NIC already exists for VM:i-615-879-VM in network:
fe60e938-c186-4dda-a37c-732ac66fd381},created:2014-09-15T16:06:48-0400,jobid:34dd7fb6-d350-430d-ae35-5f63d0986d4a}
}
But in event bus it shows as the job is success.
management-server.AsyncJobEvent.complete.None.*
{\instanceType\:\None\,\jobId\:\34dd7fb6-d350-430d-ae35-5f63d0986d4a\,\processStatus\:\0\,\commandEventType\:\NIC.CREATE\,\resultCode\:\0\,\command\:\org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd\,\account\:\eddeb7f4-dbc5-11e3-b9c8-9e300504069a\,\user\:\eddf0399-dbc5-11e3-b9c8-9e300504069a\}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7851) MS does not start after the VM it is running on is rebooted
Damodar Reddy T created CLOUDSTACK-7851: --- Summary: MS does not start after the VM it is running on is rebooted Key: CLOUDSTACK-7851 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7851 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Environment: Centos OS Reporter: Damodar Reddy T Assignee: Damodar Reddy T Priority: Critical Fix For: 4.5.0 After installing management server on centos and try to reboot the machine. It will not start the management server automatically. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7830) Usage Job fails with Data too long for column 'user_name'
Damodar Reddy T created CLOUDSTACK-7830:
---
Summary: Usage Job fails with Data too long for column
'user_name'
Key: CLOUDSTACK-7830
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7830
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Usage
Affects Versions: 4.4.0
Reporter: Damodar Reddy T
Assignee: Damodar Reddy T
Fix For: Future, 4.5.0
ISSUE:
==
Usage Job is failing with the following exception in the logs
{noformat}
2014-03-25 00:15:00,239 DEBUG [cloud.usage.UsageManagerImpl] (Usage-Job-1:null)
Creating VPN user: 4 for account: 13
2014-03-25 00:15:00,240 DEBUG [db.Transaction.Transaction] (Usage-Job-1:null)
Rolling back the transaction: Time = 2 Name =
-UsageEventDaoImpl.getRecentEvents:93-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-UsageManagerImpl.parse:541-UsageManagerImpl.run:334-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRunAndReset:351-FutureTask.runAndReset:178-ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201:165-ScheduledThreadPoolExecutor$ScheduledFutureTask.run:267-ThreadPoolExecutor.runWorker:1146-ThreadPoolExecutor$Worker.run:615-Thread.run:701;
called by
-Transaction.rollback:897-Transaction.removeUpTo:840-Transaction.close:664-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:133-UsageManagerImpl.createVPNUserEvent:1583-UsageManagerImpl.createHelperRecord:893-UsageManagerImpl.parse:562-UsageManagerImpl.run:334-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRunAndReset:351-FutureTask.runAndReset:178
2014-03-25 00:15:00,252 ERROR [cloud.usage.UsageManagerImpl] (Usage-Job-1:null)
Exception in usage manager
com.cloud.utils.exception.CloudRuntimeException: DB Exception on:
com.mysql.jdbc.JDBC4PreparedStatement@74b4624e: INSERT INTO usage_vpn_user
(usage_vpn_user.zone_id, usage_vpn_user.account_id, usage_vpn_user.domain_id,
usage_vpn_user.user_id, usage_vpn_user.user_name, usage_vpn_user.created,
usage_vpn_user.deleted) VALUES (0, 13, 14, 4,
_binary'timothy.lother...@dcxclouddemo.co.za', '2014-03-11 14:36:50', null)
at com.cloud.utils.db.GenericDaoBase.persist(GenericDaoBase.java:1348)
at
com.cloud.usage.dao.UsageVPNUserDaoImpl_EnhancerByCloudStack_60ddd7cc.CGLIB$persist$45(generated)
at
com.cloud.usage.dao.UsageVPNUserDaoImpl_EnhancerByCloudStack_60ddd7cc_FastClassByCloudStack_d13d3284.invoke(generated)
at net.sf.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
com.cloud.usage.dao.UsageVPNUserDaoImpl_EnhancerByCloudStack_60ddd7cc.persist(generated)
at
com.cloud.usage.UsageManagerImpl.createVPNUserEvent(UsageManagerImpl.java:1583)
at
com.cloud.usage.UsageManagerImpl.createHelperRecord(UsageManagerImpl.java:893)
at com.cloud.usage.UsageManagerImpl.parse(UsageManagerImpl.java:562)
at com.cloud.usage.UsageManagerImpl.run(UsageManagerImpl.java:334)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:701)
Caused by: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long
for column 'user_name' at row 1
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4072)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7792) Usage Events to be captured based on Volume State Machine
Damodar Reddy T created CLOUDSTACK-7792: --- Summary: Usage Events to be captured based on Volume State Machine Key: CLOUDSTACK-7792 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7792 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server, Usage Reporter: Damodar Reddy T Fix For: 4.5.0 Currently in CloudStack the Usage Events for Volume related actions are captured directly at various places. But actually Volume has a State Machine which can be used to capture Usage Events for volume similar to VM Usage Events -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7729) listVMSnapshot API not returning parent id in response
Damodar Reddy T created CLOUDSTACK-7729: --- Summary: listVMSnapshot API not returning parent id in response Key: CLOUDSTACK-7729 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7729 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: Damodar Reddy T Assignee: Damodar Reddy T listVMSnapshot API not returning parent id in response. Documentation says listVMSnapshot returns parent id as well as parent name. BUT only parent name is getting in the response. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7729) listVMSnapshot API not returning parent id in response
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T resolved CLOUDSTACK-7729. - Resolution: Fixed listVMSnapshot API not returning parent id in response -- Key: CLOUDSTACK-7729 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7729 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: Damodar Reddy T Assignee: Damodar Reddy T listVMSnapshot API not returning parent id in response. Documentation says listVMSnapshot returns parent id as well as parent name. BUT only parent name is getting in the response. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-7560) Usage Event is not generated when VM state is transited from RUNNING to STOPPED directly
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damodar Reddy T reassigned CLOUDSTACK-7560:
---
Assignee: Damodar Reddy T
Usage Event is not generated when VM state is transited from RUNNING to
STOPPED directly
Key: CLOUDSTACK-7560
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7560
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Usage
Affects Versions: 4.5.0
Reporter: Damodar Reddy T
Assignee: Damodar Reddy T
Fix For: Future
When Maagement server is not able to detect VM state, after a specific time
it will try to change the RUNNING state to STOPPED state directly without
STOPPING state in between. Which is causing the event not to be generated and
now if you DESTROY the VM still it will generate the usage records for a
period of 24 hrs every day.
Logs are attached below...
2014-05-15 16:13:25,197 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgent-117:ctx-775a3f34) Run missing VM report. current time:
1400163205197
2014-05-15 16:13:25,197 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgent-117:ctx-775a3f34) Detected missing VM. host: 1, vm id: 106,
power state: PowerReportMissing, last state update: 1400162537000
2014-05-15 16:13:25,197 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgent-117:ctx-775a3f34) vm id: 106 - time since last state
update(668197ms) has passed graceful period
2014-05-15 16:13:25,202 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgent-117:ctx-775a3f34) VM state report is updated. host: 1, vm id:
106, power state: PowerReportMissing
2014-05-15 16:13:25,207 INFO [c.c.v.VirtualMachineManagerImpl]
(DirectAgent-117:ctx-775a3f34) VM i-5-106-VM is at Running and we received a
power-off report while there is no pending jobs on it
2014-05-15 16:13:25,210 DEBUG [c.c.a.t.Request]
(DirectAgent-117:ctx-775a3f34) Seq 1-1971781673: Sending { Cmd , MgmtId:
20750978301280, via: 1(XSMASTER-5), Ver: v1, Flags: 100111,
[{com.cloud.agent.api.StopCommand:{isProxy:false,executeInSequence:true,checkBeforeCleanup:true,vmName:i-5-106-VM,wait:0}}]
}
2014-05-15 16:13:25,210 DEBUG [c.c.a.t.Request]
(DirectAgent-117:ctx-775a3f34) Seq 1-1971781673: Executing: { Cmd , MgmtId:
20750978301280, via: 1(XSMASTER-5), Ver: v1, Flags: 100111,
[{com.cloud.agent.api.StopCommand:{isProxy:false,executeInSequence:true,checkBeforeCleanup:true,vmName:i-5-106-VM,wait:0}}]
}
2014-05-15 16:13:25,210 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-18:ctx-7180bb9c) Seq 1-1971781673: Executing request
2014-05-15 16:13:25,249 DEBUG [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-18:ctx-7180bb9c) 9. The VM i-5-106-VM is in Stopping state
2014-05-15 16:13:25,293 INFO [c.c.h.x.r.XenServer56Resource]
(DirectAgent-18:ctx-7180bb9c) Catch com.xensource.xenapi.Types$VifInUse:
failed to destory VLAN eth0 on host c4080dac-f034-452f-9203-8e69d5512315 due
to Network has active VIFs
2014-05-15 16:13:25,294 DEBUG [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-18:ctx-7180bb9c) 10. The VM i-5-106-VM is in Stopped state
2014-05-15 16:13:25,294 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-18:ctx-7180bb9c) Seq 1-1971781673: Response Received:
2014-05-15 16:13:25,294 DEBUG [c.c.a.t.Request] (DirectAgent-18:ctx-7180bb9c)
Seq 1-1971781673: Processing: { Ans: , MgmtId: 20750978301280, via: 1, Ver:
v1, Flags: 110,
[{com.cloud.agent.api.StopAnswer:{platform:viridian:true;acpi:1;apic:true;pae:true;nx:true,result:true,details:Stop
VM i-5-106-VM Succeed,wait:0}}] }
2014-05-15 16:13:25,294 DEBUG [c.c.a.t.Request]
(DirectAgent-117:ctx-775a3f34) Seq 1-1971781673: Received: { Ans: , MgmtId:
20750978301280, via: 1, Ver: v1, Flags: 110, { StopAnswer } }
2014-05-15 16:13:25,301 DEBUG [c.c.a.m.AgentAttache]
(DirectAgent-18:ctx-7180bb9c) Seq 1-1971781673: No more commands found
2014-05-15 16:13:25,365 DEBUG [c.c.c.CapacityManagerImpl]
(DirectAgent-117:ctx-775a3f34) VM state transitted from :Running to Stopped
with event: FollowAgentPowerOffReportvm's original host id: 1 new host id:
null host id before state transition: 1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7560) Usage Event is not generated when VM state is transited from RUNNING to STOPPED directly
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damodar Reddy T resolved CLOUDSTACK-7560.
-
Resolution: Fixed
Fix Version/s: (was: Future)
4.5.0
Got fixed as part of https://issues.apache.org/jira/browse/CLOUDSTACK-7648
Usage Event is not generated when VM state is transited from RUNNING to
STOPPED directly
Key: CLOUDSTACK-7560
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7560
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Usage
Affects Versions: 4.5.0
Reporter: Damodar Reddy T
Assignee: Damodar Reddy T
Fix For: 4.5.0
When Maagement server is not able to detect VM state, after a specific time
it will try to change the RUNNING state to STOPPED state directly without
STOPPING state in between. Which is causing the event not to be generated and
now if you DESTROY the VM still it will generate the usage records for a
period of 24 hrs every day.
Logs are attached below...
2014-05-15 16:13:25,197 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgent-117:ctx-775a3f34) Run missing VM report. current time:
1400163205197
2014-05-15 16:13:25,197 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgent-117:ctx-775a3f34) Detected missing VM. host: 1, vm id: 106,
power state: PowerReportMissing, last state update: 1400162537000
2014-05-15 16:13:25,197 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgent-117:ctx-775a3f34) vm id: 106 - time since last state
update(668197ms) has passed graceful period
2014-05-15 16:13:25,202 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgent-117:ctx-775a3f34) VM state report is updated. host: 1, vm id:
106, power state: PowerReportMissing
2014-05-15 16:13:25,207 INFO [c.c.v.VirtualMachineManagerImpl]
(DirectAgent-117:ctx-775a3f34) VM i-5-106-VM is at Running and we received a
power-off report while there is no pending jobs on it
2014-05-15 16:13:25,210 DEBUG [c.c.a.t.Request]
(DirectAgent-117:ctx-775a3f34) Seq 1-1971781673: Sending { Cmd , MgmtId:
20750978301280, via: 1(XSMASTER-5), Ver: v1, Flags: 100111,
[{com.cloud.agent.api.StopCommand:{isProxy:false,executeInSequence:true,checkBeforeCleanup:true,vmName:i-5-106-VM,wait:0}}]
}
2014-05-15 16:13:25,210 DEBUG [c.c.a.t.Request]
(DirectAgent-117:ctx-775a3f34) Seq 1-1971781673: Executing: { Cmd , MgmtId:
20750978301280, via: 1(XSMASTER-5), Ver: v1, Flags: 100111,
[{com.cloud.agent.api.StopCommand:{isProxy:false,executeInSequence:true,checkBeforeCleanup:true,vmName:i-5-106-VM,wait:0}}]
}
2014-05-15 16:13:25,210 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-18:ctx-7180bb9c) Seq 1-1971781673: Executing request
2014-05-15 16:13:25,249 DEBUG [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-18:ctx-7180bb9c) 9. The VM i-5-106-VM is in Stopping state
2014-05-15 16:13:25,293 INFO [c.c.h.x.r.XenServer56Resource]
(DirectAgent-18:ctx-7180bb9c) Catch com.xensource.xenapi.Types$VifInUse:
failed to destory VLAN eth0 on host c4080dac-f034-452f-9203-8e69d5512315 due
to Network has active VIFs
2014-05-15 16:13:25,294 DEBUG [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-18:ctx-7180bb9c) 10. The VM i-5-106-VM is in Stopped state
2014-05-15 16:13:25,294 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-18:ctx-7180bb9c) Seq 1-1971781673: Response Received:
2014-05-15 16:13:25,294 DEBUG [c.c.a.t.Request] (DirectAgent-18:ctx-7180bb9c)
Seq 1-1971781673: Processing: { Ans: , MgmtId: 20750978301280, via: 1, Ver:
v1, Flags: 110,
[{com.cloud.agent.api.StopAnswer:{platform:viridian:true;acpi:1;apic:true;pae:true;nx:true,result:true,details:Stop
VM i-5-106-VM Succeed,wait:0}}] }
2014-05-15 16:13:25,294 DEBUG [c.c.a.t.Request]
(DirectAgent-117:ctx-775a3f34) Seq 1-1971781673: Received: { Ans: , MgmtId:
20750978301280, via: 1, Ver: v1, Flags: 110, { StopAnswer } }
2014-05-15 16:13:25,301 DEBUG [c.c.a.m.AgentAttache]
(DirectAgent-18:ctx-7180bb9c) Seq 1-1971781673: No more commands found
2014-05-15 16:13:25,365 DEBUG [c.c.c.CapacityManagerImpl]
(DirectAgent-117:ctx-775a3f34) VM state transitted from :Running to Stopped
with event: FollowAgentPowerOffReportvm's original host id: 1 new host id:
null host id before state transition: 1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (CLOUDSTACK-7671) [RHEL7] management server failed to start once machine is rebooted
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T reopened CLOUDSTACK-7671: - Assignee: Rayees Namathponnan (was: Damodar Reddy T) [RHEL7] management server failed to start once machine is rebooted -- Key: CLOUDSTACK-7671 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7671 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Damodar Reddy T Assignee: Rayees Namathponnan Repro stesp: Create a rhel 7 host Install MS Start MS Once MS is up and running . Reboot MS . Notice Cloudstack-management service status Bug: Notice MS fails to start even after calling service cloudstack-management restart it failed to start systemctl status cloudstack-management.service cloudstack-management.service - Citrix Cloud Plaltform Loaded: loaded (/usr/lib/systemd/system/cloudstack-management.service; enabled) Active: failed (Result: exit-code) since Tue 2014-09-23 12:10:09 IST; 1min 28s ago Process: 4618 ExecStart=/usr/sbin/cloudstack-management start (code=exited, status=1/FAILURE) Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: Starting Citrix Cloud Plaltform... Sep 23 12:10:09 Rack1Pod1Host27 cloudstack-management[4618]: /usr/sbin/tomcat: line 50: /var/run/cloudstack-management.pid: Permission denied Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: cloudstack-management.service: control process exited, code=exited status=1 Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: Failed to start Citrix Cloud Plaltform. Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: Unit cloudstack-management.service entered failed state. [root@Rack1Pod1Host27 run]# service cloudstack-management status Redirecting to /bin/systemctl status cloudstack-management.service cloudstack-management.service - Citrix Cloud Plaltform Loaded: loaded (/usr/lib/systemd/system/cloudstack-management.service; enabled) Active: failed (Result: exit-code) since Tue 2014-09-23 12:14:05 IST; 8s ago Process: 4691 ExecStart=/usr/sbin/cloudstack-management start (code=exited, status=1/FAILURE) Sep 23 12:14:05 Rack1Pod1Host27 cloudstack-management[4691]: /usr/sbin/tomcat: line 50: /var/run/cloudstack-management.pid: Permission denied Sep 23 12:14:05 Rack1Pod1Host27 systemd[1]: cloudstack-management.service: control process exited, code=exited status=1 Sep 23 12:14:05 Rack1Pod1Host27 systemd[1]: Failed to start Citrix Cloud Plaltform. Sep 23 12:14:05 Rack1Pod1Host27 systemd[1]: Unit cloudstack-management.service entered failed state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7671) [RHEL7] management server failed to start once machine is rebooted
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T resolved CLOUDSTACK-7671. - Resolution: Fixed [RHEL7] management server failed to start once machine is rebooted -- Key: CLOUDSTACK-7671 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7671 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Damodar Reddy T Assignee: Damodar Reddy T Repro stesp: Create a rhel 7 host Install MS Start MS Once MS is up and running . Reboot MS . Notice Cloudstack-management service status Bug: Notice MS fails to start even after calling service cloudstack-management restart it failed to start systemctl status cloudstack-management.service cloudstack-management.service - Citrix Cloud Plaltform Loaded: loaded (/usr/lib/systemd/system/cloudstack-management.service; enabled) Active: failed (Result: exit-code) since Tue 2014-09-23 12:10:09 IST; 1min 28s ago Process: 4618 ExecStart=/usr/sbin/cloudstack-management start (code=exited, status=1/FAILURE) Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: Starting Citrix Cloud Plaltform... Sep 23 12:10:09 Rack1Pod1Host27 cloudstack-management[4618]: /usr/sbin/tomcat: line 50: /var/run/cloudstack-management.pid: Permission denied Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: cloudstack-management.service: control process exited, code=exited status=1 Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: Failed to start Citrix Cloud Plaltform. Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: Unit cloudstack-management.service entered failed state. [root@Rack1Pod1Host27 run]# service cloudstack-management status Redirecting to /bin/systemctl status cloudstack-management.service cloudstack-management.service - Citrix Cloud Plaltform Loaded: loaded (/usr/lib/systemd/system/cloudstack-management.service; enabled) Active: failed (Result: exit-code) since Tue 2014-09-23 12:14:05 IST; 8s ago Process: 4691 ExecStart=/usr/sbin/cloudstack-management start (code=exited, status=1/FAILURE) Sep 23 12:14:05 Rack1Pod1Host27 cloudstack-management[4691]: /usr/sbin/tomcat: line 50: /var/run/cloudstack-management.pid: Permission denied Sep 23 12:14:05 Rack1Pod1Host27 systemd[1]: cloudstack-management.service: control process exited, code=exited status=1 Sep 23 12:14:05 Rack1Pod1Host27 systemd[1]: Failed to start Citrix Cloud Plaltform. Sep 23 12:14:05 Rack1Pod1Host27 systemd[1]: Unit cloudstack-management.service entered failed state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7671) [RHEL7] management server failed to start once machine is rebooted
Damodar Reddy T created CLOUDSTACK-7671: --- Summary: [RHEL7] management server failed to start once machine is rebooted Key: CLOUDSTACK-7671 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7671 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Damodar Reddy T Assignee: Damodar Reddy T Repro stesp: Create a rhel 7 host Install MS Start MS Once MS is up and running . Reboot MS . Notice Cloudstack-management service status Bug: Notice MS fails to start even after calling service cloudstack-management restart it failed to start systemctl status cloudstack-management.service cloudstack-management.service - Citrix Cloud Plaltform Loaded: loaded (/usr/lib/systemd/system/cloudstack-management.service; enabled) Active: failed (Result: exit-code) since Tue 2014-09-23 12:10:09 IST; 1min 28s ago Process: 4618 ExecStart=/usr/sbin/cloudstack-management start (code=exited, status=1/FAILURE) Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: Starting Citrix Cloud Plaltform... Sep 23 12:10:09 Rack1Pod1Host27 cloudstack-management[4618]: /usr/sbin/tomcat: line 50: /var/run/cloudstack-management.pid: Permission denied Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: cloudstack-management.service: control process exited, code=exited status=1 Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: Failed to start Citrix Cloud Plaltform. Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: Unit cloudstack-management.service entered failed state. [root@Rack1Pod1Host27 run]# service cloudstack-management status Redirecting to /bin/systemctl status cloudstack-management.service cloudstack-management.service - Citrix Cloud Plaltform Loaded: loaded (/usr/lib/systemd/system/cloudstack-management.service; enabled) Active: failed (Result: exit-code) since Tue 2014-09-23 12:14:05 IST; 8s ago Process: 4691 ExecStart=/usr/sbin/cloudstack-management start (code=exited, status=1/FAILURE) Sep 23 12:14:05 Rack1Pod1Host27 cloudstack-management[4691]: /usr/sbin/tomcat: line 50: /var/run/cloudstack-management.pid: Permission denied Sep 23 12:14:05 Rack1Pod1Host27 systemd[1]: cloudstack-management.service: control process exited, code=exited status=1 Sep 23 12:14:05 Rack1Pod1Host27 systemd[1]: Failed to start Citrix Cloud Plaltform. Sep 23 12:14:05 Rack1Pod1Host27 systemd[1]: Unit cloudstack-management.service entered failed state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7648) There are new VM State Machine changes introduced which were missed to capture the usage events
Damodar Reddy T created CLOUDSTACK-7648: --- Summary: There are new VM State Machine changes introduced which were missed to capture the usage events Key: CLOUDSTACK-7648 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7648 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: Damodar Reddy T Assignee: Damodar Reddy T Fix For: Future There are new VM State Machine changes introduced while adding VM Sync changes and these were missed to capture the usage events. This is causing to get wrong usage statistics for a VM who's state is changed by VM sync -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7560) Usage Event is not generated when VM state is transited from RUNNING to STOPPED directly
Damodar Reddy T created CLOUDSTACK-7560:
---
Summary: Usage Event is not generated when VM state is transited
from RUNNING to STOPPED directly
Key: CLOUDSTACK-7560
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7560
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Usage
Affects Versions: 4.5.0
Reporter: Damodar Reddy T
Fix For: Future
When Maagement server is not able to detect VM state, after a specific time it
will try to change the RUNNING state to STOPPED state directly without STOPPING
state in between. Which is causing the event not to be generated and now if you
DESTROY the VM still it will generate the usage records for a period of 24 hrs
every day.
Logs are attached below...
2014-05-15 16:13:25,197 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgent-117:ctx-775a3f34) Run missing VM report. current time:
1400163205197
2014-05-15 16:13:25,197 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgent-117:ctx-775a3f34) Detected missing VM. host: 1, vm id: 106, power
state: PowerReportMissing, last state update: 1400162537000
2014-05-15 16:13:25,197 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgent-117:ctx-775a3f34) vm id: 106 - time since last state
update(668197ms) has passed graceful period
2014-05-15 16:13:25,202 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
(DirectAgent-117:ctx-775a3f34) VM state report is updated. host: 1, vm id: 106,
power state: PowerReportMissing
2014-05-15 16:13:25,207 INFO [c.c.v.VirtualMachineManagerImpl]
(DirectAgent-117:ctx-775a3f34) VM i-5-106-VM is at Running and we received a
power-off report while there is no pending jobs on it
2014-05-15 16:13:25,210 DEBUG [c.c.a.t.Request] (DirectAgent-117:ctx-775a3f34)
Seq 1-1971781673: Sending { Cmd , MgmtId: 20750978301280, via: 1(XSMASTER-5),
Ver: v1, Flags: 100111,
[{com.cloud.agent.api.StopCommand:{isProxy:false,executeInSequence:true,checkBeforeCleanup:true,vmName:i-5-106-VM,wait:0}}]
}
2014-05-15 16:13:25,210 DEBUG [c.c.a.t.Request] (DirectAgent-117:ctx-775a3f34)
Seq 1-1971781673: Executing: { Cmd , MgmtId: 20750978301280, via:
1(XSMASTER-5), Ver: v1, Flags: 100111,
[{com.cloud.agent.api.StopCommand:{isProxy:false,executeInSequence:true,checkBeforeCleanup:true,vmName:i-5-106-VM,wait:0}}]
}
2014-05-15 16:13:25,210 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-18:ctx-7180bb9c) Seq 1-1971781673: Executing request
2014-05-15 16:13:25,249 DEBUG [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-18:ctx-7180bb9c) 9. The VM i-5-106-VM is in Stopping state
2014-05-15 16:13:25,293 INFO [c.c.h.x.r.XenServer56Resource]
(DirectAgent-18:ctx-7180bb9c) Catch com.xensource.xenapi.Types$VifInUse: failed
to destory VLAN eth0 on host c4080dac-f034-452f-9203-8e69d5512315 due to
Network has active VIFs
2014-05-15 16:13:25,294 DEBUG [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-18:ctx-7180bb9c) 10. The VM i-5-106-VM is in Stopped state
2014-05-15 16:13:25,294 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-18:ctx-7180bb9c) Seq 1-1971781673: Response Received:
2014-05-15 16:13:25,294 DEBUG [c.c.a.t.Request] (DirectAgent-18:ctx-7180bb9c)
Seq 1-1971781673: Processing: { Ans: , MgmtId: 20750978301280, via: 1, Ver:
v1, Flags: 110,
[{com.cloud.agent.api.StopAnswer:{platform:viridian:true;acpi:1;apic:true;pae:true;nx:true,result:true,details:Stop
VM i-5-106-VM Succeed,wait:0}}] }
2014-05-15 16:13:25,294 DEBUG [c.c.a.t.Request] (DirectAgent-117:ctx-775a3f34)
Seq 1-1971781673: Received: { Ans: , MgmtId: 20750978301280, via: 1, Ver: v1,
Flags: 110, { StopAnswer } }
2014-05-15 16:13:25,301 DEBUG [c.c.a.m.AgentAttache]
(DirectAgent-18:ctx-7180bb9c) Seq 1-1971781673: No more commands found
2014-05-15 16:13:25,365 DEBUG [c.c.c.CapacityManagerImpl]
(DirectAgent-117:ctx-775a3f34) VM state transitted from :Running to Stopped
with event: FollowAgentPowerOffReportvm's original host id: 1 new host id: null
host id before state transition: 1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7522) RPM builds should exit status 1, if there are failure in MVN build
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T updated CLOUDSTACK-7522: Assignee: Rayees Namathponnan (was: Damodar Reddy T) RPM builds should exit status 1, if there are failure in MVN build --- Key: CLOUDSTACK-7522 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7522 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.5.0 Reporter: Rayees Namathponnan Assignee: Rayees Namathponnan Priority: Blocker Fix For: 4.5.0 Steps to reproduce execute RPM build command var=$(bash ./package.sh --pack noredist --build) while executing MVN command kill java killall -9 java see the output, echo $var to see the output Expected result RPM build should exited error Actual result RPM build not exited with error , it return Done, see the output .cloudstack.framework.config.impl.ConfigDepotAdminTest log4j:WARN No appenders could be found for logger (org.apache.cloudstack.framework.config.impl.ConfigDepotImpl). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.091 sec Results : Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ cloud-framework-config --- [INFO] Building jar: /root/cloudplatform/build/source/dist/rpmbuild/BUILD/cloudstack-4.5.0-SNAPSHOT/framework/config/target/cloud-framework-config-4.5.0-SNAPSHOT.jar [INFO] [INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ cloud-framework-config --- [INFO] [INFO] [INFO] Building Apache CloudStack API 4.5.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ cloud-api --- [INFO] Deleting /root/cloudplatform/build/source/dist/rpmbuild/BUILD/cloudstack-4.5.0-SNAPSHOT/api (includes = [target, dist], excludes = []) [INFO] [INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ cloud-api --- [INFO] Starting audit... Audit done. [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-api --- [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ cloud-api --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 4 resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ cloud-api --- [INFO] Compiling 939 source files to /root/cloudplatform/build/source/dist/rpmbuild/BUILD/cloudstack-4.5.0-SNAPSHOT/api/target/classes RPM build errors: Done [root@build-test centos63]# vi package.sh Looks like this is happening after below commit https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=7ea7deded031b43042c68db0f7c5c6c8b21c18c2 if revert this commit rpm exit with return 1, if there are issue with mvn -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7464) Management Server setup doesn't proceed to completion - org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T resolved CLOUDSTACK-7464. - Resolution: Invalid Resolving this issue as the culprit commit that caused this has been reverted by Hugo. Management Server setup doesn't proceed to completion - org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException - Key: CLOUDSTACK-7464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7464 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: Pavan Kumar Bandarupally Assignee: Damodar Reddy T Priority: Blocker Fix For: 4.5.0 Attachments: catalina.out, localhost.2014-09-02.log, management-server.log, setupManagement.log After installation of management server, and database schema update, the setup is stuck at a point and doesn't proceed further. User will not be able to access the MS URL. The server is listening on port 8080 but a connection won't establish. The traces show that it is stuck at a point in the setup. 2014-09-02 11:17:46,341 INFO [c.c.u.c.ComponentContext] (localhost-startStop-1:null) Starting com.cloud.bridge.persist.dao.SHostDaoImpl_EnhancerByCloudStack_aeac22f4 2014-09-02 11:17:46,341 INFO [c.c.u.c.ComponentContext] (localhost-startStop-1:null) Starting com.cloud.bridge.persist.dao.SObjectDaoImpl_EnhancerByCloudStack_958692e5 2014-09-02 11:17:46,341 INFO [c.c.u.c.ComponentContext] (localhost-startStop-1:null) Starting com.cloud.bridge.persist.dao.CloudStackUserDaoImpl_EnhancerByCloudStack_90d5183f 2014-09-02 11:17:46,341 INFO [c.c.u.c.ComponentContext] (localhost-startStop-1:null) Starting com.cloud.bridge.service.core.ec2.EC2Engine_EnhancerByCloudStack_e8137795 2014-09-02 11:17:46,341 INFO [c.c.u.c.ComponentContext] (localhost-startStop-1:null) Starting com.cloud.bridge.service.controller.s3.ServiceProvider_EnhancerByCloudStack_1344120a -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7378) [rhel7] usage server installation is failing with java7 dependency
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T updated CLOUDSTACK-7378: Status: Reviewable (was: In Progress) [rhel7] usage server installation is failing with java7 dependency -- Key: CLOUDSTACK-7378 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7378 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: Damodar Reddy T Priority: Blocker Fix For: 4.5.0 usage server installation is failing with java7 dependency on rhel 7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7316) hitting java.lang.reflect.InvocationTargetException while starting usage server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14119851#comment-14119851 ] Damodar Reddy T commented on CLOUDSTACK-7316: - yeah this change is introduced recently. Earlier we were reading it from the hard coded path /etc/cloudstack/management/key but now we are trying to load it from the class path. This should be an issue for upgrades as well. As I have added this in %post usage section it should take care of upgrades as well. Anyhow I will test it before closing this... hitting java.lang.reflect.InvocationTargetException while starting usage server --- Key: CLOUDSTACK-7316 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7316 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Usage Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: Damodar Reddy T Priority: Blocker Fix For: 4.5.0 Attachments: usage.tar.gz Repro steps: Install MS and usage server Start MS and usage server Bug: Usage server will stop after starting usage log shows : java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243) Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'vmDiskUsageParser': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.cloud.usage.dao.UsageDao com.cloud.usage.parser.VmDiskUsageParser._usageDao; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'usageDaoImpl' defined in URL [jar:file:/usr/share/cloudstack-usage/lib/cloud-engine-schema-4.5.0-SNAPSHOT.jar!/com/cloud/usage/dao/UsageDaoImpl.class]: BeanPostProcessor before instantiation of bean failed; nested exception is net.sf.cglib.core.CodeGenerationException: java.lang.ExceptionInInitializerError--null at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:288) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1116) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:295) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:292) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:628) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:932) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479) at org.springframework.context.support.ClassPathXmlApplicationContext.init(ClassPathXmlApplicationContext.java:139) at org.springframework.context.support.ClassPathXmlApplicationContext.init(ClassPathXmlApplicationContext.java:83) at com.cloud.usage.UsageServer.start(UsageServer.java:57) ... 5 more Caused by: org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.cloud.usage.dao.UsageDao com.cloud.usage.parser.VmDiskUsageParser._usageDao; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'usageDaoImpl' defined in URL [jar:file:/usr/share/cloudstack-usage/lib/cloud-engine-schema-4.5.0-SNAPSHOT.jar!/com/cloud/usage/dao/UsageDaoImpl.class]:
[jira] [Resolved] (CLOUDSTACK-7378) [rhel7] usage server installation is failing with java7 dependency
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T resolved CLOUDSTACK-7378. - Resolution: Fixed [rhel7] usage server installation is failing with java7 dependency -- Key: CLOUDSTACK-7378 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7378 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: Damodar Reddy T Priority: Blocker Fix For: 4.5.0 usage server installation is failing with java7 dependency on rhel 7 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7116) unable to add KVM host to MS with error java.lang.UnsupportedClassVersionError: com/cloud/agent/AgentShell : Unsupported major.minor version 51.0
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T resolved CLOUDSTACK-7116. - Resolution: Not a Problem Not seeing this anymore... unable to add KVM host to MS with error java.lang.UnsupportedClassVersionError: com/cloud/agent/AgentShell : Unsupported major.minor version 51.0 - Key: CLOUDSTACK-7116 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7116 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: Damodar Reddy T Priority: Blocker Fix For: 4.5.0 Attachments: cloudstack-agent.err, management-server.log.tar.gz Repro steps: 1. Create a KVM host on rhel 6.3 As I used following build http://repo-ccp.citrix.com/releases/ASF/rhel/6.3/master/CloudPlatform-4.5.0-57-rhel6.3.tar.gz so i need to install jsvc outside of cloudstack for which I have done the following step: yum install java-gcj-compat rpm -Uvh ftp://rpmfind.net/linux/centos/6.5/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm and then I installed agent Once agent installation is complete I tried to add this KVM host to MS and host addition failed with MS logs showing 2014-07-16 06:09:19,082 DEBUG [c.c.h.k.d.LibvirtServerDiscoverer] (catalina-exec-7:ctx-ec9fe1d8 ctx-949d2702) Timeout, to wait for the host connecting to mgt svr, assuming it is failed 2014-07-16 06:09:19,083 WARN [c.c.r.ResourceManagerImpl] (catalina-exec-7:ctx-ec9fe1d8 ctx-949d2702) Unable to find the server resources at http://10.147.40.23 2014-07-16 06:09:19,084 INFO [c.c.u.e.CSExceptionErrorCode] (catalina-exec-7:ctx-ec9fe1d8 ctx-949d2702) Could not find exception: com.cloud.exception.DiscoveryException in error code list for exceptions 2014-07-16 06:09:19,084 WARN [o.a.c.a.c.a.h.AddHostCmd] (catalina-exec-7:ctx-ec9fe1d8 ctx-949d2702) Exception: com.cloud.exception.DiscoveryException: Unable to add the host at com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:791) at com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:586) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy148.discoverHosts(Unknown Source) at org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:142) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:694) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:517) at com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:317) at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118) 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 com.cloud.api.ApiServlet.processRequest(ApiServlet.java:115) at com.cloud.api.ApiServlet.doPost(ApiServlet.java:82) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
[jira] [Commented] (CLOUDSTACK-7464) Management Server setup doesn't proceed to completion on RHEL7
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14117947#comment-14117947 ] Damodar Reddy T commented on CLOUDSTACK-7464: - I think we need localhost.-mm-dd.log logs to find the actual Exception in this case as these logs are not having any relevant Errors in it. Management Server setup doesn't proceed to completion on RHEL7 -- Key: CLOUDSTACK-7464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7464 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: Pavan Kumar Bandarupally Priority: Blocker Fix For: 4.5.0 Attachments: catalina.out, management-server.log, setupManagement.log After installation of management server, and database schema update, the setup is stuck at a point and doesn't proceed further. User will not be able to access the MS URL. The server is listening on port 8080 but a connection won't establish. The traces show that it is stuck at a point in the setup. 2014-09-02 11:17:46,341 INFO [c.c.u.c.ComponentContext] (localhost-startStop-1:null) Starting com.cloud.bridge.persist.dao.SHostDaoImpl_EnhancerByCloudStack_aeac22f4 2014-09-02 11:17:46,341 INFO [c.c.u.c.ComponentContext] (localhost-startStop-1:null) Starting com.cloud.bridge.persist.dao.SObjectDaoImpl_EnhancerByCloudStack_958692e5 2014-09-02 11:17:46,341 INFO [c.c.u.c.ComponentContext] (localhost-startStop-1:null) Starting com.cloud.bridge.persist.dao.CloudStackUserDaoImpl_EnhancerByCloudStack_90d5183f 2014-09-02 11:17:46,341 INFO [c.c.u.c.ComponentContext] (localhost-startStop-1:null) Starting com.cloud.bridge.service.core.ec2.EC2Engine_EnhancerByCloudStack_e8137795 2014-09-02 11:17:46,341 INFO [c.c.u.c.ComponentContext] (localhost-startStop-1:null) Starting com.cloud.bridge.service.controller.s3.ServiceProvider_EnhancerByCloudStack_1344120a -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7464) Management Server setup doesn't proceed to completion
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14117963#comment-14117963 ] Damodar Reddy T commented on CLOUDSTACK-7464: - yeah it does not like empty xml file.. I have tested just now.. and will be uploading patch soon.. Management Server setup doesn't proceed to completion - Key: CLOUDSTACK-7464 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7464 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: Pavan Kumar Bandarupally Priority: Blocker Fix For: 4.5.0 Attachments: catalina.out, localhost.2014-09-02.log, management-server.log, setupManagement.log After installation of management server, and database schema update, the setup is stuck at a point and doesn't proceed further. User will not be able to access the MS URL. The server is listening on port 8080 but a connection won't establish. The traces show that it is stuck at a point in the setup. 2014-09-02 11:17:46,341 INFO [c.c.u.c.ComponentContext] (localhost-startStop-1:null) Starting com.cloud.bridge.persist.dao.SHostDaoImpl_EnhancerByCloudStack_aeac22f4 2014-09-02 11:17:46,341 INFO [c.c.u.c.ComponentContext] (localhost-startStop-1:null) Starting com.cloud.bridge.persist.dao.SObjectDaoImpl_EnhancerByCloudStack_958692e5 2014-09-02 11:17:46,341 INFO [c.c.u.c.ComponentContext] (localhost-startStop-1:null) Starting com.cloud.bridge.persist.dao.CloudStackUserDaoImpl_EnhancerByCloudStack_90d5183f 2014-09-02 11:17:46,341 INFO [c.c.u.c.ComponentContext] (localhost-startStop-1:null) Starting com.cloud.bridge.service.core.ec2.EC2Engine_EnhancerByCloudStack_e8137795 2014-09-02 11:17:46,341 INFO [c.c.u.c.ComponentContext] (localhost-startStop-1:null) Starting com.cloud.bridge.service.controller.s3.ServiceProvider_EnhancerByCloudStack_1344120a -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7316) hitting java.lang.reflect.InvocationTargetException while starting usage server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T resolved CLOUDSTACK-7316. - Resolution: Fixed Problem: - Usage Server was not starting when we enable DB Encryption due to not able to find key file in the class path when we install it on the same machine where management server was installed. Analysis: - Due to changes that are happened to, how CCP loads key file (earlier it used load key file from the hard coded absolute path /etc/cloudstack/management/key) to read it from the class path, when we install usage server on the same machine where management server was installed it is not able to find the file key in the class path of the usage server which is /etc/cloudstack/usage. Proposed Solution: During installation of the Usage server, if it is getting installed on the same machine where management server was installed add an alias to /etc/cloudstack/management/key in /etc/cloudstacl/usage as key if it exists. QA Notes: --- The default installation of the management server enables file based DB encryption so no need to enable it explicitly. hitting java.lang.reflect.InvocationTargetException while starting usage server --- Key: CLOUDSTACK-7316 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7316 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Usage Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: Damodar Reddy T Priority: Blocker Fix For: 4.5.0 Attachments: usage.tar.gz Repro steps: Install MS and usage server Start MS and usage server Bug: Usage server will stop after starting usage log shows : java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243) Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'vmDiskUsageParser': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.cloud.usage.dao.UsageDao com.cloud.usage.parser.VmDiskUsageParser._usageDao; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'usageDaoImpl' defined in URL [jar:file:/usr/share/cloudstack-usage/lib/cloud-engine-schema-4.5.0-SNAPSHOT.jar!/com/cloud/usage/dao/UsageDaoImpl.class]: BeanPostProcessor before instantiation of bean failed; nested exception is net.sf.cglib.core.CodeGenerationException: java.lang.ExceptionInInitializerError--null at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:288) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1116) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:295) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:292) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:628) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:932) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479) at
[jira] [Comment Edited] (CLOUDSTACK-7316) hitting java.lang.reflect.InvocationTargetException while starting usage server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14118094#comment-14118094 ] Damodar Reddy T edited comment on CLOUDSTACK-7316 at 9/2/14 11:10 AM: -- Problem: - Usage Server was not starting when we enable DB Encryption due to not able to find key file in the class path when we install it on the same machine where management server was installed. Analysis: - Due to changes that are happened to, how cloudstack loads key file (earlier it used load key file from the hard coded absolute path /etc/cloudstack/management/key) to read it from the class path, when we install usage server on the same machine where management server was installed it is not able to find the file key in the class path of the usage server which is /etc/cloudstack/usage. Proposed Solution: During installation of the Usage server, if it is getting installed on the same machine where management server was installed add an alias to /etc/cloudstack/management/key in /etc/cloudstacl/usage as key if it exists. QA Notes: --- The default installation of the management server enables file based DB encryption so no need to enable it explicitly. was (Author: damoder.reddy): Problem: - Usage Server was not starting when we enable DB Encryption due to not able to find key file in the class path when we install it on the same machine where management server was installed. Analysis: - Due to changes that are happened to, how CCP loads key file (earlier it used load key file from the hard coded absolute path /etc/cloudstack/management/key) to read it from the class path, when we install usage server on the same machine where management server was installed it is not able to find the file key in the class path of the usage server which is /etc/cloudstack/usage. Proposed Solution: During installation of the Usage server, if it is getting installed on the same machine where management server was installed add an alias to /etc/cloudstack/management/key in /etc/cloudstacl/usage as key if it exists. QA Notes: --- The default installation of the management server enables file based DB encryption so no need to enable it explicitly. hitting java.lang.reflect.InvocationTargetException while starting usage server --- Key: CLOUDSTACK-7316 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7316 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Usage Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: Damodar Reddy T Priority: Blocker Fix For: 4.5.0 Attachments: usage.tar.gz Repro steps: Install MS and usage server Start MS and usage server Bug: Usage server will stop after starting usage log shows : java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243) Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'vmDiskUsageParser': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.cloud.usage.dao.UsageDao com.cloud.usage.parser.VmDiskUsageParser._usageDao; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'usageDaoImpl' defined in URL [jar:file:/usr/share/cloudstack-usage/lib/cloud-engine-schema-4.5.0-SNAPSHOT.jar!/com/cloud/usage/dao/UsageDaoImpl.class]: BeanPostProcessor before instantiation of bean failed; nested exception is net.sf.cglib.core.CodeGenerationException: java.lang.ExceptionInInitializerError--null at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:288) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1116) at
[jira] [Updated] (CLOUDSTACK-7460) [LXC][RHEl7] Agent installaion fails if Management server is already installed on the same machine
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T updated CLOUDSTACK-7460: Priority: Major (was: Critical) [LXC][RHEl7] Agent installaion fails if Management server is already installed on the same machine -- Key: CLOUDSTACK-7460 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7460 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.5.0 Reporter: shweta agarwal Assignee: Damodar Reddy T Fix For: 4.5.0 Repro steps: on rhel 7 Machine. First install MS and try installing Agent on the same machine Bug: Agent installation will fail with following error : Transaction check error: file /var/log/cloudstack/agent from install of cloudstack-agent-4.5.0-SNAPSHOT.el7.x86_64 conflicts with file from package cloudstack-management-4.5.0-SNAPSHOT.el7.x86_64 Error Summary - Done -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7316) hitting java.lang.reflect.InvocationTargetException while starting usage server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14117379#comment-14117379 ] Damodar Reddy T commented on CLOUDSTACK-7316: - This is happening when we enable encryption for DB passwords and install management server and usage server on the same machine. Usage server is not able to find key file in it's classpath. hitting java.lang.reflect.InvocationTargetException while starting usage server --- Key: CLOUDSTACK-7316 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7316 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Usage Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: Damodar Reddy T Priority: Blocker Fix For: 4.5.0 Attachments: usage.tar.gz Repro steps: Install MS and usage server Start MS and usage server Bug: Usage server will stop after starting usage log shows : java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243) Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'vmDiskUsageParser': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.cloud.usage.dao.UsageDao com.cloud.usage.parser.VmDiskUsageParser._usageDao; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'usageDaoImpl' defined in URL [jar:file:/usr/share/cloudstack-usage/lib/cloud-engine-schema-4.5.0-SNAPSHOT.jar!/com/cloud/usage/dao/UsageDaoImpl.class]: BeanPostProcessor before instantiation of bean failed; nested exception is net.sf.cglib.core.CodeGenerationException: java.lang.ExceptionInInitializerError--null at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:288) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1116) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:295) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:292) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:628) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:932) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479) at org.springframework.context.support.ClassPathXmlApplicationContext.init(ClassPathXmlApplicationContext.java:139) at org.springframework.context.support.ClassPathXmlApplicationContext.init(ClassPathXmlApplicationContext.java:83) at com.cloud.usage.UsageServer.start(UsageServer.java:57) ... 5 more Caused by: org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.cloud.usage.dao.UsageDao com.cloud.usage.parser.VmDiskUsageParser._usageDao; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'usageDaoImpl' defined in URL [jar:file:/usr/share/cloudstack-usage/lib/cloud-engine-schema-4.5.0-SNAPSHOT.jar!/com/cloud/usage/dao/UsageDaoImpl.class]: BeanPostProcessor before instantiation of bean failed; nested exception is net.sf.cglib.core.CodeGenerationException: java.lang.ExceptionInInitializerError--null at
[jira] [Commented] (CLOUDSTACK-7245) listIsos call does not return isdynamicallyscalable in the response attributes as mentioned in API docs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14113581#comment-14113581 ] Damodar Reddy T commented on CLOUDSTACK-7245: - Problem: - From CCP-4.3 onwards we were not returning isdynamicallyscalable parameter in the response for the API call listIsos. Root Cause Analysis: - We are not setting the field isDynamicallyScalable in TemplateResponse.java Object for listIsos call. Due to this in the response it was not populating this parameter into the response. Proposed Solution: Populate the field isDynamicallyScalable by calling setDynamucallyScalable() method in TemplateResponse.java in listIsos call in TemplateJoinDaoImpl.newIsoResponse() QA Notes: --- Please note that we are not capturing isDynamicallyScalable value while registering an ISO which is a UI defect listIsos call does not return isdynamicallyscalable in the response attributes as mentioned in API docs --- Key: CLOUDSTACK-7245 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7245 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.1 Reporter: Damodar Reddy T Assignee: Damodar Reddy T Fix For: 4.5.0 There is no way to tell whether a particular iso listed is dynamically scalable or not. Even in the cloudstak UI, 'Dynamically Scalable' is listed in the template details while its not there in the ISO details. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7153) addNicToVirtualMachine not BaseAsyncCreate but creates an entity
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14113673#comment-14113673 ] Damodar Reddy T commented on CLOUDSTACK-7153: - Problem: --- When event bus is enabled and while adding a nic to a VM, This creates an entity into nic but will not put the created entity's uuid into the event bus message. Root Cause Analysis: --- In UserVmManager.addNicToVirtualMachine which is called by addNicToVmCmd was not putting the created entity's uuid into the CallContext so the Event NIC Complete was not able to get the id during event complete call so was not putting the same into event bus message. Solution proposed: Put the created entity's uuid into CallContext before returning from UserVmManager.addNicToVirtualMachine call QA Notes: --- Make sure the entity's uuid is coming in event bus message during event complete call. addNicToVirtualMachine not BaseAsyncCreate but creates an entity Key: CLOUDSTACK-7153 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7153 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: Damodar Reddy T Assignee: Damodar Reddy T Fix For: 4.5.0 addNicToVirtualMachine not BaseAsyncCreate but creates an entity. We need them to be BaseAsyncCreate so that Eventbus while publishing the completed events can put in the entity id. Right now there is a generic logic where after create function when the id is created its pushed into the context so that Eventbus can use it to publish the created UUID. If its not baseAsyncCreate you will have to go into each api and put the id in the context. Currently following is the generic code had put in ApiServer.java. We will have to do specifically into your api. Do this only if there is a hard reason not to make it baseasyncCreate Class entityClass = EventTypes.getEntityClassForEvent(createCmd.getEventType()); if (entityClass != null) ctx.putContextParameter(entityClass.getName(), objectId); -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-7106) RPM build failing with RHEL7
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T reassigned CLOUDSTACK-7106: --- Assignee: Damodar Reddy T (was: Hugo Trippaers) RPM build failing with RHEL7 Key: CLOUDSTACK-7106 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7106 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.5.0 Environment: RHEL7 Reporter: Rayees Namathponnan Assignee: Damodar Reddy T Priority: Critical Fix For: 4.5.0 RPM build failing with RHEL7, since there are dependency with tomcat, we need to create sperate spec.file for RHEL7 or re write existing spec file to support both RHE6 and 7 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-7106) RPM build failing with RHEL7
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T resolved CLOUDSTACK-7106. - Resolution: Fixed RPM build failing with RHEL7 Key: CLOUDSTACK-7106 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7106 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.5.0 Environment: RHEL7 Reporter: Rayees Namathponnan Assignee: Damodar Reddy T Priority: Critical Fix For: 4.5.0 RPM build failing with RHEL7, since there are dependency with tomcat, we need to create sperate spec.file for RHEL7 or re write existing spec file to support both RHE6 and 7 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7245) listIsos call does not return isdynamicallyscalable in the response attributes as mentioned in API docs
Damodar Reddy T created CLOUDSTACK-7245: --- Summary: listIsos call does not return isdynamicallyscalable in the response attributes as mentioned in API docs Key: CLOUDSTACK-7245 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7245 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.1 Reporter: Damodar Reddy T Assignee: Damodar Reddy T Fix For: 4.5.0 There is no way to tell whether a particular iso listed is dynamically scalable or not. Even in the cloudstak UI, 'Dynamically Scalable' is listed in the template details while its not there in the ISO details. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7249) Enable Password Strength check for all users
Damodar Reddy T created CLOUDSTACK-7249: --- Summary: Enable Password Strength check for all users Key: CLOUDSTACK-7249 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7249 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: Damodar Reddy T Assignee: Damodar Reddy T Fix For: 4.5.0 Currently we do not show the password strength of a user for his chosen password int he API response. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-7245) listIsos call does not return isdynamicallyscalable in the response attributes as mentioned in API docs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T resolved CLOUDSTACK-7245. - Resolution: Fixed Currently UI is not capturing isdynamicallyscalable parameter while registering a template and is not displaying while listing ISOs listIsos call does not return isdynamicallyscalable in the response attributes as mentioned in API docs --- Key: CLOUDSTACK-7245 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7245 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.1 Reporter: Damodar Reddy T Assignee: Damodar Reddy T Fix For: 4.5.0 There is no way to tell whether a particular iso listed is dynamically scalable or not. Even in the cloudstak UI, 'Dynamically Scalable' is listed in the template details while its not there in the ISO details. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7153) addNicToVirtualMachine not BaseAsyncCreate but creates an entity
Damodar Reddy T created CLOUDSTACK-7153: --- Summary: addNicToVirtualMachine not BaseAsyncCreate but creates an entity Key: CLOUDSTACK-7153 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7153 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: Damodar Reddy T Assignee: Damodar Reddy T Fix For: 4.5.0 addNicToVirtualMachine not BaseAsyncCreate but creates an entity. We need them to be BaseAsyncCreate so that Eventbus while publishing the completed events can put in the entity id. Right now there is a generic logic where after create function when the id is created its pushed into the context so that Eventbus can use it to publish the created UUID. If its not baseAsyncCreate you will have to go into each api and put the id in the context. Currently following is the generic code had put in ApiServer.java. We will have to do specifically into your api. Do this only if there is a hard reason not to make it baseasyncCreate Class entityClass = EventTypes.getEntityClassForEvent(createCmd.getEventType()); if (entityClass != null) ctx.putContextParameter(entityClass.getName(), objectId); -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-7153) addNicToVirtualMachine not BaseAsyncCreate but creates an entity
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T resolved CLOUDSTACK-7153. - Resolution: Fixed addNicToVirtualMachine not BaseAsyncCreate but creates an entity Key: CLOUDSTACK-7153 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7153 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: Damodar Reddy T Assignee: Damodar Reddy T Fix For: 4.5.0 addNicToVirtualMachine not BaseAsyncCreate but creates an entity. We need them to be BaseAsyncCreate so that Eventbus while publishing the completed events can put in the entity id. Right now there is a generic logic where after create function when the id is created its pushed into the context so that Eventbus can use it to publish the created UUID. If its not baseAsyncCreate you will have to go into each api and put the id in the context. Currently following is the generic code had put in ApiServer.java. We will have to do specifically into your api. Do this only if there is a hard reason not to make it baseasyncCreate Class entityClass = EventTypes.getEntityClassForEvent(createCmd.getEventType()); if (entityClass != null) ctx.putContextParameter(entityClass.getName(), objectId); -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7142) Coverity Issues fixes and better error messages
Damodar Reddy T created CLOUDSTACK-7142: --- Summary: Coverity Issues fixes and better error messages Key: CLOUDSTACK-7142 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7142 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: Damodar Reddy T Assignee: Damodar Reddy T Priority: Minor Fix For: 4.5.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6036) CloudStack stops the machine for no reason
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damodar Reddy T updated CLOUDSTACK-6036:
Labels: 4.5ReviewNeeded (was: )
CloudStack stops the machine for no reason
---
Key: CLOUDSTACK-6036
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6036
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.2.1
Environment: ACS 4.2.1 after upgrade from 3.0.2
ACS 4.2.1 clean install
XCP 1.1
Reporter: Tomasz Zieba
Assignee: Damodar Reddy T
Priority: Critical
Labels: 4.5ReviewNeeded
Fix For: 4.4.0
Attachments: management-server.log.2014-02-19.gz,
management-server.log.2014-02-20.gz, management-server.log.2014-02-24.txt
After the upgrade from version 3.0.2 to 4.2.1 appeared very strange error
associated with self-stopping machine after changing the offering.
Steps to reproduce:
1. Running instance of the machine
2. Stop with the operating system
3. Change offering of machine
4. Start the machine
5. Waiting for 10 minutes
6. CloudStack stops the machine for no reason
7. Restart the machine
In the logs you can find information:
2014-02-05 06:27:00,974 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-316:null) 11. The VM i-41-824-VM is in Running state
2014-02-05 06:27:00,974 DEBUG [agent.transport.Request]
(DirectAgent-316:null) Seq 50-1756626952: Processing: { Ans: , MgmtId:
160544475005497, via: 50, Ver: v1, Flags: 10,
[{com.cloud.agent.api.ClusterSyncAnswer:{_clusterId:2,_newStates:{i-41-824-VM:{t:f32a4fee-b64e-4868-9c52-2a27e32d4c0e,u:Running,v:viridian:true;acpi:true;apic:true;pae:true;nx:false;timeoffset:0;cores-per-socket:4}},_isExecuted:false,result:true,wait:0}}]
}
2014-02-05 06:27:00,981 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(DirectAgent-316:null) VM i-41-824-VM: cs state = Running and realState =
Running
2014-02-05 06:27:00,981 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(DirectAgent-316:null) VM i-41-824-VM: cs state = Running and realState =
Running
2014-02-05 06:36:01,240 DEBUG [agent.transport.Request]
(HA-Worker-1:work-1511) Seq 51-1374970375: Sending { Cmd , MgmtId:
160544475005497, via: 51, Ver: v1, Flags: 100111,
[{com.cloud.agent.api.StopCommand:{isProxy:false,executeInSequence:true,vmName:i-41-824-VM,wait:0}}]
}
2014-02-05 06:36:01,240 DEBUG [agent.transport.Request]
(HA-Worker-1:work-1511) Seq 51-1374970375: Executing: { Cmd , MgmtId:
160544475005497, via: 51, Ver: v1, Flags: 100111,
[{com.cloud.agent.api.StopCommand:{isProxy:false,executeInSequence:true,vmName:i-41-824-VM,wait:0}}]
}
2014-02-05 06:36:01,383 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-150:null) 9. The VM i-41-824-VM is in Stopping state
2014-02-05 06:36:27,625 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-150:null) 10. The VM i-41-824-VM is in Stopped state
You will notice that the stop of the machine corresponds to the component
HA-Worker.
Such operation after the upgrade is complicating work of users.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6036) CloudStack stops the machine for no reason
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14058744#comment-14058744
]
Damodar Reddy T commented on CLOUDSTACK-6036:
-
I tried to look into the logs long back but I could not come to a conclusion,
what is causing the issue for this. I will try to re look into the logs once
again..
CloudStack stops the machine for no reason
---
Key: CLOUDSTACK-6036
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6036
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.2.1
Environment: ACS 4.2.1 after upgrade from 3.0.2
ACS 4.2.1 clean install
XCP 1.1
Reporter: Tomasz Zieba
Assignee: Damodar Reddy T
Priority: Critical
Fix For: 4.4.0
Attachments: management-server.log.2014-02-19.gz,
management-server.log.2014-02-20.gz, management-server.log.2014-02-24.txt
After the upgrade from version 3.0.2 to 4.2.1 appeared very strange error
associated with self-stopping machine after changing the offering.
Steps to reproduce:
1. Running instance of the machine
2. Stop with the operating system
3. Change offering of machine
4. Start the machine
5. Waiting for 10 minutes
6. CloudStack stops the machine for no reason
7. Restart the machine
In the logs you can find information:
2014-02-05 06:27:00,974 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-316:null) 11. The VM i-41-824-VM is in Running state
2014-02-05 06:27:00,974 DEBUG [agent.transport.Request]
(DirectAgent-316:null) Seq 50-1756626952: Processing: { Ans: , MgmtId:
160544475005497, via: 50, Ver: v1, Flags: 10,
[{com.cloud.agent.api.ClusterSyncAnswer:{_clusterId:2,_newStates:{i-41-824-VM:{t:f32a4fee-b64e-4868-9c52-2a27e32d4c0e,u:Running,v:viridian:true;acpi:true;apic:true;pae:true;nx:false;timeoffset:0;cores-per-socket:4}},_isExecuted:false,result:true,wait:0}}]
}
2014-02-05 06:27:00,981 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(DirectAgent-316:null) VM i-41-824-VM: cs state = Running and realState =
Running
2014-02-05 06:27:00,981 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(DirectAgent-316:null) VM i-41-824-VM: cs state = Running and realState =
Running
2014-02-05 06:36:01,240 DEBUG [agent.transport.Request]
(HA-Worker-1:work-1511) Seq 51-1374970375: Sending { Cmd , MgmtId:
160544475005497, via: 51, Ver: v1, Flags: 100111,
[{com.cloud.agent.api.StopCommand:{isProxy:false,executeInSequence:true,vmName:i-41-824-VM,wait:0}}]
}
2014-02-05 06:36:01,240 DEBUG [agent.transport.Request]
(HA-Worker-1:work-1511) Seq 51-1374970375: Executing: { Cmd , MgmtId:
160544475005497, via: 51, Ver: v1, Flags: 100111,
[{com.cloud.agent.api.StopCommand:{isProxy:false,executeInSequence:true,vmName:i-41-824-VM,wait:0}}]
}
2014-02-05 06:36:01,383 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-150:null) 9. The VM i-41-824-VM is in Stopping state
2014-02-05 06:36:27,625 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-150:null) 10. The VM i-41-824-VM is in Stopped state
You will notice that the stop of the machine corresponds to the component
HA-Worker.
Such operation after the upgrade is complicating work of users.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6444) [Automation] test_01_primary_storage_iscsi failed on test_primary_storage.py - Wrong iscsi path format - it should be /targetIQN/LUN
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damodar Reddy T resolved CLOUDSTACK-6444.
-
Resolution: Fixed
[Automation] test_01_primary_storage_iscsi failed on
test_primary_storage.py - Wrong iscsi path format - it should be
/targetIQN/LUN
Key: CLOUDSTACK-6444
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6444
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, XenServer
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Assignee: Damodar Reddy T
Priority: Critical
Fix For: 4.4.0
Attachments: management-server.log.2014-04-16.gz
Error Message:
Execute cmd: createstoragepool failed, due to: errorCode: 530, errorText:None
begin captured logging
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
STARTED : TC: test_01_primary_storage_iscsi :::
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
sending GET request: listZones {}
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Computed Signature by Marvin: zCinw6XM4JSpQF6uNjzREWyHshQ=
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.240.161
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listZonessignature=zCinw6XM4JSpQF6uNjzREWyHshQ%3Dresponse=json
HTTP/1.1 200 735
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Request:
http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listZonessignature=zCinw6XM4JSpQF6uNjzREWyHshQ%3Dresponse=json
Response: { listzonesresponse : { count:2 ,zone : [
{id:4fbc4494-e655-49b6-bda1-7ad8eb641732,name:test0,dns1:10.223.240.232,dns2:10.223.240.234,internaldns1:10.223.240.232,networktype:Basic,securitygroupsenabled:true,allocationstate:Enabled,zonetoken:f0aed2ee-a79d-3608-bae5-09972653a6cf,dhcpprovider:VirtualRouter,localstorageenabled:false,tags:[]},
{id:55fe83ca-4160-40b2-89cb-63cadf8b90f9,name:test1,dns1:10.223.240.234,dns2:10.223.240.232,internaldns1:10.223.240.232,networktype:Basic,securitygroupsenabled:true,allocationstate:Enabled,zonetoken:3973cd3a-d2ed-3242-8431-b40f919051f1,dhcpprovider:VirtualRouter,localstorageenabled:false,tags:[]}
] } }
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
sending GET request: listPods {'zoneid':
u'4fbc4494-e655-49b6-bda1-7ad8eb641732'}
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Computed Signature by Marvin: Q5eN6r9ACb1qiPi7CI3wiB6wh0k=
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.240.161
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
HTTP/1.1 200 314
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Request:
http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
Response: { listpodsresponse : { count:1 ,pod : [
{id:d99714b2-7164-4d85-b5a6-c0caf12eb57a,name:test0pod0,zoneid:4fbc4494-e655-49b6-bda1-7ad8eb641732,zonename:test0,gateway:10.223.251.1,netmask:255.255.255.192,startip:10.223.251.4,endip:10.223.251.14,allocationstate:Enabled}
] } }
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
sending GET request: listClusters {'zoneid':
u'4fbc4494-e655-49b6-bda1-7ad8eb641732'}
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Computed Signature by Marvin: CGgAerZxK5EJBr34YnPiWBJHqWg=
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.240.161
requests.packages.urllib3.connectionpool: DEBUG: GET
[jira] [Created] (CLOUDSTACK-6978) CLONE - [Windows] Can not create Template from ROOT snapshot For S3 Storage Server
Damodar Reddy T created CLOUDSTACK-6978: --- Summary: CLONE - [Windows] Can not create Template from ROOT snapshot For S3 Storage Server Key: CLOUDSTACK-6978 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6978 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: Future, 4.5.0 Reporter: Damodar Reddy T Assignee: Damodar Reddy T Steps to reproduce the issue 1. Create a snapshot from ROOT disk 2. Goto the above created snapshot 3. Try to create template out of it. It is failing with the following trace. 014-05-12 04:02:01,813 WARN [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-428:ctx-2ece4baa) null due to Illegal character in path at index 47: nfs://10.147.28.7/export/home/damoder/secondary\snapshots/2/3\dc74fe1c-0891-4cb3-aaf2-1c03a25b6d58.vhd java.net.URISyntaxException: Illegal character in path at index 47: nfs://10.147.28.7/export/home/damoder/secondary\snapshots/2/3\dc74fe1c-0891-4cb3-aaf2-1c03a25b6d58.vhd at java.net.URI$Parser.fail(Unknown Source) at java.net.URI$Parser.checkChars(Unknown Source) at java.net.URI$Parser.parseHierarchical(Unknown Source) at java.net.URI$Parser.parse(Unknown Source) at java.net.URI.init(Unknown Source) at com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.createVolumeFromSnapshot(XenServerStorageProcessor.java:1617) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:96) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:52) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:542) at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:60) at com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:93) at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216) 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(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6636) [Windows] Can not create Template from ROOT snapshot
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T resolved CLOUDSTACK-6636. - Resolution: Fixed Fix Version/s: 4.5.0 [Windows] Can not create Template from ROOT snapshot Key: CLOUDSTACK-6636 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6636 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: Future, 4.5.0 Reporter: Damodar Reddy T Assignee: Damodar Reddy T Fix For: 4.5.0 Steps to reproduce the issue 1. Create a snapshot from ROOT disk 2. Goto the above created snapshot 3. Try to create template out of it. It is failing with the following trace. 014-05-12 04:02:01,813 WARN [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-428:ctx-2ece4baa) null due to Illegal character in path at index 47: nfs://10.147.28.7/export/home/damoder/secondary\snapshots/2/3\dc74fe1c-0891-4cb3-aaf2-1c03a25b6d58.vhd java.net.URISyntaxException: Illegal character in path at index 47: nfs://10.147.28.7/export/home/damoder/secondary\snapshots/2/3\dc74fe1c-0891-4cb3-aaf2-1c03a25b6d58.vhd at java.net.URI$Parser.fail(Unknown Source) at java.net.URI$Parser.checkChars(Unknown Source) at java.net.URI$Parser.parseHierarchical(Unknown Source) at java.net.URI$Parser.parse(Unknown Source) at java.net.URI.init(Unknown Source) at com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.createVolumeFromSnapshot(XenServerStorageProcessor.java:1617) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:96) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:52) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:542) at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:60) at com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:93) at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216) 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(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6444) [Automation] test_01_primary_storage_iscsi failed on test_primary_storage.py - Wrong iscsi path format - it should be /targetIQN/LUN
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14038527#comment-14038527
]
Damodar Reddy T commented on CLOUDSTACK-6444:
-
I think, This issue is caused due to the following commit
0ff943337c20e02fd39597a0977cff531a73ecae
[Automation] test_01_primary_storage_iscsi failed on
test_primary_storage.py - Wrong iscsi path format - it should be
/targetIQN/LUN
Key: CLOUDSTACK-6444
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6444
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, XenServer
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Assignee: Chandan Purushothama
Priority: Trivial
Fix For: 4.4.0
Attachments: management-server.log.2014-04-16.gz
Error Message:
Execute cmd: createstoragepool failed, due to: errorCode: 530, errorText:None
begin captured logging
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
STARTED : TC: test_01_primary_storage_iscsi :::
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
sending GET request: listZones {}
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Computed Signature by Marvin: zCinw6XM4JSpQF6uNjzREWyHshQ=
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.240.161
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listZonessignature=zCinw6XM4JSpQF6uNjzREWyHshQ%3Dresponse=json
HTTP/1.1 200 735
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Request:
http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listZonessignature=zCinw6XM4JSpQF6uNjzREWyHshQ%3Dresponse=json
Response: { listzonesresponse : { count:2 ,zone : [
{id:4fbc4494-e655-49b6-bda1-7ad8eb641732,name:test0,dns1:10.223.240.232,dns2:10.223.240.234,internaldns1:10.223.240.232,networktype:Basic,securitygroupsenabled:true,allocationstate:Enabled,zonetoken:f0aed2ee-a79d-3608-bae5-09972653a6cf,dhcpprovider:VirtualRouter,localstorageenabled:false,tags:[]},
{id:55fe83ca-4160-40b2-89cb-63cadf8b90f9,name:test1,dns1:10.223.240.234,dns2:10.223.240.232,internaldns1:10.223.240.232,networktype:Basic,securitygroupsenabled:true,allocationstate:Enabled,zonetoken:3973cd3a-d2ed-3242-8431-b40f919051f1,dhcpprovider:VirtualRouter,localstorageenabled:false,tags:[]}
] } }
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
sending GET request: listPods {'zoneid':
u'4fbc4494-e655-49b6-bda1-7ad8eb641732'}
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Computed Signature by Marvin: Q5eN6r9ACb1qiPi7CI3wiB6wh0k=
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.240.161
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
HTTP/1.1 200 314
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Request:
http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
Response: { listpodsresponse : { count:1 ,pod : [
{id:d99714b2-7164-4d85-b5a6-c0caf12eb57a,name:test0pod0,zoneid:4fbc4494-e655-49b6-bda1-7ad8eb641732,zonename:test0,gateway:10.223.251.1,netmask:255.255.255.192,startip:10.223.251.4,endip:10.223.251.14,allocationstate:Enabled}
] } }
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
sending GET request: listClusters {'zoneid':
u'4fbc4494-e655-49b6-bda1-7ad8eb641732'}
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Computed Signature by Marvin: CGgAerZxK5EJBr34YnPiWBJHqWg=
[jira] [Commented] (CLOUDSTACK-6444) [Automation] test_01_primary_storage_iscsi failed on test_primary_storage.py - Wrong iscsi path format - it should be /targetIQN/LUN
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14038603#comment-14038603
]
Damodar Reddy T commented on CLOUDSTACK-6444:
-
Before this change for Iscsi we were doing
*hostPath.replaceFirst(/, );* (Not assigning the replaced value to
hostpath so passing right value to hypervisor)
The above commit is doing
*hostpath* = hostPath.replaceFirst(/, ); (But replaced value assigned it
to the host path) which is causing the path not to start with / but
expectation is to start with /
[Automation] test_01_primary_storage_iscsi failed on
test_primary_storage.py - Wrong iscsi path format - it should be
/targetIQN/LUN
Key: CLOUDSTACK-6444
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6444
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, XenServer
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Assignee: Chandan Purushothama
Priority: Trivial
Fix For: 4.4.0
Attachments: management-server.log.2014-04-16.gz
Error Message:
Execute cmd: createstoragepool failed, due to: errorCode: 530, errorText:None
begin captured logging
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
STARTED : TC: test_01_primary_storage_iscsi :::
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
sending GET request: listZones {}
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Computed Signature by Marvin: zCinw6XM4JSpQF6uNjzREWyHshQ=
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.240.161
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listZonessignature=zCinw6XM4JSpQF6uNjzREWyHshQ%3Dresponse=json
HTTP/1.1 200 735
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Request:
http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listZonessignature=zCinw6XM4JSpQF6uNjzREWyHshQ%3Dresponse=json
Response: { listzonesresponse : { count:2 ,zone : [
{id:4fbc4494-e655-49b6-bda1-7ad8eb641732,name:test0,dns1:10.223.240.232,dns2:10.223.240.234,internaldns1:10.223.240.232,networktype:Basic,securitygroupsenabled:true,allocationstate:Enabled,zonetoken:f0aed2ee-a79d-3608-bae5-09972653a6cf,dhcpprovider:VirtualRouter,localstorageenabled:false,tags:[]},
{id:55fe83ca-4160-40b2-89cb-63cadf8b90f9,name:test1,dns1:10.223.240.234,dns2:10.223.240.232,internaldns1:10.223.240.232,networktype:Basic,securitygroupsenabled:true,allocationstate:Enabled,zonetoken:3973cd3a-d2ed-3242-8431-b40f919051f1,dhcpprovider:VirtualRouter,localstorageenabled:false,tags:[]}
] } }
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
sending GET request: listPods {'zoneid':
u'4fbc4494-e655-49b6-bda1-7ad8eb641732'}
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Computed Signature by Marvin: Q5eN6r9ACb1qiPi7CI3wiB6wh0k=
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.240.161
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
HTTP/1.1 200 314
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Request:
http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
Response: { listpodsresponse : { count:1 ,pod : [
{id:d99714b2-7164-4d85-b5a6-c0caf12eb57a,name:test0pod0,zoneid:4fbc4494-e655-49b6-bda1-7ad8eb641732,zonename:test0,gateway:10.223.251.1,netmask:255.255.255.192,startip:10.223.251.4,endip:10.223.251.14,allocationstate:Enabled}
] } }
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
sending GET request:
[jira] [Commented] (CLOUDSTACK-6444) [Automation] test_01_primary_storage_iscsi failed on test_primary_storage.py - Wrong iscsi path format - it should be /targetIQN/LUN
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14038626#comment-14038626
]
Damodar Reddy T commented on CLOUDSTACK-6444:
-
yeah.. I am testing the changes.. I will be submitting the patch for the same
soon.
[Automation] test_01_primary_storage_iscsi failed on
test_primary_storage.py - Wrong iscsi path format - it should be
/targetIQN/LUN
Key: CLOUDSTACK-6444
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6444
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, XenServer
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Assignee: Chandan Purushothama
Priority: Trivial
Fix For: 4.4.0
Attachments: management-server.log.2014-04-16.gz
Error Message:
Execute cmd: createstoragepool failed, due to: errorCode: 530, errorText:None
begin captured logging
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
STARTED : TC: test_01_primary_storage_iscsi :::
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
sending GET request: listZones {}
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Computed Signature by Marvin: zCinw6XM4JSpQF6uNjzREWyHshQ=
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.240.161
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listZonessignature=zCinw6XM4JSpQF6uNjzREWyHshQ%3Dresponse=json
HTTP/1.1 200 735
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Request:
http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listZonessignature=zCinw6XM4JSpQF6uNjzREWyHshQ%3Dresponse=json
Response: { listzonesresponse : { count:2 ,zone : [
{id:4fbc4494-e655-49b6-bda1-7ad8eb641732,name:test0,dns1:10.223.240.232,dns2:10.223.240.234,internaldns1:10.223.240.232,networktype:Basic,securitygroupsenabled:true,allocationstate:Enabled,zonetoken:f0aed2ee-a79d-3608-bae5-09972653a6cf,dhcpprovider:VirtualRouter,localstorageenabled:false,tags:[]},
{id:55fe83ca-4160-40b2-89cb-63cadf8b90f9,name:test1,dns1:10.223.240.234,dns2:10.223.240.232,internaldns1:10.223.240.232,networktype:Basic,securitygroupsenabled:true,allocationstate:Enabled,zonetoken:3973cd3a-d2ed-3242-8431-b40f919051f1,dhcpprovider:VirtualRouter,localstorageenabled:false,tags:[]}
] } }
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
sending GET request: listPods {'zoneid':
u'4fbc4494-e655-49b6-bda1-7ad8eb641732'}
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Computed Signature by Marvin: Q5eN6r9ACb1qiPi7CI3wiB6wh0k=
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.240.161
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
HTTP/1.1 200 314
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Request:
http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
Response: { listpodsresponse : { count:1 ,pod : [
{id:d99714b2-7164-4d85-b5a6-c0caf12eb57a,name:test0pod0,zoneid:4fbc4494-e655-49b6-bda1-7ad8eb641732,zonename:test0,gateway:10.223.251.1,netmask:255.255.255.192,startip:10.223.251.4,endip:10.223.251.14,allocationstate:Enabled}
] } }
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
sending GET request: listClusters {'zoneid':
u'4fbc4494-e655-49b6-bda1-7ad8eb641732'}
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Computed Signature by Marvin: CGgAerZxK5EJBr34YnPiWBJHqWg=
requests.packages.urllib3.connectionpool: INFO:
[jira] [Assigned] (CLOUDSTACK-6444) [Automation] test_01_primary_storage_iscsi failed on test_primary_storage.py - Wrong iscsi path format - it should be /targetIQN/LUN
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damodar Reddy T reassigned CLOUDSTACK-6444:
---
Assignee: Damodar Reddy T (was: Chandan Purushothama)
[Automation] test_01_primary_storage_iscsi failed on
test_primary_storage.py - Wrong iscsi path format - it should be
/targetIQN/LUN
Key: CLOUDSTACK-6444
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6444
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, XenServer
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Assignee: Damodar Reddy T
Priority: Trivial
Fix For: 4.4.0
Attachments: management-server.log.2014-04-16.gz
Error Message:
Execute cmd: createstoragepool failed, due to: errorCode: 530, errorText:None
begin captured logging
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
STARTED : TC: test_01_primary_storage_iscsi :::
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
sending GET request: listZones {}
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Computed Signature by Marvin: zCinw6XM4JSpQF6uNjzREWyHshQ=
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.240.161
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listZonessignature=zCinw6XM4JSpQF6uNjzREWyHshQ%3Dresponse=json
HTTP/1.1 200 735
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Request:
http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listZonessignature=zCinw6XM4JSpQF6uNjzREWyHshQ%3Dresponse=json
Response: { listzonesresponse : { count:2 ,zone : [
{id:4fbc4494-e655-49b6-bda1-7ad8eb641732,name:test0,dns1:10.223.240.232,dns2:10.223.240.234,internaldns1:10.223.240.232,networktype:Basic,securitygroupsenabled:true,allocationstate:Enabled,zonetoken:f0aed2ee-a79d-3608-bae5-09972653a6cf,dhcpprovider:VirtualRouter,localstorageenabled:false,tags:[]},
{id:55fe83ca-4160-40b2-89cb-63cadf8b90f9,name:test1,dns1:10.223.240.234,dns2:10.223.240.232,internaldns1:10.223.240.232,networktype:Basic,securitygroupsenabled:true,allocationstate:Enabled,zonetoken:3973cd3a-d2ed-3242-8431-b40f919051f1,dhcpprovider:VirtualRouter,localstorageenabled:false,tags:[]}
] } }
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
sending GET request: listPods {'zoneid':
u'4fbc4494-e655-49b6-bda1-7ad8eb641732'}
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Computed Signature by Marvin: Q5eN6r9ACb1qiPi7CI3wiB6wh0k=
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.240.161
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
HTTP/1.1 200 314
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Request:
http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
Response: { listpodsresponse : { count:1 ,pod : [
{id:d99714b2-7164-4d85-b5a6-c0caf12eb57a,name:test0pod0,zoneid:4fbc4494-e655-49b6-bda1-7ad8eb641732,zonename:test0,gateway:10.223.251.1,netmask:255.255.255.192,startip:10.223.251.4,endip:10.223.251.14,allocationstate:Enabled}
] } }
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
sending GET request: listClusters {'zoneid':
u'4fbc4494-e655-49b6-bda1-7ad8eb641732'}
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Computed Signature by Marvin: CGgAerZxK5EJBr34YnPiWBJHqWg=
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.240.161
[jira] [Updated] (CLOUDSTACK-6444) [Automation] test_01_primary_storage_iscsi failed on test_primary_storage.py - Wrong iscsi path format - it should be /targetIQN/LUN
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damodar Reddy T updated CLOUDSTACK-6444:
Priority: Critical (was: Trivial)
[Automation] test_01_primary_storage_iscsi failed on
test_primary_storage.py - Wrong iscsi path format - it should be
/targetIQN/LUN
Key: CLOUDSTACK-6444
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6444
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, XenServer
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Assignee: Damodar Reddy T
Priority: Critical
Fix For: 4.4.0
Attachments: management-server.log.2014-04-16.gz
Error Message:
Execute cmd: createstoragepool failed, due to: errorCode: 530, errorText:None
begin captured logging
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
STARTED : TC: test_01_primary_storage_iscsi :::
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
sending GET request: listZones {}
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Computed Signature by Marvin: zCinw6XM4JSpQF6uNjzREWyHshQ=
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.240.161
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listZonessignature=zCinw6XM4JSpQF6uNjzREWyHshQ%3Dresponse=json
HTTP/1.1 200 735
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Request:
http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listZonessignature=zCinw6XM4JSpQF6uNjzREWyHshQ%3Dresponse=json
Response: { listzonesresponse : { count:2 ,zone : [
{id:4fbc4494-e655-49b6-bda1-7ad8eb641732,name:test0,dns1:10.223.240.232,dns2:10.223.240.234,internaldns1:10.223.240.232,networktype:Basic,securitygroupsenabled:true,allocationstate:Enabled,zonetoken:f0aed2ee-a79d-3608-bae5-09972653a6cf,dhcpprovider:VirtualRouter,localstorageenabled:false,tags:[]},
{id:55fe83ca-4160-40b2-89cb-63cadf8b90f9,name:test1,dns1:10.223.240.234,dns2:10.223.240.232,internaldns1:10.223.240.232,networktype:Basic,securitygroupsenabled:true,allocationstate:Enabled,zonetoken:3973cd3a-d2ed-3242-8431-b40f919051f1,dhcpprovider:VirtualRouter,localstorageenabled:false,tags:[]}
] } }
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
sending GET request: listPods {'zoneid':
u'4fbc4494-e655-49b6-bda1-7ad8eb641732'}
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Computed Signature by Marvin: Q5eN6r9ACb1qiPi7CI3wiB6wh0k=
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.240.161
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
HTTP/1.1 200 314
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Request:
http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
Response: { listpodsresponse : { count:1 ,pod : [
{id:d99714b2-7164-4d85-b5a6-c0caf12eb57a,name:test0pod0,zoneid:4fbc4494-e655-49b6-bda1-7ad8eb641732,zonename:test0,gateway:10.223.251.1,netmask:255.255.255.192,startip:10.223.251.4,endip:10.223.251.14,allocationstate:Enabled}
] } }
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
sending GET request: listClusters {'zoneid':
u'4fbc4494-e655-49b6-bda1-7ad8eb641732'}
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Computed Signature by Marvin: CGgAerZxK5EJBr34YnPiWBJHqWg=
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.240.161
requests.packages.urllib3.connectionpool: DEBUG: GET
[jira] [Commented] (CLOUDSTACK-6407) NPE while collecting VM statistics
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14030420#comment-14030420
]
Damodar Reddy T commented on CLOUDSTACK-6407:
-
Not able reproduce on the latest build of 4.4. Closing for now.
NPE while collecting VM statistics
---
Key: CLOUDSTACK-6407
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6407
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: Sailaja Mada
Assignee: Damodar Reddy T
Fix For: 4.4.0
Attachments: management-server.log
Setup : 4.4 with XenServer 6.2.5
1. Install and configure Adv zone using XenServer 6.2.5
2. Deployed 2 Windows (8 and 2012) VM's using Domain user account .
Observed NPE's while collecting VM statistics in the Management server
log(Attached)
2014-04-15 00:00:49,574 DEBUG [c.c.s.StatsCollector]
(StatsCollector-4:ctx-2e085056) VmStatsCollector is running...
2014-04-15 00:00:49,588 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-69:ctx-9a19b721) Seq 1-6476457739135503930: Executing request
2014-04-15 00:00:49,618 WARN [c.c.a.m.DirectAgentAttache]
(DirectAgent-69:ctx-9a19b721) Seq 1-6476457739135503930: Exception Caught
while executing command
java.lang.NullPointerException
2014-04-15 00:00:49,619 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-69:ctx-9a19b721) Seq 1-6476457739135503930: Response Received:
2014-04-15 00:00:49,619 DEBUG [c.c.a.t.Request] (DirectAgent-69:ctx-9a19b721)
Seq 1-6476457739135503930: Processing: { Ans: , MgmtId: 55355881446856, via:
1, Ver: v1, Flags: 10,
[{com.cloud.agent.api.Answer:{result:false,details:java.lang.NullPointerException,wait:0}}]
}
2014-04-15 00:00:49,619 DEBUG [c.c.a.t.Request]
(StatsCollector-4:ctx-2e085056) Seq 1-6476457739135503930: Received: { Ans:
, MgmtId: 55355881446856, via: 1, Ver: v1, Flags: 10, { Answer } }
2014-04-15 00:00:49,619 DEBUG [c.c.a.m.AgentManagerImpl]
(StatsCollector-4:ctx-2e085056) Details from executing class
com.cloud.agent.api.GetVmStatsCommand: java.lang.NullPointerException
2014-04-15 00:00:49,619 WARN [c.c.v.UserVmManagerImpl]
(StatsCollector-4:ctx-2e085056) Unable to obtain VM statistics.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6407) NPE while collecting VM statistics
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damodar Reddy T resolved CLOUDSTACK-6407.
-
Resolution: Fixed
NPE while collecting VM statistics
---
Key: CLOUDSTACK-6407
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6407
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: Sailaja Mada
Assignee: Damodar Reddy T
Fix For: 4.4.0
Attachments: management-server.log
Setup : 4.4 with XenServer 6.2.5
1. Install and configure Adv zone using XenServer 6.2.5
2. Deployed 2 Windows (8 and 2012) VM's using Domain user account .
Observed NPE's while collecting VM statistics in the Management server
log(Attached)
2014-04-15 00:00:49,574 DEBUG [c.c.s.StatsCollector]
(StatsCollector-4:ctx-2e085056) VmStatsCollector is running...
2014-04-15 00:00:49,588 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-69:ctx-9a19b721) Seq 1-6476457739135503930: Executing request
2014-04-15 00:00:49,618 WARN [c.c.a.m.DirectAgentAttache]
(DirectAgent-69:ctx-9a19b721) Seq 1-6476457739135503930: Exception Caught
while executing command
java.lang.NullPointerException
2014-04-15 00:00:49,619 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-69:ctx-9a19b721) Seq 1-6476457739135503930: Response Received:
2014-04-15 00:00:49,619 DEBUG [c.c.a.t.Request] (DirectAgent-69:ctx-9a19b721)
Seq 1-6476457739135503930: Processing: { Ans: , MgmtId: 55355881446856, via:
1, Ver: v1, Flags: 10,
[{com.cloud.agent.api.Answer:{result:false,details:java.lang.NullPointerException,wait:0}}]
}
2014-04-15 00:00:49,619 DEBUG [c.c.a.t.Request]
(StatsCollector-4:ctx-2e085056) Seq 1-6476457739135503930: Received: { Ans:
, MgmtId: 55355881446856, via: 1, Ver: v1, Flags: 10, { Answer } }
2014-04-15 00:00:49,619 DEBUG [c.c.a.m.AgentManagerImpl]
(StatsCollector-4:ctx-2e085056) Details from executing class
com.cloud.agent.api.GetVmStatsCommand: java.lang.NullPointerException
2014-04-15 00:00:49,619 WARN [c.c.v.UserVmManagerImpl]
(StatsCollector-4:ctx-2e085056) Unable to obtain VM statistics.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6407) NPE while collecting VM statistics
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damodar Reddy T reassigned CLOUDSTACK-6407:
---
Assignee: Damodar Reddy T
NPE while collecting VM statistics
---
Key: CLOUDSTACK-6407
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6407
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: Sailaja Mada
Assignee: Damodar Reddy T
Fix For: 4.4.0
Attachments: management-server.log
Setup : 4.4 with XenServer 6.2.5
1. Install and configure Adv zone using XenServer 6.2.5
2. Deployed 2 Windows (8 and 2012) VM's using Domain user account .
Observed NPE's while collecting VM statistics in the Management server
log(Attached)
2014-04-15 00:00:49,574 DEBUG [c.c.s.StatsCollector]
(StatsCollector-4:ctx-2e085056) VmStatsCollector is running...
2014-04-15 00:00:49,588 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-69:ctx-9a19b721) Seq 1-6476457739135503930: Executing request
2014-04-15 00:00:49,618 WARN [c.c.a.m.DirectAgentAttache]
(DirectAgent-69:ctx-9a19b721) Seq 1-6476457739135503930: Exception Caught
while executing command
java.lang.NullPointerException
2014-04-15 00:00:49,619 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-69:ctx-9a19b721) Seq 1-6476457739135503930: Response Received:
2014-04-15 00:00:49,619 DEBUG [c.c.a.t.Request] (DirectAgent-69:ctx-9a19b721)
Seq 1-6476457739135503930: Processing: { Ans: , MgmtId: 55355881446856, via:
1, Ver: v1, Flags: 10,
[{com.cloud.agent.api.Answer:{result:false,details:java.lang.NullPointerException,wait:0}}]
}
2014-04-15 00:00:49,619 DEBUG [c.c.a.t.Request]
(StatsCollector-4:ctx-2e085056) Seq 1-6476457739135503930: Received: { Ans:
, MgmtId: 55355881446856, via: 1, Ver: v1, Flags: 10, { Answer } }
2014-04-15 00:00:49,619 DEBUG [c.c.a.m.AgentManagerImpl]
(StatsCollector-4:ctx-2e085056) Details from executing class
com.cloud.agent.api.GetVmStatsCommand: java.lang.NullPointerException
2014-04-15 00:00:49,619 WARN [c.c.v.UserVmManagerImpl]
(StatsCollector-4:ctx-2e085056) Unable to obtain VM statistics.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6839) [Windows] MSI Installer Wizard modifications(Including logos text etc..)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T updated CLOUDSTACK-6839: Component/s: UI [Windows] MSI Installer Wizard modifications(Including logos text etc..) Key: CLOUDSTACK-6839 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6839 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup, UI Affects Versions: Future, 4.5.0 Reporter: Damodar Reddy T Assignee: Stephen Turner Fix For: 4.5.0 Attachments: windows_installer.jpg The attached snapshot contains the steps involved in installation process of cloudstack on management server. It has several steps and each step has it's own wizard. We need to change the logo and the look and feel of each wizard based on ACS standards. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6839) [UI][Windows] MSI Installer Wizard modifications(Including logos text etc..)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T updated CLOUDSTACK-6839: Summary: [UI][Windows] MSI Installer Wizard modifications(Including logos text etc..) (was: [Windows] MSI Installer Wizard modifications(Including logos text etc..)) [UI][Windows] MSI Installer Wizard modifications(Including logos text etc..) Key: CLOUDSTACK-6839 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6839 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup, UI Affects Versions: Future, 4.5.0 Reporter: Damodar Reddy T Assignee: Stephen Turner Fix For: 4.5.0 Attachments: windows_installer.jpg The attached snapshot contains the steps involved in installation process of cloudstack on management server. It has several steps and each step has it's own wizard. We need to change the logo and the look and feel of each wizard based on ACS standards. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6791) [Automation] DeleteNetworkCmd fails with NullPointerException
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14017441#comment-14017441 ] Damodar Reddy T commented on CLOUDSTACK-6791: - It was successful for me on the following set up 1.. XenServer 6.2.0 2. Management Server 4.4 with commit id 1f7167555d92bc2d5eb964e6de88a052db1388a7. [Automation] DeleteNetworkCmd fails with NullPointerException - Key: CLOUDSTACK-6791 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6791 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: Automation 4.4-forward vmware 5.0 Reporter: Rayees Namathponnan Assignee: Jayapal Reddy Priority: Blocker Fix For: 4.4.0 This issue is observed with automation run , while executing test integration.component.test_multiple_ips_per_nic.TestBasicOperations.test_add_ip_to_nic_2_SHARED Test case performs below operations 225 # Steps: 226 # 1. Create Account and create network in it (isoalted/ shared/ vpc) 227 # 2. Deploy a VM in this network and account 228 # 3. Add secondary IP to the default nic of VM 229 # 4. Try to add the same IP again 230 # 5. Try to add secondary IP providing wrong virtual machine id 231 # 6. Try to add secondary IP with correct virtual machine id but wrong IP address # 7 Destroy account 232 233 # Validations: 234 # 1. Step 3 should succeed 235 # 2. Step 4 should fail 236 # 3. Step 5 should should fail 237 # 4. Step 6 should fail This issue observed during account deletion 2014-05-26 19:18:52,169 DEBUG [o.a.c.e.o.NetworkOrchestrator] (API-Job-Executor-41:ctx-b247339e job-5716 ctx-5a0ec179) Network id=616 is destroyed successfully, cleaning up corresponding resources now. 2014-05-26 19:18:52,170 DEBUG [c.c.n.g.DirectNetworkGuru] (API-Job-Executor-41:ctx-b247339e job-5716 ctx-5a0ec179) Releasing ip 172.16.27.1 of placeholder nic Nic[1645-null-null-172.16.27.1] 2014-05-26 19:18:52,171 DEBUG [c.c.u.d.T.Transaction] (API-Job-Executor-41:ctx-b247339e job-5716 ctx-5a0ec179) Rolling back the transaction: Time = 2 Name = API-Job-Executor-41; called by -TransactionLegacy.rollback:903-TransactionLegacy.removeUpTo:846-TransactionLegacy.close:670-Transaction.execute:41-Transaction.execute:46-DirectNetworkGuru.trash:327-NetworkOrchestrator$10.doInTransactionWithoutResult:2226-TransactionCallbackNoReturn.doInTransaction:25-Transaction$2.doInTransaction:49-Transaction.execute:37-Transaction.execute:46-NetworkOrchestrator.destroyNetwork:2221 2014-05-26 19:18:52,183 ERROR [c.c.a.ApiAsyncJobDispatcher] (API-Job-Executor-41:ctx-b247339e job-5716) Unexpected exception while executing org.apache.cloudstack.api.command.user.network.DeleteNetworkCmd java.lang.NullPointerException at com.cloud.network.guru.DirectNetworkGuru$3.doInTransactionWithoutResult(DirectNetworkGuru.java:334) at com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java:25) at com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49) at com.cloud.utils.db.Transaction.execute(Transaction.java:37) at com.cloud.utils.db.Transaction.execute(Transaction.java:46) at com.cloud.network.guru.DirectNetworkGuru.trash(DirectNetworkGuru.java:327) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$10.doInTransactionWithoutResult(NetworkOrchestrator.java:2226) at com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java:25) at com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49) at com.cloud.utils.db.Transaction.execute(Transaction.java:37) at com.cloud.utils.db.Transaction.execute(Transaction.java:46) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.destroyNetwork(NetworkOrchestrator.java:2221) at com.cloud.network.NetworkServiceImpl.deleteNetwork(NetworkServiceImpl.java:1828) at sun.reflect.GeneratedMethodAccessor729.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
[jira] [Comment Edited] (CLOUDSTACK-6791) [Automation] DeleteNetworkCmd fails with NullPointerException
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14017441#comment-14017441
]
Damodar Reddy T edited comment on CLOUDSTACK-6791 at 6/4/14 8:12 AM:
-
It was successful for me on the following set up
1.. XenServer 6.2.0
2. Management Server 4.4 with commit id
1f7167555d92bc2d5eb964e6de88a052db1388a7.
DelteNetwork Command is:
http://localhost:8080/client/api?command=deleteNetworkid=b394254e-a18e-4570-be3f-0a7360ea0b22response=jsonsessionkey=8WR1hf%2F4g733j53Im2uKMNf2YjM%3D_=1401868961929
And the json response for the async job after success:
{ queryasyncjobresultresponse :
{accountid:9e106ab8-eae8-11e3-9bfb-e89a8f32fe7b,userid:9e10abd5-eae8-11e3-9bfb-e89a8f32fe7b,cmd:org.apache.cloudstack.api.command.user.network.DeleteNetworkCmd,jobstatus:1,jobprocstatus:0,jobresultcode:0,jobresulttype:object,jobresult:{success:true},created:2014-06-04T13:32:42+0530,jobid:71abd9b6-c54d-44cb-97cf-9ad3d85a71b2}
}
was (Author: damoder.reddy):
It was successful for me on the following set up
1.. XenServer 6.2.0
2. Management Server 4.4 with commit id
1f7167555d92bc2d5eb964e6de88a052db1388a7.
[Automation] DeleteNetworkCmd fails with NullPointerException
-
Key: CLOUDSTACK-6791
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6791
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: Automation
4.4-forward
vmware 5.0
Reporter: Rayees Namathponnan
Assignee: Jayapal Reddy
Priority: Blocker
Fix For: 4.4.0
This issue is observed with automation run , while executing test
integration.component.test_multiple_ips_per_nic.TestBasicOperations.test_add_ip_to_nic_2_SHARED
Test case performs below operations
225 # Steps:
226 # 1. Create Account and create network in it (isoalted/ shared/
vpc)
227 # 2. Deploy a VM in this network and account
228 # 3. Add secondary IP to the default nic of VM
229 # 4. Try to add the same IP again
230 # 5. Try to add secondary IP providing wrong virtual machine id
231 # 6. Try to add secondary IP with correct virtual machine id but
wrong IP address
# 7 Destroy account
232
233 # Validations:
234 # 1. Step 3 should succeed
235 # 2. Step 4 should fail
236 # 3. Step 5 should should fail
237 # 4. Step 6 should fail
This issue observed during account deletion
2014-05-26 19:18:52,169 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(API-Job-Executor-41:ctx-b247339e job-5716 ctx-5a0ec179) Network id=616 is
destroyed successfully, cleaning up corresponding resources now.
2014-05-26 19:18:52,170 DEBUG [c.c.n.g.DirectNetworkGuru]
(API-Job-Executor-41:ctx-b247339e job-5716 ctx-5a0ec179) Releasing ip
172.16.27.1 of placeholder nic Nic[1645-null-null-172.16.27.1]
2014-05-26 19:18:52,171 DEBUG [c.c.u.d.T.Transaction]
(API-Job-Executor-41:ctx-b247339e job-5716 ctx-5a0ec179) Rolling back the
transaction: Time = 2 Name = API-Job-Executor-41; called by
-TransactionLegacy.rollback:903-TransactionLegacy.removeUpTo:846-TransactionLegacy.close:670-Transaction.execute:41-Transaction.execute:46-DirectNetworkGuru.trash:327-NetworkOrchestrator$10.doInTransactionWithoutResult:2226-TransactionCallbackNoReturn.doInTransaction:25-Transaction$2.doInTransaction:49-Transaction.execute:37-Transaction.execute:46-NetworkOrchestrator.destroyNetwork:2221
2014-05-26 19:18:52,183 ERROR [c.c.a.ApiAsyncJobDispatcher]
(API-Job-Executor-41:ctx-b247339e job-5716) Unexpected exception while
executing org.apache.cloudstack.api.command.user.network.DeleteNetworkCmd
java.lang.NullPointerException
at
com.cloud.network.guru.DirectNetworkGuru$3.doInTransactionWithoutResult(DirectNetworkGuru.java:334)
at
com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java:25)
at
com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49)
at com.cloud.utils.db.Transaction.execute(Transaction.java:37)
at com.cloud.utils.db.Transaction.execute(Transaction.java:46)
at
com.cloud.network.guru.DirectNetworkGuru.trash(DirectNetworkGuru.java:327)
at
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$10.doInTransactionWithoutResult(NetworkOrchestrator.java:2226)
at
com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java:25)
at
com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49)
at
[jira] [Resolved] (CLOUDSTACK-6702) [Windows] Give Details to admin as messages When system properties are changed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T resolved CLOUDSTACK-6702. - Resolution: Fixed [Windows] Give Details to admin as messages When system properties are changed -- Key: CLOUDSTACK-6702 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6702 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.5.0 Reporter: Damodar Reddy T Assignee: Damodar Reddy T Fix For: 4.5.0 1. Give necessary progress bar messages to admin before changing the system properties like environment varibales, firewall rules etc.. 2. Move all titles and descriptions to a property file or move to build properties -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6661) deployvm failed with NPE
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damodar Reddy T resolved CLOUDSTACK-6661.
-
Resolution: Fixed
Issue has been fixed in the commit 7bbad0491f7ec087f693814caadbe6d648d2edf2.
deployvm failed with NPE
-
Key: CLOUDSTACK-6661
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6661
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: Jayapal Reddy
Assignee: Damodar Reddy T
Priority: Critical
Fix For: 4.4.0
While deploying vm observed the NPE
java.lang.NullPointerException
at com.cloud.hypervisor.XenServerGuru.implement(XenServerGuru.java:96)
=
2014-05-14 11:58:59,398 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(867392383@qtp-1655170479-7:ctx-2fd5e67f ctx-20936702) submit async job-178,
details: AsyncJobVO {id:178, userId: 2, accountId: 2, instanceType:
VirtualMachine, instanceId: 26, cmd:
org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin, cmdInfo:
{serviceofferingid:baa62f3e-9f44-46ad-a137-7275bcaf8c99,sessionkey:Li3x1YB3+DUERGcuaZ9plLrGSZc\u003d,cmdEventType:VM.CREATE,ctxUserId:2,zoneid:e7d72675-2bf3-4bab-b673-d9d92a735603,httpmethod:GET,templateid:79f647d6-da5c-11e3-80cb-b51f7904a635,response:json,id:26,ctxDetails:{\com.cloud.template.VirtualMachineTemplate\:5,\com.cloud.vm.VirtualMachine\:26,\com.cloud.dc.DataCenter\:1,\VirtualMachine\:\ed6a3bef-8e60-4001-8fc9-d0bd1ad15312\,\com.cloud.offering.ServiceOffering\:1},hypervisor:XenServer,iptonetworklist[0].networkid:4bcc4888-3a5d-4736-8b3e-ad8204606dcd,_:1400048939193,uuid:ed6a3bef-8e60-4001-8fc9-d0bd1ad15312,ctxAccountId:2,ctxStartEventId:197},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 1, completeMsid: null, lastUpdated: null, lastPolled: null,
created: null}
2014-05-14 11:58:59,399 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-7:job-178) Add job-178 into job monitoring
2014-05-14 11:58:59,399 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-7:job-178) Executing AsyncJobVO {id:178, userId: 2,
accountId: 2, instanceType: VirtualMachine, instanceId: 26, cmd:
org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin, cmdInfo:
{serviceofferingid:baa62f3e-9f44-46ad-a137-7275bcaf8c99,sessionkey:Li3x1YB3+DUERGcuaZ9plLrGSZc\u003d,cmdEventType:VM.CREATE,ctxUserId:2,zoneid:e7d72675-2bf3-4bab-b673-d9d92a735603,httpmethod:GET,templateid:79f647d6-da5c-11e3-80cb-b51f7904a635,response:json,id:26,ctxDetails:{\com.cloud.template.VirtualMachineTemplate\:5,\com.cloud.vm.VirtualMachine\:26,\com.cloud.dc.DataCenter\:1,\VirtualMachine\:\ed6a3bef-8e60-4001-8fc9-d0bd1ad15312\,\com.cloud.offering.ServiceOffering\:1},hypervisor:XenServer,iptonetworklist[0].networkid:4bcc4888-3a5d-4736-8b3e-ad8204606dcd,_:1400048939193,uuid:ed6a3bef-8e60-4001-8fc9-d0bd1ad15312,ctxAccountId:2,ctxStartEventId:197},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 1, completeMsid: null, lastUpdated: null, lastPolled: null,
created: null}
2014-05-14 11:58:59,400 DEBUG [c.c.a.ApiServlet]
(867392383@qtp-1655170479-7:ctx-2fd5e67f ctx-20936702) ===END===
10.252.192.19 -- GET
command=deployVirtualMachineresponse=jsonsessionkey=Li3x1YB3%2BDUERGcuaZ9plLrGSZc%3Dzoneid=e7d72675-2bf3-4bab-b673-d9d92a735603templateid=79f647d6-da5c-11e3-80cb-b51f7904a635hypervisor=XenServerserviceofferingid=baa62f3e-9f44-46ad-a137-7275bcaf8c99iptonetworklist%5B0%5D.networkid=4bcc4888-3a5d-4736-8b3e-ad8204606dcd_=1400048939193
2014-05-14 11:58:59,407 DEBUG [c.c.a.d.ParamProcessWorker]
(API-Job-Executor-7:job-178 ctx-836ec730) Access granted to
Acct[7aa84a4e-da5c-11e3-80cb-b51f7904a635-admin] to service offering:1 by
RoleBasedEntityAccessChecker
2014-05-14 11:58:59,409 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker]
(API-Job-Executor-7:job-178 ctx-836ec730) IAM access check for
2-null-null-SystemCapability from cache: true
2014-05-14 11:58:59,409 DEBUG [c.c.u.AccountManagerImpl]
(API-Job-Executor-7:job-178 ctx-836ec730) Root Access granted to
Acct[7aa84a4e-da5c-11e3-80cb-b51f7904a635-admin] by
RoleBasedEntityAccessChecker
2014-05-14 11:58:59,411 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker]
(API-Job-Executor-7:job-178 ctx-836ec730) IAM access check for
2-null-null-DomainCapability from cache: false
2014-05-14 11:58:59,413 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker]
(API-Job-Executor-7:job-178 ctx-836ec730) IAM access check for
2-null-null-DomainResourceCapability from cache: false
2014-05-14 11:58:59,414 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker]
(API-Job-Executor-7:job-178 ctx-836ec730) IAM access check for
[jira] [Created] (CLOUDSTACK-6834) [Windows] Feedback Items
Damodar Reddy T created CLOUDSTACK-6834: --- Summary: [Windows] Feedback Items Key: CLOUDSTACK-6834 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6834 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: Future Reporter: Damodar Reddy T Assignee: Damodar Reddy T Fix For: 4.5.0 The feed back items received internally. 1. Need to add more fields to the database creation wizard 2. Remove Complete Option 3. Some description changes words like CloudStack etc 4. Change Default installation location if possible include version number 5. Mysql Connector Installer along with other dependecies 6. Add run Service Checkbox 7. Add ReadMe checkbox -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6834) [Windows] Feedback Items
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T updated CLOUDSTACK-6834: Description: The feed back items received internally. 1. Need to add more fields to the database creation wizard 2. Remove Complete Option 3. Some description changes words like CloudStack etc 4. Change Default installation location if possible include version number 5. Mysql Connector Installer along with other dependecies 6. Add run Service Checkbox 7. Add ReadMe checkbox 8. If possible enable logs for Custom Actions that are executed as part of installation was: The feed back items received internally. 1. Need to add more fields to the database creation wizard 2. Remove Complete Option 3. Some description changes words like CloudStack etc 4. Change Default installation location if possible include version number 5. Mysql Connector Installer along with other dependecies 6. Add run Service Checkbox 7. Add ReadMe checkbox [Windows] Feedback Items Key: CLOUDSTACK-6834 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6834 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: Future Reporter: Damodar Reddy T Assignee: Damodar Reddy T Fix For: 4.5.0 The feed back items received internally. 1. Need to add more fields to the database creation wizard 2. Remove Complete Option 3. Some description changes words like CloudStack etc 4. Change Default installation location if possible include version number 5. Mysql Connector Installer along with other dependecies 6. Add run Service Checkbox 7. Add ReadMe checkbox 8. If possible enable logs for Custom Actions that are executed as part of installation -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6839) [Windows] MSI Installer Wizard modifications(Including logos text etc..)
Damodar Reddy T created CLOUDSTACK-6839: --- Summary: [Windows] MSI Installer Wizard modifications(Including logos text etc..) Key: CLOUDSTACK-6839 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6839 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: Future, 4.5.0 Reporter: Damodar Reddy T Assignee: Stephen Turner Fix For: 4.5.0 The attached snapshot contains the steps involved in installation process of cloudstack on management server. It has several steps and each step has it's own wizard. We need to change the logo and the look and feel of each wizard based on ACS standards. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6839) [Windows] MSI Installer Wizard modifications(Including logos text etc..)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T updated CLOUDSTACK-6839: Attachment: windows_installer.jpg If we click on options button on the first wizard it will lead to the 2nd wizard in the screen shot. If we click on Install on the 1st wizard it will lead to the 3rd wizard in the screen shot. Reamaining wizards will come in the flow while installing apache cloudstack. [Windows] MSI Installer Wizard modifications(Including logos text etc..) Key: CLOUDSTACK-6839 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6839 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: Future, 4.5.0 Reporter: Damodar Reddy T Assignee: Stephen Turner Fix For: 4.5.0 Attachments: windows_installer.jpg The attached snapshot contains the steps involved in installation process of cloudstack on management server. It has several steps and each step has it's own wizard. We need to change the logo and the look and feel of each wizard based on ACS standards. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CLOUDSTACK-6839) [Windows] MSI Installer Wizard modifications(Including logos text etc..)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14017376#comment-14017376 ] Damodar Reddy T edited comment on CLOUDSTACK-6839 at 6/4/14 5:21 AM: - If we click on options button on the first wizard it will lead to the 2nd wizard in the screen shot. If we click on Install on the 1st wizard it will lead to the 3rd wizard in the screen shot. Reamaining wizards will come in the flow while installing apache cloudstack. In the Provide Database Information wizard we need to accommodate more fields to capture from the end user like encryption type, pass phrase was (Author: damoder.reddy): If we click on options button on the first wizard it will lead to the 2nd wizard in the screen shot. If we click on Install on the 1st wizard it will lead to the 3rd wizard in the screen shot. Reamaining wizards will come in the flow while installing apache cloudstack. [Windows] MSI Installer Wizard modifications(Including logos text etc..) Key: CLOUDSTACK-6839 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6839 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: Future, 4.5.0 Reporter: Damodar Reddy T Assignee: Stephen Turner Fix For: 4.5.0 Attachments: windows_installer.jpg The attached snapshot contains the steps involved in installation process of cloudstack on management server. It has several steps and each step has it's own wizard. We need to change the logo and the look and feel of each wizard based on ACS standards. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6481) Vhd-util is not copied to xenserver from MS...As a result system VMs fail to start in CS.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T resolved CLOUDSTACK-6481. - Resolution: Not a Problem Vhd-util is not copied to xenserver from MS...As a result system VMs fail to start in CS. - Key: CLOUDSTACK-6481 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6481 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup, XenServer Affects Versions: 4.4.0 Environment: Xenserver6.2 added to CS 4.4 Reporter: manasaveloori Assignee: Damodar Reddy T Priority: Blocker Fix For: 4.4.0 Attachments: management-server.log PXE booted the Xenserver. Added it to CS 4.4. observed that system vms fails to deploy with Exception: 2014-04-23 04:23:46,875 WARN [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-3:ctx-cf6a380b) Catch Exception com.cloud.utils.exception.CloudRuntimeException for template + due to com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr 5cffabad-fb53-27ad-96eb-a1728623dd7c com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr 5cffabad-fb53-27ad-96eb-a1728623dd7c at com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copy_vhd_from_secondarystorage(XenServerStorageProcessor.java:846) at com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copyTemplateToPrimaryStorage(XenServerStorageProcessor.java:962) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:77) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:52) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:542) at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:60) at com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:92) at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216) 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-04-23 04:23:46,883 DEBUG [c.c.a.m.DirectAgentAttache] (DirectAgent-3:ctx-cf6a380b) Seq 1-4533998924855246860: Response Received: Checked in xenserver the vhd-util file is missing under /opt/cloud/bin. As work around copied the vhd-util to /opt/cloud/bin. Attaching the log files -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6481) Vhd-util is not copied to xenserver from MS...As a result system VMs fail to start in CS.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015295#comment-14015295 ] Damodar Reddy T commented on CLOUDSTACK-6481: - from the logs, it could not find the vhd-util file at /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver location. We need to install vhd-util at /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver. Closing this issue as not an issue. Vhd-util is not copied to xenserver from MS...As a result system VMs fail to start in CS. - Key: CLOUDSTACK-6481 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6481 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup, XenServer Affects Versions: 4.4.0 Environment: Xenserver6.2 added to CS 4.4 Reporter: manasaveloori Assignee: Damodar Reddy T Priority: Blocker Fix For: 4.4.0 Attachments: management-server.log PXE booted the Xenserver. Added it to CS 4.4. observed that system vms fails to deploy with Exception: 2014-04-23 04:23:46,875 WARN [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-3:ctx-cf6a380b) Catch Exception com.cloud.utils.exception.CloudRuntimeException for template + due to com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr 5cffabad-fb53-27ad-96eb-a1728623dd7c com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr 5cffabad-fb53-27ad-96eb-a1728623dd7c at com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copy_vhd_from_secondarystorage(XenServerStorageProcessor.java:846) at com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copyTemplateToPrimaryStorage(XenServerStorageProcessor.java:962) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:77) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:52) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:542) at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:60) at com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:92) at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216) 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-04-23 04:23:46,883 DEBUG [c.c.a.m.DirectAgentAttache] (DirectAgent-3:ctx-cf6a380b) Seq 1-4533998924855246860: Response Received: Checked in xenserver the vhd-util file is missing under /opt/cloud/bin. As work around copied the vhd-util to /opt/cloud/bin. Attaching the log files -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CLOUDSTACK-6481) Vhd-util is not copied to xenserver from MS...As a result system VMs fail to start in CS.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015295#comment-14015295 ] Damodar Reddy T edited comment on CLOUDSTACK-6481 at 6/2/14 10:04 AM: -- from the logs, it could not find the vhd-util file at /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver location. We need to install vhd-util at /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver NOT at /usr/share/cloudstack-common/scripts/util/. Closing this issue as not an issue. was (Author: damoder.reddy): from the logs, it could not find the vhd-util file at /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver location. We need to install vhd-util at /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver. Closing this issue as not an issue. Vhd-util is not copied to xenserver from MS...As a result system VMs fail to start in CS. - Key: CLOUDSTACK-6481 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6481 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup, XenServer Affects Versions: 4.4.0 Environment: Xenserver6.2 added to CS 4.4 Reporter: manasaveloori Assignee: Damodar Reddy T Priority: Blocker Fix For: 4.4.0 Attachments: management-server.log PXE booted the Xenserver. Added it to CS 4.4. observed that system vms fails to deploy with Exception: 2014-04-23 04:23:46,875 WARN [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-3:ctx-cf6a380b) Catch Exception com.cloud.utils.exception.CloudRuntimeException for template + due to com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr 5cffabad-fb53-27ad-96eb-a1728623dd7c com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr 5cffabad-fb53-27ad-96eb-a1728623dd7c at com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copy_vhd_from_secondarystorage(XenServerStorageProcessor.java:846) at com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copyTemplateToPrimaryStorage(XenServerStorageProcessor.java:962) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:77) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:52) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:542) at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:60) at com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:92) at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216) 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-04-23 04:23:46,883 DEBUG [c.c.a.m.DirectAgentAttache] (DirectAgent-3:ctx-cf6a380b) Seq 1-4533998924855246860: Response Received: Checked in xenserver the vhd-util file is missing under /opt/cloud/bin. As work around copied the vhd-util to /opt/cloud/bin. Attaching the log files -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6702) [Windows] Give Details to admin in a popup When system properties are changed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T updated CLOUDSTACK-6702: Description: 1. Give necessary progress bar messages to admin before changing the system properties like environment varibales, firewall rules etc.. 2. Move all titles and descriptions to a property file or move to build properties was: 1. Give popups at necessary places to take permission from admin before changing the system properties like environment varibales, firewall rules etc.. 2. Move all titles and descriptions to a property file or move to build properties [Windows] Give Details to admin in a popup When system properties are changed - Key: CLOUDSTACK-6702 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6702 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.5.0 Reporter: Damodar Reddy T Assignee: Damodar Reddy T Fix For: 4.5.0 1. Give necessary progress bar messages to admin before changing the system properties like environment varibales, firewall rules etc.. 2. Move all titles and descriptions to a property file or move to build properties -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6702) [Windows] Give Details to admin as messages When system properties are changed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T updated CLOUDSTACK-6702: Summary: [Windows] Give Details to admin as messages When system properties are changed (was: [Windows] Give Details to admin in a popup When system properties are changed) [Windows] Give Details to admin as messages When system properties are changed -- Key: CLOUDSTACK-6702 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6702 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.5.0 Reporter: Damodar Reddy T Assignee: Damodar Reddy T Fix For: 4.5.0 1. Give necessary progress bar messages to admin before changing the system properties like environment varibales, firewall rules etc.. 2. Move all titles and descriptions to a property file or move to build properties -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6105) Windowsfication of CloudStack Management Server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T updated CLOUDSTACK-6105: Fix Version/s: (was: 4.4.0) 4.5.0 Windowsfication of CloudStack Management Server --- Key: CLOUDSTACK-6105 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6105 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.3.0 Reporter: Damodar Reddy T Assignee: Damodar Reddy T Labels: features Fix For: 4.5.0 Currently Management Server runs on Linux based operating systems. Though it runs on windows under cygwin terminal, there is a need to run it on windows without dependency on cygwin. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6700) [Windows]Give Option to install or not MySql Server along with Main Installer on the same server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T resolved CLOUDSTACK-6700. - Resolution: Fixed [Windows]Give Option to install or not MySql Server along with Main Installer on the same server Key: CLOUDSTACK-6700 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6700 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.5.0 Reporter: Damodar Reddy T Assignee: Damodar Reddy T Fix For: 4.5.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6563) Integrate dependencies into MSI Windows installer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T resolved CLOUDSTACK-6563. - Resolution: Fixed Integrate dependencies into MSI Windows installer - Key: CLOUDSTACK-6563 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6563 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.5.0 Reporter: Damodar Reddy T Assignee: Damodar Reddy T Fix For: 4.5.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6636) [Windows] Can not create Template from ROOT snapshot
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T reassigned CLOUDSTACK-6636: --- Assignee: Damodar Reddy T [Windows] Can not create Template from ROOT snapshot Key: CLOUDSTACK-6636 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6636 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: Future, 4.5.0 Reporter: Damodar Reddy T Assignee: Damodar Reddy T Steps to reproduce the issue 1. Create a snapshot from ROOT disk 2. Goto the above created snapshot 3. Try to create template out of it. It is failing with the following trace. 014-05-12 04:02:01,813 WARN [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-428:ctx-2ece4baa) null due to Illegal character in path at index 47: nfs://10.147.28.7/export/home/damoder/secondary\snapshots/2/3\dc74fe1c-0891-4cb3-aaf2-1c03a25b6d58.vhd java.net.URISyntaxException: Illegal character in path at index 47: nfs://10.147.28.7/export/home/damoder/secondary\snapshots/2/3\dc74fe1c-0891-4cb3-aaf2-1c03a25b6d58.vhd at java.net.URI$Parser.fail(Unknown Source) at java.net.URI$Parser.checkChars(Unknown Source) at java.net.URI$Parser.parseHierarchical(Unknown Source) at java.net.URI$Parser.parse(Unknown Source) at java.net.URI.init(Unknown Source) at com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.createVolumeFromSnapshot(XenServerStorageProcessor.java:1617) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:96) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:52) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:542) at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:60) at com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:93) at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216) 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(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6700) [Windows]Give Option to install or not MySql Server along with Main Installer on the same server
Damodar Reddy T created CLOUDSTACK-6700: --- Summary: [Windows]Give Option to install or not MySql Server along with Main Installer on the same server Key: CLOUDSTACK-6700 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6700 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.5.0 Reporter: Damodar Reddy T Assignee: Damodar Reddy T Fix For: 4.5.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6701) [Windows]Integrate System Seed Template into MSI Installer
Damodar Reddy T created CLOUDSTACK-6701: --- Summary: [Windows]Integrate System Seed Template into MSI Installer Key: CLOUDSTACK-6701 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6701 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.5.0 Reporter: Damodar Reddy T Assignee: Damodar Reddy T Fix For: 4.5.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6702) [Windows] Give Details to admin in a popup When system properties are changed
Damodar Reddy T created CLOUDSTACK-6702: --- Summary: [Windows] Give Details to admin in a popup When system properties are changed Key: CLOUDSTACK-6702 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6702 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.5.0 Reporter: Damodar Reddy T Assignee: Damodar Reddy T Fix For: 4.5.0 1. Give popups at necessary places to take permission from admin before changing the system properties like environment varibales, firewall rules etc.. 2. Move all titles and descriptions to a property file or move to build properties -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6703) [Windows] Try to install as a normal java service (Spawn a java thread)
Damodar Reddy T created CLOUDSTACK-6703: --- Summary: [Windows] Try to install as a normal java service (Spawn a java thread) Key: CLOUDSTACK-6703 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6703 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.5.0 Reporter: Damodar Reddy T Assignee: Damodar Reddy T Fix For: 4.5.0 1, Currently it is started as s tomcat service. Instead of that try to spawn a java thread service 2. Try to add Cloud stack Version some where in the service name or in the registry keys -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6704) [Windows] Localization of the windows installer
Damodar Reddy T created CLOUDSTACK-6704: --- Summary: [Windows] Localization of the windows installer Key: CLOUDSTACK-6704 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6704 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Reporter: Damodar Reddy T Assignee: Damodar Reddy T Fix For: 4.5.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6636) [Windows] Can not create Template from ROOT snapshot
Damodar Reddy T created CLOUDSTACK-6636: --- Summary: [Windows] Can not create Template from ROOT snapshot Key: CLOUDSTACK-6636 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6636 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: Future, 4.5.0 Reporter: Damodar Reddy T Steps to reproduce the issue 1. Create a snapshot from ROOT disk 2. Goto the above created snapshot 3. Try to create template out of it. It is failing with the following trace. 014-05-12 04:02:01,813 WARN [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-428:ctx-2ece4baa) null due to Illegal character in path at index 47: nfs://10.147.28.7/export/home/damoder/secondary\snapshots/2/3\dc74fe1c-0891-4cb3-aaf2-1c03a25b6d58.vhd java.net.URISyntaxException: Illegal character in path at index 47: nfs://10.147.28.7/export/home/damoder/secondary\snapshots/2/3\dc74fe1c-0891-4cb3-aaf2-1c03a25b6d58.vhd at java.net.URI$Parser.fail(Unknown Source) at java.net.URI$Parser.checkChars(Unknown Source) at java.net.URI$Parser.parseHierarchical(Unknown Source) at java.net.URI$Parser.parse(Unknown Source) at java.net.URI.init(Unknown Source) at com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.createVolumeFromSnapshot(XenServerStorageProcessor.java:1617) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:96) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:52) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:542) at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:60) at com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:93) at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216) 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(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6271) Integrate Deploy DB Into windows msi installer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T resolved CLOUDSTACK-6271. - Resolution: Fixed Fix Version/s: (was: 4.4.0) Future Integrate Deploy DB Into windows msi installer -- Key: CLOUDSTACK-6271 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6271 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: Damodar Reddy T Assignee: Damodar Reddy T Fix For: Future Currently MSI Installer assumes that the back end DB is already created. But going further deploy db should be part of installation instead of assumption. of existence -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6271) Integrate Deploy DB Into windows msi installer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T updated CLOUDSTACK-6271: Fix Version/s: 4.5.0 Integrate Deploy DB Into windows msi installer -- Key: CLOUDSTACK-6271 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6271 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: Damodar Reddy T Assignee: Damodar Reddy T Fix For: Future, 4.5.0 Currently MSI Installer assumes that the back end DB is already created. But going further deploy db should be part of installation instead of assumption. of existence -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6563) Integrate dependencies into MSI Windows installer
Damodar Reddy T created CLOUDSTACK-6563: --- Summary: Integrate dependencies into MSI Windows installer Key: CLOUDSTACK-6563 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6563 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.5.0 Reporter: Damodar Reddy T Assignee: Damodar Reddy T Fix For: 4.5.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6304) MySQLSyntaxErrorExceptions and SQLExceptions are seen on catalina.out log during Management Server Deployment
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T resolved CLOUDSTACK-6304. - Resolution: Fixed Please re open if we need to check before removing those indexes and keys instead of throwing warning MySQLSyntaxErrorExceptions and SQLExceptions are seen on catalina.out log during Management Server Deployment - Key: CLOUDSTACK-6304 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6304 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: Chandan Purushothama Assignee: Damodar Reddy T Priority: Critical Fix For: 4.4.0 Attachments: catalina.zip Attached the catalina.out log to the bug report. The log has the details pertaining to the MySQLSyntaxErrorExceptions and SQLExceptions seen during Management Server Installation. -- This message was sent by Atlassian JIRA (v6.2#6252)
