[HELP-1722] FIWARE.Request.Lab.Spain.Problems with the launch of eidas-sbc-img - JIRA

Details

Type: extRequest
Status: Closed
Priority: Major
Resolution: Done
Fix Version/s: Sprint 4.1.3
Component/s: FIWARE-LAB-HELP
Labels:
None

HD-Node:
Spain

Description

http://jira.fi-ware.org/browse/HELP-1344

Dear Gioacchino,

We've run out of resources in the Spanish node, I'm afraid you won't be
able to launch that image there.

Best regards,
José Ignacio.

________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help

Activity

Hide

Permalink

Federico Michele Facca added a comment - 17/Dec/14 12:38 AM

Dear Gioacchino,
you can use other nodes, but I believe that the image as issues. I
managed to launch the vm with any problem (no error), but when i
opened the log of the vm i find:

mount: you must specify the filesystem type
mount: you must specify the filesystem type
mount: you must specify the filesystem type
mount: you must specify the filesystem type
mount: you must specify the filesystem type
mount: you must specify the filesystem type
mount: you must specify the filesystem type
mount: you must specify the filesystem type
mount: you must specify the filesystem type
mount: you must specify the filesystem type
mount: you must specify the filesystem type
mount: you must specify the filesystem type
mount: you must specify the filesystem type
mount: you must specify the filesystem type
mount: you must specify the filesystem type
mount: you must specify the filesystem type

dracut Warning: Boot has failed. To debug this issue add "rdshell" to
the kernel command line.

dracut Warning: Signal caught!

dracut Warning: Boot has failed. To debug this issue add "rdshell" to
the kernel command line.
Kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: init Not tainted 2.6.32-431.29.2.el6.x86_64 #1
Call Trace:
[] ? panic+0xa7/0x16f
[] ? do_exit+0x862/0x870
[] ? fput+0x25/0x30
[] ? do_group_exit+0x58/0xd0
[] ? sys_exit_group+0x17/0x20
[] ? system_call_fastpath+0x16/0x1b

in case you wanna try yourself, here is the steps to launch vm in
wateford (that use neutron network):
1. select the network pane and create a network including a subnet
(e.g. 192.168.12.0/24)
2. select the router pane and create a router
3. select the created router and set the default gateway
(XIFI-public-WIT-00) - unfortunately a bug in the portal will refresh
the whole app
4. click on the created router and select the interface pane; add as
interface the subnet of your network
5. click on security pane, select keypar panel, create a keypar
6. select floating ip panel, and allocate a public ip to the project
7. click on image pane, select iotbroker and click launch: settings
flavour m1, the keypair created, and the network create. (wait the vm
to be active)
8. click on the secutiry panel, select the floating IPs, and attach
the reserved IP to your vm

best,
federico

On Tue, Dec 16, 2014 at 9:38 PM, JOSE IGNACIO CARRETERO GUARDE

–
Dr. Federico M. Facca

CREATE-NET
Via alla Cascata 56/D
38123 Povo Trento (Italy)

T +39 0461 408400 (1669)
F +39 0461 421157
M +39 334 6049758
E federico.facca@create-net.org
W www.create-net.org
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help

Show

Federico Michele Facca added a comment - 17/Dec/14 12:38 AM Dear Gioacchino, you can use other nodes, but I believe that the image as issues. I managed to launch the vm with any problem (no error), but when i opened the log of the vm i find: mount: you must specify the filesystem type mount: you must specify the filesystem type mount: you must specify the filesystem type mount: you must specify the filesystem type mount: you must specify the filesystem type mount: you must specify the filesystem type mount: you must specify the filesystem type mount: you must specify the filesystem type mount: you must specify the filesystem type mount: you must specify the filesystem type mount: you must specify the filesystem type mount: you must specify the filesystem type mount: you must specify the filesystem type mount: you must specify the filesystem type mount: you must specify the filesystem type mount: you must specify the filesystem type dracut Warning: Boot has failed. To debug this issue add "rdshell" to the kernel command line. dracut Warning: Signal caught! dracut Warning: Boot has failed. To debug this issue add "rdshell" to the kernel command line. Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: init Not tainted 2.6.32-431.29.2.el6.x86_64 #1 Call Trace: [] ? panic+0xa7/0x16f [] ? do_exit+0x862/0x870 [] ? fput+0x25/0x30 [] ? do_group_exit+0x58/0xd0 [] ? sys_exit_group+0x17/0x20 [] ? system_call_fastpath+0x16/0x1b in case you wanna try yourself, here is the steps to launch vm in wateford (that use neutron network): 1. select the network pane and create a network including a subnet (e.g. 192.168.12.0/24) 2. select the router pane and create a router 3. select the created router and set the default gateway (XIFI-public-WIT-00) - unfortunately a bug in the portal will refresh the whole app 4. click on the created router and select the interface pane; add as interface the subnet of your network 5. click on security pane, select keypar panel, create a keypar 6. select floating ip panel, and allocate a public ip to the project 7. click on image pane, select iotbroker and click launch: settings flavour m1, the keypair created, and the network create. (wait the vm to be active) 8. click on the secutiry panel, select the floating IPs, and attach the reserved IP to your vm best, federico On Tue, Dec 16, 2014 at 9:38 PM, JOSE IGNACIO CARRETERO GUARDE – Dr. Federico M. Facca CREATE-NET Via alla Cascata 56/D 38123 Povo Trento (Italy) T +39 0461 408400 (1669) F +39 0461 421157 M +39 334 6049758 E federico.facca@create-net.org W www.create-net.org _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help@lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-lab-help

FIWARE.Request.Lab.Spain.Problems with the launch of eidas-sbc-img

Details

Description

Activity

People

Dates

Agile