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

Bug 1990631: ovnkube: use ovn-nbctl daemon monitor mode to restart and log issues #1182

Merged
merged 1 commit into from Aug 27, 2021

Commits on Aug 16, 2021

  1. ovnkube: use ovn-nbctl daemon monitor mode to restart and log issues

    If the ovn-nbctl daemon has problems and dies monitor mode will restart
    it for us and log about the problem. Would help stability and debug
    issues like:
    
    utils.go:236] Gateway router GR_worker-0.ostest.test.metalkube.org does not have load balancer (OVN command '/usr/bin/ovn-nbctl --timeout=15 --data=bare --no-heading --columns=_uuid find load_balancer external_ids:UDP_lb_gateway_router=GR_worker-0.ostest.test.metalkube.org' failed: signal: alarm clock)
    services_controller.go:210] "Error syncing service, retrying" service="e2e-webhook-856/e2e-test-webhook" err="unable to create load balancer: stderr: 2021-08-10T19:19:03Z|00001|fatal_signal|WARN|terminating with signal 14 (Alarm clock)\n, err: OVN command '/usr/bin/ovn-nbctl --timeout=15 set load_balancer 3c704510-997b-42b0-962d-fdb8d9f12ab3 vips:\"172.30.37.42:8443\"=\"\"' failed: signal: alarm clock"
    dcbw committed Aug 16, 2021
    Copy the full SHA
    7d4bef3 View commit details
    Browse the repository at this point in the history