It has been raised (by Nobuto) that juju-lint fails to parse the default bundle put together by Solutions QA and used by the FE team.
This bug tracks the effort to investigate and fix the raised problem.
1) fce-templates[1]: confirm with SolQA which repo branch and bundle are the default
2) Reproduce the problem
3) Confirm with BootStack Ops if the expected juju-lint error is due to a juju-lint bug (code fixing or bundle parser rules fixing required) or a bundle bug (SolQA default bundle fix required).
Note: For step (2), a charm [2] exists and should be used.
(by nobuto)
Yes, the goal here would be:
"Juju-lint should pass with the Bundle-builder generated bundles out of the box by integrating it into the Solution QA pipeline"
Fix bundles by updating BB like missing relations, etc.
And/or fix juju-lint by eliminating unknown charms, etc.
It has been raised (by Nobuto) that juju-lint fails to parse the default bundle put together by Solutions QA and used by the FE team.
This bug tracks the effort to investigate and fix the raised problem. 1) fce-templates[1]: confirm with SolQA which repo branch and bundle are the default 2) Reproduce the problem 3) Confirm with BootStack Ops if the expected juju-lint error is due to a juju-lint bug (code fixing or bundle parser rules fixing required) or a bundle bug (SolQA default bundle fix required).
Note: For step (2), a charm [2] exists and should be used.
Imported from Launchpad using lp2gh.
date created: 2022-05-09T08:15:12Z
owner: aluria
assignee: gabrielcocenza
the launchpad url