system storage API inconsistently display system created resources

Bug #1823739 reported by Allain Legacy on 2019-04-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Low
Frank Miller

Bug Description

Brief Description
-----------------
During installation, the system creates certain storage related resources (volume groups, partitions, etc). Those resources are not consistently presented to API users. For example, the cgts-vg volume group is created by the system and returned by the system API, but its underlying partitions are not returned by the API as they are filtered out before the response is created and sent.

This type of inconsistent makes it difficult for an API user to correlate the information presented to determine whether the system is in the desired state or whether further provisioning steps are necessary. To workaround this issue, an API user must make assumptions about how the system behaves in order to ignore certain resources when determining how to reconcile the current configuration with the desired configuration.

Severity
--------
Provide the severity of the defect.
Minor

Steps to Reproduce
------------------
Install any system and observe that the physical volume groups do not all refer to a user accessible disk/partition uuid value.

Expected Behavior
------------------
The system should either hide system created resources from the user or display all resources in a consistent manor so that the end user of the API does not need to make assumptions about what it means when a particular UUID value is not found in a resource list returned by the API.

Actual Behavior
----------------
The API presents an incomplete list of resources where system resources are returned from some API endpoints but not all.

Reproducibility
---------------
100%

System Configuration
--------------------
All

Branch/Pull Time/Commit
-----------------------
n/a

Last Pass
---------
n/a

Timestamp/Logs
--------------
n/a

Test Activity
-------------
Developer

Ghada Khalil (gkhalil) wrote :

Marking as low priority / not gating as there is a concern about the churn required to address this. Will let Frank Miller review and comment accordingly.

Changed in starlingx:
importance: Undecided → Low
status: New → Triaged
assignee: nobody → Frank Miller (sensfan22)
tags: added: stx.config
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers