[HELP-1916] FIWARE.Request.Lab.FI-Lab Assistance. - JIRA

Details

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

Sender Email:
vuk.banjanin@codecentric.de

Description

Hello,
I'm a member of a small team of developers interested in using your APIs.
1) I'm currently trying to set up an instance of a VM in Fiware Lab, for
testing purposes, and every time I try to create an instance of a blueprint
I "get" a instance with the status set to error. I keep getting this error
for both types of templates, new templates and templates cloned from the
Catalog. The error i keep getting is:
Status: ERROR
Error: Infrastructure error Error in parse response after deploy the
VM***************

2)I've managed to create a "working instace of a ubuntu server 12.04. When
i try to attach a new floating point Ip i can only create an
"FederationNode-ExternalNetwork" one, and i can not create a "ext-net
adress". The FederationNode-ExternalNetwork adress can not be associated
with the working Vm ( result when I try to associate it: {"badRequest":
{"message": "Error. Unable to associate floating ip", "code": 400}} )

3)I can connect to my server from the Connection -> View Display option, i
get to the login screen of the server instance, but i can't find the
username and password for the instance. Is there a default one, or can i
set it somewhere?

I've tried this on a couple of Regions, and the Lannion region is the only
one where i was able to create an instance that says the image is running.
–
Srdačan pozdrav / Best regards,
Vuk Banjanin
codecentric d.o.o.
Bulevar oslobodjenja 127/XIII, 21000 Novi Sad,Srbija
Tel: + 381 (64) 2617764 <%2B%20381%2021%20539786>
Mob: + 381 (64) 2617764 <%2B%20381%20%2863%29%208445468>
www.codecentric.rs
www.codecentric.de
codecentric AG | Merscheider Straße 1 | 42699 Solingen | Deutschland
www.codecentric.de | blog.codecentric.de | www.meettheexperts.de |
www.more4fi.de

Sitz der Gesellschaft: Düsseldorf | HRB 63043 | Amtsgericht Düsseldorf
Vorstand: Michael Hochgürtel . Mirko Novakovic . Rainer Vehns
Aufsichtsrat: Patric Fedlmeier (Vorsitzender) . Klaus Jäger . Jürgen Schütz

Diese E-Mail einschließlich evtl. beigefügter Dateien enthält vertrauliche
und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige
Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie
bitte sofort den Absender und löschen Sie diese E-Mail und evtl.
beigefügter Dateien umgehend. Das unerlaubte Kopieren, Nutzen oder Öffnen
evtl. beigefügter Dateien sowie die unbefugte Weitergabe dieser E-Mail ist
nicht gestattet.

_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help

[Created via e-mail received from: Vuk Banjanin <vuk.banjanin@codecentric.de>]

Options
- Sort By Name
- Sort By Date
- Ascending
- Descending
- Download All

Attachments

[Fiware-lab-help] FI-Lab Assistance

14/Jan/15 2:35 PM

13 kB

Uwe Herzog

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Uwe Herzog (Inactive) added a comment - 13/Jan/15 4:45 PM

Hi Vuk,

from your email it reads that this might be an issue for several regions except Lannion for which you say things work fine.

Could you let me know which specific regions you have tried where it did not work, so that I can forward your request accordingly?

Best regards,
Uwe

Show

Uwe Herzog (Inactive) added a comment - 13/Jan/15 4:45 PM Hi Vuk, from your email it reads that this might be an issue for several regions except Lannion for which you say things work fine. Could you let me know which specific regions you have tried where it did not work, so that I can forward your request accordingly? Best regards, Uwe

5 older comments

Hide

Permalink

FW External User added a comment - 14/Jan/15 4:45 PM - edited

Hi Uwe,

If I understand it right, everything worked on Lannion region, so no action from our side. Am I right or I’ve misunderstood the comment?

Best regards

Sergio

Show

FW External User added a comment - 14/Jan/15 4:45 PM - edited Hi Uwe, If I understand it right, everything worked on Lannion region, so no action from our side. Am I right or I’ve misunderstood the comment? Best regards Sergio

Hide

Permalink

Uwe Herzog (Inactive) added a comment - 14/Jan/15 4:55 PM

Hi Sergio,

for Lannion it worked partly:
"i was able to create in image instance on Lannion" (so this worked fine)
and here comes what did not work:
"but i wasn't able to connect it to a floating Ip, i could only connect to it via the "view display" function in the browser"

Is that the thing that users need to contact you to get a public IP address?

Best regards,
Uwe

Show

Uwe Herzog (Inactive) added a comment - 14/Jan/15 4:55 PM Hi Sergio, for Lannion it worked partly: "i was able to create in image instance on Lannion" (so this worked fine) and here comes what did not work: "but i wasn't able to connect it to a floating Ip, i could only connect to it via the "view display" function in the browser" Is that the thing that users need to contact you to get a public IP address? Best regards, Uwe

Hide

Permalink

Uwe Herzog (Inactive) added a comment - 14/Jan/15 5:43 PM

Hi Vuk,

please find below the responses from two of the nodes. I saw that Lannion node already contacted you directly. I hope that these answers will help you. If the other nodes will still reply I’ll forward the answers to you.

I’ll close this ticket now. If you need further help don’t hesitate to send an email to helpdesk again.

Best regards,
Uwe

--------------------------------
Info from Prague node:

creating VMs in Prague works fine according to our tests. There is the long-standing inability to allocate public IPv4 address, but that's expected because they are all allocated to tenants or VMs most of the time. It's unfortunate, but it's a direct result of a policy decision which was to allow tenants to allocate up to one IPv4 address on a self-service basis, with no prior justification.

The user appears to have troubles deploying blueprints form the Cloud Portal. We do not have access to error logs from the Cloud Portal, and as such we cannot really help troubleshoot problems that users might have with it. To the best of our knowledge, API calls to our OpenStack controller result in VMs being created and deployed, so the problem is apparently elsewhere. I'd also like to point out that I filed a ticket [1] about the central Keystone being unreachable earlier today; that might be related to the issue at hand.
------------------------------
Info from Budapest node:
In the Budapest node there were some issues with nfs on Monday (as reported to the help desk), and we also noticed that there were no free IPs in the shared network, resulting in error during the instance creation. Both issues have been solved by now. So, Budapest node is back again.
------------------------------

Show

Uwe Herzog (Inactive) added a comment - 14/Jan/15 5:43 PM Hi Vuk, please find below the responses from two of the nodes. I saw that Lannion node already contacted you directly. I hope that these answers will help you. If the other nodes will still reply I’ll forward the answers to you. I’ll close this ticket now. If you need further help don’t hesitate to send an email to helpdesk again. Best regards, Uwe -------------------------------- Info from Prague node: creating VMs in Prague works fine according to our tests. There is the long-standing inability to allocate public IPv4 address, but that's expected because they are all allocated to tenants or VMs most of the time. It's unfortunate, but it's a direct result of a policy decision which was to allow tenants to allocate up to one IPv4 address on a self-service basis, with no prior justification. The user appears to have troubles deploying blueprints form the Cloud Portal. We do not have access to error logs from the Cloud Portal, and as such we cannot really help troubleshoot problems that users might have with it. To the best of our knowledge, API calls to our OpenStack controller result in VMs being created and deployed, so the problem is apparently elsewhere. I'd also like to point out that I filed a ticket [1] about the central Keystone being unreachable earlier today; that might be related to the issue at hand. ------------------------------ Info from Budapest node: In the Budapest node there were some issues with nfs on Monday (as reported to the help desk), and we also noticed that there were no free IPs in the shared network, resulting in error during the instance creation. Both issues have been solved by now. So, Budapest node is back again. ------------------------------

Hide

Permalink

FW External User added a comment - 15/Jan/15 9:58 AM - edited

Dear Uwe,

Concerning the node of Crete, I don't see any problem in creating an
instance from an image.
If there is an error, it is usually a problem of exceeding quotas
(number of VCPUs, instances, etc).
On the other hand, creating an instance from a Blueprint becomes to an
an ERROR which does not become from the environment of Crete (at least I
don't see anything in our logs) and every time it is something different.
For example, the last time I tried to create an instance, I got the
following ERROR message:
"Error: Error installing a product.
Description:com.telefonica.euro_iaas.paasmanager.exception.ProductInstallatorException:
Error installing product apache2-4.0 Error invokg SDC to Install
Productapache2-4.0 4.0 HTTP 500 Internal Server Error"

Best Regards,

Spyros.

_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help

Show

FW External User added a comment - 15/Jan/15 9:58 AM - edited Dear Uwe, Concerning the node of Crete, I don't see any problem in creating an instance from an image. If there is an error, it is usually a problem of exceeding quotas (number of VCPUs, instances, etc). On the other hand, creating an instance from a Blueprint becomes to an an ERROR which does not become from the environment of Crete (at least I don't see anything in our logs) and every time it is something different. For example, the last time I tried to create an instance, I got the following ERROR message: "Error: Error installing a product. Description:com.telefonica.euro_iaas.paasmanager.exception.ProductInstallatorException: Error installing product apache2-4.0 Error invokg SDC to Install Productapache2-4.0 4.0 HTTP 500 Internal Server Error" Best Regards, Spyros. _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help@lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-lab-help

Hide

Permalink

FW External User added a comment - 15/Jan/15 10:02 AM

Hi Uwe,

From the ZH side, the problem is with the metadata service - we have been
looking into how
to fix it, but we concluded that the best approach is to move to icehouse
asap and we plan on
doing this next week.

BR,
Seán.

_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help

Show

FW External User added a comment - 15/Jan/15 10:02 AM Hi Uwe, From the ZH side, the problem is with the metadata service - we have been looking into how to fix it, but we concluded that the best approach is to move to icehouse asap and we plan on doing this next week. BR, Seán. _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help@lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-lab-help

People

Assignee:

Uwe Herzog (Inactive)

Reporter:

FW External User

Votes:

0 Vote for this issue

Watchers:

3 Start watching this issue

Dates

Created:

13/Jan/15 3:23 PM

Updated:

27/May/21 10:58 AM

Resolved:

14/Jan/15 5:42 PM

Agile

View on Board