Move "Charm not recognised" error to info

Bug #2054805 reported by Nobuto Murata
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juju Lint
Fix Released
Undecided
Gabriel Cocenza

Bug Description

Some reports (including https://bugs.launchpad.net/juju-lint/+bug/2033524 as an example) pointed out the juju-lint is behind from the charm ecosystem and doesn't support any sort of COS deployment.

We just can't keep "charm not recognized" as the error level since too many false positives hide actual errors in the bundle or the deployment.

> [ERROR] [bundle.yaml] [manual/manual] Charm 'cos-proxy' not recognised

If it takes time to accommodate COS deployments, let's just move the unrecognized error to info level.

Tags: bseng-2093

Related branches

Eric Chen (eric-chen)
tags: added: bseng-2093
Andrea Ieri (aieri)
Changed in juju-lint:
status: New → In Progress
assignee: nobody → Gabriel Cocenza (gabrielcocenza)
Revision history for this message
Andrea Ieri (aieri) wrote :

Available in version 1.2.1.dev2+gee96e76

Changed in juju-lint:
status: In Progress → Fix Committed
Revision history for this message
Eric Chen (eric-chen) wrote :
Changed in juju-lint:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.