fips_check: Don't hardcode number of nodes

[mrunalp]

This is to unblock the fips job for now.
We have to follow up with checks that make
sure that the expected number of nodes
are up before running checks and tests.

Signed-off-by: Mrunal Patel mrunalp@gmail.com

[mrunalp]

/retest

[openshift-ci-robot]

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

Test name	Commit	Details	Rerun command
ci/rehearse/openshift/installer/release-4.4/e2e-azure-shared-vpc	d6fe111	link	/test pj-rehearse
ci/rehearse/openshift/cluster-network-operator/master/e2e-gcp-ovn	d6fe111	link	/test pj-rehearse
ci/rehearse/openshift/cluster-etcd-operator/master/e2e-aws-disruptive	d6fe111	link	/test pj-rehearse
ci/prow/pj-rehearse	d6fe111	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.

[smarterclayton]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mrunalp, smarterclayton

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/templates/openshift/installer/OWNERS [smarterclayton]

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

[openshift-ci-robot]

@mrunalp: Updated the following 4 configmaps:

• prow-job-cluster-launch-installer-e2e configmap in namespace ci at cluster api.ci using the following files:
  • key cluster-launch-installer-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml
• prow-job-cluster-launch-installer-e2e configmap in namespace ci at cluster app.ci using the following files:
  • key cluster-launch-installer-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml
• prow-job-cluster-launch-installer-e2e configmap in namespace ci at cluster build01 using the following files:
  • key cluster-launch-installer-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml
• prow-job-cluster-launch-installer-e2e configmap in namespace ci at cluster build02 using the following files:
  • key cluster-launch-installer-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml

Details

In response to this:

This is to unblock the fips job for now.
We have to follow up with checks that make
sure that the expected number of nodes
are up before running checks and tests.

Signed-off-by: Mrunal Patel mrunalp@gmail.com

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.