sysinv api returns different datanetworks fields for get and list operations

Bug #1842062 reported by Allain Legacy on 2019-08-30
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Brief Description
The sysinv API does not return the same set of fields for datanetworks resources for both a Get and a List operation. The Get operation includes the timestamp fields (created_at, updated_at, etc), but the List operation does not. This makes it onerous for an API user to build a complete view of the data without iterating over each resource rather than issuing a single List operation.

A Get returns the following fields:

DEBUG (http:157) RESP: {"description": null, "updated_at": null, "created_at": "2019-08-30T06:41:48.867955+00:00", "port_num": null, "uuid": "3890bca4-ea7a-4e05-8b72-70685b1e5c09", "mtu": 1500, "multicast_group": null, "mode": null, "ttl": null, "id": 1, "network_type": "vlan", "name": "group0-data0"}

While a List returns the following fields:

DEBUG (http:157) RESP: {"datanetworks": [{"description": null, "port_num": null, "uuid": "3890bca4-ea7a-4e05-8b72-70685b1e5c09", "mtu": 1500, "multicast_group": null, "mode": null, "ttl": null, "id": 1, "network_type": "vlan", "name": "group0-data0"}]}


Steps to Reproduce
system --debug datanetwork-list
system --debug datanetwork-show <uuid>

Expected Behavior
The list of fields returned should be the same between a Get and a List.

Actual Behavior
List returns only a subset of the fields available through a Get.


System Configuration

Branch/Pull Time/Commit

Last Pass

see above

Test Activity
Developer Testing

Frank Miller (sensfan22) wrote :

Based on the description and severity = low, marking this as low priority.

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

Other bug subscribers