Cannot pack charms with long names
Metadata
Current evaluation
Charm packing failed for long names due to LXC's 63-character limit. The issue was fixed by truncating instance names and appending a hash suffix to prevent collisions. The maintainer confirmed the implementation and closed the issue.
Suggested action: —
No scores available.
Issue body
```
* Command output: b'Creating charmcraft-finos-legend-gitlab-integrator-k8s-24120086-0-0-amd64\n'
* Command standard error output: b'Error: Invalid instance name: Name must be 1-63 characters long\n'
```
If we detect it's too long, we could shorten the name, but adding a hash of the full name, to avoid collisions.
To workaround this just shorten the name of the charm manually.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen3.6-35b-a3b-mtp-q6 | — | — | Charm packing failed for long names due to LXC's 63-character limit. The issue was fixed by truncating instance names and appending a hash suffix to prevent collisions. The maintainer confirmed the implementation and closed the issue. | |
| qwen/qwen3.6-35b-a3b | — | — | Charm packing failed for long names due to LXC's 63-character instance limit. Fixed by truncating overly long names and appending a hash to prevent collisions, ensuring compatibility across all backends. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Charm packing failed for long names due to LXC's 63-character instance limit. Fixed by implementing a truncation and hash suffix strategy to prevent collisions while respecting backend constraints. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Fixed by updating the instance naming logic to handle long charm names. The solution truncates excessively long names and appends a hash to prevent collisions and comply with LXC/LXD character limits. Maintainer confirmed the fix. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #685 charmcraft pack errors with LXDError - Name can only contain alphanumeric and hyphen characters | charmcraft | closed | Resolved as an upstream LXD bug. The error originated from overly strict device name validation in certain LXD revisions. Fixed in LXD 4.23 revision 22525; users should update LXD to restore charmcraft pack functionality. |