Reproducer:
#!/bin/bash
device_to_disk () {
echo "$1" | \
sed 's:\(/dev/[a-z]\+\).*:\1:'
}
device_to_disk /dev/mapper/vgubuntu-root
So device_to_disk() is doing what it is supposed to do and there was NO
CHANGE to it (as it appears).
I guess using grub-install at /dev/vda was all
## SUMMARY OF THE ISSUE ##
After reading the grub-installer script, and following execution flow:
...
if [ "$found" = "0" ] && type lvdisplay >/dev/null 2>&1 && \
(lvdisplay "$disc_offered" | grep -q 'LV Name' 2>/dev/null || \
[ -e "$(dirname "$disc_offered")/control" ]); then
I've got 3 installation questions files:
1) LVM on top of /dev/vda[1] device (with failed grub-install run).
2) LVM on top of /dev/sda[1] device (without grub-install run).
3) LVM on top of /dev/sda[1] device (with successful grub-install run).
Differences between (1) and (2):
https://pastebin.u
Xenial is facing same/similar issue for qemu-user-static being installed
into LXD aarch64 (possibly for other arches as well).
The following NEW packages will be installed:
binfmt-support qemu-kvm qemu-user-static
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 56
For LXD case, having:
config:
boot.autostart: "false"
raw.lxc: |-
lxc.mount.auto = proc:rw
Might mitigate the issue, allowing /proc/sys/fs/binfmt_misc to be
updated by lxd container. Since this is not default, possible SRU would
be to detect lxd container in qemu-user-static installation
** Description changed:
[Impact]
* Cluster resource operation timeouts are not working correctly for
systemd resources and should be working. Timeouts are important in order
for the actions executed by pacemaker - for the systemd resource in
question - don't wait forever to start (or
@jason,
I could verify this SRU but I'll let you handle it as you were the
reporter. Could you please change tags from "needed" to "done" when
you're good ? This will sinalize the update can migrate from -proposed
to -updates.
Thanks again for reporting this!
-rafaeldtinoco
--
You received thi
The autopkgtests results above look like a regression in crmsh DEP8
because of some other change (an apt-cache | grep "Package" command is
not working for crmsh) and unrelated to this upload (as other tests have
passed).
--
You received this bug notification because you are a member of Ubuntu
Bug
I'm providing a PPA containing a full v4.6.0 fence_aws backport to
Ubuntu Focal fence-agents package at:
https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1894323-focal
with source at:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/fence-
agents/+git/fence-agents/+ref/lp1894323-fo
I'm also providing a PPA containing a full v4.6.0 fence_aws backport to
Ubuntu Bionic fence-agents package at:
https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1894323-bionic
with source at:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/fence-
agents/+git/fence-agents/+ref/lp189
** Changed in: fence-agents (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: fence-agents (Ubuntu Focal)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
(how to get fence_aws working with focal and aws <- keywords for google)
# Focal fence_aws tests without any backport (current version):
node 1: focal01
node 2: focal02
node 3: focal03
primitive fence-focal stonith:fence_aws \
params access_key= secret_key="" region=us-eas
Using my proposed new version:
$ dpkg -l | grep -i fence
ii fence-agents 4.5.2-1ubuntu1~202010091535 amd64
Fence Agents for Red Hat Cluster
[rafaeldtinoco@focal01 ~]$ crm status
Cluster Summary:
* Stack: corosync
* Current DC: focal03 (version 2.0.3-4
Moving on to Bionic backport now...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894323
Title:
Add fence_aws fencing from v4.6.0 agent to Bionic
To manage notifications about this bug go to:
http
(how to get fence_aws working with bionic and aws <- keywords for
google)
# Bionic fence_aws tests with the backport (from the ppa):
[rafaeldtinoco@bionic01 ~]$ crm status
Stack: corosync
Current DC: bionic01 (version 1.1.18-2b07d5c5a9) - partition with quorum
Last updated: Thu Oct 15 01:25:05 20
minor fix: "crm configure show" <- that would give us the cib in a human
readable way so we can reproduce with the same parameters.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900016
Title:
pgsql
Public bug reported:
After the SRU of LP: #1894323, it looks like a bad behavior in pacemaker
Bionic was exposed:
When declaring the fence_aws primitive, you can either declare it as a
single resource and describe the pcmk_host_map... OR you can declare one
fence resource PER NODE doing the exact
Everything is good and ready but I have discovered a small issue in the
Bionic Backport... and relates to:
https://access.redhat.com/solutions/4642491
The story is this: when declaring the fence_aws primitive, you can
either declare it as a single resource and describe the pcmk_host_map...
OR you
** Merge proposal unlinked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/fence-agents/+git/fence-agents/+merge/392432
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894323
Title:
Add
I'm pasting an email answer here so we keep track of all that has been
discussed for this issue:
> Me and Dan have been working recently on a customer case reported as
LP: #1915828. Turns out that some linker "magic" used inside libqb
broke pacemaker (and potentially any package using QB_LO
*** This bug is a duplicate of bug 1896223 ***
https://bugs.launchpad.net/bugs/1896223
** This bug has been marked a duplicate of bug 1896223
[FFe] this is the no-quorum-policy feature (specially for mssql sevrer)
--
You received this bug notification because you are a member of Ubuntu
Bu
This is the same as:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1890185
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896223
Title:
[FFe] this is the no-quorum-policy feature (special
* Post 2.0.4 feature backport: on-fail="demote" recovery policy (LP: #1896223)
debian/patches/ubuntu/lp1896223-*:
- [c4429d86e] Log: scheduler: downgrade "active on" messages to trace
- [01c5ec67e] Low: scheduler: match initial no-quorum-policy struct value to
- [015b5c012] Doc: Pacemaker E
Release team, I would like this to be an exception so I can add a new
feature to pacemaker: the on-fail="demote" recovery policy for the
pacemaker policy engine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
I'm now running all pacemaker cluster test suite on this pacemaker
(together with latest changes in all HA stack for Groovy). Will make
sure there are no regressions in this version AND this package will
continue being maintained by Ubuntu Server team.
--
You received this bug notification becaus
The feature was announced by the following e-mail:
Forwarded Message
Subject: [ClusterLabs] Coming in Pacemaker 2.0.5: on-fail=demote /
no-quorum-policy=demote
Date: Mon, 10 Aug 2020 11:47:24 -0500
From: Ken Gaillot
Reply-To: Cluster Labs - All topics related to open-source clu
Thanks a lot for catching up with this @mfo. And Richard for all the
tests.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895526
Title:
ocfs2 file system no longer write - "disk full" despite lots
In bug:
https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1894325
I have synced v4.6.0-1 recently from Debian, and it includes fence_aws
and fence_ibmz:
- fence_aws agent being backported to Bionic (LP: #1894323)
- Add LPAR fence agent to Pacemaker (LP: #1889070)
So in this bug we sho
Public bug reported:
In Bug:
https://bugs.launchpad.net/ubuntu/+source/cluster-glue/+bug/1895355
I have backported fixes and a new feature to cluster-glue:
# ec2 stonith agent support and fixes
7c84a6ae Fix EC2 stonith plugin
27e83692 Fix: stonith:ibmhmc: Add "managedsyspat" and "password" as
** No longer affects: fence-agents (Ubuntu Groovy)
** Also affects: fence-agents (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: fence-agents (Ubuntu Bionic)
Importance: Undecided => Wishlist
** Changed in: fence-agents (Ubuntu Focal)
Importance: Undecided => Wis
that should also be checked for backport
(backporting fence_ec2 to Focal and Bionic if possible).
I opened the following bug for this:
https://bugs.launchpad.net/ubuntu/+source/cluster-glue/+bug/1896696
** Changed in: fence-agents (Ubuntu Bionic)
Assignee: Rafael David Tinoco (rafaeldtinoco
** Merge proposal unlinked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/pacemaker/+git/pacemaker/+merge/391162
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896223
Title:
[FFe] thi
Summary
* Passed: iso8601- Invalid period - []
* Passed: iso8601- Invalid period - [2019-01-01 00:00:00Z]
* Passed: iso8601- Invalid period - [2019-01-01 00:00:00Z/]
* Passed: iso8601- Invalid period - [PT2S/P1M]
* Passed: iso8601- Invalid period - [2019-13-0
$ ./CTSlab.py --nodes "groovy01 groovy02 groovy03" --once --no-loop-tests
--no-unsafe-tests --outputfile ~/cts.log
Sep 24 04:40:29 BEGINNING 15 TESTS
Sep 24 04:40:29 Stack: corosync 2+ (crm-corosync)
Sep 24 04:40:29 Schema: pacemaker-3.0
Sep 24 04:
** Summary changed:
- [FFe] this is the no-quorum-policy feature (specially for mssql sevrer)
+ [FFe] this is the no-quorum-policy feature (specially for mssql server)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Changed in: open-iscsi (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892292
Title:
iscsi boot fails to boot i
** Changed in: multipath-tools (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891202
Title:
Multipathd hangs with l
All good with published package. Good to go.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Ubuntu HA wise:
I'm recommending all HA clusters to have the cluster interfaces
configured with systemd-networkd DIRECTLY instead of wrapping it through
netplan.io. At least until we're sure that HA has no issues with
netplan.io, having it configured directly will allow us to isolate
possible issu
This bug was serving me as a base to track tested fencing agents in
Bionic, Focal and Groovy. No more reason to keep it opened, closing it
as invalid.
** Changed in: fence-agents (Ubuntu Bionic)
Status: Confirmed => Invalid
** Changed in: fence-agents (Ubuntu Eoan)
Status: Won't Fix
I'm on it now...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881762
Title:
resource timeout not respecting units
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+
I'll provide a PPA with:
commit c9be5b271
Merge: 72a1f4834 08e3f7e44
Author: Ken Gaillot
Date: Fri Feb 21 14:57:57 2020
Merge pull request #1992 from kgaillot/times
Fix systemd support when using clock_gettime()
and
commit 8254f3d25
Merge: 0625eb1a2 71ae72df9
Author: Ken Gaillot
These are the patches being backported from upstream:
* Post 2.0.3 release fixes backported to Ubuntu: Fix resource timeout
functionality (LP: #1881762)
debian/patches/ubuntu-2.0.3-fixes/:
-
lp1881762-0001-e0e59163-Build-configure-remove-no-longer-needed-LIBADD_INTL-.patch
-
lp
** Description changed:
+ [Impact]
+
+ * Cluster resource timeouts are not working and should be working.
+ Timeouts are important in order for the actions (done for the resource)
+ don't timeout before we're expecting (sometimes starting a resource can
+ take more time than the default time bec
** Also affects: pacemaker (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: pacemaker (Ubuntu)
Status: Triaged => Fix Released
** Changed in: pacemaker (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: pacemaker (
** Description changed:
[Impact]
- * Cluster resource timeouts are not working and should be working.
- Timeouts are important in order for the actions (done for the resource)
+ * Cluster resource timeouts are not working and should be working.
+ Timeouts are important in order for the acti
** Summary changed:
- [FFe] this is the no-quorum-policy feature (specially for mssql server)
+ [FFe] no-quorum-policy=demote and on-fail=demote features for MSSQL servers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Hello,
Do you have any updates on this ?
Thank you
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881762
Title:
resource timeout not respecting units
To manage notifications about this bug go to:
** Summary changed:
- [FFe] no-quorum-policy=demote and on-fail=demote features for MSSQL servers
+ no-quorum-policy=demote and on-fail=demote features for MSSQL servers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
For the SRU reviewer:
I have uploaded the source code with the orig.tar.gz together (not sure
if this is a blocker as the package is waiting for approval in queue and
has not been rejected). Please find me on IRC so I can re-upload it if
needed.
Thank you!
** Description changed:
+ SRU reviewer
** Changed in: pacemaker (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: pacemaker (Ubuntu)
Importance: High => Undecided
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896223
Titl
I have just proposed a merge at:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/pacemaker/+git/pacemaker/+merge/391596
but first I need the SRU on:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1881762
to be accepted, so I can move with this feature merge.
Will run functio
SRU reviewer:
https://pastebin.ubuntu.com/p/rgVVb66xGd/
These are the regression tests results. All good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881762
Title:
resource timeout not respecti
SRU reviewer:
https://pastebin.ubuntu.com/p/PcZq7Hr3NQ/
These are the functional tests results.
There was an issue running one test, I had to re-ran, and it is all
good:
Oct 01 04:09:09 Running test SimulStop (focal02) [ 1]
Oct 01 04:09:24 Stopping Cluster Manager on all nodes
** Description changed:
- SRU reviewer:
-
- The merge request has been reviewed by @paelzer initially, before the
- SRU review. The most important comment is this:
-
-
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/pacemaker/+git/pacemaker/+merge/391398/comments/1030355
-
- Clarifyin
** Description changed:
[Impact]
- * Cluster resource timeouts are not working and should be working.
- Timeouts are important in order for the actions (done by the resource)
- don't timeout before we're expecting (sometimes starting a resource can
- take more time than the default time beca
After having my new fix (about to be uploaded):
[rafaeldtinoco@focal01 ~]$ crm status
Cluster Summary:
* Stack: corosync
* Current DC: focal01 (version 2.0.3-4b1f869f0f) - partition with quorum
* Last updated: Sun Oct 4 14:19:09 2020
* Last change: Sun Oct 4 14:19:07 2020 by root via ci
@racb could you, please, review it again for me ? I have done what we
agreed on.
Thanks a lot!
-rafaeldtinoco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881762
Title:
resource timeout not resp
[rafaeldtinoco@gitubuntu pacemaker]$ git push pkg --delete upload/2.0.3-3ubuntu4
To ssh://git.launchpad.net/ubuntu/+source/pacemaker
- [deleted] upload/2.0.3-3ubuntu4
[rafaeldtinoco@gitubuntu pacemaker]$ git tag -d upload/2.0.3-3ubuntu4
Deleted tag 'upload/2.0.3-3ubuntu4' (was 198170f
I had to do a new MP for LP: #1881762 (a more minimal approach) and,
with that, I'll need to rebase this one (and probably re-think it based
on conversations for that SRU). Doing that...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: pacemaker (Ubuntu Focal)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: pacemaker (Ubuntu Focal)
Importance: High => Undecided
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ects: iproute2 (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: iproute2 (Ubuntu Bionic)
Importance: Undecided
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: Confirmed
** Changed in: iproute2 (Ubuntu)
Status: New => Confirmed
** Also affec
Issues comes from:
(gdb) bt
#0 render (screen_width=144) at ss.c:1204
#1 main (argc=, argv=) at ss.c:4974
render (screen_width=144) at ss.c:1204
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/191318
workaround:
sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst
127.0.0.1 | cat -
by not trying to control terminal WIDTH, segfault does not occur.
** Changed in: iproute2 (Ubuntu Bionic)
Importance: Undecided => Low
--
You received this bug notification because you are a membe
It only affects Bionic:
[rafaeldtinoco@iproute2issue iproute2]$ git describe
eb8559eff124221bfbafe934c4dbfe30f20604c0
v4.15.0-103-geb8559ef
[rafaeldtinoco@iproute2issue ~]$ rmadison iproute2
iproute2 | 3.12.0-2 | trusty | source
iproute2 | 3.12.0-2ubuntu1.2
[rafaeldtinoco@iproute2issue iproute2]$ git unfixed
eb8559eff124221bfbafe934c4dbfe30f20604c0 is the first bad commit
commit eb8559eff124221bfbafe934c4dbfe30f20604c0
Author: Jean-Philippe Brucker
Date: Sat Mar 3 16:59:44 2018 +
ss: fix NULL dereference when rendering without header
MP:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/iproute2/+git/iproute2/+merge/396921
PPA: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1913187
** Description changed:
+ [Impact]
+
+ * The ss tool crashes when a query returns no results (seg fault)
+
+ [Test Case]
+
+
$ git-ubuntu tag --upload
$ git describe
upload/4.15.0-2ubuntu1.3
$ git push pkg upload/4.15.0-2ubuntu1.3
Counting objects: 11, done.
Delta compression using up to 24 threads.
Compressing objects: 100% (11/11), done.
Writing objects: 100% (11/11), 2.07 KiB | 176.00 KiB/s, done.
Total 11 (delta 7)
o
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
** Changed in: iproute2 (Ubuntu Bionic)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of
systemd (udev) is fixed for Groovy:
systemd (245.6-1ubuntu1) groovy; urgency=medium
[ Ryan Harper ]
* Skip over by-uuid/by-label symlinks for bcache backing and cache devices (LP:
#1861941)
File: debian/patches/lp1861941-dont-generate-disk-byuuid-for-bcache-uuid.patch
https://git.launchpad.
** Merge proposal unlinked:
https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/+git/systemd/+merge/387991
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885755
Title:
test-cap-li
BUG: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1861941
TESTCASE: https://paste.ubuntu.com/p/37KGy2Smnp/
PPA: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1861941
BCACHE-TOOLS:
GROOVY: https://tinyurl.com/yxonp5hz
FOCAL: https://tinyurl.com/y3tbd3un
SYSTEMD-UDEV:
GROOVY: p
Just spoke to @ddstreet about the SYSTEMD-UDEV merges. We are discussing
if we should keep the udev delta (from upstream) or not, considering
that the issue will be already fixed by bcache-tools and udev change
would only serve not to have backing devices at /dev/disk/by-uuid and
/dev/disk/by-label
** Merge proposal unlinked:
https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/+git/systemd/+merge/387991
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861941
Title:
bcache by-u
CURRENT STATUS
Targets:
- I: ceph-iscsi
- II: targetcli-fb
Summary for the current state:
I: ceph-iscsi
[-] MIR ack (if everything else is)
I/II: python-configshell-fb (linux-blocks-teams) - DONE
[.] MIR ack
[.] Security ack - needs DEP8 inclusion
For Debian, Suggested:
-
SUMMARY:
BUG: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1861941
TESTCASE: https://paste.ubuntu.com/p/37KGy2Smnp/
PPA: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1861941
BCACHE-TOOLS:
GROOVY: https://tinyurl.com/yxonp5hz (needs-review for an upload)
FOCAL: https://tinyurl
Very nice catch @mfo,
I'm sorry to have introduced this issue and I'm glad you found it.
Thanks for sharing. I'm +1 on both uploads to fix the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/188
** Project changed: intel => ubuntu
** No longer affects: ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889172
Title:
upgrade ndctl v69
To manage notifications about this bug go to:
https:
qemu (1:5.0-5ubuntu3) groovy; urgency=medium
has the merge with this fix:
- linux-user-add-netlink-RTM_SETLINK-command.patch (Closes: #964289)
** Changed in: qemu (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** Also affects: sysstat (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: sysstat (Ubuntu Focal)
Importance: Undecided
Status: New
** No longer affects: sysstat (Ubuntu Groovy)
** Changed in: sysstat (Ubuntu)
Importance: Undecided => Low
** Changed in: s
** Description changed:
- See https://bugs.php.net/bug.php?id=79013 for this exact issue.
+ [Impact]
- Upgrading Ubuntu's supported PHP version to 7.4.4 *should* fix the
- issue, or backporting the patch in the link I included.
+ * PHP7.4.3 has an issue with cURL where it is defaulting to chun
" Fixed as of the upcoming 5.7.27, 8.0.17 release, and here's the
changelog entry "
So, judging by:
mysql-server | 5.7.31-0ubuntu0.18.04.1 | bionic-updates | all
and
mysql-server | 8.0.20-0ubuntu0.19.10.1 | eoan-updates | all
and
mysql-server | 8.0.21-0ubuntu0.20.04.3 | focal-update
** Description changed:
+
+ SRU TEAM REVIEWER: This has already been SRUed for Focal, Eoan and Bionic.
Unfortunately the Bionic SRU did not work and we had to reverse the change.
Since then we had another update and now I'm retrying the SRU.
+
+ After discussing with @paelzer (and @dannf as a
** Changed in: net-snmp (Ubuntu)
Status: In Progress => 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/1855943
Title:
net-snmp merge for focal (v5.8)
To manage notifications abou
*** This bug is a duplicate of bug 1871129 ***
https://bugs.launchpad.net/bugs/1871129
** This bug is no longer a duplicate of bug 1871240
Can't upgrade to Focal on WSL1 due to libc6 postinst
** This bug has been marked a duplicate of bug 1871129
htop is blank when using in focal in wsl1
*** This bug is a duplicate of bug 1871129 ***
https://bugs.launchpad.net/bugs/1871129
** This bug is no longer a duplicate of bug 1871240
Can't upgrade to Focal on WSL1 due to libc6 postinst
** This bug has been marked a duplicate of bug 1871129
htop is blank when using in focal in wsl1
** Changed in: ubuntuwsl
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871129
Title:
htop is blank when using in focal in w
*** This bug is a duplicate of bug 1871129 ***
https://bugs.launchpad.net/bugs/1871129
** This bug is no longer a duplicate of bug 1871240
Can't upgrade to Focal on WSL1 due to libc6 postinst
** This bug has been marked a duplicate of bug 1871129
htop is blank when using in focal in wsl1
*** This bug is a duplicate of bug 1871129 ***
https://bugs.launchpad.net/bugs/1871129
** This bug is no longer a duplicate of bug 1871240
Can't upgrade to Focal on WSL1 due to libc6 postinst
** This bug has been marked a duplicate of bug 1871129
htop is blank when using in focal in wsl1
*** This bug is a duplicate of bug 1871129 ***
https://bugs.launchpad.net/bugs/1871129
** This bug is no longer a duplicate of bug 1871240
Can't upgrade to Focal on WSL1 due to libc6 postinst
** This bug has been marked a duplicate of bug 1871129
htop is blank when using in focal in wsl1
*** This bug is a duplicate of bug 1871129 ***
https://bugs.launchpad.net/bugs/1871129
** This bug is no longer a duplicate of bug 1871240
Can't upgrade to Focal on WSL1 due to libc6 postinst
** This bug has been marked a duplicate of bug 1871129
htop is blank when using in focal in wsl1
*** This bug is a duplicate of bug 1871129 ***
https://bugs.launchpad.net/bugs/1871129
** This bug is no longer a duplicate of bug 1871240
Can't upgrade to Focal on WSL1 due to libc6 postinst
** This bug has been marked a duplicate of bug 1871129
htop is blank when using in focal in wsl1
*** This bug is a duplicate of bug 1871129 ***
https://bugs.launchpad.net/bugs/1871129
** This bug is no longer a duplicate of bug 1871240
Can't upgrade to Focal on WSL1 due to libc6 postinst
** This bug has been marked a duplicate of bug 1871129
htop is blank when using in focal in wsl1
*** This bug is a duplicate of bug 1871129 ***
https://bugs.launchpad.net/bugs/1871129
** This bug is no longer a duplicate of bug 1871240
Can't upgrade to Focal on WSL1 due to libc6 postinst
** This bug has been marked a duplicate of bug 1871129
htop is blank when using in focal in wsl1
*** This bug is a duplicate of bug 1871129 ***
https://bugs.launchpad.net/bugs/1871129
** This bug is no longer a duplicate of bug 1871240
Can't upgrade to Focal on WSL1 due to libc6 postinst
** This bug has been marked a duplicate of bug 1871129
htop is blank when using in focal in wsl1
*** This bug is a duplicate of bug 1871129 ***
https://bugs.launchpad.net/bugs/1871129
Yes! Sorry, I forgot to update this, I had provided a temporary PPA:
https://github.com/microsoft/WSL/issues/5125#issuecomment-619350931
and it seems that people were using it for some time now. Mentioning
*** This bug is a duplicate of bug 1871129 ***
https://bugs.launchpad.net/bugs/1871129
** This bug is no longer a duplicate of bug 1871240
Can't upgrade to Focal on WSL1 due to libc6 postinst
** This bug has been marked a duplicate of bug 1871129
htop is blank when using in focal in wsl1
I just pushed/uploaded a SRU for bionic from:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/qemu/+git/qemu/+merge/387269
Waiting for SRU on it.
** Changed in: qemu (Ubuntu Bionic)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this
** Also affects: sssd (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: sssd (Ubuntu Focal)
Status: New => Triaged
** Changed in: sssd (Ubuntu)
Status: New => Triaged
** Changed in: sssd (Ubuntu)
Importance: Undecided => Medium
** Changed in: sssd (Ubunt
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
This bug is present in Debian as well and Ubuntu currently does not make any
changes to the Debian package. Therefore, this bug would be best fixed
directly in Debian, and then Ubuntu will pick up the fix automatic
701 - 800 of 2815 matches
Mail list logo
