+1
I've been using hub for a while now to make it easy to grab other people's
pull requests. It's great.
Like Nate, I also prefer to keep hub separate from git so I also ignore the
install suggestion from the hub team.
On 3 August 2016 at 07:56, Rick Harding wrote:
Thanks Nate, that's really useful info and Hub makes it easy to get at
other folk's repos/forks of Juju to really collaborate, look at code that's
WIP and such.
I highly recommend folks take a peek and see how it can improve their
collaboration and workflows. Especially when reviewing and QA'ing
On Tue, Aug 2, 2016 at 12:09 PM, Rick Harding
wrote:
>
>
> On Tue, Aug 2, 2016 at 2:28 PM Curtis Hovey-Canonical <
> cur...@canonical.com> wrote:
>
>> NEW:
>>
>> Deployer: KeyError: 'uuid' connecting to environment
>> https://bugs.launchpad.net/juju-core/+bug/1608952
On Tue, Aug 2, 2016 at 2:28 PM Curtis Hovey-Canonical
wrote:
> NEW:
>
> Deployer: KeyError: 'uuid' connecting to environment
> https://bugs.launchpad.net/juju-core/+bug/1608952
> ^ Juju or deployer needs to change
>
The conversation here was that the deployer had been
The top issues page is contaminated with results from retests
http://reports.vapour.ws/releases/top-issues
(https://bugs.launchpad.net/juju-reports/+bug/1608971)
Since http://reports.vapour.ws/releases/4200 we are seeing a rise in failures
These are the issues seen in recent days that
Ok, here we go hopefully this will provide a better overhead view.
`juju bootstrap creativedrive aws --credential creativedrive --config
vpc-id=vpc-ff069a98 --config vpc-id-force='true' --upload-tools --debug
--config logging-config='=TRACE'` <- http://paste.ubuntu.com/21914113/
cat
To my utter dismay, setting the correct config 'vpc-id-force' gave me the
same result
Let me scrub and collect my machine-0.log for you.
On Tue, Aug 2, 2016 at 9:36 AM, James Beedy wrote:
> Dimiter,
>
> Thanks for the insight.
>
>
>
>
>
>
> *Can you please also
Dimiter,
Thanks for the insight.
*Can you please also paste the full logs (scrubbed of secrets) of
`jujubootstrap ... --debug` (with the vpc-id etc., but please also
include`--config logging-config='=TRACE'`), and machine-0.log
from/var/log/juju on the bootstrap node, once completed? That
Hey James,
Can you please also paste the full logs (scrubbed of secrets) of `juju
bootstrap ... --debug` (with the vpc-id etc., but please also include
`--config logging-config='=TRACE'`), and machine-0.log from
/var/log/juju on the bootstrap node, once completed? That will help
figuring out the