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

Francois Gaudreault commented on CLOUDSTACK-6096:
-------------------------------------------------

Also impact 4.3.0.

> Using eject on Windows will prevent attaching ISO to the instance
> -----------------------------------------------------------------
>
>                 Key: CLOUDSTACK-6096
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6096
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Hypervisor Controller, Management Server
>    Affects Versions: 4.2.1, 4.3.0
>            Reporter: Francois Gaudreault
>
> Seen on 4.2.1 with XS6.2 SP1 with Windows 2008 template.
> If you deploy a Windows template, and you attach an ISO to the instance, and 
> then you click on Eject from Windows, you will be able to detach the ISO from 
> CloudStack, but the SR on XenServer will remain. That will prevent a user to 
> re-attach the same or any other ISO to this instance.
> The error we see when we try to reattach the ISO is misleading since it talks 
> about the URL not being found instead of the real cause.
> 2014-02-12 20:13:44,060 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-454:null) Seq 1-1166937279: Executing request
> 2014-02-12 20:13:44,182 WARN  [xen.resource.CitrixResourceBase] 
> (DirectAgent-454:null) can not getVDIbyLocationandSR 
> 223-2-d0e89fa1-fcaf-3180-ae86-5aeab5d7a8b1.iso
> 2014-02-12 20:13:44,183 WARN [xen.resource.XenServerStorageProcessor] 
> (DirectAgent-454:null) Failed to attach iso: 
> com.cloud.utils.exception.CloudRuntimeException: Could not find ISO with URL:
> To recover from this, I had to SSH to the XenServer Hypervisor, lazy unmount 
> the stuck SR, and remove it. Then I was able to reattach the ISO again.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to