Unable to change the juju-gui-source with latest version of Juju

Bug #1427377 reported by Jeff Pihach
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-gui
Invalid
Undecided
Unassigned

Bug Description

After deploying the charm and checking to make sure that it worked as expected. Changing the juju-gui-source configuration option causes a config change hook failure.

Juju: 1.22-beta4-trusty-amd64
Juju-GUI: trusty-19

Error message:
2015-03-02 20:42:50 INFO unit.juju-gui/0.juju-log cmd.go:247 fatal: Refusing to fetch into current branch refs/heads/develop of non-bare repository
Unexpected end of command stream

Full traceback:
2015-03-02 20:41:27 INFO unit.juju-gui/0.juju-log cmd.go:247 Using source https://github.com/juju/juju-gui.git: develop
2015-03-02 20:42:38 INFO unit.juju-gui/0.juju-log cmd.go:247 Retrieving Juju GUI source checkout from https://github.com/juju/juju-gui.git (develop).
2015-03-02 20:42:50 INFO unit.juju-gui/0.juju-log cmd.go:247 Exception caught:
2015-03-02 20:42:50 INFO unit.juju-gui/0.juju-log cmd.go:247 fatal: Refusing to fetch into current branch refs/heads/develop of non-bare repository
Unexpected end of command stream

2015-03-02 20:42:50 INFO unit.juju-gui/0.juju-log cmd.go:247 <<< Exiting config-changed
2015-03-02 20:42:50 INFO unit.juju-gui/0.config-changed logger.go:40 Traceback (most recent call last):
2015-03-02 20:42:50 INFO unit.juju-gui/0.config-changed logger.go:40 File "/var/lib/juju/agents/unit-juju-gui-0/charm/hooks/config-changed", line 58, in <module>
2015-03-02 20:42:50 INFO unit.juju-gui/0.config-changed logger.go:40 main()
2015-03-02 20:42:50 INFO unit.juju-gui/0.config-changed logger.go:40 File "/var/lib/juju/agents/unit-juju-gui-0/charm/hooks/config-changed", line 49, in main
2015-03-02 20:42:50 INFO unit.juju-gui/0.config-changed logger.go:40 backend.install()
2015-03-02 20:42:50 INFO unit.juju-gui/0.config-changed logger.go:40 File "/var/lib/juju/agents/unit-juju-gui-0/charm/hooks/backend.py", line 286, in install
2015-03-02 20:42:50 INFO unit.juju-gui/0.config-changed logger.go:40 call_methods(self.mixins, 'install', self)
2015-03-02 20:42:50 INFO unit.juju-gui/0.config-changed logger.go:40 File "/var/lib/juju/agents/unit-juju-gui-0/charm/hooks/backend.py", line 219, in call_methods
2015-03-02 20:42:50 INFO unit.juju-gui/0.config-changed logger.go:40 method(*args)
2015-03-02 20:42:50 INFO unit.juju-gui/0.config-changed logger.go:40 File "/var/lib/juju/agents/unit-juju-gui-0/charm/hooks/backend.py", line 114, in install
2015-03-02 20:42:50 INFO unit.juju-gui/0.config-changed logger.go:40 branch_url, revision, logpath)
2015-03-02 20:42:50 INFO unit.juju-gui/0.config-changed logger.go:40 File "/var/lib/juju/agents/unit-juju-gui-0/charm/hooks/utils.py", line 665, in fetch_gui_from_branch
2015-03-02 20:42:50 INFO unit.juju-gui/0.config-changed logger.go:40 'origin', '{0}:{0}'.format(revision)))
2015-03-02 20:42:50 INFO unit.juju-gui/0.config-changed logger.go:40 File "/var/lib/juju/agents/unit-juju-gui-0/charm/hooks/shelltoolbox.py", line 457, in run
2015-03-02 20:42:50 INFO unit.juju-gui/0.config-changed logger.go:40 raise exception
2015-03-02 20:42:50 INFO unit.juju-gui/0.config-changed logger.go:40 subprocess.CalledProcessError: Command '['git', '--git-dir', '/var/lib/juju/agents/unit-juju-gui-0/charm/juju-gui-source/.git', '--work-tree', '/var/lib/juju/agents/unit-juju-gui-0/charm/juju-gui-source', 'fetch', '--depth', '1', 'origin', 'develop:develop']' returned non-zero exit status 128
2015-03-02 20:42:50 ERROR juju.worker.uniter.operation runhook.go:86 hook "config-changed" failed: exit status 1

Jeff Pihach (hatch)
description: updated
description: updated
Revision history for this message
Richard Harding (rharding) wrote :

This should have been just 'develop' as a value unless you're referring to a fork of the repo. Closing this as invalid. If it doesn't work pointing to a fork please open a bug with the info from that failed attempt.

Changed in juju-gui:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.