Default release workflow doesn't deploy anything as the custom workflow
Bug #1664169 reported by
Ekaterina Khomyakova
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
High
|
Fuel Sustaining |
Bug Description
Fuel 10 #1338
Steps to reproduce:
1. Log in to Fuel UI
2. Create env
3. Add 1 controller node
4. Go to 'Workflows' tab and download JSON file for Type "default", Level Release
5. Upload new workflow with downloaded JSON file
6. Go to 'Dashboard' tab and select Deployment Mode: Custom Workflow
7. Run custom workflow on the controller node
Actual result:
UI tells 'Success' after several seconds, but almost all tasks were skipped. And there is no changes on controller.
Expected results:
Tasks were executed
summary: |
- Default release workflow doesn't deploy anything + Default release workflow doesn't deploy anything as the custom workflow |
Changed in fuel: | |
assignee: | nobody → Fuel Sustaining (fuel-sustaining-team) |
importance: | Undecided → High |
status: | New → Confirmed |
tags: | added: area-python |
To post a comment you must log in.
Seems that the problem is in the lack of warning or error message that nodes are not provisioned yet.
Tasks are running on provisioned node, but fail on upload_cirros step.