 |
RackTables since the very first public release stores L2 addresses as upper case hex strings, so the lower case data is likely an effect of a direct INSERT. Before 0.21.0 RackTables did not check whether the data it read from the database comes in upper case, so the inconsistency could remain hidden with a potential to manifest elsewhere. In the current implementation the invalid data format triggers an immediate exception, which is the intended behaviour. This way, the only thing that needs to be done in this case is to remind that 3rd party software should not access RackTables database directly, there is the internal PHP API for that. |
 |
We don't have any third party software interacting with the database and always added data through the UI. I suspect there must have been a bug at some point that was already fixed which allowed it to be inserted through the UI, as we have not seen this issue with any hosts added after upgrading to 0.21.5. But it'd be nice if one of the following was present: * There was a more descriptive error message * Something that autocorrects the data upon upgrading from an older version * Something that autocorrects the data when viewing it, similar to how colons are added to L2 addresses * Selecting UPPER(l2address) just to make sure it's in a format that's expected It would have made debugging this much easier, since it was not apparent from the error message that this was an L2 address. It just looked like a random hex string, being all lowercase with no colons. |
|
|
Thank you for the feedback. It could indeed be a bug in old RackTables versions, or could be something else. The post-upgrade diagnostics would be a bit easier using the data integrity report, which includes a check for this specific anomaly ("L2 address invalid characters"). You can try it and see if it flags anything else. Regarding using UPPER() for this data column, let me mention that it would not be a correct solution without going into too much technical detail. |
|
|
Where do I find that information? |
|
|
main page -> reports -> data integrity |
|
|
Is there anything else that remains to be done in the scope of this request? |
|
|
Alright, closing as resolved then. |
- Anonymous
