[jira] [Updated] (CLOUDSTACK-7493) [Automation] Egress Firewall Rule fails to create on the Virtual Router in Hyper-V Setup - Reports Success instead of failure report
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayapal Reddy updated CLOUDSTACK-7493:
--
Assignee: Rajesh Battala (was: Jayapal Reddy)
[Automation] Egress Firewall Rule fails to create on the Virtual Router in
Hyper-V Setup - Reports Success instead of failure report
Key: CLOUDSTACK-7493
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7493
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Rajesh Battala
Priority: Blocker
Fix For: 4.5.0
==
Error in management Server log:
==
{code}
2014-09-03 18:04:36,689 DEBUG [c.c.a.ApiServlet]
(catalina-exec-22:ctx-a84568da ctx-c6c0fc58 ctx-985e7722) ===END===
10.220.135.217 -- GET
jobid=561bbb6c-7931-493d-a778-525086befb96apiKey=hCPmYiAF1lm_sBLrhXIEWXCJt0vYbxzkeFfv7E1ZhyPPL_TF6BvI8cVOm2AqLlzWwa2w9dO0eFQu6SafM_st3gcommand=queryAsyncJobResultresponse=jsonsignature=fWkgkcIGrOu7YQc%2Fw5GD%2B3HHGkM%3D
2014-09-03 18:04:36,701 DEBUG [c.c.a.t.Request]
(API-Job-Executor-33:ctx-4c5fd3c9 job-316 ctx-8bc88918) Seq
1-4477422454536405316: Sending { Cmd , MgmtId: 174253150778429, via:
1(10.220.163.36), Ver: v1, Flags: 11,
[{com.cloud.agent.api.routing.SetFirewallRulesCommand:{rules:[{id:36,srcIp:,protocol:all,revoked:false,alreadyAdded:false,sourceCidrList:[0.0.0.0/0],purpose:Firewall,trafficType:Egress,defaultEgressPolicy:false}],accessDetails:{router.guest.ip:192.168.200.1,firewall.egress.default:false,zone.network.type:Advanced,router.ip:10.220.165.184,router.name:r-45-VM},wait:0}}]
}
2014-09-03 18:04:36,701 DEBUG [c.c.a.t.Request]
(API-Job-Executor-33:ctx-4c5fd3c9 job-316 ctx-8bc88918) Seq
1-4477422454536405316: Executing: { Cmd , MgmtId: 174253150778429, via:
1(10.220.163.36), Ver: v1, Flags: 11,
[{com.cloud.agent.api.routing.SetFirewallRulesCommand:{rules:[{id:36,srcIp:,protocol:all,revoked:false,alreadyAdded:false,sourceCidrList:[0.0.0.0/0],purpose:Firewall,trafficType:Egress,defaultEgressPolicy:false}],accessDetails:{router.guest.ip:192.168.200.1,firewall.egress.default:false,zone.network.type:Advanced,router.ip:10.220.165.184,router.name:r-45-VM},wait:0}}]
}
2014-09-03 18:04:36,702 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-316:ctx-c363d57a) Seq 1-4477422454536405316: Executing request
2014-09-03 18:04:36,702 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-316:ctx-c363d57a) Use router's private IP for SSH control. IP :
10.220.165.184
2014-09-03 18:04:36,702 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-316:ctx-c363d57a) Run command on VR: 10.220.165.184, script:
firewall_egress.sh with args: -F -E -P 0 -a :all:0:0:0.0.0.0/0:,
2014-09-03 18:04:37,394 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-14:null) SeqA 3-604: Processing Seq 3-604: { Cmd ,
MgmtId: -1, via: 3, Ver: v1, Flags: 11,
[{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:2,_loadInfo:{\n
\connections\: []\n},wait:0}}] }
2014-09-03 18:04:37,397 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-14:null) SeqA 3-604: Sending Seq 3-604: { Ans: ,
MgmtId: 174253150778429, via: 3, Ver: v1, Flags: 100010,
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2014-09-03 18:04:37,826 DEBUG [c.c.s.StorageManagerImpl]
(StorageManager-Scavenger-3:ctx-e8a5b20a) Storage pool garbage collector
found 0 templates to clean up in storage pool:
XenRT-Zone-0-Pod-0-Cluster-0-Primary-Store-0
2014-09-03 18:04:37,829 DEBUG [c.c.s.StorageManagerImpl]
(StorageManager-Scavenger-3:ctx-e8a5b20a) Secondary storage garbage collector
found 0 templates to cleanup on template_store_ref for store:
cifs://10.220.163.36/storage/secondary
2014-09-03 18:04:37,831 DEBUG [c.c.s.StorageManagerImpl]
(StorageManager-Scavenger-3:ctx-e8a5b20a) Secondary storage garbage collector
found 0 snapshots to cleanup on snapshot_store_ref for store:
cifs://10.220.163.36/storage/secondary
2014-09-03 18:04:37,832 DEBUG [c.c.s.StorageManagerImpl]
(StorageManager-Scavenger-3:ctx-e8a5b20a) Secondary storage garbage collector
found 0 volumes to cleanup on volume_store_ref for store:
cifs://10.220.163.36/storage/secondary
2014-09-03 18:04:37,940 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-316:ctx-c363d57a) firewall_egress.sh execution result: true
2014-09-03 18:04:37,940 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-316:ctx-c363d57a) Seq 1-4477422454536405316: Response Received:
2014-09-03
[jira] [Commented] (CLOUDSTACK-7493) [Automation] Egress Firewall Rule fails to create on the Virtual Router in Hyper-V Setup - Reports Success instead of failure report
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14125192#comment-14125192
]
Jayapal Reddy commented on CLOUDSTACK-7493:
---
Hi Rajesh,
[~rajesh_battala]
From the log the setEgressFirewallRuleCommand is success and script execution
in VR is also success.
[~chandanp]
How did you check rule creation failed in VR ?
firewall_egress.sh execution result: true
2014-09-03 18:04:37,940 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-316:ctx-c363d57a) Seq 1-4477422454536405316: Response Received:
2014-09-03 18:04:37,940 DEBUG [c.c.a.t.Request] (DirectAgent-316:ctx-c363d57a)
Seq 1-4477422454536405316: Processing: { Ans: , MgmtId: 174253150778429, via:
1, Ver: v1, Flags: 0, [{com.cloud.agent.api.Answer:{result:true,details:
[Automation] Egress Firewall Rule fails to create on the Virtual Router in
Hyper-V Setup - Reports Success instead of failure report
Key: CLOUDSTACK-7493
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7493
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Jayapal Reddy
Priority: Blocker
Fix For: 4.5.0
==
Error in management Server log:
==
{code}
2014-09-03 18:04:36,689 DEBUG [c.c.a.ApiServlet]
(catalina-exec-22:ctx-a84568da ctx-c6c0fc58 ctx-985e7722) ===END===
10.220.135.217 -- GET
jobid=561bbb6c-7931-493d-a778-525086befb96apiKey=hCPmYiAF1lm_sBLrhXIEWXCJt0vYbxzkeFfv7E1ZhyPPL_TF6BvI8cVOm2AqLlzWwa2w9dO0eFQu6SafM_st3gcommand=queryAsyncJobResultresponse=jsonsignature=fWkgkcIGrOu7YQc%2Fw5GD%2B3HHGkM%3D
2014-09-03 18:04:36,701 DEBUG [c.c.a.t.Request]
(API-Job-Executor-33:ctx-4c5fd3c9 job-316 ctx-8bc88918) Seq
1-4477422454536405316: Sending { Cmd , MgmtId: 174253150778429, via:
1(10.220.163.36), Ver: v1, Flags: 11,
[{com.cloud.agent.api.routing.SetFirewallRulesCommand:{rules:[{id:36,srcIp:,protocol:all,revoked:false,alreadyAdded:false,sourceCidrList:[0.0.0.0/0],purpose:Firewall,trafficType:Egress,defaultEgressPolicy:false}],accessDetails:{router.guest.ip:192.168.200.1,firewall.egress.default:false,zone.network.type:Advanced,router.ip:10.220.165.184,router.name:r-45-VM},wait:0}}]
}
2014-09-03 18:04:36,701 DEBUG [c.c.a.t.Request]
(API-Job-Executor-33:ctx-4c5fd3c9 job-316 ctx-8bc88918) Seq
1-4477422454536405316: Executing: { Cmd , MgmtId: 174253150778429, via:
1(10.220.163.36), Ver: v1, Flags: 11,
[{com.cloud.agent.api.routing.SetFirewallRulesCommand:{rules:[{id:36,srcIp:,protocol:all,revoked:false,alreadyAdded:false,sourceCidrList:[0.0.0.0/0],purpose:Firewall,trafficType:Egress,defaultEgressPolicy:false}],accessDetails:{router.guest.ip:192.168.200.1,firewall.egress.default:false,zone.network.type:Advanced,router.ip:10.220.165.184,router.name:r-45-VM},wait:0}}]
}
2014-09-03 18:04:36,702 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-316:ctx-c363d57a) Seq 1-4477422454536405316: Executing request
2014-09-03 18:04:36,702 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-316:ctx-c363d57a) Use router's private IP for SSH control. IP :
10.220.165.184
2014-09-03 18:04:36,702 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-316:ctx-c363d57a) Run command on VR: 10.220.165.184, script:
firewall_egress.sh with args: -F -E -P 0 -a :all:0:0:0.0.0.0/0:,
2014-09-03 18:04:37,394 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-14:null) SeqA 3-604: Processing Seq 3-604: { Cmd ,
MgmtId: -1, via: 3, Ver: v1, Flags: 11,
[{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:2,_loadInfo:{\n
\connections\: []\n},wait:0}}] }
2014-09-03 18:04:37,397 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-14:null) SeqA 3-604: Sending Seq 3-604: { Ans: ,
MgmtId: 174253150778429, via: 3, Ver: v1, Flags: 100010,
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2014-09-03 18:04:37,826 DEBUG [c.c.s.StorageManagerImpl]
(StorageManager-Scavenger-3:ctx-e8a5b20a) Storage pool garbage collector
found 0 templates to clean up in storage pool:
XenRT-Zone-0-Pod-0-Cluster-0-Primary-Store-0
2014-09-03 18:04:37,829 DEBUG [c.c.s.StorageManagerImpl]
(StorageManager-Scavenger-3:ctx-e8a5b20a) Secondary storage garbage collector
found 0 templates to cleanup on template_store_ref for store:
cifs://10.220.163.36/storage/secondary
2014-09-03 18:04:37,831 DEBUG [c.c.s.StorageManagerImpl]
(StorageManager-Scavenger-3:ctx-e8a5b20a) Secondary storage garbage collector
found 0 snapshots to cleanup
[jira] [Resolved] (CLOUDSTACK-5992) [Upgrade] default values of configuraiton parameters in configuration table are set NULL on fresh setup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi resolved CLOUDSTACK-5992. - Resolution: Fixed [Upgrade] default values of configuraiton parameters in configuration table are set NULL on fresh setup Key: CLOUDSTACK-5992 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5992 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Upgrade Affects Versions: 4.3.0 Reporter: Harikrishna Patnala Assignee: Harikrishna Patnala Fix For: 4.5.0 Attachments: ConfigPropertiesComparison.html During recent Upgrade test, 1) many of the global parameters have NULL values as the default Values. 2) Component names are different in fresh and upgrade setup I attached the comparison document to this -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7500) [BVT blocker] setup/dev/basic.cfg needs 2 simulator hosts
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14125207#comment-14125207 ] ASF subversion and git services commented on CLOUDSTACK-7500: - Commit c9dbfa0632788aa99e412d8173288fb38006db19 in cloudstack's branch refs/heads/master from [~johnmdilley] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c9dbfa0 ] CLOUDSTACK-7500: Add 2 hosts to simulator basic.cfg Signed-off-by: SrikanteswaraRao Talluri tall...@apache.org [BVT blocker] setup/dev/basic.cfg needs 2 simulator hosts - Key: CLOUDSTACK-7500 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7500 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, marvin Affects Versions: Future, 4.5.0 Reporter: John Dilley Assignee: John Dilley Priority: Critical Fix For: Future, 4.5.0 setup/dev/basic.cfg only has one simulated host, but some tests require 2 hosts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-6898) [Hyper-V] Open the console of a VM from CS, reboot the VM ( from CS or from inside the console), the console gets stuck at a point.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshul Gangwar reassigned CLOUDSTACK-6898: -- Assignee: Anshul Gangwar (was: Devdeep Singh) [Hyper-V] Open the console of a VM from CS, reboot the VM ( from CS or from inside the console), the console gets stuck at a point. --- Key: CLOUDSTACK-6898 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6898 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.0 Environment: Hyper-V Reporter: Abhinav Roy Assignee: Anshul Gangwar Priority: Critical Labels: hyper-V,, hyper-v, hyperv Fix For: 4.4.0 Attachments: CS-6898.jpg Steps : == 1. Deploy a Hyper-V setup with advanced zone. 2. Deploy a VM. 3. Now open the console of the VM from CS UI. 4. Now reboot the VM from CS or from inside the console of VM Expected behavior : === 1. The console should be accessible when the the VM is rebooting and after it boots up. Observed behavior : == The console gets stuck at the point of stopping the VM and remains in that state. Even if you close the console and reopen , it remains in the same state. Attaching a screenshot for that. Workaround : Either close the console or even in the open state don't do any activity on it for 3 mins. After that it becomes accessible again. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7495) [Automation][HyperV] Stack trace along with error message - CloudStack currently only supports volumes marked as the KVM, VMware, or XenServer hypervisor type for
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14125217#comment-14125217
]
Sailaja Mada commented on CLOUDSTACK-7495:
--
This is automated and BVT is skipping this test:
elif hosts[0].hypervisor.lower() in (vmware, hyperv):
self.skipTest(Resize Volume is unsupported on VmWare and Hyper-V)
[Automation][HyperV] Stack trace along with error message - CloudStack
currently only supports volumes marked as the KVM, VMware, or XenServer
hypervisor type for resize.
--
Key: CLOUDSTACK-7495
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7495
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, Test
Affects Versions: 4.5.0
Reporter: Chandan Purushothama
Assignee: Devdeep Singh
Priority: Critical
Fix For: 4.5.0
{code}
2014-09-03 17:55:32,084 DEBUG [c.c.a.ApiServlet]
(catalina-exec-11:ctx-5e814549 ctx-6724d865 ctx-56a27ef7) ===END===
10.220.135.217 -- GET
jobid=3f397629-d004-4020-a97d-8aa277ea2c61apiKey=hCPmYiAF1lm_sBLrhXIEWXCJt0vYbxzkeFfv7E1ZhyPPL_TF6BvI8cVOm2AqLlzWwa2w9dO0eFQu6SafM_st3gcommand=queryAsyncJobResultresponse=jsonsignature=6X9pGZqTxQTAxWy4N73kVno%2B62s%3D
2014-09-03 17:55:32,091 ERROR [c.c.a.ApiAsyncJobDispatcher]
(API-Job-Executor-123:ctx-0a86f6fa job-255) Unexpected exception while
executing
org.apache.cloudstack.api.command.admin.volume.ResizeVolumeCmdByAdmin
com.cloud.exception.InvalidParameterValueException: CloudStack currently only
supports volumes marked as the KVM, VMware, or XenServer hypervisor type for
resize.
at
com.cloud.storage.VolumeApiServiceImpl.resizeVolume(VolumeApiServiceImpl.java:725)
at
com.cloud.storage.VolumeApiServiceImpl.resizeVolume(VolumeApiServiceImpl.java:150)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy184.resizeVolume(Unknown Source)
at
org.apache.cloudstack.api.command.admin.volume.ResizeVolumeCmdByAdmin.execute(ResizeVolumeCmdByAdmin.java:37)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141)
at
com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at
[jira] [Updated] (CLOUDSTACK-6898) [Hyper-V] Open the console of a VM from CS, reboot the VM ( from CS or from inside the console), the console gets stuck at a point.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshul Gangwar updated CLOUDSTACK-6898: --- Status: Reviewable (was: In Progress) [Hyper-V] Open the console of a VM from CS, reboot the VM ( from CS or from inside the console), the console gets stuck at a point. --- Key: CLOUDSTACK-6898 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6898 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.0 Environment: Hyper-V Reporter: Abhinav Roy Assignee: Anshul Gangwar Priority: Critical Labels: hyper-V,, hyper-v, hyperv Fix For: 4.4.0 Attachments: CS-6898.jpg Steps : == 1. Deploy a Hyper-V setup with advanced zone. 2. Deploy a VM. 3. Now open the console of the VM from CS UI. 4. Now reboot the VM from CS or from inside the console of VM Expected behavior : === 1. The console should be accessible when the the VM is rebooting and after it boots up. Observed behavior : == The console gets stuck at the point of stopping the VM and remains in that state. Even if you close the console and reopen , it remains in the same state. Attaching a screenshot for that. Workaround : Either close the console or even in the open state don't do any activity on it for 3 mins. After that it becomes accessible again. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6898) [Hyper-V] Open the console of a VM from CS, reboot the VM ( from CS or from inside the console), the console gets stuck at a point.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14125221#comment-14125221 ] Anshul Gangwar commented on CLOUDSTACK-6898: patch is available for review at https://reviews.apache.org/r/25292/ [Hyper-V] Open the console of a VM from CS, reboot the VM ( from CS or from inside the console), the console gets stuck at a point. --- Key: CLOUDSTACK-6898 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6898 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.0 Environment: Hyper-V Reporter: Abhinav Roy Assignee: Anshul Gangwar Priority: Critical Labels: hyper-V,, hyper-v, hyperv Fix For: 4.4.0 Attachments: CS-6898.jpg Steps : == 1. Deploy a Hyper-V setup with advanced zone. 2. Deploy a VM. 3. Now open the console of the VM from CS UI. 4. Now reboot the VM from CS or from inside the console of VM Expected behavior : === 1. The console should be accessible when the the VM is rebooting and after it boots up. Observed behavior : == The console gets stuck at the point of stopping the VM and remains in that state. Even if you close the console and reopen , it remains in the same state. Attaching a screenshot for that. Workaround : Either close the console or even in the open state don't do any activity on it for 3 mins. After that it becomes accessible again. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7476) centos cloudstack-usage script does not always pass along $JAVA_HOME
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14125223#comment-14125223 ] ASF GitHub Bot commented on CLOUDSTACK-7476: Github user karuturi commented on the pull request: https://github.com/apache/cloudstack/pull/17#issuecomment-54777280 4.4:packaging/debian/init/cloud-usage already has the new logic to set $JAVA_HOME (e77da80e01b0774951e5c2ab1b23539af002b8b4) Given that it is already in 4.3(3bf4c294313eb0bdb9597f0af2cf6b81a8b4) and master(c468228fe807c621decc5919dadae9bcbb38c753), I think we should port the change to the file 4.4:packaging/centos63/cloud-usage.rc as well centos cloudstack-usage script does not always pass along $JAVA_HOME Key: CLOUDSTACK-7476 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7476 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Usage Affects Versions: 4.5.0 Environment: secured centos/redhat Reporter: Leo Simons Fix For: 4.5.0 /etc/init.d/cloudstack-usage finds a $JAVA_HOME and makes sure the environment variable is set, then assumes this variable will be picked up by JSVC. However, on a secured environment (selinux w/ env_reset enabled in sudoers), the runuser command that is invoked by the daemon() function does not pass along environment variables, so $JAVA_HOME is empty, and JSVC falls back to its default behavior, which may not find java or may not find the intended java. The simple solution is to pass -home to JSVC, passing it on the command line instead of as an environment variable. I'll provide a patch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
