Strange output of 'node label set' command

Bug #1490949 reported by Julia Aranovich
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Medium
Artem Roma

Bug Description

The output of 'node label set' command differs if no labels or nodes specified:

(fuel2) node label set --labels k3 k4
usage: node label set [-h] [-l LABELS [LABELS ...]]
                      (-n NODES [NODES ...] | --nodes-all)
node label set: error: one of the arguments -n/--nodes --nodes-all is required

(fuel2) node label set --nodes 3 4
'NoneType' object is not iterable

I think it should be consistent.

Changed in fuel:
assignee: Andriy Popovych (popovych-andrey) → Fuel Python Team (fuel-python)
Dmitry Pyzhov (dpyzhov)
tags: added: area-python
Artem Roma (aroma-x)
Changed in fuel:
assignee: Fuel Python Team (fuel-python) → Artem Roma (aroma-x)
Revision history for this message
Artem Roma (aroma-x) wrote :

This bug is already fixed: get appropriate message when labels value are omitting. Thus move to invalid

Changed in fuel:
status: Confirmed → Won't Fix
status: Won't Fix → 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.