← Back to issue list

travis: stop setting up testbr0 for lxd

View original Github issue

Metadata

Project
snapcraft
Number
#2148
Type
pull request
State
closed
Author
kyrofa
Labels
Created
Updated
Closed

Current evaluation

Closed and abandoned. The author proposed removing testbr0 setup for LXD 3.1 compatibility but later decided to maintain the LXD 3.0 track instead.

Suggested action:

No scores available.

Issue body

- [ ] Have you followed the [guidelines for contributing](https://github.com/snapcore/snapcraft/blob/master/CONTRIBUTING.md)? - [ ] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)? - [ ] If this is a bugfix. Have you checked that there is a bug report open for the issue you are trying to fix on [bug reports](https://bugs.launchpad.net/snapcraft)? - [ ] If this is a new feature. Have you discussed the design on the [forum](https://forum.snapcraft.io)? - [ ] Have you successfully run `./runtests.sh static`? - [ ] Have you successfully run `./runtests.sh unit`? ----- LXD 3.1 was recently released, and it doesn't like how we're configuring the network. Connectivity seems to work without it.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Closed and abandoned. The author proposed removing testbr0 setup for LXD 3.1 compatibility but later decided to maintain the LXD 3.0 track instead.
qwen3.6-35b-a3b-mtp-q6 Rejected. The maintainer closed the pull request, opting to remain on the LXD 3.0 track rather than updating Travis to stop configuring testbr0 for LXD 3.1.
qwen3.6-35b-a3b-mtp-q6 Rejected. The maintainer declined the network configuration change, deciding to remain on the LXD 3.0 track instead of upgrading to LXD 3.1, and closed the pull request without merging.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#2149 travis: use LXD from 3.0 track snapcraft merged Merged Travis CI configuration update switching to the LXD 3.0 track and removing the obsolete testbr0 setup. This resolves build failures caused by recent LXD networking changes. Approved by reviewer and passed CI checks.
81%