Default release workflow doesn't deploy anything as the custom workflow

Bug #1664169 reported by Ekaterina Khomyakova
6
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

Tags: area-python
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
Revision history for this message
Ekaterina Khomyakova (ekhomyakova) wrote :

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.

Revision history for this message
Vladimir Kuklin (vkuklin) wrote :

This is the expected behaviour - the graph is executed on the nodes that are filtered according to the filter. If filter is empty, as in our case, then only provisioned nodes will be sent to the deployment. You need to check which nodes the graph was executed on or specify nodes explicitly in the call.

Changed in fuel:
status: Confirmed → Invalid
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.