You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Chandan Purushothama (JIRA)" <ji...@apache.org> on 2013/02/28 00:11:12 UTC

[jira] [Resolved] (CLOUDSTACK-1262) Failed to Prepare Secondary Storage in VMware,

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chandan Purushothama resolved CLOUDSTACK-1262.
----------------------------------------------

    Resolution: Fixed

The issue did not surface on my setup. I used a Freshly deployed RHEL 6.3 VM for my 4.1 management server purposes. From what I saw with certain setups is, it looks like the RHEL 6.3 VMs that were previously used for ASF 4.0 will create problems for ASF 4.1 deployments. It got something to do with the changes made in ASF 4.1 release of creating a "cloud" user and corresponding "cloudstack" named paths instead of "cloud" named paths. Since ASF 4.0 deployments already have a cloud user created, a subsequent creation of such an User during ASF 4.1 deployments is not done. We clean up the packages before a new deployment for testing. But we do not delete the cloud user before every new deployment. Because we didn’t come across such a situation before. We need to take care of this scenario during ASF 4.0 to 4.1 Upgrade.
                
> 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
>         Environment: CentOS 6.3
> Vmware
>            Reporter: Rayees Namathponnan
>            Assignee: Chandan Purushothama
>            Priority: Blocker
>             Fix For: 4.1.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