[Bug 2039206] Re: open-vm-tools "hwclock" needed for VM guest customization not available
We've updated to use "timedatectl" but "hwclock" to set hardware clock for Ubuntu 24.04 and later releases. The fix is included in the recent releases of vCenter: VMware vCenter Server 8.0U3 & 8.0U3a VMware vCenter Server 7.0 Update 3q No image change needed after upgrading vCenter server to the above releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2039206 Title: open-vm-tools "hwclock" needed for VM guest customization not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/2039206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039206] Re: open-vm-tools "hwclock" needed for VM guest customization not available
We've updated to use "timedatectl" but "hwclock" to set hardware clock for Ubuntu 24.04 and later releases. The fix is included in the recent releases of vCenter: VMware vCenter Server 8.0U3 & 8.0U3a VMware vCenter Server 7.0 Update 3q Need image change needed after upgrading vCenter server to the above releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2039206 Title: open-vm-tools "hwclock" needed for VM guest customization not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/2039206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066700] Re: systemd-networkd is inactive by default since ubuntu 23.10?
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 23.10? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2066700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066700] Re: systemd-networkd is inactive by default since ubuntu 23.10?
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 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2066700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066700] Re: systemd-networkd is inactive by default since ubuntu 23.10?
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2066700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039206] Re: open-vm-tools "hwclock" needed for VM guest customization not available
> 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 OS releases. > Therefore your customers should not expect any new guest OS release to > function correctly with your Guest Customization feature prior to receiving > such an update from you. > It sounds like this problem will go away as soon as you release your fixed > vSphere update? Yes，this is reason we always test "Guest Customization" on new guest os daily/beta build before it's released to catch such failure due to guest os change. If the fix is on vSphere side, customer will have to wait for the next vSphere release which contains the fix and must upgrade to it to get the fix. While if guest side(at least in guest os GA build) can fix it, customer will not encounter the failure at all. Certainly, where the fix goes to is case by case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2039206 Title: open-vm-tools "hwclock" needed for VM guest customization not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/2039206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039206] Re: open-vm-tools "hwclock" needed for VM guest customization not available
> 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 OS releases. > Therefore your customers should not expect any new guest OS release to > function correctly with your Guest Customization feature prior to receiving > such an update from you. > It sounds like this problem will go away as soon as you release your fixed > vSphere update? When "Guest Customization" fails due to a guest os change, we will work with guest os team to see how to resolve it. The fix could be either on vSphere side or on guest os side. Such failure can be caught before guest os release since we always test new guest os daily/beta build before it's released. If the fix is on vSphere side, customer will have to wait for the next vSphere release which contains the fix and upgrade to it. If the fix is on guest side(at least in guest os GA build), then customer need NOT upgrade vSphere to get the fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2039206 Title: open-vm-tools "hwclock" needed for VM guest customization not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/2039206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039206] Re: open-vm-tools "hwclock" needed for VM guest customization not available
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 hwclock command, customers who are using the current vSphere 8.0 - 8.0U2 releases will encounter this issue. Understood that timedatctl command shall be used with systemd, still if adding hwclock command back has no conflict, it will be great helpful for customers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2039206 Title: open-vm-tools "hwclock" needed for VM guest customization not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/2039206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962843] Re: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket
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: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd- networkd.socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962843] Re: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket
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 OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd- networkd.socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962843] Re: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket
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 'shutdown.target' in file /usr/lib/systemd/system/systemd- networkd.socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962843] Re: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket
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 Server images, please systemd experts look into this. By running below command on Ubuntu 21.04 Desktop, Ubuntu 22.04 Desktop and Ubuntu 22.04 Server VMs, got some .svg files, attached them in svg_files.zip to this bug for your reference. 1. systemd-analyze plot > plot2104_desktop.svg 2. systemd-analyze plot > plot2204_desktop.svg 3. systemd-analyze plot > plot2204_server.svg 4. systemd-analyze dot 'systemd-networkd.service' | dot -Tsvg > dot2104_desktop.svg 5. systemd-analyze dot 'systemd-networkd.service' | dot -Tsvg > dot2204_desktop.svg 6. systemd-analyze dot 'systemd-networkd.service' | dot -Tsvg > dot2204_server.svg According to the plot output, systemd-networkd starts late only on Ubuntu 22.04 Desktop VM, this leads to customization command 'netplan apply' fail. ** Attachment added: "svg files" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962843/+attachment/5566877/+files/svg_files.zip -- 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 'shutdown.target' in file /usr/lib/systemd/system/systemd- networkd.socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
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 modify OVF file extracted from OVA file, it contains a password property which is "Default User's password", the default user is ubuntu. Once you get into the VM, you can install cloud-init-vmware-guestinfo and then save the VM as source VM. -- 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 Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
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 question: did you trigger guest customization on the VM? if not, you needn't disable guest customization from the vmware-toolbox-cmd. There should be a default user 'ubuntu' which is configured in /etc/cloud/cloud.cfg, I think you will be asked to set password for this user when you deploy focal-server-cloudimg-amd64.ova on ESXi(I'm not sure what free version means, were you using vCenter server?) At last, we need cloud-init logs to see what really happened in VM, command 'sudo cloud-init collect-logs' should help to collect them. -- 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 Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
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 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 Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
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 https://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64.ova, it's 11.0.5. So you have to upgrade to 11.1.0+ to disable guest-customization. -- 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 Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
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 guest-config at the same boot. For perl script based guest-customization, it has dependency on dbus, due to the reason in comment #28, it fails with cloud-init running. For cloud-init based guest-customization, it uses the same cloud-init datasource OVF with ISO file, but different seed. Cloud-init can only apply either guest-customization or ISO userdata guest-config. Good news is if you are using vSphere7, you can use customization post- customization script to finish your workflow, need below steps: 1. Power-on VM which deploy from ova. 2. Disable cloud-init by running the command “sudo touch /etc/cloud/cloud-init.disabled” 3. Enable customization script by running the command "vmware-toolbox-cmd config set deployPkg enable-custom-scripts true" 3. Power-off VM and convert it to template. 4. Create a new guest-customization specification which includes network-configs and customization script, the script looks like: #!/bin/sh if [ x$1 == x"postcustomization" ]; then rm /etc/cloud/cloud-init.disabled systemctl reboot fi 5. Generate the cloud-init configurations for guest-config dynamically and create a cloud-init.iso file 6. The rest steps you did Related document and KB: a. Create a Customization Specification for Linux https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-9A5093A5-C54F-4502-941B-3F9C0F573A39.html b. Setting the customization script for virtual machines in vSphere 7.0 https://kb.vmware.com/s/article/74880 -- 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 Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793715 Title: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
@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 reason at comment #8. So dbus is running too late to make customization work even with the fix in 6.7U3. In your case, I suggest you create a new template but turn ova into template directly. Steps: 1. Power-on VM which deploy from ova. 2. Disable cloud-init by by running the command “sudo touch /etc/cloud/cloud-init.disabled” 3. Power-off VM and convert it to template. -- 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 Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893898] Re: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova
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 is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893898 Title: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1893898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893898] Re: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova
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 - https://code.vmware.com/docs/11750/virtual-disk-development-kit-programming-guide/GUID-C13FE900-6B19-4082-A040-354FB1F60BCB.html VDDK SDK: https://code.vmware.com/web/sdk/7.0/vddk Here is an example: https://github.com/vmware/photon/blob/master/support /image-builder/ovagenerator.py#L53 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893898 Title: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1893898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871975] Re: network configuration is disabled by default in cloud-init for ubuntu live server beta
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 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1871975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892447] Re: Why ignore new name server if 3 name servers exists
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 servers will be discarded. In our scenario, new name servers sent to cloud-init by OVF datasource, but the result is inconsistent, depends on how many name servers exist before power-on. If change the implementation to append the current name servers to the new name servers, then the current name servers are in the tail, then keep the first 3 of the list. In such way, new name servers can be always set. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892447 Title: Why ignore new name server if 3 name servers exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1892447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892447] [NEW] Why ignore new name server if 3 name servers exists
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 already exists, I know the max number is 3 for name servers. But why not replace the existing name servers by new ones? Thanks, Pengpeng ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892447 Title: Why ignore new name server if 3 name servers exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1892447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871975] Re: network configuration is disabled by default in cloud-init for ubuntu live server beta
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 disabled by default in cloud-init for ubuntu live server beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1871975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871975] Re: network configuration is disabled by default in cloud-init for ubuntu live server beta
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1871975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871975] Re: network configuration is disabled by default in cloud-init for ubuntu live server beta
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 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1871975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871975] Re: network configuration is disabled by default in cloud-init for ubuntu live server beta
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1871975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871975] Re: network configuration is disabled by default in cloud-init for ubuntu live server beta
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 Ubuntu Live Server VMs, so he clone the step3 created VM and Customize the new VMs network (cloud-init works here, using OVF datasource) to have different IP addresses. 5. Since the subiquity-disable-cloudinit-networking.cfg exists, cloned VMs fail to configure Netplan network configuration by cloud-init. ** Changed in: cloud-init (Ubuntu) Status: Incomplete => Confirmed -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1871975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871975] Re: network configuration is disabled by default in cloud-init for ubuntu live server beta
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 default in cloud-init for ubuntu live server beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1871975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871975] Re: network configuration is disabled by default in cloud-init for ubuntu live server beta
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 default. If the Subiquity works one time, is it possible that subiquity-disable- cloudinit-networking.cfg is deleted after installation. ** Changed in: cloud-init (Ubuntu) Status: Incomplete => Confirmed -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1871975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871975] Re: network configuration is disabled by default in cloud-init for ubuntu live server beta
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 subiquity-disable-cloudinit-networking.cfg exists. This prevents some user scenarios working which I'm sure they are working on Ubuntu 18.04: For ex: On VMware vSphere platform, an Ubuntu system network can be customized to different netplan configuration by cloud-init. I believe public clouds such as AWS and Azure are using cloud-init to configure network for new instance. Please share more information on how subiquity works with cloud-init, change the status back to New. ** Changed in: cloud-init (Ubuntu) Status: Incomplete => New -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1871975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850775] Re: DNS info is not loaded by dhclient
@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: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850775] Re: DNS info is not loaded by dhclient
@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 dhclient To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850775] Re: DNS info is not loaded by dhclient
@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 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: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850775] Re: DNS info is not loaded by dhclient
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 the root cause is not same with bug 1849608 -- 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: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850775] Re: DNS info is not loaded by dhclient
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- hooks.d/resolved script at boot, but it's possible that when this script executed, systemd-resolved.service is not ready for reload or restart. -- 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: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850775] [NEW] DNS info is not loaded by dhclient
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 "systemd-resolve --status", the DNS domain and server is not set. But /run/systemd/resolved.conf.d/isc- dhcp-v4-ens160.conf contains the new DNS domain and server. 4. Manually run "systemctl try-reload-or-restart systemd- resolved.service" and then DNS is set correctly, "systemd-resolve --status" output have the new DNS domain and server. I tried the same steps on Ubuntu18.04 Desktop, no such issue. DNS updated correctly after reboot. Thanks, Pengpeng ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Package changed: cloud-init (Ubuntu) => network-manager (Ubuntu) -- 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: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844763] Re: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso
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 go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844763] Re: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso
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 -- 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 go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844763] Re: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844763] Re: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso
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. https://bugs.launchpad.net/bugs/1844763 Title: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833192] Re: VMware: post custom script isn't run correctly
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 correctly To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1833192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
@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 open-vm-tools.service file, since it will create dependency cycle during booting. And If it's possible, I suggest use Ubuntu18.04, not Ubuntu16.04 to work with cloud-init -- 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 Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
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 customization engine: -- 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 Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
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. https://bugs.launchpad.net/bugs/1793715 Title: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
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 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 Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
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 Customization works with either pure 'perl' scripts or cloud-init as the customization engine. For 'perl' scripts customization, scripts are triggered by open-vm-tools.service, the 'hostnamectl' is the cmd in scripts to set hostname. And 'hostnamectl' has dependency on 'dbus.service'. For 'cloud-init' customization, only 2 config files are copied to a folder by open-vm-tools.service, and then cloud-init-local.service read the config file from that folder to do the customization. This is the reason of "bug 1667831 to have open-vm-tools before cloud-init-local was by Sankar from VMWare". And AFAIK, cloud-init is not using 'hostnamectl' to set hostname for Ubuntu distro. so when do the 'cloud-init' customization on Ubuntu, there is no dependency on 'dbus.service'. And Yes, I also noticed the cycle dependency was introduced if add 'After=dbus.service' to 'open-vm-tools.service' when cloud-init*.services are also enabled.(https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1796875/comments/8) So the 'after=dbus.service' should only be added when using perl scripts as customization engine. see details in the workaround KB for Ubuntu18.04 Live Server https://kb.vmware.com/s/article/54986 For Set cloud-init as the customization engine: no need add 'after=dbus.service' to open-vm-tools.service For Set perl script as the customization engine: need add 'after=dbus.service' to open-vm-tools.service and also disable or remove cloud-init -- 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 Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766538] Re: network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server
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 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 notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1766538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
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 Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803939] Re: cloud-init.service dependency is missing on 10.3.5 open-vm-tools service
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 -- 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 on 10.3.5 open-vm-tools service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1803939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803939] [NEW] cloud-init.service dependency is missing on 10.3.5 open-vm-tools service
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” under [Unit] section of open-vm-tools.service file. Thanks, Pengpeng ** Affects: open-vm-tools (Ubuntu) Importance: Undecided Status: New -- 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 on 10.3.5 open-vm-tools service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1803939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803939] Re: cloud-init.service dependency is missing on 10.3.5 open-vm-tools 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 After=vgauth.service [Service] -- 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 on 10.3.5 open-vm-tools service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1803939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803939] Re: cloud-init.service dependency is missing on 10.3.5 open-vm-tools 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 on 10.3.5 open-vm-tools service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1803939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796875] Re: cloud-init and cloud-init-local services boot sequence does not obey dependency settings
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 boot sequence does not obey dependency settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1796875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798540] Re: Question on '/var/lib/cloud/instance'
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz-plugins-main/+bug/1798540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796875] Re: cloud-init and cloud-init-local services boot sequence does not obey dependency settings
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 services boot sequence does not obey dependency settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1796875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798540] [NEW] Question on '/var/lib/cloud/instance'
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 https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1796875 Looking forward to your response, thanks. Pengpeng ** Affects: compiz-plugins-main (Ubuntu) Importance: Undecided Status: New -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz-plugins-main/+bug/1798540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796875] Re: cloud-init and cloud-init-local services boot sequence does not obey dependency settings
@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 go to launch a LP bug for Ubuntu 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/1796875 Title: cloud-init and cloud-init-local services boot sequence does not obey dependency settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1796875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796875] Re: cloud-init and cloud-init-local services boot sequence does not obey dependency settings
@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 it. ** Attachment added: "cloud-init-18.04.1-FAIL.tar.gz" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1796875/+attachment/5200337/+files/cloud-init-18.04.1-FAIL.tar.gz -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1796875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796875] Re: cloud-init and cloud-init-local services boot sequence does not obey dependency settings
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 $ vmtoolsd -v VMware Tools daemon, version 10.2.0.1608 (build-7253323) -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1796875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796875] Re: cloud-init and cloud-init-local services boot sequence does not obey dependency settings
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 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1796875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796875] Re: cloud-init and cloud-init-local services boot sequence does not obey dependency settings
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 -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1796875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796875] Re: cloud-init and cloud-init-local services boot sequence does not obey dependency settings
@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 sequence does not obey dependency settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1796875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796875] [NEW] cloud-init and cloud-init-local services boot sequence does not obey dependency settings
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- init-local.service I did some testing on the following combination: Ubuntu18.10 daily build + cloud-init 18.4-0 FAIL Ubuntu18.04.1 + cloud-init 18.4-0 FAIL Ubuntu18.04.1 + cloud-init 18.3-9 FAIL Ubuntu18.04GA + cloud-init 18.3-9 PASS This could be a regression from Ubuntu18.04.1, please help to check it. On the PASS test, the sequence is: cloud-init.service +2.317s └─systemd-networkd-wait-online.service @17.308s +1.706s └─systemd-networkd.service @17.223s +83ms └─network-pre.target @17.219s └─cloud-init-local.service @2.791s +14.426s └─systemd-remount-fs.service @1.792s +994ms └─systemd-journald.socket @1.719s └─system.slice @1.712s └─-.slice @1.698s On the Fail test, the sequence is: cloud-init-local.service └─open-vm-tools.service @2min 6.601s └─dbus.service @2min 6.593s └─basic.target @2min 6.576s └─paths.target @2min 6.566s └─acpid.path @2min 6.557s └─sysinit.target @2min 6.556s └─cloud-init.service @2min 2.386s +4.169s └─systemd-journald.socket @1.012s └─system.slice @998ms └─-.slice @998ms ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1796875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796875] Re: cloud-init and cloud-init-local services boot sequence does not obey dependency settings
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1796875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
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 workaround, We publish this KB to tell customer about this issue. Here is a thread that customer met and workaround this issue: https://github.com/vmware/open-vm-tools/issues/240 ** Bug watch added: github.com/vmware/open-vm-tools/issues #240 https://github.com/vmware/open-vm-tools/issues/240 -- 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 Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790434] [NEW] Cherry pick a fix of cloud-init
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 current or near next Ubuntu release, or what's schedule of rebase the cloud-init version which contains this fix, looking forward to your comment. Thanks, Pengpeng ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790434 Title: Cherry pick a fix of cloud-init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1790434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766538] Re: network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server
** 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 cloud-init does not work on Ubuntu18.04 Beta2 Server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776452] Re: Fail to set DNS server and search domain when customize Ubuntu18.04 to DHCP IP by cloud-init
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. https://bugs.launchpad.net/bugs/1776452 Title: Fail to set DNS server and search domain when customize Ubuntu18.04 to DHCP IP by cloud-init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1776452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776452] [NEW] Fail to set DNS server and search domain when customize Ubuntu18.04 to DHCP IP by cloud-init
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:
2018-06-12 09:50:19,852 - stages.py[INFO]: Applying network configuration from
ds bringup=False: {'version': 1, 'config': [{'type': 'physical', 'name':
'ens160', 'mac_address': '00:50:56:bd:45:d2', 'subnets': [{'control': 'auto',
'type': 'dhcp'}]}, {'type': 'nameserver', 'address': ['10.117.21.1',
'10.117.21.2'], 'search': ['dns.test.com']}]}
To attach cloud-init logs by 'cloud-init collect-logs' and 50-cloud-init.yaml
Note: If customize the same VM with Static IP and DNS servers/search domain,
they will be written to /etc/netplan/50-cloud-init.yaml correctly.
** Affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776452
Title:
Fail to set DNS server and search domain when customize Ubuntu18.04 to
DHCP IP by cloud-init
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1776452/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776452] Re: Fail to set DNS server and search domain when customize Ubuntu18.04 to DHCP IP by cloud-init
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. https://bugs.launchpad.net/bugs/1776452 Title: Fail to set DNS server and search domain when customize Ubuntu18.04 to DHCP IP by cloud-init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1776452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776452] Re: Fail to set DNS server and search domain when customize Ubuntu18.04 to DHCP IP by cloud-init
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. https://bugs.launchpad.net/bugs/1776452 Title: Fail to set DNS server and search domain when customize Ubuntu18.04 to DHCP IP by cloud-init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1776452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766538] Re: network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server
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 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766538] Re: network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server
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 Server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766538] Re: network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766538] Re: network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server
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 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766538] Re: network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server
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 steps and collected cloud-init logs on the GA version of Ubuntu18.04 Server. 1. Installed Ubuntu18.04 Server GA build on a VMware VM 2. Ran 'apt install cloud-init' to install cloud-init 3. Did VMware guest customization by cloud-init on this VM 4. Ran 'cloud-init collect-logs', please find the generated .gz file in attachment I set the bug status back to "New", please relook at this issue. Let me know if any other info needed here. Thanks, Pengpeng -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766538] Re: network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server
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 cloud-init source /etc/network/interfaces.d/*.cfg >ls /etc/network/interfaces.d 50-cloud-init.yaml Ubuntu 18.04 Server: >ls /etc/network if-post-down.d if-pre-up.dif-up.dinterfaces interfaces.before_vmware_customization >cat /etc/network/interfaces # DO NOT EDIT THIS FILE BY HAND -- AUTOMATICALLY GENERATED BY cloud-init source /etc/network/interfaces.d/*.cfg >ls /etc/netplan 01-netcfg.yaml50-cloud-init.yaml ·On Desktop, it has ’50-cloud-init.cfg’ under /etc/network/interfaces.d which is correct network configuration according to customization spec ·On Server, there is no /etc/network/interfaces.d directory, the ’50-cloud-init.cfg’ is under /etc/netplan and it does not change according to customization spec. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766538] [NEW] network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server
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 parsed the cust.cfg, but VM network is not customized correctly according to cust.cfg. ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766538] Re: network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server
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. https://bugs.launchpad.net/bugs/1766538 Title: network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762881] [NEW] cloud-init (18.2-0ubuntu1) does NOT detect the correct datasource after installed Ubuntu18.04 Beta2 Server on a VMWare VM
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]”. This is not the expected datasource, the expected one should be 'DataSourceOVF'. could you please help to check this. ** Affects: open-vm-tools (Ubuntu) Importance: Undecided Status: New ** Tags: ds-identify ** Tags added: ds-identify -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762881 Title: cloud-init (18.2-0ubuntu1) does NOT detect the correct datasource after installed Ubuntu18.04 Beta2 Server on a VMWare VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1762881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760776] Re: cloud-init (18.2-0ubuntu1) service is not running in ubuntu-18.04-desktop-64
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 ntp.conf.sles.tmpl ntp.conf.ubuntu.tmpl resolv.conf.tmpl sources.list.debian.tmpl sources.list.ubuntu.tmpl timesyncd.conf.tmpl -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760776 Title: cloud-init (18.2-0ubuntu1) service is not running in ubuntu-18.04-desktop-64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1760776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760776] Re: cloud-init (18.2-0ubuntu1) service is not running in ubuntu-18.04-desktop-64
** 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" https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1760776/+attachment/5101172/+files/ds-identify.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760776 Title: cloud-init (18.2-0ubuntu1) service is not running in ubuntu-18.04-desktop-64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1760776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760776] Re: cloud-init (18.2-0ubuntu1) service is not running in ubuntu-18.04-desktop-64
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 did not manually configure /etc/cloud/cloud.cfg either on that Ubuntu Server, unfortunately the Server VM has been deleted. I will install a new one. I think ds-identify should be able to find the correct ds on a VMware VM, if not true, what's configure should be set here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760776 Title: cloud-init (18.2-0ubuntu1) service is not running in ubuntu-18.04-desktop-64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1760776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760776] Re: cloud-init (18.2-0ubuntu1) service is not running in ubuntu-18.04-desktop-64
** 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. https://bugs.launchpad.net/bugs/1760776 Title: cloud-init (18.2-0ubuntu1) service is not running in ubuntu-18.04-desktop-64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1760776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760776] Re: cloud-init (18.2-0ubuntu1) service is not running in ubuntu-18.04-desktop-64
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 Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed run cloud-init collect-logs and attached .gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760776 Title: cloud-init (18.2-0ubuntu1) service is not running in ubuntu-18.04-desktop-64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1760776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760776] Re: cloud-init (18.2-0ubuntu1) service is not running in ubuntu-18.04-desktop-64
** 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. https://bugs.launchpad.net/bugs/1760776 Title: cloud-init (18.2-0ubuntu1) service is not running in ubuntu-18.04-desktop-64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1760776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
