Hi Fernando, On SophiaAntipolis node, the following sanity check tests are red : * test_deploy_instance_with_new_network <javascript:openFailureDetailsInNewWindow('#tests.regions.test_sophiaantipolis.TestSuite:test_deploy_instance_with_new_network');> * test_deploy_instance_with_new_network_and_all_params <javascript:openFailureDetailsInNewWindow('#tests.regions.test_sophiaantipolis.TestSuite:test_deploy_instance_with_new_network_and_all_params');> * test_deploy_instance_with_new_network_and_associate_public_ip <javascript:openFailureDetailsInNewWindow('#tests.regions.test_sophiaantipolis.TestSuite:test_deploy_instance_with_new_network_and_associate_public_ip');> * test_deploy_instance_with_new_network_and_check_metadata_service <javascript:openFailureDetailsInNewWindow('#tests.regions.test_sophiaantipolis.TestSuite:test_deploy_instance_with_new_network_and_check_metadata_service');> * test_deploy_instance_with_new_network_and_e2e_connection_using_public_ip <javascript:openFailureDetailsInNewWindow('#tests.regions.test_sophiaantipolis.TestSuite:test_deploy_instance_with_new_network_and_e2e_connection_using_public_ip');> * test_deploy_instance_with_new_network_and_e2e_snat_connection <javascript:openFailureDetailsInNewWindow('#tests.regions.test_sophiaantipolis.TestSuite:test_deploy_instance_with_new_network_and_e2e_snat_connection');> * test_deploy_instance_with_new_network_and_keypair <javascript:openFailureDetailsInNewWindow('#tests.regions.test_sophiaantipolis.TestSuite:test_deploy_instance_with_new_network_and_keypair');> * test_deploy_instance_with_new_network_and_metadata <javascript:openFailureDetailsInNewWindow('#tests.regions.test_sophiaantipolis.TestSuite:test_deploy_instance_with_new_network_and_metadata');> * test_deploy_instance_with_new_network_and_sec_group <javascript:openFailureDetailsInNewWindow('#tests.regions.test_sophiaantipolis.TestSuite:test_deploy_instance_with_new_network_and_sec_group');> * test_deploy_instance_with_shared_network_and_e2e_connection_using_public_ip <javascript:openFailureDetailsInNewWindow('#tests.regions.test_sophiaantipolis.TestSuite:test_deploy_instance_with_shared_network_and_e2e_connection_using_public_ip');> * test_deploy_instance_with_shared_network_and_e2e_snat_connection <javascript:openFailureDetailsInNewWindow('#tests.regions.test_sophiaantipolis.TestSuite:test_deploy_instance_with_shared_network_and_e2e_snat_connection');> Most of them are failing for the same reason found into the Debug messages "Not enough resources to launch new instance: Quota exceeded for cores: Requested 1, but already used 6 of 6 cores" In the infographic Fiware Lab view the sanity check status is red or grey for all the nodes excepted Spain. Philippe Le 04/05/2016 à 09:59, Cristian Cristelotti a écrit : > Hi Fernando, > > on the status page all nodes are red or grey on the sanity column, but on the sanity tests we are green. > > Cristian > > ----- Messaggio originale ----- > Da: "FERNANDO LOPEZ AGUILAR"<fernando.lopezaguilar at telefonica.com> > A: "Pietropaolo Alfonso"<Alfonso.Pietropaolo at eng.it> > Cc:fiware-lab-federation-nodes at lists.fiware.org > Inviato: Martedì, 3 maggio 2016 17:08:28 > Oggetto: [Fiware-lab-federation-nodes] New release of FI-Health tool > > > > > > > Dear all, > > > We have updated the new version of the Sanity Checks tool (Release 5.3.1), the new functionalities are the following: > > > > FIHealth Dashboard v1.7.0: > > > * Progress status of sanity checks retrieved from Jenkins > > > FIHealth Sanity Checks v1.7.0: > > > * Add feature to move old {region}_results.txt to a directory > * Add feature to update Jenkins jobs on demand when "setup" job is executed > * Add transaction id in log messages to track requests throughout a sanity check > * Change HTTP framework by CherryPy to solve errors with PhoneHome server > > Besides, we have updated the regions list > > > Best regards, > Fernando.. > > > > > > 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-federation-nodes mailing list > Fiware-lab-federation-nodes at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-lab-federation-nodes > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-lab-federation-nodes/attachments/20160504/1cad6fe0/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy