Riccardo Magrini's questions

My virtual lab via virt-manager:

• MAAS server

• JUJU controller

  but after the bootstrap, using the following command:

  $: juju bootstrap maas-cloud maas-cloud-controller --debug .... .... ....

I've received an error:

13:00:20 ERROR juju.cmd.juju.commands bootstrap.go:776 failed to bootstrap model: cannot start bootstrap instance: unexpected: ServerError: 400 Bad Request ({"distro_series": ["'**bionic**' is not a valid distro_series.  It should be one of: '', 'ubuntu/focal'."]})

All lab is based on Ubuntu 20.04 and I can't understand because it signed me "bionic" when it isn't present.... On MAAS is set the 20.04

someone can explain me that thanks.

how can I increase the quota of the security group set on Openstack? By default it's set on 10 and for my lab I need more of them. If I try to deploy an App this is the error:

OverQuotaClient: resources.security_group_host_group_master_3: Quota exceeded for resources: ['security_group_rule'].

Someone know how I can resolve that? Thanks

I'd like to create a new cloud in JUJU for OPENSTACK and use that to deploy the Apps on my Instances. In my lab, MAAS, JUJU and OPENSTACK are correctly installed and the instancse works fine. I've followed this guide but at the end during the bootstrap I receive this error:

ERROR authentication failed.: authentication failed

IP plan:

Network: 10.20.81.0/24
Maas: 10.20.81.1
Juju: 10.20.81.2
Openstack: 10.20.81.21-24
External Gateway: 10.20.81.254
Private Network: 10.1.0.0/24
Instance: 10.1.0.12 - 10.20.81.220 (floating IP)
Private Gateway: 10.1.0.1
Private DHCP service: 10.1.0.10

Network topology:

                          +-------------+
                              Firewall
                            10.20.81.254
                          +-------------+
                                 | 
+-------------------------------------------------------------+
                              Switch 
      vlan81              vlan81                  vlan81
+-------------------------------------------------------------+
        |                   |                   || | | |
+--------------+     +-------------+       +------------------+
|Maas+Juju           |Juju Gui|            |Openstack
|10.20.81.1          |10.20.81.2           |10.20.81.21-24
+--------------+     +-------------+       +------------------+
                                                     |
                                +----------------------------------------+
                                Private Subnet-1           Public Subnet-2
                                 10.1.0.0/24                10.20.81.0/24
                                 +---+----+--+              +---+------+
                                 |   |        +----+            |
                                 |   |     .1 |    |.221        |
                                 |   +--------+ VR +------------+
                                 |            |    |
                                 +--+-+       +----+
                                 |    |
                                 |VM |
                                 |.12 |
                                 |    |
                                 +----+

these commands have being launched on MAAS server, where I've installed juju.

   $:juju add-cloud
    Cloud Types
      lxd
      maas
      manual
      openstack
      vsphere

Select cloud type: openstack
    Enter a name for your openstack cloud: openstack-cloud
    Enter the API endpoint url for the cloud []: http://10.20.81.22:5000/v3
    Enter a path to the CA certificate for your cloud if one is required to access it. (optional) [none]: 
    Auth Types
  access-key
  userpass
    Select one or more auth types separated by commas: userpass
    Enter region name: RegionOne
   Enter the API endpoint url for the region [use cloud api url]: 
    Enter another region? (y/N): n
   Cloud "openstack-cloud" successfully added
    You will need to add credentials for this cloud (`juju add-credential openstack-cloud`)
before creating a controller (`juju bootstrap openstack-cloud`).


$:juju add-credential openstack-cloud
Enter credential name: richardsith
    Using auth-type "userpass".
    Enter username: admin
    Enter password: 
    Enter tenant-name (optional): 
    Enter tenant-id (optional): 
    Enter version (optional): 
    Enter domain-name (optional): 
    Enter project-domain-name (optional): 
    Enter user-domain-name (optional): 
    Credential "admin" added locally for cloud "openstack-cloud".


Maas_$:juju bootstrap openstack-cloud
ERROR authentication failed.: authentication failed
caused by: requesting token failed
caused by: Resource at http://10.20.81.22:5000/v3/tokens not found
caused by: request (http://10.20.81.22:5000/v3/tokens) returned unexpected status: 404; error info: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<title>404 Not Found</title>
<h1>Not Found</h1>
<p>The requested URL was not found on the server.  If you entered the URL manually please check your spelling and try again.</p>

then

Maas_$:juju list-credentials --format yaml --show-secrets
local-credentials:
  maas-cloud:
    richardsith:
      auth-type: oauth1
      maas-oauth: j3GCen9ncJfJQYQ5ZS:ef59sS4XdwhxVPXLSR:TcxGjfyDXS42yj7afbzWrAuhMJtvNWq5
  openstack-cloud:
    richardsith:
      auth-type: userpass
      password: r1ch@rd!
      username: admin

Maas_$:juju show-cloud openstack-cloud
defined: local
type: openstack
description: Openstack Cloud
auth-types: [userpass]
endpoint: http://10.20.81.22:5000/v3
regions:
  RegionOne: {}

opening that url on my browser I've:

I performed a cluster node installation using this guide [OpenStack Charms Deployment Guide].(https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/latest/install-maas.html), where the type of network is a Flat network and the components used are:

• Maas
• Juju
• Openstack.

My lab has the following network plan:

                         +-------------+
                              Firewall
                            10.20.81.254
                          +-------------+
                                 | 
+-------------------------------------------------------------+
                              Switch 
      vlan81              vlan81                  vlan81
+-------------------------------------------------------------+
        |                   |                   || || || ||
+--------------+     +------------+        +------------------+
|Maas+Juju           |Juju Gui|            |Openstack
|10.20.81.1          |10.20.81.2           |10.20.81.21-24
+--------------+     +-------------+       +------------------+
                                                     |
                                +--------------------------------------------+
                                Private Subnet-1           Public Subnet-2
                                 10.0.0.0/24                10.20.81.0/24
                                 +---+----+--+              +----+------+
                                 |    |        +----+            |
                                 |    |        |    |            |
                                 |    +--------+ VR +-------------+
                                 |             |    |
                                 +--+-+        +----+
                                 |    |
                                 | VM |
                                 | .9 |
                                 |    |

my lab:

1 IBM System 3540 M4 Maas (500GB HDD - 8GB RAM - 1 Nic)
1 IBM System 3540 M4 Juju (500GB HDD - 8GB RAM -1 Nic)
4 IBM System 3540 M4 Openstack (500GBx2 HDD - 16GB RAM - 2 Nic)
1 Palo Alto Network Firewall

IP plan:

Public Network: 10.20.81.0/24
Private Network: 10.0.0.0/24

Maas: 10.20.81.1
Juju: 10.20.81.2
Openstack: 10.20.81.21-24
Gateway 10.20.81.254
Private Network 10.0.0.0/24
Instance: 10.0.0.9 - 10.20.81.215 (floating)

Openstack Router:

Openstack Security Group:

Maas route:

$: ip route
default via 10.20.81.254 dev enp2s0 proto static 
10.20.81.0/24 dev enp2s0 proto kernel scope link src 10.20.81.1 

Juju Controller:

ubuntu@juju-controller:~$ ip route
default via 10.20.81.254 dev enp8s0 proto static 
10.20.81.0/24 dev enp8s0 proto kernel scope link src 10.20.81.2 

Compute Nodes:

ubuntu@os-compute01:~$ ip route
default via 10.20.81.254 dev br-eno2 proto static 
10.20.81.0/24 dev br-eno2 proto kernel scope link src 10.20.81.21 
10.38.53.0/24 dev lxdbr0 proto kernel scope link src 10.38.53.1

ubuntu@os-compute02:~$ ip route
default via 10.20.81.254 dev br-eno2 proto static 
10.20.81.0/24 dev br-eno2 proto kernel scope link src 10.20.81.22 
10.104.230.0/24 dev lxdbr0 proto kernel scope link src 10.104.230.1 

ubuntu@os-compute03:~$ ip route
default via 10.20.81.254 dev br-eno2 proto static 
10.20.81.0/24 dev br-eno2 proto kernel scope link src 10.20.81.23 
10.126.34.0/24 dev lxdbr0 proto kernel scope link src 10.126.34.1 

ubuntu@os-compute04:~$ ip route
default via 10.20.81.254 dev br-eno2 proto static 
10.20.81.0/24 dev br-eno2 proto kernel scope link src 10.20.81.24 
10.72.47.0/24 dev lxdbr0 proto kernel scope link src 10.72.47.1 

Router:

$:openstack router show u1804Ro
Password: 
   +-------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Field                   | Value                                                                                                                                                                                    |
+-------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| admin_state_up          | UP                                                                                                                                                                                       |
| availability_zone_hints |                                                                                                                                                                                          |
| availability_zones      | nova                                                                                                                                                                                     |
| created_at              | 2019-02-28T22:27:36Z                                                                                                                                                                     |
| description             |                                                                                                                                                                                          |
| distributed             | False                                                                                                                                                                                    |
| external_gateway_info   | {"network_id": "e2ba9320-b1cb-4fd8-acd8-b4d9df9df819", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "b3ae37b6-487b-4063-8d69-ec849fd9c9c7", "ip_address": "10.20.81.212"}]} |
| flavor_id               | None                                                                                                                                                                                     |
| ha                      | False                                                                                                                                                                                    |
| id                      | fc288112-3fce-405d-9c3f-5451253de4f0                                                                                                                                                     |
| interfaces_info         | [{"subnet_id": "c7fcfa82-ec70-4917-8f24-7074bf22743b", "ip_address": "10.0.0.1", "port_id": "84693247-3f86-4c84-b0f6-aa8bd95c6c16"}]                                                     |
| name                    | u1804Ro                                                                                                                                                                                  |
| project_id              | 1f4809b5083549c1a35c4c023487752c                                                                                                                                                         |
| revision_number         | 8                                                                                                                                                                                        |
| routes                  |                                                                                                                                                                                          |
| status                  | ACTIVE                                                                                                                                                                                   |
| tags                    |                                                                                                                                                                                          |
| updated_at              | 2019-03-01T14:02:46Z                                                                                                                                                                     |
+-------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

Security Group list

$:openstack security group list
Password: 
+--------------------------------------+----------+-----------------------------+----------------------------------+
| ID                                   | Name     | Description                 | Project                          |
+--------------------------------------+----------+-----------------------------+----------------------------------+
| 57f3fbd9-7574-4116-826f-083a1241bc0f | default  | Default security group      | 3e59e7cde179423abcdce8fe431fbea0 |
| c242b952-8b07-4d25-b24e-ada213cc116f | u1804Sec | Security Group for u1804Pro | 3e59e7cde179423abcdce8fe431fbea0 |
+--------------------------------------+----------+-----------------------------+----------------------------------+

Security Group rule list

$:openstack security group rule list
Password: 
+--------------------------------------+-------------+-----------+------------+--------------------------------------+--------------------------------------+
| ID                                   | IP Protocol | IP Range  | Port Range | Remote Security Group                | Security Group                       |
+--------------------------------------+-------------+-----------+------------+--------------------------------------+--------------------------------------+
| 07b3bd3f-cc62-409c-bc65-62eea6c7b3ea | None        | None      |            | 57f3fbd9-7574-4116-826f-083a1241bc0f | 57f3fbd9-7574-4116-826f-083a1241bc0f |
| 34216d9f-f5fc-44a3-9e1a-ac52b0cdc334 | None        | None      |            | None                                 | 57f3fbd9-7574-4116-826f-083a1241bc0f |
| 472eff92-c0f8-4a7e-806d-de98fe066d8f | tcp         | 0.0.0.0/0 | 22:22      | None                                 | c242b952-8b07-4d25-b24e-ada213cc116f |
| 8f101215-759d-48bc-b665-bd72463ecb3d | None        | None      |            | None                                 | c242b952-8b07-4d25-b24e-ada213cc116f |
| a6a0e040-3cc8-4cc3-bedf-2aa1adc52018 | None        | None      |            | None                                 | 57f3fbd9-7574-4116-826f-083a1241bc0f |
| d4346b18-65b3-49a6-9763-05229e468dac | None        | None      |            | 57f3fbd9-7574-4116-826f-083a1241bc0f | 57f3fbd9-7574-4116-826f-083a1241bc0f |
| dc9f8a32-7315-493a-b8ed-9b5919afc2c8 | None        | None      |            | None                                 | c242b952-8b07-4d25-b24e-ada213cc116f |
+--------------------------------------+-------------+-----------+------------+--------------------------------------+--------------------------------------+

anyone can help me to solve that? thanks in advance

After the deploy of Openstack via Juju the ceph-osd results in blocked

$: juju status 
ceph-osd/0                blocked   idle       1        10.20.253.197                      No block devices detected using current configuration
ceph-osd/1*               blocked   idle       2        10.20.253.199                      No block devices detected using current configuration
ceph-osd/2                blocked   idle       0        10.20.253.200                      No block devices detected using current configuration

I have juju ssh into the first machine with the ceph-osd/0

$: juju ssh ceph-osd/0

and I run the following commands:

$: sudo fdisk -l
Disk /dev/vda: 500 GiB, 536870912000 bytes, 1048576000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xaa276e23

Device     Boot Start        End    Sectors  Size Id Type
/dev/vda1        2048 1048575966 1048573919  500G 83 Linux


Disk /dev/vdb: 500 GiB, 536870912000 bytes, 1048576000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: CAA6111D-5ECF-48EB-B4BF-9EC58E38AD64

Device     Start        End    Sectors  Size Type
/dev/vdb1   2048       4095       2048    1M BIOS boot
/dev/vdb2   4096 1048563711 1048559616  500G Linux filesystem

$: df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            7.9G     0  7.9G   0% /dev
tmpfs           1.6G  856K  1.6G   1% /run
/dev/vda1       492G   12G  455G   3% /
tmpfs           7.9G     0  7.9G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           7.9G     0  7.9G   0% /sys/fs/cgroup
tmpfs           100K     0  100K   0% /var/lib/lxd/shmounts
tmpfs           100K     0  100K   0% /var/lib/lxd/devlxd
tmpfs           1.6G     0  1.6G   0% /run/user/1000  

$: lsblk 
    NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
    vda    252:0    0  500G  0 disk 
    └─vda1 252:1    0  500G  0 part /
    vdb    252:16   0  500G  0 disk 
    ├─vdb1 252:17   0    1M  0 part 
    └─vdb2 252:18   0  500G  0 part 

Where is the button "save"? it's no longer present on Juju gui (Juju GUI at version 2.7.3). If I decide to configure of new parameters on a charm via Juju gui how do I can save that?

while on JAAS it's present

After I deployed Maas and Canonical Distribution of Openstack on a virtual environment (VMware ESXi), I found out that Maas server has a correct clock time while the nodes used for Openstack have different time. On VMware the NTP server is set with ntp.ubuntu.com.

From juju status I saw the container ntpmaster/0 and its ntp.conf is so configurated:

ubuntu@juju-eba318-3-lxd-1:~$ more /etc/ntp.conf
# juju generated ntp configuration
driftfile /var/lib/ntp/ntp.drift
statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable
restrict -4 default kod notrap nomodify nopeer noquery
restrict -6 default kod notrap nomodify nopeer noquery


restrict 127.0.0.1
restrict ::1
# SERVERS


# LOCAL time source
server 127.127.1.0
fudge 127.127.1.0 stratum 5

# PEERS 

why different clock?

Lab:

All environment Lab has been realised using only Ubuntu 16.04 LTS:

1 VM for MAAS + conjure-up (memory: 8GB, CPU: 1, HDD: 500GB);

1 VM for JUJU (memory: 8GB, CPU: 1, HDD: 500GB);

1 VM for LANDSCAPE (memory: 8GB, CPU: 1, HDD: 500GB);

5 VM for OPENSTACK (memory: 16GB, CPU: 1, HDD: 500GBx2);

After to have deployed JUJU, and LANDSCAPE via conjure-up, the last step is to deploy Openstack via Landscape. The initial situation is showed above:

LANDSCAPE has all the requests completed

select the public network

and complete the task selected the modules

then let's start with its own installation

All machines are deployed

the progress goes head

then about 50%, received that error:

any suggest?

All environment Lab has been realised on Ubuntu 16.04 LTS

• 1 VM for MAAS
• 1 VM for JUJU
• 1 VM for LANDSCAPE
• 5 VM for OPENSTACK

The initial situation is the following

running the conjure command as suggest from official guide

$: conjure-up --bootstrap-to nodeJuju

conjure begins the deploy

but after the vm is deployed

I receive this error:

I've pasted the conjure-up.log here (https://paste.ubuntu.com/24328008/), at the end of that there is this error:

*

2017-04-06 14:43:54 ERROR cmd supercommand.go:458 new environ: Authorization Error: 'Expired timestamp: given 1491489833 and now 1491497374 has a greater difference than threshold
 300'

*

any idea?

I saw that LXD and JUJU are available via snap, is there a way to have also MAAS, LANDSCAPE and zfsutils-linux via snap?

Over LXD and JUJU, now we can install also MAAS via snap Install from a Snap, but zfsutils-linux is still missing.

At the end of the procedure of installing there is an option "Virtual Machine Host" in Ubuntu 16.04, someone can explain me what is it?

I've installed Ubuntu MaaS using VMware Workstation on a vm with Ubuntu 14.04 and upgraded it via ppa stable.

I'd like to add some vnodes to MaaS and setting them their Power Type as "VMware" but I don't know how I've to make that

I've also installed the package python-pyvmomi

sudo apt-get install python-pyvmomi --install-suggests

as suggested here

http://maas.ubuntu.com/docs1.8/changelog.html

but nothing. anyone knows how making that? thanks in advance

SOLUTION:

as suggested me by Mike, the solution has been:

• create all my VMs under "Shared VMs";
• filled all parts in "Add Hardware > Chassis" using as values my Host.

Then after few seconds I've seen all VMs in MaaS

run the commission step

I've completed almost all steps about the installation of Canonical Distribution realized it on an Virtual Environment.

At the end the procedure I see Landscape Dashboard deployed of Juju. This is the situation of MaaS

while Landscape

if I scrolled down the page the result has been that

I've added the second HD on all the VM and re-put them in ready state on MaaS, then I've run Openstack with Landscape.... but the error is always the same.

How do I have to upgrade the configuration to see also the second disk and resolve that?

Thanks in advance

I've installed Ubuntu 14.04 with Unity and I'd like to sync my contacts from Google on Gnome contacts without to pass via Evolution.

I've tested it on Gnome Shell 3.14 and it run perfectly while on unity no.

Why? is there a app that I've to install on Ubuntu 14.04 Unity?

thanks in advance.

I've changed my old laptop with a new one but I don't understand why using on both virt-manager the qemu-system-x86 on new one takes 100% of CPU when run a vm, while on old one not.

The command:

lscpu

has this output:

Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                4
On-line CPU(s) list:   0-3
Thread(s) per core:    2
Core(s) per socket:    2
Socket(s):             1
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 69
Stepping:              1
CPU MHz:               754.000
BogoMIPS:              5187.74
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              4096K
NUMA node0 CPU(s):     0-3

While in my old PC it just uses 15%-30% of the CPU. I've also actived the kvm from the BIOS but nothing changes: it continues to use 100%.

The top command gives me:

PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
3410 libvirt+  20   0 3641892 902428  10332 S 101,4 11,2   1:03.36 qemu-system-x86

How should I proceed?

I'd like to upload on my MaaS server (ppa stable) the image of Ubuntu Core ("Snappy") to try it and provision new nodes using that custom image.

I tested Snappy in a KVM environment and now I'd like to test it in my Lab.

How should I proceed?

I'm trying to install the new Canonical Distribution on a virtual environment following the guide published here:

http://www.ubuntu.com/download/cloud/install-ubuntu-openstack

but during the installation the installer gave me this error: " A fatal error has occured: Couldn't create admin See /home/user/.cloud-install/command.log " In the file I saw this lines:

http://paste.ubuntu.com/9006273/

someone knows what went wrong and which is the solution?

I'd like to realize an infrastructure using Ubuntu 14.04Lts like this:

• 1 Region Controller (RC), Ubuntu 14.04 Server Edition
• 2 Cluster Controller(CC), Ubuntu 14.04 Server Edition

MaaS has been installed via Ubuntu ISO and then upgraded using ppa stable, while on two Cluster Controller I've installed only maas-cluster-controller and maas-dhcp maas-dns.

All Servers are on the same network.

When I try to add the two CC on the RC I don't see any pending cluster

I've found this solution Connect cluster controller to the region controller (MaaS) but when I tried to run this command

$: sudo maas-provision install-shared-secret

I've received this error

usage: __main__.py [-h] [-c FILENAME]
                   {atomic-write,customize-config,generate-dhcp-config,install-uefi-config,start-cluster-controller,upgrade-cluster}
                   ...
__main__.py: error: invalid choice: 'install-shared-secret' (choose from u'atomic-write', u'customize-config', u'generate-dhcp-config', u'install-uefi-config', u'start-cluster-controller', u'upgrade-cluster')

I've also found this command on the changelog of MaaS (http://maas.ubuntu.com/docs/changelog.html), the note says that:

"RPC security. As a step towards mutually verified TLS connections between MAAS’s components, 1.7 introduces a simple shared-secret mechanism to authenticate the region with the clusters and vice-versa. For those clusters that run on the same machine as the region controller (which will account for most people), everything will continue to work without intervention. However, if you’re running a cluster on a separate machine, you must install the secret: After upgrading the region controller, view /var/lib/maas/secret (it’s text) and copy it. On each cluster, run: sudo -u maas maas-provision install-shared-secret You’ll be prompted for the secret; paste it in and press enter. It is a password prompt, so the secret will not be echoed back to you. That’s it; the upgraded cluster controller will find the secret without needing to be told."

I've also run that and the error is different

$: sudo -u maas maas-provision install-shared-secret

This utility may only be run as root.

why ???

I've also open this ask some months ago showing the same issue

How to add a new cluster controller to MaaS release 1.7?

I'd like to close that, any suggests to resolve that?

I've a problem with libvirt 1.2.2 and VirtualBox 4.3.

After installing Ubuntu 14.04 server and setting MAAS and JUJU, I need to use virsh to see the list of my installed VM (as reported in the guide How to configure MAAS to be able to boot virtual machines.) I've also created 2 other nodes and set MAAS server correctly, but when trying to use virsh to see the list of the installed VM I don't receive any list.

The command is that:

sudo virsh list --all

While, if I run this

sudo virsh -c vbox:///session

the answer is that

libvir: error : could not connect to vbox:///session error: failed to connect to the hypervisor

Is there someone, who have had the same issue and how to resolve it?

following the official guide:

• https://jujucharms.com/docs/stable/clouds-maas

and considered that I've generated the ssh key (added it to UI of MAAS) and the API key, my environments.yaml file presents in this way:

environments:
  maas:
    type: maas
    maas-server: 'http://x.x.x.x/MAAS/'
    maas-oauth: 'NDPA86PsEzS7bFynSy:vqJLkyHUJbvYzbtY5Q:sXXXXXXXXXXXXXXXXXXXXXX
    admin-secret: 'nothing'
    default-series: precise
    authorized-keys-path: ~/.ssh/id_rsa.pub # or any file you want.

when I try to run the command:

juju bootstrap

receive the following error:

ERROR environment has no access-key or secret-key

Someone can explain me where is the wrong?

• MAAS and JUJU are installed using their ppa stable on an Ubuntu 12.04.3 Server
• I've already enlisted 2 machines on my Maas and they are in Commissioning status
• In the environments.yaml file the line "default" has as value "maas"