Public bug reported:
Depending on distribution the default number of tasks (threads) maybe
unexpectedly low or it may be the default systemd setting (512). Given
that more and more installers and other code are taking advantage of
multiprocessing capabilities it is becoming more likely that
Public bug reported:
During install template expansion for SUSE distributions fails for
config and systemd templates.
** Affects: cloud-init
Importance: Undecided
Assignee: Robert Schweikert (rjschwei)
Status: New
** Changed in: cloud-init
Assignee: (unassigned
Public bug reported:
On older SUSE distributions (SLES 11) the init script integration is
broken.
** Affects: cloud-init
Importance: Undecided
Assignee: Robert Schweikert (rjschwei)
Status: New
** Changed in: cloud-init
Assignee: (unassigned) => Robert Schweik
Public bug reported:
It is not possible to add zypper repos via simple yaml config
** Affects: cloud-init
Importance: Undecided
Assignee: Robert Schweikert (rjschwei)
Status: New
** Changed in: cloud-init
Assignee: (unassigned) => Robert Schweikert (rjschwei)
--
, but sles is not
listed as a supported distribution.
** Affects: cloud-init
Importance: Undecided
Assignee: Robert Schweikert (rjschwei)
Status: New
** Changed in: cloud-init
Assignee: (unassigned) => Robert Schweikert (rjschwei)
--
You received this bug notification because
-init
Importance: Undecided
Assignee: Robert Schweikert (rjschwei)
Status: New
** Changed in: cloud-init
Assignee: (unassigned) => Robert Schweikert (rjschwei)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscri
Public bug reported:
Older ifconig, route, netstat, and arp tools are being deprecated on
Linux distributions. cloud-init should in all cases support the newer
iproute2 tools.
ifconfig used in:
cloudinit/sources/DataSourceAzure.py
cloudinit/netinfo.py
tools/mock-meta.py
netstat used
Schweikert (rjschwei)
Status: New
** Changed in: cloud-init
Assignee: (unassigned) => Robert Schweikert (rjschwei)
--
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/1732
Public bug reported:
At present cloud-init supports configuration for ntp, and timesyncd.
chrony is yet another way to configure time keeping on a Linux system
and should be supported.
Tests on AWS have shown that chrony is more reliable with the EC2
timesource than ntp.
** Affects: cloud-init
Public bug reported:
openSUSE and SLES use wicked for network handling and not dhclient. The
cloud-init-local code assumes dhclient and thus fails:
# systemctl status cloud-init-local.service
● cloud-init-local.service - Initial cloud-init job (pre-networking)
Loaded: loaded
Public bug reported:
On openSUSE and SUSE Linux Enterprise server the hostname is not written
to /etc/hosts when managed_etc_hosts is enabled.
** Affects: cloud-init
Importance: Undecided
Assignee: Robert Schweikert (rjschwei)
Status: New
** Changed in: cloud-init
for
template hosts.suse
** Affects: cloud-init
Importance: Undecided
Assignee: Robert Schweikert (rjschwei)
Status: New
** Changed in: cloud-init
Assignee: (unassigned) => Robert Schweikert (rjschwei)
--
You received this bug notification because you are a member of Ya
_read_modules
for item in cfg_mods:
TypeError: 'NoneType' object is not iterable
Rather than complaining cloud-init should handle this gracefully and
just skip the stage and do nothing.
** Affects: cloud-init
Importance: Undecided
Assignee: Robert Schweikert (rjschwei)
St
Public bug reported:
Upstream Python has deprecated platform.linux_distribution()[1] and the
implementation is being removed in 3.7. This has an effect on template
rendering during install and possibly other places in the code during
runtime.
Options are to use an external module [2] or
Public bug reported:
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.
Schweikert (rjschwei)
Status: New
** Changed in: cloud-init
Assignee: (unassigned) => Robert Schweikert (rjschwei)
** Merge proposal linked:
https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/357752
--
You received this bug notification because you are a mem
or for ONBOOT=no as
STARTMODE=manual.
** Affects: cloud-init
Importance: Undecided
Assignee: Robert Schweikert (rjschwei)
Status: New
** Changed in: cloud-init
Assignee: (unassigned) => Robert Schweikert (rjschwei)
--
You received this bug notification because you are a mem
Public bug reported:
Looks like we need to figure out how to do distribution specific
handling in sysconfig.py for the file content anyway.
For a static network configuration on openSUSE and SLES BOTOPROTO must
be set to "static", but based on the comment in sysconfig.py
# grep
Public bug reported:
Persistsing OpenStack metadata may fail.
OpenStack has an entry named "random_seed" in the metadata [1]. This
entry is treaded specially in the openstack.py helper when the metadat
is read [2]. The attempt to decode the read data my result in a string
that is not utf-8
Public bug reported:
On SUSE distros the routes need to be written to ifroute-* files.
At present the sysconfig renderer does not write the default routes to
ifroute-* files, rather the default rout information is set in ifcfg-*.
However the values DEFROUTE=yes and IPV6_DEFAULTGW have no meaning
Public bug reported:
If the user does not supply any dns resolution information in the
configuartion cloud-init should not write a resolv.conf file that just
contains the header. Putting a basically empty resolv.conf file in place
prevents other tools to write the resolv.conf file as it is
Public bug reported:
ds-identify is executed from a systemd generator [1]. Based on my
understanding of the intention of both this creates a non resolvable
timing conflict.
Generators run very early in the boot process.
The cloud-init generator runs ds-identify which in turn runs "blkid" to
psdcw1kdi/etc/hosts (quiet=False)
tests.unittests.test_handler.test_handler_apt_configure_sources_list_v3: DEBUG:
got security mirror: shit
** Affects: cloud-init
Importance: Undecided
Assignee: Robert Schweikert (rjschwei)
Status: New
** Changed in: cloud-init
Assignee: (unassigned) => Robert Schweikert (rjschwei)
--
Schweikert (rjschwei)
Status: New
** Changed in: cloud-init
Assignee: (unassigned) => Robert Schweikert (rjschwei)
--
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/1793193
Ti
Public bug reported:
On a VM with many interfaces it is possible that udev is slow. This may
lead to the situation that 70-persistent-net.rules is being written to
by cloud-init while also being written to by the net rules generator (75
-persistent-net-generator.rules). This may lead to
Public bug reported:
The sysconfig renderer uses
IPV6ADDR
IPV6ADDR_SECONDARIES
but this is not part of the set of names understood on SUSE distros it
should be
IPADDR6
IPADDR6_?
** Affects: cloud-init
Importance: Undecided
Assignee: Robert Schweikert (rjschwei)
Status: New
Public bug reported:
In OpenStack it is possible to configure a network setup such that the
metadata server is accessible via a "secondary" NIC, for example eth1.
In such a setup cloud-init fails to locate the proper NIC to access the
metadata server.
** Affects: cloud-init
Importance:
Public bug reported:
User changes applied by cloud-init to /etc/resolv.conf may get
clobbered.
The netconfig tool manages a symlink from /etc/resolv.conf to
/var/run/netconfig/resolv.conf. When cloud-init writes dns information
it opens the file, i.e. in this case /var/run/netconfig/resolv.conf
Public bug reported:
Not sure why this is showing up now in a number of instances as the code
has been there for quite some time. sysconfig.py contains
def available_sysconfig(target=None):
expected = ['ifup', 'ifdown']
search = ['/sbin', '/usr/sbin']
for p in expected:
if
Public bug reported:
The Azure data source assumes that the network is set up by dhcpclient.
During cloud-init initialization the following traceback is generated:
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/cloudinit/sources/DataSourceAzure.py",
line 668, in
2083, in subp
cmd=args)
ProcessExecutionError: Unexpected error while running command.
This is a regression from 19.1 on SUSE where exiting routes were simply
skipped.
** Affects: cloud-init
Importance: Undecided
Assignee: Robert Schweikert (rjschwei)
Status: New
** Changed in: cloud-i
6 and IPv4 configurations are defined, or if only one
protocol is used and the IP is static
** Affects: cloud-init
Importance: Undecided
Assignee: Robert Schweikert (rjschwei)
Status: New
** Changed in: cloud-init
Assignee: (unassigned) => Robert Schweikert (rjsch
Public bug reported:
When creating an AMI from a running instance without cleaning the cloud-
init cache an instance from the new AMI is no properly identified as a
new instance and none of the PER_INSTANCE tasks will be executed.
The problem is that the Ec2 data source will return the cached
Public bug reported:
The Azure data source assumes that all Linux distros use dhclient.
Location of a lease file is hard coded to
"""
LEASE_FILE = '/var/lib/dhcp/dhclient.eth0.leases'
"""
and if the file is not found the data source reports errors:
"""
Failed to read
34 matches
Mail list logo
