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

Kelven Yang commented on CLOUDSTACK-1262:
-----------------------------------------

A patch request has been filed to the review board for 4.1 branch.
Path is pushed to master branch
                
> Failed to Prepare Secondary Storage in VMware, 
> -----------------------------------------------
>
>                 Key: CLOUDSTACK-1262
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1262
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Install and Setup
>    Affects Versions: 4.1.0, 4.2.0
>         Environment: CentOS 6.3
> Vmware
>            Reporter: Rayees Namathponnan
>            Assignee: Kelven Yang
>            Priority: Blocker
>             Fix For: 4.1.0, 4.2.0
>
>         Attachments: management-server.log
>
>
> Failed to prepare secondary storage VM in VMware, since we are expecting 
> systemvm.iso is available at /usr/lib64/cloud/common//vms/systemvm.iso 
> instead of /usr/share/cloudstack-common/vms/systemvm.iso
> /plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/manager/VmwareManagerImpl.java
>     private File getSystemVMPatchIsoFile() {
>         // locate systemvm.iso
>         URL url = 
> this.getClass().getProtectionDomain().getCodeSource().getLocation();
>         File file = new File(url.getFile());
>         File isoFile = new File(file.getParent() + "/vms/systemvm.iso");
>         if (!isoFile.exists()) {
>             isoFile = new File("/usr/lib64/cloud/common/" + 
> "/vms/systemvm.iso");
>             if (!isoFile.exists()) {
>                 isoFile = new File("/usr/lib/cloud/common/" + 
> "/vms/systemvm.iso");
>             }
>         }
>         return isoFile;
>     }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to