> 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
Public bug reported:
Description: Encountered multiple issues while attempting to connect and
activate a Thunderbolt device. Initially, the device was recognized but
then disconnected shortly after. System logs indicated a DROM data CRC
mismatch, despite which, the system attempted to continue
Thank you Olivier
The command resolved my problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970148
Title:
Brave & Chrome browsers freezes on download and print to pdf
To manage
** Package changed: ubuntu => chromium-browser (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970148
Title:
Brave & Chrome browsers freezes on download and print to pdf
To manage
I am on Ubuntu 22.04.
It also freezes my Google chrome browser(Version 100.0.4896.127), if I
try to upload any file from local. The page and the window become
unresponsive. But I can create new window or close the browser using
right click menu from the GNOME on the top and right sidebar.
--
Hi @Nick Rosbrook (enr0n)
Will any modification(regarding snapd udev rule) be included in the
Ubuntu 22.04 release version?
Thanks,
Regards,
Jiwei
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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:
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
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
According to our investigation, I found that the issue is caused by the
"mount" system call can not be allowed to execute.
And after checking the upstream commit, the issue is introduced by the
following patch,
commit ee8f26180d01e3ddd4e5f20b03b81e5e737657ae
Author: Lennart Poettering
Date:
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
root@plis231v:~# ps -o cmd fp 1
CMD
/sbin/init
root@plis231v:~# sudo ls -lah /proc/1/exe
lrwxrwxrwx 1 root root 0 Feb 11 22:51 /proc/1/exe -> /sbin/upstart
root@plis231v:~# cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.15.0-167-generic root=/dev/mapper/plis231v-root ro quiet
root@plis231v:~#
--
You
any suggestion to fix this?
I had tried below command.
root@plis231v:~# sudo dpkg -l | grep systemd
ii libpam-systemd:amd64 229-4ubuntu21.31+esm1
amd64system and service manager - PAM mod
ii libsystemd0:amd64
root@plis231v:~# systemctl status
Failed to read server status: Invalid argument
root@plis231v:~#
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961418
Title:
snap failed to run with
root@plis231v:~# apt show snapd
Package: snapd
Version: 2.54.3+16.04~esm2
Built-Using: apparmor (= 2.10.95-0ubuntu2.11), libcap2 (= 1:2.24-12),
libseccomp (= 2.4.3-1ubuntu3.16.04.3)
Priority: optional
Section: devel
Maintainer: Ubuntu Developers
Installed-Size: 146 MB
Depends: adduser, apparmor
Hey Alberto Mardegan,
This issue is blocking us to enable livepatch.
root@plis231v:~# systemctl status snapd
Failed to get properties: No such interface ''
root@plis231v:~# systemctl status snapd.socket Failed to get properties: No
such interface ''
root@plis231v:~# journalctl -b -u snapd
Public bug reported:
I tried to enable livepatch without any success. ([Bug 1960689] )
support suggested me report a bug for snapd.
root@plis231v:~# sudo ua enable livepatch
One moment, checking your subscription first
Unexpected error(s) occurred.
For more details, see the log:
.
root@plis231v:~#
-Original Message-
From: nore...@launchpad.net On Behalf Of Lucas
Albuquerque Medeiros de Moura
Sent: Tuesday, February 15, 2022 8:11 AM
To: Gene Sun
Subject: [Bug 1960689] Re: livepatch is not able to enabled
CAUTION: EXTERNAL EMAIL
Hello Gene Sun,
It seems
...@launchpad.net On Behalf Of Grant Orndorff
Sent: Monday, February 14, 2022 1:54 PM
To: Gene Sun
Subject: [Bug 1960689] Re: livepatch is not able to enabled
CAUTION: EXTERNAL EMAIL
Hello Gene Sun, thank you for taking the time to file a bug!
The livepatch service is installed as a snap when you
root@plis231v:~# uname -a
Linux plis231v 4.15.0-167-generic #175~16.04.1-Ubuntu SMP Mon Jan 17 16:44:18
UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
root@plis231v:~#
root@plis231v:~#
root@plis231v:~# sudo ua enable livepatch
One moment, checking your subscription first
Unexpected error(s) occurred.
Public bug reported:
I tried to enable livepatch without any success.
root@plis231v:~# sudo ua enable livepatch
One moment, checking your subscription first
Unexpected error(s) occurred.
For more details, see the log: /var/log/ubuntu-advantage.log
To file a bug run: ubuntu-bug
apport-collect reports much much more than I'm willing to share, and I
believe what I've provided is sufficient.
So I'll pass this time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954844
Title:
Public bug reported:
The culprit might as well be the same as reported in
https://bugs.launchpad.net/ubuntu/+source/lxqt-panel/+bug/1881397
The reason I'm opening this, according to upstream, where I initially reported
the problem,
https://github.com/lxqt/lxqt/issues/2154
is that the problem
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950644
Title:
ubuntu_ltp / finit_module02 fails on v4.15 and other kernels
To manage
> And I've just reinstalled them all.
with,
sudo apt install --reinstall fcitx fcitx-bin fcitx-config-common fcitx-
config-gtk fcitx-data fcitx-frontend-all fcitx-frontend-gtk2 fcitx-
frontend-gtk3 fcitx-frontend-qt5:amd64 fcitx-module-dbus fcitx-module-
kimpanel fcitx-module-lua
Public bug reported:
I'm getting the following error whenever I start GTK related programs,
like meld, firefox etc:
GLib-GIO-CRITICAL **: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION
(connection)' failed
All search hits suggests that it is fcitx-module-dbus' problem, and
removing it will
So far I can only find fcitx-module-dbus *version 4* in 21.10 impish's
repo, but it does has fcitx5.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950065
Title:
GLib-GIO-CRITICAL **:
Public bug reported:
[Impact]
* Update bpftrace to latest version 0.14.0
[Scope]
* 20.04
** Affects: bpftrace (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I use ubuntu20.04 and set static IP 192.168.11.22 in
/etc/network/interfaces. Most time it could work but sometimes the IP
changed to 192.168.11.105, which same to be a DHCP IP. I checked the
syslog and journalctl, find that eth0 same to disconnect and be re-
configured by
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
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
Public bug reported:
This one is opened to track the merge of the mlx-bootctl driver fix to
support rshim logging display from linux sysfs.
SRU Justification:
[Impact]
* N/A.
[Fix]
* Add support to display rshim logging bufferthe check properly to make sure
the buffer won't wrap-around.
Public bug reported:
This one is used to track a code merge of the tmfifo driver.
SRU Justification:
[Impact]
* The virtio framework uses wmb() when updating avail->idx. It guarantees the
write order, but not necessarily loading order for the code accessing the
memory. So potentially it could
Public bug reported:
THis one is created to track the commit merge of the mlxbf-tmfifo driver
to support ctrl message and MAC configuration.
SRU Justification:
[Impact]
* N/A.
[Fix]
* N/A.
[Test Case]
* Set DISPLAY_LEVEL to 1 in /dev/rshim0/misc and do 'cat /dev/rshim0/misc' from
external
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, 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
Verified that the same fix has been available in the master-next branch.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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, 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
** Description changed:
On Bluefield platforms, the 'bfrshlog' script can be used to write a
string into the internal rshim logging buffer which has size 1KB. When
the buffer is full, the intention is to drop the new data. However, due
to a bug, the buffer could be overwritten and
Public bug reported:
On Bluefield platforms, the 'bfrshlog' script can be used to write a
string into the internal rshim logging buffer which has size 1KB. When
the buffer is full, the intention is to drop the new data. However, due
to a bug, the buffer could be overwritten and wrap-around when
I have encountered this problem in the armhf board too. I employed
Xubuntu 20.04 on both RK3399(aarch64) and RK3288(armhf). Then I found
that the lightdm-greater cannot work in RK3288. The log is the same as
Steve said. I attempted to avoid this problem by logging in
automatically. It's a trick to
actually, the shell extension(in ubuntu software) Multi Monitors Add-On
works, although it is not perfect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682542
Title:
Add support for top bars on
When I am in the full-screen on the primary monitor, the top bar is
blocked, so it is necessary for me to show the top bar in another
monitor. It is truely a bug to be fixed, but the Linux seems not to be
aware of it.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
OC RAM results in hardware Error in dmesg, and auto-reboot from time to time.
The same BIOS setting OC RAM worked just fine on Windows 10 2004, and also
passed RAM TEST 86.
error log:
[ 316.850589] [Hardware Error]: Corrected error, no action required.
[ 316.850593]
I created the install media using rufus in DD mode (instead of ISO) and it
worked.
sun
On Tue, Oct 27, 2020 at 10:10 PM Sunil S Kulkarni (सुनील सुरेश कुलकर्णी) <
sunil...@gmail.com> wrote:
> I have checked the ISO using the sha. But I still experience the error.
> I am b
I have checked the ISO using the sha. But I still experience the error.
I am burning again with universal USB installer. I'll try with that and
I'll report again.
sun
On Tue, Oct 27, 2020 at 4:00 PM Chris Guiver <1901...@bugs.launchpad.net>
wrote:
> I see a "CasperMD5CheckResult:
Public bug reported:
Installing 20.04 LTS on a samsung pro SSD and on I5 10400. Hyper-
threading and TPM are disabled.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
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
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
Public bug reported:
The ddclient needs upgrade for Ubuntu 20.04 LTS, or at least put
ddclient (3.9.1-5) into focal-backports.
My /etc/ddclient.conf has been working for years, but recently it is
broken:
rm /var/cache/ddclient/ddclient.cache
$ sudo ddclient -daemon=0 -force
FAILED: Could not
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,
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
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
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
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
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
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
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
latest version 4.0.3-0.1 is in Ubuntu now
(https://launchpad.net/ubuntu/+source/shc), thus closing this old bug.
Please reopen if problem persists.
** Changed in: shc (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@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:
Hi,How did you finally solve this problem?
i am in add
sudo -E add-apt-repository ppa:mosquitto-dev/mosquitto-ppa
exception message:
Cannot add PPA: 'ppa:~mosquitto-dev/ubuntu/mosquitto-ppa'.
ERROR: '~mosquitto-dev' user or team does not exist.
--
You received this bug notification because you
@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
@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
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-
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
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
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
> This bug report will be marked for expiration in 59 days
I'll wait for it to close itself then, if nobody else can confirm it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845745
Title:
Cannot
> Lubuntu didn't support sddm until 18.10
Ah, that might explains it. I'm using the Lubuntu 18.04 without much
upgrade. I.e., my system being 18.04 and not fully updated might be the
cause.
** Summary changed:
- Cannot change login user for SDDM
+ Cannot change login user for SDDM under
Public bug reported:
I have more than one user set up but the login screen only shows the initial
(original) user with SDDM.
Using LightDM allows me to type in (thus change to) the other users, and they
are able to login just fine.
I.e., my SDDM login screen always stuck with the original
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.
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
@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
Thanks for the comment.
The input file is almost identical to that of the original package. I
checked https://bugs.debian.org/219188, and found that it only talks
about the warning of can't parse dependency, not this fatal error on
debian/changelog. Moreover, the package has been created in
Public bug reported:
There is no debian/changelog file involved when using equivs-build, so
would the "fatal error occurred while parsing debian/changelog" error be
a bug?
Here are the details:
$ cat ttf-ubuntu-font-family
Package: ttf-ubuntu-font-family
Architecture: all
Version: 91:0.83-2
Public bug reported:
Just like reported (twice) at
https://bugzilla.redhat.com/show_bug.cgi?id=1350122,
dar will Segmentation fault when using the xz compression:
$ /usr/bin/dar -zxz -R . -c /path/to/my-dar-full
Segmentation fault
Mainly because `xz` support is actually disabled from libdar
Public bug reported:
My simple Netboot install configuration file doesn't have any kernel
specification, except a commented out line of:
#d-i base-installer/kernel/image string linux-generic
It worked all the way up to 18.04, but when I'm trying 19.04 just now,
I'm getting:
in-target: Setting
There is a long story why shc hasn't been updated which I won't get into
details.
But I've waited long enough and finally decided that I should take up packing
shc again. The newest version has just been packaged and uploaded to to
mentors.debian.net. The URL is:
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
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 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
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
Public bug reported:
it talks about attaching files, but there's nothing on this page to do
so
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubiquity 18.10.12 [modified:
lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux
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
--
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
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
1 - 100 of 486 matches
Mail list logo
