It is impossible to execute tasks only on the master node

Bug #1648139 reported by Vladimir Maliaev
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
Low
Fuel Sustaining
Mitaka
Won't Fix
Low
Fuel Sustaining
Newton
Confirmed
Low
Fuel Sustaining
Ocata
Confirmed
Low
Fuel Sustaining

Bug Description

"Fuel2 graph execute” can not run individually on master. If I need to run a graph only on master node it is expected to point "master" as a target node in -n NODES parameter.

fuel2 graph execute [-h] -e ENV [-t TYPE] [-n NODES [NODES ...]] [-d]

if I try to use 'master':
fuel2 graph execute: error: argument -n/--nodes: invalid int value: 'master'

if I try to substitute 0:
404 Client Error: Not Found for url: http://172.16.25.2:8000/api/v1/clusters/1/deploy/?nodes=0&graph_type=change_link (NodeCollection not found)

Expected behaviour:
Execute graph only on the Fuel (master)

Changed in fuel:
milestone: none → 9.2
assignee: nobody → Fuel Sustaining (fuel-sustaining-team)
importance: Undecided → Medium
status: New → Confirmed
tags: added: area-python
Revision history for this message
Stanislaw Bogatkin (sbogatkin) wrote :

There is easy workaround - as graph runs for cluster, just apply it on any node, master tasks will be executed also. Lowered priority.

tags: added: customer-found
Revision history for this message
Vladimir Maliaev (vmaliaev) wrote :

The easy workaround above is good for small deployments or test Labs, not for big clouds in pre-production status. In that case a customer does not give a permission to redeploy any node in the cluster.

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.