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

ASF subversion and git services commented on CLOUDSTACK-5275:
-------------------------------------------------------------

Commit 2b1d9977282f9949791a005d601955355643e35c in branch refs/heads/master 
from [~devdeep]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2b1d997 ]

CLOUDSTACK-5248: Fixed creation of mount point when running as non root (cloud) 
user.
The systemvm iso file is copied only when a systemvm or router vm is to be 
started on
a host. The file gets copied to the secondary storage. The mount point used is 
the one
that has permissions for regular user to mount a share.
CLOUDSTACK-5275: The failure was because a secondary storage wasn't available 
when the
host was added. When a setup is done through wizard the hosts get added before 
the
secondary storage. CS was tying to copy yhe systemvm iso to secondary and it 
used to
fail if it wasn't available. Made a change to copy the iso only when a systemvm 
is
being started on a host.
CLOUDSTACK-5202: Made changes to clean up mount points on stop and start.

All the three are related fixes; so putting a fix in one commit.


> [Hyper-V] Adding host requires an agent restart to be performed for 
> successful addition
> ---------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5275
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5275
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Hypervisor Controller
>    Affects Versions: 4.3.0
>         Environment: Hyper-V, Advanced zone
>            Reporter: Sowmya Krishnan
>            Assignee: Devdeep Singh
>            Priority: Critical
>              Labels: hyper-V,
>             Fix For: 4.3.0
>
>
> Create an advanced zone with single cluster, pod and secondary storage. 
> Adding host doesn't go through. We need to explicitly restart the hyper v 
> agent for having the host to get recognized and added. There are no errors or 
> exceptions thrown, it just stops after the following logs, there's no action 
> beyond this. 
> 2013-11-26 12:04:21,395 DEBUG [c.c.a.ApiServlet] 
> (catalina-exec-3:ctx-0e4961c6) ===START===  10.104.255.45 -- POST  
> command=addHost&response=json&sessionkey=
> 5DGP7gv1vXNaK35rAxfIEi7256o%3D
> 2013-11-26 12:04:21,417 INFO  [c.c.r.ResourceManagerImpl] 
> (catalina-exec-3:ctx-0e4961c6 ctx-2a13907e) Trying to add a new host at 
> http://10.102.192.39 in dat a center 1
> 2013-11-26 12:04:21,418 INFO  [c.c.h.h.d.HypervServerDiscoverer] 
> (catalina-exec-3:ctx-0e4961c6 ctx-2a13907e) Discover host. dc(zone): 1, pod: 
> 1, cluster: 1, uri host: 10.102.192.39
> 2013-11-26 12:04:21,424 INFO  [c.c.h.h.d.HypervServerDiscoverer] 
> (catalina-exec-3:ctx-0e4961c6 ctx-2a13907e) 
> Creatingcom.cloud.hypervisor.hyperv.resource.Hyp
> ervDirectConnectResource HypervDummyResourceBase for zone/pod/cluster 1/1/1
> 2013-11-26 12:04:21,428 DEBUG [c.c.h.h.r.HypervDirectConnectResource] 
> (catalina-exec-3:ctx-0e4961c6 ctx-2a13907e) POST request 
> tohttp://10.102.192.39:8250/ap 
> i/HypervResource/com.cloud.agent.api.ReadyCommand with 
> contents{"contextMap":{},"wait":0}
> 2013-11-26 12:04:21,428 DEBUG [c.c.h.h.r.HypervDirectConnectResource] 
> (catalina-exec-3:ctx-0e4961c6 ctx-2a13907e) Sending cmd to 
> http://10.102.192.39:8250/api/HypervResource/com.cloud.agent.api.ReadyCommand 
> cmd data:{"contextMap":{},"wait":0}
> Only if agent is restarted, host gets added successfully.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Reply via email to