juju / juju-gui-charm

Charm for Juju GUI.
GNU Affero General Public License v3.0
2 stars 16 forks source link

pip install the juju-gui tarball. Still non-functional. #2

Closed bac closed 8 years ago

bac commented 8 years ago

QA:

juju bootstrap
make deploy
juju status       # Ensure no errors
juju ssh juju-gui/0
pip list             # Ensure juju-gui (1.8.1000)
bac commented 8 years ago

:-1: Tests fail

jcsackett commented 8 years ago

I see this in the deploy output:

WARNING making "/home/jc/Code/charms/trusty/juju-gui/hooks/cached-website-relation-joined" executable in charm

Not part of your branch, but can you go ahead and chmod +x that hook file in this branch?

jcsackett commented 8 years ago

Also I'm seeing the start hook failing:

root@jc-local-machine-1:/var/lib/juju/agents/unit-juju-gui-0/charm# hooks/start
Traceback (most recent call last):
  File "hooks/start", line 34, in <module>
    main()
  File "hooks/start", line 29, in main
    backend.start()
  File "/var/lib/juju/agents/unit-juju-gui-0/charm/hooks/backend.py", line 237, in start
    call_methods(self.mixins, 'start', self)
  File "/var/lib/juju/agents/unit-juju-gui-0/charm/hooks/backend.py", line 186, in call_methods
    method(*args)
  File "/var/lib/juju/agents/unit-juju-gui-0/charm/hooks/backend.py", line 137, in start
    juju_env_uuid=os.getenv('JUJU_ENV_UUID', None))
  File "/var/lib/juju/agents/unit-juju-gui-0/charm/hooks/utils.py", line 398, in write_gui_config
    render_to_file('config.js.template', context, config_js_path)
  File "/var/lib/juju/agents/unit-juju-gui-0/charm/hooks/utils.py", line 273, in render_to_file
    with open(destination, 'w') as stream:
IOError: [Errno 2] No such file or directory: '/var/lib/juju-gui/juju-gui/build-prod/juju-ui/assets/config.js'
root@jc-local-machine-1:/var/lib/juju/agents/unit-juju-gui-0/charm# 

Looks like the error you were describing before...?

jcsackett commented 8 years ago

QA OK-ish.

I see jujugui, but if I try to import it in a python session it fails; seems like jujugui doesn't provide Pyramid as a requirement in its setup, or something--not an issue in this branch, but worth noting.

bac commented 8 years ago

Test failures were for routines that are being gutted but eventual functionality is uncertain. I have used @unittest.skip on them to preserve test setup that I'd hate to have to come up with again.

jcsackett commented 8 years ago

:+1: