bootstrap_admin_node.sh continues even fuelmenu fails in the interactive mode
Bug #1569014 reported by
Ilya Kharin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Maksim Malchuk | ||
Mitaka |
Fix Released
|
High
|
Maksim Malchuk |
Bug Description
In case if you entered in fuelmenu during the installation of the master node and it fails by some reason with non-zero status the bootstrap process continues.
Steps to reproduce:
1. Boot from 9.0 ISO with the specified flag 'showmenu=yes'
2. Enter in fuelmenu
3. During the configuration fuelmenu fails and exit with non-zero exit status
Expected result:
The bootstrap process should be terminate.
Actual result:
The bootstrap process continues even in case you did not specify everything you wanted, and errors regarding fuelmenu failure are very hard to notice.
Workaround
Interrupt the bootstrap script, fix fuelmenu manually, and then run bootstrap_
description: | updated |
tags: | added: area-library |
Changed in fuel: | |
assignee: | nobody → Fuel Library Team (fuel-library) |
importance: | Undecided → High |
status: | New → Confirmed |
milestone: | none → 9.0 |
Changed in fuel: | |
assignee: | Fuel Library Team (fuel-library) → Maksim Malchuk (mmalchuk) |
Changed in fuel: | |
status: | Confirmed → Incomplete |
Changed in fuel: | |
status: | Incomplete → In Progress |
Changed in fuel: | |
milestone: | 9.0 → 10.0 |
tags: | added: team-bugfix |
tags: | added: on-verification |
To post a comment you must log in.
Ilya, how did you get Fuelmenu to fail and exit? If there's a scenario that causes it to crash, we should fix that. There should be no scenario where fuelmenu exits nonzero. If there is and we really need to plan for it, we can add logic in bootstrap_ admin_node. sh to catch it.