Back to bug 809621

Who When What Removed Added
Angus Thomas 2012-04-30 14:43:42 UTC Keywords Triaged
Hugh Brock 2012-05-08 16:51:59 UTC CC hbrock
Angus Thomas 2012-05-23 10:54:29 UTC Status NEW ASSIGNED
Assignee athomas matt.wagner
Jan Provaznik 2012-05-23 14:41:30 UTC CC jprovazn
Matt Wagner 2012-05-23 19:12:58 UTC Status ASSIGNED MODIFIED
Chris Pelland 2012-05-29 16:11:08 UTC Blocks 826116
Chris Pelland 2012-05-29 16:12:32 UTC Keywords ZStream
CC cpelland
errata-xmlrpc 2012-08-09 21:57:04 UTC Status MODIFIED ON_QA
Julie 2012-11-07 01:53:47 UTC Status ON_QA VERIFIED
CC dgao
CC juwu
Doc Text Previously launching an instance with the configserver inactive will create instances that are in a forever pending state. Those instances can't be deleted. This bug fix updates deployment.rb so that the configserver returns a 503 error and give instances a create_failed status when the configserver is not reachable.
Alexandra 2012-11-19 04:17:25 UTC CC asettle
Doc Text Previously launching an instance with the configserver inactive will create instances that are in a forever pending state. Those instances can't be deleted. This bug fix updates deployment.rb so that the configserver returns a 503 error and give instances a create_failed status when the configserver is not reachable. Previously launching an instance with the configserver inactive was creating instances that were in a forever pending state. Those instances were unable to be deleted. This bug fix updates for deployment.rb so that the configserver returns a 503 error and provides instances a create_failed status when the configserver is not reachable.
Dan Macpherson 2012-11-28 16:53:02 UTC CC dmacpher
Doc Text Previously launching an instance with the configserver inactive was creating instances that were in a forever pending state. Those instances were unable to be deleted. This bug fix updates for deployment.rb so that the configserver returns a 503 error and provides instances a create_failed status when the configserver is not reachable. Launching an instance with the configserver inactive created instances in a forever pending state were unable to be deleted. This bug fix updates deployment.rb so that the configserver returns a 503 error. This provides instances a create_failed status when the configserver is not reachable.
errata-xmlrpc 2012-12-04 01:09:14 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2012-12-04 15:02:36 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2012-12-04 10:02:36 UTC
John Skeoch 2013-09-02 07:01:58 UTC CC jturner
John Skeoch 2014-08-17 22:27:39 UTC CC athomas

Back to bug 809621