Super-linter: Cannot find rules files - FATAL

Created on 2 Nov 2020 · 25Comments · Source: github/super-linter

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..`

bug

Source

denis-matchenko

👍47 👀6

Most helpful comment

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

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

dec5e on 3 Nov 2020

🎉6 👍5 ❤3

All 25 comments

+1, the same issue for https://github.com/actions/virtual-environments

maxim-lobanov on 2 Nov 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 2 Nov 2020

👍1

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

dmerrick on 2 Nov 2020

👍1

@dmerrick I'm looking for an exact version number for when this passed in a PR just 6 hours ago, but the best I could find was in Pull github/super-linter:v3 which contained "Digest: sha256:b5b43c0f80224919968b1482b48d82c2424cf596e09468917025575a6bf110d2".

shgysk8zer0 on 2 Nov 2020

ACTIONS_RUNNER_DEBUG: true log:

4_Lint Code Base.txt

denis-matchenko on 2 Nov 2020

Same issue here
2020-11-02 20:25:05 [FATAL] -> ANSIBLE_LINTER_RULES rules file () doesn't exist. Terminating...

brndnwng on 2 Nov 2020

How are you running super-linter? After building the latest master and running it locally, I couldn't reproduce.

ferrarimarco on 2 Nov 2020

+1, the same issue for https://github.com/actions/virtual-environments

Mon, 02 Nov 2020 14:33:59 GMT -  6 hours ago everything is good
Mon, 02 Nov 2020 20:01:29 GMT - 30 minutes ago [FATAL]     -> ANSIBLE_LINTER_RULES rules file () doesn't exist. Terminating...

cageyv on 2 Nov 2020

@ferrarimarco I'm seeing the error when running with the Github action (github/super-linter@v3) and when pulling the latest docker image down with Jenkins.

mego22 on 2 Nov 2020

Clearing my assignment, as it's getting late here :)

In the meantime, can you try running building locally and run against the same code base?

ferrarimarco on 2 Nov 2020

same issue, vanilla superlinter.yml straight from the docs as a starting point (only changed the branch name)

name: Super-Linter

# Run this workflow every time a new commit pushed to your repository
on: push

jobs:
  # Set the job key. The key is displayed as the job name
  # when a job name is not provided
  super-lint:
    # Name the Job
    name: Lint code base
    # Set the type of machine to run on
    runs-on: ubuntu-latest

    steps:
      # Checks out a copy of your repository on the ubuntu-latest machine
      - name: Checkout code
        uses: actions/checkout@v2

      # Runs the Super-Linter action
      - name: Run Super-Linter
        uses: github/super-linter@v3
        env:
          DEFAULT_BRANCH: master
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

logs

/usr/bin/docker run --name ghcriogithubsuperlinterv3_864aae --label 1e5c35 --workdir /github/workspace --rm -e DEFAULT_BRANCH -e GITHUB_TOKEN -e HOME -e GITHUB_JOB -e GITHUB_REF -e GITHUB_SHA -e GITHUB_REPOSITORY -e GITHUB_REPOSITORY_OWNER -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_RETENTION_DAYS -e GITHUB_ACTOR -e GITHUB_WORKFLOW -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GITHUB_EVENT_NAME -e GITHUB_SERVER_URL -e GITHUB_API_URL -e GITHUB_GRAPHQL_URL -e GITHUB_WORKSPACE -e GITHUB_ACTION -e GITHUB_EVENT_PATH -e GITHUB_PATH -e GITHUB_ENV -e RUNNER_OS -e RUNNER_TOOL_CACHE -e RUNNER_TEMP -e RUNNER_WORKSPACE -e ACTIONS_RUNTIME_URL -e ACTIONS_RUNTIME_TOKEN -e ACTIONS_CACHE_URL -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/CANMessageParser/CANMessageParser":"/github/workspace" ghcr.io/github/super-linter:v3
...
2020-11-02 19:25:12 [INFO]   ---------------------------------------------
2020-11-02 19:25:12 [INFO]   --- GitHub Actions Multi Language Linter ----
2020-11-02 19:25:12 [INFO]    - Image Creation Date:[2020-11-02T15:17:06Z]
2020-11-02 19:25:12 [INFO]    - Image Revision:[5a04bd9]
2020-11-02 19:25:12 [INFO]    - Image Version:[v3]
2020-11-02 19:25:12 [INFO]   ---------------------------------------------
2020-11-02 19:25:12 [INFO]   ---------------------------------------------
2020-11-02 19:25:12 [INFO]   The Super-Linter source code can be found at:
2020-11-02 19:25:12 [INFO]    - https://github.com/github/super-linter
2020-11-02 19:25:12 [INFO]   ---------------------------------------------
2020-11-02 19:25:12 [INFO]   --------------------------------------------
2020-11-02 19:25:12 [INFO]   Gathering GitHub information...
2020-11-02 19:25:12 [INFO]   Successfully found:[GITHUB_SHA], value:[fdb79c6a57f0ba1b3c1e6960b79d44a15e223c7d]
2020-11-02 19:25:12 [INFO]   Successfully found:[GITHUB_WORKSPACE], value:[/github/workspace]
2020-11-02 19:25:12 [INFO]   Successfully found:[GITHUB_EVENT_PATH], value:[/github/workflow/event.json]
2020-11-02 19:25:12 [INFO]   Successfully found:[GITHUB_ORG], value:[dwhiteddsoft]
2020-11-02 19:25:12 [INFO]   Successfully found:[GITHUB_REPO], value:[CANMessageParser]
2020-11-02 19:25:12 [INFO]   Successfully found:[GITHUB_TOKEN]
2020-11-02 19:25:12 [INFO]   Successfully found:[GITHUB_REPOSITORY], value:[dwhiteddsoft/CANMessageParser]
2020-11-02 19:25:12 [INFO]   Successfully found:[GITHUB_RUN_ID], value:[342310911]
2020-11-02 19:25:12 [INFO]   --------------------------------------------
2020-11-02 19:25:12 [INFO]   Gathering user validation information...
2020-11-02 19:25:12 [INFO]   - Validating ALL files in code base...
2020-11-02 19:25:13 [FATAL]     -> ANSIBLE_LINTER_RULES rules file () doesn't exist. Terminating...

andrejpk on 2 Nov 2020

Built the image locally and got the same result:

docker run --rm \
>       -e RUN_LOCAL=true \
>       -e MULTI_STATUS=false \
>       -e DISABLE_ERRORS=false \
>       -e VALIDATE_ALL_CODEBASE=true \
>       -e VALIDATE_DOCKERFILE=false \
>       -e ANSIBLE_DIRECTORY=/ \
>       -v $$PWD:/tmp/lint \
> superlinter
--------------------------------------------------------------------------------

                              /@@#///////@@/(@//@%/(@.@(       @@
                          @@//////////////////////////////#*  @@@
                        @////@//(///////////@@@@@///@//@/@**//@@(
                      @///////@///////////////@@@@    (           @,
                     @/(&/@////////////////////                     @
                    @////////////////////////@@                      @
                  @%////////(//////////%/////&@            @@       *,@           ______________
             @@@@@/@/#/////(&//////////////////                       .@         /              \
        *@@@@@.    .%///(//@//////////////////&.   .@@,                 @%      / Don't mind me  \
      @@%           .&@&&/@.@//&/////(//////////    @@@@@@@@@         .. &@    / I'm just looking \
    @@%               @@@@@   @&/////////////////#   @/       V  @@/ ,@@@ @   <  for some trash... |
@@@%                   @@@@        .%@@@@//////#@ @   @@         @     .,.     \__________________/
                                          @@@/@(  (@@@@% @/\      %
                                           @@@@(    .     .@@/\   #
                                             @                  %@%

--------------------------------------------------------------------------------
2020-11-02 21:37:54 [INFO]   ---------------------------------------------
2020-11-02 21:37:54 [INFO]   --- GitHub Actions Multi Language Linter ----
2020-11-02 21:37:54 [INFO]    - Image Creation Date:[]
2020-11-02 21:37:54 [INFO]    - Image Revision:[]
2020-11-02 21:37:54 [INFO]    - Image Version:[]
2020-11-02 21:37:54 [INFO]   ---------------------------------------------
2020-11-02 21:37:54 [INFO]   ---------------------------------------------
2020-11-02 21:37:54 [INFO]   The Super-Linter source code can be found at:
2020-11-02 21:37:54 [INFO]    - https://github.com/github/super-linter
2020-11-02 21:37:54 [INFO]   ---------------------------------------------
2020-11-02 21:37:54 [INFO]   --------------------------------------------
2020-11-02 21:37:55 [INFO]   Gathering GitHub information...
2020-11-02 21:37:55 [INFO]   NOTE: ENV VAR [RUN_LOCAL] has been set to:[true]
2020-11-02 21:37:55 [INFO]   bypassing GitHub Actions variables...
2020-11-02 21:37:55 [INFO]   Linting all files in mapped directory:[/tmp/lint]
2020-11-02 21:37:55 [INFO]   Successfully found:[GITHUB_TOKEN]
2020-11-02 21:37:55 [INFO]   --------------------------------------------
2020-11-02 21:37:55 [INFO]   Gathering user validation information...
2020-11-02 21:37:55 [FATAL]     -> ANSIBLE_LINTER_RULES rules file () doesn't exist. Terminating...

mego22 on 2 Nov 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 2 Nov 2020

👍1

When I build from 5a04bd98750ed6c576c9a480e2708b94589d012b I get the described error:

2020-11-03 00:04:45 [INFO]   Gathering user validation information...
2020-11-03 00:04:46 [FATAL]     -> ANSIBLE_LINTER_RULES rules file () doesn't exist. Terminating...

When I build from e4b007cd406479d8261c9d8ba72fb1df0366e2e2 I do not.

So I think the changes from https://github.com/github/super-linter/pull/927 introduced this issue.

/cc @ferrarimarco @admiralAwkbar

solvaholic on 3 Nov 2020

Starting today, I'm seeing the same issue on two separate organization private repositories:

2020-11-03 05:44:09 [FATAL]     -> ANSIBLE_LINTER_RULES rules file () doesn't exist. Terminating...

For both workflows, I've configured VALIDATE_ALL_CODEBASE: false so the Ansible linter should not even be executed.

I've tried pinning the version:

uses: github/[email protected]

But to no avail, the workflow run seems to pull ghcr.io/github/super-linter:v3 regardless...

TomerFi on 3 Nov 2020

I've tried pinning the version:
uses: github/[email protected]
But to no avail, the workflow run seems to pull ghcr.io/github/super-linter:v3 regardless...

Try 3.13.1 instead, see https://github.com/github/super-linter/issues/938#issuecomment-720769293:

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

TheLastZombie on 3 Nov 2020

@TheLastZombie
Thank you, but that doesn't work.

First of all for both v3.13.1 and v3.13.3 the action is set to pull ghcr.io/github/super-linter:v3.
Which is a bug in itself, #943 has already been opened on that topic.

As for the https://github.com/github/super-linter/issues/938#issuecomment-720769293.
I wonder if it still works... 🤷‍♂️

The comment was 9 hours ago and the buggy release v3.13.3 was 17 hours ago.
idk, maybe the image used for the test was not yet updated...

TomerFi on 3 Nov 2020

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

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

dec5e on 3 Nov 2020

🎉6 👍5 ❤3

@dec5e
Works well!
Cool workaround!
:-)

TomerFi on 3 Nov 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...

bazzadp on 3 Nov 2020

👍1

Oh and also they don't always publish the latest version to docker (e.g. v1.13.2 is missing despite that being a working version for example).

bazzadp on 3 Nov 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 3 Nov 2020

👍1

You can use actions from docker image to lock to a specific version:
uses: docker://github/super-linter:v3.13.1

In case you'd prefer to use GitHub's container registry rather than Docker hub, this syntax works as well:

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

solvaholic on 3 Nov 2020

950 solved this

admiralAwkbar on 3 Nov 2020

👍2 🚀1

@solvaholic thanks for the info!

admiralAwkbar on 3 Nov 2020

👍1

Was this page helpful?

0 / 5 - 0 ratings

Related issues

Using GitHub Actions no report is found

brunomartinspro · 4Comments

Suggestion: use Perlcritic for perl

bbaassssiiee · 5Comments

How can I remove the mouse?

IlanCosman · 4Comments

Add more pre-release testing

bazzadp · 3Comments

Support .rubocop_todo.yml

DawidJanczak · 5Comments