super-linter: Cannot find rules files - FATAL

Describe the bug A clear and concise description of what the bug is. Log:

2020-11-02 16:52:17 [INFO]   Gathering user validation information...
2020-11-02 16:52:17 [INFO]   - Only validating [new], or [edited] files in code base...
2020-11-02 16:52:17 [FATAL]     -> ANSIBLE_LINTER_RULES rules file () doesn't exist. Terminating...

To Reproduce Steps to reproduce the behavior:

Go to ‘.github/linters’
Leave only the necessary rules (eg. .yaml-lint.yml)
Run job
See error

Expected behavior Add only necessary linters rules to .github/linters

Screenshots If applicable, add screenshots to help explain your problem.

Additional context It looks like all rules should be added to .github/linters

Upon adding .ansible-lint.yml:

2020-11-02 17:39:25 [INFO]   User provided file:[/github/workspace/.github/linters/.ansible-lint.yml] exists, setting rules file...
2020-11-02 17:39:25 [FATAL]     -> CLOUDFORMATION_LINTER_RULES rules file () doesn't exist. Terminating..`

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 52
Comments: 25 (7 by maintainers)

Commits related to this issue

Create super-linter.yml Adds most basic super-linter config to demonstrate [github/super-linter#938](https://github.com/github/super-linter/issues/938). This is copy/pasted from marketplace instructi... — committed to shgysk8zer0/super-linter-test by shgysk8zer0 4 years ago
Apply workaround for GitHub Super Linter See https://github.com/github/super-linter/issues/938 — committed to WeblateOrg/meta by nijel 4 years ago
Pin super-linter version to avoid the issue described in https://github.com/github/super-linter/issues/938 — committed to solvaholic/octodns-sync by solvaholic 4 years ago

Most upvoted comments

You can use actions from docker image to lock to a specific version:

uses: docker://github/super-linter:v3.13.1

+14

dec5e on Nov 3, 2020

#950 solved this

admiralAwkbar on Nov 3, 2020

@solvaholic thanks for the info!

admiralAwkbar on Nov 3, 2020

When I build from bdc7aa6a1a90fb89c50ef5b8ba9d7ba511981a20 (current master, also the v3.13.4 release) I get success.

Re-running the failed job in Actions still got a ❌ :

2020-11-03 15:21:27 [INFO]   Gathering user validation information...
2020-11-03 15:21:27 [INFO]   - Only validating [new], or [edited] files in code base...
2020-11-03 15:21:28 [FATAL]     -> ANSIBLE_LINTER_RULES rules file () doesn't exist. Terminating...

I see similar failure when I docker pull ghcr.io/github/super-linter:v3 and run that. So I think the v3 docker image is not really the latest v3 release, maybe as described in https://github.com/github/super-linter/issues/708.

edit: oic this conversation’s been had. I’d missed some issue updates, am catching up now. 🤦

solvaholic on Nov 3, 2020

The only issue with that workaround is dependabot will no longer see this as a Github Action dependency and so will no longer alert when there’s a new version of the super-linter. But as a workaround it’s better than every run being broken for now…

tunetheweb on Nov 3, 2020

tldr: for github actions/workflows, v3.13.1 appears to work, and v3.13.2 doesn’t exist. (current v3 is v3.13.3.)

hopefully this is helpful for folks to work around this for now, and helpful in terms of narrowing down cause(s).

Seems to be working for me with v3.13.1 on one of our projects. Our last successful lint (from a few days ago) had this in the output:

2020-10-31 01:10:52 [INFO  ]   --- GitHub Actions Multi Language Linter ----
2020-10-31 01:10:52 [INFO  ]    - Image Creation Date:[2020-10-15T21:59:46Z]
2020-10-31 01:10:52 [INFO  ]    - Image Revision:[21eea65]
2020-10-31 01:10:52 [INFO  ]    - Image Version:[v3]

and that git revision matches v3.13.1 in https://github.com/github/super-linter/releases .

Here’s the version info from a failing build with :v3 a few hours ago (revision for 3.13.3):

2020-11-02 21:26:35 [INFO]    - Image Creation Date:[2020-11-02T15:17:06Z]
2020-11-02 21:26:35 [INFO]    - Image Revision:[5a04bd9]

an aside about 3.13.2

I’d wondered why it was using .1 despite the fact that .2 was tagged a while ago, but I tried a build with v3.13.2 (aftrer confirming that .1 worked) and it looks like the docker image for that wasn’t built/released:


Pull down action image 'github/super-linter:v3.13.2'
  /usr/bin/docker pull github/super-linter:v3.13.2
  Error response from daemon: manifest for github/super-linter:v3.13.2 not found: manifest unknown: manifest unknown
  Warning: Docker pull failed with exit code 1, back off 5.111 seconds before retry.
  /usr/bin/docker pull github/super-linter:v3.13.2
  Error response from daemon: manifest for github/super-linter:v3.13.2 not found: manifest unknown: manifest unknown
  Warning: Docker pull failed with exit code 1, back off 5.981 seconds before retry.
  /usr/bin/docker pull github/super-linter:v3.13.2
  Error response from daemon: manifest for github/super-linter:v3.13.2 not found: manifest unknown: manifest unknown
Error: Docker pull failed with exit code 1

edited to add logs:
these truncated logs don’t show much more than what i have described above, but just in case:

lintlog-fail.txt lintlog-working.txt

mtigas on Nov 2, 2020

I also tried downgrading to v3.12.0 and am getting the same error

dmerrick on Nov 2, 2020

I saw this same error, copied the cfnlintrc.yml from template linter configs, and it’s now reporting the same issue but for Dart.

It seems that all config files are expected and any missing file will result in this error.

shgysk8zer0 on Nov 2, 2020