ci-operator/step-registry/gather/aws-console: Allow missing kubeconfig

[wking]

@abhinavdahiya pointed out that there may be some IDs in the SHARED_DIR file, and when there are, we can gather those even if we lack a kubeconfig to extract additional IDs from within the cluster.

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wking

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• ci-operator/step-registry/gather/aws-console/OWNERS [wking]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[wking]

/assign @cgwalters

[wking]

registration-operator e2e looks fine. e2e-aws-csi suggests we may also want to make cluster-API calls non-fatal, so we still gather SHARED_DIR-provided IDs even when we have a kubeconfig but cannot reach the cluster. However, I also want to hear about it (by failing the step) if these fail because we somehow flub the command itself. I'm not sure how to distinguish between "failed because the cluster was dead/unreachable" and "failed because we need to tweak the step command". If folks feel like I should add || echo 'failed to get IDs from nodes and similar catchers and not worry about the "we need to tweak the step but don't notice because we're ignoring those errors" case, let me know.

[openshift-merge-robot]

@wking: The following tests failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
ci/rehearse/openshift/aws-ebs-csi-driver/release-4.5/e2e-aws-csi	ad42349	link	/test pj-rehearse
ci/rehearse/open-cluster-management/registration-operator/master/e2e	ad42349	link	/test pj-rehearse
ci/rehearse/openshift/aws-ebs-csi-driver/master/e2e-aws-csi	ad42349	link	/test pj-rehearse
ci/rehearse/kubevirt/hyperconverged-cluster-operator/release-1.2/hco-e2e-image-index-aws	ad42349	link	/test pj-rehearse
ci/rehearse/openshift/oc/release-4.2/e2e-cmd	ad42349	link	/test pj-rehearse
ci/rehearse/openshift-knative/serverless-operator/master/4.6-upstream-e2e-aws-ocp-46	ad42349	link	/test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-aws-proxy	ad42349	link	/test pj-rehearse
ci/rehearse/openshift/origin/master/e2e-aws-proxy	ad42349	link	/test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-aws-shared-vpc	ad42349	link	/test pj-rehearse
ci/rehearse/openshift/cluster-logging-operator/master/e2e-operator	ad42349	link	/test pj-rehearse
ci/rehearse/openshift/cluster-etcd-operator/master/e2e-agnostic	ad42349	link	/test pj-rehearse
ci/prow/pj-rehearse	ad42349	link	/test pj-rehearse
ci/rehearse/openshift/kubernetes/master/e2e-aws-selfupgrade	ad42349	link	/test pj-rehearse

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.