Network issues after upgrading to 2.3

Blake Rouse blake.rouse at canonical.com
Mon Mar 19 13:15:31 UTC 2018


Nick,

I would review your settings in both regiond.conf and rackd.conf to make
sure that they have the maas_url configured correctly. You should review
the interface configuration of your controller on the "Controllers" tab to
make sure the networking configuration looks correct.

If you need to make any changes to the regiond.conf and rackd.conf, be sure
to restart maas-regiond and maas-rackd.

Hopefully that helps!

Thanks,
Blake Rouse
Technical Lead Software Engineer
MAAS Team
Canonical Ltd.

On Mon, Mar 19, 2018 at 3:57 AM, Nick Tan <nick.tan at spookfish.com> wrote:

> Hi again,
>
>
>
> I created a squashfs image with a root password so I could get in and look
> at the cloud-init logs.  This entry caught my eye:
>
>
>
> DataSourceMAAS.py[CRITICAL]: Giving up on md from [‘http://
> [::1]/MAAS/metadata/2012-03-01/meta-data/instance-id’] after 126 seconds
>
>
>
> Digging deeper, the cloud-init.log shows this at the start:
>
>
>
> 2018-03-19 07:00:11,115 - util.py[DEBUG]: Cloud-init v. 17.2 running
> 'init-local' at Mon, 19 Mar 2018 07:00:11 +0000. Up 12.77 seconds.
>
> 2018-03-19 07:00:11,116 - main.py[INFO]: wrote cloud-config data from
> cloud-config-url='http://10.18.39.2/MAAS/metadata/latest/
> by-id/8taaws/?op=get_preseed' to /etc/cloud/cloud.cfg.d/91_
> kernel_cmdline_url.cfg
>
>
>
> At this point it is using the correct IP address of the MAAS server
> (10.18.39.2).  Next, I had a look at the /etc/cloud/cloud.cfg.d/91_kernel_cmdline_url.cfg
> file and it’s replaced the IP address with [::1]
>
>
>
> #cloud-config
>
> apt:
>
>   preserve_sources_list: false
>
>   primary:
>
>   - arches: [default]
>
>     uri: http://archive.ubuntu.com/ubuntu
>
>   proxy: http://[::1]:8000/
>
>   security:
>
>   - arches: [default]
>
>     uri: http://archive.ubuntu.com/ubuntu
>
> apt_proxy: http://[::1]:8000/
>
> datasource:
>
>   MAAS: {consumer_key: xxxxxx, metadata_url: 'http://
> [::1]/MAAS/metadata/',
>
>     token_key: xxxxxx, token_secret: xxxxxx}
>
> manage_etc_hosts: true
>
> reporting:
>
>   maas: {consumer_key: xxxxxx, endpoint: 'http://[::1]/MAAS/metadata/
> status/8taaws',
>
>     token_key: xxxxxx, token_secret: xxxxxx,
>
>     type: webhook}
>
> rsyslog:
>
>   remotes: {maas: '::1:514'}
>
> system_info:
>
>   package_mirrors:
>
>   - arches: [i386, amd64]
>
>     failsafe: {primary: 'http://archive.ubuntu.com/ubuntu', security: '
> http://security.ubuntu.com/ubuntu'}
>
>     search:
>
>       primary: ['http://archive.ubuntu.com/ubuntu']
>
>       security: ['http://archive.ubuntu.com/ubuntu']
>
>   - arches: [default]
>
>     failsafe: {primary: 'http://ports.ubuntu.com/ubuntu-ports', security:
> 'http://ports.ubuntu.com/ubuntu-ports'}
>
>     search:
>
>       primary: ['http://ports.ubuntu.com/ubuntu-ports']
>
>       security: ['http://ports.ubuntu.com/ubuntu-ports']
>
>
>
>
>
> I’m thinking that somewhere in my MAAS server settings it’s configured to
> send a IPv6 address?  I can’t find anything in the web GUI, is there a CLI
> command I can run to find out and fix it?
>
>
>
> Thanks,
>
> Nick
>
>
>
> *Nick Tan,* Senior Systems Administrator
>
> *Spookfish Global Operations Pty Ltd*
>
> m: +61 413 134 846
>
> w: spookfish.com
>
> *From: *Maas-devel <maas-devel-bounces at lists.ubuntu.com> on behalf of
> Nick Tan <nick.tan at spookfish.com>
> *Date: *Monday, 19 March 2018 at 12:19 pm
> *To: *"maas-devel at lists.ubuntu.com" <maas-devel at lists.ubuntu.com>
> *Subject: *Network issues after upgrading to 2.3
>
>
>
> This sender failed our fraud detection checks and may not
> be who they appear to be. Learn about spoofing
> <http://aka.ms/LearnAboutSpoofing>
>
> Feedback <http://aka.ms/SafetyTipsFeedback>
>
> Hi all,
>
>
>
> I had a functioning MAAS 2.0.0 install which I recently upgraded to
> 2.3.0.  Since then, I can’t commission or deploy machines.  It looks like
> I’m hitting the same problem as https://bugs.launchpad.net/
> maas/+bug/1738782 ie: the node boots, but stalls at “MAAS: searching for
> network data from DataSourceMAAS” before continuing to a login prompt and
> doing nothing.
>
>
>
> Nothing on the network side has changed - just the upgrade of MAAS.  All
> the MAAS components are installed on the same server running Ubuntu 16.04
> server.
>
>
>
> Has anyone else seen this issue and have any ideas on how to resolve it?
> Is it feasible to downgrade back to 2.0.0?
>
>
>
> Thanks,
>
> Nick
>
>
>
> *Nick Tan,* Senior Systems Administrator
>
> *Spookfish Global Operations Pty Ltd*
>
> m: +61 413 134 846
>
> w: spookfish.com
>
> PRIVACY AND CONFIDENTIALITY NOTICE
> *The information contained in this message is intended for the named
> recipients only. It may contain confidential information and if you are not
> the intended recipient, you must not copy, distribute or take any action in
> reliance on it. If you have received this message in error please destroy
> it and reply to the sender immediately or contact us at the above telephone
> number. *
> VIRUS DISCLAIMER
> *While we take every precaution against presence of computer viruses on
> our system, we accept no responsibility for loss or damage arising from the
> transmission of viruses to e-mail recipients.*
>
> PRIVACY AND CONFIDENTIALITY NOTICE
> *The information contained in this message is intended for the named
> recipients only. It may contain confidential information and if you are not
> the intended recipient, you must not copy, distribute or take any action in
> reliance on it. If you have received this message in error please destroy
> it and reply to the sender immediately or contact us at the above telephone
> number. *
> VIRUS DISCLAIMER
> *While we take every precaution against presence of computer viruses on
> our system, we accept no responsibility for loss or damage arising from the
> transmission of viruses to e-mail recipients.*
>
> --
> Maas-devel mailing list
> Maas-devel at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/maas-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/maas-devel/attachments/20180319/c8cc51db/attachment.html>


More information about the Maas-devel mailing list