CI: Molecule test starts to fail on master

[camilamacedo86]

Bug Report

What did you do?

The PR"s starts to report this issue.

What did you expect to see?

All CI jobs work well as expected

What did you see instead? Under which circumstances?

The make test-e2e-ansible-molecule finish with The job exceeded the maximum log length, and has been terminated. because it is falling. E.g prs:

• fix: modify olm-status-descriptor-test in scorecard #4009
• cleanup e2e: centralize the code to manage the prerequisites #3996

   TASK [Create the test.example.com/v1alpha1.SubresourcesTest] *******************
fatal: [localhost]: FAILED! => {"changed": true, "duration": 300, "method": "create", "msg": "Resource creation timed out", "result": {"apiVersion": "test.example.com/v1alpha1", "kind": "SubresourcesTest", "metadata": {"creationTimestamp": "2020-10-12T02:08:07Z", "generation": 1, "managedFields": [{"apiVersion": "test.example.com/v1alpha1", "fieldsType": "FieldsV1", "fieldsV1": {"f:spec": {".": {}, "f:execCommand": {}, "f:logMessage": {}}}, "manager": "OpenAPI-Generator", "operation": "Update", "time": "2020-10-12T02:08:07Z"}, {"apiVersion": "test.example.com/v1alpha1", "fieldsType": "FieldsV1", "fieldsV1": {"f:status": {".": {}, "f:conditions": {}}}, "manager": "ansible-operator", "operation": "Update", "time": "2020-10-12T02:12:13Z"}], "name": "subresources-test", "namespace": "osdk-test", "resourceVersion": "4472", "selfLink": "/apis/test.example.com/v1alpha1/namespaces/osdk-test/subresourcestests/subresources-test", "uid": "f1eed8a6-13cc-4747-90fe-f88bdf97eb48"}, "spec": {"execCommand": "echo 'hello world'", "logMessage": "Running..."}, "status": {"conditions": [{"lastTransitionTime": "2020-10-12T02:12:05Z", "message": "Running reconciliation", "reason": "Running", "status": "False", "type": "Running"}, {"ansibleResult": {"changed": 0, "completion": "2020-10-12T02:12:12.965865", "failures": 0, "ok": 0, "skipped": 0}, "lastTransitionTime": "2020-10-12T02:12:13Z", "message": "MODULE FAILURE\nSee stdout/stderr for the exact error", "reason": "Failed", "status": "True", "type": "Failure"}]}}}

[camilamacedo86]

c/c @asmacdo @fabianvf

[camilamacedo86]

The version of https://galaxy.ansible.com/community/kubernetes is not pinned and was released in the latest days. So, it might be related to it.

[joelanford]

I've been seeing this issue as well. I tried pinning community.kubernetes to 1.0.0 and then got a different error related to a timeout waiting for the bsycorp/kind container to be ready.

https://travis-ci.org/github/joelanford/operator-sdk/jobs/734733429#L2971

[asmacdo]

Should be fixed by #4014