=== CyberJacob|Away is now known as CyberJacob | ||
ashipika | Hello.. | 09:12 |
---|---|---|
ashipika | Is admin-secret mandatory for juju-gui? or is there another way to set the password? | 09:13 |
lazypower | ashipika: do you mean can you reset it? | 10:13 |
lazypower | to simple simpler, like "swordfish" or do you mean can you disable it all together? | 10:13 |
ashipika | anybody here that knows anything about juju-gui? | 11:09 |
lazypower | ashipika: Certainly, What questions do you have? | 11:47 |
ashipika | oh, i figured it out.. in null environment the admin-secret in the .juju/environments.yaml is disregarded | 11:49 |
ashipika | i had to look into .juju/environments/null.jenv to find to proper admin-secret | 11:49 |
ashipika | for the juju-gui password, that is | 11:49 |
lazypower | its in ~/.juju/environments.yaml | 11:49 |
ashipika | i described it here: https://bugs.launchpad.net/bugs/1263900 | 11:50 |
lazypower | did that differ from what was in the null provider? | 11:50 |
_mup_ | Bug #1263900: Null environment disregards admin-secret in environments.yaml <juju-core:New> <https://launchpad.net/bugs/1263900> | 11:50 |
lazypower | Interesting, one sec | 11:50 |
ashipika | ok | 11:50 |
lazypower | I'm going to provision some VM's and try to reproduce this | 11:54 |
lazypower | can you give me the output of juju -v? | 11:54 |
ashipika | version? 1.17.0-precise-amd64 | 11:55 |
lazypower | thank you | 11:57 |
lazypower | ashipika: looks to be isolated to the 1.17 branch of juju-core. I've bootstrapped a null environment with 4 new environments.yaml and it translates 1:1 thusfar. | 12:18 |
lazypower | *note i'm running 1.16.5 | 12:18 |
lazypower | Are you aware that you're on the -dev branch of juju-core? | 12:18 |
ashipika | yes | 12:18 |
ashipika | since null environment is in development | 12:18 |
lazypower | Ok, just making sure you didn't find a stray AU post and dive in. | 12:19 |
ashipika | ok.. i just wanted to confirm that was not expected behavior.. | 12:20 |
lazypower | Indeed, that would be a bug. | 12:21 |
ashipika | i added a comment to the bug report stating the juju version | 12:22 |
lazypower | Excellent, thank you. | 12:26 |
marcoceppi | ashipika: it can be expected behavior | 12:50 |
marcoceppi | ashipika: if you bootstrap, then change the environments.yaml, the effects won't take hold until the next bootstrap. | 12:50 |
ashipika | marcoceppi, i understand, however i did not change the environments.yaml after bootstrap | 12:51 |
marcoceppi | ashipika: this could be related to this bug | 12:51 |
marcoceppi | ashipika: https://bugs.launchpad.net/juju-core/+bug/1246343 | 12:58 |
_mup_ | Bug #1246343: destroy-environment no longer removes .jenv <charmers> <destroy-environment> <landscape> <juju-core:In Progress by axwalk> <https://launchpad.net/bugs/1246343> | 12:58 |
ashipika | doubt it.. i bootstrapped a fresh vm | 13:02 |
=== xnox_ is now known as xnox | ||
=== amol_ is now known as amol | ||
=== OutOfControl is now known as benonsoftware | ||
maxcan | is there any reason that exposing haproxy in a local environment wouldn't open port 80? | 23:07 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!