For the 2 fixes:
LP: #1437359
LP: #1677684
I have submitted to upstream the following merge request:
https://salsa.debian.org/ha-team/corosync/-/merge_requests/2
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs
** Description changed:
Together with fixes for:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684
This bug will also backport/cherrypick the following post release fixes:
- -> c631951e icmap: icmap_ini
** Description changed:
- Apart from fixes for:
+ Together with fixes for:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684
This bug will also backport/cherrypick the following post release fixes:
-> c
; efe48120 totemconfig: Free leaks found by coverity = fix
** Affects: corosync (Ubuntu)
Importance: High
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: Confirmed
** Changed in: corosync (Ubuntu)
Status: New => Confirmed
** Changed in: corosync (Ubuntu)
# verification with 5.3 kernel
(k)rafaeldtinoco@drbdtest01:~$ sudo dd if=/dev/zero of=/.loop bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 2.35899 s, 455 MB/s
(k)rafaeldtinoco@drbdtest01:~$ sudo losetup --find --show /.loop
/dev/loop0
(k)rafaeldti
# verification with 5.0 kernel
(k)rafaeldtinoco@drbdtest01:~$ sudo dd if=/dev/zero of=/.loop bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 2.25077 s, 477 MB/s
(k)rafaeldtinoco@drbdtest01:~$ sudo losetup --find --show /.loop
/dev/loop0
(k)rafaeldti
# verification with v4.15 kernel:
(k)rafaeldtinoco@drbdtest01:~$ sudo dd if=/dev/zero of=/.loop bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 2.25576 s, 476 MB/s
(k)rafaeldtinoco@drbdtest01:~$ sudo losetup --find --show /.loop
/dev/loop0
(k)rafa
$ dput ubuntu ../puppet_5.5.10-4ubuntu2_source.changes
Checking signature on .changes
gpg: ../puppet_5.5.10-4ubuntu2_source.changes: Valid signature from
A93E0E0AD83C0D0F
Checking signature on .dsc
gpg: ../puppet_5.5.10-4ubuntu2.dsc: Valid signature from A93E0E0AD83C0D0F
Uploading to ubuntu (via f
Sponsoring this after talking to @lucaskanashiro on IRC.
** Changed in: puppet (Ubuntu)
Status: New => In Progress
** Changed in: puppet (Ubuntu)
Importance: Undecided => Medium
** Changed in: puppet (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
pmod -a for the first time in recent
kernels (>= 5.3.x) (LP: #1864992)
* Removed --add-udeb from dh_makeshlibs, since libkmod2-udeb does not
actually contain a library. (Closes: #939779)
-- Rafael David Tinoco Wed, 11 Mar 2020
19:32:52 +
(k)rafaeldtinoco@ekmodissue:~$ apt-cach
. (Closes: #939779)
-- Rafael David Tinoco Wed, 11 Mar 2020
19:37:06 +
(k)rafaeldtinoco@bkmodissue:~$ apt-cache policy kmod
kmod:
Installed: 24-1ubuntu3.3
Candidate: 24-1ubuntu3.3
Version table:
*** 24-1ubuntu3.3 500
500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/ma
Questions:
- ndctl backport from Focal isn't really needed to build it (only a debhelper
version change)
- are there any missing features in Bionic ndctl that disallow ipctl to work
properly ?
- want me to provide a PPA for you to test it ?
** Changed in: ipmctl (Ubuntu)
Assignee: (un
** Changed in: ipmctl (Ubuntu)
Status: New => Triaged
** Changed in: ipmctl (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1868882
Title:
I believe the patch you're mentioning is worth backporting to Bionic and
Eoan is this:
$ git log -1 -p be65b26b67099be2b2b4890d736dbd1ad15adf36 | diffstat
include/seccomp-syscalls.h| 208 +-
src/arch-aarch64-syscalls.c | 35 ++-
src/arch-arm-sy
Could you provide a failing test case so we can base the SRU (stable
release update) on that use it as a non-regression test ?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1868720
Title:
kernels (>= 5.3.x) (LP: #1864992)
-- Rafael David Tinoco Thu, 12 Mar 2020 13:15:28
+
---
and it should have taken care of this issue.. checking the given
example:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/amd64/d/d
Thanks doko, focal was Fix Released for the original initramfs-tools,
iirc. That made me miss the fix for Focal. I'm applying the same fix
(Eoan/Bionic SRUs) to Focal.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://b
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1437359
Title:
A PIDFILE is double-defined for the corosync-notifyd init script
To manage notifications
I'm closing up corosync / corosync-* bugs for Focal and will check sysv
script tomorrow. For now, I can say that:
(c)rafaeldtinoco@clusterdev:~$ sudo systemctl status corosync-qdevice
● corosync-qdevice.service - Corosync Qdevice daemon
Loaded: loaded (/lib/systemd/system/corosync-qdevice.ser
Hello Bert,
We are not yet fully disabling sysv related scripts because there are
systems that are not, yet, using systemd. Not for this case, but, one of
these examples is windows WSL environment, where systemd is not
supported yet. Just wanted to mention this to show there are some other
things
Status: Triaged => Won't Fix
** Changed in: corosync (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: corosync (Ubuntu Precise)
Status: Incomplete => Won't Fix
** Changed in: corosync (Ubuntu)
Importance: High => Undecid
This issue still exists and should be fixed. I'm putting together with
some other SRUs so all of them are done at once. Thanks @niedbalski for
bringing up this issue. I'll fix Ubuntu Focal for now and try to get
along with the needed SRUs.
** Changed in: corosync (Ubuntu Trusty)
Assignee: Jor
(c)rafaeldtinoco@clusterdev:~/.../sources/ubuntu/corosync$ git diff HEAD
diff --git a/debian/corosync-notifyd.init b/debian/corosync-notifyd.init
index c908618..837e48a 100644
--- a/debian/corosync-notifyd.init
+++ b/debian/corosync-notifyd.init
@@ -21,7 +21,6 @@ NAME=corosync-notifyd
DAEMON=/usr/
** Also affects: corosync (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: corosync (Ubuntu Xenial)
Status: New => Incomplete
** Changed in: corosync (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a membe
Okay, this is a very simple fix but it is tricky... mainly because ..
possibly 99% of the users of this package are using systemd and the
corosync service unit file... which does not face this issue. I'm not
entirely sure a SRU is the right thing to do on all affected Ubuntu
versions (Xenial, Bioni
** Also affects: corosync (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: corosync (Ubuntu Focal)
Importance: Undecided
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: Triaged
** Also affects: corosync (Ubuntu Trusty)
Importance: Undecided
>From upstream documentation:
"""
Pacemaker used to obtain membership and quorum from a custom Corosync plugin.
This plugin also had the capability to start Pacemaker automatically when
Corosync was started. Neither behavior is possible with Corosync 2.0 and beyond
as support for plugins was re
** Also affects: corosync (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: corosync (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: corosync (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: corosync (Ubuntu Bionic)
reporting this.
** Changed in: corosync (Ubuntu)
Status: Triaged => Fix Released
** Changed in: corosync (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed t
** Also affects: corosync (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: corosync (Ubuntu Trusty)
Status: New => Incomplete
** Changed in: corosync (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: corosync (Ubuntu)
Assignee: Joao (nobrefr)
nged in: cluster-glue (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to cluster-glue in Ubuntu.
https://bugs.launchpad.net/bugs/1251298
Title:
Failed to sign on to LRMd wit
Correct flag for this bug is: Fix Released
per upstream fix:
commit d3b983953d43dd17162be04de405d223fb21cd26
Author: Angus Salkeld
Date: Wed Nov 24 14:35:56 2010 +1100
Add totem/interface/ttl config option.
This adds a per-interface config option to
adjust the TTL.
Signed-of
Currently we have:
if [ "$RUN_ARBITRATOR" != "yes" ]; then
log_warning_msg "To run $DESC, please set RUN_ARBITRATOR to
'yes' in /etc/default/booth"
log_end_msg 0
exit 0
fi
# in eoan:
rafaeldtinoco@workstation:~/.../debian/booth/d
Trying to hint this as a force-badtest in britney. Whenever this is
solved, please remove force-badtest.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1868108
Title:
[autopkgtest][focal] r
Upstream issue:
https://github.com/ruby-gnome/ruby-gnome/issues/1389
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1868108
Title:
[autopkgtest][focal] ruby-gnome/3.4.1-2build1
class:Tes
Public bug reported:
ruby-gnome/3.4.1-2* package fails with:
2020-03-19T13:29:50+00:00: Running test for
/tmp/autopkgtest.2iRDtE/build.GH8/src/webkit2-gtk
@rbasak,
## Before my package is installed:
$ dpkg -l drbd-utils | grep RAID
ii drbd-utils 8.9.10-2 amd64RAID 1 over TCP/IP for Linux (user
utilities)
$ sudo losetup --find --show /.loop
/dev/loop0
$ sudo drbdadm create-md r0
initializing activity log
NOT initializing bitmap
W
** Description changed:
OBS: I have split this bug into 2 bugs:
- fence-agents (this) and pacemaker (LP: #1866119)
SRU: fence-agents
[Impact]
* fence_scsi is not currently working in a share disk environment
* all clusters relying in fence_scsi and/or fence_scsi
** Description changed:
OBS: I have split this bug into 2 bugs:
- - fence-agents (this) and pacemaker (LP: #1866119)
+ - fence-agents (this) and pacemaker (LP: #1866119)
SRU: fence-agents
[Impact]
* fence_scsi is not currently working in a share disk environment
I'm flagging this as won't fix because of LP: #1864992. Focal has been
merged with 0.136ubuntu1 containing this "fix". Eoan and Bionic will not
face this issue with fix for LP: #1864992.
** Changed in: initramfs-tools (Ubuntu Eoan)
Status: In Progress => Won't Fix
** Changed in: initramfs-
Testing Bionic kernel with the initial situation the bug being dropped
said to fix:
(k)rafaeldtinoco@bkmodissue:~$ sudo rm
/lib/modules/4.15.0-91-generic/modules.builtin.bin
(k)rafaeldtinoco@bkmodissue:~$ sudo depmod -a -F
/boot/System.map-4.15.0-91-generic
ok
(k)rafaeldtinoco@bkmodissue:.../4
** Description changed:
+ [Impact]
+
+ * There is no impact to the end user but spurious error messages (tons
+ of them) causing the perception that something really bad happened:
+
+ Example of one of those tons of messages:
+
+ depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() cou
Testing Bionic kernel with the initial situation the bug being dropped
said to fix:
(k)rafaeldtinoco@bkmodissue:~$ sudo rm
/lib/modules/4.15.0-91-generic/modules.builtin.bin
(k)rafaeldtinoco@bkmodissue:~$ sudo depmod -a -F
/boot/System.map-4.15.0-91-generic
(k)rafaeldtinoco@bkmodissue:~$ sudo rm
I have created a PPA for this issue:
https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1864992
Please provide feedback if possible. I haven't done Focal yet because
git-ubuntu is facing a small problem importing latest focal source
package to do the merge.. will check it tomorrow.
--
You r
@cascardo did a MR for focal and added you as a reviewer. will do the
other MR for eoan and bionic now.
** No longer affects: curtin
** No longer affects: subiquity
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bu
Reason for keeping verbose_missing_bin patch was because of test case
described at:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684901
(k)root@fkmodissue:.../5.4.0-18-generic$ sudo mv modules.alias.bin
modules.alias.bin.old
(k)root@fkmodissue:.../5.4.0-18-generic$ sudo modprobe hehe
modpro
** Also affects: initramfs-tools (Ubuntu Focal)
Importance: Medium
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: Fix Released
** Changed in: initramfs-tools (Ubuntu Eoan)
Status: New => In Progress
** Changed in: initramfs-tools (Ubuntu Bionic)
Status:
** Also affects: kmod (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: kmod (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: kmod (Ubuntu Focal)
Importance: Medium
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: In
Sorry @cascardo, forgot to update there. I'll revert half of Debian
patch... (the could not open builtin file).. turning it back to DBG()
only message. This "fixes" the issue. We can solve implement whatever
Debian decides later.. but getting rid of those messages now is good or
we will have many b
@cascardo brought to us that there is on-going discussion about this in:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948257#95
which I missed...
Debian has this patch:
+ debian/patches/verbose_missing_bin
Description: Report an error when some .bin files do not exist
Author: Marco d'Itri
Fix works in kernel 5.0 as well:
(k)rafaeldtinoco@drbdfix:~$ sudo dd if=/dev/zero of=/.loop bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 1.71956 s, 624 MB/s
(k)rafaeldtinoco@drbdfix:~$ sudo losetup --find --show /.loop
/dev/loop0
(k)rafaeldtinoco
Here is the thing...
log_setup_kmod_log() is the function controlling verbocity level. When
called from do_modprobe() execution path, it has a way to control the
"log priority", being able to control how verbose the execution should
be. Meanwhile, when log_setup_kmod_log() is called from do_depmod
Kmod source shows:
idx = index_file_open(fn);
if (idx == NULL) {
DBG(ctx, "could not open builtin file '%s'\n", fn);
return NULL;
}
and this is continuously called.
I'll check if DBG should be enabled in our case OR we should patch
upstream.
** Changed in: subiquity
Status: New =
Alright, afaict what is happening is this:
In Focal I first faced this issue when upgrading kmod to
26+20191223-1ubuntu1.. but my reproducer was "update-initramfs" only.
The issue is that both: mkinitramfs (initramfs-tools) needs a patch to
work with recent 5.x kernels:
# mkinitramfs (initramfs-t
Disco is EOL. All other supported versions need same patch for HWE
kernels.
** Also affects: initramfs-tools (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: initramfs-tools (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: initramfs-tools (Ub
Related bugs:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1866012
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1864992
--
You received this bug notification because you are a member of Ubuntu
Server, which is s
Related bugs:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1866012
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1864992
--
You received this bug notification because you are a member of Ubuntu
Server, which is s
** No longer affects: kmod (Ubuntu Focal)
** No longer affects: kmod (Ubuntu)
** No longer affects: initramfs-tools (Ubuntu Focal)
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1863261
Tit
Thanks for the feedback. I have uploaded the fix:
rafaeldtinoco@workstation:~/.../drbd-utils$ dput ubuntu
../drbd-utils_8.9.10-2ubuntu0.1_source.changes
Checking signature on .changes
gpg: ../drbd-utils_8.9.10-2ubuntu0.1_source.changes: Valid signature from
A93E0E0AD83C0D0F
Checking signature on
Alright, sorry for the delay, I'm revisiting this now...
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1864992
Title:
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
** Description changed:
[Impact]
* One can't manage drbd resources through drbdadm command after kernel
has been upgraded to 5.3 (latest HWE kernel).
[Test Case]
$ sudo dd if=/dev/zero of=/.loop bs=1M count=1024
$ sudo losetup --find --show /.loop
/dev/loop0
$ cat /
PPA: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1866458
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1866458
Title:
drbd not working after kernel upgrade 5.0.x -> 5.3.x
To m
@a1bert: please check PPA and if the fix solves your initial issue if
you can. I'm pretty confident it will as the testcase is simple and I
was able to verify on my side... anyway =). I'll wait launchpad to fix
this small issue to push the merge review into ubuntu-server upload
queue so a colleague
I'm having some issues pushing drbd-utils to my launchpad git repo and
launchpad team is working on it. Meanwhile I'm attaching this bug the
debdiff AND sending source package to a PPA to get reviews and
feedbacks.
--
You received this bug notification because you are a member of Ubuntu
Server, w
** Patch added: "drbd-utils_8.9.10-2ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/drbd-utils/+bug/1866458/+attachment/5334993/+files/drbd-utils_8.9.10-2ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug
After applying the given patch:
(k)rafaeldtinoco@drbdfix:~$ sudo dd if=/dev/zero of=/.loop bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 1.93099 s, 556 MB/s
(k)rafaeldtinoco@drbdfix:~$ sudo losetup --find --show /.loop
/dev/loop0
(k)rafaeldtinoco@
o affects: drbd-utils (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: drbd-utils (Ubuntu)
Status: In Progress => Fix Released
** Changed in: drbd-utils (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: drbd-utils (Ubuntu
anged in: drbd-utils (Ubuntu)
Importance: Undecided => Medium
** Changed in: drbd-utils (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
** Changed in: drbd-utils (Ubuntu)
Status: Triaged => Confirmed
--
You received this bug notification because you ar
em: couldn't find command:
fuser', last-rc-change='Fri Mar 6 21:14:36 2020', queued=0ms, exec=44ms
Because the nodes were missing "psmisc" package.
** Affects: resource-agents (Ubuntu)
Importance: Medium
Assignee: Rafael David Tinoco (rafaeldtinoco)
It only happens during package installation. Right after the package is
already installed, you can "modprobe -r dlm" and "modprobe dlm" again
and then the devices are properly translated from existing - from the
pkg - udev rules.
(k)rafaeldtinoco@clubionic03:~$ systemctl status dlm
● dlm.service -
I have monitored udev when modprobing dlm module and those are the udev
events being triggered:
(k)rafaeldtinoco@clubionic01:~$ sudo udevadm monitor --kernel
monitor will print the received events for:
KERNEL - the kernel uevent
KERNEL[10516.364250] add /module/dlm (module)
KERNEL[10516.3644
ot;misc/dlm-control"
KERNEL=="dlm-monitor", MODE="0666", SYMLINK+="misc/dlm-monitor"
KERNEL=="dlm_plock", MODE="0666", SYMLINK+="misc/dlm_plock"
KERNEL=="dlm_*", MODE="0660", SYMLINK+="misc/%k"
of POLICY_PASSIVE
3ba5ddf man: Change strcat to strncat
ed7573d man: Fix covscan reports in doxyxml.c
As it does not seem to need a freeze exception.
** Affects: kronosnet (Ubuntu)
Importance: Wishlist
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: Confirmed
** Affects: kronos
I believe this was fixed already so Im closing it as Fix Released.
** Changed in: kronosnet (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to kronosnet in Ubuntu.
https://bugs.launchpad.net/bugs/186
xpansion
d821ef33 iSCSILogicalUnit.in fixes (#1427)
c718050a Low: mysql-common: fix startup check
And I should revisit that.
** Affects: resource-agents (Ubuntu)
Importance: Wishlist
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: Confirmed
** Affects: resource-agents (Ubu
** Merge proposal unlinked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/pacemaker/+git/pacemaker/+merge/380336
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1866119
Title:
** Description changed:
OBS: This bug was originally into LP: #1865523 but it was split.
SRU: pacemaker
[Impact]
- * fence_scsi is not currently working in a share disk environment
+ * fence_scsi is not currently working in a share disk environment
- * all clusters relyin
** Summary changed:
- [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1
+ [bionic] fence_scsi not working properly with Pacemaker 1.1.18-2ubuntu1.1
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.l
SUMMARY:
One using packages from:
https://launchpad.net/~ubuntu-server-ha/+archive/ubuntu/staging
in Ubuntu Bionic will be workedaround temporarily (until fixes are
released) for the bugs:
https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1865523
https://bugs.launchpad.net/ubuntu/+sou
SUMMARY:
One using packages from:
https://launchpad.net/~ubuntu-server-ha/+archive/ubuntu/staging
in Ubuntu Bionic will be workedaround temporarily (until fixes are
released) for the bugs:
https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1865523
https://bugs.launchpad.net/ubuntu/+sou
A PPA can be currently found at : https://launchpad.net/~ubuntu-server-
ha/+archive/ubuntu/staging
I'm adjusting the SRU but, meanwhile, that PPA provides a working
version for Ubuntu Bionic.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to
A PPA can be currently found at : https://launchpad.net/~ubuntu-server-
ha/+archive/ubuntu/staging
I'm adjusting the SRU but, meanwhile, that PPA provides a working
version for Ubuntu Bionic.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to
** Description changed:
+ OBS: This bug was originally into LP: #1865523 but it was split.
+
+ SRU: pacemaker
+
+ [Impact]
+
+ * fence_scsi is not currently working in a share disk environment
+
+ * all clusters relying in fence_scsi and/or fence_scsi + watchdog won't
+ be able to start
** No longer affects: pacemaker (Ubuntu)
** No longer affects: pacemaker (Ubuntu Bionic)
** Description changed:
+ OBS: I have split this bug into 2 bugs:
+ - fence-agents (this) and pacemaker (LP: #1866119)
+
SRU: fence-agents
[Impact]
* fence_scsi is not currently worki
Public bug reported:
OBS: This bug was originally into LP: #1865523 but it was split.
SRU: pacemaker
[Impact]
* fence_scsi is not currently working in a share disk environment
* all clusters relying in fence_scsi and/or fence_scsi + watchdog won't
be able to start the fencing agents OR,
** Description changed:
+ SRU: fence-agents
+
+ [Impact]
+
+ * fence_scsi is not currently working in a share disk environment
+
+ * all clusters relying in fence_scsi and/or fence_scsi + watchdog won't
+ be able to start the fencing agents OR, in worst case scenarios, the
+ fence_scsi a
Preferred way for this fix was:
commit 0d34fbabc13891da41582b0823867dc5733fffef
Author: Rafael David Tinoco
Date: Mon Oct 24 15:35:03 2016
vhost: migration blocker only if shared log is used
Commit 31190ed7 added a migration blocker in vhost_dev_init() to
check if memfd would
QEMU BUG: https://bugs.launchpad.net/qemu/+bug/1626972
** Changed in: libvirt (Ubuntu)
Status: Fix Released => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1613423
Tit
# Demonstration of fence_scsi fencing a node:
(k)rafaeldtinoco@clubionic03:~/.../upstream$ cat /etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
# iscsi
auto eth1
iface eth1 inet static
address 10.250.1.12/24
# private
auto eth2
iface eth2 inet static
Now I'm going to work with this package and check needed Pacemaker
fixes. After that I'm going to propose both merges together.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1865523
Title:
# For Ubuntu Bionic:
Okay, after bisecting fence-scsi and monitoring all its functions I was
able to isolate the patches that I need to take to bionic to make it
compatible with existing version and, at the same time, operational:
Note: all tests were conducted with Pacemaker v1.1.19-0ubuntu1 and
# Demonstration of fence_scsi agent working in Bionic:
(k)rafaeldtinoco@clubionic01:~/.../upstream$ sudo dpkg -i ./*.deb
dpkg: warning: downgrading fence-agents from 4.4.0-2 to 4.0.25-2ubuntu1
(Reading database ... 85434 files and directories currently installed.)
Preparing to unpack .../fence-age
w
** Changed in: pacemaker (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: pacemaker (Ubuntu)
Importance: Medium => Undecided
** Changed in: pacemaker (Ubuntu)
Status: Confirmed => Triaged
** Also affects: pacemaker (Ubuntu Foca
cluster.bionic. 4.0
Peripheral device type: disk
PR generation=0x0, there is NO reservation held
** Affects: pacemaker (Ubuntu)
Importance: Medium
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: Confirmed
** Changed in: pacemaker (Ubuntu)
Status: New =&
** Changed in: ruby-psych (Ubuntu)
Assignee: Lucas Kanashiro (lucaskanashiro) => (unassigned)
** Changed in: jruby (Ubuntu)
Assignee: Lucas Kanashiro (lucaskanashiro) => (unassigned)
** Changed in: ruby-psych (Ubuntu)
Assignee: (unassigned) => Steve Langasek (vorlon)
--
You recei
Targetcli got into -proposed:
https://bugs.launchpad.net/ubuntu/+source/targetcli-fb/1:2.1.51-0ubuntu1
Subscribing security for targetcli-fb MIR security analysis.
** Changed in: targetcli-fb (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: target
Ok, Im uploading targetcli-fb based on our discussions after you fixed
the todos:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/targetcli-
fb/+git/targetcli-fb/+merge/379938
And will assign security team to targetcli-fb after uploaded.
Thanks a lot @Christian.
--
You received this b
This bug was fixed in the package ruby-defaults - 1:2.7~0
Sponsored for Lucas Kanashiro (lucaskanashiro)
---
ruby-defaults (1:2.7~0) experimental; urgency=medium
[ Antonio Terceiro ]
* Make Ruby 2.7 the default and drop Ruby 2.5
* debian/tests/control: add test-name pkg-config t
This bug was fixed in the package sbd - 1.4.1-3
Sponsored for Rafael David Tinoco (rafaeldtinoco)
---
sbd (1.4.1-3) unstable; urgency=medium
* debian/control: cleanup Build-Depends
-- Valentin Vidic Sat, 11 Jan 2020 11:48:05 +0100
sbd (1.4.1-2) unstable; urgency=medium
##
## SUMMARY (please correct me if I'm wrong)
##
python-rtslib-fb- lib: object API for managing Linux LIO kernel
target
python-configshell-fb - lib: framework for building CLI-based apps
MIR #1)
ceph-iscsi - LIO gateways for Ceph (logic and CLI
tools)
deps:
201 - 300 of 690 matches
Mail list logo
