yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1799301@xxxxxxxxxxxxxxxxxx>]

[Expired for cloud-init because there has been no activity for 60 days.]

** Changed in: cloud-init
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1799301

Title:
  SUSE sysconfig renderer enablement incomplete

Status in cloud-init:
  Expired

Bug description:
  With db50bc0d9 the sysconfig renderer was enabled for openSUSE and
  SUSE Linux Enterprise. This implementation is incomplete and network
  rendering for openSUSE and SLES is now completely broken.

  Message in cloud-init.log:

  stages.py[ERROR]: Unable to render networking. Network config is
  likely broken: No available network renderers found. Searched through
  list: ['eni', 'sysconfig', 'netplan']

  The issue is that the available() method in sysconfig.py looks for

      expected_paths = [
          'etc/sysconfig/network-scripts/network-functions',
          'etc/sysconfig/network-scripts/ifdown-eth']

  in addition to ifup and ifdown. While ifup and ifdown are found the
  above scripts do not exists on openSUSE and SLES.

  The equivalent to 'etc/sysconfig/network-scripts/network-functions' would be 'etc/sysconfig/network/functions.netconfig', there is no default ifdown-eth, any ifdown scripts would exist in
  'etc/sysconfig/network/if-down.d' but this is empty by default.

  One option is of course to not look for such specific location and
  "trust" that the necessary script for the given distro are installed.
  We would only check for ifup and ifdown commands as those are
  necessary. The underying distro implementation for script handling may
  not be as important here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1799301/+subscriptions