-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dev1.1.0g // Bad csv format breaks 'ztp' commands #26
Comments
Sounds like it's doing exactly what it's supposed to. |
@icovada of course; but from what I understand, error handling should be implemented to adhere to development best practices; so the end user is provided with a simplistic error message. Which would prevent the end user from having to seek assistance; i.e. "Missing in external CSV" is easier to decipher and take action than a traceback. @PackeTsar has done an excellent job all around with FreeZTP. I created the issue to bring the traceback to his attention, not so much to seek assistance with the error. |
Added bug to tracker issue |
Received the following traceback when my keystore_id rows had more delimiters than the header row.
All ZTP commands gave the same traceback until the csv format was fixed.
The text was updated successfully, but these errors were encountered: