Bug 1381691 - oadm diagnostics does not recognize flannel SDN - reports missing openvswitch as error
Summary: oadm diagnostics does not recognize flannel SDN - reports missing openvswitch...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oc
Version: 3.2.0
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
: ---
Assignee: Luke Meyer
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-04 18:24 UTC by Mark Lamourine
Modified: 2020-07-16 08:56 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-21 12:55:55 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Mark Lamourine 2016-10-04 18:24:41 UTC 
Description of problem:

When running 'oadm diagnostics' on an OCP 3.2 service using the flannel sdn an error is reported:

ERROR: [DS3002 from diagnostic UnitStatus@openshift/origin/pkg/diagnostics/systemd/unit_status.go:55]
       systemd unit atomic-openshift-node depends on unit openvswitch, which is not loaded.


Version-Release number of selected component (if applicable): 3.2


How reproducible:



Steps to Reproduce:
1. install OpenShift via openshift-ansible with flannel
2. on any master VM, run 'oadm diagnostics'
3.

Actual results:

oadm diagnostics
....
ERROR: [DS3002 from diagnostic UnitStatus@openshift/origin/pkg/diagnostics/systemd/unit_status.go:55]
       systemd unit atomic-openshift-node depends on unit openvswitch, which is not loaded.
...
[Note] Summary of diagnostics execution (version v3.2.1.15):
[Note] Warnings seen: 4
[Note] Errors seen: 1



Expected results:

No error reported


Additional info:
Comment 2 Stephen Cuppett 2019-11-21 12:55:55 UTC 
OCP 3.6-3.10 is no longer on full support [1]. Marking un-triaged bugs CLOSED DEFERRED. If you have a customer case with a support exception or have reproduced on 3.11+, please reopen and include those details. When reopening, please set the Version to the appropriate version where reproduced.

[1]: https://access.redhat.com/support/policy/updates/openshift
Note You need to log in before you can comment on or make changes to this bug.