Tag Info

New answers tagged

0

So your node is a VM, right? MAAS will call virsh as the "maas" user, so ~maas/.ssh/id_rsa has to exist, be correct in terms of permissions and be a private key allowed to login on the host where the VM is running. You can test it by becoming the maas user on the MAAS machine and trying to use virsh as MAAS would. For example: sudo -H -u maas virsh -c ...


0

The Landscape Autopilot will install Ubuntu OpenStack, as defined in the Ubuntu OpenStack reference architecture. This is also in the process of a major update, so I can't point you to a source of relevant documentation, but I can promise that both that and documentation for the Autopilot installer are in progress, and I will add links to this answer when ...


0

Try adjusting your hardware clock. If you are using Cisco switches, try to enable Portfast. Try to dig and ping your fully qualified domain name of your node and make sure DNS and network connectivity are set right.


1

It is hard to see what is going on from the posted details. I assume by charm store you are referring to the website? In that case, more detail on your topology is required. I'm almost sure that Squid is overkill. Is 172.16.1.0/24 your main subnet, through which you access the internet? What is the gateway of your server, 172.16.1.1? Where are your nodes ...


1

The currently released version does not support HA. That's coming shortly in an upcoming release.


0

I found a solution: 1) I Uses static ip for IPMI and I updated the BIOS of servers. 2) After adding nodes again, everything worked!


1

A few things to check: Verify that MAAS has the images you want to deploy in terms of Ubuntu releases and architecture. Verify that your VM has a big enough disk for an Ubuntu installation (say, give it 10G) Verify in MAAS that the node (VM) hardware is correct, i.e., that MAAS discovered the hardware correctly specially regarding the disk. I don't ...


0

Look inside /etc/init for the conf files instead. You'll find some of the MaaS support services. In addition to restarting the apache server (for the region site) MaaS has quite a bunch, depending on what you need restarted. There's dhcp. sudo service maas-dhcpd restart The cluster daemon,which is essentially the provision manager including twisted and ...


5

If you're using the install resources on the ISO and not the OpenStack Autopilot, then there are no licensing restrictions at all and you can provision and install on as many servers as you want. If you want to use the Autopilot and/or manage those machines with Landscape post-install, you'll need to purchase additional seats to cover your needs. Hope that ...


2

Delete the cached copy /home/test/.juju/environments/maas.jenv, then make sure /home/test/.juju/environments.yaml has the right MAAS API key, and try again.


2

In 14.10 MAAS now handles the importing of boot images. You know longer need to run that script. On the new "Images" page you can start the import process. You can also do this from the command line. Once you have logged in using the command line. [Documentation for logging over the command line is here].1 maas boot-resources import You can then monitor ...


2

Ok, a few things: a) The syntax for no_proxy is an IP or a hostname, separated by commas, not a URL. So yours should have been just the IP. That being said, I don't think you need (or should) specify the proxy itself in there. Take a look at https://jujucharms.com/docs/1.22/howto-proxies b) I think you are missing a port in the http-proxy variable. Or did ...


6

I believe you will have to redeploy the service on that machine. Even in MAAS, it's usually best to recommission the node if its hardware changed.


1

we haven't yet finalized the 1.8 release plan but plan to have a beta out this month. Are there any specific features in 1.8 that you care about that are not in 1.7? We could look into backporting if necessary.


2

If you use the latest Landscape Autopilot, LDS 15.01, then you need at least: one machine for MAAS one machine for LDS 3 machines for OpenStack Details about the networking setup can be found here: https://insights.ubuntu.com/2015/04/10/maas-network-layouts-for-the-landscape-autopilot/ Or at this askubuntu q&a: How should I setup MAAS so that it ...


2

1) Could be a possible bug, the MAAS UI should support multiple entries. 2) You'll need to make your changes within /etc/bind/maas/named.conf* as those files are included into the top level named options.


0

One instance where this is required is when configuring Neutron OpenVSwitch within Autopilot as you will need to select your 'provider' network. That information is pulled from MAAS, therefore, it needs to be defined within MAAS.


2

The warning is unfortunate. Looks like anything you set for the first time will yield that loud WARNING. Checkout this example: andreas@nsn7:~$ juju unset-env http-proxy andreas@nsn7:~$ andreas@nsn7:~$ juju unset-env http-proxy WARNING key "http-proxy" is not defined in the current environment configuration: possible misspelling andreas@nsn7:~$ ...


1

Proxy settings for juju are explained in this question/answer: juju http-proxy and no_proxy settings


1

I suspect your MAAS node cannot reach out to the internet to install the necessary software. The charm-helpers PPA is being used by the node, not your local machine.


2

Try to login on the machines that are stuck in "allocating" and see what's going on. Try juju ssh <unit-name>, or just juju ssh N where "N" is the machine id. Also, the debug-log command you used will by default only show the last few lines, like tail(1). Try juju debug-log --replay, that will give you the full output. But I think your best bet is to ...


0

You can add the MAAS IP to /etc/resolv.conf as a nameserver, but that will get overwritten eventually. How to make it permanent depends on how your network is setup and is out of scope for this question. But it should get you going for now. Alternatively, and temporarily (because the IP will change), you can also just add the node4.maas name to /etc/hosts ...


1

You use deploy when the service doesn't exist yet. You use add-unit when the service already exists.


1

Did you change the interfaces on these two nodes after commissioning? If you did, can you try commissioning them again in their current state and then try to bootstrap with juju manually? Instructions on how to configure juju with MAAS can be found here: https://jujucharms.com/docs/1.20/config-maas


1

Note: Clicking resolve in the GUI as you did you're actually telling Juju that the issue has been resolved not telling it to resolve the issue. It's hard to debug why Wordpress isn't working in this case without actually poking at it but the failure to add the new unit may have put the charm in a broken state which hasn't actually been resolved (see ...


0

I'll add a general answer here that could help others. When encountering such issues, where it's not clear what is failing, the general suggestion is to go simple. In this case, try to provision nodes in MAAS directly with juju instead of going through the cloud installer. It should be much easier and faster to debug. This URL has instructions on to use ...


1

While it is "stuck" there, can you ssh into 172.16.1.141 (the address from your screenshot, it will vary between attempts) as ubuntu, from the same machine where you are bootstrapping from? I've seen this before and there was a stuck dpkg or apt-get process on that node as a result of an incorrect MTU. Meaning, ssh worked, but as soon as a transfer of ...


0

Try inspecting the MAAS logs, I think something is wrong over there. Also, looks like you are not running the latest MAAS, and it also helps to run the latest juju: sudo add-apt-repository ppa:juju/stable sudo add-apt-repository ppa:maas-maintainers/stable sudo apt-get update sudo apt-get dist-upgrade # (or selectively install juju-core and maas ...


0

Does this work after bootstrap? juju deploy --repository=/opt/charms local:trusty/mysql juju deploy --repository=/opt/charms local:trusty/wordpress There is no need to add-machine and then deploy. You can also specify --constraints in the deploy command line if needed, but let's start simple.


0

You have one node. One node is allocated for juju-gui. You are asking for 2 more nodes. You only have one node, and it is in use, so you have no matching nodes available. If you are using VMs, you need to build two more. If you are using hardware, you need to buy more.


2

MAAS will make sure /you/ have access to each node by adding the key that Juju tells it (and that key is only your public-key). Units do not have SSH access to themselves by design (think of the security implications!). If you wanted to make it so that all units or services can access each other you need to have each machines generate an SSH key for the ...


1

In answer to your general question, the cloud-init package is responsible for generating host keys during first boot on cloud images. In your more specific case, I don't think it currently generates ed25519 keys, but this hasn't been known to cause any issues for any users. If it does cause a problem for you, you should note your use case in more detail in ...



Top 50 recent answers are included