Add ROSA HCP testing for File Integrity Operator

[rhmdnd]

This commit adds a test config for running FIO on ROSA HCP.

[rhmdnd]

/pj-rehearse pull-ci-openshift-file-integrity-operator-master-e2e-rosa

[openshift-ci-robot]

@rhmdnd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[rhmdnd]

/pj-rehearse pull-ci-openshift-file-integrity-operator-master-e2e-rosa

[openshift-ci-robot]

@rhmdnd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[rhmdnd]

/pj-rehearse pull-ci-openshift-file-integrity-operator-master-e2e-rosa

[openshift-ci-robot]

@rhmdnd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[xiaojiey]

/hold for test

[rhmdnd]

This will need to go hand-in-hand with openshift/file-integrity-operator#539

[rhmdnd]

/pj-rehearse pull-ci-openshift-file-integrity-operator-master-e2e-rosa

Should be good to exercise this now that we landed openshift/file-integrity-operator#539

[openshift-ci-robot]

@rhmdnd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[rhmdnd]

Still hitting some issues - we'll have to recreate locally:

 === RUN   TestFileIntegrityLogAndReinitDatabase
    helpers.go:430: TEST SETUP: failed to add custom resource scheme to framework: failed to build the dynamic client: timed out waiting for the condition
--- FAIL: TestFileIntegrityLogAndReinitDatabase (10.25s) 

[rhmdnd]

/pj-rehearse

[openshift-ci-robot]

@rhmdnd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[rhmdnd]

/pj-rehearse pull-ci-openshift-file-integrity-operator-master-e2e-rosa

[openshift-ci-robot]

@rhmdnd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[rhmdnd]

/pj-rehearse pull-ci-openshift-file-integrity-operator-master-e2e-rosa

[rhmdnd]

/pj-rehearse pull-ci-openshift-file-integrity-operator-master-e2e-rosa

[openshift-ci-robot]

@rhmdnd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-ci-robot]

@rhmdnd, pj-rehearse: unable prepare a candidate for rehearsal; rehearsals will not be run. This could be due to a branch that needs to be rebased. ERROR:

couldn't rebase candidate onto master: %!w(<nil>)

[rhmdnd]

/pj-rehearse pull-ci-openshift-file-integrity-operator-master-e2e-rosa

[openshift-ci-robot]

@rhmdnd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[yuumasato]

/lgtm

The e2e test is running and the fail comes from an actual test, not an infrastructure fail..

[rhmdnd]

@xiaojiey should be ready for another round of reviews.

[rhmdnd]

Adding in the optional label so this e2e test doesn't block us from merging patches while we smooth out the ROSA support.

[rhmdnd]

/pj-rehearse ack

[openshift-ci-robot]

@rhmdnd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-ci-robot]

[REHEARSALNOTIFIER]
@rhmdnd: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
pull-ci-openshift-file-integrity-operator-master-e2e-rosa	openshift/file-integrity-operator	presubmit	Presubmit changed
pull-ci-openshift-file-integrity-operator-master-ci-index-file-integrity-operator-bundle	openshift/file-integrity-operator	presubmit	Ci-operator config changed
pull-ci-openshift-file-integrity-operator-master-e2e-aws	openshift/file-integrity-operator	presubmit	Ci-operator config changed
pull-ci-openshift-file-integrity-operator-master-e2e-bundle-aws	openshift/file-integrity-operator	presubmit	Ci-operator config changed
pull-ci-openshift-file-integrity-operator-master-e2e-bundle-aws-upgrade	openshift/file-integrity-operator	presubmit	Ci-operator config changed
pull-ci-openshift-file-integrity-operator-master-go-build	openshift/file-integrity-operator	presubmit	Ci-operator config changed
pull-ci-openshift-file-integrity-operator-master-images	openshift/file-integrity-operator	presubmit	Ci-operator config changed
pull-ci-openshift-file-integrity-operator-master-unit	openshift/file-integrity-operator	presubmit	Ci-operator config changed
pull-ci-openshift-file-integrity-operator-master-verify	openshift/file-integrity-operator	presubmit	Ci-operator config changed

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[Vincent056]

/pj-rehearse pull-ci-openshift-file-integrity-operator-master-e2e-rosa

[openshift-ci-robot]

@Vincent056: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[Vincent056]

/lgtm

[Vincent056]

cluster set up was successful, let's fix the failing test in other pr

[xiaojiey]

/lgtm
The e2e failure was caused by
Cannot create a test MC: no kind is registered for the type v1.MachineConfig in scheme "github.com/openshift/file-integrity-operator/tests/framework/framework.go:141"

BTW, I was able to install FIO successfully with a nodeSelector config in the subscription.

% cat ~/func/co_install_rosa_hcp.yaml 
---
apiVersion: v1
kind: Namespace
metadata:
  labels:
    openshift.io/cluster-monitoring: "true"
    pod-security.kubernetes.io/enforce: privileged 
  name: openshift-compliance
---
apiVersion: operators.coreos.com/v1
kind: OperatorGroup
metadata:
  name: compliance-operator
  namespace: openshift-compliance
spec:
  targetNamespaces:
  - openshift-compliance
---
apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: compliance-operator-sub
  namespace: openshift-compliance
spec:
  channel: "stable"
  installPlanApproval: Automatic
  name: compliance-operator
  source: compliance-operator
  sourceNamespace: openshift-marketplace
  config:
    nodeSelector:
      node-role.kubernetes.io/worker: ""
% oc apply -f fio_install_r_rosa_hcp.yaml 
namespace/openshift-file-integrity created
operatorgroup.operators.coreos.com/openshift-file-integrity-qbcd created
subscription.operators.coreos.com/file-integrity-operator created
% oc project openshift-file-integrity
Now using project "openshift-file-integrity" on server "https://api.n9928-8a5vj-949.ak3p.p3.openshiftapps.com:443".
% oc get csv
NAME                             DISPLAY                   VERSION   REPLACES                         PHASE
file-integrity-operator.v1.3.4   File Integrity Operator   1.3.4     file-integrity-operator.v1.3.3   Succeeded
% oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.15.23   True        False         3h38m   Cluster version is 4.15.23
% oc get pod
NAME                                       READY   STATUS    RESTARTS      AGE
file-integrity-operator-5ddf87777c-bfmdc   1/1     Running   1 (53s ago)   60s
% oc apply -f ~/func/fileintegrity.yaml 
fileintegrity.fileintegrity.openshift.io/example-fileintegrity created
% oc get fileintegrity example-fileintegrity -o=jsonpath={.status.phase}
Active%                                                                                                                                                                                                             % oc get fileintegritynodestatus   
NAME                                               NODE                         STATUS
example-fileintegrity-ip-10-0-1-238.ec2.internal   ip-10-0-1-238.ec2.internal   Succeeded
example-fileintegrity-ip-10-0-1-88.ec2.internal    ip-10-0-1-88.ec2.internal    Succeeded

[xiaojiey]

/unhold

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rhmdnd, Vincent056, xiaojiey, yuumasato

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/config/openshift/file-integrity-operator/OWNERS [Vincent056,rhmdnd,xiaojiey,yuumasato]
• ci-operator/jobs/openshift/file-integrity-operator/OWNERS [Vincent056,rhmdnd,xiaojiey,yuumasato]

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

[rhmdnd]

/pj-rehearse ack

[openshift-ci-robot]

@rhmdnd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-ci]

@rhmdnd: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/rehearse/openshift/file-integrity-operator/master/e2e-rosa	b9fe423	link	unknown	/pj-rehearse pull-ci-openshift-file-integrity-operator-master-e2e-rosa

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-sigs/prow repository. I understand the commands that are listed here.