yahoo-eng-team team mailing list archive

[Alexsander de Souza <2065787@xxxxxxxxxxxxxxxxxx>]

the '/run/net-*' files should follow klibc's ipconfig format [1], but
the documentation is misleading. In one place it says that PROTO should
be one of 'dhcp', 'bootp', 'rarp' or 'none', but later it states that
'off', 'static' and 'none' means no autoconfiguration. cloud-init
follows the former specification, while klibc implementation and open-
iscsi scripts use the latter.

This can be fixed by:

A) fixing cloud-init (`cloudinit/net/cmdline.py:94`) to allow `off` and
`static`

B) fixing open-iscsi (`debian/extra/initramfs/local-top/iscsi:172`) to
use `none` instead of `static`

Either way, this is not a MAAS bug


[1] https://git.kernel.org/pub/scm/libs/klibc/klibc.git/plain/usr/kinit/ipconfig/README.ipconfig

** Also affects: cloud-init
   Importance: Undecided
       Status: New

** Also affects: open-iscsi
   Importance: Undecided
       Status: New

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
       Status: New

** No longer affects: cloud-init

** No longer affects: open-iscsi

** Also affects: open-iscsi (Ubuntu)
   Importance: Undecided
       Status: New

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

-- 
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/2065787

Title:
  Error on cloud-init when kernel parameter "iscsi_auto" is set

Status in MAAS:
  Invalid
Status in cloud-init package in Ubuntu:
  New
Status in open-iscsi package in Ubuntu:
  New

Bug description:
  On server enlistment, when the kernel parameter "iscsi_auto" is set and the VM has a local disk (I don't know if the local disk is part of this error), an error is raised at the cloud-config level.
  I have attached a screenshot of the error. If necessary, I have a video of the full boot process.

  Another important thing: this environment is running on top of Cisco
  UCS.

  I am available to assist in resolving the issue. If deemed necessary,
  we can schedule a call and conduct tests in a testing environment
  (where this error is occurring).

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