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

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

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.
------------------------------

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

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

Thank you Jan for the fast reply!

Best regards,
Uwe

Dear Uwe,

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.

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

Dear Uwe,
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.

With kind regards,
Jan

[1] http://jira.fi-ware.org/browse/HELP-1923

URL: https://rt4.cesnet.cz/rt/Ticket/Display.html?id=102970

Vas pozadavek byl podle nasich zaznamu vyrizen. Pokud mate nejake dalsi
dotazy, nebo nejasnosti, odpovezte prosim na tuto zpravu.

According to our records, your request has been resolved. If you have any
further questions or concerns, please respond to this message.

Dear node helpdesks,

I received below help request which affects several nodes: Budapest, Prague, Berlin, Zurich, Crete and Lannion, please take a look below, and also check the attached original message.

It refers to Jira ticket http://jira.fi-ware.org/browse/HELP-1916
I send you that by email because I cannot assign a ticket to multiple nodes.

Please decide yourself if you want to answer directly to the user or provide me the answer if you want me to send the feedback to the user. Make sure you always cc fiware-lab-help@lists.fi-ware.org<fiware-lab-help@lists.fi-ware.org> if you answer directly to the user.

Best regards,
Uwe

From: Vuk Banjanin vuk.banjanin@codecentric.de
Sent: 14 January 2015 10:30
To: Uwe Herzog
Subject: Re: [Fiware-lab-help] FI-Lab Assistance

Thank you for the fast reply. The regions in question are Budapest, Prague, Berlin, Zurich, and Crete, and i was able to create in image instance on Lannion, 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. I've had success with the Poznan region, where everything works fine. All the mentioned regions (except Poznan) returned errors when trying to create instances of Blueprints. When i tried to create an instance of an image on the mentioned regions, i also got an error, but i think this was due to the reason that no floating IP address could be associated with an image.
I have another question. Is there a way to run an instance on the virtual machine locally, for testing purposes? Thank you in advance.

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