FYI on status - the upload with the fix is complete, yet it is atm blocked to
migrate to the archive by a component mismatch.
I have pinged the related MIR request and hope this gets resolved soon.
If not - given some time - I'll upload with the respective tool disabled, so it
can migrate.
--
Thanks for your bump on this skomma!
>From my reading this fell dormant as there was no good insight how to
reproduce this for the people that could add the fix to the package.
Might you be able to provide some steps how to recreate this to test and
verify the fix as this is part of the SRU
Hi,
thanks Jan for the patch!
As note to the bug - in the packaging the patch is against
./plugins/node.d/mysql_.in, so it should become a quilt patch.
I checked the latest packaged version which is 2.0.30-1 which still does
not have the fix.
Although upstream that file is
So Hanns,
do you have other related apparmor Denies in your dmesg?
Also if possible could you attach a copy of your upgrade related logs?
You should be able to use this after your failed upgrade to do so:
$ apport-bug 1594902
--
You received this bug notification because you are a member of
Actually invalid matches the case better, so I chose that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1657733
Title:
KVM module handling different per Architecture - s390x
To manage
Thanks Tim, if that was the case it is fine IMHO.
I neither need nor want to overrule them - it is good to have the bug
thou as a document hopefully somebody will remember or a search engine
will find next time the question comes up.
Therefore setting to Won't Fix.
** Changed in: linux (Ubuntu)
Hi,
from the log
mysql_upgrade: Got error: 2002: Can't connect to local MySQL server through
socket '/var/run/mysqld/mysqld.sock' (2) while connecting to the MySQL server
Upgrade process encountered error and will not continue.
mysql_upgrade failed with exit status 11
That means the server did
Interesting - I found more similar reports which rises the chance that
something is odd not that much tied to your personal setup.
I dupped it onto this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1658067 ***
https://bugs.launchpad.net/bugs/1658067
** This bug has been marked a duplicate of bug 1658067
package mysql-server-5.7 5.7.17-0ubuntu0.16.04.1 failed to install/upgrade:
subprocess installed post-installation script returned error exit
Hi,
thank you for your report and your help to make Ubuntu better!
We build with libnuma-dev which should auto-enable
https://bugs.mysql.com/bug.php?id=72811.
Might I ask you to describe what effect you see by this missing (other
than the Denie in the log) - just to help rating the importance
@Nish - you have the apache2 merge assigned this cycle - what do you
think?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658469
Title:
mod_http2 is not available under Apache 2.4.23 / Ubuntu
Hi Dino99,
I'm not sure I could follow all comments in this bug 100%, so I want to check
for confirmation - would it be appropriate to Dup this bug onto bug 1639962 as
well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
on an upgrade it tries to ensure that the internal DB structures are up to date.
Doing so processes the schema of all tables.
In your case I see in the log:
Repairing tables
performance_schema_o.cond_instances
Error: Table 'performance_schema_o.cond_instances' doesn't exist
status :
Looking at the Vcs git that is listed I see that the change came in with
Debians 5.6.14+dfsg-1.
(https://anonscm.debian.org/git/pkg-mysql/mysql.git)
That means the individual fix is in the past and can't be found in that repo.
But even checking for the past of this in
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
FYI - upstream fix 44f79a0b
Author: Daniel P. Berrange
lxc: ensure libvirt_lxc and qemu-nbd move into systemd machine slice
Should be fixed completely when merging libvirt >=3.0
It seems no one bothered for quite a while - so I keep low prio.
The tests that trigger that
*** This bug is a duplicate of bug 1639962 ***
https://bugs.launchpad.net/bugs/1639962
Already handled as part of the merge in bug 1639962
** This bug has been marked a duplicate of bug 1639962
smbd crashed on startup with newest libtevent
--
You received this bug notification because
Hi,
Hans is right it needs a merge but there is already one working on it -
subscribing Nish so he can dup this onto the merge bug if existing or reuse
this one as merge bug.
@Nish - I saw you assigning yourself on similar bugs like 1639962 so I
assigned you here to allow you to handle it
Hi Mike,
thanks for the report.
Let us try to sort it out what exactly your issue is and where it came from.
To sort out the delta I'd recommend
git+ssh://git.launchpad.net/~libvirt-maintainers/ubuntu/+source/libvirt
There you see it split even better than in debdiffs.
.7 upcoming and not
"Automatic provisioning tools usually waits for SSH to answer at the TCP
level and then expect things to work from here."
I'll let Scott handle the details, but as he mentioned by design runcmd
or user scripts run afterward anyway. To make sure that cloud-init
really is complete I happen to check
** Summary changed:
- package mysql-server-5.7 5.7.17-0ubuntu0.16.04.1 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 1
+ mysql_upgrade: Got error: 2002: Can't connect to local MySQL server through
socket '/var/run/mysqld/mysqld.sock'
**
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
for the required DB updates along a package update it uses the local socket.
In the log I've found:
2017-01-22T13:34:46.779325Z 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.7.16-0ubuntu0.16.10.1'
Hi,
the auto-generated log does contain too much information in regard to the issue.
What I see is:
Setting up docker.io (1.12.3-0ubuntu4~16.04.2) ...
Adding group `docker' (GID 134) ...
Done.
Job for docker.service failed because the control process exited with error
code. See "systemctl status
Hi,
in the log I've seen:
2017-01-15T18:31:03.674750Z 0 [Warning] TIMESTAMP with implicit DEFAULT value
is deprecated. Please use --explicit_defaults_for_timestamp server option (see
documentation for more details).
2017-01-15T18:31:28.754081Z 0 [Warning] InnoDB: 1048576 bytes should have been
Hi,
it is sad to hear that you never got it working to share files with your
windows systems.
As a side note - for whatever it might be worth to you - this simple guide
worked for me https://help.ubuntu.com/lts/serverguide/samba-fileserver.html
Now to the issue you see here.
This samba failing
*** This bug is a duplicate of bug 1658478 ***
https://bugs.launchpad.net/bugs/1658478
>From the log:
Version: '5.7.16-0ubuntu0.16.04.1' socket: '/var/run/mysqld/mysqld.sock'
port: 3306 (Ubuntu)
2017-01-22T09:32:58.158535Z 2 [Note] Access denied for user 'root'@'localhost'
(using
*** This bug is a duplicate of bug 1658067 ***
https://bugs.launchpad.net/bugs/1658067
You'r assumption is correct - there were a few more of those reports, so
Dup'ing onto just one
** This bug has been marked a duplicate of bug 1658067
mysql_upgrade: Got error: 2002: Can't connect to
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
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
Just to confirm - On install it usually asks you to set a mysql root
password (not mandatory) - did you set one?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658478
Title:
on-upgrade Access
*** This bug is a duplicate of bug 1658067 ***
https://bugs.launchpad.net/bugs/1658067
You'r assumption is correct - there were a few more of those reports, so
Dup'ing onto just one
** This bug has been marked a duplicate of bug 1658067
on-upgrade 2002: Can't connect to local MySQL server
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,
it seems that apache fails on restart after upgrade while initializing mod-php.
Setting up libapache2-mod-php7.0 (7.0.13-0ubuntu0.16.04.1) ...
Replacing config file /etc/php/7.0/apache2/php.ini with new version
Module mpm_event disabled.
Enabling module mpm_prefork.
apache2_switch_mpm Switch
Hi,
sorry but the log holds not enough information to pinpoint the issue.
In general you can try to do a reinstall to clean it up like described (for
another package) here:
http://askubuntu.com/questions/490671/fix-half-installed-package
Other than that also "Ubuntu 15.10 "Wily Werewolf" is no
Hi,
thank you for your report and your help to make Ubuntu better.
I came by trying to triage this bug, but since this more or less starts
with a question on the reasoning of changes to mysql packaging "Are
there any reasons why this has been removed in 1604 : chmod 2750
/var/log/mysql ?" I
Hi James,
thank your for your report and your help to make Ubuntu better.
These are essentially two issues in one.
For the first being "fail sasl+pam" - would you have some steps to reproduce
the issue.
At least I must admit I never set them up, and others coming by to help might
as well.
So if
Hi Simon,
thank you for your report as always!
You reported this against Trusty - I'd expect so, but do you happen to
know right away if this affects Xenial and Zesty as well?
AFAIK these rules are added by "add_file_path" depending on the flag as r or rw.
This is iterated by
Thanks Dino99 for your report.
I'm linkin in the related Debian und Upstream bugs.
Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840298
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840382
=> Fixed in move to 4.4.6
Upstream:
https://bugzilla.samba.org/show_bug.cgi?id=12283
@Lars & Robie - there was a flurry of mysql upgrade issues in the recent days.
I was able to identify two different behaviours and dupp'ed all others.
Subscribing you two for a deeper though on it while waiting for the reporters
to share more on their setup.
--
You received this bug
*** This bug is a duplicate of bug 1592669 ***
https://bugs.launchpad.net/bugs/1592669
@Lars & Robie - there was a flurry of mysql upgrade issues in the recent days.
I was able to identify two different behaviours and dupp'ed all others.
Subscribing you two for a deeper though on it while
Ping - we have the next fix for Xenial in the queue - all others are
released now, has this one "baked" enough for Xenial SRU to migrate?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626972
Title:
On Tue, Jan 24, 2017 at 1:52 AM, Rafael David Tinoco <
rafael.tin...@canonical.com> wrote:
> Christian, could you please move Xenial for me ? I have some
> end users waiting for this. Thank you very much.
>
I can't - IIRC that is up to the SRU Team, I pinged the #ubuntu-release
channel if one
FYI Merging latest for new Dev release as usual.
Since there was no further feedback on these issues with 16.04 and given that
MLX DPDK build is a known PITA wit hits dependency to MLX instead of
openfabrics libibverbs setting this to incomplete now to have a chance to time
out.
** Changed in:
FYI - merge for Zesty in progress and 4.88 contains a fix as listed by Andreas
Metzler.
Subscribing Security Team to consider security SRUs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580454
FYI - merge for zesty in progress - thanks for the Info.
Subscribing the security Team for their consideration on security SRU updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654750
Title:
Thanks Thomas to reassign so I finally got aware of this.
At least I can confirm the issue on Xenial:
qemu at version 1:2.5+dfsg-5ubuntu10.6
sudo qemu-debootstrap --no-check-gpg --arch=sparc64 sid sparc64
http://ftp.debian-ports.org/debian
[...]
I: Running command: chroot sparc64
As I expected this is not very "exclusive" linking in the Debian bug
** Bug watch added: Debian Bug tracker #828041
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828041
** Also affects: qemu (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828041
Importance: Unknown
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
** Changed in: qemu (Ubuntu)
Importance: Undecided => Low
** No longer affects: qemu-linaro (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OTOH the kernel patch is much much smaller:
$ git show 7cc851039d643a2ee7df4d18177150f2c3a484f5 | diffstat
prom_init.c |1 +
1 file changed, 1 insertion(+)
See
https://github.com/torvalds/linux/commit/7cc851039d643a2ee7df4d18177150f2c3a484f5
IMHO I'd almost expect to only SRU the kernel
The Qemu patches are only ppc, which leaves some hope that the potential
to affect other architectures should be minimal :-)
$ git show 7386ae6372cc07c77a39cb 8cd2ce7aaa3c3fadc561f4 52b2519c4ea9a6aa4df7ab
eac4fba965136f61cc239a b30ff227c27c931155f768 | diffstat
hw/ppc/spapr_hcall.c|
Hi,
thank you lagarcia for your expertise on this.
I try to summarize how I understand the last post - please correct me if
I'm wrong.
1. on POWER8NVL "Xenial qemu" in host and "Xenials kernel" in the guest
fail (that is the bug)
2. on POWER8NVL "Xenial qemu + the fixes" in host and "Xenial
For now I have prepared a qemu ppa to allow the reporter more testing.
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2409/
That has the mentioned pactches on top of Xenial qemu and should allow
to test case #2 of my list above.
--
You received this bug notification because you are
Thank you Simon,
since this is "only" about silencing a warning it wasn't worth an SRU in my
personal opinion.
I can consider to wrap it up in another SRU thou and let the SRU Team decide.
The "impact" of warnigns might be too low, but OTOH the regression potential is
as well and Xenial will be
On Mon, Jan 30, 2017 at 3:38 PM, Mike Rushton
wrote:
> @Christian The branch is for a fix in the plainbox-provider-checkbox
> package which is part of the certification suite
>
@Mike - sure I saw what it patche :-)
I wanted a clarification if this cancels the
@Mike - is the branch you linked meant to augment or to replace the
suggested SRU (which should be tested from the ppa I linked)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656112
Title:
Power
For now setting to imcomplete to reflect that no one can really work on
it until more data was provided.
** Changed in: qemu (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi vishal,
these days - even more when this was reported - I'd recommend a newer DPDK.
In Zesty proposed you can find 16.11 in Yakkety the latest stable release being
16.07.2.
The same applies if you compile yourself - so might I ask are you also seeing
this with a recent DPDK version?
TL;DR
Hi Jason,
thanks for the report.
FYI - we discussed on that last week and what to debug next time we hit
it.
We can't do much yet - for now this report is meant to be a focal point
that others can find if they run into the same.
--
You received this bug notification because you are a member of
Documenting my brainstorm list of things to check next time here:
This might not be perfect solution, but a start.
It is just what came to my mind and might be incomplete.
0. always report the /var/log/libvirt/qemu/guestname.log so one can consider
the timing
0. also include the guest xml
Hi,
to confirm that is patch "virsh: host: Use bitmap size in bytes rather than bit
count" right?
Assuming that I'm setting all >=Yakkety to fix Released as that was in
anything >= v1.3.4
Am I correct that you hereby requested a Xenial SRU for this fix?
** Also affects: libvirt (Ubuntu Xenial)
Hi Thiago,
sorry the size of the last update was rather huge.
Re-quoting the TL;DR section of it to make sure you see the status update -
read the full comment for details:
TL;DR: working for me, please help understanding your issue by:
1. share your network configuration xmls
2. Try with a
Since release is correctly in queue but blocked due to the component
mismatch for now setting back from released to committed to reflect
that.
** Changed in: dpdk (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: qemu (Ubuntu Yakkety)
Status: Confirmed => In Progress
** Changed in: qemu (Ubuntu Xenial)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Note: Add "tgt" to the list of packages that disable a feature because
it is waiting for this MIR.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1274247
Title:
[MIR] Glusterfs
To manage
FYI 10.7 migrated a few minutes ago, the SRU Team can now evaluate your
fix to move it to proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656480
Title:
QEMU Does not Send L2 Broadcasts
I tried to recreate.
Note: as it was reported on power + Xenial this test was done on ppc64el Xenial
as of today
To do so with as much debugging as possible I created a normal Xenial KVM Guest
via
$ uvt-kvm create --cpu 4 --password=ubuntu paelzer-testlvm-xenial release=xenial
Then I added a
Hi,
as usual bugproxy accumulated a lot of info to go through.
I'll try to summarize - please feel free to correct - "VG/LV are not available
in /dev/mapper/ after reboot".
Would that be a proper (and simpler) definition of the issue?
** Summary changed:
-
Internal: for anyone else debugging on this, the mentioned test setup is
on Diamond in guest "paelzer-testlvm-xenial"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1657646
Title:
VG/LV are not
Just learned that SRU for that would be more ok than I expected, quoting the
SRU policy:
"For Long Term Support releases we regularly want to enable new hardware. Such
changes are appropriate provided that we can ensure not to affect upgrades on
existing hardware."
That said waiting for
Nish, do you have any newer update on the progress 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/1578600
Title:
Multiple connections to Interbase with php 7.0 are not allowed
To manage
Thank you Simon and Kees,
I personally would not want it allowed in my base profile - but I'll leave that
for the other bug to decide.
We certainly can consider adding it to mysql together with the others.
I feel relieved that the impact seems low, but OTOH that means it likely boils
down to a
/me is ignoring any irony for now
Joshua just finally cleaned and handled a lot of bugs that were missed to have
taken care of - thank you for that.
That said if you come by hundreds of similar issues sometimes answers become
rather short.
And IMHO most of the time people don't even care as
Huh - why doesn't it take my Yakkety task.
If a driver comes by accepting it - the Yakkety task should be Triaged High.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/165
Title:
invoke-rc.d
Thanks for your update Artur!
Flagging status correctly so that it is clear this can be fixed with a merge
and what can be considered for an SRU later on.
** Also affects: init-system-helpers (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848861
Importance: Unknown
*** This bug is a duplicate of bug 165 ***
https://bugs.launchpad.net/bugs/165
** This bug is no longer a duplicate of bug 1639823
package ipmiutil 3.0.0-1 failed to install/upgrade: subprocess installed
post-installation script returned error exit status 1
** This bug has been
*** This bug is a duplicate of bug 165 ***
https://bugs.launchpad.net/bugs/165
** This bug has been marked a duplicate of bug 165
invoke-rc.d starts disabled systemd service if there are init scripts
--
You received this bug notification because you are a member of Ubuntu
In fact I see that:
ipmiutil | 3.0.1-1 | zesty-proposed/universe
** Changed in: ipmiutil (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/165
*** This bug is a duplicate of bug 165 ***
https://bugs.launchpad.net/bugs/165
** This bug is no longer a duplicate of bug 1639823
package ipmiutil 3.0.0-1 failed to install/upgrade: subprocess installed
post-installation script returned error exit status 1
** This bug has been
*** This bug is a duplicate of bug 165 ***
https://bugs.launchpad.net/bugs/165
** This bug is no longer a duplicate of bug 1639823
package ipmiutil 3.0.0-1 failed to install/upgrade: subprocess installed
post-installation script returned error exit status 1
** This bug has been
If you want to start on this one to help you a bit more for complex
merges I'd highly recommend (in fact I use it even for trivial ones) to
follow https://wiki.ubuntu.com/UbuntuDevelopment/Merging/GitWorkflow
Seems somewhat doable:
git diff old/debian | diffstat
changelog
Thank you for taking the time to report this bug and helping to make
Ubuntu better. I appreciate the quality of this bug report and I'm sure
it'll be helpful to others experiencing the same issue.
I happend to find plugins for docker and lxd which should add some info:
sos/plugins/docker.py
@racb - I know you are on the squid merge - have you (or could you) have
a look at the packaging/generating of this file on the current version
you prepare?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for your report - this seems to be an undying issue.
See
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1005257
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1053682
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/117
Hi N-Ronny,
I have never debugged openvpn/pam in that regard myself.
But I hapened to find https://github.com/Yubico/yubico-pam/issues/26 which made
me wonder.
The version is clearly older.
Now both (the yubico.so and openvpn) are build with -fstack-protector and
-fstack-protector-strong.
Once your issue hopefully is resolved we can rename this into "improve
concurrent tomcat installationa and apport reports" and go on with these
efforts. Well we could also split that in another bug if needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Subscribing Server team as:
1. I wonder if we should have a postinst check for concurrent tomcat start
issues based on that.
2. catalina.out should be collected by apport
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
thanks for your report and your help to make Ubuntu better!
The automatically attached logs only state that:
Creating config file /etc/logrotate.d/tomcat7 with new version
Job for tomcat7.service failed because the control process exited with error
code. See "systemctl status
Hi,
thank you for your report and your help to make Ubuntu better!
I checked Xenial and it was fine for tomcat7 and 8 already containing
that change.
That came in via 7.0.72-2.
It was also that way back in time at 7.0.14-1
I found what changed it for Trusty:
7.0.52-1ubuntu0.8 driven by Marc
** Changed in: qemu (Ubuntu)
Status: New => Triaged
** Changed in: qemu (Ubuntu Xenial)
Status: New => Triaged
** Changed in: qemu (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: qemu (Ubuntu)
Importance: Undecided => High
--
You received this bug
I picked up a report today on IRC which I wanted to discuss here with
the audience that created the change.
The report was that with 16.04.2 the libvirt user now shows up on e.g.
gdm dropdown when selecting users.
I thought it filters system users, but then --system (=get a low number) and
Also an ack from Debian and a release into Debian unstable.
Could one look into sponsoring fix-1664478-pg-repack-testcase.debdiff into
Yakkety (MOTU).
** Changed in: pg-repack (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of
A few of the flaky tests show up as expected, and one that might need an extra
look at "mimeo" fails on arm due to newpid.
Nish and I will (re-)test some and if needed evaluate that and come back here
with a v-done after that.
--
You received this bug notification because you are a member of
FYI - testing of the full chain T/X/Y/Z in proposed for verification is
in progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641532
Title:
machine-types trusty and utopic are not unique
Thanks for the Data Eric.
It confirms Ryans assumptions.
The ongoing I/O keeps the device queue with 50-70 Requests of 1MB size busy.
Any request from update-grub that enters has to go through that queue.
Which due to the load has 190+-20ms.
If now also the assumption on the barriers is true
Hi Rafael,
Not so important but FYI your link in the description is broken - it
leads me to some weird catching site, not really an emulatortalk.info
with some content.
I like your tests in #12 and #18, but can you think and compare several
permutations of commits to non-active layers? Those
There was a short "WTF" moment as it seems
https://launchpad.net/ubuntu/+source/libvirt/1.2.2-0ubuntu13.1.18 existed.
But it was only in proposed and got removed from there by inactivity to test
the case.
There is also https://launchpad.net/ubuntu/+source/libvirt/1.2.2-0ubuntu13.1.19
which
Hi,
the proxy did well at hiding your actual reply by quoting my full pust.
But since you asked for updates I have to kindly ask you instead -
please read my detailed repro approach in comment #5 (things just worked
for me).
It is ending with:
> Could you either
> 1. report your exact steps on
On Wed, Feb 22, 2017 at 3:53 PM, Ryan Harper <1666...@bugs.launchpad.net>
wrote:
> What sort of disks and connections are we talking about on the host? How
> are they attached? Is sda in any of the LVM groups?
> Any way we can get a sosreport from the host?
>
The function the upstream fix relates to in Openstack is:
def set_vif_host_backend_ethernet_config(conf, tapname):
"""Populate a LibvirtConfigGuestInterface instance
with host backend details for an externally configured
host device.
Before the change it was part of "get_config(self,
I'm going off some more testing with that in mind what I documented on
the bug already.
I really want to understand why it hits you now and if this is a SRU-
regression, so here some questions.
Questions to Logan:
- Could you share your guest XML to help me to understand what combination
drives
901 - 1000 of 5968 matches
Mail list logo