The error is specific to models created before upgrade of the controller, new 2.5.2 models can deploy the bundle with no errors.
I did notice, if you go back to use the 2.4.7 juju client successful to deploy:
$ /snap/bin/juju version
2.5.2-cosmic-amd64
$ /snap/bin/juju status
Model Controller Cloud/Region Version SLA Timestamp
ubuntu 1821418-2.4.7 localhost/localhost 2.5.2 unsupported 14:56:25-04:00
App Version Status Scale Charm Store Rev OS Notes
ubuntu 16.04 active 1 ubuntu jujucharms 12 ubuntu
Unit Workload Agent Machine Public address Ports Message
ubuntu/0* active idle 0 10.121.191.12 ready
Machine State DNS Inst id Series AZ Message
0 started 10.121.191.12 juju-1f3ed3-0 xenial Running
8$ /snap/bin/juju deploy ./bundle25.yaml
ERROR cannot deploy bundle: connection is shut down
$ sudo snap refresh juju --channel 2.4/stable
juju (2.4/stable) 2.4.7 from Canonical✓ refreshed
$ /snap/bin/juju version
2.4.7-cosmic-amd64
$ /snap/bin/juju deploy ./bundle25.yaml
No changes to apply.
$
Reproduced with info in comments #6 and #7.
The error is specific to models created before upgrade of the controller, new 2.5.2 models can deploy the bundle with no errors.
I did notice, if you go back to use the 2.4.7 juju client successful to deploy:
$ /snap/bin/juju version
2.5.2-cosmic-amd64
$ /snap/bin/juju status
Model Controller Cloud/Region Version SLA Timestamp
ubuntu 1821418-2.4.7 localhost/localhost 2.5.2 unsupported 14:56:25-04:00
App Version Status Scale Charm Store Rev OS Notes
ubuntu 16.04 active 1 ubuntu jujucharms 12 ubuntu
Unit Workload Agent Machine Public address Ports Message
ubuntu/0* active idle 0 10.121.191.12 ready
Machine State DNS Inst id Series AZ Message
0 started 10.121.191.12 juju-1f3ed3-0 xenial Running
8$ /snap/bin/juju deploy ./bundle25.yaml
ERROR cannot deploy bundle: connection is shut down
$ sudo snap refresh juju --channel 2.4/stable
juju (2.4/stable) 2.4.7 from Canonical✓ refreshed
$ /snap/bin/juju version
2.4.7-cosmic-amd64
$ /snap/bin/juju deploy ./bundle25.yaml
No changes to apply.
$