To FIWARE Tech Support:

I received notice from FIWARE this morning that the issue has been resolved supposedly but I'm still getting the same exact error.

I have also seen the same error reported by another user in your bug report forum http://jira.fiware.org/browse/HELP-5821 two weeks ago, and supposedly it was resolved a few days ago as well, but it is still happening to me.

Please let me know when I can try testing again or if there is another node that I can try instead.

Thanks,
Dan

The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.

From: Ziembienski, Dan
Sent: Thursday, February 18, 2016 4:29 PM
To: 'fiware-lab-help@lists.fiware.org' <fiware-lab-help@lists.fiware.org>
Subject: RE: FIWARE Lab Assistance

Hello again,

As an update to the prior email, I realized the keypair was not specified for the blueprint instance launch, and I suspected that maybe that caused the obscure nondescript error. So I assigned a keypair to a new blueprint, but then got a different error:

Info: Connected to project philipsfiware cloud (ID 8ca9e20c9197468da44cfc5c7b4dfe58)
Success: Blueprint Instance abc001 status.

Description: Create environment abc001

Status: ERROR

Error: Infrastructure error Error interacting with OpenStack Error in parse response after deploy the VM 43ba38c5-7ac3-4f88-b815-582a8cb5c035 {"server": {"status": "ERROR", "updated": "2016-02-18T20:29:44Z", "hostId": "2485dc15a94a35f4bc0af79b3a1575355ee505e4f79a3b4b1f1aa606", "addresses": {}, "links": [

,

], "key_name": "keypair20160218", "image": {"id": "3a39252a-ec91-4b7e-a33c-a49f9791712c", "links": [

]}, "OS-EXT-STS:task_state": "spawning", "OS-EXT-STS:vm_state": "error", "OS-SRV-USG:launched_at": null, "flavor": {"id": "1", "links": [{"href": "http://130.206.112.3:8774/8ca9e20c9197468da44cfc5c7b4dfe58/flavors/1", "rel"
Thanks,
Dan

From: Ziembienski, Dan
Sent: Thursday, February 18, 2016 2:39 PM
To: 'fiware-lab-help@lists.fiware.org' <fiware-lab-help@lists.fiware.org<fiware-lab-help@lists.fiware.org>>
Subject: FIWARE Lab Assistance

Hi,

I'm evaluating the FIWARE platform. I've watched many of the videos from the FIWARE summit last year that you have posted on youtube.com; and I understand the architecture; and I have created a FIWARE Labs account of username "philipsfiware" under my email dan.ziembienski@fiware.com<dan.ziembienski@fiware.com>. I've tried following some of your video tutorials for creating blueprints and launching blueprint instances. However, I always get a nondescript error when I try to launch any instance:

Error: undefined. Cause: 400 Error info<https://cloud.lab.fiware.org/>

Success: Blueprint Instance test20160218B status.

Description: Create environment test20160218B

Status: ERROR

Error: Infrastructure error Error interacting with OpenStack Error creating server: String index out of range: -10

Also, I tried launching computer instances of an ubuntu14 image, and specified a keypair that I generated, and supposedly it launched. But then I get the following nondescript error when I try to assign a floating IP to the computer instance so that I can try to access it from SSH externally:

undefined. Cause: 400 Error
{"badRequest": {"message": "No nw_info cache associated with instance", "code": 400}}

Any help would be appreciated.

Thanks,
Dan Ziembienski

The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.

Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: "Ziembienski, Dan" <Dan.Ziembienski@philips.com>]