Details
-
Type: extRequest
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-LAB-HELP
-
Labels:None
-
HD-Node:Budapest
Description
Trying to create a new storage volume of 1 GB in the budapest region does
not seem to work.
The browser Console give this error:
Failed to load resource: the server responded with a status of 503 (Service
Unavailable)
https://cloud.lab.fi-ware.org/Budapest/paas/rest/catalog/org/FIWARE/environment
Browser : Chrome Version 38.0.2125.104
OS : Linux version 3.13.0-37-generic (buildd@roseapple) (gcc version 4.8.2
(Ubuntu 4.8.2-19ubuntu1) ) #64-Ubuntu SMP Mon Sep 22 21:30:01 UTC 2014
–
_____________________________
Abbas AHMAD
Ingénieur Informatique - Génie Logiciel
Université de Franche-Comté, Besançon
abbasaliwehbeahmad@gmail.com
+33 (0)6.47.56.85.94
_______________________________________________
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: Abbas Ahmad <abbasaliwehbeahmad@gmail.com>]
Activity
Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
---|---|---|---|---|---|---|---|---|---|
|
99d 37m | 1 | Uwe Herzog (Inactive) | 12/Feb/15 12:26 PM | |||||
|
5s | 1 | Uwe Herzog (Inactive) | 12/Feb/15 12:27 PM |
Fix Version/s | 2021 [ 12600 ] |
Summary | [Fiware-lab-help] Unable to create new Storage Volume : Budapest region | FIWARE.Request.Lab.Budapest.Unable to create new Storage Volume : Budapest region |
HD-Node | Budapest [ 10911 ] |
Resolution | Done [ 10000 ] | |
Status | In Progress [ 3 ] | Closed [ 6 ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Component/s | FIWARE-LAB-HELP [ 10279 ] |
Workflow | FW eRequest Workflow [ 18577 ] | FW extRequest Workflow-II [ 20293 ] |
Issue Type | eRequest [ 10101 ] | extRequest [ 10104 ] |
FI-WARE Environment | FI-LAB [ 10100 ] |
Reporter | FW External User [ fw.external.urser ] | Abbas Ahmad [ abbas.ahmad ] |
Assignee | Budapest Node Helpdesk [ wigner ] |
Link | This issue is cloned by HELP-1040 [ HELP-1040 ] |
Field | Original Value | New Value |
---|---|---|
Description |
Trying to create a new storage volume of 1 GB in the budapest region does not seem to work. The browser Console give this error: Failed to load resource: the server responded with a status of 503 (Service Unavailable) https://cloud.lab.fi-ware.org/Budapest/paas/rest/catalog/org/FIWARE/environment Browser : Chrome Version 38.0.2125.104 OS : Linux version 3.13.0-37-generic (buildd@roseapple) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #64-Ubuntu SMP Mon Sep 22 21:30:01 UTC 2014 -- _____________________________ *Abbas AHMAD* Etudiant en Master 2 Informatique - Génie Logiciel Université de Franche-Comté, Besançon abbasaliwehbeahmad@gmail.com +33 (0)6.47.56.85.94 _______________________________________________ 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: Abbas Ahmad <abbasaliwehbeahmad@gmail.com>] |
Trying to create a new storage volume of 1 GB in the budapest region does not seem to work. The browser Console give this error: Failed to load resource: the server responded with a status of 503 (Service Unavailable) https://cloud.lab.fi-ware.org/Budapest/paas/rest/catalog/org/FIWARE/environment Browser : Chrome Version 38.0.2125.104 OS : Linux version 3.13.0-37-generic (buildd@roseapple) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #64-Ubuntu SMP Mon Sep 22 21:30:01 UTC 2014 -- _____________________________ *Abbas AHMAD* Ingénieur Informatique - Génie Logiciel Université de Franche-Comté, Besançon abbasaliwehbeahmad@gmail.com +33 (0)6.47.56.85.94 _______________________________________________ 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: Abbas Ahmad <abbasaliwehbeahmad@gmail.com>] |
The volume in Budapest is working properly. We checked the logs and there is no sign of the above error. I cannot reproduce the error by creating volumes. However, we realized that sometimes the cloud portal is not working properly: the portal do not realize that the ticket has already expired and try using that, resulting in unexpected behaviour.