using juju 1.25.13 (from ppa:juju/stable) in an updated trusty system
this problem is still there, to solve it default-series can be set.

root@juju1:~# apt-cache policy distro-info-data
distro-info-data:
  Installed: 0.18ubuntu0.8
  Candidate: 0.18ubuntu0.8
  Version table:
 *** 0.18ubuntu0.8 0
        500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     0.18ubuntu0.7 0
        500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
     0.18 0
        500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
root@juju1:~# cat .juju/environments.yaml 
default: maas

environments:
    maas:
        type: maas
        maas-server: 'http://1.2.3.4/MAAS/'
        maas-oauth: 'XXXX'
        bootstrap-timeout: 1800

root@juju1:~# juju bootstrap --constraints tags=virtual --upload-tools=true     
                                                                                
              
Bootstrapping environment "maas"
Starting new instance for initial state server
Launching instance
WARNING no architecture was specified, acquiring an arbitrary node
Bootstrap failed, destroying environment
ERROR failed to bootstrap environment: cannot start bootstrap instance: 
gomaasapi: got error back from server: 400 BAD REQUEST ({"distro_series": 
["'bionic' is not a valid distro_series.  It should be one of: '', 
'centos/centos66', 'centos/centos70', 'ubuntu/trusty', 'ubuntu/xenial', 
'ubuntu/zesty', 'ubuntu/artful'."]})
root@juju1:~# vim .juju/environments.yaml
root@juju1:~# cat .juju/environments.yaml 
default: maas

environments:
    maas:
        type: maas
        default-series: xenial
        maas-server: 'http://1.2.3.4/MAAS/'
        maas-oauth: 'XXXX'
        bootstrap-timeout: 1800
root@juju1:~# juju bootstrap --constraints tags=virtual 
Bootstrapping environment "maas"
Starting new instance for initial state server
Launching instance
WARNING no architecture was specified, acquiring an arbitrary node
 - /MAAS/api/1.0/nodes/node-203ee4d8-42c9-11e5-9809-5254006803c2/
Installing Juju agent on bootstrap instance
Waiting for address
Attempting to connect to vm9.maas:22
...
Fetching tools: curl ...
Bootstrapping Juju machine agent
Starting Juju machine agent (jujud-machine-0)
Bootstrap agent installed
maas -> maas
Waiting for API to become available
Waiting for API to become available
Bootstrap complete


** Also affects: juju-core
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727355

Title:
  Juju attempts to bootstrap bionic by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1727355/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to