Fuel setup menu doesn't have a support for serial interface
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Won't Fix
|
Medium
|
Matthew Mosesohn | ||
6.0.x |
Won't Fix
|
Medium
|
Matthew Mosesohn | ||
7.0.x |
Won't Fix
|
Medium
|
Matthew Mosesohn | ||
8.0.x |
Won't Fix
|
Medium
|
Matthew Mosesohn |
Bug Description
1. TROUBLE DESCRIPTION
1.1. Trouble summary
The fuel menu is written with urwid and there's no support for devices that only have a
serial interface.
1.2. Detailed trouble description
In ideal circumstances, after booting the Fuel ISO and choosing to show the Fuel
setup menu (showmenu=yes), a graphical menu (AKA fuelmenu) is shown in order to
configure the installation (http://
That menu is written with urwid and there's no support for devices that only have a
serial interface. This means that the menu is never shown and the default
configuration vales are used (root credentials being root:r00tme).
Even though the root password can be changed after the installation, the security
risk is still there: the time span between the end of the installation and the changing
of the password. There, the system's root account is be vulnerable, because it's
using a well-known password.
Changed in fuel: | |
assignee: | nobody → Fuel Library Team (fuel-library) |
tags: | added: customer-found |
Changed in fuel: | |
assignee: | Fuel Library Team (fuel-library) → Matthew Mosesohn (raytrac3r) |
tags: | added: release-notes |
Changed in fuel: | |
milestone: | 6.1 → 8.0 |
status: | Won't Fix → Confirmed |
no longer affects: | fuel/8.0.x |
tags: | added: area-library |
tags: | added: blocked |
tags: | added: team-bugfix |
tags: | removed: blocked |
tags: | added: blocked |
no longer affects: | fuel/mitaka |
tags: | removed: blocked |
tags: |
added: 8.0 release-notes-done removed: release-notes |
tags: | added: wontfix-workaround |
There is a many workarounds to this, as from changing root password manually from another console to disable networking. Also, there is don't breaks deployment, so make it a medium.