... so if one package is updated but not the other, the index in `netaddr` will become incorrect. I ran some tests with `netaddr` upstream and it seems like the library works fine with any OUI, even OUIs with incorrectly encoded characters in them, etc.
To test this theory, you could run netaddr as follows to regenerate the indexes:
sudo python3 -m netaddr.eui.ieee
You would need to restart MAAS after doing this, since netaddr keeps the indexes cached in memory.
Hm. I think the root cause of this might be that the index is not updated often enough (that is, it could be a Debian package mismatch).
The `netaddr` package defines the following:
ls -la /usr/lib/ python3/ dist-packages/ netaddr/ eui/oui. txt python3/ dist-packages/ netaddr/ eui/oui. txt -> ../../. ./../.. /share/ ieee-data/ oui.txt
lrwxrwxrwx 1 root root 38 Oct 23 2015 /usr/lib/
readlink -f /usr/lib/ python3/ dist-packages/ netaddr/ eui/oui. txt ieee-data/ oui.txt
/usr/share/
The `ieee-data` provides the actual data:
dpkg -S /usr/share/ ieee-data/ oui.txt ieee-data/ oui.txt
ieee-data: /usr/share/
... so if one package is updated but not the other, the index in `netaddr` will become incorrect. I ran some tests with `netaddr` upstream and it seems like the library works fine with any OUI, even OUIs with incorrectly encoded characters in them, etc.
To test this theory, you could run netaddr as follows to regenerate the indexes:
sudo python3 -m netaddr.eui.ieee
You would need to restart MAAS after doing this, since netaddr keeps the indexes cached in memory.