Description of problem: "oc adm diagnostics all" is always failed with "provided options object is not a PodLogOptions" to run network diags test pods on a Disconnected OCP environment, even though the test image URL is specified correctly using "--networkcheck-test-pod-image". I've also checked a previous bugzilla[0] which is closed about this issue. BUT the issue is existing until now after published Errata resolved this issue. The case[0] was private mode, so I create newly bug ticket to discuss here instead of opening the closed case again. e.g.> $ sudo oc adm diagnostics all \ --appcreate-app-image='int.registry.example.com:5000/openshift3/ose-deployer:v3.11.146' \ --networkcheck-test-pod-image='int.registry.example.com:5000/openshift3/ose-deployer:v3.11.146' \ --diagnosticpod-images='int.registry.example.com:5000/openshift3/ose-${component}:${version}' \ --diaglevel=0 ~~~ : [Note] Running diagnostic: NetworkCheck Description: Create a pod on all schedulable nodes and run network diagnostics from the application standpoint ERROR: [DNet2005 from diagnostic NetworkCheck@openshift/origin/pkg/oc/cli/admin/diagnostics/diagnostics/cluster/network/run_pod.go:202] Setting up test environment for network diagnostics failed: Failed to run network diags test pod and service: Failed to run network diags test pods, failed: 24, total: 24, fetching logs failed: [provided options object is not a PodLogOptions, provided options object is not a PodLogOptions, provided options object is not a PodLogOptions, provided options object is not a PodLogOptions, provided options object is not a PodLogOptions, provided options object is not a PodLogOptions, provided options object is not a PodLogOptions, provided options object is not a PodLogOptions, provided options object is not a PodLogOptions, provided options object is not a PodLogOptions, provided options object is not a PodLogOptions, provided options object is not a PodLogOptions, provided options object is not a PodLogOptions, provided options object is not a PodLogOptions, provided options object is not a PodLogOptions, provided options object is not a PodLogOptions, provided options object is not a PodLogOptions, provided options object is not a PodLogOptions, provided options object is not a PodLogOptions, provided options object is not a PodLogOptions, provided options object is not a PodLogOptions, provided options object is not a PodLogOptions, provided options object is not a PodLogOptions, provided options object is not a PodLogOptions] : ~~~ [0] networkcheck diagnostics test pods die if test pod image is pulled from on-prem/disconnected registry (and work if pulled from registry.access.redhat.com) [ https://bugzilla.redhat.com/show_bug.cgi?id=1600741 ] Version-Release number of selected component (if applicable): OpenShift v3.11.146 How reproducible: You can always reproduce when you execute "oc adm diagnostics all --appcreate-app-image=... --networkcheck-test-pod-image=... --diagnosticpod-images=..." in a disconnected OpenShift system. Steps to Reproduce: 1. 2. 3. Actual results: "NetworkCheck" is always failed to run test pods with "provided options object is not a PodLogOptions" error messages in disconnected OpenShift cluster. Expected results: "NetworkCheck" is successful to run test pods without "Failed to run network diags test pods, failed: 24, total: 24, fetching logs failed ..." error messages in disconnected OpenShift cluster. Additional info: This issue has been reported here[0] and has been resolved by This errata[1](OCP 3.11.117), BUT the issue is happening as always until now (OCP 3.11.146). [0] networkcheck diagnostics test pods die if test pod image is pulled from on-prem/disconnected registry (and work if pulled from registry.access.redhat.com) [ https://bugzilla.redhat.com/show_bug.cgi?id=1600741 ] [1] RHBA-2019:1605 - Bug Fix Advisory [ https://access.redhat.com/errata/RHBA-2019:1605 ] - OCP 3.11.117
Sending this over to Luke who owns the diagnostics tooling.
This bug hasn't had any engineering activity in the last ~30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale". If you have further information on the current state of the bug, please update it and remove the "LifecycleStale" keyword, otherwise this bug will be automatically closed in 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
This bug hasn't had any activity 7 days after it was marked as LifecycleStale, so we are closing this bug as WONTFIX. If you consider this bug still valuable, please reopen it or create new bug.
In the queue waiting for its merge turn.
It's still waiting for it's turn to merge.
Checked with latest oc version: oc v3.11.235, still could reproduce the issue now. will check it later with v3.11.242 . So change status to modified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2990