"status_reason: Create timed out " is conflict to "bay_create_timeout: 0"

Bug #1590636 reported by PanFengyun
6
This bug affects 1 person
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-633c-4c2d-938a-f8057c043a8f | k8sbay | 1 | 1 | CREATE_FAILED |
+--------------------------------------+--------+------------+--------------+---------------+
$ heat event-list k8sbay-xprq7cdlfa2t
...
| kube_minions | 6266efa2-99d5-4afb-a80a-47a75e03fc7e | CREATE aborted | CREATE_FAILED | 2016-06-08T02:41:45 |
| kube_masters | c32a0fe9-a2bc-40f7-ab94-e4131e296555 | CREATE aborted | CREATE_FAILED | 2016-06-08T02:41:45 |
| k8sbay-xprq7cdlfa2t | 49bd60fa-7806-41e5-a465-4590ea6dbd3d | Create timed out | CREATE_FAILED | 2016-06-08T02:41:45 |
+----------------------+--------------------------------------+------------------------+--------------------+---------------------+
$ magnum bay-show k8sbay
...
| status | CREATE_FAILED |
| uuid | c09a0f40-633c-4c2d-938a-f8057c043a8f |
| status_reason | Create timed out |
...
| bay_create_timeout | 0 |

2.the help info in conductor/handlers/bay_conductor.py:
-------
 53 cfg.IntOpt('bay_create_timeout',
 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_timeout of heat.

bug: " status_reason: Create timed out " is conflict to "bay_create_timeout: 0"
reason: when dodn't set bay_create_timeout to create bay, magnum will use stack_action_timeout of heat.
revise: set bay_create_timeout with 3600, like stack_action_timeout of heat.

Changed in magnum:
assignee: nobody → PanFengyun (pan-feng-yun)
Changed in magnum:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to magnum (master)

Reviewed: https://review.openstack.org/327445
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=f5150078eee19fb326b14a0f0dfb8fd5d04e43b8
Submitter: Jenkins
Branch: master

commit f5150078eee19fb326b14a0f0dfb8fd5d04e43b8
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
    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://review.openstack.org/#/c/334138/

    Change-Id: Iebc9915dcf2894a2dbed912244a2c7c308b4d9d7
    Closes-bug: #1590636

Changed in magnum:
status: In Progress → Fix Released
Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/python-magnumclient 2.2.0

This issue was fixed in the openstack/python-magnumclient 2.2.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/magnum 3.0.0

This issue was fixed in the openstack/magnum 3.0.0 release.

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

Other bug subscribers

Remote bug watches

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