CI hates juju, maybe the feelings are mutual
John Meinel
john at arbash-meinel.com
Thu Apr 10 18:14:30 UTC 2014
Actually, I was trying to fix it, and it is more broken than we realized.
We no longer support multiple extra arguments to SCP. It always complains
if there is one that isn't exactly the last one. (-o "foo" says it isn't
accepted, -o"foo" is allowed, but you can't supply 2 of them, etc).
It just needs to be fixed.
I think a better way is to allow "--", but just interpret each argument as
potentially a target, and expand it if it has a clear MACHINE_OR_UNIT: at
the beginning.
https://bugs.launchpad.net/juju-core/+bug/1306208
On Thu, Apr 10, 2014 at 7:05 PM, Aaron Bentley
<aaron.bentley at canonical.com>wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 14-04-10 08:23 AM, John Meinel wrote:
> > Note that copying off the all-machines log seems to be broken, the
> > lines:
> >
> > juju --show-log scp -e test-release-aws -- -o
> > 'StrictHostKeyChecking no' -o 'UserKnownHostsFile /dev/null' -i
> > /var/lib/jenkins/cloud-city/staging-juju-rsa
> > 0:/var/log/juju/all-machines.log
> >
> /var/lib/jenkins/jobs/aws-upgrade/workspace/artifacts/all-machines-test-release-aws.log
> >
> >
> 2014-04-10 03:40:59 INFO juju.cmd supercommand.go:297 running
> juju-1.18.0-precise-amd64 [gc]
> > 2014-04-10 03:40:59 INFO juju api.go:238 connecting to API
> > addresses: [ec2-54-86-4-94.compute-1.amazonaws.com:17070
> > <http://ec2-54-86-4-94.compute-1.amazonaws.com:17070>] 2014-04-10
> > 03:40:59 INFO juju apiclient.go:114 state/api: dialing
> > "wss://ec2-54-86-4-94.compute-1.amazonaws.com:17070/
> > <http://ec2-54-86-4-94.compute-1.amazonaws.com:17070/>" 2014-04-10
> > 03:40:59 INFO juju apiclient.go:124 state/api: connection
> > established 2014-04-10 03:40:59 ERROR juju.cmd supercommand.go:300
> > unexpected argument "-o"; extra arguments must be last
> >
> >
> > It looks like you have to spell it:
> >
> > juju --show-log scp -e test-release-aws
> > 0:/var/log/juju/all-machines.log
> >
> /var/lib/jenkins/jobs/aws-upgrade/workspace/artifacts/all-machines-test-release-aws.log
> > -o 'StrictHostKeyChecking no' -o 'UserKnownHostsFile /dev/null' -i
> > /var/lib/jenkins/cloud-city/staging-juju-rsa
> >
> > I don't know if "--" for SCP ever worked, but it appears 1.18 wants
> > a different spelling.
>
> Using '--' to separate commands was the only way that used to work for
> juju scp. Most all-machines.log that you'll find in CI bug reports
> were produced this way.
>
> If you passed -o directly, juju would complain that it was not a valid
> option, no matter where you put it. This problem did not happen with
> juju ssh.
>
> It's nice that things are easier now, but it's a shame that the fix
> broke existing scripts.
>
> Aaron
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQEcBAEBAgAGBQJTRrMjAAoJEK84cMOcf+9hshsH/0338ET9mAJhcAHPd2pBdtzy
> 9s4nXlARPrEH0/SW2IbmamSvLRRuNHRG/FrP/98fBsT3G9Db7099+ywgYhfzvtvN
> ucaE1Tu+1XiSi+ZFWW9CJP00JQP4CyPbpA9wsbHMbBPn3BBUO8+gkkmt2XbW1/1N
> MqkAgBRWuQDN7EGMYQLFhjIs6ipxv5wbtIRdEqdcChZbHsoKLNYSfdRQhdpq4ikR
> lkwAodnsMOP7KPGTyX8LUEYnNJYf1E516Hf7IaRTw875XC0Hk863fI58wBFG6fe+
> 1DGM+l0C0H95Do4ExxgEq2xmONhL33/g7FzUVstaRNkm04xPvI4iypHMvZH08+A=
> =+ALO
> -----END PGP SIGNATURE-----
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20140410/71f9034f/attachment-0001.html>
More information about the Juju-dev
mailing list