use port-element-id over portno

Bug #1659285 reported by Andreas Scheuring
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-dpm
Triaged
High
Unassigned

Bug Description

At the moment the portno of the physical_adapter_mappings defaults to 0 when none is given. The idea behind that was, that it does not need to be specified on single port adapters. But what happens if an adapter with the port element id "foo" gets introduced (which is not 0). In this case the current logic will fail. To work around the whole problematic the option example should get renamed to

<portno> -> <port-element-id> (if still used somewhere)
To be discussed: <port-element-id> should become mandatory?

Changed in networking-dpm:
importance: Undecided → High
summary: - make physical_adapter_mappings porto mandatroy
+ make physical_adapter_mappings porto mandatory
Changed in networking-dpm:
status: New → Triaged
description: updated
summary: - make physical_adapter_mappings porto mandatory
+ use port-element-id over portno
description: updated
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.