Skip to content

LXC: Network tests in CI fail due to not receiving an IPv4 address #1274

Description

@theelliotm

Relevant area(s)

Linux

Brief description of your issue

On the RHEL-10 LXC tests, containers aren't receiving IPv4 addresses, and all network tests fail.

Either documentation needs to be updated to reflect how a RHEL system should be configured to use bubblewrap, and/or the CI images need to be updated to reflect documentation.

Steps to reproduce

Run Scheduled Validation Tests under the nightly trigger.

Expected behavior

All bubblewrap containers receive IPv4 addresses.

Actual behavior

Bubblewrap containers are not receiving IPv4 addressses.

Received error in CI job:

Error: Container did not receive an IPv4 address within 30s; check that lxc-net/dnsmasq is running and able to assign one. A bridge offering only IPv6 leaves the container unable to reach the IPv4 destinations its policy names.
Container did not receive an IPv4 address within 30s; check that lxc-net/dnsmasq is running and able to assign one. A bridge offering only IPv6 leaves the container unable to reach the IPv4 destinations its policy names.
{"error":{"code":"backend_error","message":"Container did not receive an IPv4 address within 30s; check that lxc-net/dnsmasq is running and able to assign one. A bridge offering only IPv6 leaves the container unable to reach the IPv4 destinations its policy names."}}

for the following tests:

  • LXC Network IPv6+CIDR
  • LXC Network Invalid CIDR
  • LXC Network Dual-Stack Hostname
  • LXC Network CIDR Boundary
  • LXC Network Enforcement
  • LXC Network Schema 0.7
  • LXC Network GA Egress (0.8)
  • LXC Network 0.8 Omitted Network Section
  • LXC Network 0.8 Deny-All Loopback
  • LXC Network Deny Precedence
  • LXC Network Proxy
  • LXC Network Proxy Hostname (off-host)
  • LXC Network Proxy Reuse
  • LXC Network Preserve Policy
  • LXC Network Reuse Tightening
  • LXC Network Reuse Loosening
  • LXC Inbound Default-Deny
  • LXC Inbound Traffic
  • LXC Network Legacy Default-Allow v0.8 Compatibility

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Backend-LXCLinux container isolation implemented with LXC.Issue-BugSomething is not working as intended.OS-LinuxApplies specifically to Linux hosts or Linux behavior.Priority2High-impact issue affecting key functionality; prioritize for the next appropriate release.Release v1.0Issues tracked for the version 1.0 release

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions