Comment 1 for bug 1436925

I cannot reproduce this bug. I could successfully to talk to a 1.18 server with a 1.23-beta2 client:

$ juju version
1.23-beta2-trusty-amd64
$ juju status
WARNING ignoring invalid API endpoint environment UUID
environment: local
machines:
  "0":
    agent-state: started
    agent-version: 1.18.1.1
    dns-name: localhost
    instance-id: localhost
    series: trusty
services: {}

There is a comment on the code that allows this is, api.go:285:

// For backwards-compatibility, we have to allow connections
// with an empty UUID. Login will work for the same reasons.

I note the bug mentions a missing .jenv. A 1.23 client without a .jenv should be considered broken, it cannot talk to any server without a .jenv.