Public bug reported:
Brent Baude and Paul Meyer realized that on Azure, that when the
'agent_command' is set to __builtin__ (the current default in trunk)
that cloud-init does not bounce the network device in order to do a ddns
update of the systems' hostname.
** Affects: cloud-init
Public bug reported:
As discussed some in merge proposal at [1].
The sysconfig renderer could use some work.
a.) seems like we should not be rendering ifcfg-lo at least in the case that it
already exists.
b.) we should be able to now replace _write_network with something that uses
The last screenshot (ipaddrdelifup.png) we think shows what went wrong.
Jason had an rtl device attached to this kvm vm. It doesn't seem to like
setting the MTU to 9000.
Possibly that is a bug in the driver, or possibly it is a limitation of the
(emulated or real) hardware.
2 fixes:
a.) do
** Also affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1669875
Title:
identify openstack vmware platform
** Changed in: cloud-init
Status: Confirmed => Fix Committed
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
Report mode could exit with 1 (disable) and the caller (cloud-init-
generator) would then disable cloud-init.
Thats not very "report only".
The change needed is to just make report always exit with 0 (enable).
** Affects: cloud-init
Importance: Undecided
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init
Public bug reported:
We need a way to identify locally that we are running on openstack when
inside a guest of VmWare.
** Affects: cloud-init
Importance: Medium
Status: Confirmed
** Tags: dsid
--
You received this bug notification because you are a member of Yahoo!
Engineering
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init
Status: New => Fix Released
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in:
Marking fix-released in nova-lxd in zesty.
** Description changed:
nova-lxd uses the Openstack Network metadata service.
In an effort to avoid polling metadata services in cloud-init we will disable
attempts to reach the MD without positive identification of the cloud.
We need to
** Also affects: cloud-init (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu Xenial)
Status: New => Incomplete
** Changed in: cloud-init (Ubuntu Yakkety)
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Also affects: cloud-init (Ubuntu Yakkety)
Importance: Undecided
** Changed in: cloud-init (Ubuntu)
Status: Fix Released => Confirmed
--
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/1667735
Title:
cloud-init doesn't retry metadata lookups
** No longer affects: cloud-init
** No longer affects: cloud-init (Ubuntu)
** No longer affects: cloud-init (Ubuntu Xenial)
** No longer affects: cloud-init (Ubuntu Yakkety)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
** Changed in: cloud-init
Status: Confirmed => Fix Committed
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
--
Public bug reported:
when cloud-init writes mount entries into /etc/fstab, it adds:
x-systemd.requires=cloud-init.service
This is because a subsequent boot of cloud-init may need to remove that
entry (a new instance for example).
cloud-init has a feature where it can be disabled by:
sudo
service
Status in cloud-init:
New
Status in cloud-init package in Ubuntu:
New
Bug description:
Had a private chat conversation with Scott Moser (@smoser). As per his
instructions, logging this bug. We need to add 'cloud-init' dependency
for 'open-vm-tools' service.
This is how 'Guest
Public bug reported:
Currently there is no positive identification for ovf datasource in ds-identify.
The ovf specification for iso transport only says that there will be a cdrom
attached in iso9660 format, and that it would have an 'ovf-env.xml' file.
At this point, ds-identify does not do any
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: nova-lxd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Zesty)
Importance: High
Status: Fix Released
** Also affects: nova-lxd
** Summary changed:
- ds-identify finding by fslable does not work right
+ ds-identify finding by fslabel does not work right
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init
Status:
Public bug reported:
in vmtest for curtin, we fail to boot the installed system because
has_fs_with_label does not work right.
** Affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
** Changed in: cloud-init
Status: Confirmed => Fix Committed
** Also affects: nova-lxd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nova-lxd (Ubuntu)
Status: New => Confirmed
** Changed in: nova-lxd (Ubuntu)
Importance: Undecided => Medium
--
You
Public bug reported:
On i386 and amd64, openstack puts 'OpenStack Nova', into the dmi platform
information. OpenStack using kvm on ppc64el or ppc64, does not identify itself
to the guest in any way.
The result is that cloud-init cannot identify it is running on
openstack.
We need two things
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: nova
Status: New => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Public bug reported:
On i386 and amd64, openstack puts 'OpenStack Nova', into the dmi platform
information. OpenStack using kvm on arm64, does not identify itself to the
guest in any way.
The result is that OpenStack nodes will not attempt to reach the metadata
service and will be unusable.
We
** Also affects: cloud-init (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu Yakkety)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Yakkety)
Importance: Undecided => Medium
--
You received this bug notification because you
** Also affects: cloud-init (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu Yakkety)
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Also affects: nova-lxd
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in:
Public bug reported:
nova-lxd uses the Openstack Network metadata service.
In an effort to avoid polling metadata services in cloud-init we will disable
attempts to reach the MD without positive identification of the cloud.
We need to be able to positively identify that the container we are
Public bug reported:
Brightbox provides an EC2 Metadata service lookalike, and that is how cloud-init
gets metadata on their platform.
In an effort to avoid polling metadata services in cloud-init we will disable
attempts to reach the MD without positive identification of the cloud.
We need to
/identify_ec2_instances.html
** Affects: cloud-init
Importance: Medium
Assignee: Scott Moser (smoser)
Status: In Progress
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init
Status: Con
** Changed in: cloud-init
Status: In Progress => Fix Committed
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Committed
** Changed in: cloud-init (Ubuntu)
Status: Fix Committed =>
Public bug reported:
Currently, a config like this:
| version: 1
| config:
|- 'type': 'physical'
| 'name': 'iface0'
| 'subnets':
|- {'type': 'dhcp4'}
|- {'type': 'dhcp6'}
Will render:
| auto lo
| iface lo inet loopback
|
| auto iface0
| iface iface0 inet dhcp
|
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => Medium
** No longer affects: maas (Ubuntu)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
This is fixed in 0.7.9.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
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/1611074
Title:
Reformatting of
** Changed in: cloud-init
Status: Confirmed => Fix Released
** Changed in: cloud-init
Milestone: 0.7.9 => None
--
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/1351960
Title:
This is fixed in cloud-init 0.7.9.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
This is fixed in cloud-init 0.7.9.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
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/1354694
Title:
useradd
This is fixed in cloud-init 0.7.9.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
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/1460715
Title:
MBR disk
This is fixed in cloud-init 0.7.9.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
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/1354694
Title:
useradd
This is fixed in cloud-init 0.7.9.
** Changed in: cloud-init
Status: Fix Released => Fix Committed
--
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/1354694
Title:
useradd
This is fixed in cloud-init 0.7.9.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
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/1538522
Title:
Calls
This is fixed in cloud-init 0.7.9.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
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/1621615
Title:
network not
This is fixed in cloud-init 0.7.9.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
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/1626243
Title:
Cloud-init
This is fixed in cloud-init 0.7.9.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
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/1642062
Title:
This is fixed in cloud-init 0.7.9.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
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/1629797
Title:
resolve
This is fixed in cloud-init 0.7.9.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
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/1639930
Title:
initramfs
** Also affects: cloud-init
Importance: Undecided
Status: New
--
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/1636912
Title:
systemd-networkd runs too late for
This is fixed in cloud-init 0.7.9.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
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/1628337
Title:
cloud-init
This is fixed in cloud-init 0.7.9.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
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/1635350
Title:
unit tests
This is fixed in cloud-init 0.7.9.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init
Status: New => Fix Released
--
You received this bug notification because you are a member
This is fixed in cloud-init 0.7.9.
** Changed in: cloud-init
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1642679
Title:
The
This is fixed in cloud-init 0.7.9.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
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/1643990
Title:
This is fixed in cloud-init 0.7.9
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
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/1582323
Title:
Commissioning
This is fixed in cloud-init 0.7.9.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
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/1625766
Title:
Fallback
This is fixed in cloud-init 0.7.9.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
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/1644043
Title:
Read Kernel
This is fixed in cloud-init 0.7.9.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Importance: Undecided => High
** Changed in: cloud-init
Status: New => Fix Released
--
You received this bug notification because you are a member of
This is fixed in cloud-init 0.7.9.
** Changed in: cloud-init
Status: New => Fix Released
--
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/1647910
Title:
hostname is set
Public bug reported:
I was again bit by this... tox works fine (running flake8)
but built of zesty failed.
In cloud-init, the Makefile that is run during build runs (currently)
pep8 and pyflakes (either pyflakes2 or pyflakes3).
I think what we ultimately want is to run flake8 and let it run
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu)
** Changed in: cloud-init (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: cloud-init
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Low
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Changed in: cloud-init
Status: Triaged => Fix Committed
** Also
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init
re-opening this for cloud-init as the change in cloud-init actually
regressed the behavior.
** Changed in: cloud-init (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: cloud-init (Ubuntu Xenial)
Status: Fix Released => Confirmed
** Changed in: cloud-init
Status:
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Also affects: cloud-init (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Wily)
Importance: Undecided
Status: New
** No longer affects: cloud-init (Ubuntu Vivid)
** No longer affects: cloud-init (Ubuntu Wily)
--
You received this bug
buntu Xenial)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: cloud-init (Ubuntu Xenial)
Assignee: (unassigned) => Scott Moser (smoser)
** Changed in: cloud-init (Ubuntu Yakkety)
Importance: Undecid
ety)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu Yakkety)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu Xenial)
Assignee: (unassigned) => Scott Moser (s
buntu Xenial)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu Yakkety)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu Xenial)
Assignee: (unassigned) => Scott Moser (smoser)
--
You received this bug notification because you are a member of Ya
buntu Xenial)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu Yakkety)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: cloud-init (Ubuntu Xenial)
Assignee: (unassigned) => Scott
** Also affects: maas
Importance: Undecided
Status: New
--
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/1646571
Title:
apt failures non fatal, but cloud the log
Status in
Public bug reported:
output of cloud-init-local.service can get lost in systemd.
The result is that there is no output in /var/log/cloud-init.log from
cloud-init-local.service.
There is some information in
https://code.launchpad.net/~harlowja/cloud-init/+git/cloud-init/+merge/301729
about how
This is fixed in commit
9e904bbc3336b96475bfd00fb3bf1262ae4de49f
https://git.launchpad.net/cloud-init/commit/?id=9e904bbc3336b96475bfd00fb3bf1262ae4de49f
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: cloud-init (Ubuntu Xenial)
Status: New =>
Hi,
I've subscribed Xiang to this as he recently pinged me on a different string
that may appear as a network device. My response to him was:
| This non-sense really needs to stop.
| We need to fix openstack to stop sending arbitrary "types" of network
| devices that mean nothing to the guest.
** Changed in: cloud-init (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: cloud-init (Ubuntu Xenial)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
Public bug reported:
cloud-init-local.service writes to /var/lib/cloud/ and is more correct
to have that listed here than /var/lib.
** Affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a
fixed in upstream commit 02f6c4bb8cef17b3fe04ef4dc1ef199e20aeb4d9
** Description changed:
+ === Begin SRU Template ===
+ [Impact]
+ Support for lxd configuration of networking does not work with lxd 2.3+ as
+ the current path for configuration in cloud-init uses debconf but newer
+ lxd does
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Xenial)
Importance: Undecided => Medium
--
You received this bug notification because you are a
** Also affects: dbus (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: dbus (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Also affects: cloud-init (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Xenial)
Importance:
The initial fix is easy, but bug 1621615 changes sneaked in without a
unit test.
I'd really like a unit test of read_kernel_cmdline_config to accompany this
change.
Also, a change to 'DHCP6_CONTENT_1' in tests/unittests/test_net.py to contain
what we're currently expecting.
diff --git
Public bug reported:
In changes made under bug 1621615 (specifically a1cdebdea), we now
expect that there may be a 'ip6=' argument on the kernel command line.
The changes made did not test the case where there is 'ip6=' and no
'ip='.
The code currently will return with no network configuration
** Also affects: cloud-init (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Zesty)
Importance: Medium
Status: Fix Released
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: cloud-init
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
--
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/1635350
Title:
unit tests fail as non-root on maas
Public bug reported:
As discussed at [1], the addition of AliYun datasource did not enable it by
default.
This is because it has no definitive check before polling the network for data.
Lawrence suggested he has a solution for this.
[1] https://code.launchpad.net/~smoser/cloud-init/+git/cloud-
*** This bug is a duplicate of bug 1575055 ***
https://bugs.launchpad.net/bugs/1575055
** This bug has been marked a duplicate of bug 1575055
check_instance_id() error on reboots when using config-drive
--
You received this bug notification because you are a member of Yahoo!
Engineering
** Changed in: cloud-init (Ubuntu)
Status: Fix Released => In Progress
--
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/1629797
Title:
resolve service in nsswitch.conf adds 25
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix Committed
** Changed in: cloud-init
Importance: Undecided => High
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
*** This bug is a duplicate of bug 1629797 ***
https://bugs.launchpad.net/bugs/1629797
I'm 95% sure that this is a dupe of bug 1629797
I'm going to mark it as such, and if we find out otherwise un-dupe it.
** This bug has been marked a duplicate of bug 1629797
resolve service in
** Description changed:
Given this command line:
BOOT_IMAGE=ubuntu/amd64/hwe-y/yakkety/daily/boot-kernel nomodeset
iscsi_target_name=iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-amd64-hwe-y-yakkety-daily
iscsi_target_ip=2001:67c:1562:8010::2:1 iscsi_target_port=3260
iscsi_initiator=kearns
** No longer affects: cloud-init
--
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/1618572
Title:
apt-key add fails in overlayfs
Status in linux package in Ubuntu:
Confirmed
Status
** Merge proposal linked:
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/306345
** Also affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
** No longer affects: cloud-init
--
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/1623570
Title:
Azure: cannot start walinux agent (Transaction order is cyclic.)
Status in cloud-init
So we have a couple of options here:
a.) use '__builtin__' mode in cloud-init for the walinux agent functionality.
this in theory should work, but we have not largely tested it. Basically
this path has cloud-init doing the metadata service exchange itself rather than
relying on walinux-agent to
Public bug reported:
When bringing up the Azure datasource in cloud-init.service, cloud-init
tries 'service start walinuxagent'.
That previously worked fine, and the agent would start and then would
produce the certificate files that cloud-init needed (for ssh keys and
things).
I found this
501 - 600 of 930 matches
Mail list logo
