You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Jeroen Kleijer <je...@gmail.com> on 2024/09/07 11:42:14 UTC

Unable to deploy VM instances

Ls,

I've installed ACS (4.19.0.2-1) several times already but as of yesterday
I'm running into something I haven't seen before:
I've created a zone, pod and cluster and added hosts. I created a guest
network (L2 VLAN with ConfigDrive) and installed a Template. (Rocky Linux
9) This has worked numerous times before but now, when I try to spin up a
new VM in my new setup, I'm hit with the following error message:

Unable to orchestrate start VM instance
{"id":10,"instanceName":"i-2-10-VM","type":"User","uuid":"0604b5e6-eb27-4d76-89c2-481d07683187"}
due to [Unable to create iso file: i-2-10-VM.iso due to gexorriso 1.5.4 :
RockRidge filesystem manipulator, libburnia project.xorriso : FAILURE : Not
a known command: '-o'xorriso : FAILURE : Not a known command:
'/tmp/configdrive2202287813434599114/i-2-10-VM.iso'xorriso : FAILURE : Not
a known command: '-ldots'xorriso : FAILURE : Not a known command:
'-allow-lowercase'xorriso : FAILURE : Not a known command:
'-allow-multidot'xorriso : FAILURE : Not a known command:
'-cache-inodes'xorriso : FAILURE : Not a known command: '-l'xorriso :
FAILURE : Not a known command: '-quiet'xorriso : FAILURE : Not a known
command: '-J'xorriso : FAILURE : Not a known command: '-r'xorriso : FAILURE
: Not a known command: '-V'xorriso : FAILURE : Not a known command:
'config-2'xorriso : FAILURE : Not a known command:
'/tmp/configdrive2202287813434599114'xorriso : aborting : -abort_on
'FAILURE' encountered 'FAILURE'].

Has anyone seen this error before and know what it means or how to resolve
it?
My System VMs are in an Up and Running state with the Agents running as
well so that can't be it.

Kind regards,

Jeroen Kleijer

Re: Unable to deploy VM instances

Posted by Jeroen Kleijer <je...@gmail.com>.
Hi Daan,

I've reverted back to installing ACS on Rocky Linux 8 and then the error
does not show up.
I'll try to investigate further but at the moment I've got some other
issues going on.

Kind regards,

Jeroen Kleijer

On Mon, Sep 9, 2024 at 8:51 AM Daan Hoogland <da...@gmail.com>
wrote:

> Jeroen,
> Can you deploy other templates? The text seems like an error message that
> ACS would not create but only pass on and looks like either coming from the
> backend or the template.
>
> On Sat, Sep 7, 2024 at 1:42 PM Jeroen Kleijer <je...@gmail.com>
> wrote:
>
> > Ls,
> >
> > I've installed ACS (4.19.0.2-1) several times already but as of yesterday
> > I'm running into something I haven't seen before:
> > I've created a zone, pod and cluster and added hosts. I created a guest
> > network (L2 VLAN with ConfigDrive) and installed a Template. (Rocky Linux
> > 9) This has worked numerous times before but now, when I try to spin up a
> > new VM in my new setup, I'm hit with the following error message:
> >
> > Unable to orchestrate start VM instance
> >
> >
> {"id":10,"instanceName":"i-2-10-VM","type":"User","uuid":"0604b5e6-eb27-4d76-89c2-481d07683187"}
> > due to [Unable to create iso file: i-2-10-VM.iso due to gexorriso 1.5.4 :
> > RockRidge filesystem manipulator, libburnia project.xorriso : FAILURE :
> Not
> > a known command: '-o'xorriso : FAILURE : Not a known command:
> > '/tmp/configdrive2202287813434599114/i-2-10-VM.iso'xorriso : FAILURE :
> Not
> > a known command: '-ldots'xorriso : FAILURE : Not a known command:
> > '-allow-lowercase'xorriso : FAILURE : Not a known command:
> > '-allow-multidot'xorriso : FAILURE : Not a known command:
> > '-cache-inodes'xorriso : FAILURE : Not a known command: '-l'xorriso :
> > FAILURE : Not a known command: '-quiet'xorriso : FAILURE : Not a known
> > command: '-J'xorriso : FAILURE : Not a known command: '-r'xorriso :
> FAILURE
> > : Not a known command: '-V'xorriso : FAILURE : Not a known command:
> > 'config-2'xorriso : FAILURE : Not a known command:
> > '/tmp/configdrive2202287813434599114'xorriso : aborting : -abort_on
> > 'FAILURE' encountered 'FAILURE'].
> >
> > Has anyone seen this error before and know what it means or how to
> resolve
> > it?
> > My System VMs are in an Up and Running state with the Agents running as
> > well so that can't be it.
> >
> > Kind regards,
> >
> > Jeroen Kleijer
> >
>
>
> --
> Daan
>

Re: Unable to deploy VM instances

Posted by Daan Hoogland <da...@gmail.com>.
Jeroen,
Can you deploy other templates? The text seems like an error message that
ACS would not create but only pass on and looks like either coming from the
backend or the template.

On Sat, Sep 7, 2024 at 1:42 PM Jeroen Kleijer <je...@gmail.com>
wrote:

> Ls,
>
> I've installed ACS (4.19.0.2-1) several times already but as of yesterday
> I'm running into something I haven't seen before:
> I've created a zone, pod and cluster and added hosts. I created a guest
> network (L2 VLAN with ConfigDrive) and installed a Template. (Rocky Linux
> 9) This has worked numerous times before but now, when I try to spin up a
> new VM in my new setup, I'm hit with the following error message:
>
> Unable to orchestrate start VM instance
>
> {"id":10,"instanceName":"i-2-10-VM","type":"User","uuid":"0604b5e6-eb27-4d76-89c2-481d07683187"}
> due to [Unable to create iso file: i-2-10-VM.iso due to gexorriso 1.5.4 :
> RockRidge filesystem manipulator, libburnia project.xorriso : FAILURE : Not
> a known command: '-o'xorriso : FAILURE : Not a known command:
> '/tmp/configdrive2202287813434599114/i-2-10-VM.iso'xorriso : FAILURE : Not
> a known command: '-ldots'xorriso : FAILURE : Not a known command:
> '-allow-lowercase'xorriso : FAILURE : Not a known command:
> '-allow-multidot'xorriso : FAILURE : Not a known command:
> '-cache-inodes'xorriso : FAILURE : Not a known command: '-l'xorriso :
> FAILURE : Not a known command: '-quiet'xorriso : FAILURE : Not a known
> command: '-J'xorriso : FAILURE : Not a known command: '-r'xorriso : FAILURE
> : Not a known command: '-V'xorriso : FAILURE : Not a known command:
> 'config-2'xorriso : FAILURE : Not a known command:
> '/tmp/configdrive2202287813434599114'xorriso : aborting : -abort_on
> 'FAILURE' encountered 'FAILURE'].
>
> Has anyone seen this error before and know what it means or how to resolve
> it?
> My System VMs are in an Up and Running state with the Agents running as
> well so that can't be it.
>
> Kind regards,
>
> Jeroen Kleijer
>


-- 
Daan