Override_resources is unable to remove customized parameters

Bug #1814550 reported by Alexander Rubtsov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
Medium
Roman Lubianyi

Bug Description

--- Environment ---
MOS: 9.2

--- Description ---
The override_resources feature (https://docs.mirantis.com/fuel-docs/mitaka/userdocs/fuel-user-guide/cli/cli_config_openstack.html) enables to add a new parameter / change the value of a parameter.
However as soon as the customized value has been uploaded, it can not be removed by override_resources means (i.e. reverted to initial value).

--- Steps to reproduce ---
1. Deploy an environment
2. Create the following /root/nova.yaml file on the Fuel node:
configuration:
  nova_config:
    DEFAULT/verbose:
      value: 'True'

3. Upload the configuration:
fuel openstack-config --env 1 --upload --file nova.yaml

4. Download the changed configuration:
fuel deployment --env 1 --default

5. Ensure that the modified value is in place:
grep -r "verbose" -A1 /root/deployment_1/
/root/deployment_1/2.yaml: DEFAULT/verbose:
/root/deployment_1/2.yaml- value: 'True'
--
/root/deployment_1/3.yaml: DEFAULT/verbose:
/root/deployment_1/3.yaml- value: 'True'

6. Remove the parameter from the /root/nova.yaml file:
configuration:
  nova_config:
# DEFAULT/verbose:
# value: 'True'

7. Upload the changes
fuel openstack-config --env 1 --upload --file nova.yaml

8. Download the changed configuration:
fuel deployment --env 1 --default

9. Verify the current value of the parameter:
grep -r "verbose" -A1 /root/deployment_1/

--- Actual behavior ---
The modified value is still here
/root/deployment_1/2.yaml: DEFAULT/verbose:
/root/deployment_1/2.yaml- value: 'True'
--
/root/deployment_1/3.yaml: DEFAULT/verbose:
/root/deployment_1/3.yaml- value: 'True'

--- Expected behavior ---
There are no modifications

Revision history for this message
Alexander Rubtsov (arubtsov) wrote :

sla2 for 9.0-updates

Changed in fuel:
importance: Undecided → Medium
assignee: nobody → MOS Maintenance (mos-maintenance)
milestone: none → 9.x-updates
tags: added: customer-found sla2
Changed in fuel:
milestone: 9.x-updates → 9.2-mu-11
status: New → Confirmed
Revision history for this message
Alexander Rubtsov (arubtsov) wrote :

Hello, do you have any updates regarding this matter?

Changed in fuel:
assignee: MOS Maintenance (mos-maintenance) → Roman Lubianyi (rlubianyi)
Revision history for this message
Roman Lubianyi (rlubianyi) wrote :

Hello Alexander,
We have identified an issue:
When you apply or download configuration with removed parameter fuel cli didn't check "is_active" flag in the openstack_configs table. Currently, we are working on the patch for this issue.

Revision history for this message
Fuel Devops McRobotson (fuel-devops-robot) wrote : Fix proposed to openstack/fuel-web (9.0/mitaka)

Fix proposed to branch: 9.0/mitaka
Change author: Oleksiy Molchanov <email address hidden>
Review: https://review.fuel-infra.org/40680

Changed in fuel:
status: Confirmed → In Progress
Revision history for this message
Oleksiy Molchanov (omolchanov) wrote :

Alexander, you need to identify and delete config you have added

fuel openstack-config --list --env ID
fuel openstack-config --delete --config CONF_ID

PS: patch should be applied with nailgun service restart

Revision history for this message
Fuel Devops McRobotson (fuel-devops-robot) wrote : Fix merged to openstack/fuel-web (9.0/mitaka)

Reviewed: https://review.fuel-infra.org/40680
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0/mitaka

Commit: 3042a396968f4741a8554ef31255d95a45041772
Author: Oleksiy Molchanov <email address hidden>
Date: Fri Mar 1 10:26:55 2019

Add to deployment custom configs that are active

Closes-Bug: 1814550
Change-Id: If3326434373251aaa935fc449d065cacce9eb567

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
Pavel Glazov (pglazovv) wrote :

Verified:
[root@nailgun ~]# vim /root/nova.yaml
[root@nailgun ~]# fuel openstack-config --env 1 --upload --file nova.yaml
id | is_active | config_type | cluster_id | node_id | node_role
---+-----------+-------------+------------+---------+----------
1 | True | cluster | 1 | |
[root@nailgun ~]# fuel deployment --env 1 --default
Default deployment info was downloaded to /root/deployment_1
[root@nailgun ~]# grep -r "verbose" -A1 /root/deployment_1/
/root/deployment_1/6.yaml: DEFAULT/verbose:
/root/deployment_1/6.yaml- value: 'True'
--
/root/deployment_1/5.yaml: DEFAULT/verbose:
/root/deployment_1/5.yaml- value: 'True'
--
/root/deployment_1/3.yaml: DEFAULT/verbose:
/root/deployment_1/3.yaml- value: 'True'
--
/root/deployment_1/2.yaml: DEFAULT/verbose:
/root/deployment_1/2.yaml- value: 'True'
--
/root/deployment_1/4.yaml: DEFAULT/verbose:
/root/deployment_1/4.yaml- value: 'True'
--
/root/deployment_1/1.yaml: DEFAULT/verbose:
/root/deployment_1/1.yaml- value: 'True'
[root@nailgun ~]# vim /root/nova.yaml
[root@nailgun ~]# fuel openstack-config --env 1 --upload --file nova.yaml
id | is_active | config_type | cluster_id | node_id | node_role
---+-----------+-------------+------------+---------+----------
2 | True | cluster | 1 | |
[root@nailgun ~]# fuel deployment --env 1 --default
Default deployment info was downloaded to /root/deployment_1
[root@nailgun ~]# grep -r "verbose" -A1 /root/deployment_1/
[root@nailgun ~]#

Changed in fuel:
status: Fix Committed → Fix Released
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.