Hello,

I saw in the HTML web page some informations that I think should not be there as they are. Can you delete them?

BR
Riwal

The Zurich public network name has been changed again to public-ext-net-01 according to jira ticket NODEM-194 instructions. (We had the same issue as Theofanis that we took the name agreed in the minutes of the Prague meeting for the previous issue, but this is not consistent with what we now see in the jira ticket).

Can you update please?

Dears,

we got some intressting issue on the Budapest node. We saw this in the log:
test_deploy_instance_with_new_network_and_check_metadata_service:
"
2015-12-01 12:03:38,987 UTC - TestCase - DEBUG - Received hostname: 'lannion2-testing-instance-meta-20151201115403'. Expected hostname: 'budapest2-testing-instance-snat-20151201120324'
2015-12-01 12:03:38,987 UTC - TestCase - DEBUG - Signal hostname received is not the expected one. Waiting for valid signal...
2015-12-01 12:04:37,488 UTC - TestCase - DEBUG - Received hostname: 'crete-testing-instance-meta-20151201120317'. Expected hostname: 'budapest2-testing-instance-snat-20151201120324'
2015-12-01 12:04:37,488 UTC - TestCase - DEBUG - Signal hostname received is not the expected one. Waiting for valid signal...
"

Why do we see 'crete' and 'lannion2' on the received side? Is this some configuration problem on our side, or in the keystone proxy?

Thanks,
Gergő

Please add Berlin2 for sanity check. Berlin can be removed, because it should not be used by the users anymore.

Please add Stockholm2.
We have no object storage and are using neutron on Icehouse.
Network names are the same as for Stockholm.
Stockholm can be removed as it is more or less obsolete regarding tests now.

Please remove temporarily the storage tests for Trento node.
We do not implemented yet.
Thanks

New external_network_name = "public-ext-net-01"
(Old external_network_name = "XIFIpublicACREO")

Dear Fernando,

we renamed our networks. Please change the sanity check configuration. The names was changed to:

mdvpnInternal -> node-int-net-02
publicInternal -> node-int-net-01
mdvpnRange -> federation-ext-net-01
publicRange -> public-ext-net-01

Thanks,
Gergő

Hi,

Our old environment will be switched off soon, so you can remove "Budapest" from the sanity tests.

Thank you!
Sandor

The network name in the Spain node has been renamed to "public-ext-net-01", so it should be changed from net8300 to the new name.

Dear All,

"Budapest2" is up and running since monday, based on IceHouse. Could you please add it to the sanity check?

We use the same network names as in the "Budapest" region.

Thank you in advance,
Best,
Sandor

In Trento we have 2 Public network.
The first network has no more Public IP. In order to avoiding error in the test, the script has to manage multiple public networks.

Thanks

Hello,

following my last mail, as we talked we changed default network name "net04_ext".

Our current network name:
federation-ext-net-01
public-ext-net-01
node-int-net-01

Could you change the name in the script for Sophia Antipolis node please?

Thank you.

Lannion2 is on air since monday 27/04. Could you please add it to the nodes that are tests every morning?

BR
rkerherve

The Neuropublic (PiraeusN) external network name has been changed to "public-ext-net-1". Please change accordingly so the test_allocate_ip test will not fail for PiraeusN region.

Please include the Sao Paulo node in the tests!!

Neuropublic external network name has been changed to public-ext-net-01 according to jira ticket NODEM-194 instructions. Please change accordingly.

Please change the public network in : public-ext-net-02

The internal network associated is : node-int-net-02

We need to change the network because the first network has no free Public IP.

Hello
Please change Poznan network to public-ext-net-01.

We see we have an error in one of the tests, most likely because the centralized test assumes that the name of our external network is net04_ext instead of public-ext-net-1. If you could change this I think we might be able to pass all test tomorrow.

Thanks,
Bruno.

We have observed some differences between the results of the centralized sanity tests and the manual tests (through the cloud portal).

• In particular, (maybe perchance) when we updated our floating nets to public-ext-net-01 , federation-ext-net-01 (instead public-ext-net-1 and federation-ext-net-1, respectively), after a NODEM jira request, we observed that the public/centralized sanity tests detects as error for out node the allocation of floating IPs ( ‘Sanity Test Output’ Error: FloatingIpPoolNotFound: Floating ip pool not found. (HTTP 404) (Request-ID: req-ffb39e9a-2679-44e6-9306-5f5165cef8ae) ).
• However, by performing manual testing everything works properly.
• Could you please check if the Sanity Test Suite for PiraeusU nod, needs any update after the floating networks name update? In the NODEM Jira Ticket, there was a comment that the network names are case sensitive. So potentially need somewhere in the scripts an update.
  Apologies in advance if I have understood something wrong!

Best Regards,
Dimitris Kelaidonis, on behalf of PiraeusU node

It would be good if the error reports had specific times associated with them - it would be good if you could log time at the start of the test as well as the time when you conclude the test fails. This info should be printed in the error log.

It would really help debugging - right now, the only time reference we have is the time at the top of http://fi-health.lab.fi-ware.eu/RegionSanityCheck/ which I guess is the time when all the tests end.

Thanks,
Seán.

It would be good if the notification email sent to the list pertaining to that node included the following info:

• a link to the fi-health page which we could just click on
• the results of the tests so we could see the test results from the email and not just get a notification that there has been a change

I guess this is pretty obvious, so you prob have it on the todo list in any case...this is just to maybe push it up the prio list ;-)

Following the Jira ticket NODEM-194 instructions we changed the networks names:

• node-int-net-01
• federation-ext-net-02
• public-ext-net-03

Please, update configuration as you can.

Berlin was the old Grizzly setup and is not used anymore. Therefore it can be removed from the list of nodes to check the health.

The default floating ip pool for Zurich2 is public-ext-net-01 when the sanity check is executed we noticed that this name is changed to public-ext-net-03 (as shown below) leading to test failure for some unittests.

Logs from Nova:
2016-04-05 12:32:56.034 4796 DEBUG nova.api.openstack.wsgi [REDACTED] Action: 'create', calling method: <bound method FloatingIPController.create of <nova.api.openstack.compute.contrib.floating_ips.FloatingIPController object at 0x7f1e5f11a250>>, body: {"pool": "public-ext-net-03"} _process_stack /usr/lib/python2.7/dist-packages/nova/api/openstack/wsgi.py:780

Dear Fernando,

We saw the following errors in the sanity check that may be related to the script and not to the node:

1. Key pair 'testing_keypair06' already exists. (HTTP 409)
2. Quota exceeded for instances: Requested 1, but already used 3 of 3 instances (HTTP 413)
3. Key pair 'testing_keypair04' already exists. (HTTP 409)

For me it seems that some cleanup scripts don't work properly. Since the keypairs should be deleted before testing the creation, etc...
Could you please have a look at it?

The issue is related to Budapest node...

Best,
Sandor

Please replace the Karlskrona with Karlskrona2 region.

When running the fiware-region-sanity-tests, the timestamp variable in test_report_template.html does not replace with the timestamp correctly. The resulting html file is empty where the timestamp is to be found.
Output is; (tests_results.html) (adapted to not mess with html formatting too much)
...[snip]..
h1 FIWARE REGIONS - SANITY CHECK | /h1
...[snip]..

Añadir tests automáticos relacionados con Object Storage en México

Dear Developers,

The sanity check of Budapest node seems stucked in "in progress" state. Could you please check and fix the issue!

Thank you in advance!
Sandor

Update the network name.
public-ext-net-01

Please modify the network
from: "Berlin": "ext-net-public",
to: "Berlin": "public-ext-net-01",
in the settings.json

Many thanks

Please add Zurich2 region.
We have object-storage service but it shouldn't be included in the sanity check yet as there is an issue with keystone and the cloud portal for this service. We will create another issue to enable it as soon as this is fixed.

The public network name remains the same - public-ext-net-01.