service getting stuck in deploy in progress state

Bug #1540482 reported by Sriram
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Poppy
New
Medium
Unassigned

Bug Description

Sometimes, a job execution failure by the worker can leave the service stuck, with state being set to deploy in progress.

This denies the chance of fixing the service, either through an empty patch to the service or through other means.

This bug, needs to be resolved, by having a common revert in place for Taskflow Tasks, that would set the state of the service to be 'failed'

Sriram (thesriram)
Changed in poppy:
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to poppy (master)

Reviewed: https://review.openstack.org/274721
Committed: https://git.openstack.org/cgit/openstack/poppy/commit/?id=3647f722521a40fa749184ee99ded4124f532ecc
Submitter: Jenkins
Branch: master

commit 3647f722521a40fa749184ee99ded4124f532ecc
Author: Sriram Madapusi Vasudevan <email address hidden>
Date: Mon Feb 1 10:41:08 2016 -0500

    feat: admin endpoint to set status of a particular service

    - REQUEST

      POST http://127.0.0.1:8888/v1.0/admin/services/status

      {
          "project_id": "98765431",
          "service_id": "e8b44506-71b7-4074-9bc8-1b5037ade112",
          "status": "deployed"
      }

    - RESPONSE

      201

    Implements: blueprint admin-endpoint-to-set-service-status
    Related-Bug: 1540482

    Change-Id: I89d40601c55af6cc3c2d45352d8e24c691107bd0

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers