Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[23.11] Adapt tests for upstream changes #765

Merged
merged 2 commits into from
Aug 10, 2023
Merged

Conversation

sysvinit
Copy link
Member

Upstream has changed the handling of guest network interfaces in the test library, which now unconditionally creates udev rules to force network interfaces to have specific names. Unfortunately these rules clash with and take precedence over our own rules in the platform, which means that a variety of tests were failing because network interfaces did not have the expected names.

This PR refactors the existing tests to use the new virtualisation.interfaces option, which allows us to explicitly specify the desired name for each interface.

@flyingcircusio/release-managers

Security implications

  • Security requirements defined? (WHERE)
    • The platform test suite should be kept compatible with the upstream test functionality to ensure that tests continue to run correctly
  • Security requirements tested? (EVIDENCE)
    • Tested manually in Hydra that tests previously disabled due to network-related failures now run again correctly.

As a side-effect of the introduction of the upstream
virtualisation.interfaces option for explicitly specifying the names
of interfaces in guest VMs, interfaces configured using the existing
virtualisation.vlans option now include udev rules which force the
name of the interface to ethX (for some vlan X). Due to ordering these
rules override the rules set in the platform, which means that network
interfaces are not named as expected within test VMs.

As there is no straightforward way to disable these extra udev rules,
refactor the tests to use the new virtualisation.interfaces option to
specify the required network interfaces with their desired names.
Remove the port number from the database URL, otherwise k3s's
postgresql driver will attempt to connect using TCP over the loopback.
@dpausp
Copy link
Member

dpausp commented Aug 10, 2023

Some tests are still broken. Will be fixed later.

@dpausp dpausp merged commit b033258 into pre-fc-23.11 Aug 10, 2023
@dpausp dpausp deleted the sysvinit/23.11-tests branch August 10, 2023 10:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants