'version string generation failed' on deploy
Bug #1789447 reported by
Stuart Bishop
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Nam Nguyen |
Bug Description
With 2.4.2, I've started seeing spurious (?) warnings when deploying:
$ juju deploy ~/charms/
WARNING version string generation failed : exit status 128
Deploying charm "local:
Everything seems to be working fine, despite the noise.
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Ian Booth (wallyworld) |
milestone: | none → 2.4.3 |
Changed in juju: | |
status: | Triaged → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Changed in juju: | |
milestone: | none → 2.5.1 |
tags: | added: bitesize |
Changed in juju: | |
assignee: | Ian Booth (wallyworld) → Richard Harding (rharding) |
Changed in juju: | |
milestone: | 2.5.1 → 2.5.2 |
Changed in juju: | |
assignee: | Richard Harding (rharding) → nobody |
Changed in juju: | |
milestone: | 2.5.2 → 2.5.3 |
Changed in juju: | |
milestone: | 2.5.3 → 2.5.4 |
Changed in juju: | |
milestone: | 2.5.4 → 2.5.5 |
Changed in juju: | |
milestone: | 2.5.6 → 2.5.8 |
Changed in juju: | |
milestone: | 2.5.8 → 2.5.9 |
Changed in juju: | |
assignee: | nobody → Nam Nguyen (nammn) |
Changed in juju: | |
milestone: | 2.5.9 → 2.7-beta1 |
Changed in juju: | |
status: | Triaged → Fix Committed |
tags: | added: sts |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The issue here is that we now run "git describe --dirty" to pick up the sha of the latest commit and include that in a version file in the charm archive. This is reported in juju status.
However, it seems git describe can sometimes fail with error code 128 if it can't find any suitable tags. Using --always should fix this.
Note that it is just noise in that if there's an error running git describe, the charm deploy still goes ahead.