juju deploy says "charm not found" when metadata.yaml name is not valid.
Bug #1384369 reported by
Jay R. Wren
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
Medium
|
Unassigned | ||
Juju Charm Tools |
Won't Fix
|
Undecided
|
Unassigned | ||
juju-core |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
$ mkdir trusty ; cd trusty ; juju charm generate for_example ; mv for_example for-example ; cd ..
$ juju deploy local:trusty/
ERROR charm not found in "/home/
But the directory is right there!
I expect a message WHY it is not found. No config.yaml, no metadata.yaml (those were there in this case), or metadata.yaml contains an invalid charm name.
I also expect a message telling me WHY the charm name is invalid. It should tell me that _ is not allowed.
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → 2.0.1 |
Changed in juju-core: | |
status: | Triaged → Won't Fix |
Changed in juju: | |
milestone: | 2.0.1 → none |
To post a comment you must log in.
This is an issue with Juju, not with charm tools directly. Charms from local repositories are ingested by metadata.yaml names not by directory name. To be fair the error message is correct, The charm was not found in that JUJU_REPOSITORY, this is an issue with educating users on how Juju figures out where charms are and what they are.