Good morning,
I’m moving my last piece of infrastructure from Proxmox now that I can get the Incus Agent on vyos. I have create OVS Bridges to attach to the VM in my network project, however I get this error when trying to use nic and type as network. I also cannot modify the default project to make networks false
❯ incus profile edit overseer
Config parsing error: Device validation failed for "INTRA": Failed loading device "INTRA": Failed to load network "ovs-br0" for project "default": Network not found
This is the profile I set
│ File: overseer-2
───────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────────
1 │ config: {}
2 │ description: ""
3 │ devices:
4 │ BOND1:
5 │ address: "01:00.0"
6 │ type: pci
7 │ BOND2:
8 │ address: "01:00.1"
9 │ type: pci
10 │ INTRA:
11 │ network: ovs-br0
12 │ type: nic
13 │ WAN:
14 │ address: "03:00.0"
15 │ type: pci
16 │ name: overseer-0
17 │ used_by: []
18 │ project: networking
| NAME | IMAGES | PROFILES | STORAGE VOLUMES | STORAGE BUCKETS | NETWORKS | NETWORK ZONES | DESCRIPTION | USED BY |
+-------------------+--------+----------+-----------------+-----------------+----------+---------------+-----------------------+---------+
| default | YES | YES | YES | YES | YES | YES | Default Incus project | 1 |
+-------------------+--------+----------+-----------------+-----------------+----------+---------------+-----------------------+---------+
| infra | NO | NO | NO | NO | NO | NO | Infra Support Project | 0 |
+-------------------+--------+----------+-----------------+-----------------+----------+---------------+-----------------------+---------+
| network (current) | NO | YES | YES | YES | NO | NO | Networking Project | 2 |
+-------------------+--------+----------+-----------------+-----------------+----------+---------------+-----------------------+---------+
| serv | NO | NO | NO | NO | NO | NO | services project | 0 |
Networks
❯ incus network ls
+-------------+----------+---------+------+------+-------------+---------+-------+
| NAME | TYPE | MANAGED | IPV4 | IPV6 | DESCRIPTION | USED BY | STATE |
+-------------+----------+---------+------+------+-------------+---------+-------+
| bridge0 | bridge | NO | | | | 0 | |
+-------------+----------+---------+------+------+-------------+---------+-------+
| eno1 | physical | NO | | | | 0 | |
+-------------+----------+---------+------+------+-------------+---------+-------+
| lo | loopback | NO | | | | 0 | |
+-------------+----------+---------+------+------+-------------+---------+-------+
| ovs-br0 | bridge | NO | | | | 0 | |
+-------------+----------+---------+------+------+-------------+---------+-------+
| ovs-eminent | bridge | NO | | | | 0 | |
+-------------+----------+---------+------+------+-------------+---------+-------+
| ovs-infra | bridge | NO | | | | 0 | |
+-------------+----------+---------+------+------+-------------+---------+-------+
| ovs-iot | bridge | NO | | | | 0 | |
+-------------+----------+---------+------+------+-------------+---------+-------+
| ovs-mgmt | bridge | NO | | | | 0 | |
+-------------+----------+---------+------+------+-------------+---------+-------+
| ovs-serv | bridge | NO | | | | 0 | |
+-------------+----------+---------+------+------+-------------+---------+-------+
| ovs-system | unknown | NO | | | | 0 | |
+-------------+----------+---------+------+------+-------------+---------+-------+
| ovs-work | bridge | NO | | | | 0 | |
+-------------+----------+---------+------+------+-------------+---------+-------+