win client thinks the cloud-init log is on the c drive

[Curtis Hovey]

The win client cannot bootstrap in aws as of commit 47c36c4f (https://github.com/juju/juju/commit/47c36c4fdf2413345c3338ce8021f19d9f1baea1). The test previously passed with commit 6cbf17b. The only commit after the last working on was a change to the help command line, so 47c36c4f is probably bad
    http://juju-ci.vapour.ws:8080/job/win-client-deploy/705/console

Attempting to connect to 54.164.13.65:22
/bin/bash: line 306: C:/Juju/log/cloud-init-output.log: No such file or directory
2014-08-20 18:36:26 ERROR juju.provider.common bootstrap.go:123 bootstrap failed: Process exited with: 1. Reason was: ()
Stopping instance...

[Tim Penhey (thumper)]

I don't think it is the commit listed as it is only the uniter code and nothing to do with bootstrap.

[Tim Penhey (thumper)]

$ git diff 8ed40cf..c5ab7f9

This shows more than just uniter changes.

[Tim Penhey (thumper)]

Gah, that diff is the wrong way around.

[Ian Booth (wallyworld)]

I reverted https://github.com/juju/juju/pull/189 which is strongly suspected as the cause of this bug. Marking as Fix Committed - we can reopen is needed.

[Gabriel Samfira (gabriel-samfira)]

*sigh*. It was two line fix inside NewMachineConfig :-( . Is there a way to run both the test on Ubuntu and the test on Windows when doing the merge?

[Curtis Hovey (sinzui)]

The windows machine that does the CI is technically accessible to the git-merge-juju process.

I think the intent of git-merge-juju is to be fast and somewhat reliable, but we know that the unit-tests fails for other series and archs fail often. Maybe we want to extend git-merge-juju to also run the tests for precise-amd64 and win2012+amd64.

How do we run the unit-tests on a windows machine? If there is a script, we can add or extend the job that makes the win installer to also run the unit-tests in the unpacked release tarball.

[Gabriel Samfira (gabriel-samfira)]

That would be great :). Right now, the windows test basically does a bootstrap to make sure the juju tools still work.

We have a small team now working on getting the full suite of unit tests running on windows, seeing as how we are 95%+ done with the windows agent support (only crytical bit left now is the logging changes).

My hope is to get them running as soon as possible, and avoid silly (but anoying) bugs such as this.

I apologise for blocking master...