Closed ebeahan closed 7 years ago
Am working on a PR to address.
Okay, if the format is not matching the expected format this should fail the unit tests...so it also means there is a NAPALM unit test issue that needs corrected.
Would that mean adjusting the existing model here with a more stringent check? Still getting familiar with the napalm testing structure.
https://github.com/napalm-automation/napalm-base/blob/develop/napalm_base/test/models.py#L172
As per doc of the mac
helper, it should transform this anyway: https://github.com/napalm-automation/napalm-base/blob/develop/napalm_base/helpers.py#L205-L211
Otherwise, we need to address it.
It is probably an error in the formatting of the expected_result.json files in:
https://github.com/ktbyers/napalm-ios/tree/devel/test/unit/mocked_data/test_get_mac_address_table
We will just need to update these expected_result.json files to be the proper format.
Fix merged in https://github.com/napalm-automation/napalm-ios/pull/110.
Description of Issue/Question
Did you follow the steps from https://github.com/napalm-automation/napalm#faq
Setup
napalm-ios version
IOS version
Steps to Reproduce the Issue
Per discussions on Slack, napalm drivers should normalize MAC addresses to the 11:AA:22:BB:33:CC convention. Currently napalm-ios is returning MAC addresses in the 11aa.22bb.33cc format.
A helper function called
mac
already exists in napalm-base helpers to handle the formatting.Example: