[jira] [Created] (CLOUDSTACK-7037) Unable to add new vm/service to existing LB rule of SSL protocol
Rajesh Battala created CLOUDSTACK-7037: -- Summary: Unable to add new vm/service to existing LB rule of SSL protocol Key: CLOUDSTACK-7037 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7037 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.5.0 Reporter: Rajesh Battala Assignee: Rajesh Battala Priority: Blocker Fix For: 4.5.0 Exception is thrown from nitro api when try to add new vm to LB rule. INFO [o.a.c.f.j.i.AsyncJobMonitor] (API-Job-Executor-20:ctx-eb12ce6b job-82) Add job-82 into job monitoring ERROR [c.c.n.r.NetscalerResource] (DirectAgent-418:ctx-6caefe76) Failed to execute LoadBalancerConfigCommand due to com.citrix.netscaler.nitro.exception.nitro_exception: Operation not permitted at com.citrix.netscaler.nitro.resource.base.base_resource.put_data(base_resource.java:693) at com.citrix.netscaler.nitro.resource.base.base_resource.update_resource(base_resource.java:196) at com.citrix.netscaler.nitro.resource.base.base_resource.update_resource(base_resource.java:180) at com.citrix.netscaler.nitro.resource.config.lb.lbvserver_service_binding.add(lbvserver_service_binding.java:256) at com.cloud.network.resource.NetscalerResource.execute(NetscalerResource.java:650) at com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:427) at com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:416) at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:293) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) 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:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7037) Unable to add new vm/service to existing LB rule of SSL protocol
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14049722#comment-14049722 ] Rajesh Battala commented on CLOUDSTACK-7037: Root Cause: When try to add the VM to LB rule of SSL protocol, first service is getting added with ssl type instead of HTTP. As service is getting created with SSL type and binding to SSL lb vserver which will take HTTP based servers is failing. This bug is introduced by SSL Offload/Terminate feature. I will be fixing this issue by making servvice to be HTTP type when its getting assigned to SSL type lb vserver. Unable to add new vm/service to existing LB rule of SSL protocol Key: CLOUDSTACK-7037 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7037 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.5.0 Reporter: Rajesh Battala Assignee: Rajesh Battala Priority: Blocker Fix For: 4.5.0 Exception is thrown from nitro api when try to add new vm to LB rule. INFO [o.a.c.f.j.i.AsyncJobMonitor] (API-Job-Executor-20:ctx-eb12ce6b job-82) Add job-82 into job monitoring ERROR [c.c.n.r.NetscalerResource] (DirectAgent-418:ctx-6caefe76) Failed to execute LoadBalancerConfigCommand due to com.citrix.netscaler.nitro.exception.nitro_exception: Operation not permitted at com.citrix.netscaler.nitro.resource.base.base_resource.put_data(base_resource.java:693) at com.citrix.netscaler.nitro.resource.base.base_resource.update_resource(base_resource.java:196) at com.citrix.netscaler.nitro.resource.base.base_resource.update_resource(base_resource.java:180) at com.citrix.netscaler.nitro.resource.config.lb.lbvserver_service_binding.add(lbvserver_service_binding.java:256) at com.cloud.network.resource.NetscalerResource.execute(NetscalerResource.java:650) at com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:427) at com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:416) at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:293) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) 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:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7026) mark the test_01_primary_storage_iscsi as test that requires hardware
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14049757#comment-14049757 ] ASF subversion and git services commented on CLOUDSTACK-7026: - Commit a28d65fc4a535b85d3f04e7f2dcccf6ec8092c8f in cloudstack's branch refs/heads/4.4-forward from [~bharat.kumar] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a28d65f ] CLOUDSTACK-7026 mark the test_01_primary_storage_iscsi as test that requires hardware Signed-off-by: Abhinandan Prateek aprat...@apache.org mark the test_01_primary_storage_iscsi as test that requires hardware - Key: CLOUDSTACK-7026 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7026 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.4.0 Reporter: Bharat Kumar Assignee: Bharat Kumar Fix For: 4.4.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7037) Unable to add new vm/service to existing LB rule of SSL protocol
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14049820#comment-14049820 ] ASF subversion and git services commented on CLOUDSTACK-7037: - Commit d64adf59126ec41905977ffb14fde167e7e305aa in cloudstack's branch refs/heads/master from [~rajesh_battala] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d64adf5 ] CLOUDSTACK-7037 Unable to add new vm/service to existing LB rule of SSL protocol Unable to add new vm/service to existing LB rule of SSL protocol Key: CLOUDSTACK-7037 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7037 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.5.0 Reporter: Rajesh Battala Assignee: Rajesh Battala Priority: Blocker Fix For: 4.5.0 Exception is thrown from nitro api when try to add new vm to LB rule. INFO [o.a.c.f.j.i.AsyncJobMonitor] (API-Job-Executor-20:ctx-eb12ce6b job-82) Add job-82 into job monitoring ERROR [c.c.n.r.NetscalerResource] (DirectAgent-418:ctx-6caefe76) Failed to execute LoadBalancerConfigCommand due to com.citrix.netscaler.nitro.exception.nitro_exception: Operation not permitted at com.citrix.netscaler.nitro.resource.base.base_resource.put_data(base_resource.java:693) at com.citrix.netscaler.nitro.resource.base.base_resource.update_resource(base_resource.java:196) at com.citrix.netscaler.nitro.resource.base.base_resource.update_resource(base_resource.java:180) at com.citrix.netscaler.nitro.resource.config.lb.lbvserver_service_binding.add(lbvserver_service_binding.java:256) at com.cloud.network.resource.NetscalerResource.execute(NetscalerResource.java:650) at com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:427) at com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:416) at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:293) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) 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:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6191) Volume provisioning type option
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14049882#comment-14049882 ] Ilia Shakitko commented on CLOUDSTACK-6191: --- Thanks for reacting! Volume provisioning type option --- Key: CLOUDSTACK-6191 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6191 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: KVM, Management Server Reporter: Yoshikazu Nojima Assignee: Yoshikazu Nojima Priority: Minor Fix For: 4.5.0 Thin provisioning of a volume saves consumption of a storage, and fat provisioning minimizes IOPS performance overhead. This feature implements a global setting to provide users an option to select how to provision volumes. Design doc: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Volume+provisioning+type+option -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6665) DHCP does not release ip addresses properly on VPC routers (edithosts.sh)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14049950#comment-14049950
]
ASF subversion and git services commented on CLOUDSTACK-6665:
-
Commit 6d0650bbcd26a7147857548c5f20949d2c986f76 in cloudstack's branch
refs/heads/4.3 from [~jvanliesh...@schubergphilis.com]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6d0650b ]
CLOUDSTACK-6665: A fix for vpc routers not releasing dhcp leases.
Signed-off-by: Sebastien Goasguen run...@gmail.com
DHCP does not release ip addresses properly on VPC routers (edithosts.sh)
-
Key: CLOUDSTACK-6665
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6665
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: SystemVM
Affects Versions: 4.3.0, 4.4.0
Reporter: Remi Bergsma
Priority: Critical
DHCP does not release ip addresses properly on VPC routers (edithosts.sh)
How to reproduce:
- create vpc network with small prefix
- create as many vm’s until all ip address space is consumed
- delete one vm
- now create a vm again: there should be an ip address freed
- it does not work though. Error on router:
/var/log/dnsmasq.log:May 13 12:53:16 dnsmasq-dhcp[32100]: DHCPDISCOVER(eth3)
02:00:00:0d:00:b6 no address available
How to reproduce #2:
- create a vm with static ip
- destroy it
- create vm with same static ip: this ip should be free again
This does not work either:
/var/log/dnsmasq.log:May 13 13:59:41 dnsmasq-dhcp[32100]: DHCPDISCOVER(eth3)
02:00:69:06:00:c1 no address available
Cause:
edithosts.sh is supposed to clean up addresses.
edithosts.sh line 101:
dhcp_release eth0 $ipv4 $(grep $ipv4 $DHCP_LEASES | awk '{print $2}')
/dev/null 21
But it doesn’t work, because eth0 is the link local address on VPC routers.
We should make the interface variable on VPC routers.
It does work fine on redundant routers, for example. Because eth0 is the
actual guest network.
CloudStack reports to the user: Insufficient capacity.
Manual work-around:
Run on the router:
dhcp_release eth3 02:00:69:06:00:c1 10.75.16.8
Replace eth3 with the correct interface.
It logs:
/var/log/messages-20140419:May 13 13:38:29 r-4197-VM cloud: edithosts:
released 10.75.16.8
It now works!
This an annoying bug for users that use static ip’s in their networks. Also
users that deploy a lot of test vm’s in the same network are impacted. Let’s
fix it :-)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6665) DHCP does not release ip addresses properly on VPC routers (edithosts.sh)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14049954#comment-14049954
]
ASF subversion and git services commented on CLOUDSTACK-6665:
-
Commit 0e50cb1246f762e9d1f0ece937395ffb193c6452 in cloudstack's branch
refs/heads/4.3 from [~jvanliesh...@schubergphilis.com]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0e50cb1 ]
CLOUDSTACK-6665: A fix for vpc routers not releasing dhcp leases.
Author: John Nielsen j...@betterservers.com
Signed-off-by: Sebastien Goasguen run...@gmail.com
DHCP does not release ip addresses properly on VPC routers (edithosts.sh)
-
Key: CLOUDSTACK-6665
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6665
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: SystemVM
Affects Versions: 4.3.0, 4.4.0
Reporter: Remi Bergsma
Priority: Critical
DHCP does not release ip addresses properly on VPC routers (edithosts.sh)
How to reproduce:
- create vpc network with small prefix
- create as many vm’s until all ip address space is consumed
- delete one vm
- now create a vm again: there should be an ip address freed
- it does not work though. Error on router:
/var/log/dnsmasq.log:May 13 12:53:16 dnsmasq-dhcp[32100]: DHCPDISCOVER(eth3)
02:00:00:0d:00:b6 no address available
How to reproduce #2:
- create a vm with static ip
- destroy it
- create vm with same static ip: this ip should be free again
This does not work either:
/var/log/dnsmasq.log:May 13 13:59:41 dnsmasq-dhcp[32100]: DHCPDISCOVER(eth3)
02:00:69:06:00:c1 no address available
Cause:
edithosts.sh is supposed to clean up addresses.
edithosts.sh line 101:
dhcp_release eth0 $ipv4 $(grep $ipv4 $DHCP_LEASES | awk '{print $2}')
/dev/null 21
But it doesn’t work, because eth0 is the link local address on VPC routers.
We should make the interface variable on VPC routers.
It does work fine on redundant routers, for example. Because eth0 is the
actual guest network.
CloudStack reports to the user: Insufficient capacity.
Manual work-around:
Run on the router:
dhcp_release eth3 02:00:69:06:00:c1 10.75.16.8
Replace eth3 with the correct interface.
It logs:
/var/log/messages-20140419:May 13 13:38:29 r-4197-VM cloud: edithosts:
released 10.75.16.8
It now works!
This an annoying bug for users that use static ip’s in their networks. Also
users that deploy a lot of test vm’s in the same network are impacted. Let’s
fix it :-)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6665) DHCP does not release ip addresses properly on VPC routers (edithosts.sh)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sebastien goasguen resolved CLOUDSTACK-6665.
Resolution: Fixed
Fix Version/s: 4.3.1
4.4.0
DHCP does not release ip addresses properly on VPC routers (edithosts.sh)
-
Key: CLOUDSTACK-6665
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6665
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: SystemVM
Affects Versions: 4.3.0, 4.4.0
Reporter: Remi Bergsma
Priority: Critical
Fix For: 4.4.0, 4.3.1
DHCP does not release ip addresses properly on VPC routers (edithosts.sh)
How to reproduce:
- create vpc network with small prefix
- create as many vm’s until all ip address space is consumed
- delete one vm
- now create a vm again: there should be an ip address freed
- it does not work though. Error on router:
/var/log/dnsmasq.log:May 13 12:53:16 dnsmasq-dhcp[32100]: DHCPDISCOVER(eth3)
02:00:00:0d:00:b6 no address available
How to reproduce #2:
- create a vm with static ip
- destroy it
- create vm with same static ip: this ip should be free again
This does not work either:
/var/log/dnsmasq.log:May 13 13:59:41 dnsmasq-dhcp[32100]: DHCPDISCOVER(eth3)
02:00:69:06:00:c1 no address available
Cause:
edithosts.sh is supposed to clean up addresses.
edithosts.sh line 101:
dhcp_release eth0 $ipv4 $(grep $ipv4 $DHCP_LEASES | awk '{print $2}')
/dev/null 21
But it doesn’t work, because eth0 is the link local address on VPC routers.
We should make the interface variable on VPC routers.
It does work fine on redundant routers, for example. Because eth0 is the
actual guest network.
CloudStack reports to the user: Insufficient capacity.
Manual work-around:
Run on the router:
dhcp_release eth3 02:00:69:06:00:c1 10.75.16.8
Replace eth3 with the correct interface.
It logs:
/var/log/messages-20140419:May 13 13:38:29 r-4197-VM cloud: edithosts:
released 10.75.16.8
It now works!
This an annoying bug for users that use static ip’s in their networks. Also
users that deploy a lot of test vm’s in the same network are impacted. Let’s
fix it :-)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6665) DHCP does not release ip addresses properly on VPC routers (edithosts.sh)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14049955#comment-14049955
]
sebastien goasguen commented on CLOUDSTACK-6665:
Let's close it, I just committed it to 4.3.1 and talking with Daan this is in
master and 4.4
DHCP does not release ip addresses properly on VPC routers (edithosts.sh)
-
Key: CLOUDSTACK-6665
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6665
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: SystemVM
Affects Versions: 4.3.0, 4.4.0
Reporter: Remi Bergsma
Priority: Critical
Fix For: 4.4.0, 4.3.1
DHCP does not release ip addresses properly on VPC routers (edithosts.sh)
How to reproduce:
- create vpc network with small prefix
- create as many vm’s until all ip address space is consumed
- delete one vm
- now create a vm again: there should be an ip address freed
- it does not work though. Error on router:
/var/log/dnsmasq.log:May 13 12:53:16 dnsmasq-dhcp[32100]: DHCPDISCOVER(eth3)
02:00:00:0d:00:b6 no address available
How to reproduce #2:
- create a vm with static ip
- destroy it
- create vm with same static ip: this ip should be free again
This does not work either:
/var/log/dnsmasq.log:May 13 13:59:41 dnsmasq-dhcp[32100]: DHCPDISCOVER(eth3)
02:00:69:06:00:c1 no address available
Cause:
edithosts.sh is supposed to clean up addresses.
edithosts.sh line 101:
dhcp_release eth0 $ipv4 $(grep $ipv4 $DHCP_LEASES | awk '{print $2}')
/dev/null 21
But it doesn’t work, because eth0 is the link local address on VPC routers.
We should make the interface variable on VPC routers.
It does work fine on redundant routers, for example. Because eth0 is the
actual guest network.
CloudStack reports to the user: Insufficient capacity.
Manual work-around:
Run on the router:
dhcp_release eth3 02:00:69:06:00:c1 10.75.16.8
Replace eth3 with the correct interface.
It logs:
/var/log/messages-20140419:May 13 13:38:29 r-4197-VM cloud: edithosts:
released 10.75.16.8
It now works!
This an annoying bug for users that use static ip’s in their networks. Also
users that deploy a lot of test vm’s in the same network are impacted. Let’s
fix it :-)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6892) Database HA Config prevents mgmt server from starting
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050025#comment-14050025 ] sebastien goasguen commented on CLOUDSTACK-6892: [~adrianlewis] what's your OS and hypervisor ? Database HA Config prevents mgmt server from starting - Key: CLOUDSTACK-6892 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6892 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup, Management Server Affects Versions: Future, 4.3.0, 4.4.0 Environment: MySQL configured for DB HA Reporter: Adrian Lewis Assignee: Hugo Trippaers Priority: Critical When configuring the database HA feature introduced in 4.3, the manangement server fails to create the DB connection due to the mysql connector jar being loaded using tomcat's common class loader but the cloud-plugin-database-mysqlha-4.3.0.jar is loaded by the webapp class loader. The cloud-plugin-database-mysqlha-4.3.0.jar needs to also be loaded from the common class loader instead of webapp class loader. Fix is to declare the cloud-plugin-database-mysqlha-4.3.0.jar under the common.loader section in /etc/cloudstack/management/catalina.properties. Only tested using a fresh install on Centos 6.5 and the public repo packages. Manual fix provided by Damoder Reddy in users mailing list: Looks like we did not change the catalina.properties while refactoring out the mysql connector part -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6892) Database HA Config prevents mgmt server from starting
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050036#comment-14050036 ] Adrian Lewis commented on CLOUDSTACK-6892: -- Using VMware Workstation to run a single CS mgmt VM with two MySQL VMs - all three using Centos 6.5 minimal install. No hypervisor involved - no hosts/clusters etc registered with CS as was just testing the MySQL HA side of things. Database HA Config prevents mgmt server from starting - Key: CLOUDSTACK-6892 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6892 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup, Management Server Affects Versions: Future, 4.3.0, 4.4.0 Environment: MySQL configured for DB HA Reporter: Adrian Lewis Assignee: Hugo Trippaers Priority: Critical When configuring the database HA feature introduced in 4.3, the manangement server fails to create the DB connection due to the mysql connector jar being loaded using tomcat's common class loader but the cloud-plugin-database-mysqlha-4.3.0.jar is loaded by the webapp class loader. The cloud-plugin-database-mysqlha-4.3.0.jar needs to also be loaded from the common class loader instead of webapp class loader. Fix is to declare the cloud-plugin-database-mysqlha-4.3.0.jar under the common.loader section in /etc/cloudstack/management/catalina.properties. Only tested using a fresh install on Centos 6.5 and the public repo packages. Manual fix provided by Damoder Reddy in users mailing list: Looks like we did not change the catalina.properties while refactoring out the mysql connector part -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7038) MySQL Client RPMs not a dependency in CS Packages
Adrian Lewis created CLOUDSTACK-7038: Summary: MySQL Client RPMs not a dependency in CS Packages Key: CLOUDSTACK-7038 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7038 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.3.0, 4.4.0 Environment: Centos or RPM-based distro where MySQL installed on separate server Reporter: Adrian Lewis Priority: Minor Perhaps simple enough to fix in docs but if anyone is installing from packages on Centos, the 'mysql' client package is not installed as a dependency which it should be. Likely not picked up in testing as those installing the 'mysql-server' package will automatically get the client part but for those using MySQL on a separate server, the management server will not start. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6278) Baremetal Advanced Networking support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-6278: --- Affects Version/s: (was: 4.4.0) 4.5.0 Baremetal Advanced Networking support - Key: CLOUDSTACK-6278 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6278 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Baremetal Affects Versions: 4.5.0 Reporter: frank zhang Assignee: frank zhang Fix For: 4.5.0 functional spec link: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Baremetal+Advanced+Networking+Support -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6278) Baremetal Advanced Networking support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-6278: --- Fix Version/s: (was: 4.4.0) 4.5.0 Baremetal Advanced Networking support - Key: CLOUDSTACK-6278 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6278 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Baremetal Affects Versions: 4.5.0 Reporter: frank zhang Assignee: frank zhang Fix For: 4.5.0 functional spec link: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Baremetal+Advanced+Networking+Support -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6278) Baremetal Advanced Networking support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050342#comment-14050342 ] Animesh Chaturvedi commented on CLOUDSTACK-6278: Pushing out to 4.5 Baremetal Advanced Networking support - Key: CLOUDSTACK-6278 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6278 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Baremetal Affects Versions: 4.5.0 Reporter: frank zhang Assignee: frank zhang Fix For: 4.5.0 functional spec link: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Baremetal+Advanced+Networking+Support -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7039) MySQLIntegrityConstraintViolationException during Management Server Start phase: Duplicate entry '1' for key 'PRIMARY'
Chandan Purushothama created CLOUDSTACK-7039: Summary: MySQLIntegrityConstraintViolationException during Management Server Start phase: Duplicate entry '1' for key 'PRIMARY' Key: CLOUDSTACK-7039 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7039 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: Chandan Purushothama Priority: Blocker Fix For: 4.5.0 MySQLIntegrityConstraintViolationException: 2014-07-02 10:03:33,354 INFO [c.c.u.d.GenericDaoBase] (main:null) Cache created: [ name = DiskOfferingDaoImpl status = STATUS_ALIVE eternal = false overflowToDisk = false maxEntriesLocalHeap = 50 maxEntriesLocalDisk = 0 memoryStoreEvictionPolicy = LRU timeToLiveSeconds = 600 timeToIdleSeconds = 300 persistence = none diskExpiryThreadIntervalSeconds = 120 cacheEventListeners: net.sf.ehcache.statistics.LiveCacheStatisticsWrapper hitCount = 0 memoryStoreHitCount = 0 diskStoreHitCount = 0 missCountNotFound = 0 missCountExpired = 0 maxBytesLocalHeap = 0 overflowToOffHeap = false maxBytesLocalOffHeap = 0 maxBytesLocalDisk = 0 pinned = false ] 2014-07-02 10:03:33,398 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught SQLException when inserting system account com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '1' for key 'PRIMARY' at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1040) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2415) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2333) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2318) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at com.cloud.server.ConfigurationServerImpl$3.doInTransactionWithoutResult(ConfigurationServerImpl.java:465) 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.server.ConfigurationServerImpl.saveUser(ConfigurationServerImpl.java:456) at com.cloud.server.ConfigurationServerImpl.persistDefaultValues(ConfigurationServerImpl.java:177) at com.cloud.server.ConfigurationServerImpl.configure(ConfigurationServerImpl.java:165) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:114) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:153) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:110) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:56) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51) at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:339) at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:143) at
[jira] [Updated] (CLOUDSTACK-7039) MySQLIntegrityConstraintViolationException during Management Server Start phase: Duplicate entry '1' for key 'PRIMARY'
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Purushothama updated CLOUDSTACK-7039: - Attachment: management-server.zip MySQLIntegrityConstraintViolationException during Management Server Start phase: Duplicate entry '1' for key 'PRIMARY' -- Key: CLOUDSTACK-7039 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7039 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: Chandan Purushothama Priority: Blocker Fix For: 4.5.0 Attachments: management-server.zip MySQLIntegrityConstraintViolationException: 2014-07-02 10:03:33,354 INFO [c.c.u.d.GenericDaoBase] (main:null) Cache created: [ name = DiskOfferingDaoImpl status = STATUS_ALIVE eternal = false overflowToDisk = false maxEntriesLocalHeap = 50 maxEntriesLocalDisk = 0 memoryStoreEvictionPolicy = LRU timeToLiveSeconds = 600 timeToIdleSeconds = 300 persistence = none diskExpiryThreadIntervalSeconds = 120 cacheEventListeners: net.sf.ehcache.statistics.LiveCacheStatisticsWrapper hitCount = 0 memoryStoreHitCount = 0 diskStoreHitCount = 0 missCountNotFound = 0 missCountExpired = 0 maxBytesLocalHeap = 0 overflowToOffHeap = false maxBytesLocalOffHeap = 0 maxBytesLocalDisk = 0 pinned = false ] 2014-07-02 10:03:33,398 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught SQLException when inserting system account com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '1' for key 'PRIMARY' at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1040) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2415) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2333) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2318) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at com.cloud.server.ConfigurationServerImpl$3.doInTransactionWithoutResult(ConfigurationServerImpl.java:465) 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.server.ConfigurationServerImpl.saveUser(ConfigurationServerImpl.java:456) at com.cloud.server.ConfigurationServerImpl.persistDefaultValues(ConfigurationServerImpl.java:177) at com.cloud.server.ConfigurationServerImpl.configure(ConfigurationServerImpl.java:165) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:114) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:153) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:110) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:56) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167) at
[jira] [Updated] (CLOUDSTACK-7039) MySQLIntegrityConstraintViolationException- Caught SQLException when inserting system account: Duplicate entry '1' for key 'PRIMARY'
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Purushothama updated CLOUDSTACK-7039: - Summary: MySQLIntegrityConstraintViolationException- Caught SQLException when inserting system account: Duplicate entry '1' for key 'PRIMARY' (was: MySQLIntegrityConstraintViolationException during Management Server Start phase: Duplicate entry '1' for key 'PRIMARY') MySQLIntegrityConstraintViolationException- Caught SQLException when inserting system account: Duplicate entry '1' for key 'PRIMARY' Key: CLOUDSTACK-7039 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7039 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: Chandan Purushothama Priority: Blocker Fix For: 4.5.0 Attachments: management-server.zip MySQLIntegrityConstraintViolationException: 2014-07-02 10:03:33,354 INFO [c.c.u.d.GenericDaoBase] (main:null) Cache created: [ name = DiskOfferingDaoImpl status = STATUS_ALIVE eternal = false overflowToDisk = false maxEntriesLocalHeap = 50 maxEntriesLocalDisk = 0 memoryStoreEvictionPolicy = LRU timeToLiveSeconds = 600 timeToIdleSeconds = 300 persistence = none diskExpiryThreadIntervalSeconds = 120 cacheEventListeners: net.sf.ehcache.statistics.LiveCacheStatisticsWrapper hitCount = 0 memoryStoreHitCount = 0 diskStoreHitCount = 0 missCountNotFound = 0 missCountExpired = 0 maxBytesLocalHeap = 0 overflowToOffHeap = false maxBytesLocalOffHeap = 0 maxBytesLocalDisk = 0 pinned = false ] 2014-07-02 10:03:33,398 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught SQLException when inserting system account com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '1' for key 'PRIMARY' at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1040) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2415) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2333) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2318) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at com.cloud.server.ConfigurationServerImpl$3.doInTransactionWithoutResult(ConfigurationServerImpl.java:465) 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.server.ConfigurationServerImpl.saveUser(ConfigurationServerImpl.java:456) at com.cloud.server.ConfigurationServerImpl.persistDefaultValues(ConfigurationServerImpl.java:177) at com.cloud.server.ConfigurationServerImpl.configure(ConfigurationServerImpl.java:165) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:114) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:153) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:110) at
[jira] [Updated] (CLOUDSTACK-7039) MySQLIntegrityConstraintViolationException- Caught SQLException when inserting system account: Duplicate entry '1' for key 'PRIMARY'
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Purushothama updated CLOUDSTACK-7039: - Description: The following bug is hit after starting the 4.5.0 Management Server MySQLIntegrityConstraintViolationException: 2014-07-02 10:03:33,354 INFO [c.c.u.d.GenericDaoBase] (main:null) Cache created: [ name = DiskOfferingDaoImpl status = STATUS_ALIVE eternal = false overflowToDisk = false maxEntriesLocalHeap = 50 maxEntriesLocalDisk = 0 memoryStoreEvictionPolicy = LRU timeToLiveSeconds = 600 timeToIdleSeconds = 300 persistence = none diskExpiryThreadIntervalSeconds = 120 cacheEventListeners: net.sf.ehcache.statistics.LiveCacheStatisticsWrapper hitCount = 0 memoryStoreHitCount = 0 diskStoreHitCount = 0 missCountNotFound = 0 missCountExpired = 0 maxBytesLocalHeap = 0 overflowToOffHeap = false maxBytesLocalOffHeap = 0 maxBytesLocalDisk = 0 pinned = false ] 2014-07-02 10:03:33,398 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught SQLException when inserting system account com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '1' for key 'PRIMARY' at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1040) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2415) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2333) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2318) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at com.cloud.server.ConfigurationServerImpl$3.doInTransactionWithoutResult(ConfigurationServerImpl.java:465) 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.server.ConfigurationServerImpl.saveUser(ConfigurationServerImpl.java:456) at com.cloud.server.ConfigurationServerImpl.persistDefaultValues(ConfigurationServerImpl.java:177) at com.cloud.server.ConfigurationServerImpl.configure(ConfigurationServerImpl.java:165) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:114) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:153) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:110) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:56) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51) at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:339) at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:143) at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:108) at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:945) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:482) at
[jira] [Updated] (CLOUDSTACK-7040) MySQLIntegrityConstraintViolationException- Caught SQLException when inserting system user : Duplicate entry '1' for key 'PRIMARY'
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Purushothama updated CLOUDSTACK-7040: - Attachment: management-server.zip MySQLIntegrityConstraintViolationException- Caught SQLException when inserting system user : Duplicate entry '1' for key 'PRIMARY' -- Key: CLOUDSTACK-7040 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7040 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: Chandan Purushothama Priority: Blocker Fix For: 4.5.0 Attachments: management-server.zip The following bug is hit after starting the 4.5.0 Management Server MySQLIntegrityConstraintViolationException: 2014-07-02 10:08:29,300 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught SQLException when inserting system user com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '1' for key 'PRIMARY' at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1040) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2415) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2333) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2318) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at com.cloud.server.ConfigurationServerImpl$3.doInTransactionWithoutResult(ConfigurationServerImpl.java:475) 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.server.ConfigurationServerImpl.saveUser(ConfigurationServerImpl.java:456) at com.cloud.server.ConfigurationServerImpl.persistDefaultValues(ConfigurationServerImpl.java:177) at com.cloud.server.ConfigurationServerImpl.configure(ConfigurationServerImpl.java:165) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:114) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:153) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:110) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:56) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51) at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:339) at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:143) at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:108) at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:945) at
[jira] [Created] (CLOUDSTACK-7040) MySQLIntegrityConstraintViolationException- Caught SQLException when inserting system user : Duplicate entry '1' for key 'PRIMARY'
Chandan Purushothama created CLOUDSTACK-7040: Summary: MySQLIntegrityConstraintViolationException- Caught SQLException when inserting system user : Duplicate entry '1' for key 'PRIMARY' Key: CLOUDSTACK-7040 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7040 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: Chandan Purushothama Priority: Blocker Fix For: 4.5.0 Attachments: management-server.zip The following bug is hit after starting the 4.5.0 Management Server MySQLIntegrityConstraintViolationException: 2014-07-02 10:08:29,300 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught SQLException when inserting system user com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '1' for key 'PRIMARY' at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1040) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2415) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2333) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2318) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at com.cloud.server.ConfigurationServerImpl$3.doInTransactionWithoutResult(ConfigurationServerImpl.java:475) 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.server.ConfigurationServerImpl.saveUser(ConfigurationServerImpl.java:456) at com.cloud.server.ConfigurationServerImpl.persistDefaultValues(ConfigurationServerImpl.java:177) at com.cloud.server.ConfigurationServerImpl.configure(ConfigurationServerImpl.java:165) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:114) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:153) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:110) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:56) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51) at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:339) at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:143) at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:108) at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:945) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:482) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContext(DefaultModuleDefinitionSet.java:145) at
[jira] [Created] (CLOUDSTACK-7041) MySQLIntegrityConstraintViolationException- Caught SQLExceptions when creating admin account and user: Duplicate entry '2' for key 'PRIMARY'
Chandan Purushothama created CLOUDSTACK-7041: Summary: MySQLIntegrityConstraintViolationException- Caught SQLExceptions when creating admin account and user: Duplicate entry '2' for key 'PRIMARY' Key: CLOUDSTACK-7041 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7041 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: Chandan Purushothama Priority: Blocker Fix For: 4.5.0 The following bug is hit after starting the 4.5.0 Management Server MySQLIntegrityConstraintViolationException: 2014-07-02 10:08:29,304 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught SQLException when creating admin account com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '2' for key 'PRIMARY' at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1040) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2415) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2333) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2318) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at com.cloud.server.ConfigurationServerImpl$3.doInTransactionWithoutResult(ConfigurationServerImpl.java:492) 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.server.ConfigurationServerImpl.saveUser(ConfigurationServerImpl.java:456) at com.cloud.server.ConfigurationServerImpl.persistDefaultValues(ConfigurationServerImpl.java:177) at com.cloud.server.ConfigurationServerImpl.configure(ConfigurationServerImpl.java:165) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:114) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:153) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:110) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:56) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51) at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:339) at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:143) at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:108) at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:945) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:482) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContext(DefaultModuleDefinitionSet.java:145) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$2.with(DefaultModuleDefinitionSet.java:122) at
[jira] [Updated] (CLOUDSTACK-7041) MySQLIntegrityConstraintViolationException- Caught SQLExceptions when creating admin account and user: Duplicate entry '2' for key 'PRIMARY'
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Purushothama updated CLOUDSTACK-7041: - Attachment: management-server.zip MySQLIntegrityConstraintViolationException- Caught SQLExceptions when creating admin account and user: Duplicate entry '2' for key 'PRIMARY' Key: CLOUDSTACK-7041 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7041 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: Chandan Purushothama Priority: Blocker Fix For: 4.5.0 Attachments: management-server.zip The following bug is hit after starting the 4.5.0 Management Server MySQLIntegrityConstraintViolationException: 2014-07-02 10:08:29,304 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught SQLException when creating admin account com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '2' for key 'PRIMARY' at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1040) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2415) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2333) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2318) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at com.cloud.server.ConfigurationServerImpl$3.doInTransactionWithoutResult(ConfigurationServerImpl.java:492) 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.server.ConfigurationServerImpl.saveUser(ConfigurationServerImpl.java:456) at com.cloud.server.ConfigurationServerImpl.persistDefaultValues(ConfigurationServerImpl.java:177) at com.cloud.server.ConfigurationServerImpl.configure(ConfigurationServerImpl.java:165) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:114) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:153) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:110) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:56) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51) at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:339) at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:143) at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:108) at
[jira] [Created] (CLOUDSTACK-7042) MySQLSyntaxErrorException: Table 'cloud.network_group' doesn't exist
Chandan Purushothama created CLOUDSTACK-7042: Summary: MySQLSyntaxErrorException: Table 'cloud.network_group' doesn't exist Key: CLOUDSTACK-7042 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7042 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: Chandan Purushothama Priority: Blocker Fix For: 4.5.0 The following bug is hit after starting the 4.5.0 Management Server MySQLIntegrityConstraintViolationException: 2014-07-02 10:08:29,307 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught SQLException: no network_group com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'cloud.network_group' doesn't exist at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119) at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2283) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) at com.cloud.server.ConfigurationServerImpl$3.doInTransactionWithoutResult(ConfigurationServerImpl.java:513) 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.server.ConfigurationServerImpl.saveUser(ConfigurationServerImpl.java:456) at com.cloud.server.ConfigurationServerImpl.persistDefaultValues(ConfigurationServerImpl.java:177) at com.cloud.server.ConfigurationServerImpl.configure(ConfigurationServerImpl.java:165) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:114) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:153) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:110) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:56) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51) at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:339) at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:143) at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:108) at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:945) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:482) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContext(DefaultModuleDefinitionSet.java:145) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$2.with(DefaultModuleDefinitionSet.java:122) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:245) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:250) at
[jira] [Updated] (CLOUDSTACK-7042) MySQLSyntaxErrorException: Table 'cloud.network_group' doesn't exist
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Purushothama updated CLOUDSTACK-7042: - Attachment: management-server.zip MySQLSyntaxErrorException: Table 'cloud.network_group' doesn't exist Key: CLOUDSTACK-7042 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7042 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: Chandan Purushothama Priority: Blocker Fix For: 4.5.0 Attachments: management-server.zip The following bug is hit after starting the 4.5.0 Management Server MySQLIntegrityConstraintViolationException: 2014-07-02 10:08:29,307 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught SQLException: no network_group com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'cloud.network_group' doesn't exist at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119) at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2283) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) at com.cloud.server.ConfigurationServerImpl$3.doInTransactionWithoutResult(ConfigurationServerImpl.java:513) 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.server.ConfigurationServerImpl.saveUser(ConfigurationServerImpl.java:456) at com.cloud.server.ConfigurationServerImpl.persistDefaultValues(ConfigurationServerImpl.java:177) at com.cloud.server.ConfigurationServerImpl.configure(ConfigurationServerImpl.java:165) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:114) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:153) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:110) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:56) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51) at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:339) at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:143) at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:108) at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:945) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:482) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContext(DefaultModuleDefinitionSet.java:145) at
[jira] [Updated] (CLOUDSTACK-7043) Management server fails to load due to DB Decryption failure
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Purushothama updated CLOUDSTACK-7043: - Attachment: management-server.zip Management server fails to load due to DB Decryption failure Key: CLOUDSTACK-7043 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7043 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: Chandan Purushothama Priority: Blocker Fix For: 4.5.0 Attachments: management-server.zip The following bug is hit after starting the 4.5.0 Management Server == Error while decrypting: == 2014-07-02 10:08:29,533 INFO [c.c.s.ConfigurationServerImpl] (main:null) Processing updateKeyPairs 2014-07-02 10:08:29,533 INFO [c.c.s.ConfigurationServerImpl] (main:null) Keypairs already in database, updating local copy 2014-07-02 10:08:29,587 INFO [c.c.s.ConfigurationServerImpl] (main:null) Going to update systemvm iso with generated keypairs if needed 2014-07-02 10:08:29,587 INFO [c.c.s.ConfigurationServerImpl] (main:null) Trying to inject public and private keys into systemvm iso 2014-07-02 10:08:29,587 DEBUG [c.c.u.s.Script] (main:null) Looking for scripts/vm/systemvm/injectkeys.sh in the classpath 2014-07-02 10:08:29,587 DEBUG [c.c.u.s.Script] (main:null) System resource: null 2014-07-02 10:08:29,589 DEBUG [c.c.u.s.Script] (main:null) Classpath resource: null 2014-07-02 10:08:29,589 DEBUG [c.c.u.s.Script] (main:null) Looking for scripts/vm/systemvm/injectkeys.sh 2014-07-02 10:08:29,589 DEBUG [c.c.u.s.Script] (main:null) Current binaries reside at /usr/share/cloudstack-management/webapps/client/WEB-INF/lib 2014-07-02 10:08:29,590 DEBUG [c.c.u.s.Script] (main:null) Looking for scripts/vm/systemvm/injectkeys.sh in /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/scripts/vm/systemvm/injectkeys.sh 2014-07-02 10:08:29,591 DEBUG [c.c.u.s.Script] (main:null) Looking for scripts/vm/systemvm/injectkeys.sh in /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/scripts/vm/systemvm/injectkeys.sh 2014-07-02 10:08:29,591 DEBUG [c.c.u.s.Script] (main:null) Looking for scripts/vm/systemvm/injectkeys.sh in /usr/share/cloudstack-management/webapps/client/WEB-INF/scripts/vm/systemvm/injectkeys.sh 2014-07-02 10:08:29,591 DEBUG [c.c.u.s.Script] (main:null) Looking for scripts/vm/systemvm/injectkeys.sh in /usr/share/cloudstack-management/webapps/client/scripts/vm/systemvm/injectkeys.sh 2014-07-02 10:08:29,591 DEBUG [c.c.u.s.Script] (main:null) Looking for scripts/vm/systemvm/injectkeys.sh in /usr/share/cloudstack-management/webapps/scripts/vm/systemvm/injectkeys.sh 2014-07-02 10:08:29,591 DEBUG [c.c.u.s.Script] (main:null) Looking for scripts/vm/systemvm/injectkeys.sh in /usr/share/cloudstack-management/scripts/vm/systemvm/injectkeys.sh 2014-07-02 10:08:29,591 DEBUG [c.c.u.s.Script] (main:null) Looking for scripts/vm/systemvm/injectkeys.sh in /usr/share/scripts/vm/systemvm/injectkeys.sh 2014-07-02 10:08:29,591 DEBUG [c.c.u.s.Script] (main:null) Looking for scripts/vm/systemvm/injectkeys.sh in /usr/scripts/vm/systemvm/injectkeys.sh 2014-07-02 10:08:29,591 DEBUG [c.c.u.s.Script] (main:null) Looking for scripts/vm/systemvm/injectkeys.sh in /scripts/vm/systemvm/injectkeys.sh 2014-07-02 10:08:29,591 DEBUG [c.c.u.s.Script] (main:null) Searching in environment.properties 2014-07-02 10:08:29,591 DEBUG [c.c.u.s.Script] (main:null) environment.properties says scripts should be in /usr/share/cloudstack-common 2014-07-02 10:08:29,591 DEBUG [c.c.u.s.Script] (main:null) Looking for scripts/vm/systemvm/injectkeys.sh in /usr/share/cloudstack-common/scripts/vm/systemvm/injectkeys.sh 2014-07-02 10:08:29,591 DEBUG [c.c.u.s.Script] (main:null) Looking for vms/systemvm.iso in the classpath 2014-07-02 10:08:29,592 DEBUG [c.c.u.s.Script] (main:null) System resource: null 2014-07-02 10:08:29,593 DEBUG [c.c.u.s.Script] (main:null) Classpath resource: null 2014-07-02 10:08:29,593 DEBUG [c.c.u.s.Script] (main:null) Looking for vms/systemvm.iso 2014-07-02 10:08:29,593 DEBUG [c.c.u.s.Script] (main:null) Current binaries reside at /usr/share/cloudstack-management/webapps/client/WEB-INF/lib 2014-07-02 10:08:29,593 DEBUG [c.c.u.s.Script] (main:null) Looking for vms/systemvm.iso in /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/vms/systemvm.iso 2014-07-02 10:08:29,593 DEBUG [c.c.u.s.Script] (main:null) Looking for vms/systemvm.iso in /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/vms/systemvm.iso 2014-07-02 10:08:29,593 DEBUG
[jira] [Created] (CLOUDSTACK-7043) Management server fails to load due to DB Decryption failure
Chandan Purushothama created CLOUDSTACK-7043: Summary: Management server fails to load due to DB Decryption failure Key: CLOUDSTACK-7043 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7043 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: Chandan Purushothama Priority: Blocker Fix For: 4.5.0 Attachments: management-server.zip The following bug is hit after starting the 4.5.0 Management Server == Error while decrypting: == 2014-07-02 10:08:29,533 INFO [c.c.s.ConfigurationServerImpl] (main:null) Processing updateKeyPairs 2014-07-02 10:08:29,533 INFO [c.c.s.ConfigurationServerImpl] (main:null) Keypairs already in database, updating local copy 2014-07-02 10:08:29,587 INFO [c.c.s.ConfigurationServerImpl] (main:null) Going to update systemvm iso with generated keypairs if needed 2014-07-02 10:08:29,587 INFO [c.c.s.ConfigurationServerImpl] (main:null) Trying to inject public and private keys into systemvm iso 2014-07-02 10:08:29,587 DEBUG [c.c.u.s.Script] (main:null) Looking for scripts/vm/systemvm/injectkeys.sh in the classpath 2014-07-02 10:08:29,587 DEBUG [c.c.u.s.Script] (main:null) System resource: null 2014-07-02 10:08:29,589 DEBUG [c.c.u.s.Script] (main:null) Classpath resource: null 2014-07-02 10:08:29,589 DEBUG [c.c.u.s.Script] (main:null) Looking for scripts/vm/systemvm/injectkeys.sh 2014-07-02 10:08:29,589 DEBUG [c.c.u.s.Script] (main:null) Current binaries reside at /usr/share/cloudstack-management/webapps/client/WEB-INF/lib 2014-07-02 10:08:29,590 DEBUG [c.c.u.s.Script] (main:null) Looking for scripts/vm/systemvm/injectkeys.sh in /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/scripts/vm/systemvm/injectkeys.sh 2014-07-02 10:08:29,591 DEBUG [c.c.u.s.Script] (main:null) Looking for scripts/vm/systemvm/injectkeys.sh in /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/scripts/vm/systemvm/injectkeys.sh 2014-07-02 10:08:29,591 DEBUG [c.c.u.s.Script] (main:null) Looking for scripts/vm/systemvm/injectkeys.sh in /usr/share/cloudstack-management/webapps/client/WEB-INF/scripts/vm/systemvm/injectkeys.sh 2014-07-02 10:08:29,591 DEBUG [c.c.u.s.Script] (main:null) Looking for scripts/vm/systemvm/injectkeys.sh in /usr/share/cloudstack-management/webapps/client/scripts/vm/systemvm/injectkeys.sh 2014-07-02 10:08:29,591 DEBUG [c.c.u.s.Script] (main:null) Looking for scripts/vm/systemvm/injectkeys.sh in /usr/share/cloudstack-management/webapps/scripts/vm/systemvm/injectkeys.sh 2014-07-02 10:08:29,591 DEBUG [c.c.u.s.Script] (main:null) Looking for scripts/vm/systemvm/injectkeys.sh in /usr/share/cloudstack-management/scripts/vm/systemvm/injectkeys.sh 2014-07-02 10:08:29,591 DEBUG [c.c.u.s.Script] (main:null) Looking for scripts/vm/systemvm/injectkeys.sh in /usr/share/scripts/vm/systemvm/injectkeys.sh 2014-07-02 10:08:29,591 DEBUG [c.c.u.s.Script] (main:null) Looking for scripts/vm/systemvm/injectkeys.sh in /usr/scripts/vm/systemvm/injectkeys.sh 2014-07-02 10:08:29,591 DEBUG [c.c.u.s.Script] (main:null) Looking for scripts/vm/systemvm/injectkeys.sh in /scripts/vm/systemvm/injectkeys.sh 2014-07-02 10:08:29,591 DEBUG [c.c.u.s.Script] (main:null) Searching in environment.properties 2014-07-02 10:08:29,591 DEBUG [c.c.u.s.Script] (main:null) environment.properties says scripts should be in /usr/share/cloudstack-common 2014-07-02 10:08:29,591 DEBUG [c.c.u.s.Script] (main:null) Looking for scripts/vm/systemvm/injectkeys.sh in /usr/share/cloudstack-common/scripts/vm/systemvm/injectkeys.sh 2014-07-02 10:08:29,591 DEBUG [c.c.u.s.Script] (main:null) Looking for vms/systemvm.iso in the classpath 2014-07-02 10:08:29,592 DEBUG [c.c.u.s.Script] (main:null) System resource: null 2014-07-02 10:08:29,593 DEBUG [c.c.u.s.Script] (main:null) Classpath resource: null 2014-07-02 10:08:29,593 DEBUG [c.c.u.s.Script] (main:null) Looking for vms/systemvm.iso 2014-07-02 10:08:29,593 DEBUG [c.c.u.s.Script] (main:null) Current binaries reside at /usr/share/cloudstack-management/webapps/client/WEB-INF/lib 2014-07-02 10:08:29,593 DEBUG [c.c.u.s.Script] (main:null) Looking for vms/systemvm.iso in /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/vms/systemvm.iso 2014-07-02 10:08:29,593 DEBUG [c.c.u.s.Script] (main:null) Looking for vms/systemvm.iso in /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/vms/systemvm.iso 2014-07-02 10:08:29,593 DEBUG [c.c.u.s.Script] (main:null) Looking for vms/systemvm.iso in /usr/share/cloudstack-management/webapps/client/WEB-INF/vms/systemvm.iso 2014-07-02 10:08:29,593 DEBUG [c.c.u.s.Script] (main:null) Looking for vms/systemvm.iso in
[jira] [Commented] (CLOUDSTACK-7000) ListSnapshotPolicy should list by policyid. Introduce updateSnapshotPolicy command
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050653#comment-14050653 ] ASF subversion and git services commented on CLOUDSTACK-7000: - Commit 63c4f028971f80a9dfa32125a3eed71468209497 in cloudstack's branch refs/heads/4.4-forward from [~nitinme] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=63c4f02 ] CLOUDSTACK-7000: Fix bugs in ListSnapshotPolicy and updateSnapshotPolicy command ListSnapshotPolicy should list by policyid. Introduce updateSnapshotPolicy command -- Key: CLOUDSTACK-7000 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7000 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Snapshot Affects Versions: 4.5.0 Reporter: Nitin Mehta Assignee: Nitin Mehta Fix For: 4.5.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7000) ListSnapshotPolicy should list by policyid. Introduce updateSnapshotPolicy command
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050654#comment-14050654 ] ASF subversion and git services commented on CLOUDSTACK-7000: - Commit 1f7a818440b40659be8882e2d52a043d099940e0 in cloudstack's branch refs/heads/master from [~nitinme] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1f7a818 ] CLOUDSTACK-7000: Fix bugs in ListSnapshotPolicy and updateSnapshotPolicy command (cherry picked from commit 63c4f028971f80a9dfa32125a3eed71468209497) ListSnapshotPolicy should list by policyid. Introduce updateSnapshotPolicy command -- Key: CLOUDSTACK-7000 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7000 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Snapshot Affects Versions: 4.5.0 Reporter: Nitin Mehta Assignee: Nitin Mehta Fix For: 4.5.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-7000) ListSnapshotPolicy should list by policyid. Introduce updateSnapshotPolicy command
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-7000. - Resolution: Fixed ListSnapshotPolicy should list by policyid. Introduce updateSnapshotPolicy command -- Key: CLOUDSTACK-7000 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7000 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Snapshot Affects Versions: 4.5.0 Reporter: Nitin Mehta Assignee: Nitin Mehta Fix For: 4.5.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7044) [Automation] Remove getPortableIpRangeServices from common.py and move portableIpRange information to test_data.py
Chandan Purushothama created CLOUDSTACK-7044:
Summary: [Automation] Remove getPortableIpRangeServices from
common.py and move portableIpRange information to test_data.py
Key: CLOUDSTACK-7044
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7044
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
Fix For: 4.5.0
We do not have cloudstack config files present in the code. Hence anyone new
who wants to run the test_portable_ip.py test cases do not have any information
about what needs to be provided in the config file for the tests execution.
Pushing such data to test_data.py gives an idea about what data should be used.
Kindly remove the below method from common.py and add the data to test_data.py.
Please remove the method references from test_portable_ip.py too.
def getPortableIpRangeServices(config):
Reads config values related to portable ip and fills up
services accordingly
services = {}
attributeError = False
if config.portableIpRange.startip:
services[startip] = config.portableIpRange.startip
else:
attributeError = True
if config.portableIpRange.endip:
services[endip] = config.portableIpRange.endip
else:
attributeError = True
if config.portableIpRange.netmask:
services[netmask] = config.portableIpRange.netmask
else:
attributeError = True
if config.portableIpRange.gateway:
services[gateway] = config.portableIpRange.gateway
else:
attributeError = True
if config.portableIpRange.vlan:
services[vlan] = config.portableIpRange.vlan
if attributeError:
services = FAILED
return services
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (CLOUDSTACK-7045) createPrivateGateway/createStaticRoute APIs - Started/Completed events are missing for the commands
Alena Prokharchyk created CLOUDSTACK-7045: - Summary: createPrivateGateway/createStaticRoute APIs - Started/Completed events are missing for the commands Key: CLOUDSTACK-7045 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7045 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Reporter: Alena Prokharchyk Assignee: Alena Prokharchyk Fix For: 4.5.0 createPrivateGateway/createStaticRoute have only Created/Scheduled events published. Started/Completed events are missing as they are not annotated in the service methods called by execute API method. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7046) /volume/storageid in addition to /volume/storage
Vladimir Melnik created CLOUDSTACK-7046: --- Summary: /volume/storageid in addition to /volume/storage Key: CLOUDSTACK-7046 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7046 Project: CloudStack Issue Type: Wish Security Level: Public (Anyone can view this level - this is the default.) Components: API Reporter: Vladimir Melnik Priority: Minor When I query API for some virtualmachine, I'm getting ./virtualmachine/host and ./virtualmachine/hostid in the resulting DOM. But when I query for some volume, I'm getting ./volume/storage, but not getting ./volume/storageid that would be so good to get as a part of the result. Please consider adding the storageid parameter. Thank you! -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6449) System VMs aren't being expunged
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Melnik updated CLOUDSTACK-6449: Priority: Major (was: Minor) System VMs aren't being expunged Key: CLOUDSTACK-6449 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6449 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: SystemVM Affects Versions: 4.2.1 Reporter: Vladimir Melnik CloudStack doesn't expunge a secondary storage VM when you destroy it, so it stays in Expunging state forever. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7047) DeploymentPlanner should include disabled resources only when the VM owner is Admin account
Prachi Damle created CLOUDSTACK-7047: Summary: DeploymentPlanner should include disabled resources only when the VM owner is Admin account Key: CLOUDSTACK-7047 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7047 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Reporter: Prachi Damle Assignee: Prachi Damle Fix For: 4.4.0, 4.5.0 Currently planner includes the disabled resources if caller of the deployVM API is admin. So if admin calls the API on behalf of a user (by passing in account and domainid of user) then disabled resources get included in the planning search. This is not right as the VM owner is a user account and the VM should not go to disabled resources then. Fix needed: DeploymentPlanner should include disabled resources only when the VM owner is Admin account. The disabled resources should be ignored when VM is owned by any other user. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7048) Add usediops parameter to StoragePool API response
Yoshikazu Nojima created CLOUDSTACK-7048: Summary: Add usediops parameter to StoragePool API response Key: CLOUDSTACK-7048 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7048 Project: CloudStack Issue Type: New Feature Security Level: Public (Anyone can view this level - this is the default.) Reporter: Yoshikazu Nojima Assignee: Yoshikazu Nojima Priority: Minor To monitor how many iops are allocated to volumes in total, this ticket adds usediops parameter to StoragePool API response. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6935) Some storage pool filter is not enabled in ZoneWideStoragePoolAllocator
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yoshikazu Nojima resolved CLOUDSTACK-6935. -- Resolution: Fixed Fix Version/s: 4.5.0 Future Some storage pool filter is not enabled in ZoneWideStoragePoolAllocator --- Key: CLOUDSTACK-6935 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6935 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, Storage Controller Reporter: Yoshikazu Nojima Assignee: Yoshikazu Nojima Fix For: Future, 4.5.0 Some storage pool filtering logic like hypervisor type check, storage type check for root volume and avoid list check is not enabled in ZoneWideStoragePoolAllocator. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6191) Volume provisioning type option
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050895#comment-14050895 ] Yoshikazu Nojima commented on CLOUDSTACK-6191: -- I tried to install cloudstack deb package made from master branch to UbuntuServer 14.04, but management server doesn't start up. It may take time to reproduce the bug you reported. Volume provisioning type option --- Key: CLOUDSTACK-6191 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6191 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: KVM, Management Server Reporter: Yoshikazu Nojima Assignee: Yoshikazu Nojima Priority: Minor Fix For: 4.5.0 Thin provisioning of a volume saves consumption of a storage, and fat provisioning minimizes IOPS performance overhead. This feature implements a global setting to provide users an option to select how to provision volumes. Design doc: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Volume+provisioning+type+option -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7049) APIs return sensitive information which CloudStack does not manage and which caller did not request
Demetrius Tsitrelis created CLOUDSTACK-7049: --- Summary: APIs return sensitive information which CloudStack does not manage and which caller did not request Key: CLOUDSTACK-7049 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7049 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: API Affects Versions: 4.4.0 Reporter: Demetrius Tsitrelis Priority: Critical CloudStack stores sensitive information such as passwords and keys. Some of this information it creates such as the users’ secret keys. Admins configure CloudStack with the other types of sensitive information such as host passwords, S3 secret keys, etc. There are two problems with the way the API returns sensitive information: 1) Many of the APIs return the entire state of the modified object on which they operate. For example, if the API to remove a NIC from a VM is called then the response returns the VM password even though the caller did not ask for it. 2) Some of the APIs return sensitive information which is not created nor managed by CloudStack. For instance, the listS3s API returns the S3 secret key. There doesn’t seem to be any legitimate use case for returning this category of information; this type of sensitive data could go into CloudStack for its internal use but should not come out via the API (i.e., CloudStack is not a password manager app!). Substantial changes cannot be made to the API without bumping the API version. A near-term mitigation for these problems then is simply to return empty strings in the response for the sensitive information which is not requested or which is not managed by CloudStack. So for the removeNicFromVirtualMachine API, for instance, return an empty string for the password value. A caller could still use getVMPassword to obtain the password if he needed it since it is CloudStack which generated the VM password. For the S3 case, ALWAYS return an empty value for the S3 secret key since that key is managed by Amazon and not CloudStack. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7045) createPrivateGateway/createStaticRoute APIs - Started/Completed events are missing for the commands
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050905#comment-14050905 ] Alena Prokharchyk commented on CLOUDSTACK-7045: --- Steps for QA to verify the fix: 1) Create VPC. 2) Add private gateway to it. Verify that the 4 events below are generated: ++---+---+ | type | state | description | ++---+---+ | PRIVATE.GATEWAY.CREATE | Created | Successfully created entity for creating VPC private gateway. Private Gateway Id: 5 | | PRIVATE.GATEWAY.CREATE | Scheduled | Applying VPC private gateway. Private gateway Id: 5 | | PRIVATE.GATEWAY.CREATE | Started | Applying VPC private gateway | | PRIVATE.GATEWAY.CREATE | Completed |Successfully completed Applying VPC private gateway. Private Gateway Id: 5 | ++---+---+ 3) Add static route to the gateway. Verify that 4 events below are generated: mysql select type, state, description from event where id =87; +-+---+---+ | type| state | description | +-+---+---+ | STATIC.ROUTE.CREATE | Created | Successfully created entity for creating static route. Static route Id: 2 | | STATIC.ROUTE.CREATE | Scheduled | Applying static route. Static route Id: 2 | | STATIC.ROUTE.CREATE | Started | Applying static route. Static route Id: 2 | | STATIC.ROUTE.CREATE | Completed | Successfully completed creating static route. Static route Id: 2 | +-+---+---+ createPrivateGateway/createStaticRoute APIs - Started/Completed events are missing for the commands --- Key: CLOUDSTACK-7045 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7045 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Reporter: Alena Prokharchyk Assignee: Alena Prokharchyk Fix For: 4.5.0 createPrivateGateway/createStaticRoute have only Created/Scheduled events published. Started/Completed events are missing as they are not annotated in the service methods called by execute API method. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7045) createPrivateGateway/createStaticRoute APIs - Started/Completed events are missing for the commands
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050914#comment-14050914 ] ASF subversion and git services commented on CLOUDSTACK-7045: - Commit 324b5d5a577f7b34afe9c9fc0ad7e6b08b01a543 in cloudstack's branch refs/heads/master from [~alena1108] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=324b5d5 ] CLOUDSTACK-7045: save started/completed events for createPrivateGateway and createStaticRoute apis createPrivateGateway/createStaticRoute APIs - Started/Completed events are missing for the commands --- Key: CLOUDSTACK-7045 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7045 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Reporter: Alena Prokharchyk Assignee: Alena Prokharchyk Fix For: 4.5.0 createPrivateGateway/createStaticRoute have only Created/Scheduled events published. Started/Completed events are missing as they are not annotated in the service methods called by execute API method. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-7045) createPrivateGateway/createStaticRoute APIs - Started/Completed events are missing for the commands
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk resolved CLOUDSTACK-7045. --- Resolution: Fixed createPrivateGateway/createStaticRoute APIs - Started/Completed events are missing for the commands --- Key: CLOUDSTACK-7045 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7045 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Reporter: Alena Prokharchyk Assignee: Alena Prokharchyk Fix For: 4.5.0 createPrivateGateway/createStaticRoute have only Created/Scheduled events published. Started/Completed events are missing as they are not annotated in the service methods called by execute API method. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7047) DeploymentPlanner should include disabled resources only when the VM owner is Admin account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050930#comment-14050930 ] ASF subversion and git services commented on CLOUDSTACK-7047: - Commit 48574f2d606ebddb358457301a3dbaa896e9595c in cloudstack's branch refs/heads/master from [~prachidamle] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=48574f2 ] CLOUDSTACK-7047: DeploymentPlanner should include disabled resources only when the VM owner is Admin account Changes: - removing unused imports DeploymentPlanner should include disabled resources only when the VM owner is Admin account --- Key: CLOUDSTACK-7047 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7047 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Reporter: Prachi Damle Assignee: Prachi Damle Fix For: 4.4.0, 4.5.0 Currently planner includes the disabled resources if caller of the deployVM API is admin. So if admin calls the API on behalf of a user (by passing in account and domainid of user) then disabled resources get included in the planning search. This is not right as the VM owner is a user account and the VM should not go to disabled resources then. Fix needed: DeploymentPlanner should include disabled resources only when the VM owner is Admin account. The disabled resources should be ignored when VM is owned by any other user. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7047) DeploymentPlanner should include disabled resources only when the VM owner is Admin account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050928#comment-14050928 ] ASF subversion and git services commented on CLOUDSTACK-7047: - Commit 9f68870a779d0b969e4fb8f766846537a456e2ad in cloudstack's branch refs/heads/master from [~prachidamle] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9f68870 ] CLOUDSTACK-7047: DeploymentPlanner should include disabled resources only when the VM owner is Admin account Changes: -DeploymentPlanner should include disabled resources only when the VM owner is Admin account. The disabled resources should be ignored when VM is owned by any other user. DeploymentPlanner should include disabled resources only when the VM owner is Admin account --- Key: CLOUDSTACK-7047 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7047 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Reporter: Prachi Damle Assignee: Prachi Damle Fix For: 4.4.0, 4.5.0 Currently planner includes the disabled resources if caller of the deployVM API is admin. So if admin calls the API on behalf of a user (by passing in account and domainid of user) then disabled resources get included in the planning search. This is not right as the VM owner is a user account and the VM should not go to disabled resources then. Fix needed: DeploymentPlanner should include disabled resources only when the VM owner is Admin account. The disabled resources should be ignored when VM is owned by any other user. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7041) MySQLIntegrityConstraintViolationException- Caught SQLExceptions when creating admin account and user: Duplicate entry '2' for key 'PRIMARY'
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Purushothama updated CLOUDSTACK-7041: - Priority: Major (was: Blocker) MySQLIntegrityConstraintViolationException- Caught SQLExceptions when creating admin account and user: Duplicate entry '2' for key 'PRIMARY' Key: CLOUDSTACK-7041 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7041 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: Chandan Purushothama Fix For: 4.5.0 Attachments: management-server.zip The following bug is hit after starting the 4.5.0 Management Server MySQLIntegrityConstraintViolationException: 2014-07-02 10:08:29,304 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught SQLException when creating admin account com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '2' for key 'PRIMARY' at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1040) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2415) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2333) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2318) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at com.cloud.server.ConfigurationServerImpl$3.doInTransactionWithoutResult(ConfigurationServerImpl.java:492) 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.server.ConfigurationServerImpl.saveUser(ConfigurationServerImpl.java:456) at com.cloud.server.ConfigurationServerImpl.persistDefaultValues(ConfigurationServerImpl.java:177) at com.cloud.server.ConfigurationServerImpl.configure(ConfigurationServerImpl.java:165) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:114) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:153) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:110) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:56) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51) at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:339) at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:143) at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:108) at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:945) at
[jira] [Updated] (CLOUDSTACK-7042) MySQLSyntaxErrorException: Table 'cloud.network_group' doesn't exist
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Purushothama updated CLOUDSTACK-7042: - Priority: Major (was: Blocker) MySQLSyntaxErrorException: Table 'cloud.network_group' doesn't exist Key: CLOUDSTACK-7042 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7042 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: Chandan Purushothama Fix For: 4.5.0 Attachments: management-server.zip The following bug is hit after starting the 4.5.0 Management Server MySQLIntegrityConstraintViolationException: 2014-07-02 10:08:29,307 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught SQLException: no network_group com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'cloud.network_group' doesn't exist at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119) at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2283) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) at com.cloud.server.ConfigurationServerImpl$3.doInTransactionWithoutResult(ConfigurationServerImpl.java:513) 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.server.ConfigurationServerImpl.saveUser(ConfigurationServerImpl.java:456) at com.cloud.server.ConfigurationServerImpl.persistDefaultValues(ConfigurationServerImpl.java:177) at com.cloud.server.ConfigurationServerImpl.configure(ConfigurationServerImpl.java:165) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:114) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:153) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:110) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:56) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51) at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:339) at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:143) at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:108) at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:945) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:482) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContext(DefaultModuleDefinitionSet.java:145) at
[jira] [Updated] (CLOUDSTACK-7039) MySQLIntegrityConstraintViolationException- Caught SQLException when inserting system account: Duplicate entry '1' for key 'PRIMARY'
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Purushothama updated CLOUDSTACK-7039: - Priority: Major (was: Blocker) MySQLIntegrityConstraintViolationException- Caught SQLException when inserting system account: Duplicate entry '1' for key 'PRIMARY' Key: CLOUDSTACK-7039 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7039 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: Chandan Purushothama Fix For: 4.5.0 Attachments: management-server.zip The following bug is hit after starting the 4.5.0 Management Server MySQLIntegrityConstraintViolationException: 2014-07-02 10:03:33,354 INFO [c.c.u.d.GenericDaoBase] (main:null) Cache created: [ name = DiskOfferingDaoImpl status = STATUS_ALIVE eternal = false overflowToDisk = false maxEntriesLocalHeap = 50 maxEntriesLocalDisk = 0 memoryStoreEvictionPolicy = LRU timeToLiveSeconds = 600 timeToIdleSeconds = 300 persistence = none diskExpiryThreadIntervalSeconds = 120 cacheEventListeners: net.sf.ehcache.statistics.LiveCacheStatisticsWrapper hitCount = 0 memoryStoreHitCount = 0 diskStoreHitCount = 0 missCountNotFound = 0 missCountExpired = 0 maxBytesLocalHeap = 0 overflowToOffHeap = false maxBytesLocalOffHeap = 0 maxBytesLocalDisk = 0 pinned = false ] 2014-07-02 10:03:33,398 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught SQLException when inserting system account com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '1' for key 'PRIMARY' at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1040) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2415) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2333) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2318) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at com.cloud.server.ConfigurationServerImpl$3.doInTransactionWithoutResult(ConfigurationServerImpl.java:465) 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.server.ConfigurationServerImpl.saveUser(ConfigurationServerImpl.java:456) at com.cloud.server.ConfigurationServerImpl.persistDefaultValues(ConfigurationServerImpl.java:177) at com.cloud.server.ConfigurationServerImpl.configure(ConfigurationServerImpl.java:165) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:114) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:153) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:110) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:56) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167)
[jira] [Updated] (CLOUDSTACK-7040) MySQLIntegrityConstraintViolationException- Caught SQLException when inserting system user : Duplicate entry '1' for key 'PRIMARY'
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Purushothama updated CLOUDSTACK-7040: - Priority: Major (was: Blocker) MySQLIntegrityConstraintViolationException- Caught SQLException when inserting system user : Duplicate entry '1' for key 'PRIMARY' -- Key: CLOUDSTACK-7040 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7040 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: Chandan Purushothama Fix For: 4.5.0 Attachments: management-server.zip The following bug is hit after starting the 4.5.0 Management Server MySQLIntegrityConstraintViolationException: 2014-07-02 10:08:29,300 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught SQLException when inserting system user com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '1' for key 'PRIMARY' at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1040) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2415) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2333) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2318) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at com.cloud.server.ConfigurationServerImpl$3.doInTransactionWithoutResult(ConfigurationServerImpl.java:475) 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.server.ConfigurationServerImpl.saveUser(ConfigurationServerImpl.java:456) at com.cloud.server.ConfigurationServerImpl.persistDefaultValues(ConfigurationServerImpl.java:177) at com.cloud.server.ConfigurationServerImpl.configure(ConfigurationServerImpl.java:165) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:114) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:153) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:110) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:56) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51) at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:339) at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:143) at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:108) at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:945) at
[jira] [Commented] (CLOUDSTACK-7047) DeploymentPlanner should include disabled resources only when the VM owner is Admin account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050956#comment-14050956 ] ASF subversion and git services commented on CLOUDSTACK-7047: - Commit f37b1524892ab805615dbff2c59e5a1d10c116d3 in cloudstack's branch refs/heads/4.4-forward from [~prachidamle] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f37b152 ] CLOUDSTACK-7047: DeploymentPlanner should include disabled resources only when the VM owner is Admin account Changes: - removing unused imports Conflicts: server/src/com/cloud/deploy/DeploymentPlanningManagerImpl.java DeploymentPlanner should include disabled resources only when the VM owner is Admin account --- Key: CLOUDSTACK-7047 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7047 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Reporter: Prachi Damle Assignee: Prachi Damle Fix For: 4.4.0, 4.5.0 Currently planner includes the disabled resources if caller of the deployVM API is admin. So if admin calls the API on behalf of a user (by passing in account and domainid of user) then disabled resources get included in the planning search. This is not right as the VM owner is a user account and the VM should not go to disabled resources then. Fix needed: DeploymentPlanner should include disabled resources only when the VM owner is Admin account. The disabled resources should be ignored when VM is owned by any other user. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7047) DeploymentPlanner should include disabled resources only when the VM owner is Admin account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050957#comment-14050957 ] ASF subversion and git services commented on CLOUDSTACK-7047: - Commit 40e28de7275804f4483868ba8a737878ff54fba8 in cloudstack's branch refs/heads/4.4-forward from [~prachidamle] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=40e28de ] CLOUDSTACK-7047: DeploymentPlanner should include disabled resources only when the VM owner is Admin account Changes: -DeploymentPlanner should include disabled resources only when the VM owner is Admin account. The disabled resources should be ignored when VM is owned by any other user. DeploymentPlanner should include disabled resources only when the VM owner is Admin account --- Key: CLOUDSTACK-7047 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7047 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Reporter: Prachi Damle Assignee: Prachi Damle Fix For: 4.4.0, 4.5.0 Currently planner includes the disabled resources if caller of the deployVM API is admin. So if admin calls the API on behalf of a user (by passing in account and domainid of user) then disabled resources get included in the planning search. This is not right as the VM owner is a user account and the VM should not go to disabled resources then. Fix needed: DeploymentPlanner should include disabled resources only when the VM owner is Admin account. The disabled resources should be ignored when VM is owned by any other user. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7051) [Automation] Failed to create SSVM and CPVM in KVM,
Rayees Namathponnan created CLOUDSTACK-7051: --- Summary: [Automation] Failed to create SSVM and CPVM in KVM, Key: CLOUDSTACK-7051 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7051 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.5.0 Environment: RHEL : 6.3 build : 4.5 Reporter: Rayees Namathponnan Priority: Blocker Fix For: 4.5.0 SSVM and CPVM not creating with latest 4.5 build, copy command failing form agent observed below error in agent log, 2014-07-02 16:14:58,170 DEBUG [utils.script.Script] (agentRequest-Handler-1:null) Execution is successful. 2014-07-02 16:14:58,171 DEBUG [utils.script.Script] (agentRequest-Handler-1:null) Formatting '/mnt/4f3ad80a-b7 96-3db3-b126-9c12b5b5eafc/48ef9a74-0244-11e4-b040-1a6f7bb0d0a8', fmt=qcow2 size=262144 encryption=off clus ter_size=65536 preallocation='off' 2014-07-02 16:14:58,171 DEBUG [utils.script.Script] (agentRequest-Handler-1:null) Executing: qemu-img info --o utput json /mnt/4f3ad80a-b796-3db3-b126-9c12b5b5eafc/48ef9a74-0244-11e4-b040-1a6f7bb0d0a8 2014-07-02 16:14:58,173 DEBUG [utils.script.Script] (agentRequest-Handler-1:null) Exit value is 1 2014-07-02 16:14:58,173 DEBUG [utils.script.Script] (agentRequest-Handler-1:null) info: invalid option -- '-'q emu-img version 0.12.1, Copyright (c) 2004-2008 Fabrice Bellardusage: qemu-img command [command options]QEMU d isk image utilityCommand syntax: check [-f fmt] filename create [-f fmt] [-o options] filename [size] commi t [-f fmt] [-t cache] filename convert [-c] [-p] [-f fmt] [-t cache] [-O output_fmt] [-o options] [-S sparse_ size] filename [filename2 [...]] output_filename info [-f fmt] filename snapshot [-l | -a snapshot | -c snap shot | -d snapshot] filename rebase [-f fmt] [-t cache] [-p] [-u] -b backing_file [-F backing_fmt] filename resize filename [+ | -]sizeCommand parameters: 'filename' is a disk image filename 'fmt' is the disk image f ormat. It is guessed automatically in most cases 'cache' is the cache mode used to write the output disk imag e, the validoptions are: 'none', 'writeback' (default), 'writethrough' and 'unsafe' 'size' is the disk im age size in bytes. Optional suffixes'k' or 'K' (kilobyte, 1024), 'M' (megabyte, 1024k), 'G' (gigabyte, 102 4M)and T (terabyte, 1024G) are supported. 'b' is ignored. 'output_filename' is the destination disk image filename 'output_fmt' is the destination format 'options' is a comma separated list of format specific opti ons in aname=value format. Use -o ? for an overview of the options supported by theused format '-c' i ndicates that target image must be compressed (qcow format only) '-u' enables unsafe rebasing. It is assumed that old and new backing file match exactly. The image doesn't need a working backing file before rebasing in this case (useful for renaming the backing file) '-h' with or without a command shows this help a nd lists the supported formats '-p' show progress of command (only certain commands) '-S' indicates the cons ecutive number of bytes that must contain only zeros for qemu-img to create a sparse image during conver sionParameters to snapshot subcommand: 'snapshot' is the name of the snapshot to create, apply or delete '-a ' applies a snapshot (revert disk to saved state) '-c' creates a snapshot '-d' deletes a snapshot '-l' lists all snapshots in the given imageSupported formats: raw cow qcow vdi vmdk cloop dmg bochs vpc vvfat qcow2 qed parallels nbd blkdebug host_cdrom host_floppy host_device file -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7051) [Automation] Failed to create SSVM and CPVM in KVM,
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan updated CLOUDSTACK-7051: Attachment: agent.rar management-server.rar [Automation] Failed to create SSVM and CPVM in KVM, Key: CLOUDSTACK-7051 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7051 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.5.0 Environment: RHEL : 6.3 build : 4.5 Reporter: Rayees Namathponnan Priority: Blocker Fix For: 4.5.0 Attachments: agent.rar, management-server.rar SSVM and CPVM not creating with latest 4.5 build, copy command failing form agent observed below error in agent log, 2014-07-02 16:14:58,170 DEBUG [utils.script.Script] (agentRequest-Handler-1:null) Execution is successful. 2014-07-02 16:14:58,171 DEBUG [utils.script.Script] (agentRequest-Handler-1:null) Formatting '/mnt/4f3ad80a-b7 96-3db3-b126-9c12b5b5eafc/48ef9a74-0244-11e4-b040-1a6f7bb0d0a8', fmt=qcow2 size=262144 encryption=off clus ter_size=65536 preallocation='off' 2014-07-02 16:14:58,171 DEBUG [utils.script.Script] (agentRequest-Handler-1:null) Executing: qemu-img info --o utput json /mnt/4f3ad80a-b796-3db3-b126-9c12b5b5eafc/48ef9a74-0244-11e4-b040-1a6f7bb0d0a8 2014-07-02 16:14:58,173 DEBUG [utils.script.Script] (agentRequest-Handler-1:null) Exit value is 1 2014-07-02 16:14:58,173 DEBUG [utils.script.Script] (agentRequest-Handler-1:null) info: invalid option -- '-'q emu-img version 0.12.1, Copyright (c) 2004-2008 Fabrice Bellardusage: qemu-img command [command options]QEMU d isk image utilityCommand syntax: check [-f fmt] filename create [-f fmt] [-o options] filename [size] commi t [-f fmt] [-t cache] filename convert [-c] [-p] [-f fmt] [-t cache] [-O output_fmt] [-o options] [-S sparse_ size] filename [filename2 [...]] output_filename info [-f fmt] filename snapshot [-l | -a snapshot | -c snap shot | -d snapshot] filename rebase [-f fmt] [-t cache] [-p] [-u] -b backing_file [-F backing_fmt] filename resize filename [+ | -]sizeCommand parameters: 'filename' is a disk image filename 'fmt' is the disk image f ormat. It is guessed automatically in most cases 'cache' is the cache mode used to write the output disk imag e, the validoptions are: 'none', 'writeback' (default), 'writethrough' and 'unsafe' 'size' is the disk im age size in bytes. Optional suffixes'k' or 'K' (kilobyte, 1024), 'M' (megabyte, 1024k), 'G' (gigabyte, 102 4M)and T (terabyte, 1024G) are supported. 'b' is ignored. 'output_filename' is the destination disk image filename 'output_fmt' is the destination format 'options' is a comma separated list of format specific opti ons in aname=value format. Use -o ? for an overview of the options supported by theused format '-c' i ndicates that target image must be compressed (qcow format only) '-u' enables unsafe rebasing. It is assumed that old and new backing file match exactly. The image doesn't need a working backing file before rebasing in this case (useful for renaming the backing file) '-h' with or without a command shows this help a nd lists the supported formats '-p' show progress of command (only certain commands) '-S' indicates the cons ecutive number of bytes that must contain only zeros for qemu-img to create a sparse image during conver sionParameters to snapshot subcommand: 'snapshot' is the name of the snapshot to create, apply or delete '-a ' applies a snapshot (revert disk to saved state) '-c' creates a snapshot '-d' deletes a snapshot '-l' lists all snapshots in the given imageSupported formats: raw cow qcow vdi vmdk cloop dmg bochs vpc vvfat qcow2 qed parallels nbd blkdebug host_cdrom host_floppy host_device file -- This message was sent by Atlassian JIRA (v6.2#6252)
