Bug introduced in https://github.com/vyos/vyos-1x/commit/dff5f3f38f60b9da8e791593998e6f614da6e5ec into 1.2 tree.
Description
Details
- Difficulty level
- Easy (less than an hour)
- Version
- 1.2-rolling-201909220118
- Why the issue appeared?
- Will be filled on close
- Is it a breaking change?
- Behavior change
- Issue type
- Bug (incorrect behavior)
Event Timeline
Has this been merged into 1.2, or just 1.3? Because all of the 1.2-rolling images currently available from downloads.vyos.io right now have this bug in them :-(
It's in 1.2 rolling too, but the iso has to rebuild. You can alternatively download and manually install http://dev.packages.vyos.net/repositories/current/vyos/pool/main/v/vyos-1x/vyos-1x_1.3.0-16_all.deb.
That's fixed the problem we had, but we've encountered some other strangeness.
First boot into 201909231545 took about 20 minutes for VyOS to be pingable. It was clear that eth1 and eth3 were not the right devices. Looking through logs gave all sorts of mess:
Second boot into 201909231545 and eth3 was named _ instead:
We ran ip link set name eth3 dev _ and did a load /config/config.new and all was well again.
Haven't had a proper chance to delve into why the interface renaming is a problem during boot.