This is proper behavior.
When you upload new configuration for the same entity (node, role, cluster) - previous active configuration is marked as inactive/deleted. From spec:
"is_active field will be automatically managed by nailgun.
When user upload new data, old data for given entity (ex. node_role=compute)
will be mark as inactive (is_active=False) and new data will be marked as
active (is_active=True)."
List action show active records by default, if you want to show deleted (inactive) records use --deleted:
This is proper behavior.
When you upload new configuration for the same entity (node, role, cluster) - previous active configuration is marked as inactive/deleted. From spec:
"is_active field will be automatically managed by nailgun.
When user upload new data, old data for given entity (ex. node_role=compute)
will be mark as inactive (is_active=False) and new data will be marked as
active (is_active=True)."
List action show active records by default, if you want to show deleted (inactive) records use --deleted:
[root@nailgun log]# fuel openstack-config --list --env 1 --deleted ------- -|----- ------- -|----- ------- |------ ---|--- ------- ------- -|----- ------- -|----- ------- |------ ---|--- -------
id | is_active | config_type | cluster_id | node_id | node_role
---|---
1 | False | node | 1 | 1 | None
[root@nailgun log]# fuel openstack-config --list --env 1
id | is_active | config_type | cluster_id | node_id | node_role
---|---
2 | True | node | 1 | 1 | None
[root@nailgun log]#