"status_reason: Create timed out " is conflict to "bay_create_timeout: 0"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
Fix Released
|
Undecided
|
PanFengyun |
Bug Description
description:
1.I use the follow command(not set bay_create_timeout) to create a bay, but I get timeout and CREATE_FAILED:
$ magnum bay-create --name k8sbay --baymodel k8sbaymodel --node-count 1
$ magnum bay-list
+------
| uuid | name | node_count | master_count | status |
+------
| c09a0f40-
+------
$ heat event-list k8sbay-xprq7cdlfa2t
...
| kube_minions | 6266efa2-
| kube_masters | c32a0fe9-
| k8sbay-xprq7cdlfa2t | 49bd60fa-
+------
$ magnum bay-show k8sbay
...
| status | CREATE_FAILED |
| uuid | c09a0f40-
| status_reason | Create timed out |
...
| bay_create_timeout | 0 |
2.the help info in conductor/
-------
53 cfg.IntOpt(
54 help=('The length of time to let bay creation continue. This '
55 'interval is in minutes. The default is no timeout.'))
-------
"The default is no timeout" is wrong , the bay will use stack_action_
bug: " status_reason: Create timed out " is conflict to "bay_create_
reason: when dodn't set bay_create_timeout to create bay, magnum will use stack_action_
revise: set bay_create_timeout with 3600, like stack_action_
Changed in magnum: | |
assignee: | nobody → PanFengyun (pan-feng-yun) |
Changed in magnum: | |
status: | New → In Progress |
Reviewed: https:/ /review. openstack. org/327445 /git.openstack. org/cgit/ openstack/ magnum/ commit/ ?id=f5150078eee 19fb326b14a0f0d fb8fd5d04e43b8
Committed: https:/
Submitter: Jenkins
Branch: master
commit f5150078eee19fb 326b14a0f0dfb8f d5d04e43b8
Author: PanFengyun <email address hidden>
Date: Sun Jul 3 23:26:32 2016 +0800
Bay_ create_ timeout should be set to 60 default
Bay_ create_ timeout default is 0 and means that magnum create bay /review. openstack. org/#/c/ 334138/
without timeout. But heat create stack with timeout absolutely.
So it is impossible to create bay without timeout. And I had send
a patch which allow heat to create stack without timeout, but the
core of heat did not agree with it.
The patch is: https:/
Change-Id: Iebc9915dcf2894 a2dbed912244a2c 7c308b4d9d7
Closes-bug: #1590636