unable to run --noop on specified set of nodes
Bug #1617993 reported by
Ivan Berezovskiy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Anastasiia Guzikova | ||
Mitaka |
Fix Released
|
High
|
Anastasiia Guzikova | ||
Newton |
Fix Committed
|
High
|
Anastasiia Guzikova |
Bug Description
Steps to reproduce:
Deploy latest 9.1 env (3 controllers, 3 compute nodes).
Try to find customizations in the env on the node using Noop run feature.
Expected result:
Noop run started and successful.
Actual result:
fuel2 env nodes deploy -e 1 --nodes 1 --noop
usage: fuel2 env nodes deploy [-h] -e ENV -n NODES [NODES ...]
fuel2 env nodes deploy: error: unrecognized arguments: --noop
Also now it's possible to execute:
fuel2 env deploy/redeploy --noop
We should follow this way and use Noop run feature with `fuel2 env nodes deploy` only.
tags: | added: on-verification |
To post a comment you must log in.
Fix proposed to branch: stable/mitaka /review. openstack. org/362079
Review: https:/