Flag --force is not available for "fuel2 env deploy" command

Bug #1624315 reported by Alexandra
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Fuel Sustaining

Bug Description

Configuration:
9.1 snapshot #268
3 controllers + 2 computes + 2 ceph-osd
Neutron with VLAN segmentation

Summary:
Unable to user --force flag for fuel2 env deploy
It's required for full report of noop run

[root@nailgun ~]# fuel2 env deploy --noop --force 1
usage: fuel2 env deploy [-h] [-d] [--noop] id
fuel2 env deploy: error: unrecognized arguments: --force

Actions:
1) Modify any config (for example, /etc/nova/nova.conf on controller
2) Run fuel2 env deploy
[root@nailgun ~]# fuel2 env deploy --noop 1
Deployment task with id 14 for the environment 1 has been started.

[root@nailgun ~]# fuel task
id | status | name | cluster | progress | uuid
---+---------+-------------------------+---------+----------+-------------------------------------
5 | ready | deploy | 1 | 100 | b2912c87-12ae-4fbf-8481-66313dca1b86
8 | ready | provision | 1 | 100 | 9b57ac32-a416-4adb-b42f-540d57789f9d
10 | ready | verify_networks | 1 | 100 | 452c0223-3b0e-415d-8050-df73dd56b61f
12 | ready | check_repo_availability | 1 | 100 | d1bc8cbb-d5d8-40cf-bfdc-2ca9d49d80ab
9 | ready | deployment | 1 | 100 | 150d54df-807c-40d9-833b-7d16c4d2dc68
13 | ready | create_stats_user | 1 | 100 | fea57144-1577-4cd7-8983-e0fca4777c4e
11 | ready | check_dhcp | 1 | 100 | 93c15ef8-51a3-44af-8a0a-30a95a9c4408
17 | running | dry_run_deployment | 1 | 100 | cd5fc88c-5615-4e73-8288-704711306816
14 | running | deploy | 1 | 100 | 1a1d1162-d463-490b-b8dc-2e372009dc2b

3) Check summary of task (tid=17)
[root@nailgun ~]# more task_res_with_summary | grep Nova_conf
[root@nailgun ~]#
=> there is no info about custom change

Tags: area-python
Revision history for this message
Alexandra (aallakhverdieva) wrote :
Revision history for this message
Alexandra (aallakhverdieva) wrote :
Changed in fuel:
importance: Undecided → High
assignee: nobody → Fuel Sustaining (fuel-sustaining-team)
milestone: none → 9.1
Dmitry Klenov (dklenov)
tags: added: area-python
Changed in fuel:
status: New → Confirmed
Revision history for this message
Dmitry Pyzhov (dpyzhov) wrote :

You can use 'env redeploy' instead

Changed in fuel:
milestone: 9.1 → 9.2
Revision history for this message
Vitalii Kulanov (vitaliy-t) wrote :

@Dmitry, command 'fuel2 env redeploy' also doesn't contain '--force' flag. It contains the same list of params as 'fuel2 env deploy':

[root@fuel ~]# fuel2 env redeploy
usage: fuel2 env redeploy [-h] [-d] [--noop] id

@Alexandra, you cant try to use:

[root@fuel ~]# fuel2 env nodes deploy
usage: fuel2 env nodes deploy [-h] -e ENV -n NODES [NODES ...] [-f] [--noop]

Revision history for this message
Alexandra (aallakhverdieva) wrote :

"fuel2 env nodes deploy" works well
About 'fuel2 env redeploy' - indeed, it doesn't contain --force flag also, but it detects custom changes anyway

Revision history for this message
Bulat Gaifullin (bulat.gaifullin) wrote :

fuel2 env redeploy is same as 'fuel2 env deploy --force', there is reason why fuel2 env deploy and fuel2 env redeploy does not contain attribute 'force'.

Changed in fuel:
status: Confirmed → Invalid
Revision history for this message
Alexandra (aallakhverdieva) wrote :

Do you mean that 'fuel2 env deploy' shouldn't contain attribute 'force'?

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.