| bdx | heyyyya | 15:58 |
|---|---|---|
| bdx | how can my users login to a controller from another host? | 15:59 |
| bdx | I thought it may be as simple as running `juju register <ip address of controller> | 16:00 |
| bdx | I can't find any docs on this | 16:00 |
| bdx | ahh got it | 16:06 |
| bdx | they just run the register command, but with the ip of the controller, instead of the register hash | 16:07 |
| bdx | hmmmm ... well thatt doesn't work | 16:08 |
| bdx | https://bugs.launchpad.net/juju/+bug/1754701 | 16:14 |
| mup | Bug #1754701: `juju register` workflow ? <juju:New> <https://launchpad.net/bugs/1754701> | 16:14 |
| bdx | followed it up with a docs bug too https://github.com/juju/docs/issues/2513 | 16:21 |
| bdx | rahwork, rick_h: rahworkx@external/devops-sandbox | 16:51 |
| bdx | ^ model stuck in destroying in jaas | 16:52 |
| bdx | the machine in that model was a manually added machine that was physically removed, but then never removed in the context of juju | 16:52 |
| bdx | now trying to remove the model it hangs | 16:53 |
| bdx | never destroys | 16:53 |
| ryebot | bdx check .local/share/juju/models.yaml, there may be a stale entry that you can remove if you're sure the machines are gone. | 16:55 |
| bdx | ryebot: cool ... I mean I can still get `juju status` on the model .... | 16:55 |
| bdx | ryebot: I would think that would indicate that the model still actually exists ? | 16:56 |
| bdx | ryebot: https://pastebin.com/qisLu5dm | 16:58 |
| ryebot | bdx looking | 16:58 |
| ryebot | What happens if you force remove that machine? | 16:58 |
| ryebot | bdx^ | 16:59 |
| bdx | it never leaves | 16:59 |
| ryebot | bdx can you confirm it's actually gone via aws console or cli? | 17:00 |
| bdx | ryebot: one interesting observation https://pastebin.com/uURCXgUL | 17:01 |
| bdx | after trying to --force remove the machine, it seems the juju agent has come back to life lol | 17:02 |
| ryebot | Oh, weird. | 17:02 |
| ryebot | I'd probably try another force removal | 17:03 |
| bdx | yeah, I just hammered it with ~20ish | 17:03 |
| ryebot | Ah, well then. | 17:03 |
| bdx | I'm cracking open another bug for this | 17:04 |
| bdx | ryebot: thanks for your insight | 17:04 |
| ryebot | I think at this point I'd destroy the machine via aws cli/console and then wipe the model | 17:04 |
| bdx | its a manually added machine | 17:04 |
| ryebot | bdx np good luck | 17:04 |
| bdx | no one who has access to the model has access to the physical machine anymore lol | 17:05 |
| rick_h | bdx: can you destroy-machine --force? | 17:15 |
| bdx | rick_h: I can run the command, but it has no affect | 17:16 |
| bdx | oh | 17:16 |
| bdx | destroy-machine? | 17:16 |
| rick_h | bdx: right, go to the model, destroy-machine --force all the machines | 17:16 |
| bdx | oh lol ... nope cant run that one | 17:16 |
| rick_h | then destroy-model (now empty) | 17:16 |
| rick_h | :( | 17:17 |
| rick_h | have to go the bug route and see what we can figure out sorry. That's the best get out of jail card I know for that | 17:17 |
| bdx | destroy-model | 17:17 |
| bdx | is a thing | 17:17 |
| bdx | destroy-machine isnt | 17:17 |
| rick_h | remove-machine? | 17:18 |
| rick_h | I thought it was destroy | 17:18 |
| bdx | but yeah ... got the friday bug attack all lit up | 17:18 |
| bdx | https://bugs.launchpad.net/juju/+bug/1754711 | 17:18 |
| mup | Bug #1754711: `juju destroy-model <model-name>` - model never destroys <juju:New> <https://launchpad.net/bugs/1754711> | 17:18 |
| rick_h | bdx: sorry, remove-machine --force | 17:18 |
| bdx | yeah, rick_h .... ya know what that did? | 17:18 |
| rick_h | heh..no | 17:18 |
| bdx | interesting behavior https://paste.ubuntu.com/p/ywJ7Cns8HS/ | 17:19 |
| bdx | lol | 17:19 |
| rahworkx | Hello all, does anyone know a way to provision multiple kube-api-loadbalancer aws instances in the cdk bundle.yml ? | 19:02 |
| rahworkx | Hello all was also wondering when bootstrapping a aws controller is there a way to config open port source ip's? | 19:28 |
| kwmonroe | rahworkx: this will open ports on any unit: juju run --unit <application>/<n> open-port XXXX' | 20:51 |
| kwmonroe | or if you wanted ports for multiple units, you could do it at the application level with: juju run --application <app> 'open-port XXXX' | 20:51 |
| kwmonroe | or everthing with: juju run --all 'open-port XXXX' | 20:51 |
| kwmonroe | but typically you'd rely on the charm author to open the right ports for their application. is there a reason you want additional ports opened outside of the charm's defaults? | 20:52 |
| kwmonroe | oh wait, i may be misunderstanding your question -- you wanted ports opened at bootstrap time? for the controller or a specific app or what? | 20:53 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!