Hi,
from your log:
[...]
Searching for GRUB installation directory ... found: /boot/grub
Testing for an existing GRUB menu.lst file ...
Could not find /boot/grub/menu.lst file. Would you like /boot/grub/menu.lst
generated for you? (y/N) /usr/sbin/update-grub-legacy-ec2: line 1101: read:
read
FYI - the libvirt change is in git, just needs a few other things and
tests to be complete for an upload.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784023
Title:
Update profiles for usrmerge
Hmm, might this be due to a specific issue on your BMC (config or FW
level)?
$ cat /proc/cpuinfo | grep machine
machine : PowerNV 9006-12C
$ sudo ipmitool user list 1
ID Name Callin Link Auth IPMI Msg Channel Priv Limit
1truefalse false
Public bug reported:
Split from bug 1745114 which needs more apparmor features to complete.
The two most interesting places to tweak livbirt/qemu guest apparmor config are:
1. per guest (that is bug 1745114)
2. for all guests which is abstractions/libvirt-qemu
This might be a special case for
Trying an interim TL;DR:
- Service A - --no-stop-on-upgrade
A Requires A1.socket
A Requires A2.socket
- Service B - --restart-after-upgrade
B Requires=A1.socket
- A and B have also sysV scripts.
- d/rules calls dh_installinit and dh_systemd_start
- maintscripts get
This is confusing enough
Was incomplete - once more
Trying an interim TL;DR:
- Service A - --no-stop-on-upgrade
A Requires A1.socket
A Requires A2.socket
- Service B - --restart-after-upgrade
B Requires=A1.socket
- A and B have also sysV scripts.
- d/rules calls dh_installinit and dh_systemd_start
- maintscripts
Fix V:
- drop virtlogd sysV script (to fix the original issue) and drop the
dh_systemd__start call to
libvirtd (to avoid the secondary issue)
- Intention: libvirtd (re)start is taken care of by dh_installinit anyway,
avoid the bad restarts
on virtlogd with this tweak
- with that it
Please do mind that this is in the new queue as I mentioned upfront - for the
two new PMDs.
Build is complete but while waiting for NEW to be accepted it can't be tested
yet from proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Spun up a VM with 18.04 Desktop and verified from proposed.
Starting now -> setting verified.
FYI: I beg your pardon, since it was in a VM UI session I have no easy
copy of the upgrade log that I usually would add.
** Tags removed: verification-needed verification-needed-bionic
** Tags added:
Submitted my updated findings to Debian
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786179
Title:
double virtlogd sockets with services running can trigger issues on
upgrade
To manage
Public bug reported:
Postgresql stable update
Current versions in supported releases:
postgresql-9.3 | 9.3.23-0ubuntu0.14.04 trusty
postgresql-9.5 | 9.5.13-0ubuntu0.16.04 xenial
postgresql-10 | 10.4-0ubuntu0.18.04 bionic
postgresql-10 | 10.5-1cosmic
Special cases:
-
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/postgresql-9.3/+git/postgresql-9.3/+merge/353090
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/postgresql-9.5/+git/postgresql-9.5/+merge/353091
** Merge proposal linked:
Thanks Amos for the ping, we will discuss in our standup today who could take a
look at the merge.
4.x in Debian LGTM on the tracker page and bugs, do you know about any big
things to be aware of when going 3.x->4.x?
--
You received this bug notification because you are a member of Ubuntu
Your system has plenty of conffiles manually deleted.
Like for example:
modified.conffile..etc.libvirt.libvirtd.conf: [deleted]
DPKG/Apt can't differentiate if you wanted this as a configuration of
the service or just to remove it. With that the service can't restart
and that is what is needed
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time
>From your log I see:
Setting up mysql-server-5.7 (5.7.23-0ubuntu0.18.04.1) ...
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration or
Hardware problem, rather than a bug in Ubuntu, I'm marking this bug as
Incomplete.
If indeed this is a local configuration problem, you can find
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time
Hi Andy,
I can't tell from the log what happened.
But usually the only reasonable way out is to re-install all of said package as
described in [1].
Also I wonder seeing python being unable to run at all it seems, if
there is more broken on your system or if you have disk/filesystem
issues
*** This bug is a duplicate of bug 1761406 ***
https://bugs.launchpad.net/bugs/1761406
This kind of error is frequent enough to be interesting, but so far lacks a
good way to debug.
Since the dumps are not directly leading to a bug a reproducer would be great.
We want to join forces so I
Hi Ante, being a Kernel introduced issue Jürg was testing it (not me as
I had no spare HW at the time anyway) - see comment #24.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767857
Title:
Kernel
Got hold of a P9 system and was glad that it seems to reproduce there as well
(I was afraid it might only show on P8 which I had no free one atm).
- confirmed to affect Bionic
- confirmed to affect Cosmic
- proposed PPA confirmed to fix the issue
Hangs are at very early boot of the initrd or
[1] is building and has to pass propsoed-migration.
Taking a look tomorrow when the tests had some time to run.
[1]: https://launchpad.net/ubuntu/+source/qemu/1:2.12+dfsg-3ubuntu4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yeah it is always good to have such insights here to be found by search
engines for the next who hits it.
Glad that my recommendations helped.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384532
I agree strongswan/openconnect (and maybe more) are affected by the
symptom, while the bug lies in bind9-host/avahi packages at least
according to current debugging.
>From my experience I guess what would be great to get more traction on this is
>to get a shorter reproducer than setting up some
Hmm, that would mean the new upstream isn't as good as we 'd have hoped :-/
And you said the same 2.4.6 but from a PPA or so works fine?
Could you refer me to that PPA, maybe I can pull in some modifications
from there that would help Ubuntu as well.
--
You received this bug notification
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
Hi,
your logs suggest that you tried to switch between mysql/mariadb which are
incompatible.
I'm not sure what else to recommend than to follow exactly what was suggested
by the messages you copied and posted here.
You have to decide to either retain the old DB data (and install the
matching
Working on Bionic SRu prep in https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/3367/+packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787408
Title:
qemu 1:2.11+dfsg-1ubuntu7.4
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time
>From your log:
авг 18 12:20:40 vbif-System-Product-Name amavis[3367]: Starting amavisd: head:
cannot open '/etc/mailname' for reading: No such file or directory
авг 18 12:20:40 vbif-System-Product-Name amavis[3367]: The value of variable
$myhostname is "vbif-System-Product-Name", but should
Hi,
I'm checking old bugs every now and then, and this one had no activity since 6
months.
Reading the comments so far it reads like a valid bug, but with too few leads
to actually take action fixing or further debugging it :-/
Without being able to action as-is I'll drop the server-team
Verified what just got released in Cosmic to work as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787408
Title:
qemu 1:2.11+dfsg-1ubuntu7.4 hangs when -cpu POWER9 is specified
To manage
*** This bug is a duplicate of bug 1679435 ***
https://bugs.launchpad.net/bugs/1679435
This appears to be a dup of bug 1679435
There is plenty of detail to be found, but the most important TL;DR for you is
that it usually goes away by either of:
1. re-running theinstall/update
2. running
Hi Sonny,
the issue is that after an upgrade services have to be restarted - this fails
in your case.
The logs that are submitted are not helping to point at any particular issue,
but the TL;DR is that the configuration of postgresql has to be fixed so the
service can restart.
If you have no
Working on Bionic SRu prep in https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/3367/+packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755912
Title:
qemu-system-x86_64 crashed
Oh, I just realized while initially reported against qemu in bug 1781526
that this is a kernel, and not a qemu patch.
That spreads the timeline a bit:
- this should be in Cosmic before Release to avoid issues due to the fix of
1781526.
- since that is kind of short I'll bump priority there.
-
New Problem, new Bug - at least since the current one is already closed in
Cosmic.
Fortunately the SRU itself was still on hold waiting for another PPC fix to
complete to bundle them so we can make this part of it still.
I forked bug 1788098 for it.
Please set that for reverse bug mirroring to
FYI - until we can make this work, please do realize that at least the
global abstraction libvirt-qemu got a local override in Cosmic that can
be used to extend rules for all guests without having to bother with
conffile prompts later on.
--
You received this bug notification because you are a
I summarized it in another bug nicely (I think), quoting it here to be
on the main bug as well:
This had two phases with both having had their own issues:
Phase I: ~2013-2016: the libvirt- stayed around and could be used for
such overrides, but they cluttered the file system and overview was
As I assumed the old (cron) and new (virt-aa-helper call) cleanup code makes
the libvirt- files unusable.
Also all old approaches wanted to avoid cluttering /etc/apparmor.d/libvirt/* to
not loose overview.
Best (not fastest, but best) solution would really the "include if avail" once
available
*** This bug is a duplicate of bug 1745114 ***
https://bugs.launchpad.net/bugs/1745114
Yeah this had two phases with both having had their own issues, I'm
already working on this at a lower priority.
Phase I: ~2013-2016: the libvirt- stayed around and could be used for
such overrides, but
FYI: this is essentially an IBM request, reverse mirroring will happen
at some point, but I wanted to make you aware right now
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788098
Title:
Avoid
For this particular case the log files are not needed and/or applicable.
After discussing in #stable-kernel I set it to confirmed.
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: linux (Ubuntu Cosmic)
Status: Incomplete => Confirmed
--
You received
Public bug reported:
--- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---
Hi, in some environments it was observed that this qemu patch to enable THP
made it more likely to hit guest migration issues, however the following kernel
patch resolves those migration issues:
On Tue, Aug 21, 2018 at 12:30 PM Martin Wolf <1787...@bugs.launchpad.net>
wrote:
> I use the original openvpn repo for 16.04 xenial
> https://community.openvpn.net/openvpn/wiki/OpenvpnSoftwareRepos
Unfortunately they don't seem to publish deb-src to learn what they did.
I need to ask there ...
I'm discussing with upstream what they might do different, but so far all seems
that those should be the same - not sure what you hit.
If we can identify a bug we can still work on it down the road after Feature
Freeze, but in general the 2.4.6 looks good and fixes plenty of other things
for
*** This bug is a duplicate of bug 1731502 ***
https://bugs.launchpad.net/bugs/1731502
Hi,
it gets an timeout while waiting for interfaces.
>From your log:
"nmbd: No local IPv4 non-loopback interfaces available, waiting for interface
..."
Maybe a setup problem?
I never had IPV6 only samba
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time
*** This bug is a duplicate of bug 1731502 ***
https://bugs.launchpad.net/bugs/1731502
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the
>From the log:
Running sa-compile (may take a long time)
Jul 23 17:27:26.363 [1356] info: config: failed to parse line, skipping, in
"/etc/spamassassin/local.cf": use_dcc 0
sa-compile: not compiling; 'spamassassin --lint' check failed!
ESC[1mdpkg:ESC[0m error processing package sa-compile
marking newer releases Fix Relased per Former comment.
** Also affects: asterisk (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: asterisk (Ubuntu Cosmic)
Importance: High
Status: Confirmed
** Also affects: asterisk (Ubuntu Xenial)
Importance: Undecided
@kstenerud - please review, integrate, fixup, test, build, ... the usual things.
@fermulator - kstenerud will take care to carry your fix into Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
FYI bug 1786261 could be another symptoms of this, reporters there will
take a look and might add another affected package to this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752411
Title:
Hi,
I just realized with you tracking it down so far - could it be "another
symptom" of bug 1752411 ?
If so we should add strongswan there as affected and make this bug a
Dup, so that ALL effects of this one issue are in one place.
I'd be glad if one of you could make the detail check if you
Me as well now also passed a set of other tests over night, being ready
to SRU now after I added an SRU Template.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787408
Title:
qemu
FYI - in the SRU queue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787408
Title:
qemu 1:2.11+dfsg-1ubuntu7.4 hangs when -cpu POWER9 is specified
To manage notifications about this bug go to:
Uploaded to Cosmic, tracking migration there and prepping SRU here ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788226
Title:
libvirt might misdetect guests as not properly shut down when
** Description changed:
+ [Impact]
+
+ * Systems using plenty of PCI Host Devices can have lost the Qemu PID
+from /proc/ but the kernel still holds it quite a while while
+cleaning up resources.
+That leads to libvirtd giving up on the process and keeping the guest
+forever
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu.
You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community
Since we use this bug tracker to track bugs in Ubuntu, rather than
configuration
Hi,
that is an odd combination of program versions you have there.
Your system reports as Ubuntu Xenial 16.04
But it has kernel 4.10 which is not supported there (4.4 as released or 4.15 as
HWE kernel)
On open-vm-tools there is also newer version released already
2:10.2.0-3~ubuntu0.16.04.1
The
FYI - atm this is blocked on 1788098 being delivered
I'm tracking the other bug and we can pick up here again once resolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781526
Title:
Ubuntu18.04
The final form is working as expected on the case just as much as all
the former versions I had tested.
40 devices attached, getting the proper plus 80 seconds:
debug : virProcessKillPainfullyDelay:361 : vpid=34896 force=1 extradelay=80
--
You received this bug notification because you are a
** Description changed:
+ FYI: This blocks bug 1781526 - once this one here is resolved we can go
+ on with SRU considerations for 1781526
+
--- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---
- Hi, in some environments it was observed that this qemu patch to enable THP
made
** Description changed:
- When using qemu-system-x86_64 with the option -vga qxl, it crashes. The
- easiest way to crash it is by trying to change the guest's resolution.
- However, the system may randomly crash too, not happening only when
- changing resolution. Here is the terminal output of
** Description changed:
+ [Impact]
+
+ * The qemu code prior to qemu 3.0 has an issue where the power9 machine
+spec makes the guest issue unsupported instructions. Qemu has to be
+adapted to be able to understand that and not break.
+
+ * backport of upstream fix
The init script isn't used anymore instead it is systemd.
Therefore since Bionic the script security setting is at the systemd service:
--- a/debian/openvpn@.service
+++ b/debian/openvpn@.service
@@ -13,7 +13,7 @@ Documentation=https://community.openvpn.net/openvpn/wiki/HOWTO
Type=notify
Hi fermulator,
I was wondering vice versa if 5 seconds would be too short actually.
Yes the good cases will return in sub-second, but it is the bad cases we want
to fix here.
Having a bit more time to recover if it can doesn't seem too bad to me.
On the question of host -W for waiting.
While it
Odd, thanks for the clarification - that was absolutely helpful.
I'll try a repro with the config you initially added here tomorrow.
You were suspicious about the script security parameter before.
In your case with the 2.4.6 version, it clearly should set that from the
systemd service script.
Thanks Trent for the extra verification.
Tests also look good so far, but currently since a lot got uploaded due to
feature freeze some tests take a while.
We should have that in cosmic soon and then can pick the same for Bionic.
Thanks also for your thoughts on a better long term solution.
--
Thanks Hans for the pre-triage!
@Lukas - I have seen a few cases when booting from size-minimized images
that even if the universe repository is enabled there never was an "apt
update" run (The data packed into the image would be stale anyway, so
there is no reason to bloat it), and therefore no
Hi,
you seem to have all kinds of services already running, in your log I found:
Apache stumbling:
Aug 23 10:42:05 k-HP-EliteBook-8460p apachectl[7951]: (98)Address already in
use: AH00072: make_sock: could not bind to address [::]:80
Aug 23 10:42:05 k-HP-EliteBook-8460p apachectl[7951]:
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time
Hi Alexey,
I agree - I can reproduce the error and see just the same.
Bionic - reload hangs and then fails, eventually the service is fully restarted
due to the kill after timeout
Cosmic - working fine and reports:
The logs contain a few unrelated warnings as I run it in a container, but one
Tested, confirmed wrapped in a libvirt upstream patch and submitted at
https://www.redhat.com/archives/libvir-list/2018-August/msg01532.html
Lets give the people a few days to read and ack as well then we can push
it to cosmic.
It came to my mind that due to HWE-Kernels we eventually also want
I followed the linked howto sans the ipv6 pieces as I had no ipv6 target range
anywhere to be used.
I can connect just fine with that.
Before I do that it would be easier for you to check if dropping the ipv6 lines
from the server conf make it work.
If it does - then we know it only affects the
Nice, thanks for the verification of my suggestions.
So effectively we gain CAP_DAC_OVERRIDE and loose CAP_DAC_READ_SEARCH
CAP_AUDIT_WRITE.
I'll need to check the hostory how/why they were added/dropped respectively,
but that sounds like a fix that certainly can be done - much better then when
most operations are asynchronous, virsh only tells libvirtd what to do and
then spins for a reply.
Stracing virsh won't help.
You could enable libvirtd debug and take a check at the log.
See https://libvirt.org/logging.html
--
You received this bug notification because you are a member of
Subscribed there as well now to stay on top of it if upstream gets to a
conclusion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755912
Title:
qemu-system-x86_64 crashed with SIGABRT when using
Thanks Leonardo for your check as well!
I agree that this particular issue here is fixed as we hoped.
The other one with the freeze did not occur for me, you might open another bug
if you have any pointers how we could go on on this.
--
You received this bug notification because you are a
Running the Bionic ISO like:
$ qemu-system-x86_64 -cpu host -smp cores=4,threads=2 -boot d -m 2048
-enable-kvm -vga qxl -vnc :21 -cdrom ubuntu-18.04-desktop-amd64.iso
Attaching like:
$ vncviewer FullColor=1 AutoSelect=0 10.245.168.42:5921
(alternatives on tigervnc)
Well for me it had "-k de" as
Arr reading is hard today, you had the other bug open already ... grml
:-)
Never the less - This bug here is fixed in the proposed version and for
now that is the important part.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Martin,
no problem.
Exchaning the file "completely" might be too much unless we can reason all the
changes.
Some I'd think were made in Debian/Ubuntu for valid reasons and should be kept.
So if I might ask you continue your test for combinations of the delta.
I only reordered things to make
On Wed, Aug 29, 2018 at 2:01 AM Seth Arnold <1786...@bugs.launchpad.net>
wrote:
> This is unlikely to get security team traction before 18.10.
>
@Seth - 18.10 would be ok with me, but can we plan for "early 18.10, like
the first 1/3 of the cycle" to not be locked up by component mismatches
until
I think you are good on the files of dnsmasq, I missed that those are the
complete files indeed.
I beg your pardon for doing too much things at once.
Thanks for the upstream issue, I subscribed there to keep on track.
But there I can see right what I assumed:
kubic-kvm git:(kubic-kvm) ✗ cat
Acks are in, pushed for Cosmic
** Changed in: chrony (Ubuntu Bionic)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787366
Title:
avoid service start hang due to
I agree to Seth that this seems more a like an upstream feature request.
If you do end up filing an upstream bug, please link to it from here, so that
Ubuntu can follow and either merge it down the road when a new version includes
it or if the discussion reveals that it could be resolved via a
As expected this got unblocked with the new libvirt and works now.
** Changed in: libvirt (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786157
Title:
Odd, Ubuntu has no particular Delta on the 2.4.4 package.
I'd try to make you an 2.4.6 package available - that I'd want to do for the
upcoming Ubuntu Cosmic release anyway.
If it is good in there we at least know there really is an upstream fix
between 2.4.4 and 2.4.6 that has to be found to
This affects Debian as well and we should not take Delta for such a low prio
issue.
I've created a PR for them to take which once merged will be picked up
automatically on the next Ubuntu Release.
=> https://salsa.debian.org/libvirt-team/virt-manager/merge_requests/1
Unfortunately those can't
Hallo,
your log essentially show s it failing due to a bad configuration:
Unable to locate guest account [smbguest]!
get_guest_info3 failed with NT_STATUS_NO_SUCH_USER
ERROR: failed to setup guest info.
I assume you have enabled something like this in your /etc/smb.conf
guest account =
Umm, I just realized the samba-ad-dc.service issue was Joe.
If that is an issue pelase report a new bug for it.
The request about reproducing the case and reporting the logs above
should be going to @Tim instead.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi Joe,
the initial bug contains no journal log or systemctl status of the failing
service after install.
On the initial report per TerminalLog it seems smb itself failed:
Aug 15 09:11:35 Thinkpad smbd[17311]: STATUS=daemon 'smbd' finished starting up
and ready to serve connections
Aug 15
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time
Also answered the askubuntu entry ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787800
Title:
Cannot execute Virsh command through SSH on Ubuntu 18.04
To manage notifications about this bug
Confirmed, but the sev is really low IMHO.
Thanks for the report thou - those things are missed too easily and for too
long.
** Changed in: virt-manager (Ubuntu)
Status: New => Confirmed
** Changed in: virt-manager (Ubuntu)
Importance: Undecided => Low
--
You received this bug
Hi Tung,
as other people have stated on [1] I first assumed that just the guest is
missing.
I tried to recreate with 18.04 and as expected found this:
ubuntu@node-horsea:~$ virsh dominfo c3
Id: 340
Name: c3
UUID: eac4d5b1-1503-43cd-8f6a-b89c1b04d794
OS Type:
I beg your pardon, it was released in 18.04 - why change the milestone
to 18.10?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692476
Title:
[18.04 FEAT]: qemu: Enable RDMA support in qemu
To
** Description changed:
[Impact]
- * backport upstream fix to avoid issues with newer kernels handling of
-getrandom calls
+ * backport upstream fix to avoid issues with newer kernels handling of
+ getrandom calls
- * The Bionic kernel itself doesn't have the changes yet that
701 - 800 of 10003 matches
Mail list logo
