[
https://issues.apache.org/jira/browse/CLOUDSTACK-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13592243#comment-13592243
]
ASF subversion and git services commented on CLOUDSTACK-1262:
-------------------------------------------------------------
Commit 99284e7c954b6771dd5101abe5352d4d43a4105c in branch refs/heads/4.1 from
[~cloudplatform_common]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;h=99284e7 ]
CLOUDSTACK-1262: update default built-in systemvm.iso search patch to be
consistent with RPM location
Signed-off-by: Kelven Yang <kelv...@gmail.com>
> 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
