Tag Info

New answers tagged

0

I'm not 100% sure, but I made a new network in MAAS called public and added the 2nd NIC from all my dual NIC'd computers in MAAS that are on that network. (I have 3) Then in landscape's Open vSwitch configuration I chose this 'public' network. It got me past that step, don't know if it works correctly as I found your post since I was having the same ...


3

Not a 100% complete answer since I may need more details. Please comment here if you have anything updated you need me to look at. But, I think this could be your issue. The checklist is dynamic, it will compute again when you reload the page. You will not need to re-install landscape. I suspect you probably did try to reload the page already -- I'm ...


0

Try https://launchpad.net/~maas-maintainers/+archive/ubuntu/stable for the current stable version of MAAS.


0

I had a problem with the dns forwarder on my maas server which was probably the cause of this. An upgrade to an updated maas pointed out the problem to me. After fixing it machines seem to be deploying better.


0

The developers are working on a proper fix for this, but they gave me a work around that does the job. The workaround looks like: mkdir ~/.cloud-install touch ~/.cloud-install/multi openstack-install -u


3

I will answer my own post again. The problem was that the maas nodes didn't have network connectivity. I have turned maas controller into a gateway/router edited resolv.conf on every node and when I got internet connectivity through the maas controller and host resolution charms installed without a problem. I would recommend everyone who faces this problem ...


1

Problem resolved. If you ssh to a server and your keyboard layout is not the same as the language settings on the server juju fails to bootstrap the system. I have changed my layout to en_US and bootstrapping worked fine. It's the similar problem when you install postgresql where it fails to install if you don't have the same keyboard layout language as the ...


0

I had this same issue... unfortunately it was quicker for me to rebuild than to troubleshoot, so no help there. I did find though that if you press "q" to exit this issue does not occur. If you hit "cancel" though this problem pops up again.


0

Make sure your node's hardware architecture is set to amd64/generic.


0

So, I re-commissioned all of my servers, cleared out the .juju directory, except for my environments.yaml and I still get "TLS handshake failed: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "juju-generated CA for environment \"maas\"")". What more ...


0

The problem appears to have been caused by the physical clocks being not in sync enough with the server and critical parts of the commissioning happen before they run ntpdate. I installed 3 commissioning files to sync ntpdate andd the hardware clock. 01-ntpdate - sync's with ntpdate and then writes to the hardware clock #!/bin/sh /usr/sbin/ntpdate -v ...


0

The charm updates to support the Juno OpenStack release are fully compatible with the RabbitMQ charm - we test this on every commit we make to any of the OpenStack charms as part of the day-to-day charm development cycle. The RabbitMQ (rabbitmq-server) charm should be automatically creating users under the openstack vhost for all related services, and ...


0

You may not need both wakeonlan and etherwake. The template for wakeonlan in /etc/maas/templates/power/ether_wake.template checks for wakeonlan first and checks etherwake if wakeonlan is not installed. I found that my servers would wake up if I used etherwake, but not with wakeonlan. etherwake defaults to using eth0. My maas server needed to use em1 ...


2

I'm not sure about all the downloads that you are seeing but at least lxc images are retrieved over HTTPS so will not be cacheable. See: https://www.mail-archive.com/juju@lists.ubuntu.com/msg01303.html


1

The installer sets apt-http-proxy to whatever your MAAS server IP is for an existing MAAS installation. So whenever juju deploys any services which require apt-get installs it'll pull from that proxy.


0

From https://wiki.ubuntu.com/ServerTeam/CloudToolsArchive: "The Cloud Tools archive is only supported on Ubuntu 12.04" I guess they haven't gotten to updating it to support 14.04. The maas package in 14.10 is at version 1.7.0~beta8+bzr3272-0ubuntu1 -- note the "beta" word there, so as far as stable releases go, what is in 14.04 is the latest one.


3

The Canonical Distribution of Ubuntu OpenStack is based on the same packages Ubuntu OpenStack is, but is deployed as a standard reference architecture using Landscape automation (we call this the OpenStack Autopilot), and is a brand associated with using Ubuntu technologies within Canonical's best practices. One thing is building an Ubuntu OpenStack using ...


1

From OP's second comment; I resolved the problem with re-installing MaaS via the Ubuntu ISO, without using the CLI.


0

Can you check if you are running the latest version of the cloud installer from this ppa? ppa:cloud-installer/testing If -u from that ppa doesn't work, let's debug it and file a bug.


0

You can set your HTTP/S proxy within the settings page in the MAAS web UI under Network Configuration.



Top 50 recent answers are included