*** This bug is a duplicate of bug 1721808 ***
    https://bugs.launchpad.net/bugs/1721808

I believe there was a similar bug report from manjo before. which was
fixed by upgrading to the stable PPA.

However, we do request and require that MAAS as installed from xenial-
updates (and all deps) are working correctly.

What is missing from xenial-updates? Please make this bug report affect
those packages with xenial series as affected.

** Changed in: maas
       Status: Invalid => Confirmed

** Also affects: maas (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: maas (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: maas (Ubuntu Xenial)
   Importance: Undecided => Critical

** Changed in: maas (Ubuntu)
       Status: New => Fix Released

** Changed in: maas (Ubuntu Xenial)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1726909

Title:
  Nodes fail deploying with 17.10 due to hang on "waiting for network"
  at boot

Status in MAAS:
  Invalid
Status in maas package in Ubuntu:
  Fix Released
Status in maas source package in Xenial:
  Invalid

Bug description:
  When I try to deploy an Artful image to nodes that previously deployed
  properly with 16.04, deployment fails due to timeout. It seems that
  the curtin install finishes successfully but the nodes are hanging at
  'Waiting for network' on boot.

  After looking into the image it seems as though MaaS/Curtin are
  setting the node up with '/etc/network/interfaces' instead of netplan,
  which is no longer supported.

  
  Output of 'dpkg -l '*maas*'|cat':

  ||/ Name                            Version                              
Architecture Description
  
+++-===============================-====================================-============-=============================================
  un  maas                            <none>                               
<none>       (no description available)
  ii  maas-cli                        2.2.2-6099-g8751f91-0ubuntu1~16.04.1 all  
        MAAS client and command-line interface
  ii  maas-common                     2.2.2-6099-g8751f91-0ubuntu1~16.04.1 all  
        MAAS server common files
  ii  maas-dns                        2.2.2-6099-g8751f91-0ubuntu1~16.04.1 all  
        MAAS DNS server
  ii  maas-proxy                      2.2.2-6099-g8751f91-0ubuntu1~16.04.1 all  
        MAAS Caching Proxy
  ii  maas-region-api                 2.2.2-6099-g8751f91-0ubuntu1~16.04.1 all  
        Region controller API service for MAAS
  ii  maas-region-controller          2.2.2-6099-g8751f91-0ubuntu1~16.04.1 all  
        Region Controller for MAAS
  un  maas-region-controller-min      <none>                               
<none>       (no description available)
  un  python-django-maas              <none>                               
<none>       (no description available)
  un  python-maas-client              <none>                               
<none>       (no description available)
  ii  python3-django-maas             2.2.2-6099-g8751f91-0ubuntu1~16.04.1 all  
        MAAS server Django web framework (Python 3)
  ii  python3-maas-client             2.2.2-6099-g8751f91-0ubuntu1~16.04.1 all  
        MAAS python API client (Python 3)
  ii  python3-maas-provisioningserver 2.2.2-6099-g8751f91-0ubuntu1~16.04.1 all  
        MAAS server provisioning libraries (Python 3)

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1726909/+subscriptions

_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

Reply via email to