Question

3

JUJU and ERROR environment has no access-key or secret-key

rated 0 times [ 3] [ 0] / answers: 1 / hits: 6114 / 1 Year ago, mon, january 16, 2023, 7:38:14

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"

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

itchlos

Add To Favorites

Follow

Total Points: 486

Total Questions: 115

Total Answers: 110

Location: Macau

Member since Fri, Apr 28, 2023

1 Year ago

itchlos questions

1 How do I remove password from a PDF using ghostscript, when password is known?

Fri, Apr 8, 22, 15:40, 2 Years ago

1 Install Ubuntu server 22.04 without internet

Wed, Nov 10, 21, 23:32, 3 Years ago

1 Facing problem to update software and can't get Ubuntu version 22.04

Mon, Jun 14, 21, 10:10, 3 Years ago

1 Find files with certain text within certain date range

Mon, Nov 28, 22, 20:56, 1 Year ago

1 Failed to start netplan-wpa-wlan0.sevice: Unit netplan-wpa-wlan0.service not found

Sun, Aug 1, 21, 19:12, 3 Years ago

View All

answered 1 Year ago arbaour · Accepted Answer

When nodes in MaaS are in the commissioning state, they are not available for Juju to use. When the nodes are ready for allocation, they will show in MaaS as the Ready state.

When you bootstrap using Juju, it creates a node that will queue future deploy and relation setting commands to be run at the correct time during the installation of the various services.

The gomaasapi: got error back from server: 409 CONFLICT error is a generic error meaning that Maas encountered and error while trying to fulfill your request. In your case, because all of your machines are in a commissioning state and not a ready state, MaaS has no nodes that Juju can use to set up the bootstrap machine on. Because of that, you get the 409 CONFLICT error.

When nodes are in the commissioning state, they should be booted up, running an image from the MaaS server that prepares them for use. You may want to check that the nodes that are supposedly commissioning are booted up and not stuck at some boot prompt or turned off. If they are running, try connecting a monitor to them and see what you can see.

If they are not running, check and see if you have the power setting set in MaaS correct -- MaaS may not be able to signal the machines to boot (using IPMI, WOL, etc) and therefore the commissioning image is never booted and run and the nodes are stuck in the commisioning state without human intervention. (If this is the case, you can get past this by manually (as in physically if the machines are physical, or by telling VirtualBox to start the VM if that is what you are using) powering on the nodes that are stuck in the commissioning state.)

If you are using virtual machines to test MaaS, let me know and I will update my answer -- there are some quirks to testing MaaS with virtual machines.