Conversation
1783918 to
f588621
Compare
In recent research with real hardware we have found our previous assumptions to be incorrect, so we are updating it to be controller = 1 and pcipf OR pcivf in the devlink port output[0]. [0]: https://docs.kernel.org/networking/devlink/devlink-port.html Signed-off-by: MJ Ponsonby <mj.ponsonby@canonical.com>
|
@crypticC0der the dqlite build error persists, I also checked on main branch. From my perspective this is likely technical debt in dqlite, which has now been forced into error by toolchain changes in resolute. To unblock this a tactical approach could be:
|
Signed-off-by: MJ Ponsonby <mj.ponsonby@canonical.com>
Why raise an issue when you can raise a PR |
|
the snapcraft change is based on not having this merged canonical/dqlite#875, so when it gets merged and added in a release we can remove it which will be nice |
|
Intriguing, now we have a Go crash |
Given it just passed after another retry it is likely this is the source of the intermittent test failure \o/. Let's deal with that separately though. |
|
Also, LP#2144987 |
In recent research with real hardware we have found our previous assumptions to be incorrect, so we are updating it to be controller = 1 and pcipf OR pcivf in the devlink port output 0 1.