You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Özhan Rüzgar Karaman (JIRA)" <ji...@apache.org> on 2017/01/21 11:50:26 UTC

[jira] [Commented] (CLOUDSTACK-9144) VMware in Basic Zone: VR never leaves the "Starting" state

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

Özhan Rüzgar Karaman commented on CLOUDSTACK-9144:
--------------------------------------------------

4.9.2 version also effects from this problem, vr never leaves on starting state. Do we have any workaround on this problem...



> VMware in Basic Zone: VR never leaves the "Starting" state
> ----------------------------------------------------------
>
>                 Key: CLOUDSTACK-9144
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9144
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Virtual Router, VMware
>    Affects Versions: 4.6.0, 4.7.0
>         Environment: Management server running on Ubuntu 12.04
> Secondary storage being served off of the same computer as that which was running the management server
>            Reporter: Mike Tutkowski
>             Fix For: Future
>
>         Attachments: cloud.log, syslog, vmops.log
>
>
> I fetched the latest code and checked out the 4.6 branch.
> The code was compiled as such:
> mvn -P developer,systemvm clean install -D noredist
> I grabbed the latest system VM template from http://jenkins.buildacloud.org/.
> I walked through the new-zone wizard (creating a basic zone) and tried to make use of it with two ESXi 5.5 hosts (under the control of vCenter Server).
> The SSVM and CPVM seemed to come up OK, but the VR (once I tried to kick off my first user VM) never exited the "Starting" state.
> I repeated this same process for 4.7 and arrived at the same results.
> I then fell back to 4.5, repeated the process, and was successful.



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