Details
-
Type: extRequest
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-LAB-HELP
-
Labels:None
-
Sender Email:
-
HD-Node:Spain
Description
Dear friends from FIWARE,
My instance in FI LAB unexpectedly appeared today as SHUTDOWN (state:
SHUTOFF , power state: SHUTDOWN).
Whenever I try to reboot the instance via the Actions menu I get the
following message:
{"conflictingRequest": {"message": "Cannot 'reboot' while instance is in
vm_state stopped", "code": 409}}
The result: State and power state remain the same and instance
is inaccessible.
My instance's background info:
- Region: Spain2
- Every time Spain2 node recovers from failures (as informed by FIWARE
sanity check portal) I experience similar problems related to
inaccessibility of my instance. Last time I solved the issue by releasing
its associated floating ip, then requesting a new one and associating it
back to my instance. Nonetheless, I'm pretty sure this is not the standard
procedure to follow in order to wake an instance up and having it up and
running.
I kindly ask you to help me get my instance running.
Best regards.
Sergio
_______________________________________________
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: Sergio G-Miranda <planetmediasergiomiranda@gmail.com>]
Dear friends from FIWARE,
My instance is ACTIVE and running in FILAB Web interface. I can even
connect via web VNC.
Unfortunately I cannot connect via SSH. I tried releasing its associated
floating ip, then requesting a new one and associating it
back to my instance. But no luck.
I kindly ask you to help me get successful SSH connection to my instance.
Regards.
On Wed, Jun 10, 2015 at 12:47 PM, Help-Desk <jira-help-desk@fi-ware.org>