[Fiware-lab-help] fault symptoms with the fi-lab portal - reason unclear - please confirm

[Bochow, Bernd]

Dear All,

since yesterday around 14:00 CEST I noticed a strange behavior of the cloud portal that I was not able to track down.

I would like to ask if anybody of you has observed similar symptoms as described below.

Many Thanks for your help!
Any hint would be highly appreciated since I cannot use the portal now any more.

=======

I was creating routers and networks for an experiment on the Berlin node under my personal tenant 3014.

At some point around that time the portal started to behave strangely.
I observed the following:

- my key-pairs and instances vanished and the flavors I could select from switched to different ones.
- the floating-IP ranges I could select from changed and I could instantiate an image any more.
(now got the error that I would need admin rights to launch an image)

At this point in time I could see that I seemingly was not able to change anymore between regions.
Regardless which region I selected from the drop-down list I ended up on some remote node (although the portal displayed the region selected).
I could not identify the region active but it is the one offering the floating IPs from "net8300" and the flavors m1.tiny, m1.small, m2.largerdisk.
The usual log on/off, refresh and browser cache clear did not help, so I assume it was not a local problem.

Further trying to track down the problem I noticed the following.

- I was still able to see my routers and networks.
- I verified via the CLI that these have been instantiated at the Berlin node correctly.
- I could modify these and set the default gateway on the router via the portal (I could select here from the Berlin node networks provided).
- When trying to delete the networks and routers I failed and got an error message
{"QuantumError": "Unable to complete operation on network d4b6d33a-4cd8-41e2-8dc9-47024ccf1858. There are one or more ports still in use on the network."}
- via CLI I could identify that there was a port allocated but not shown via the portal. This port was created before the point in time when the problems started (along with the corresponding network/router and a vm instance that also vanished as noted before).
- via CLI I could remove this port and then succeeded in removing the network through the cloud portal.


Best Regards, Bernd

============
Bernd Bochow
Next Generation Network Infrastructures
Fraunhofer Institute for Open Communication Systems (FOKUS)
Kaiserin-Augusta-Allee 31, D-10589 Berlin
e-mail: bernd.bochow at fokus.fraunhofer.de<mailto:bernd.bochow at fokus.fraunhofer.de>, bernd.bochow at ieee.org<mailto:bernd.bochow at ieee.org>
phone:  +49 30 3463-7238
fax:    +49 30 3463-997238

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-lab-help/attachments/20140625/b343b3dc/attachment.html>