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
Bugs, which is subscribed to Ub
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
Bugs, which is subscribed to Ub
** 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
Let me clarify better why I'm flagging this as incomplete:
14:20 my upstream fix was to qemu
14:20 and it fixed the issue by not having the memfd file
created
14:20 for live migrations.. but there might be cases where
there should be one
14:21 in those cases, libvirt should be creating the a
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613423
Title:
Mitaka
There wasn't any action in libvirt side (so I'm making this incomplete).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613423
Title:
Mitaka + Trusty (kernel 3.13) not using apparmor capability by
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
# 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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865523
Title:
[bionic]
# 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
# 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
ntu)
Importance: Undecided => Low
** Changed in: kmod (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
--
You received this bug notification because you are
@dsmythies, @kaihengfeng
you seem to be correct.
First time I saw that issue was in a kmod regression test iirc.
The fix was supposed to be in:
initramfs-tools (0.133ubuntu15) focal; urgency=medium
from:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261
but I see now tha
*** This bug is a duplicate of bug 1864992 ***
https://bugs.launchpad.net/bugs/1864992
** This bug has been marked a duplicate of bug 1864992
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open
builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'
--
Y
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864992
Title:
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() coul
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864436
Title:
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() coul
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
dpkg-deb: building package 'uwsgi-plugins-all' in
'../uwsgi-plugins-all_2.0.18-5ubuntu7_amd64.deb'.
dpkg-genbuildinfo --build=binary
dpkg-genchanges --build=binary >../uwsgi_2.0.18-5ubuntu7_amd64.changes
dpkg-genchanges: warning: substitution variable ${uwsgi:RubyKind} used, but is
not defined
I have just sponsored this for you, feel free to close this bug manually
as your changelog entry is not mentioning this particular bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865576
Title:
M
: New => Invalid
** Changed in: fence-agents (Ubuntu Bionic)
Status: Confirmed => Invalid
** Changed in: fence-agents (Ubuntu Bionic)
Importance: High => Undecided
** Changed in: fence-agents (Ubuntu Bionic)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
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
Checking git history in salsa for both I can see that ruby-psych has
oscillated in between suggests and depends 2 or 3 times.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864988
Title:
[focal] jru
Public bug reported:
Currently there is a build-dependency loop among jruby and ruby-psych.
I'll probably drop ruby-psych from jruby, build it, and put it back on
to workaround this for now.
This became apparent during ruby2.7 transitions:
- https://people.canonical.com/~ubuntu-
archive/transi
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:
Yes, I have just confirmed that in Bionic, the fence_scsi fails to
create the /var/run/cluster by itself:
rafaeldtinoco@clubionic01:~$ crm configure
crm(live)configure# primitive fence_clufocal stonith:fence_scsi \
> params pcmk_host_list="10.250.98.10 10.250.98.11 10.250.98.12"
device
Previous command show the full set of commands given by fence_scsi agent to the
storage server, for the shared disk used by the cluster. Bellow is the exact
same test at Azure environment. I was having issues before and I'm not having
them anymore as it seems. I'll have to investigate what the c
I was able to confirm that, in Ubuntu Focal, during fence_scsi
initialization:
(k)rafaeldtinoco@clufocal01:~$ crm configure show
node 1: clufocal01
node 2: clufocal02
node 3: clufocal03
primitive fence_clufocal stonith:fence_scsi \
params pcmk_host_list="clufocal01 clufocal02 clufocal03"
@vybava,
I just realized the bug description has the exact command sequence you
need. But I'm putting again in this comment to make things easier.
Please follow the order that was written bellow:
##
## NODE #1
##
# tell "fence_scsi" agent that node 1 is "on"
$ sudo fence_scsi --verbose -n 10.25
ents (Ubuntu Focal)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864404
Title:
fence_scsi cannot open /var/run/cluster/fence_scsi.key (do
I have discussed this again with @canonical-server team and it seems
that this package is python2 and maintainer (@dustin) said there won't
be any updates to this in the future.
It looks like the recommended similar behaviour, to what powernap was
providing, is Ubuntu Openstack power saving functi
** Changed in: powernap (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853001
Title:
RM powernap binary & source packages from Focal
To manage notificat
I have tried in another environment, using LIO as storage server, and
Focal (because I only had Focal available) and I was able to release all
keys from the shared disk:
(k)rafaeldtinoco@clufocal01:~$ sudo sg_persist -v --out --release
--param-rk=0xbf09 --prout-type=5 /dev/sda
inquiry cdb
00 [DRIVER_OK]
** Affects: fence-agents (Ubuntu)
Importance: Undecided
Status: New
** Affects: fence-agents (Ubuntu Bionic)
Importance: High
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: Confirmed
** Also affects: fence-agents (Ubuntu Bionic)
Importance:
Creating an easier reproducer:
Node 01:
rafaeldtinoco@clubionic01:~$ sudo sg_persist --out --register
--param-sark=3abe /dev/sdc
Msft Virtual Disk 1.0
Peripheral device type: disk
rafaeldtinoco@clubionic01:~$ sudo sg_persist --out --reserve
--param-rk=3abe --prout-type=5
** Also affects: fence-agents (Ubuntu Bionic)
Importance: Undecided
Status: New
** No longer affects: fence-agents (Ubuntu Xenial)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864404
Titl
** Also affects: fence-agents (Ubuntu Bionic)
Importance: Undecided
Status: New
** No longer affects: fence-agents (Ubuntu Xenial)
** Summary changed:
- [xenial] fence_scsi does not support hostnames in node list
+ [bionic] fence_scsi does not support hostnames in node list
--
You re
** Summary changed:
- fence_scsi does not support hostnames in node list
+ [xenial] fence_scsi does not support hostnames in node list
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864410
Title:
[
nce-agents (Ubuntu Xenial)
Importance: Medium
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: Confirmed
** Also affects: fence-agents (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: fence-agents (Ubuntu Xenial)
Status: New => Confirmed
** Chan
Make sure to also create the "fence_scsi.dev" file doing the same:
# node01
create a file /etc/fence_scsi.dev containing: /dev/disk/by-path/acpi-
VMBUS:01-scsi-0:0:0:0
# node02
create a file /etc/fence_scsi.dev containing: /dev/disk/by-path/acpi-
VMBUS:01-scsi-0:0:0:0
# node03
create a file /
# WORKAROUND:
A way to workaround this issue is the following... in a 3 node cluster
you can do this:
# node01
create a file /etc/fence_scsi.key containing: 62ed
# node02
create a file /etc/fence_scsi.key containing: 62ed0001
# node03
create a file /etc/fence_scsi.key containing: 62ed000
ed by fence_scsi agent does not
exist.
** Affects: fence-agents (Ubuntu)
Importance: Undecided
Status: New
** Affects: fence-agents (Ubuntu Xenial)
Importance: High
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: Confirmed
** Also affects: fence-agents (Ubuntu X
Thanks a lot Alex. I'll add some DEP8 tests to python-configshell-fb.
Already created a card for it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854362
Title:
[MIR] ceph-iscsi, tcmu, python-confi
The following commit, merged upstream:
commit ba7caf4
Author: Valentin Vidic
Date: Sat Nov 23 12:44:23 2019
debian/tests: make the corosync test skippable
diff --git a/debian/tests/control b/debian/tests/control
index 4257fe9..3a1ef7f 100644
--- a/debian/tests/control
+++ b/debian/t
** Changed in: multipath-tools (Ubuntu)
Status: Confirmed => 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/1862282
Title:
[merge] multipath-tools should be merged to 0.8.3-1
To
Public bug reported:
Package: sbd (debian: 1.4.1-3, ubuntu: 1.4.0-18-g5e3283c-1ubuntu1) needs
merge
** Affects: sbd (Ubuntu)
Importance: Medium
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: In Progress
** Changed in: sbd (Ubuntu)
Status: New => Incompl
** Merge proposal unlinked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/corosync/+git/corosync/+merge/379581
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828228
Title:
corosync fa
** Merge proposal linked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/corosync/+git/corosync/+merge/379581
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864087
Title:
Package: coro
** Merge proposal linked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/pacemaker/+git/pacemaker/+merge/379595
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864116
Title:
Package: pa
** Merge proposal unlinked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/pacemaker/+git/pacemaker/+merge/379595
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828228
Title:
corosync
Public bug reported:
Package: pacemaker (debian: 2.0.3-3, ubuntu: 2.0.1-5ubuntu5) needs merge
** Affects: pacemaker (Ubuntu)
Importance: Medium
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: In Progress
** Changed in: pacemaker (Ubuntu)
Status: New =>
+ d/t/quorumtool: skip if memlock can't be set to unlimited by uid 0
-- Rafael David Tinoco Thu, 20 Feb 2020
17:57:22 +
corosync (3.0.3-2) unstable; urgency=medium
* [d0a06e5] Separate the autopkgtests and make them generate artifacts
* [8680d48] Run Salsa CI reprotest with
Public bug reported:
Package: corosync (debian: 3.0.3-2, ubuntu: 3.0.2-1ubuntu2) needs merge
** Affects: corosync (Ubuntu)
Importance: Medium
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: In Progress
** Changed in: corosync (Ubuntu)
Status: New => In Progr
** Description changed:
== ceph-iscsi ==
[Availability]
In universe
[Rationale]
Provides iSCSI gateway to a Ceph cluster, allowing clients which don't
understand RBD to use Ceph storage.
[Security]
No security history found.
[Quality assurance]
Package runs tests dur
James,
Its in my TODO list to take care of iSCSI session in server guide after
freeze. So, yep. If you have someone to take care of cinder at your side
than I think we're good.
Adding targetcli-fb to the MIR list then...
** Also affects: targetcli-fb (Ubuntu)
Importance: Undecided
Stat
Thats awesome @ginggs, thanks for reviewing it and, indeed, I'll mention
that in the changelog.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863739
Title:
[focal] cacti needs a merge from 1.2.4+ds
Alright @ginggs, based on the Debian bug and your input I have dropped
that commit from the merge request, will submit resulting package back
to PPA so we have an updated build to test. Thanks for the feedback.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
BTW, if this sounds good, and I hope it does, I'd vote for demoting tgt
in favor of having targetcli-fb as the only iSCSI target available in
[main] (good comparison tables can be found at: http://www.linux-
iscsi.org/wiki/Features, and justifies the request IMO).
--
You received this bug notific
BUG: https://bugs.launchpad.net/ubuntu/+source/cacti/+bug/1863739
MERGE:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/cacti/+git/cacti/+merge/379397
PPA: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1863739
** Merge proposal linked:
https://code.launchpad.net/~rafaeldtin
cacti (Ubuntu)
Importance: Medium
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: In Progress
** Changed in: cacti (Ubuntu)
Status: New => Triaged
** Changed in: cacti (Ubuntu)
Status: Triaged => In Progress
** Changed in: cacti (Ubuntu)
Importance
targetcli-fb depends on python3-rtslib-fb and project is hosted here:
https://github.com/open-iscsi/targetcli-fb
It is not a direct need judging original request by James Page BUT its
the CLI for configuring LIO/TCM kernel function. There is no other tool
able to configure LIO/TCM kernel iSCSI ta
Any chances of this landing in 20.04 ?
I really would like to have:
- python3-configshell-fb
- python3-rtslib-fb
- targetcli-fb
included in 20.04 [main] as the official - including the kernel side -
way to provide iSCSI targets
(https://www.kernel.org/doc/Documentation/target/tcmu-design.txt) to
I'm also setting this bug to affect fence-agents as it could provide
some workaround for Persistent Reserve Out (5Fh) without the preempt and
abort support (also as a whishlist, and for documentation purposes).
** Also affects: fence-agents (Ubuntu)
Importance: Undecided
Status: New
**
Public bug reported:
When using TGT to serve iSCSI targets/luns to a corosync/pacemaker
cluster, if one wants to use "fence_scsi" to fence the shared disk for a
particular node it won't be able to as tgt does not implement the
PREEMPT AND ABORT (05h) service.
A error like this will occur:
$ sudo
Thanks christian, you are right.
I opened this in rush thinking about not forgetting it when doing the
fixes after the freeze.
/usr/share/doc/tgt/examples/targets.conf.example <- here you go, as you
said!
Not sure I should worry about changing the man page about it or not. In
this case, for exam
.
** Affects: fence-agents (Ubuntu)
Importance: Medium
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: Confirmed
** Changed in: fence-agents (Ubuntu)
Status: New => Confirmed
** Changed in: fence-agents (Ubuntu)
Importance: Undecided => Medium
** Change
https://salsa.debian.org/ha-team/pacemaker/merge_requests/1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863437
Title:
[focal] pacemaker i386 should drop a few i386 only packages
To manage notifi
Upstream already had the following commit (since @vorlon opened the bug
in January):
commit 543574f18
Author: Ferenc Wágner
Date: Thu Jan 9 14:19:19 2020
Omit pacemaker{, -cli-utils, -remote} on Ubuntu/i386
Closes: #948379
diff --git a/debian/rules b/debian/rules
index 1d186d74
Merged and uploaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863437
Title:
[focal] pacemaker i386 should drop a few i386 only packages
To manage notifications about this bug go to:
https://b
targets.conf is empty
2) /usr/share/doc/tgt/targets.conf.example does not exist in any package
as it seems.
** Affects: tgt (Ubuntu)
Importance: Medium
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: Confirmed
** Changed in: tgt (Ubuntu)
Status: New => Conf
"fakeroot debian/rules build-arch" gives me:
dpkg-deb: building package 'pacemaker-remote' in
'../pacemaker-remote_2.0.1-5ubuntu5_i386.deb'.
dpkg-deb: building package 'pacemaker' in
'../pacemaker_2.0.1-5ubuntu5_i386.deb'.
dpkg-deb: building package 'libcrmcluster29' in
'../libcrmcluster29_2.0.
# i386 build in local environment
dpkg-deb: building package 'libcib27' in '../libcib27_2.0.1-5ubuntu5_i386.deb'.
dpkg-deb: building package 'pacemaker-common' in
'../pacemaker-common_2.0.1-5ubuntu5_all.deb'.
dpkg-deb: building package 'libcrmcommon34' in
'../libcrmcommon34_2.0.1-5ubuntu5_i386.d
* Affects: pacemaker (Ubuntu)
Importance: Medium
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: In Progress
** Affects: pacemaker (Ubuntu Focal)
Importance: Medium
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: In Progress
** Changed in: pacem
MERGE: https://code.launchpad.net/~rafaeldtinoco/britney/hints-
ubuntu/+merge/379234
Will allow pacemaker migration as it will unblock bad i386 autopkgtest
results.
** Branch linked: lp:~rafaeldtinoco/britney/hints-ubuntu
--
You received this bug notification because you are a member of Ubuntu
PPA: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1863261
MERGE:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/379222
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
** Merge proposal linked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/379222
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863261
Title:
** Also affects: kmod (Ubuntu)
Importance: Undecided
Status: New
** Changed in: kmod (Ubuntu Focal)
Status: New => 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/1863261
57
** Affects: initramfs-tools (Ubuntu)
Importance: Medium
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: In Progress
** Affects: initramfs-tools (Ubuntu Focal)
Importance: Medium
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: In Progress
** Ch
Balint, based on your input...
> thanks for the fixes in Eoan. Unfortunately we have a product based on
> disco and cannot move forward at this time. Being a networking shop,
> this issue has a serious effect on us and we would like to avoid moving
> to something like ifupdown2 within our stable b
*** This bug is a duplicate of bug 1815101 ***
https://bugs.launchpad.net/bugs/1815101
Hello Matthew, actually this might be a duplicate of BUG 1815101 because
that fix was not backported to Xenial. I can include Xenial in that list
and study efforts to backport the systemd-networkd to Xenial
Xenial)
Importance: Undecided => Medium
** Changed in: keepalived (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: keepalived (Ubuntu Xenial)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
** No longer affects: heartbeat (Ubuntu Xenial)
** Changed in
Related bugs:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1862364
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1862770
** Changed in: mysql-8.0 (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of U
*** This bug is a duplicate of bug 1862364 ***
https://bugs.launchpad.net/bugs/1862364
Ah, nm, this is a duplicate =o).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862770
Title:
MySQL autopk
I have just uploaded mysql-8.0_8.0.19-0ubuntu3 containing fixes for the
2020 year in mysql tests. I'll flag this as Fix Committed and Fix
Released manually as only LP: #1862364 was referred in that changelog.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have just uploaded mysql-8.0_8.0.19-0ubuntu3 containing fixes for the
2020 year in mysql tests.
Related bugs:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1862770
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1859100
** Changed in: mysql-8.0 (Ubuntu)
Status: Triag
*** This bug is a duplicate of bug 1862364 ***
https://bugs.launchpad.net/bugs/1862364
Related bugs:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1862364
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1859100
--
You received this bug notification because you are a memb
*** This bug is a duplicate of bug 1862364 ***
https://bugs.launchpad.net/bugs/1862364
I have just uploaded mysql-8.0_8.0.19-0ubuntu3 containing fixes for the
2020 year in mysql tests. I'll flag this as Fix Committed and Fix
Released manually as only LP: #1862364 was referred in that changelog
I just pushed the merge and uploaded source code.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861316
Title:
ubuntu 20.04: libnss-winbind:386 should remain
To manage notifications about this bug
** Changed in: samba (Ubuntu)
Status: Triaged => 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/1861316
Title:
ubuntu 20.04: libnss-winbind:386 should remain
To manage notificatio
$ rmadison crmsh
crmsh | 1.2.5+hg1034-1ubuntu3 | trusty | source, all
crmsh | 1.2.5+hg1034-1ubuntu4 | trusty-updates | source, all
crmsh | 2.2.0-1 | xenial | source, ...
crmsh | 3.0.1-3ubuntu1| bionic/universe | source, all
crmsh | 3.0.1-3ubuntu1
Acording to:
https://bugs.launchpad.net/ubuntu/+source/crmsh/+bug/1205019/comments/10
It was proposed to main again by doko.
I'll wait full pacemaker migration - and test crmsh installation - to
close this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Thanks Steve!! Package is back to archive, moving on with what needed
this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862928
Title:
python-crypto (i386) needs rebuild in Focal (python 3.7 -> py
Correct! I missed that part. 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/1862947
Title:
crmsh should be taken back to -main
To manage notifications about this bug go to:
https://bugs.l
801 - 900 of 2815 matches
Mail list logo
