[jira] [Created] (CLOUDSTACK-8909) Web Console not working with Hyper-V Windows Server 2012 R2

2015-09-24 Thread Thomas (JIRA)
Thomas created CLOUDSTACK-8909:
--

 Summary: Web Console not working with Hyper-V Windows Server 2012 
R2
 Key: CLOUDSTACK-8909
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8909
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: VNC Proxy
Affects Versions: 4.5.2
 Environment: Redundant Management Server Cluster, CentOS7. Two Zones, 
one for XEN, one for Hyper-V
Two xen hosts, two Hyper-V hosts
Reporter: Thomas
Priority: Critical


Webconsole is not working with Hyper-V
Only a black Screen is showing up in console proxy browser window.
I already tried to debug it with:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/View+Console+and+Console+Proxy+Troubleshooting
Everything seems to be fine.

I also used the rdp-config.bat on the hosts:
https://github.com/apache/cloudstack/blob/master/services/console-proxy-rdp/rdpconsole/rdp-config.bat

Firewall on the hyperv hosts is off.

Logs Management Servers:
2015-09-24 17:01:19,387 INFO  [o.a.c.f.j.i.AsyncJobManagerImpl] 
(AsyncJobMgr-Heartbeat-1:ctx-6af52d42) Begin cleanup expired async-jobs
2015-09-24 17:01:19,392 INFO  [o.a.c.f.j.i.AsyncJobManagerImpl] 
(AsyncJobMgr-Heartbeat-1:ctx-6af52d42) End cleanup expired async-jobs
2015-09-24 17:01:21,100 DEBUG [c.c.a.m.AgentManagerImpl] 
(AgentManager-Handler-13:null) SeqA 14-4610: Processing Seq 14-4610:  { Cmd , 
MgmtId: -1, via: 14, Ver: v1, Flags: 11, 
[{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":75,"_loadInfo":"{\n
  \"connections\": [\n{\n  \"id\": 6,\n  \"clientInfo\": \"\",\n
  \"host\": \"9D626339-6969-407D-98F7-51308B3F5F47\",\n  \"port\": 2179,\n  
\"tag\": \"5e76b628-73da-4c39-aaf6-9df7f3b26cef\",\n  \"createTime\": 
1443106699001,\n  \"lastUsedTime\": 1443106877898\n}\n  
]\n}","wait":0}}] }
2015-09-24 17:01:21,103 DEBUG [c.c.a.m.AgentManagerImpl] 
(AgentManager-Handler-13:null) SeqA 14-4610: Sending Seq 14-4610:  { Ans: , 
MgmtId: 146454695956, via: 14, Ver: v1, Flags: 100010, 
[{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
2015-09-24 17:01:21,158 DEBUG [c.c.a.m.DirectAgentAttache] 
(DirectAgent-181:ctx-beeaa240) Seq 3-1841972247594567063: Executing request
2015-09-24 17:01:21,223 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-181:ctx-beeaa240) Vm cpu utilization 0.11527
2015-09-24 17:01:21,223 DEBUG [c.c.a.m.DirectAgentAttache] 
(DirectAgent-181:ctx-beeaa240) Seq 3-1841972247594567063: Response Received:
2015-09-24 17:01:21,223 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] 
(DirectAgent-181:ctx-beeaa240) Seq 3-1841972247594567063: MgmtId 146454790969: 
Resp: Routing to peer
2015-09-24 17:01:21,243 DEBUG [c.c.a.m.DirectAgentAttache] 
(DirectAgent-372:ctx-ee7a486a) Seq 4-7128353785197397239: Executing request
2015-09-24 17:01:21,285 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-372:ctx-ee7a486a) Vm cpu utilization 0.19724
2015-09-24 17:01:21,285 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-372:ctx-ee7a486a) Vm cpu utilization 0.11638
2015-09-24 17:01:21,285 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-372:ctx-ee7a486a) Vm cpu utilization 0.20613
2015-09-24 17:01:21,285 DEBUG [c.c.a.m.DirectAgentAttache] 
(DirectAgent-372:ctx-ee7a486a) Seq 4-7128353785197397239: Response Received:
2015-09-24 17:01:21,286 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] 
(DirectAgent-372:ctx-ee7a486a) Seq 4-7128353785197397239: MgmtId 146454790969: 
Resp: Routing to peer
2015-09-24 17:01:21,302 DEBUG [c.c.a.m.DirectAgentAttache] 
(DirectAgent-370:ctx-f4af3477) Seq 11-5374201730336556383: Executing request
2015-09-24 17:01:21,303 DEBUG [c.c.h.h.r.HypervDirectConnectResource] 
(DirectAgent-370:ctx-f4af3477) POST request to 
https://192.168.4.63:8250/api/HypervResource/com.cloud.agent.api.GetVmStatsCommand
 with contents 
{"vmNames":["i-2-81-VM"],"hostGuid":"6fa76640-72db-38ba-a034-5d70a0d43fc6-HypervResource","hostName":"192.168.4.63","contextMap":{},"wait":0}
2015-09-24 17:01:21,306 DEBUG [c.c.h.h.r.HypervDirectConnectResource] 
(DirectAgent-370:ctx-f4af3477) Sending cmd to 
https://192.168.4.63:8250/api/HypervResource/com.cloud.agent.api.GetVmStatsCommand
 cmd 
data:{"vmNames":["i-2-81-VM"],"hostGuid":"6fa76640-72db-38ba-a034-5d70a0d43fc6-HypervResource","hostName":"192.168.4.63","contextMap":{},"wait":0}
2015-09-24 17:01:21,580 DEBUG [c.c.h.h.r.HypervDirectConnectResource] 
(DirectAgent-370:ctx-f4af3477) POST response is 
[{"com.cloud.agent.api.GetVmStatsAnswer":{"vmStatsMap":{"i-2-81-VM":{"cpuUtilization":0.0,"networkReadKBs":1.0,"networkWriteKBs":1.0,"numCPUs":1,"entityType":"vm"}},"result":true,"contextMap":{}}}]
2015-09-24 17:01:21,581 DEBUG [c.c.h.h.r.HypervDirectConnectResource] 
(DirectAgent-370:ctx-f4af3477) executeRequest received response 
[{

[jira] [Commented] (CLOUDSTACK-8923) Create storage network IP range failed, Unknown parameters : zoneid

2015-10-01 Thread Thomas (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14940482#comment-14940482
 ] 

Thomas commented on CLOUDSTACK-8923:


I also habe this issue. Installed master build via Jenkins packages.

> Create storage network IP range failed, Unknown parameters : zoneid
> ---
>
> Key: CLOUDSTACK-8923
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8923
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Secondary Storage
>Affects Versions: 4.6.0
> Environment: CentOS 6 HVs and MGMT
>Reporter: Nux
>Priority: Blocker
>
> I am installing ACS from today's master (3ded3e9 
> http://tmp.nux.ro/acs460snap/ ). 
> Adding an initial zone via the web UI wizard fails at the secondary storage 
> setup stage:
> 2015-09-29 14:07:40,319 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
> (API-Job-Executor-25:ctx-73c1ad88 job-27) Add job-27 into job monitoring
> 2015-09-29 14:07:40,322 DEBUG [c.c.a.ApiServlet] 
> (catalina-exec-5:ctx-314bbaae ctx-2db63923) ===END===  85.13.192.198 -- GET  
> command=createStorageNetworkIpRange&response=json&gateway=192.168.200.67&netmask=255.255.255.0&vlan=123&startip=192.168.200.200&endip=192.168.200.222&zoneid=2f0efdcf-adf6-4373-858e-87de6af4cc08&podid=eb7814d2-9a22-4ca4-93af-4a6b8abac67c&_=1443532060283
> 2015-09-29 14:07:40,327 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
> (API-Job-Executor-25:ctx-73c1ad88 job-27) Executing AsyncJobVO {id:27, 
> userId: 2, accountId: 2, instanceType: None, instanceId: null, cmd: 
> org.apache.cloudstack.api.command.admin.network.CreateStorageNetworkIpRangeCmd,
>  cmdInfo: {"response":"json","ctxDetails":"{\"interface 
> com.cloud.dc.Pod\":\"eb7814d2-9a22-4ca4-93af-4a6b8abac67c\"}","cmdEventType":"STORAGE.IP.RANGE.CREATE","ctxUserId":"2","gateway":"192.168.200.67","podid":"eb7814d2-9a22-4ca4-93af-4a6b8abac67c","zoneid":"2f0efdcf-adf6-4373-858e-87de6af4cc08","startip":"192.168.200.200","vlan":"123","httpmethod":"GET","_":"1443532060283","ctxAccountId":"2","ctxStartEventId":"68","netmask":"255.255.255.0","endip":"192.168.200.222"},
>  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
> null, initMsid: 266785867798693, completeMsid: null, lastUpdated: null, 
> lastPolled: null, created: null}
> 2015-09-29 14:07:40,330 WARN  [c.c.a.d.ParamGenericValidationWorker] 
> (API-Job-Executor-25:ctx-73c1ad88 job-27 ctx-1fa03c4a) Received unknown 
> parameters for command createStorageNetworkIpRange. Unknown parameters : 
> zoneid
> 2015-09-29 14:07:40,391 WARN  [o.a.c.a.c.a.n.CreateStorageNetworkIpRangeCmd] 
> (API-Job-Executor-25:ctx-73c1ad88 job-27 ctx-1fa03c4a) Create storage network 
> IP range failed
> com.cloud.utils.exception.CloudRuntimeException: Unable to commit or close 
> the connection. 
>   at 
> com.cloud.utils.db.TransactionLegacy.commit(TransactionLegacy.java:730)
>   at com.cloud.utils.db.Transaction.execute(Transaction.java:46)
>   at 
> com.cloud.network.StorageNetworkManagerImpl.createIpRange(StorageNetworkManagerImpl.java:229)
>   at 
> org.apache.cloudstack.api.command.admin.network.CreateStorageNetworkIpRangeCmd.execute(CreateStorageNetworkIpRangeCmd.java:118)
>   at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:150)
>   at 
> com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
>   at 
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:537)
>   at 
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
>   at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
>   at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
>   at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
>   at 
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
>   at 
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:494)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.sql.SQLException: Connection is closed.
>   at 
> org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectio

[jira] [Comment Edited] (CLOUDSTACK-8923) Create storage network IP range failed, Unknown parameters : zoneid

2015-10-01 Thread Thomas (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14940482#comment-14940482
 ] 

Thomas edited comment on CLOUDSTACK-8923 at 10/2/15 6:38 AM:
-

I also have this issue. Installed master build via Jenkins packages.


was (Author: disappear):
I also habe this issue. Installed master build via Jenkins packages.

> Create storage network IP range failed, Unknown parameters : zoneid
> ---
>
> Key: CLOUDSTACK-8923
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8923
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Secondary Storage
>Affects Versions: 4.6.0
> Environment: CentOS 6 HVs and MGMT
>Reporter: Nux
>Priority: Blocker
>
> I am installing ACS from today's master (3ded3e9 
> http://tmp.nux.ro/acs460snap/ ). 
> Adding an initial zone via the web UI wizard fails at the secondary storage 
> setup stage:
> 2015-09-29 14:07:40,319 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
> (API-Job-Executor-25:ctx-73c1ad88 job-27) Add job-27 into job monitoring
> 2015-09-29 14:07:40,322 DEBUG [c.c.a.ApiServlet] 
> (catalina-exec-5:ctx-314bbaae ctx-2db63923) ===END===  85.13.192.198 -- GET  
> command=createStorageNetworkIpRange&response=json&gateway=192.168.200.67&netmask=255.255.255.0&vlan=123&startip=192.168.200.200&endip=192.168.200.222&zoneid=2f0efdcf-adf6-4373-858e-87de6af4cc08&podid=eb7814d2-9a22-4ca4-93af-4a6b8abac67c&_=1443532060283
> 2015-09-29 14:07:40,327 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
> (API-Job-Executor-25:ctx-73c1ad88 job-27) Executing AsyncJobVO {id:27, 
> userId: 2, accountId: 2, instanceType: None, instanceId: null, cmd: 
> org.apache.cloudstack.api.command.admin.network.CreateStorageNetworkIpRangeCmd,
>  cmdInfo: {"response":"json","ctxDetails":"{\"interface 
> com.cloud.dc.Pod\":\"eb7814d2-9a22-4ca4-93af-4a6b8abac67c\"}","cmdEventType":"STORAGE.IP.RANGE.CREATE","ctxUserId":"2","gateway":"192.168.200.67","podid":"eb7814d2-9a22-4ca4-93af-4a6b8abac67c","zoneid":"2f0efdcf-adf6-4373-858e-87de6af4cc08","startip":"192.168.200.200","vlan":"123","httpmethod":"GET","_":"1443532060283","ctxAccountId":"2","ctxStartEventId":"68","netmask":"255.255.255.0","endip":"192.168.200.222"},
>  cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
> null, initMsid: 266785867798693, completeMsid: null, lastUpdated: null, 
> lastPolled: null, created: null}
> 2015-09-29 14:07:40,330 WARN  [c.c.a.d.ParamGenericValidationWorker] 
> (API-Job-Executor-25:ctx-73c1ad88 job-27 ctx-1fa03c4a) Received unknown 
> parameters for command createStorageNetworkIpRange. Unknown parameters : 
> zoneid
> 2015-09-29 14:07:40,391 WARN  [o.a.c.a.c.a.n.CreateStorageNetworkIpRangeCmd] 
> (API-Job-Executor-25:ctx-73c1ad88 job-27 ctx-1fa03c4a) Create storage network 
> IP range failed
> com.cloud.utils.exception.CloudRuntimeException: Unable to commit or close 
> the connection. 
>   at 
> com.cloud.utils.db.TransactionLegacy.commit(TransactionLegacy.java:730)
>   at com.cloud.utils.db.Transaction.execute(Transaction.java:46)
>   at 
> com.cloud.network.StorageNetworkManagerImpl.createIpRange(StorageNetworkManagerImpl.java:229)
>   at 
> org.apache.cloudstack.api.command.admin.network.CreateStorageNetworkIpRangeCmd.execute(CreateStorageNetworkIpRangeCmd.java:118)
>   at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:150)
>   at 
> com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
>   at 
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:537)
>   at 
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
>   at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
>   at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
>   at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
>   at 
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
>   at 
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:494)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thre

[jira] [Commented] (CLOUDSTACK-8444) [Hyper-V] Add a Failover Clustering of Hyper-V support in CloudStack

2015-11-13 Thread Thomas (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15005043#comment-15005043
 ] 

Thomas commented on CLOUDSTACK-8444:


Hey any updates in this ?
4.6 will be released soon, so will this be a new feature?

> [Hyper-V] Add a Failover Clustering of Hyper-V support in CloudStack
> 
>
> Key: CLOUDSTACK-8444
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8444
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Anshul Gangwar
>Assignee: Anshul Gangwar
>
> This will enable us to add support for HA and cluster shared volume in Hyper-V



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


[jira] [Comment Edited] (CLOUDSTACK-8444) [Hyper-V] Add a Failover Clustering of Hyper-V support in CloudStack

2015-11-16 Thread Thomas (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15005043#comment-15005043
 ] 

Thomas edited comment on CLOUDSTACK-8444 at 11/16/15 3:27 PM:
--

Hey any updates on this ?
4.6 will be released soon, so will this be a new feature?


was (Author: disappear):
Hey any updates in this ?
4.6 will be released soon, so will this be a new feature?

> [Hyper-V] Add a Failover Clustering of Hyper-V support in CloudStack
> 
>
> Key: CLOUDSTACK-8444
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8444
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Anshul Gangwar
>Assignee: Anshul Gangwar
>
> This will enable us to add support for HA and cluster shared volume in Hyper-V



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


[jira] [Created] (CLOUDSTACK-9209) Database HA not working on a fresh install on Ubuntu 12.04

2016-01-05 Thread Thomas (JIRA)
Thomas created CLOUDSTACK-9209:
--

 Summary: Database HA not working on a fresh install on Ubuntu 12.04
 Key: CLOUDSTACK-9209
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9209
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Install and Setup
Affects Versions: 4.7.0
 Environment: Two Ubuntu 12.04 Management Servers, Mysql Master Master 
Replication, Official community repository: 
http://cloudstack.apt-get.eu/ubuntu/dists/precise/4.7/
Reporter: Thomas
Priority: Blocker


The cloudstack-management service will not come up because of this error:
2016-01-05 16:15:00,899 INFO  [c.c.u.d.T.Transaction] (main:null) (logid:) Is 
Data Base High Availiability enabled? Ans : true
2016-01-05 16:15:00,924 INFO  [c.c.u.d.T.Transaction] (main:null) (logid:) The 
slaves configured for Cloud Data base is/are : 192.168.0.90
2016-01-05 16:15:00,974 ERROR [c.c.u.d.Merovingian2] (main:null) (logid:) 
Unable to get a new db connection
java.sql.SQLException: Invalid load balancing strategy 
'com.cloud.utils.db.StaticStrategy'.
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:934)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:931)
at com.mysql.jdbc.Util.loadExtensions(Util.java:588)
at 
com.mysql.jdbc.LoadBalancingConnectionProxy.(LoadBalancingConnectionProxy.java:279)
at 
com.mysql.jdbc.FailoverConnectionProxy.(FailoverConnectionProxy.java:66)
at 
com.mysql.jdbc.NonRegisteringDriver.connectFailover(NonRegisteringDriver.java:382)
at 
com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:301)
at java.sql.DriverManager.getConnection(DriverManager.java:571)
at java.sql.DriverManager.getConnection(DriverManager.java:215)
at 
org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:75)
at 
org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)
at 
org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1188)
at 
org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)
at 
com.cloud.utils.db.TransactionLegacy.getStandaloneConnectionWithException(TransactionLegacy.java:202)
at com.cloud.utils.db.Merovingian2.(Merovingian2.java:68)
at 
com.cloud.utils.db.Merovingian2.createLockMaster(Merovingian2.java:88)
at 
com.cloud.server.LockMasterListener.(LockMasterListener.java:33)
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 
org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:148)
at 
org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:121)
at 
org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:277)
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1077)
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:981)
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:487)
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458)
at 
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
at 
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223)
at 
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)
at 
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:191)
at 
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:636)
at 
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:934)
at 
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479)
at 
org.apache.cloudstack.spring.module.model.impl.D

[jira] [Updated] (CLOUDSTACK-9209) Database HA not working on a fresh install on Ubuntu 12.04

2016-01-05 Thread Thomas (JIRA)

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

Thomas updated CLOUDSTACK-9209:
---
Description: 
The cloudstack-management service will not come up because of this error:
2016-01-05 16:15:00,899 INFO  [c.c.u.d.T.Transaction] (main:null) (logid:) Is 
Data Base High Availiability enabled? Ans : true
2016-01-05 16:15:00,924 INFO  [c.c.u.d.T.Transaction] (main:null) (logid:) The 
slaves configured for Cloud Data base is/are : 192.168.0.90
2016-01-05 16:15:00,974 ERROR [c.c.u.d.Merovingian2] (main:null) (logid:) 
Unable to get a new db connection
java.sql.SQLException: Invalid load balancing strategy 
'com.cloud.utils.db.StaticStrategy'.
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:934)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:931)
at com.mysql.jdbc.Util.loadExtensions(Util.java:588)
at 
com.mysql.jdbc.LoadBalancingConnectionProxy.(LoadBalancingConnectionProxy.java:279)
at 
com.mysql.jdbc.FailoverConnectionProxy.(FailoverConnectionProxy.java:66)
at 
com.mysql.jdbc.NonRegisteringDriver.connectFailover(NonRegisteringDriver.java:382)
at 
com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:301)
at java.sql.DriverManager.getConnection(DriverManager.java:571)
at java.sql.DriverManager.getConnection(DriverManager.java:215)
at 
org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:75)
at 
org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)
at 
org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1188)
at 
org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)
at 
com.cloud.utils.db.TransactionLegacy.getStandaloneConnectionWithException(TransactionLegacy.java:202)
at com.cloud.utils.db.Merovingian2.(Merovingian2.java:68)
at 
com.cloud.utils.db.Merovingian2.createLockMaster(Merovingian2.java:88)
at 
com.cloud.server.LockMasterListener.(LockMasterListener.java:33)
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 
org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:148)
at 
org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:121)
at 
org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:277)
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1077)
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:981)
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:487)
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458)
at 
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
at 
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223)
at 
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)
at 
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:191)
at 
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:636)
at 
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:934)
at 
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479)
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 
org.apache.c

[jira] [Created] (CLOUDSTACK-9286) Delete Domain not working: Failed to clean up domain resources and sub domains, delete failed on domain

2016-02-15 Thread Thomas (JIRA)
Thomas created CLOUDSTACK-9286:
--

 Summary: Delete Domain not working: Failed to clean up domain 
resources and sub domains, delete failed on domain
 Key: CLOUDSTACK-9286
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9286
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Automation
Affects Versions: 4.7.0
 Environment: Two CentOS7 MGMT Servers
XenServer Hypervisors
Reporter: Thomas


If you disable an account of a domain and then try to delete that domain it 
fails with following error:
--
2016-02-15 16:22:04,921 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
(API-Job-Executor-25:ctx-da3cbbe6 job-1635) (logid:7354b28c) Executing 
AsyncJobVO {id:1635, userId: 18, accountId: 2, instanceType: None, instanceId: 
null, cmd: org.apache.cloudstack.api.command.admin.domain.DeleteDomainCmd, 
cmdInfo: 
{"cleanup":"true","response":"json","ctxUserId":"18","httpmethod":"GET","ctxStartEventId":"4107","id":"dd40f585-73d6-4710-a4b7-7dd74e910675","ctxDetails":"{\"interface
 
com.cloud.domain.Domain\":\"dd40f585-73d6-4710-a4b7-7dd74e910675\"}","ctxAccountId":"2","uuid":"dd40f585-73d6-4710-a4b7-7dd74e910675","cmdEventType":"DOMAIN.DELETE","_":"1455549724913"},
 cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
null, initMsid: 22095312942840, completeMsid: null, lastUpdated: null, 
lastPolled: null, created: null}
2016-02-15 16:22:04,921 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
(catalina-exec-11:ctx-5ea86460 ctx-69c37a64) (logid:ee5245e3) submit async 
job-1635, details: AsyncJobVO {id:1635, userId: 18, accountId: 2, instanceType: 
None, instanceId: null, cmd: 
org.apache.cloudstack.api.command.admin.domain.DeleteDomainCmd, cmdInfo: 
{"cleanup":"true","response":"json","ctxUserId":"18","httpmethod":"GET","ctxStartEventId":"4107","id":"dd40f585-73d6-4710-a4b7-7dd74e910675","ctxDetails":"{\"interface
 
com.cloud.domain.Domain\":\"dd40f585-73d6-4710-a4b7-7dd74e910675\"}","ctxAccountId":"2","uuid":"dd40f585-73d6-4710-a4b7-7dd74e910675","cmdEventType":"DOMAIN.DELETE","_":"1455549724913"},
 cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
null, initMsid: 22095312942840, completeMsid: null, lastUpdated: null, 
lastPolled: null, created: null}
2016-02-15 16:22:04,922 DEBUG [c.c.a.ApiServlet] (catalina-exec-11:ctx-5ea86460 
ctx-69c37a64) (logid:ee5245e3) ===END===  212.123.98.2 -- GET  
command=deleteDomain&id=dd40f585-73d6-4710-a4b7-7dd74e910675&cleanup=true&response=json&_=1455549724913
2016-02-15 16:22:04,937 DEBUG [c.c.u.AccountManagerImpl] 
(API-Job-Executor-25:ctx-da3cbbe6 job-1635 ctx-633df0cf) (logid:7354b28c) 
Access granted to Acct[c1022585-b874-11e5-b4fa-1418774e8f7a-admin] to 
Domain:97/x/xxx/ by AffinityGroupAccessChecker
2016-02-15 16:22:04,937 DEBUG [c.c.u.DomainManagerImpl] 
(API-Job-Executor-25:ctx-da3cbbe6 job-1635 ctx-633df0cf) (logid:7354b28c) 
Marking domain id=97 as Inactive before actually deleting it
2016-02-15 16:22:04,940 DEBUG [c.c.u.DomainManagerImpl] 
(API-Job-Executor-25:ctx-da3cbbe6 job-1635 ctx-633df0cf) (logid:7354b28c) 
Cleaning up domain id=97
2016-02-15 16:22:04,949 DEBUG [c.c.u.DomainManagerImpl] 
(API-Job-Executor-25:ctx-da3cbbe6 job-1635 ctx-633df0cf) (logid:7354b28c) 
Deleting networks for domain id=97
2016-02-15 16:22:04,952 DEBUG [c.c.u.DomainManagerImpl] 
(API-Job-Executor-25:ctx-da3cbbe6 job-1635 ctx-633df0cf) (logid:7354b28c) Can't 
delete the domain yet because it has 1accounts that need a cleanup
2016-02-15 16:22:04,952 ERROR [c.c.u.DomainManagerImpl] 
(API-Job-Executor-25:ctx-da3cbbe6 job-1635 ctx-633df0cf) (logid:7354b28c) 
Exception deleting domain with id 97
com.cloud.utils.exception.CloudRuntimeException: Failed to clean up domain 
resources and sub domains, delete failed on domain 500211 (id: 97).
at 
com.cloud.user.DomainManagerImpl.deleteDomain(DomainManagerImpl.java:268)
at 
com.cloud.user.DomainManagerImpl.deleteDomain(DomainManagerImpl.java:251)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at 
org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106)
at 
org.springframework.aop.framework.ReflectiveMethodI

[jira] [Commented] (CLOUDSTACK-9209) Database HA not working on a fresh install on Ubuntu 12.04

2016-02-18 Thread Thomas (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15153854#comment-15153854
 ] 

Thomas commented on CLOUDSTACK-9209:


Hi Simon,

sorry i don`t have this setup running anymore, i switches to Centos7 MGMT 
Server and Galera Cluster.
Maybe the packaging is broken for ubuntu and has missing dependencies?

> Database HA not working on a fresh install on Ubuntu 12.04
> --
>
> Key: CLOUDSTACK-9209
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9209
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Install and Setup
>Affects Versions: 4.7.0
> Environment: Two Ubuntu 12.04 Management Servers, Mysql Master Master 
> Replication, Official community repository: 
> http://cloudstack.apt-get.eu/ubuntu/dists/precise/4.7/
>Reporter: Thomas
>Priority: Blocker
>
> The cloudstack-management service will not come up because of this error:
> 2016-01-05 16:15:00,899 INFO  [c.c.u.d.T.Transaction] (main:null) (logid:) Is 
> Data Base High Availiability enabled? Ans : true
> 2016-01-05 16:15:00,924 INFO  [c.c.u.d.T.Transaction] (main:null) (logid:) 
> The slaves configured for Cloud Data base is/are : 192.168.0.90
> 2016-01-05 16:15:00,974 ERROR [c.c.u.d.Merovingian2] (main:null) (logid:) 
> Unable to get a new db connection
> java.sql.SQLException: Invalid load balancing strategy 
> 'com.cloud.utils.db.StaticStrategy'.
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:934)
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:931)
> at com.mysql.jdbc.Util.loadExtensions(Util.java:588)
> at 
> com.mysql.jdbc.LoadBalancingConnectionProxy.(LoadBalancingConnectionProxy.java:279)
> at 
> com.mysql.jdbc.FailoverConnectionProxy.(FailoverConnectionProxy.java:66)
> at 
> com.mysql.jdbc.NonRegisteringDriver.connectFailover(NonRegisteringDriver.java:382)
> at 
> com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:301)
> at java.sql.DriverManager.getConnection(DriverManager.java:571)
> at java.sql.DriverManager.getConnection(DriverManager.java:215)
> at 
> org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:75)
> at 
> org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)
> at 
> org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1188)
> at 
> org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)
> at 
> com.cloud.utils.db.TransactionLegacy.getStandaloneConnectionWithException(TransactionLegacy.java:202)
> at com.cloud.utils.db.Merovingian2.(Merovingian2.java:68)
> at 
> com.cloud.utils.db.Merovingian2.createLockMaster(Merovingian2.java:88)
> at 
> com.cloud.server.LockMasterListener.(LockMasterListener.java:33)
> 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 
> org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:148)
> at 
> org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:121)
> at 
> org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:277)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1077)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:981)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:487)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
> at 
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)
> at 
> or

[jira] [Comment Edited] (CLOUDSTACK-9209) Database HA not working on a fresh install on Ubuntu 12.04

2016-02-18 Thread Thomas (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15153854#comment-15153854
 ] 

Thomas edited comment on CLOUDSTACK-9209 at 2/19/16 7:34 AM:
-

Hi Simon,

sorry i don`t have this setup running anymore, i switched to Centos7 MGMT 
Server and Galera Cluster.
Maybe the packaging is broken for ubuntu and has missing dependencies?


was (Author: disappear):
Hi Simon,

sorry i don`t have this setup running anymore, i switches to Centos7 MGMT 
Server and Galera Cluster.
Maybe the packaging is broken for ubuntu and has missing dependencies?

> Database HA not working on a fresh install on Ubuntu 12.04
> --
>
> Key: CLOUDSTACK-9209
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9209
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Install and Setup
>Affects Versions: 4.7.0
> Environment: Two Ubuntu 12.04 Management Servers, Mysql Master Master 
> Replication, Official community repository: 
> http://cloudstack.apt-get.eu/ubuntu/dists/precise/4.7/
>Reporter: Thomas
>Priority: Blocker
>
> The cloudstack-management service will not come up because of this error:
> 2016-01-05 16:15:00,899 INFO  [c.c.u.d.T.Transaction] (main:null) (logid:) Is 
> Data Base High Availiability enabled? Ans : true
> 2016-01-05 16:15:00,924 INFO  [c.c.u.d.T.Transaction] (main:null) (logid:) 
> The slaves configured for Cloud Data base is/are : 192.168.0.90
> 2016-01-05 16:15:00,974 ERROR [c.c.u.d.Merovingian2] (main:null) (logid:) 
> Unable to get a new db connection
> java.sql.SQLException: Invalid load balancing strategy 
> 'com.cloud.utils.db.StaticStrategy'.
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:934)
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:931)
> at com.mysql.jdbc.Util.loadExtensions(Util.java:588)
> at 
> com.mysql.jdbc.LoadBalancingConnectionProxy.(LoadBalancingConnectionProxy.java:279)
> at 
> com.mysql.jdbc.FailoverConnectionProxy.(FailoverConnectionProxy.java:66)
> at 
> com.mysql.jdbc.NonRegisteringDriver.connectFailover(NonRegisteringDriver.java:382)
> at 
> com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:301)
> at java.sql.DriverManager.getConnection(DriverManager.java:571)
> at java.sql.DriverManager.getConnection(DriverManager.java:215)
> at 
> org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:75)
> at 
> org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)
> at 
> org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1188)
> at 
> org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)
> at 
> com.cloud.utils.db.TransactionLegacy.getStandaloneConnectionWithException(TransactionLegacy.java:202)
> at com.cloud.utils.db.Merovingian2.(Merovingian2.java:68)
> at 
> com.cloud.utils.db.Merovingian2.createLockMaster(Merovingian2.java:88)
> at 
> com.cloud.server.LockMasterListener.(LockMasterListener.java:33)
> 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 
> org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:148)
> at 
> org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:121)
> at 
> org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:277)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1077)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:981)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:487)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
> at 
>

[jira] [Commented] (CLOUDSTACK-9209) Database HA not working on a fresh install on Ubuntu 12.04

2016-02-21 Thread Thomas (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156554#comment-15156554
 ] 

Thomas commented on CLOUDSTACK-9209:


No, same error.
Because of this Galera Acitve Activa Cluster with keepalived is now running..

> Database HA not working on a fresh install on Ubuntu 12.04
> --
>
> Key: CLOUDSTACK-9209
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9209
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Install and Setup
>Affects Versions: 4.7.0
> Environment: Two Ubuntu 12.04 Management Servers, Mysql Master Master 
> Replication, Official community repository: 
> http://cloudstack.apt-get.eu/ubuntu/dists/precise/4.7/
>Reporter: Thomas
>Priority: Blocker
>
> The cloudstack-management service will not come up because of this error:
> 2016-01-05 16:15:00,899 INFO  [c.c.u.d.T.Transaction] (main:null) (logid:) Is 
> Data Base High Availiability enabled? Ans : true
> 2016-01-05 16:15:00,924 INFO  [c.c.u.d.T.Transaction] (main:null) (logid:) 
> The slaves configured for Cloud Data base is/are : 192.168.0.90
> 2016-01-05 16:15:00,974 ERROR [c.c.u.d.Merovingian2] (main:null) (logid:) 
> Unable to get a new db connection
> java.sql.SQLException: Invalid load balancing strategy 
> 'com.cloud.utils.db.StaticStrategy'.
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:934)
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:931)
> at com.mysql.jdbc.Util.loadExtensions(Util.java:588)
> at 
> com.mysql.jdbc.LoadBalancingConnectionProxy.(LoadBalancingConnectionProxy.java:279)
> at 
> com.mysql.jdbc.FailoverConnectionProxy.(FailoverConnectionProxy.java:66)
> at 
> com.mysql.jdbc.NonRegisteringDriver.connectFailover(NonRegisteringDriver.java:382)
> at 
> com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:301)
> at java.sql.DriverManager.getConnection(DriverManager.java:571)
> at java.sql.DriverManager.getConnection(DriverManager.java:215)
> at 
> org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:75)
> at 
> org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)
> at 
> org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1188)
> at 
> org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)
> at 
> com.cloud.utils.db.TransactionLegacy.getStandaloneConnectionWithException(TransactionLegacy.java:202)
> at com.cloud.utils.db.Merovingian2.(Merovingian2.java:68)
> at 
> com.cloud.utils.db.Merovingian2.createLockMaster(Merovingian2.java:88)
> at 
> com.cloud.server.LockMasterListener.(LockMasterListener.java:33)
> 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 
> org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:148)
> at 
> org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:121)
> at 
> org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:277)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1077)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:981)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:487)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
> at 
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.ja

[jira] [Comment Edited] (CLOUDSTACK-9209) Database HA not working on a fresh install on Ubuntu 12.04

2016-02-21 Thread Thomas (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156554#comment-15156554
 ] 

Thomas edited comment on CLOUDSTACK-9209 at 2/22/16 6:48 AM:
-

No, same error.
Because of this Galera Acitve Active Cluster with keepalived is now running..


was (Author: disappear):
No, same error.
Because of this Galera Acitve Activa Cluster with keepalived is now running..

> Database HA not working on a fresh install on Ubuntu 12.04
> --
>
> Key: CLOUDSTACK-9209
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9209
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Install and Setup
>Affects Versions: 4.7.0
> Environment: Two Ubuntu 12.04 Management Servers, Mysql Master Master 
> Replication, Official community repository: 
> http://cloudstack.apt-get.eu/ubuntu/dists/precise/4.7/
>Reporter: Thomas
>Priority: Blocker
>
> The cloudstack-management service will not come up because of this error:
> 2016-01-05 16:15:00,899 INFO  [c.c.u.d.T.Transaction] (main:null) (logid:) Is 
> Data Base High Availiability enabled? Ans : true
> 2016-01-05 16:15:00,924 INFO  [c.c.u.d.T.Transaction] (main:null) (logid:) 
> The slaves configured for Cloud Data base is/are : 192.168.0.90
> 2016-01-05 16:15:00,974 ERROR [c.c.u.d.Merovingian2] (main:null) (logid:) 
> Unable to get a new db connection
> java.sql.SQLException: Invalid load balancing strategy 
> 'com.cloud.utils.db.StaticStrategy'.
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:934)
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:931)
> at com.mysql.jdbc.Util.loadExtensions(Util.java:588)
> at 
> com.mysql.jdbc.LoadBalancingConnectionProxy.(LoadBalancingConnectionProxy.java:279)
> at 
> com.mysql.jdbc.FailoverConnectionProxy.(FailoverConnectionProxy.java:66)
> at 
> com.mysql.jdbc.NonRegisteringDriver.connectFailover(NonRegisteringDriver.java:382)
> at 
> com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:301)
> at java.sql.DriverManager.getConnection(DriverManager.java:571)
> at java.sql.DriverManager.getConnection(DriverManager.java:215)
> at 
> org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:75)
> at 
> org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)
> at 
> org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1188)
> at 
> org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)
> at 
> com.cloud.utils.db.TransactionLegacy.getStandaloneConnectionWithException(TransactionLegacy.java:202)
> at com.cloud.utils.db.Merovingian2.(Merovingian2.java:68)
> at 
> com.cloud.utils.db.Merovingian2.createLockMaster(Merovingian2.java:88)
> at 
> com.cloud.server.LockMasterListener.(LockMasterListener.java:33)
> 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 
> org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:148)
> at 
> org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:121)
> at 
> org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:277)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1077)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:981)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:487)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
> at 
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223)
> at 
> org.springframework.beans.factory.suppor

[jira] [Created] (CLOUDSTACK-9311) User cant resize VM root disk for XenServer

2016-03-18 Thread Thomas (JIRA)
Thomas created CLOUDSTACK-9311:
--

 Summary: User cant resize VM root disk for XenServer
 Key: CLOUDSTACK-9311
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9311
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: XenServer
Affects Versions: 4.8.0
 Environment: Redundant MGMT-Servers, Xenserver Cluster
Reporter: Thomas


A user can`t resize the root disk of a vm via gui.

We found a temporarily bugfix:
/usr/share/cloudstack-management/webapps/client/scripts/storage.js
From:
if (jsonObj.hypervisor == "KVM" || jsonObj.hypervisor == "XenServer" || 
jsonObj.hypervisor == "VMware") {
if (jsonObj.state == "Ready" || jsonObj.state == "Allocated") {
allowedActions.push("resize");
}
}
To:
//if (jsonObj.hypervisor == "KVM" || jsonObj.hypervisor == "XenServer" 
|| jsonObj.hypervisor == "VMware") {
if (jsonObj.state == "Ready" || jsonObj.state == "Allocated") {
allowedActions.push("resize");
}
//}

Attention, there is also a .gz version of that file, you need to move it away 
or recreate it with the adjustments.

So we think there must be a problem with the:
jsonObj.hypervisor var => not filled or wrong filled or so..



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


[jira] [Commented] (CLOUDSTACK-9311) User cant resize VM root disk for XenServer

2016-03-21 Thread Thomas (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15203830#comment-15203830
 ] 

Thomas commented on CLOUDSTACK-9311:


Hi Wei,

as user there is no information available about hypervisor, only as admin user.

The volume state is: Ready

> User cant resize VM root disk for XenServer
> ---
>
> Key: CLOUDSTACK-9311
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9311
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: XenServer
>Affects Versions: 4.8.0
> Environment: Redundant MGMT-Servers, Xenserver Cluster
>Reporter: Thomas
>
> A user can`t resize the root disk of a vm via gui.
> We found a temporarily bugfix:
> /usr/share/cloudstack-management/webapps/client/scripts/storage.js
> From:
> if (jsonObj.hypervisor == "KVM" || jsonObj.hypervisor == "XenServer" 
> || jsonObj.hypervisor == "VMware") {
> if (jsonObj.state == "Ready" || jsonObj.state == "Allocated") {
> allowedActions.push("resize");
> }
> }
> To:
> //if (jsonObj.hypervisor == "KVM" || jsonObj.hypervisor == 
> "XenServer" || jsonObj.hypervisor == "VMware") {
> if (jsonObj.state == "Ready" || jsonObj.state == "Allocated") {
> allowedActions.push("resize");
> }
> //}
> Attention, there is also a .gz version of that file, you need to move it away 
> or recreate it with the adjustments.
> So we think there must be a problem with the:
> jsonObj.hypervisor var => not filled or wrong filled or so..



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


[jira] [Created] (CLOUDSTACK-9356) VPC add VPN User fails same error as CLOUDSTACK-8927

2016-04-20 Thread Thomas (JIRA)
Thomas created CLOUDSTACK-9356:
--

 Summary: VPC add VPN User fails same error as CLOUDSTACK-8927
 Key: CLOUDSTACK-9356
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9356
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server, VPC, XenServer
Affects Versions: 4.8.0
 Environment: Two CentOS7 MGMT Servers, Two XenServerClusters, Advanced 
Networking, VLAN isolated
Reporter: Thomas
Priority: Critical


When we try to add an VPN User on a VPC following error occurs:
Management Server:
---
Apr 20 09:24:43 WARN  [resource.virtualnetwork.VirtualRoutingResource] 
(DirectAgent-68:ctx-de5cbf45) (logid:180e35ed) Expected 1 answers while 
executing VpnUsersCfgCommand but received 2
Apr 20 09:24:43 admin02 server: WARN  [c.c.a.r.v.VirtualRoutingResource] 
(DirectAgent-68:ctx-de5cbf45) (logid:180e35ed) Expected 1 answers while 
executing VpnUsersCfgCommand but received 2
Apr 20 09:24:47 WARN  [resource.virtualnetwork.VirtualRoutingResource] 
(DirectAgent-268:ctx-873174f6) (logid:180e35ed) Expected 1 answers while 
executing VpnUsersCfgCommand but received 2
Apr 20 09:24:47 admin02 server: WARN  [c.c.a.r.v.VirtualRoutingResource] 
(DirectAgent-268:ctx-873174f6) (logid:180e35ed) Expected 1 answers while 
executing VpnUsersCfgCommand but received 2
Apr 20 09:24:47 WARN  [network.vpn.RemoteAccessVpnManagerImpl] 
(API-Job-Executor-58:ctx-7f86f610 job-1169 ctx-1073feac) (logid:180e35ed) 
Unable to apply vpn users
Apr 20 09:24:47 localhost java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
Apr 20 09:24:47 localhost at 
java.util.ArrayList.rangeCheck(ArrayList.java:653)
Apr 20 09:24:47 localhost at java.util.ArrayList.get(ArrayList.java:429)
Apr 20 09:24:47 localhost at 
com.cloud.network.vpn.RemoteAccessVpnManagerImpl.applyVpnUsers(RemoteAccessVpnManagerImpl.java:532)
Apr 20 09:24:47 localhost at 
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Apr 20 09:24:47 localhost at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
Apr 20 09:24:47 localhost at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
Apr 20 09:24:47 localhost at 
java.lang.reflect.Method.invoke(Method.java:498)
Apr 20 09:24:47 localhost at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
Apr 20 09:24:47 localhost at 
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
Apr 20 09:24:47 localhost at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
Apr 20 09:24:47 localhost at 
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
Apr 20 09:24:47 localhost at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
Apr 20 09:24:47 localhost at 
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
Apr 20 09:24:47 localhost at com.sun.proxy.$Proxy234.applyVpnUsers(Unknown 
Source)
Apr 20 09:24:47 localhost at 
org.apache.cloudstack.api.command.user.vpn.AddVpnUserCmd.execute(AddVpnUserCmd.java:122)
Apr 20 09:24:47 localhost at 
com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:150)
Apr 20 09:24:47 localhost at 
com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
Apr 20 09:24:47 localhost at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:554)
Apr 20 09:24:47 localhost at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
Apr 20 09:24:47 localhost at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
Apr 20 09:24:47 localhost at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
Apr 20 09:24:47 localhost at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
Apr 20 09:24:47 localhost at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
Apr 20 09:24:47 localhost at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:502)
Apr 20 09:24:47 localhost at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
Apr 20 09:24:47 localhost at 
java.util.concurrent.FutureTask.run(FutureTask.java:266)
Apr 20 09:24:47 localhost at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
Apr 20 09:24:47 localhost at 
java.

[jira] [Created] (CLOUDSTACK-9360) Set guest passwor not working with redundant routers

2016-04-21 Thread Thomas (JIRA)
Thomas created CLOUDSTACK-9360:
--

 Summary: Set guest passwor not working with redundant routers
 Key: CLOUDSTACK-9360
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9360
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server, VPC
Affects Versions: 4.8.0
 Environment: Two CentOS7 MGMT Servers, redundant router vms
Reporter: Thomas
Priority: Critical


We got a problem with the set guest password function. 
When you spawn a redundant router (VPC or not) the VMs don`t set their password 
correctly.

We broke it down to the /opt/cloud/bin/passwd_server_ip.py script which checks 
the Client IP for the save password function on the routerVM:
---
if clientAddress not in ['localhost', '127.0.0.1', listeningAddress]:
syslog.syslog('serve_password: non-localhost IP trying to save password: 
%s' % clientAddress)
self.send_response(403)
return
---

In the logs we see:
--
Apr 21 09:02:01 r-80-VM passwd_server_ip.py: serve_password: non-localhost IP 
trying to save password: 10.0.0.236
--

The routerVMs eth2 config:
--
4: eth2:  mtu 1500 qdisc pfifo_fast state UP 
qlen 1000
link/ether 02:00:2c:d7:00:08 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.236/24 brd 10.0.0.255 scope global eth2
inet 10.0.0.1/24 brd 10.0.0.255 scope global secondary eth2
--

So what happens:
The management server triggers the router vm to store a new password for a new 
spawned or password reseting guest vm.
The router vm then tries locally to connect to the password python server with 
it`s primary eth2 ip, in our example: 10.0.0.236
The python password server then checks the client IP via:
if clientAddress not in ['localhost', '127.0.0.1', listeningAddress]:
and exists with: serve_password: non-localhost IP trying to save password: 
10.0.0.236
cause the listeningAddress is filled with: 10.0.0.1

How to fix
First possibility:
Configure the 10.0.0.1 IP as primary IP => maybe not possible cause its managed 
by keepalived

Second possibilty:
Adjust the password server if check and check also for the ip 10.0.0.236.
I tried to implement this with a subprocess and grep in 
/var/cache/cloud/processed/guest_network.json.* or with a os command and ip a | 
grep eth2 | grep -v mtu | cut -d ' ' -f 6 | cut -d '/' -f 1

Maybe someone could support here?



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


[jira] [Updated] (CLOUDSTACK-9360) Set guest password not working with redundant routers

2016-04-21 Thread Thomas (JIRA)

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

Thomas updated CLOUDSTACK-9360:
---
Summary: Set guest password not working with redundant routers  (was: Set 
guest passwor not working with redundant routers)

> Set guest password not working with redundant routers
> -
>
> Key: CLOUDSTACK-9360
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9360
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VPC
>Affects Versions: 4.8.0
> Environment: Two CentOS7 MGMT Servers, redundant router vms
>Reporter: Thomas
>Priority: Critical
>
> We got a problem with the set guest password function. 
> When you spawn a redundant router (VPC or not) the VMs don`t set their 
> password correctly.
> We broke it down to the /opt/cloud/bin/passwd_server_ip.py script which 
> checks the Client IP for the save password function on the routerVM:
> ---
> if clientAddress not in ['localhost', '127.0.0.1', listeningAddress]:
> syslog.syslog('serve_password: non-localhost IP trying to save password: 
> %s' % clientAddress)
> self.send_response(403)
> return
> ---
> In the logs we see:
> --
> Apr 21 09:02:01 r-80-VM passwd_server_ip.py: serve_password: non-localhost IP 
> trying to save password: 10.0.0.236
> --
> The routerVMs eth2 config:
> --
> 4: eth2:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 02:00:2c:d7:00:08 brd ff:ff:ff:ff:ff:ff
> inet 10.0.0.236/24 brd 10.0.0.255 scope global eth2
> inet 10.0.0.1/24 brd 10.0.0.255 scope global secondary eth2
> --
> So what happens:
> The management server triggers the router vm to store a new password for a 
> new spawned or password reseting guest vm.
> The router vm then tries locally to connect to the password python server 
> with it`s primary eth2 ip, in our example: 10.0.0.236
> The python password server then checks the client IP via:
> if clientAddress not in ['localhost', '127.0.0.1', listeningAddress]:
> and exists with: serve_password: non-localhost IP trying to save password: 
> 10.0.0.236
> cause the listeningAddress is filled with: 10.0.0.1
> How to fix
> First possibility:
> Configure the 10.0.0.1 IP as primary IP => maybe not possible cause its 
> managed by keepalived
> Second possibilty:
> Adjust the password server if check and check also for the ip 10.0.0.236.
> I tried to implement this with a subprocess and grep in 
> /var/cache/cloud/processed/guest_network.json.* or with a os command and ip a 
> | grep eth2 | grep -v mtu | cut -d ' ' -f 6 | cut -d '/' -f 1
> Maybe someone could support here?



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


[jira] [Commented] (CLOUDSTACK-9356) VPC add VPN User fails same error as CLOUDSTACK-8927

2016-04-21 Thread Thomas (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15251967#comment-15251967
 ] 

Thomas commented on CLOUDSTACK-9356:


This seems to come from:
 
cloudstack/core/src/com/cloud/agent/resource/virtualnetwork/VirtualRoutingResource.java

 // Not sure why this matters, but log it anyway
if (cmd.getAnswersCount() != results.size()) {
s_logger.warn("Expected " + cmd.getAnswersCount() + " answers while 
executing " + cmd.getClass().getSimpleName() + " but received " + 
results.size());
}

Maybe we can remove this check?

> VPC add VPN User fails same error as CLOUDSTACK-8927
> 
>
> Key: CLOUDSTACK-9356
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9356
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VPC, XenServer
>Affects Versions: 4.8.0
> Environment: Two CentOS7 MGMT Servers, Two XenServerClusters, 
> Advanced Networking, VLAN isolated
>Reporter: Thomas
>Priority: Critical
>
> When we try to add an VPN User on a VPC following error occurs:
> Management Server:
> ---
> Apr 20 09:24:43 WARN  [resource.virtualnetwork.VirtualRoutingResource] 
> (DirectAgent-68:ctx-de5cbf45) (logid:180e35ed) Expected 1 answers while 
> executing VpnUsersCfgCommand but received 2
> Apr 20 09:24:43 admin02 server: WARN  [c.c.a.r.v.VirtualRoutingResource] 
> (DirectAgent-68:ctx-de5cbf45) (logid:180e35ed) Expected 1 answers while 
> executing VpnUsersCfgCommand but received 2
> Apr 20 09:24:47 WARN  [resource.virtualnetwork.VirtualRoutingResource] 
> (DirectAgent-268:ctx-873174f6) (logid:180e35ed) Expected 1 answers while 
> executing VpnUsersCfgCommand but received 2
> Apr 20 09:24:47 admin02 server: WARN  [c.c.a.r.v.VirtualRoutingResource] 
> (DirectAgent-268:ctx-873174f6) (logid:180e35ed) Expected 1 answers while 
> executing VpnUsersCfgCommand but received 2
> Apr 20 09:24:47 WARN  [network.vpn.RemoteAccessVpnManagerImpl] 
> (API-Job-Executor-58:ctx-7f86f610 job-1169 ctx-1073feac) (logid:180e35ed) 
> Unable to apply vpn users
> Apr 20 09:24:47 localhost java.lang.IndexOutOfBoundsException: Index: 1, 
> Size: 1
> Apr 20 09:24:47 localhost at 
> java.util.ArrayList.rangeCheck(ArrayList.java:653)
> Apr 20 09:24:47 localhost at java.util.ArrayList.get(ArrayList.java:429)
> Apr 20 09:24:47 localhost at 
> com.cloud.network.vpn.RemoteAccessVpnManagerImpl.applyVpnUsers(RemoteAccessVpnManagerImpl.java:532)
> Apr 20 09:24:47 localhost at 
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> Apr 20 09:24:47 localhost at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> Apr 20 09:24:47 localhost at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Apr 20 09:24:47 localhost at 
> java.lang.reflect.Method.invoke(Method.java:498)
> Apr 20 09:24:47 localhost at 
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> Apr 20 09:24:47 localhost at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> Apr 20 09:24:47 localhost at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> Apr 20 09:24:47 localhost at 
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> Apr 20 09:24:47 localhost at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> Apr 20 09:24:47 localhost at 
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> Apr 20 09:24:47 localhost at 
> com.sun.proxy.$Proxy234.applyVpnUsers(Unknown Source)
> Apr 20 09:24:47 localhost at 
> org.apache.cloudstack.api.command.user.vpn.AddVpnUserCmd.execute(AddVpnUserCmd.java:122)
> Apr 20 09:24:47 localhost at 
> com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:150)
> Apr 20 09:24:47 localhost at 
> com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
> Apr 20 09:24:47 localhost at 
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:554)
> Apr 20 09:24:47 localhost at 
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> Apr 20 09:24:47 localhost at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> Apr 20 09:24:47 localhost at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithCon

[jira] [Comment Edited] (CLOUDSTACK-9360) Set guest password not working with redundant routers

2016-04-22 Thread Thomas (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15253627#comment-15253627
 ] 

Thomas edited comment on CLOUDSTACK-9360 at 4/22/16 9:40 AM:
-

Sorry but this is not the fix.
It starts two password servers, one on the secondary and one on the main IP of 
eth2:
root  4681  0.0  0.5  17668  1468 ?S09:25   0:00 /bin/bash 
/opt/cloud/bin/passwd_server_ip 10.0.0.1 dummy
root  4683  0.0  3.3  47944  8332 ?S09:25   0:00  \_ python 
/opt/cloud/bin/passwd_server_ip.py 10.0.0.1
root  4692  0.0  0.5  17668  1468 ?S09:25   0:00 /bin/bash 
/opt/cloud/bin/passwd_server_ip 10.0.0.129 dummy
root  4695  0.0  3.3  47944  8332 ?S09:25   0:00  \_ python 
/opt/cloud/bin/passwd_server_ip.py 10.0.0.129

When you try to  reset the password via GUI the local password file doesn`t get 
updated and no passwd_server is logging anything to /var/log/messages

It seems to run in a timeout when it executes:
--
curl --header "DomU_Request: save_password" "http://10.0.0.1:8080/"; -F 
"ip=10.0.0.104" -F "password=NEWPW" -F "token=x"

curl: (7) couldn't connect to host
---


was (Author: disappear):
Sorry but this is not the fix.
It starts two password servers, one on the secondary and one on the main IP of 
eth2:
root  4681  0.0  0.5  17668  1468 ?S09:25   0:00 /bin/bash 
/opt/cloud/bin/passwd_server_ip 10.0.0.1 dummy
root  4683  0.0  3.3  47944  8332 ?S09:25   0:00  \_ python 
/opt/cloud/bin/passwd_server_ip.py 10.0.0.1
root  4692  0.0  0.5  17668  1468 ?S09:25   0:00 /bin/bash 
/opt/cloud/bin/passwd_server_ip 10.0.0.129 dummy
root  4695  0.0  3.3  47944  8332 ?S09:25   0:00  \_ python 
/opt/cloud/bin/passwd_server_ip.py 10.0.0.129

When you try to change reset password vie GUI the local password file doesn`t 
get updated and no passwd_server is logging anything to /var/log/messages

It seems to run in a timeout when it executes:
--
curl --header "DomU_Request: save_password" "http://10.0.0.1:8080/"; -F 
"ip=10.0.0.104" -F "password=NEWPW" -F "token=x"

curl: (7) couldn't connect to host
---

> Set guest password not working with redundant routers
> -
>
> Key: CLOUDSTACK-9360
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9360
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VPC
>Affects Versions: 4.8.0
> Environment: Two CentOS7 MGMT Servers, redundant router vms
>Reporter: Thomas
>Priority: Critical
>
> We got a problem with the set guest password function. 
> When you spawn a redundant router (VPC or not) the VMs don`t set their 
> password correctly.
> We broke it down to the /opt/cloud/bin/passwd_server_ip.py script which 
> checks the Client IP for the save password function on the routerVM:
> ---
> if clientAddress not in ['localhost', '127.0.0.1', listeningAddress]:
> syslog.syslog('serve_password: non-localhost IP trying to save password: 
> %s' % clientAddress)
> self.send_response(403)
> return
> ---
> In the logs we see:
> --
> Apr 21 09:02:01 r-80-VM passwd_server_ip.py: serve_password: non-localhost IP 
> trying to save password: 10.0.0.236
> --
> The routerVMs eth2 config:
> --
> 4: eth2:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 02:00:2c:d7:00:08 brd ff:ff:ff:ff:ff:ff
> inet 10.0.0.236/24 brd 10.0.0.255 scope global eth2
> inet 10.0.0.1/24 brd 10.0.0.255 scope global secondary eth2
> --
> So what happens:
> The management server triggers the router vm to store a new password for a 
> new spawned or password reseting guest vm.
> The router vm then tries locally to connect to the password python server 
> with it`s primary eth2 ip, in our example: 10.0.0.236
> The python password server then checks the client IP via:
> if clientAddress not in ['localhost', '127.0.0.1', listeningAddress]:
> and exists with: serve_password: non-localhost IP trying to save password: 
> 10.0.0.236
> cause the listeningAddress is filled with: 10.0.0.1
> How to fix
> First possibility:
> Configure the 10.0.0.1 IP as primary IP => maybe not possible cause its 
> managed by keepalived
> Second possibilty:
> Adjust the password server if check and check also for the ip 10.0.0.236.
> I tried to implement this with a subprocess and grep in 
> /var/cache/cloud/processed/guest_network.json.* or with a os command and ip a 
> | grep eth2 | grep -v mtu | cut -d ' ' -f 6 | cut -d '/' -f 1
> Maybe someone could support here?



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


[jira] [Commented] (CLOUDSTACK-9360) Set guest password not working with redundant routers

2016-04-22 Thread Thomas (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15253627#comment-15253627
 ] 

Thomas commented on CLOUDSTACK-9360:


Sorry but this is not the fix.
It starts two password servers, one on the secondary and one on the main IP of 
eth2:
root  4681  0.0  0.5  17668  1468 ?S09:25   0:00 /bin/bash 
/opt/cloud/bin/passwd_server_ip 10.0.0.1 dummy
root  4683  0.0  3.3  47944  8332 ?S09:25   0:00  \_ python 
/opt/cloud/bin/passwd_server_ip.py 10.0.0.1
root  4692  0.0  0.5  17668  1468 ?S09:25   0:00 /bin/bash 
/opt/cloud/bin/passwd_server_ip 10.0.0.129 dummy
root  4695  0.0  3.3  47944  8332 ?S09:25   0:00  \_ python 
/opt/cloud/bin/passwd_server_ip.py 10.0.0.129

When you try to change reset password vie GUI the local password file doesn`t 
get updated and no passwd_server is logging anything to /var/log/messages

It seems to run in a timeout when it executes:
--
curl --header "DomU_Request: save_password" "http://10.0.0.1:8080/"; -F 
"ip=10.0.0.104" -F "password=NEWPW" -F "token=x"

curl: (7) couldn't connect to host
---

> Set guest password not working with redundant routers
> -
>
> Key: CLOUDSTACK-9360
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9360
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VPC
>Affects Versions: 4.8.0
> Environment: Two CentOS7 MGMT Servers, redundant router vms
>Reporter: Thomas
>Priority: Critical
>
> We got a problem with the set guest password function. 
> When you spawn a redundant router (VPC or not) the VMs don`t set their 
> password correctly.
> We broke it down to the /opt/cloud/bin/passwd_server_ip.py script which 
> checks the Client IP for the save password function on the routerVM:
> ---
> if clientAddress not in ['localhost', '127.0.0.1', listeningAddress]:
> syslog.syslog('serve_password: non-localhost IP trying to save password: 
> %s' % clientAddress)
> self.send_response(403)
> return
> ---
> In the logs we see:
> --
> Apr 21 09:02:01 r-80-VM passwd_server_ip.py: serve_password: non-localhost IP 
> trying to save password: 10.0.0.236
> --
> The routerVMs eth2 config:
> --
> 4: eth2:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 02:00:2c:d7:00:08 brd ff:ff:ff:ff:ff:ff
> inet 10.0.0.236/24 brd 10.0.0.255 scope global eth2
> inet 10.0.0.1/24 brd 10.0.0.255 scope global secondary eth2
> --
> So what happens:
> The management server triggers the router vm to store a new password for a 
> new spawned or password reseting guest vm.
> The router vm then tries locally to connect to the password python server 
> with it`s primary eth2 ip, in our example: 10.0.0.236
> The python password server then checks the client IP via:
> if clientAddress not in ['localhost', '127.0.0.1', listeningAddress]:
> and exists with: serve_password: non-localhost IP trying to save password: 
> 10.0.0.236
> cause the listeningAddress is filled with: 10.0.0.1
> How to fix
> First possibility:
> Configure the 10.0.0.1 IP as primary IP => maybe not possible cause its 
> managed by keepalived
> Second possibilty:
> Adjust the password server if check and check also for the ip 10.0.0.236.
> I tried to implement this with a subprocess and grep in 
> /var/cache/cloud/processed/guest_network.json.* or with a os command and ip a 
> | grep eth2 | grep -v mtu | cut -d ' ' -f 6 | cut -d '/' -f 1
> Maybe someone could support here?



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


[jira] [Commented] (CLOUDSTACK-9360) Set guest password not working with redundant routers

2016-04-22 Thread Thomas (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15253682#comment-15253682
 ] 

Thomas commented on CLOUDSTACK-9360:


Hi Wei,

but there is also a logical mistake.
Lets assume that the client tries to get its password from the 
dhcp-server-identifier which is the main IP from the VR for example:
10.0.0.153

The virtual router saved the password via: curl --header "DomU_Request: 
save_password" "http://10.0.0.1:8080/"; -F "ip=10.0.0.104" -F "password=NEWPW" 
-F "token=xxx"

So the password server with the 10.0.0.1 was used. 
The password server with the 10.0.0.153 looks in its password file: 
/var/cache/cloud/passwords-10.0.0.153 and there is no new password for the 
client, cause its in the  /var/cache/cloud/passwords-10.0.0.1 file.

This could happen, so for me the better fix would be to remove the IP-Check for 
the DomU_Request: save_password request, cause the token also will be checked, 
so it`s not a security risk. The clients need to update their 
guest-set-password boot scripts and use the routers identifier in their DHCP 
lease file for the password server connect.

What do you think?

> Set guest password not working with redundant routers
> -
>
> Key: CLOUDSTACK-9360
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9360
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VPC
>Affects Versions: 4.8.0
> Environment: Two CentOS7 MGMT Servers, redundant router vms
>Reporter: Thomas
>Priority: Critical
>
> We got a problem with the set guest password function. 
> When you spawn a redundant router (VPC or not) the VMs don`t set their 
> password correctly.
> We broke it down to the /opt/cloud/bin/passwd_server_ip.py script which 
> checks the Client IP for the save password function on the routerVM:
> ---
> if clientAddress not in ['localhost', '127.0.0.1', listeningAddress]:
> syslog.syslog('serve_password: non-localhost IP trying to save password: 
> %s' % clientAddress)
> self.send_response(403)
> return
> ---
> In the logs we see:
> --
> Apr 21 09:02:01 r-80-VM passwd_server_ip.py: serve_password: non-localhost IP 
> trying to save password: 10.0.0.236
> --
> The routerVMs eth2 config:
> --
> 4: eth2:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 02:00:2c:d7:00:08 brd ff:ff:ff:ff:ff:ff
> inet 10.0.0.236/24 brd 10.0.0.255 scope global eth2
> inet 10.0.0.1/24 brd 10.0.0.255 scope global secondary eth2
> --
> So what happens:
> The management server triggers the router vm to store a new password for a 
> new spawned or password reseting guest vm.
> The router vm then tries locally to connect to the password python server 
> with it`s primary eth2 ip, in our example: 10.0.0.236
> The python password server then checks the client IP via:
> if clientAddress not in ['localhost', '127.0.0.1', listeningAddress]:
> and exists with: serve_password: non-localhost IP trying to save password: 
> 10.0.0.236
> cause the listeningAddress is filled with: 10.0.0.1
> How to fix
> First possibility:
> Configure the 10.0.0.1 IP as primary IP => maybe not possible cause its 
> managed by keepalived
> Second possibilty:
> Adjust the password server if check and check also for the ip 10.0.0.236.
> I tried to implement this with a subprocess and grep in 
> /var/cache/cloud/processed/guest_network.json.* or with a os command and ip a 
> | grep eth2 | grep -v mtu | cut -d ' ' -f 6 | cut -d '/' -f 1
> Maybe someone could support here?



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


[jira] [Comment Edited] (CLOUDSTACK-9360) Set guest password not working with redundant routers

2016-04-22 Thread Thomas (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15253682#comment-15253682
 ] 

Thomas edited comment on CLOUDSTACK-9360 at 4/22/16 10:10 AM:
--

Hi Wei,

but there is also a logical mistake.
Lets assume that the client tries to get its password from the 
dhcp-server-identifier which is the main IP from the VR for example:
10.0.0.153

The virtual router saved the password via: curl --header "DomU_Request: 
save_password" "http://10.0.0.1:8080/"; -F "ip=10.0.0.104" -F "password=NEWPW" 
-F "token=xxx"

So the password server with the 10.0.0.1 param was used. 
The password server with the 10.0.0.153 param looks in its password file: 
/var/cache/cloud/passwords-10.0.0.153 and there is no new password for the 
client, cause its in the  /var/cache/cloud/passwords-10.0.0.1 file.

This could happen, so for me the better fix would be to remove the IP-Check for 
the DomU_Request: save_password request, cause the token also will be checked, 
so it`s not a security risk. The clients need to update their 
guest-set-password boot scripts and use the routers identifier in their DHCP 
lease file for the password server connect.

What do you think?


was (Author: disappear):
Hi Wei,

but there is also a logical mistake.
Lets assume that the client tries to get its password from the 
dhcp-server-identifier which is the main IP from the VR for example:
10.0.0.153

The virtual router saved the password via: curl --header "DomU_Request: 
save_password" "http://10.0.0.1:8080/"; -F "ip=10.0.0.104" -F "password=NEWPW" 
-F "token=xxx"

So the password server with the 10.0.0.1 param was used. 
The password server with the 10.0.0.153 looks in its password file: 
/var/cache/cloud/passwords-10.0.0.153 and there is no new password for the 
client, cause its in the  /var/cache/cloud/passwords-10.0.0.1 file.

This could happen, so for me the better fix would be to remove the IP-Check for 
the DomU_Request: save_password request, cause the token also will be checked, 
so it`s not a security risk. The clients need to update their 
guest-set-password boot scripts and use the routers identifier in their DHCP 
lease file for the password server connect.

What do you think?

> Set guest password not working with redundant routers
> -
>
> Key: CLOUDSTACK-9360
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9360
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VPC
>Affects Versions: 4.8.0
> Environment: Two CentOS7 MGMT Servers, redundant router vms
>Reporter: Thomas
>Priority: Critical
>
> We got a problem with the set guest password function. 
> When you spawn a redundant router (VPC or not) the VMs don`t set their 
> password correctly.
> We broke it down to the /opt/cloud/bin/passwd_server_ip.py script which 
> checks the Client IP for the save password function on the routerVM:
> ---
> if clientAddress not in ['localhost', '127.0.0.1', listeningAddress]:
> syslog.syslog('serve_password: non-localhost IP trying to save password: 
> %s' % clientAddress)
> self.send_response(403)
> return
> ---
> In the logs we see:
> --
> Apr 21 09:02:01 r-80-VM passwd_server_ip.py: serve_password: non-localhost IP 
> trying to save password: 10.0.0.236
> --
> The routerVMs eth2 config:
> --
> 4: eth2:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 02:00:2c:d7:00:08 brd ff:ff:ff:ff:ff:ff
> inet 10.0.0.236/24 brd 10.0.0.255 scope global eth2
> inet 10.0.0.1/24 brd 10.0.0.255 scope global secondary eth2
> --
> So what happens:
> The management server triggers the router vm to store a new password for a 
> new spawned or password reseting guest vm.
> The router vm then tries locally to connect to the password python server 
> with it`s primary eth2 ip, in our example: 10.0.0.236
> The python password server then checks the client IP via:
> if clientAddress not in ['localhost', '127.0.0.1', listeningAddress]:
> and exists with: serve_password: non-localhost IP trying to save password: 
> 10.0.0.236
> cause the listeningAddress is filled with: 10.0.0.1
> How to fix
> First possibility:
> Configure the 10.0.0.1 IP as primary IP => maybe not possible cause its 
> managed by keepalived
> Second possibilty:
> Adjust the password server if check and check also for the ip 10.0.0.236.
> I tried to implement this with a subprocess and grep in 
> /var/cache/cloud/processed/guest_network.json.* or with a os command and ip a 
> | grep eth2 | grep -v mtu | cut -d ' ' -f 6 | cut -d '/' -f 1
> Maybe someone could support here?



--
This message was sent by Atlassian JIRA
(

[jira] [Comment Edited] (CLOUDSTACK-9360) Set guest password not working with redundant routers

2016-04-22 Thread Thomas (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15253682#comment-15253682
 ] 

Thomas edited comment on CLOUDSTACK-9360 at 4/22/16 10:10 AM:
--

Hi Wei,

but there is also a logical mistake.
Lets assume that the client tries to get its password from the 
dhcp-server-identifier which is the main IP from the VR for example:
10.0.0.153

The virtual router saved the password via: curl --header "DomU_Request: 
save_password" "http://10.0.0.1:8080/"; -F "ip=10.0.0.104" -F "password=NEWPW" 
-F "token=xxx"

So the password server with the 10.0.0.1 param was used. 
The password server with the 10.0.0.153 looks in its password file: 
/var/cache/cloud/passwords-10.0.0.153 and there is no new password for the 
client, cause its in the  /var/cache/cloud/passwords-10.0.0.1 file.

This could happen, so for me the better fix would be to remove the IP-Check for 
the DomU_Request: save_password request, cause the token also will be checked, 
so it`s not a security risk. The clients need to update their 
guest-set-password boot scripts and use the routers identifier in their DHCP 
lease file for the password server connect.

What do you think?


was (Author: disappear):
Hi Wei,

but there is also a logical mistake.
Lets assume that the client tries to get its password from the 
dhcp-server-identifier which is the main IP from the VR for example:
10.0.0.153

The virtual router saved the password via: curl --header "DomU_Request: 
save_password" "http://10.0.0.1:8080/"; -F "ip=10.0.0.104" -F "password=NEWPW" 
-F "token=xxx"

So the password server with the 10.0.0.1 was used. 
The password server with the 10.0.0.153 looks in its password file: 
/var/cache/cloud/passwords-10.0.0.153 and there is no new password for the 
client, cause its in the  /var/cache/cloud/passwords-10.0.0.1 file.

This could happen, so for me the better fix would be to remove the IP-Check for 
the DomU_Request: save_password request, cause the token also will be checked, 
so it`s not a security risk. The clients need to update their 
guest-set-password boot scripts and use the routers identifier in their DHCP 
lease file for the password server connect.

What do you think?

> Set guest password not working with redundant routers
> -
>
> Key: CLOUDSTACK-9360
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9360
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VPC
>Affects Versions: 4.8.0
> Environment: Two CentOS7 MGMT Servers, redundant router vms
>Reporter: Thomas
>Priority: Critical
>
> We got a problem with the set guest password function. 
> When you spawn a redundant router (VPC or not) the VMs don`t set their 
> password correctly.
> We broke it down to the /opt/cloud/bin/passwd_server_ip.py script which 
> checks the Client IP for the save password function on the routerVM:
> ---
> if clientAddress not in ['localhost', '127.0.0.1', listeningAddress]:
> syslog.syslog('serve_password: non-localhost IP trying to save password: 
> %s' % clientAddress)
> self.send_response(403)
> return
> ---
> In the logs we see:
> --
> Apr 21 09:02:01 r-80-VM passwd_server_ip.py: serve_password: non-localhost IP 
> trying to save password: 10.0.0.236
> --
> The routerVMs eth2 config:
> --
> 4: eth2:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 02:00:2c:d7:00:08 brd ff:ff:ff:ff:ff:ff
> inet 10.0.0.236/24 brd 10.0.0.255 scope global eth2
> inet 10.0.0.1/24 brd 10.0.0.255 scope global secondary eth2
> --
> So what happens:
> The management server triggers the router vm to store a new password for a 
> new spawned or password reseting guest vm.
> The router vm then tries locally to connect to the password python server 
> with it`s primary eth2 ip, in our example: 10.0.0.236
> The python password server then checks the client IP via:
> if clientAddress not in ['localhost', '127.0.0.1', listeningAddress]:
> and exists with: serve_password: non-localhost IP trying to save password: 
> 10.0.0.236
> cause the listeningAddress is filled with: 10.0.0.1
> How to fix
> First possibility:
> Configure the 10.0.0.1 IP as primary IP => maybe not possible cause its 
> managed by keepalived
> Second possibilty:
> Adjust the password server if check and check also for the ip 10.0.0.236.
> I tried to implement this with a subprocess and grep in 
> /var/cache/cloud/processed/guest_network.json.* or with a os command and ip a 
> | grep eth2 | grep -v mtu | cut -d ' ' -f 6 | cut -d '/' -f 1
> Maybe someone could support here?



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

[jira] [Commented] (CLOUDSTACK-9360) Set guest password not working with redundant routers

2016-04-22 Thread Thomas (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15253744#comment-15253744
 ] 

Thomas commented on CLOUDSTACK-9360:


Okay, I will check it again on fresh created VPC routers..

> Set guest password not working with redundant routers
> -
>
> Key: CLOUDSTACK-9360
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9360
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VPC
>Affects Versions: 4.8.0
> Environment: Two CentOS7 MGMT Servers, redundant router vms
>Reporter: Thomas
>Priority: Critical
>
> We got a problem with the set guest password function. 
> When you spawn a redundant router (VPC or not) the VMs don`t set their 
> password correctly.
> We broke it down to the /opt/cloud/bin/passwd_server_ip.py script which 
> checks the Client IP for the save password function on the routerVM:
> ---
> if clientAddress not in ['localhost', '127.0.0.1', listeningAddress]:
> syslog.syslog('serve_password: non-localhost IP trying to save password: 
> %s' % clientAddress)
> self.send_response(403)
> return
> ---
> In the logs we see:
> --
> Apr 21 09:02:01 r-80-VM passwd_server_ip.py: serve_password: non-localhost IP 
> trying to save password: 10.0.0.236
> --
> The routerVMs eth2 config:
> --
> 4: eth2:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 02:00:2c:d7:00:08 brd ff:ff:ff:ff:ff:ff
> inet 10.0.0.236/24 brd 10.0.0.255 scope global eth2
> inet 10.0.0.1/24 brd 10.0.0.255 scope global secondary eth2
> --
> So what happens:
> The management server triggers the router vm to store a new password for a 
> new spawned or password reseting guest vm.
> The router vm then tries locally to connect to the password python server 
> with it`s primary eth2 ip, in our example: 10.0.0.236
> The python password server then checks the client IP via:
> if clientAddress not in ['localhost', '127.0.0.1', listeningAddress]:
> and exists with: serve_password: non-localhost IP trying to save password: 
> 10.0.0.236
> cause the listeningAddress is filled with: 10.0.0.1
> How to fix
> First possibility:
> Configure the 10.0.0.1 IP as primary IP => maybe not possible cause its 
> managed by keepalived
> Second possibilty:
> Adjust the password server if check and check also for the ip 10.0.0.236.
> I tried to implement this with a subprocess and grep in 
> /var/cache/cloud/processed/guest_network.json.* or with a os command and ip a 
> | grep eth2 | grep -v mtu | cut -d ' ' -f 6 | cut -d '/' -f 1
> Maybe someone could support here?



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


[jira] [Commented] (CLOUDSTACK-9360) Set guest password not working with redundant routers

2016-04-22 Thread Thomas (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15254103#comment-15254103
 ] 

Thomas commented on CLOUDSTACK-9360:


No luck something doesn`t work well with that patches. No connection to the 
internet anymore, i went back to my temp fix (no ip check, just token). I don`t 
had time to look into this deeper.

> Set guest password not working with redundant routers
> -
>
> Key: CLOUDSTACK-9360
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9360
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VPC
>Affects Versions: 4.8.0
> Environment: Two CentOS7 MGMT Servers, redundant router vms
>Reporter: Thomas
>Priority: Critical
>
> We got a problem with the set guest password function. 
> When you spawn a redundant router (VPC or not) the VMs don`t set their 
> password correctly.
> We broke it down to the /opt/cloud/bin/passwd_server_ip.py script which 
> checks the Client IP for the save password function on the routerVM:
> ---
> if clientAddress not in ['localhost', '127.0.0.1', listeningAddress]:
> syslog.syslog('serve_password: non-localhost IP trying to save password: 
> %s' % clientAddress)
> self.send_response(403)
> return
> ---
> In the logs we see:
> --
> Apr 21 09:02:01 r-80-VM passwd_server_ip.py: serve_password: non-localhost IP 
> trying to save password: 10.0.0.236
> --
> The routerVMs eth2 config:
> --
> 4: eth2:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 02:00:2c:d7:00:08 brd ff:ff:ff:ff:ff:ff
> inet 10.0.0.236/24 brd 10.0.0.255 scope global eth2
> inet 10.0.0.1/24 brd 10.0.0.255 scope global secondary eth2
> --
> So what happens:
> The management server triggers the router vm to store a new password for a 
> new spawned or password reseting guest vm.
> The router vm then tries locally to connect to the password python server 
> with it`s primary eth2 ip, in our example: 10.0.0.236
> The python password server then checks the client IP via:
> if clientAddress not in ['localhost', '127.0.0.1', listeningAddress]:
> and exists with: serve_password: non-localhost IP trying to save password: 
> 10.0.0.236
> cause the listeningAddress is filled with: 10.0.0.1
> How to fix
> First possibility:
> Configure the 10.0.0.1 IP as primary IP => maybe not possible cause its 
> managed by keepalived
> Second possibilty:
> Adjust the password server if check and check also for the ip 10.0.0.236.
> I tried to implement this with a subprocess and grep in 
> /var/cache/cloud/processed/guest_network.json.* or with a os command and ip a 
> | grep eth2 | grep -v mtu | cut -d ' ' -f 6 | cut -d '/' -f 1
> Maybe someone could support here?



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


[jira] [Comment Edited] (CLOUDSTACK-9360) Set guest password not working with redundant routers

2016-04-22 Thread Thomas (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15254103#comment-15254103
 ] 

Thomas edited comment on CLOUDSTACK-9360 at 4/22/16 3:37 PM:
-

No luck something doesn`t work well in our setup with that patches. No 
connection to the internet anymore, i went back to my temp fix (no ip check, 
just token). I don`t had time to look into this deeper.


was (Author: disappear):
No luck something doesn`t work well with that patches. No connection to the 
internet anymore, i went back to my temp fix (no ip check, just token). I don`t 
had time to look into this deeper.

> Set guest password not working with redundant routers
> -
>
> Key: CLOUDSTACK-9360
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9360
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VPC
>Affects Versions: 4.8.0
> Environment: Two CentOS7 MGMT Servers, redundant router vms
>Reporter: Thomas
>Priority: Critical
>
> We got a problem with the set guest password function. 
> When you spawn a redundant router (VPC or not) the VMs don`t set their 
> password correctly.
> We broke it down to the /opt/cloud/bin/passwd_server_ip.py script which 
> checks the Client IP for the save password function on the routerVM:
> ---
> if clientAddress not in ['localhost', '127.0.0.1', listeningAddress]:
> syslog.syslog('serve_password: non-localhost IP trying to save password: 
> %s' % clientAddress)
> self.send_response(403)
> return
> ---
> In the logs we see:
> --
> Apr 21 09:02:01 r-80-VM passwd_server_ip.py: serve_password: non-localhost IP 
> trying to save password: 10.0.0.236
> --
> The routerVMs eth2 config:
> --
> 4: eth2:  mtu 1500 qdisc pfifo_fast state UP 
> qlen 1000
> link/ether 02:00:2c:d7:00:08 brd ff:ff:ff:ff:ff:ff
> inet 10.0.0.236/24 brd 10.0.0.255 scope global eth2
> inet 10.0.0.1/24 brd 10.0.0.255 scope global secondary eth2
> --
> So what happens:
> The management server triggers the router vm to store a new password for a 
> new spawned or password reseting guest vm.
> The router vm then tries locally to connect to the password python server 
> with it`s primary eth2 ip, in our example: 10.0.0.236
> The python password server then checks the client IP via:
> if clientAddress not in ['localhost', '127.0.0.1', listeningAddress]:
> and exists with: serve_password: non-localhost IP trying to save password: 
> 10.0.0.236
> cause the listeningAddress is filled with: 10.0.0.1
> How to fix
> First possibility:
> Configure the 10.0.0.1 IP as primary IP => maybe not possible cause its 
> managed by keepalived
> Second possibilty:
> Adjust the password server if check and check also for the ip 10.0.0.236.
> I tried to implement this with a subprocess and grep in 
> /var/cache/cloud/processed/guest_network.json.* or with a os command and ip a 
> | grep eth2 | grep -v mtu | cut -d ' ' -f 6 | cut -d '/' -f 1
> Maybe someone could support here?



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


[jira] [Commented] (CLOUDSTACK-9356) VPC add VPN User fails same error as CLOUDSTACK-8927

2016-04-27 Thread Thomas (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15261590#comment-15261590
 ] 

Thomas commented on CLOUDSTACK-9356:


Removing this if clause doesn`t help, so I can not find any workaround yet for 
this.
Maybe someone got an hint for this?

> VPC add VPN User fails same error as CLOUDSTACK-8927
> 
>
> Key: CLOUDSTACK-9356
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9356
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VPC, XenServer
>Affects Versions: 4.8.0
> Environment: Two CentOS7 MGMT Servers, Two XenServerClusters, 
> Advanced Networking, VLAN isolated
>Reporter: Thomas
>Priority: Critical
>
> When we try to add an VPN User on a VPC following error occurs:
> Management Server:
> ---
> Apr 20 09:24:43 WARN  [resource.virtualnetwork.VirtualRoutingResource] 
> (DirectAgent-68:ctx-de5cbf45) (logid:180e35ed) Expected 1 answers while 
> executing VpnUsersCfgCommand but received 2
> Apr 20 09:24:43 admin02 server: WARN  [c.c.a.r.v.VirtualRoutingResource] 
> (DirectAgent-68:ctx-de5cbf45) (logid:180e35ed) Expected 1 answers while 
> executing VpnUsersCfgCommand but received 2
> Apr 20 09:24:47 WARN  [resource.virtualnetwork.VirtualRoutingResource] 
> (DirectAgent-268:ctx-873174f6) (logid:180e35ed) Expected 1 answers while 
> executing VpnUsersCfgCommand but received 2
> Apr 20 09:24:47 admin02 server: WARN  [c.c.a.r.v.VirtualRoutingResource] 
> (DirectAgent-268:ctx-873174f6) (logid:180e35ed) Expected 1 answers while 
> executing VpnUsersCfgCommand but received 2
> Apr 20 09:24:47 WARN  [network.vpn.RemoteAccessVpnManagerImpl] 
> (API-Job-Executor-58:ctx-7f86f610 job-1169 ctx-1073feac) (logid:180e35ed) 
> Unable to apply vpn users
> Apr 20 09:24:47 localhost java.lang.IndexOutOfBoundsException: Index: 1, 
> Size: 1
> Apr 20 09:24:47 localhost at 
> java.util.ArrayList.rangeCheck(ArrayList.java:653)
> Apr 20 09:24:47 localhost at java.util.ArrayList.get(ArrayList.java:429)
> Apr 20 09:24:47 localhost at 
> com.cloud.network.vpn.RemoteAccessVpnManagerImpl.applyVpnUsers(RemoteAccessVpnManagerImpl.java:532)
> Apr 20 09:24:47 localhost at 
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> Apr 20 09:24:47 localhost at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> Apr 20 09:24:47 localhost at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Apr 20 09:24:47 localhost at 
> java.lang.reflect.Method.invoke(Method.java:498)
> Apr 20 09:24:47 localhost at 
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> Apr 20 09:24:47 localhost at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> Apr 20 09:24:47 localhost at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> Apr 20 09:24:47 localhost at 
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> Apr 20 09:24:47 localhost at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> Apr 20 09:24:47 localhost at 
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> Apr 20 09:24:47 localhost at 
> com.sun.proxy.$Proxy234.applyVpnUsers(Unknown Source)
> Apr 20 09:24:47 localhost at 
> org.apache.cloudstack.api.command.user.vpn.AddVpnUserCmd.execute(AddVpnUserCmd.java:122)
> Apr 20 09:24:47 localhost at 
> com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:150)
> Apr 20 09:24:47 localhost at 
> com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
> Apr 20 09:24:47 localhost at 
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:554)
> Apr 20 09:24:47 localhost at 
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> Apr 20 09:24:47 localhost at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> Apr 20 09:24:47 localhost at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> Apr 20 09:24:47 localhost at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> Apr 20 09:24:47 localhost at 
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnabl