404 from Heat when creating cluster from Quickstart doc
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
Fix Released
|
Undecided
|
Randall Burt |
Bug Description
If I create a new Devstack server and run the following commands from the Quickstart document (http://
test -f ~/.ssh/id_rsa.pub || ssh-keygen -t rsa -N "" -f ~/.ssh/id_rsa
nova keypair-add --pub-key ~/.ssh/id_rsa.pub testkey
magnum cluster-
magnum cluster-create --name k8s-cluster \
The cluster-create fails with reason "Stack with id 9df444d5-
2016-12-19 21:16:16.750 26034 DEBUG heatclient.
2016-12-19 21:16:16.819 26034 DEBUG heatclient.
HTTP/1.1 404 Not Found
Content-Type: application/json; charset=UTF-8
Content-Length: 618
X-Openstack-
Date: Mon, 19 Dec 2016 21:16:16 GMT
Connection: keep-alive
{"explanation": "The resource could not be found.", "code": 404, "error": {"message": "The Stack (9df444d5-
If I do an "openstack stack list", I see stack "9df444d5-
description: | updated |
Changed in magnum: | |
assignee: | nobody → Jaycen Grant (jaycen-v-grant) |
Changed in magnum: | |
assignee: | Jaycen Grant (jaycen-v-grant) → Randall Burt (randall-burt) |
status: | New → In Progress |
elder magnum[master] $ git bisect start 9149168af376f8a da1ae2d7145] Merge "Disable horizon, swift and ceilometer" ef2249e70462aed e9b585c4fae] Merge "Consolidate heat network resources" 9f5fa6d2907a0e1 df6e3ec19cc] Merge "Change gate Fedora Atomic image to the automated f24 build" 56bbaa43f03b3c6 8c5ed7b5b4e] Merge "Move cluster status updates into driver" 39ca85219edd4b7 8bcc6d9d11e] Merge "[install] Fix endpoint creation" af6688e5d4856de 2c4ad2ef499] Move cluster status updates into driver f6688e5d4856de2 c4ad2ef499 is the first bad commit f6688e5d4856de2 c4ad2ef499
elder magnum[master] $ git bisect good f2f9bd4653f
elder magnum[master] $ git bisect bad 2f9f613c9ac3e0
Bisecting: 34 revisions left to test after this (roughly 5 steps)
[5ede934aafa162
elder magnum[(no branch, bisect started on master)] $ git bisect good
Bisecting: 17 revisions left to test after this (roughly 4 steps)
[43dabfff37edb0
elder magnum[(no branch, bisect started on master)] $ git bisect bad Bisecting: 8 revisions left to test after this (roughly 3 steps)
[cfce4315814ce7
elder magnum[(no branch, bisect started on master)] $ git bisect good
Bisecting: 3 revisions left to test after this (roughly 2 steps)
[0f4bd421f19743
elder magnum[(no branch, bisect started on master)] $ git bisect bad
Bisecting: 2 revisions left to test after this (roughly 1 step)
[da04fe8b1c28c1
elder magnum[(no branch, bisect started on master)] $ git bisect good
Bisecting: 1 revision left to test after this (roughly 1 step)
[759c1b3b2b46b6
elder magnum[(no branch, bisect started on master)] $ git bisect bad
759c1b3b2b46b6a
commit 759c1b3b2b46b6a
Author: Randall Burt <email address hidden>
Date: Thu Dec 1 19:32:42 2016 -0600
Move cluster status updates into driver
This is an alternative implementation to:
https:/ /review. openstack. org/#/c/ 397961
This version implements an earlier proposal from the
spec that adds a driver method for synchronizing
cluster state. This method is optional so that drivers
that do not wish to leverage the existing periodic
synchronization task can do so in whatever manner
they wish and Magnum will not force them to do anything
unnecessarily.
1. add an update_ cluster_ status method to the driver cluster_ status for Heat drivers
interface
2. implment update_
using the existing tested logic
3. Remove cluster status updates from the cluster conductor
in favor of the periodic sync_cluster_status task - this
should avoid timeouts and race conditions possible in the
previous implementation
4. Update the periodic sync_cluster_status method to use
the driver to update cluster status rather than calling
Heat directly
Change-Id: Iae0ec7af254234 3cc51e85f0efd21 086d693e540 Blueprint: bp-driver- consolodation
Partial-