Poppy

Services go into pending after exhausting max DNS retries

Bug #1494430 reported by Sriram
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Poppy
Fix Released
Undecided
Sriram
Poppy liberty-3 "liberty-3"

Bug Description

Services go into pending after exhausting maximum DNS retries. The job should go ahead and mark the service to be failed, before quitting. This will allow operations to be taken to get the service back to deployed.

Example:

In the case of rate limits being hit on every retry, the service should go to failed.

An empty patch should be able to get the service back to deployed, after the DNS api goes back to normal operation.

Sriram (thesriram)
Changed in poppy:
assignee: nobody → Sriram (thesriram)
status: New → Confirmed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to poppy (master)

Related fix proposed to branch: master
Review: https://review.openstack.org/222309

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to poppy (master)

Reviewed: https://review.openstack.org/222309
Committed: https://git.openstack.org/cgit/stackforge/poppy/commit/?id=0165725b6d1aafb0bbcfe6f1af2c2b816072d60b
Submitter: Jenkins
Branch: master

commit 0165725b6d1aafb0bbcfe6f1af2c2b816072d60b
Author: Sriram Madapusi Vasudevan <email address hidden>
Date: Thu Sep 10 14:11:57 2015 -0400

    fix: update service state to failed, after exhausting DNS retries

    Change-Id: I4eea482dca0bd60f92e4b9c6b0b091504fe86907
    Related-Bug: 1494430

Sriram (thesriram)
Changed in poppy:
milestone: none → liberty-3
status: Confirmed → Fix Committed
Amit Gandhi (amit-gandhi)
Changed in poppy:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.