Bug 1316302 - [RFE] Diagnostics pod that can be deployed to test a new nodes and successful install.
Summary: [RFE] Diagnostics pod that can be deployed to test a new nodes and successful...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Luke Meyer
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-09 22:38 UTC by Ryan Howe
Modified: 2019-10-10 11:30 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-31 11:30:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ryan Howe 2016-03-09 22:38:07 UTC
Description of problem:

  - Requesting a quickstart template that would deploy a pod that runs on all nodes or a single node that would test for a successful install of the cluster or addition of a node. 

         - Ensures pods have access to external network
         - Makes sure that DNS is configured
         - Checks if services are started and interfaces configured 
         - Runs `openshift ex diagnostics`

Comment 1 Luke Meyer 2016-04-14 17:12:16 UTC
This would be an enhancement of the existing diagnostic DiagnosticPod. It doesn't run on all nodes or check external connectivity yet.

BTW tell people to use "oadm diagnostics" - it's graduated from experimental status.

To test external connectivity requires a viable external target to attempt to connect to, as well as awareness of any proxy params. Do you have an opinion on what external target would be acceptable? "www.google.com" perhaps. The other complication is that the customer may not *want* external connectivity, and I don't know of a good way to detect that intent. So this would probably be a warning if it failed.

What do you mean by services started and interfaces configured? Which services and which interfaces? Are you thinking this test pod would have privileged access to everything on the node and basically run a local "oadm diagnostics" on every node?

Comment 2 Ryan Howe 2016-08-19 19:47:47 UTC
The latest command checks DNS and network. I'm fine with this being closed


Note You need to log in before you can comment on or make changes to this bug.