| === frankban|afk is now known as frankban | ||
| === fnordahl_ is now known as fnordahl | ||
| === tinwood_ is now known as tinwood | ||
| === mhilton_ is now known as mhilton | ||
| === Spads_ is now known as Spads | ||
| === aluria` is now known as aluria | ||
| === atrius_ is now known as atrius | ||
| === stub` is now known as stub | ||
| cnf | 5 down pending xenial cannot run instances: cannot run instance: No available machine matches constraints | 11:50 |
|---|---|---|
| cnf | how do i make it try again? | 11:50 |
| cnf | this is against MaaS | 11:50 |
| bdx | cnf: juju help commands | 13:02 |
| cnf | bdx: yes, i did that | 13:02 |
| bdx | cnf: juju help commands | grep remove-machine | 13:02 |
| cnf | i can't find a command that does it | 13:02 |
| cnf | right, so you can't retry, you have to remove, and readd | 13:02 |
| bdx | then | 13:02 |
| bdx | juju help remove-machine | 13:02 |
| cnf | which doesn't work btw, you have to remove the unit first | 13:05 |
| bdx | ahh | 13:06 |
| bdx | cnf | 13:06 |
| bdx | please read the help docs for remove-machine | 13:07 |
| cnf | i have removed the machine ages ago | 13:07 |
| cnf | my question was how can i make it retry, to which the answer is "you can't" aparently | 13:07 |
| bdx | cnf: if it failed the first time, what makes you think it would succeed a second time without manual intervention of some sort? | 13:10 |
| cnf | because i did the manual intervention on maas | 13:10 |
| bdx | cnf: yeah, you just have to `juju remove-machine # --force` and redeploy it | 13:13 |
| bdx | (to the best of my knowledge) | 13:13 |
| cnf | yeah... | 13:15 |
| === dosaboy_ is now known as dosaboy | ||
| === Berg is now known as Guest57443 | ||
| zeestrat | cnf: you might want pour some more gasoline on this fire so we can get retry-provisioning to work: https://bugs.launchpad.net/juju/+bug/1645422 | 16:44 |
| mup | Bug #1645422: retry-provisioning doesn't retry failed deployments on MAAS <4010> <cdo-qa> <cpe-onsite> <landscape> <maas-provider> <retry-provisioning> <juju:Triaged> <https://launchpad.net/bugs/1645422> | 16:44 |
| cnf | zeestrat: will do tomorrow | 16:54 |
| cnf | zeestrat: thanks | 16:55 |
| === frankban is now known as frankban|afk | ||
| === grumble is now known as Guest10721 | ||
| === rumble is now known as grumble | ||
| === sarnold_ is now known as sarnold | ||
| Mmike | Hi, all. Is there a (faster than 'juju models') way to get the current juju model? | 19:32 |
| Mmike | I want to add that info into my bash prompt, but having bash do 'juju models' each time is pretty slow | 19:33 |
| Mmike | currently i'm defaulting JUJU_MODEL to 'default' and display that, and refrain from using 'juju switch', and I display JUJU_MODEL in my path, but I'm wondering if there is a better way | 19:34 |
| === mwhudson_ is now known as mwhudson | ||
| kwmonroe | Mmike: you mentioned refraining from 'juju switch', but calling that with no args will give you the current <controller>[:model] | 23:02 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!