-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to deploy VMs with additional disks on EGI FedCloud OpenStack sites #578
Comments
Hi @alahiff, Try to remove the line:
In some connectors are not supported. |
Hi @micafer, thanks for the quick reply. Removing the device line results in a slightly different error:
|
Sometimes the problem is that the device is already used, try to use another one: vdc, vdd ... |
I had already tried a few other devices without success. I've now tried some more and I still always have the same problem. BTW if I create a VM using https://dashboard.appdb.egi.eu/vmops on IN2P3-IRES, for example, and specify an additional disk, everything is fine (and vdb is used). I think this webpage uses IM internally (?) |
Yes the AppDB VMOps dashboard uses the IM internally to launch the VMs. |
Not just Bari, also IN2P3-IRES and INFN-PADOVA-STACK. |
I have contacted with the AppDB VMOps dashboard developers and they say me that the RADL code that they use is like that:
|
I can create a VM using the VMOps dashboard on RECAS-BARI and it works fine, but when using IM directly with the RADL extract above I get:
For IN2P3-IRES it doesn't actually work on the VMOps dashboard. Fortunately I get the same error:
In this case I assume there is a message/error containing a French accent which is causing problems. |
In RECAS Bari I have tried using this RADL code and it worked for me.
But I think that I know that reason that causes your error. In the case of IN2P3-IRES as you said there is an error message containing a French accent which is causing problems.
It means that you are selecting a flavour too small fot the image selected. You probably has used the smalles one (as me) and you get this error. (I will also have to fix this error with French accents). |
Yes, I had taken the site endpoint from appdb, which for RECAS-BARI has a slash at the end. I have now tried without the slash and it works. I also just tried IN2P3-IRES with a larger flavour, and it also works. Thanks! |
You are wellcome. |
If I create a VM with an additional disk by including something like this in the RADL:
this works as expected on CESNET-MetaCloud (and also on Azure and Google btw). However, I can't get it to work on FedCloud sites which use OpenStack such as RECAS-BARI and IN2P3-IRES. I get an error like this:
Looking in
/var/log/im/im.log
I see this:So the volume seems to be successfully created but is almost immediately deleted for some reason, then an
Internal Server Error
appears.I am using the grycap/im:1.6.7-1 Docker image.
The text was updated successfully, but these errors were encountered: