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

nocloud do not wait for known physical network interfaces to be up before configuring network #9871

Closed
Tracked by #9825
vills opened this issue Dec 3, 2024 · 2 comments · Fixed by #9865
Closed
Tracked by #9825
Assignees

Comments

@vills
Copy link

vills commented Dec 3, 2024

nocloud variant doesn't wait for all known to it (listed in config ethernets) to be up in State before configuring network. this cause server to be left in unreachable state.

Logs

talos-log.txt

Environment

  • Talos version: 1.8.3
  • Platform: nocloud
@smira
Copy link
Member

smira commented Dec 3, 2024

We can fail/reconcile on changes, but the code today doesn't seem to be good.

It looks like the log is cut a bit, it doesn't have anything coming from udevd.

@vills
Copy link
Author

vills commented Dec 3, 2024

Oooops. Wrong log uploaded. Here is the correct one -
talos-log-2.txt

And network_config as well:

version: 2
bonds:
  aggi:
    interfaces:
    - int0
    - int1
    addresses:
    - 10.26.98.92/29
    parameters:
      mode: 802.3ad
      lacp-rate: slow
      mii-monitor-interval: 100
      up-delay: 200
      down-delay: 200
      transmit-hash-policy: layer3+4
    routes:
    - to: 10.0.0.0/8
      via: 10.26.98.91
    - to: 192.168.0.0/16
      via: 10.26.98.91
    - to: 188.42.208.0/21
      via: 10.26.98.91
  agge:
    interfaces:
    - ext0
    - ext1
    addresses:
    - 188.42.48.188/29
    parameters:
      mode: 802.3ad
      lacp-rate: slow
      mii-monitor-interval: 100
      up-delay: 200
      down-delay: 200
      transmit-hash-policy: layer3+4
    gateway4: 188.42.48.187
ethernets:
  int0:
    match:
      macaddress: a0:36:9f:e6:49:30
  int1:
    match:
      macaddress: a0:36:9f:e5:06:d4
  ext0:
    match:
      macaddress: a0:36:9f:e6:49:32
  ext1:
    match:
      macaddress: a0:36:9f:e5:06:d6

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 a pull request may close this issue.

2 participants