Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-2242

FIWARE.Request.Lab.Gent.VM keep on "deleting" (ERROR status) and I cannot delete it

    Details

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

      Description

      Hi!

      As you can see in the report http://fi-health.lab.fi-ware.eu/RegionSanityCheck,
      some of the Gent sanity checks are failing due to this error:

      Quota exceeded for ram: Requested 2048, but already used 2048 of 3072 ram (HTTP 413)
      

      I can see that there is a VM with "deleting" status in the Tenant used for launching that test cases and I cannot delete it.

      • User: e.cloud10
      • TenantId: 00000000000000000000000000011233

      Could you please take a look to that VM?

      • Name: testing_instance_06
      • ID: d2b2b82b-9f8d-4908-aa61-756bfefd86f4
      • Status: ERROR
      • Image Name: CentOS-6.3init

      Thanks!

      BR,
      Javier.

        Activity

        Hide
        Vicent Vicent Borja Torres (Inactive) added a comment -

        We will check it and report with more details.

        Show
        Vicent Vicent Borja Torres (Inactive) added a comment - We will check it and report with more details.
        Hide
        Vicent Vicent Borja Torres (Inactive) added a comment - - edited

        VM was deleted from compute but the database was not ware of it. Traced the messages until an error exception, that seems database never received delete confirmation. As follows:

        2015-03-02 10:41:21.598 AUDIT nova.compute.manager [req-c646a76b-084d-4c17-8f0e-43100dc8c9f1 e-dot-cloud10 00000000000000000000000000011233] [instance: d2b2b82b-9f8d-4908-aa61-756bfefd86f4] Terminating instance
        2015-03-02 10:41:22.924 ERROR nova.openstack.common.rpc.amqp [req-c646a76b-084d-4c17-8f0e-43100dc8c9f1 e-dot-cloud10 00000000000000000000000000011233] Exception during message handling

        RabbitMQ crashes and can miss messages, while the service is auto-recovering.

        Problem solved, restoring database manually.

        Show
        Vicent Vicent Borja Torres (Inactive) added a comment - - edited VM was deleted from compute but the database was not ware of it. Traced the messages until an error exception, that seems database never received delete confirmation. As follows: 2015-03-02 10:41:21.598 AUDIT nova.compute.manager [req-c646a76b-084d-4c17-8f0e-43100dc8c9f1 e-dot-cloud10 00000000000000000000000000011233] [instance: d2b2b82b-9f8d-4908-aa61-756bfefd86f4] Terminating instance 2015-03-02 10:41:22.924 ERROR nova.openstack.common.rpc.amqp [req-c646a76b-084d-4c17-8f0e-43100dc8c9f1 e-dot-cloud10 00000000000000000000000000011233] Exception during message handling RabbitMQ crashes and can miss messages, while the service is auto-recovering. Problem solved, restoring database manually.
        Hide
        Vicent Vicent Borja Torres (Inactive) added a comment -

        ERROR Status is because is trying to delete a VM that is already deleted at the domain level (compute), and the script just raise an exception with and exit before finish. And never manage to clean the database info.

        Show
        Vicent Vicent Borja Torres (Inactive) added a comment - ERROR Status is because is trying to delete a VM that is already deleted at the domain level (compute), and the script just raise an exception with and exit before finish. And never manage to clean the database info.

          People

          • Assignee:
            Vicent Vicent Borja Torres (Inactive)
            Reporter:
            cloudtid Javier Fernández (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: