Fixing logic to identify proper 'port_config.ini' file. #376
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Upon collection of minigraph_facts by ansible scripts, these ones are being unable to identify the proper port-speeds within port_alias.py. In consequence, a bunch of testcases fail and an incorrect minigraph.xml configuration file is generated.
Current code assumes that each platform holds its port_config.ini file
within a flat folder struct -- something like this:
However, there are platforms (e.g. Celestica) that support different
port-layouts, and as such, make use of a more structural folder
scheme:
The current code will erroneously pick a random port_config.ini file
within this folder hierarchy, so i'm fixing the file-identification logic to
fully match the SKU being utilized.