ping: please help to relook this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766538
Title:
network customization with cloud-init does not work on Ubuntu18.04
Beta2 Server
To manage
Thanks a lot Chad, we will look at this and back to you later
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766538
Title:
network customization with cloud-init does not work on Ubuntu18.04
Beta2
Public bug reported:
The dns servers and search domain was NOT written to /etc/netplan/50
-cloud-init.yaml when customize a Ubuntu18.04 Server with DHCP IP and
DNS servers/search domain.
>From cloud-init.log, I can see it applying network configuration with dns
>servers and search domain:
50-cloud-init.yaml file
** Attachment added: "50-cloud-init.yaml"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1776452/+attachment/5151696/+files/50-cloud-init.yaml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
cloud-init logs
** Attachment added: "cloud-init.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1776452/+attachment/5151695/+files/cloud-init.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We have found the root cause, need update code at
https://git.launchpad.net/cloud-
init/tree/cloudinit/sources/helpers/vmware/imc/config_nic.py, I will
submit a fix on this.
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Pengpeng Sun (pengpengs)
--
You received this
Hi Chad,
Thanks for your investigation. You are right, I tried many times on that
Beta2 build(also did apt install nettools to use ifconfig), for Desktop,
I observes networking configuration is not handled by netplan, while
eni(/etc/network/interfaces) takes effect.
Today I did the following
the cloud-init log
** Attachment added: "cloud-init.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538/+attachment/5132723/+files/cloud-init.tar.gz
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you
Attached the cust.cfg, Thanks Christian.
** Attachment added: "cust.cfg"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1776452/+attachment/5154229/+files/cust.cfg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~pengpengs/cloud-init/+git/cloud-init/+merge/353303
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766538
Title:
network customization with
Yes, I saw 'No ds found [mode=search, notfound=disabled]. Disabled
cloud-init' from /run/cloud-init/ds-identify.log, will attach it.
The Ubuntu Server is the server build I downloaded from below link and
installed on a VMware VM.
Server: http://cdimage.ubuntu.com/ubuntu-server/daily/current/
I
** Attachment added: "ds-identify.log"
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1760776/+attachment/5101168/+files/ds-identify.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
list -Rl /etc/cloud
.:
cloud.cfg
cloud.cfg.d
templates
./cloud.cfg.d:
05_logging.cfg
90_dpkg.cfg
README
./templates:
chef_client.rb.tmpl
hosts.debian.tmpl
hosts.freebsd.tmpl
hosts.redhat.tmpl
hosts.suse.tmpl
ntp.conf.debian.tmpl
ntp.conf.fedora.tmpl
ntp.conf.opensuse.tmpl
ntp.conf.rhel.tmpl
** Attachment removed: "ds-identify.log"
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1760776/+attachment/5101168/+files/ds-identify.log
** Attachment added: "ds-identify.log"
Public bug reported:
After installed Ubuntu18.04 Beta2 Server on a VMWare VM, cloud-init service
running after power-on.
‘DataSourceNoCloud’ was detected, I checked /var/run/cloud-init directory, a
result.json file shows “DataSourceNoCloud
[seed=/var/lib/cloud/seed/nocloud-net] [dsmode=net]”.
I compared Desktop with Server after customization.
Ubuntu 18.04 Desktop:
>ls /etc/network
if-post-down.d if-pre-up.dif-up.dinterfaces
interfaces.before_vmware_customizationinterfaces.d
>cat /etc/network/interfaces
# DO NOT EDIT THIS FILE BY HAND -- AUTOMATICALLY GENERATED BY
Public bug reported:
This issue does NOT exist on Ubuntu18.04 Beta2 Desktop, it only
reproduces on Ubuntu18.04 Beta2 Server
Ubuntu18.04 Beta2 Server is installed on a VMware VM.
VMware customization Config File was copied to /var/run/vmware-imc/cust.cfg
correctly.
Check cloud-init.log, it
attached cloud-init.log
** Attachment added: "cloud-init.log"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538/+attachment/5126433/+files/cloud-init.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "cloud-init.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1760776/+attachment/5100599/+files/cloud-init.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
reproduced the same issue on Apr.1 build
1. tried reboot, cloud-init service was still inactive.
2. I checked /var/log/cloud-init-output.log, it says 'netstat' cmd not found.
After install net-tools, and run "service cloud-init start", still can not
active it. /var/log/cloud-init-output.log says
@Scott, thanks a lot for your investigation.
The /var/lib/cloud/instance is a directory in Ubuntu18.04.1 and Ubuntu18.10
daily build, while it is a symbolic link in Ubuntu18.04 GA, could this be a
regression bug for Ubuntu release? Or for some reason, it was changed from
Ubuntu18.04.1. I will
Public bug reported:
Hi there,
Found the /var/lib/cloud/instance became to a directory from
Ubuntu18.04.1 and Ubuntu18.10, it was a symbolic link on Ubuntu18.04 GA.
Want to know the reason of this change, since it makes cloud-init fails
on Ubuntu18.04.1 and Ubuntu18.10, see details at
Filed a LP bug to Ubuntu https://bugs.launchpad.net/ubuntu/+source
/compiz-plugins-main/+bug/1798540
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796875
Title:
cloud-init and cloud-init-local
@Scott, I found the dependency error was caused by a workaround of us,
it might not the root cause of failure on Ubuntu18.04.1 and Ubuntu18.10
After remove the workaround, I got the cloud-init logs again, please
check the new attachment cloud-init-18.04.1-FAIL.tar.gz, there are some
Tracebacks in
Confirmed on Ubuntu18.10 GA build, the 'var/lib/cloud/instance' is back
to a symbolic link.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796875
Title:
cloud-init and cloud-init-local services
Confirmed on Ubuntu18.10 GA build, the 'var/lib/cloud/instance' is back
to a symbolic link.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798540
Title:
Question on '/var/lib/cloud/instance'
To
VMTools version from UBUNTU18.10 daily build FAIL test
$ vmtoolsd -v
VMware Tools daemon, version 10.3.0.5330 (build-8931395)
VMTools version from UBUNTU18.04.1 FAIL test
$ vmtoolsd -v
VMware Tools daemon, version 10.2.0.1608 (build-7253323)
VMTools version from UBUNTU18.04GA PASS test
$
Public bug reported:
Observed the cloud-init.service and cloud-init-local service boot
sequence does NOT obey the dependency setting in these .service files.
According to the dependency [Before/After] settings on these service
files, the correct sequence should be cloud-init.service After cloud-
Link with VMWare bug: 2212195
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796875
Title:
cloud-init and cloud-init-local services boot sequence does not obey
dependency settings
To manage
@Scott Thanks for your input, please find the cloud-init logs for both
PASS and FAIL test.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796875
Title:
cloud-init and cloud-init-local services boot
Attach cloud-init logs from UBUNTU18.04GA PASS test
** Attachment added: "cloud-init_PASS.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1796875/+attachment/5199323/+files/cloud-init_PASS.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Attach cloud-init logs from UBUNTU18.10 daily build FAIL test
** Attachment added: "cloud-init_FAIL.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1796875/+attachment/5199324/+files/cloud-init_FAIL.tar.gz
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => New
Public bug reported:
Hi there,
There is a fix of cloud-init merged to main 5 days ago, see it here:
https://git.launchpad.net/cloud-init/commit/?id=9c35f9762028b8bf15cdcd6b42c0fafc233ddda3
It fixed an issue of customizing a VMware VM, I'm wondering if you could
cherry pick this fix to the
As to Joshua's question:
Customization of hostname is using "hostnamectl set-hostname theNewHostName"
which requires 'dbus.service' is running. We found the dbus.service might not
be running when perl/cloud-init executes the hostnamectl command on Ubuntu18.04
(Open-vm-tools v10.2.0).
As the
Public bug reported:
Hi there,
Found on version 10.3.5, the cloud-init.service dependency is NOT in
open-vm-tools.service.
Want to check with you if it’s removed on purpose? and what’s the reason of
removing it.
The cloud-init.service dependency was adding “Before=cloud-init-local.service”
$vmtoolsd -v
VMware Tools daemon, version 10.3.5.6873 (build-9998599)
$cat /lib/systemd/system/open-vm-tools.service
[Unit]
Description=Service for virtual machines hosted on VMware
Documentation=http://github.com/vmware/open-vm-tools
ConditionVirtualization=vmware
Requires=vgauth.service
change to open-vm-tools package
** Package changed: linux (Ubuntu) => open-vm-tools (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803939
Title:
cloud-init.service dependency is missing
Hi Christian,
Thanks for your checking and quick response, and you are right. I
double-checked my Ubuntu16.04 VM, it was configured with a local source
on open-vm-tools indeed. After remove the local source and re-install
open-vm-tools, it's 10.2.0 and has the dependency.
Thanks,
Pengpeng
--
Hi Joshua,
Sorry for the late response.
Yes, adding "After=dbus.service" to open-vm-tools.service file is the
workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793715
Title:
VMWare
Hi Matti,
With "disable_vmware_customization: false" entry added, its enabling
Guest OS Customization with Cloud-Init. Was the bionic installed on a
VMware VM and did Guest OS Customization?
Thanks,
Pengpeng
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Yes, I just tried 'After=dbus.socket' on my Ubuntu18.10, it works.
We need do some verifications and then update our KB if it works on the other
Ubuntu versions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the suggestion!
Actually we are working on using (A) only and by default. Before that happens,
(B) needs be kept.
Instead of splitting vmtoolsd/open-vm-tools services, we might fix this issue
in scripts, make sure when 'hostnamectl' cmd executes, the dbus.service is
running.
--
You
Thanks a lot for the info, Christian.
Let me answer your questions firstly:
- are your scripts triggered by cloud init
NO.
- if so in which config module/phase as I'm sure I have done cloud-init driven
hostname changed?
- OR are your scripts triggered by open-vm-tools directly?
VMware Guest OS
Hi Christian,
According to #15, please do NOT make "After=dbus.socket" as a part of
open-vm-tools package.
While we will update VMware KBs to change from "After=dbus.service" to
"After=dbus.socket" for (B).
A) For Set cloud-init as the customization engine:
B) For Set perl script as the
Verified VMware post customization script worked fine with cloud-init
19.2-24 on Ubuntu16.04.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833192
Title:
VMware: post custom script isn't run
Hi team,
Please let us know if this is as-designed or not, Ubuntu desktop version
was using /etc/network/interfaces to configure static IP address and
etc...
Best regards,
Pengpeng
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Maher AlAsfar (malasfar)
What's cloud-init version on the Ubuntu16.04? The version need be greater or
equal to 18.2 to make customization work.
What's open-vm-tools version on the Ubuntu16.04?
If you customize Ubuntu with cloud-init, please do NOT add any
"After=dbus.x" to
@Dan, could you please confirm if your fix will be patched on
Ubuntu19.10? If yes, when it will happen?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850775
Title:
DNS info is not loaded by
Thanks Till, which systemd service's dependency got changed?
I compared /lib/systemd/system/systemd-resolved.conf between 18.04 and
19.10, they are same. There is "After=systemd-sysusers.service systemd-
networkd.service".
I do NOT know when and who triggers /etc/dhcp/dhclient-enter-
@Dan, The issue is resolved by your fix.
Instead of only changing /etc/dhcp/dhclient-enter-hooks.d/resolved
script, I added your repository "ppa:ddstreet/systemd" and
updated/upgraded systemd, then the issue was NOT reproducing.
--
You received this bug notification because you are a member of
Thanks @Dan, I applied the patch
https://launchpadlibrarian.net/448207988/resolved.patch to my VM, but the issue
is still reproducing.
The md5sum line is before creating "$statedir/isc-dhcp-v4-$interface.conf",
while I can see the isc-dhcp-v4-$interface.conf file is created on my VM.
I think
Hi Joshua,
Thanks for your reply.
Could you please confirm if all Ubuntu types uses Netplan from 19.10, I
noticed from 17.10 to 19.04, Desktop type has ifupdown, Server and Live
Server are using Netplan.
Thanks,
Pengpeng
** Changed in: network-manager (Ubuntu)
Status: Invalid => New
--
Re-new this bug for requesting above confirmation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844763
Title:
file /etc/network/interfaces is missing in eoan-desktop-amd64.iso
To manage
Thanks for the confirmation!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844763
Title:
file /etc/network/interfaces is missing in eoan-desktop-amd64.iso
To manage notifications about this bug
Public bug reported:
Hi Team,
Could you please help to confirm if this is an issue on Ubuntu19.10
Desktop?
1. Update /etc/dhcp/dhclient.conf file to include below 2 new lines.
supersede domain-name "vmware.com";
supersede domain-name-servers 10.117.0.1;
2. Reboot
3. check DNS info by
@Balint, thanks a lot for the information.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850775
Title:
DNS info is not loaded by dhclient
To manage notifications about this bug go to:
Sure, list the use case step by step as below:
1. Customer create a Ubuntu VM on vSphere
2. Customer attach Live Server installer ISO to VM's CD-ROM
3. Customer power-on the VM and go through installation wizard to install
Ubuntu Live Server (subiquity works here)
4. Customer want to create more
Hi,
When does subiquity write netplan configuration? At installation? Will
it run again on an installed system? If no, can we remove subiquity-
disable-cloudinit-networking.cfg after installation done?
The problem is cloud-init can never write netplan configuration with
Thanks Richard for the updates.
As far as I know, Ubuntu 20.04 has been GAed at Apr.24, 2020. So the change is
not included in GA version(please correct me if I'm wrong), could you please
let us know when the change will probably be shipped to Ubuntu 20.04 Live
server.
--
You received this
Hi Dan, Paride,
Any updates on this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871975
Title:
network configuration is disabled by default in cloud-init for ubuntu
live server beta
To
Thanks for the explanation.
On VMware vSphere platform, Customer can install Ubuntu Live Server
system through ISO image on a Virtual Machine, then the Live Server
Ubuntu VM will contain subiquity-disable-cloudinit-networking.cfg. This
leads to cloud-init can NOT manage network on this VM by
I mean the subiquity-disable-cloudinit-networking.cfg is deleted
automatically, not by Customer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871975
Title:
network configuration is disabled by
To include VMTools version info to ova template, write
'ddb.toolsVersion=2147483647' to the VMDK file before create the
template.
VDDK SDK VixDiskLib_WriteMetadata API can be used to write "ddb.toolsVersion"
metadata -
Verified no such issue on 20.04 cloud image (OVA).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871975
Title:
network configuration is disabled by default in cloud-init for ubuntu
live server
Thanks Robert for the quick confirmation, so I assume that the bionic,
focal, and groovy images will be updated to include VMTools version
info. We will let customer to retry once the new images are available.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
emm...I see the new name servers are appended to the current name
servers list. https://github.com/canonical/cloud-
init/blob/master/cloudinit/distros/parsers/resolv_conf.py#L79
So the new name servers are always in the tail, if there are already 3
current name servers exist, then any new name
Public bug reported:
Hi team,
This might be a question which has been asked by someone else, but I did
NOT find related bugs by searching.
See https://github.com/canonical/cloud-
init/blob/master/cloudinit/distros/parsers/resolv_conf.py#L83, new name
server(s) will be ignored if 3 name servers
Hi team,
Any updates on this, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871975
Title:
network configuration is disabled by default in cloud-init for ubuntu
live server beta
To
Hi team,
Could you please share some info on this, when and how this issue is
going to be fixed? Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871975
Title:
network configuration is
Hello Lukáš,
You mentioned "initiate it with cloud-init (userdata + metadata)", may I
know how did you initiate userdata and metadata? also you mentioned
guestinfo.userdata and guestinfo.metadata, did you use the way described
here: https://github.com/vmware/cloud-init-vmware-guestinfo ?
Another
terraform is new to me, but if it's using https://github.com/vmware
/cloud-init-vmware-guestinfo, it won't work unless the installation has
been done in VM. See https://github.com/vmware/cloud-init-vmware-
guestinfo/blob/master/README.md
So you have to power-on the VM firstly, have you tried to
Understood. I think you are using vSphere7, guest-customization does support
netplan from vSphere 6.7U3g, so network-config can be set.
Guest-customization has 2 engines: one is perl scripts, the other is
cloud-init. Unfortunately, neither of them can work with cloud-init to set
userdata
Yes, exactly. I wonder how the network-config file is applied in your
current workflow.
Yes, guest customization can be turned off if VM's open-vm-tools version is
11.1.0 or above, see KB https://kb.vmware.com/s/article/78903.
I just checked open-vm-tools version in
I think the network disconnection is a result of guest-customization task,
although the vm side customization has been disabled according to the tools
configuration.
You can try connect the vm network right before power-on VM by gosv, then the
vm network can be available automatically.
--
You
Yes, let me understand your case more clearly, I thought cloud-init is
only needed at step1.
Attach an iso to set up user, ssk-key, is this a one time job or you
want it happen for all cloned new VMs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Florian
The issue is a bit of different with the one reported at the beginning
of this bug. Let me explain the details and provide a workaround for
you.
The key is when dbus.service is running at booting.
With ova, cloud-init will be enabled and run, when it's running, it
blocks dbus, see
This issue doesn't reproduce on 22.04 Live server image, its
'/usr/lib/systemd/system/systemd-networkd.socket' is same with 22.04
Desktop image, so looks like shutdown.target in systemd-networkd.socket
is not the root cause. I think the systemd dependence is quite different
between Desktop and
VMware internal bug for this is 2928681.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962843
Title:
Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to
adding
Appreciate your help, Christian. I'm trying to find a way to reproduce
this issue without vSphere, will post it here once get it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962843
Title:
Guest
Yes, same here. I got the same good news with beta image.
Christian, thanks for your help again. I think we can close this bug for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962843
Title:
> If you wish to undertake "Guest Customization" reliably then you must
> interact correctly with the interfaces provided by the guest OS. These will
> of course change from release to release of the guest OS, so in general it is
> always necessary to adapt interactions as required by new guest
> If you wish to undertake "Guest Customization" reliably then you must
> interact correctly with the interfaces provided by the guest OS. These will
> of course change from release to release of the guest OS, so in general it is
> always necessary to adapt interactions as required by new guest
Thanks Robie for the information, this is exactly the VMware guest
customization updating in the next vSphere 8.0 update release which is
"Using timedatectl command to set hardware clock since Ubuntu 23.10".
However as Ubuntu 24.04 is LTS, it's widely supported on vSphere 8.x
line, without
Hi Nick,
Thanks for the info! So for Desktop, it's always NetworkManager as Netplan
renderer; and for Server, it's systemd-networkd.
Another question, what if there is no renderer set in Netplan Yaml file, can
Netplan load network configuration correctly?
--
You received this bug notification
For example:
network:
version: 2
ethernets:
enp3s0:
dhcp4: true
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066700
Title:
systemd-networkd is inactive by default since ubuntu
** Package changed: network-manager (Ubuntu) => netplan.io (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066700
Title:
systemd-networkd is inactive by default since ubuntu 23.10?
To
86 matches
Mail list logo
