Openshift Action Pack job is failing with error - error: unknown flag: --config

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Openshift Action Pack job PCK.AUTOMIC_OPENSHIFT.PUB.ACTION.GET_RESOURCE is failing with the error message in the report log below.

oc --config "E:\Automic\Agents\Windows\temp\0002547210\config" login "https://casplda02:6443" --token=sha256~y2vfU85NWpnRXs1v2zKs06XDkKc5Gzxs5225yl1SJBQ

error: unknown flag: --config

See 'oc login --help' for usage.

Environment

Release : 12.3.x, 21.x

Cause

Environmental issue

Resolution

Based on the log, it is failing when the command oc is executed with the option "--config".

================================================================================================================

"********************************"

"** EXECUTION START **"

"********************************"

""

oc --config "E:\Automic\Agents\Windows\temp\0002547210\config" login "https://casplda02:6443" --token=sha256~y2vfU85NWpnRXs1v2zKs06XDkKc5Gzxs5225yl1SJBQ

error: unknown flag: --config

See 'oc login --help' for usage.

================================================================================================================

According to the "oc config --help", parameters that goes with oc command and the option "--config" with hypens is not valid. Please see the output from the "oc config --help".

===================================================================================================================

C:\Automic\openshift-client-windows-4.9.9>oc config --help

Modify kubeconfig files using subcommands like "oc config set current-context my-context"

The loading order follows these rules:

If the --kubeconfig flag is set, then only that file is loaded. The flag may only be set once and no merging takes

place.

If $KUBECONFIG environment variable is set, then it is used as a list of paths (normal path delimiting rules for

your system). These paths are merged. When a value is modified, it is modified in the file that defines the stanza. When

a value is created, it is created in the first file that exists. If no files in the chain exist, then it creates the

last file in the list.

Otherwise, ${HOME}/.kube/config is used and no merging takes place.

Usage:

oc config SUBCOMMAND [flags]

Available Commands:

current-context Display the current-context

delete-cluster Delete the specified cluster from the kubeconfig

delete-context Delete the specified context from the kubeconfig

delete-user Delete the specified user from the kubeconfig

get-clusters Display clusters defined in the kubeconfig

get-contexts Describe one or many contexts

get-users Display users defined in the kubeconfig

rename-context Rename a context from the kubeconfig file

set Set an individual value in a kubeconfig file

set-cluster Set a cluster entry in kubeconfig

set-context Set a context entry in kubeconfig

set-credentials Set a user entry in kubeconfig

unset Unset an individual value in a kubeconfig file

use-context Set the current-context in a kubeconfig file

view Display merged kubeconfig settings or a specified kubeconfig file

Use "oc <command> --help" for more information about a given command.

Use "oc options" for a list of global command-line options (applies to all commands).

===================================================================================================================

In order to move forward with this issue, please trace where the command "oc -config" is being defined and replace it with the correct option. Also, Broadcom's support can only provide a best-effort support because the Action Packs for OpenShift objects(open source from github) are not developed directly by Broadcom's developers but by external personnel. Thus, it is only supported by Broadcom's community. I also suggest that you post also this issue on our community and git-hub.

Broadcom's community:

https://community.broadcom.com/enterprisesoftware/home

Github:

https://github.com/Automic-Community/Openshift-Action-Pack

Thanks

Bobby