On a Fuel Master node the keystone container never can start after stop
Bug #1599418 reported by
Sergey Abramov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Won't Fix
|
Medium
|
Fuel Sustaining | ||
Bug Description
Detailed bug description:
After MU on fuel-8 container can't start.
Steps to reproduce:
change astute.yaml conf.
dockerctl stop keystone
dockerctl start keystone
Actual result:
checking with command "! shell_container keystone pgrep puppet"
keystone failed to start.
Expected results:
keystone is ready.
Workaround:
dockerctl destroy keystone
dockerctl start keystone
| summary: |
- container never can to start after stop + On a Fuel Master node the keystone container never can to start after + stop |
| summary: |
- On a Fuel Master node the keystone container never can to start after - stop + On a Fuel Master node the keystone container never can start after stop |
| Changed in fuel: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
| assignee: | nobody → Fuel Sustaining (fuel-sustaining-team) |
| milestone: | none → 8.0-updates |
Revision history for this message
| Alexey Stupnikov (astupnikov) wrote | #1 |
| Changed in fuel: | |
| status: | Confirmed → Won't Fix |
To post a comment you must log in.
Closing as won't fix as we don't fix bugs with medium priority in stable branches.