.deployer-store-cache relies on ~/.juju
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-deployer |
Fix Released
|
Medium
|
Tim Van Steenburgh |
Bug Description
This was found while using the latest daily from ppa:ahasenack/
Traceback (most recent call last):
File "/usr/bin/
load_
File "/usr/lib/
run()
File "/usr/lib/
importer.
File "/usr/lib/
self.
File "/usr/lib/
no_
File "/usr/lib/
charm.fetch()
File "/usr/lib/
self.
File "/usr/lib/
cache_dir = self._get_
File "/usr/lib/
os.
OSError: [Errno 2] No such file or directory: '/home/
juju 2 no longer creates ~/.juju, it uses .local/share/juju instead.
I missed this during the juju2 support work.
Manually creating ~/.juju works as a workaround.
Related branches
- Marco Ceppi (community): Approve
- Matt Bruzek (community): Approve
- juju-deployers: Pending requested
-
Diff: 138 lines (+15/-43)3 files modifieddeployer/env/base.py (+2/-30)
deployer/utils.py (+12/-12)
setup.py (+1/-1)
description: | updated |
Changed in juju-deployer: | |
assignee: | nobody → Tim Van Steenburgh (tvansteenburgh) |
importance: | Undecided → Medium |
Changed in juju-deployer: | |
status: | New → Triaged |
status: | Triaged → In Progress |
milestone: | none → 0.7.1 |
Changed in juju-deployer: | |
status: | In Progress → Fix Committed |
Changed in juju-deployer: | |
status: | Fix Committed → Fix Released |