yahoo-eng-team team mailing list archive

[James Falcon <1878682@xxxxxxxxxxxxxxxxxx>]

I set the Ubuntu aspect of this as "Won't Fix" as this is really an
upstream bug and will be tracked on GitHub.

** Changed in: cloud-init (Ubuntu)
       Status: Triaged => Won't Fix

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

Title:
  IPv6 not enabled by default

Status in cloud-init:
  Expired
Status in cloud-init package in Ubuntu:
  Won't Fix

Bug description:
  In ubuntu-20.04-server-cloudimg-amd64-disk-kvm.img provided on cloud-
  images.ubuntu.com does not have IPv6 enabled by default. This
  precludes the use of an IPv6 webserver (URL supplied with the SMBIOS
  option) to feed the NoCloudNet datasource.

  I can enable IPv6 using "network-config" on a NoCloud cidata volume,
  but at that point I might as well just put my user-data in there and
  not use NoCloudNet. I would prefer to avoid this method.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cloud-init 20.1-10-g71af48df-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-1009.9-kvm 5.4.30
  Uname: Linux 5.4.0-1009-kvm x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CloudName: NoCloud
  Date: Thu May 14 15:26:23 2020
  PackageArchitecture: all
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: cloud-init
  UpgradeStatus: No upgrade log present (probably fresh install)
  logs.tgz: Error: [Errno 2] No such file or directory: '/tmp/cloud-init-logs.tgz'

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