| 2020-03-07 12:50:40 |
a1bert |
bug |
|
|
added bug |
| 2020-03-07 16:06:05 |
Rafael David Tinoco |
drbd-utils (Ubuntu): status |
New |
Triaged |
|
| 2020-03-07 16:06:10 |
Rafael David Tinoco |
drbd-utils (Ubuntu): importance |
Undecided |
Medium |
|
| 2020-03-07 16:06:19 |
Rafael David Tinoco |
drbd-utils (Ubuntu): assignee |
|
Rafael David Tinoco (rafaeldtinoco) |
|
| 2020-03-07 16:06:28 |
Rafael David Tinoco |
bug |
|
|
added subscriber Ubuntu Server |
| 2020-03-07 16:06:35 |
Rafael David Tinoco |
bug |
|
|
added subscriber Ubuntu Server High Availability |
| 2020-03-07 16:11:59 |
Rafael David Tinoco |
drbd-utils (Ubuntu): status |
Triaged |
Confirmed |
|
| 2020-03-09 12:18:15 |
Robie Basak |
tags |
amd64 apport-bug bionic |
amd64 apport-bug bionic server-next |
|
| 2020-03-09 17:15:55 |
Pierre-Luc Bertrand |
bug |
|
|
added subscriber Pierre-Luc Bertrand |
| 2020-03-09 23:38:03 |
Rafael David Tinoco |
description |
I am not able to bring drbd resource up after kernel upgrade (5.0 -> 5.3)
/sbin/drbdadm -v up amail
drbdsetup-84 new-resource amail
amail: Invalid argument
Command 'drbdsetup-84 new-resource amail' terminated with exit code 20
drbdadm: new-minor amail: skipped due to earlier error
it maybe this issue:
https://www.mail-archive.com/openembedded-devel@lists.openembedded.org/msg64900.html
but not tested by me
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: drbd-utils 8.9.10-2
ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
Date: Sat Mar 7 13:39:39 2020
Dependencies:
gcc-8-base 8.3.0-6ubuntu1~18.04.1
libc6 2.27-3ubuntu1
libgcc1 1:8.3.0-6ubuntu1~18.04.1
libstdc++6 8.3.0-6ubuntu1~18.04.1
lsb-base 9.20170808ubuntu1
InstallationDate: Installed on 2019-10-22 (136 days ago)
InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
SourcePackage: drbd-utils
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.drbd.d.global_common.conf: 2019-12-05T11:34:58.322390 |
[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 /etc/drbd.d/r0.res
resource r0 {
protocol C;
startup {
wfc-timeout 15;
degr-wfc-timeout 60;
}
net {
cram-hmac-alg sha1;
shared-secret "secret";
}
on drbdfix {
device /dev/drbd0;
disk /dev/loop0;
address 10.250.99.202:7788;
meta-disk internal;
}
on drbdnon {
device /dev/drbd0;
disk /dev/loop0;
address 192.168.0.2:7788;
meta-disk internal;
}
}
* Check that with kernel 5.0.0 drbdadm command works fine for the configured resource:
$ uname -a
Linux drbdfix 5.0.0-43-generic #47~18.04.1-Ubuntu SMP Mon Mar 2 04:28:21 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
$ sudo drbdadm -v up r0
no resources defined!
* And with kernel 5.3.0 it does not:
$ uname -a
Linux drbdfix 5.3.0-42-generic #34~18.04.1-Ubuntu SMP Fri Feb 28 13:42:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
$ sudo drbdadm -v up r0
drbdsetup-84 new-resource r0
r0: Invalid argument
Command 'drbdsetup-84 new-resource r0' terminated with exit code 20
drbdadm: new-minor r0: skipped due to earlier error
[Regression Potential]
* TBD
[Other Info]
* Original Case Description:
I am not able to bring drbd resource up after kernel upgrade (5.0 -> 5.3)
/sbin/drbdadm -v up amail
drbdsetup-84 new-resource amail
amail: Invalid argument
Command 'drbdsetup-84 new-resource amail' terminated with exit code 20
drbdadm: new-minor amail: skipped due to earlier error
it maybe this issue:
https://www.mail-archive.com/openembedded-devel@lists.openembedded.org/msg64900.html
but not tested by me
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: drbd-utils 8.9.10-2
ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
Date: Sat Mar 7 13:39:39 2020
Dependencies:
gcc-8-base 8.3.0-6ubuntu1~18.04.1
libc6 2.27-3ubuntu1
libgcc1 1:8.3.0-6ubuntu1~18.04.1
libstdc++6 8.3.0-6ubuntu1~18.04.1
lsb-base 9.20170808ubuntu1
InstallationDate: Installed on 2019-10-22 (136 days ago)
InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
SourcePackage: drbd-utils
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.drbd.d.global_common.conf: 2019-12-05T11:34:58.322390 |
|
| 2020-03-09 23:38:07 |
Rafael David Tinoco |
drbd-utils (Ubuntu): status |
Confirmed |
In Progress |
|
| 2020-03-09 23:38:29 |
Rafael David Tinoco |
nominated for series |
|
Ubuntu Bionic |
|
| 2020-03-09 23:38:29 |
Rafael David Tinoco |
bug task added |
|
drbd-utils (Ubuntu Bionic) |
|
| 2020-03-09 23:38:34 |
Rafael David Tinoco |
drbd-utils (Ubuntu): status |
In Progress |
Fix Released |
|
| 2020-03-09 23:38:36 |
Rafael David Tinoco |
drbd-utils (Ubuntu): assignee |
Rafael David Tinoco (rafaeldtinoco) |
|
|
| 2020-03-09 23:38:38 |
Rafael David Tinoco |
drbd-utils (Ubuntu): importance |
Medium |
Undecided |
|
| 2020-03-09 23:38:40 |
Rafael David Tinoco |
drbd-utils (Ubuntu Bionic): status |
New |
In Progress |
|
| 2020-03-09 23:38:42 |
Rafael David Tinoco |
drbd-utils (Ubuntu Bionic): importance |
Undecided |
Medium |
|
| 2020-03-09 23:38:44 |
Rafael David Tinoco |
drbd-utils (Ubuntu Bionic): assignee |
|
Rafael David Tinoco (rafaeldtinoco) |
|
| 2020-03-10 00:08:53 |
Rafael David Tinoco |
description |
[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 /etc/drbd.d/r0.res
resource r0 {
protocol C;
startup {
wfc-timeout 15;
degr-wfc-timeout 60;
}
net {
cram-hmac-alg sha1;
shared-secret "secret";
}
on drbdfix {
device /dev/drbd0;
disk /dev/loop0;
address 10.250.99.202:7788;
meta-disk internal;
}
on drbdnon {
device /dev/drbd0;
disk /dev/loop0;
address 192.168.0.2:7788;
meta-disk internal;
}
}
* Check that with kernel 5.0.0 drbdadm command works fine for the configured resource:
$ uname -a
Linux drbdfix 5.0.0-43-generic #47~18.04.1-Ubuntu SMP Mon Mar 2 04:28:21 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
$ sudo drbdadm -v up r0
no resources defined!
* And with kernel 5.3.0 it does not:
$ uname -a
Linux drbdfix 5.3.0-42-generic #34~18.04.1-Ubuntu SMP Fri Feb 28 13:42:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
$ sudo drbdadm -v up r0
drbdsetup-84 new-resource r0
r0: Invalid argument
Command 'drbdsetup-84 new-resource r0' terminated with exit code 20
drbdadm: new-minor r0: skipped due to earlier error
[Regression Potential]
* TBD
[Other Info]
* Original Case Description:
I am not able to bring drbd resource up after kernel upgrade (5.0 -> 5.3)
/sbin/drbdadm -v up amail
drbdsetup-84 new-resource amail
amail: Invalid argument
Command 'drbdsetup-84 new-resource amail' terminated with exit code 20
drbdadm: new-minor amail: skipped due to earlier error
it maybe this issue:
https://www.mail-archive.com/openembedded-devel@lists.openembedded.org/msg64900.html
but not tested by me
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: drbd-utils 8.9.10-2
ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
Date: Sat Mar 7 13:39:39 2020
Dependencies:
gcc-8-base 8.3.0-6ubuntu1~18.04.1
libc6 2.27-3ubuntu1
libgcc1 1:8.3.0-6ubuntu1~18.04.1
libstdc++6 8.3.0-6ubuntu1~18.04.1
lsb-base 9.20170808ubuntu1
InstallationDate: Installed on 2019-10-22 (136 days ago)
InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
SourcePackage: drbd-utils
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.drbd.d.global_common.conf: 2019-12-05T11:34:58.322390 |
[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 /etc/drbd.d/r0.res
resource r0 {
protocol C;
startup {
wfc-timeout 15;
degr-wfc-timeout 60;
}
net {
cram-hmac-alg sha1;
shared-secret "secret";
}
on drbdfix {
device /dev/drbd0;
disk /dev/loop0;
address 10.250.99.202:7788;
meta-disk internal;
}
on drbdnon {
device /dev/drbd0;
disk /dev/loop0;
address 192.168.0.2:7788;
meta-disk internal;
}
}
* Check that with kernel 5.0.0 drbdadm command works fine for the configured resource:
$ uname -a
Linux drbdfix 5.0.0-43-generic #47~18.04.1-Ubuntu SMP Mon Mar 2 04:28:21 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
$ sudo drbdadm create-md r0
initializing activity log
NOT initializing bitmap
Writing meta data...
New drbd meta data block successfully created.
$ sudo drbdadm -v up r0
drbdsetup-84 new-resource r0
drbdsetup-84 new-minor r0 0 0
drbdmeta 0 v08 /dev/loop0 internal apply-al
drbdsetup-84 attach 0 /dev/loop0 /dev/loop0 internal
drbdsetup-84 connect r0 ipv4:10.250.99.202:7788 ipv4:192.168.0.2:7788 --protocol=C --cram-hmac-alg=sha1 --shared-secret=secret
* And with kernel 5.3.0 it does not:
$ uname -a
Linux drbdfix 5.3.0-42-generic #34~18.04.1-Ubuntu SMP Fri Feb 28 13:42:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
$ sudo drbdadm -v up r0
drbdsetup-84 new-resource r0
r0: Invalid argument
Command 'drbdsetup-84 new-resource r0' terminated with exit code 20
drbdadm: new-minor r0: skipped due to earlier error
[Regression Potential]
* TBD
[Other Info]
* Original Case Description:
I am not able to bring drbd resource up after kernel upgrade (5.0 -> 5.3)
/sbin/drbdadm -v up amail
drbdsetup-84 new-resource amail
amail: Invalid argument
Command 'drbdsetup-84 new-resource amail' terminated with exit code 20
drbdadm: new-minor amail: skipped due to earlier error
it maybe this issue:
https://www.mail-archive.com/openembedded-devel@lists.openembedded.org/msg64900.html
but not tested by me
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: drbd-utils 8.9.10-2
ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
Date: Sat Mar 7 13:39:39 2020
Dependencies:
gcc-8-base 8.3.0-6ubuntu1~18.04.1
libc6 2.27-3ubuntu1
libgcc1 1:8.3.0-6ubuntu1~18.04.1
libstdc++6 8.3.0-6ubuntu1~18.04.1
lsb-base 9.20170808ubuntu1
InstallationDate: Installed on 2019-10-22 (136 days ago)
InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
SourcePackage: drbd-utils
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.drbd.d.global_common.conf: 2019-12-05T11:34:58.322390 |
|
| 2020-03-10 00:17:25 |
Rafael David Tinoco |
attachment 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 |
|
| 2020-03-10 10:41:05 |
Rafael David Tinoco |
description |
[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 /etc/drbd.d/r0.res
resource r0 {
protocol C;
startup {
wfc-timeout 15;
degr-wfc-timeout 60;
}
net {
cram-hmac-alg sha1;
shared-secret "secret";
}
on drbdfix {
device /dev/drbd0;
disk /dev/loop0;
address 10.250.99.202:7788;
meta-disk internal;
}
on drbdnon {
device /dev/drbd0;
disk /dev/loop0;
address 192.168.0.2:7788;
meta-disk internal;
}
}
* Check that with kernel 5.0.0 drbdadm command works fine for the configured resource:
$ uname -a
Linux drbdfix 5.0.0-43-generic #47~18.04.1-Ubuntu SMP Mon Mar 2 04:28:21 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
$ sudo drbdadm create-md r0
initializing activity log
NOT initializing bitmap
Writing meta data...
New drbd meta data block successfully created.
$ sudo drbdadm -v up r0
drbdsetup-84 new-resource r0
drbdsetup-84 new-minor r0 0 0
drbdmeta 0 v08 /dev/loop0 internal apply-al
drbdsetup-84 attach 0 /dev/loop0 /dev/loop0 internal
drbdsetup-84 connect r0 ipv4:10.250.99.202:7788 ipv4:192.168.0.2:7788 --protocol=C --cram-hmac-alg=sha1 --shared-secret=secret
* And with kernel 5.3.0 it does not:
$ uname -a
Linux drbdfix 5.3.0-42-generic #34~18.04.1-Ubuntu SMP Fri Feb 28 13:42:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
$ sudo drbdadm -v up r0
drbdsetup-84 new-resource r0
r0: Invalid argument
Command 'drbdsetup-84 new-resource r0' terminated with exit code 20
drbdadm: new-minor r0: skipped due to earlier error
[Regression Potential]
* TBD
[Other Info]
* Original Case Description:
I am not able to bring drbd resource up after kernel upgrade (5.0 -> 5.3)
/sbin/drbdadm -v up amail
drbdsetup-84 new-resource amail
amail: Invalid argument
Command 'drbdsetup-84 new-resource amail' terminated with exit code 20
drbdadm: new-minor amail: skipped due to earlier error
it maybe this issue:
https://www.mail-archive.com/openembedded-devel@lists.openembedded.org/msg64900.html
but not tested by me
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: drbd-utils 8.9.10-2
ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
Date: Sat Mar 7 13:39:39 2020
Dependencies:
gcc-8-base 8.3.0-6ubuntu1~18.04.1
libc6 2.27-3ubuntu1
libgcc1 1:8.3.0-6ubuntu1~18.04.1
libstdc++6 8.3.0-6ubuntu1~18.04.1
lsb-base 9.20170808ubuntu1
InstallationDate: Installed on 2019-10-22 (136 days ago)
InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
SourcePackage: drbd-utils
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.drbd.d.global_common.conf: 2019-12-05T11:34:58.322390 |
[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 /etc/drbd.d/r0.res
resource r0 {
protocol C;
startup {
wfc-timeout 15;
degr-wfc-timeout 60;
}
net {
cram-hmac-alg sha1;
shared-secret "secret";
}
on drbdfix {
device /dev/drbd0;
disk /dev/loop0;
address 10.250.99.202:7788;
meta-disk internal;
}
on drbdnon {
device /dev/drbd0;
disk /dev/loop0;
address 192.168.0.2:7788;
meta-disk internal;
}
}
* Check that with kernel 5.0.0 drbdadm command works fine for the configured resource:
$ uname -a
Linux drbdfix 5.0.0-43-generic #47~18.04.1-Ubuntu SMP Mon Mar 2 04:28:21 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
$ sudo drbdadm create-md r0
initializing activity log
NOT initializing bitmap
Writing meta data...
New drbd meta data block successfully created.
$ sudo drbdadm -v up r0
drbdsetup-84 new-resource r0
drbdsetup-84 new-minor r0 0 0
drbdmeta 0 v08 /dev/loop0 internal apply-al
drbdsetup-84 attach 0 /dev/loop0 /dev/loop0 internal
drbdsetup-84 connect r0 ipv4:10.250.99.202:7788 ipv4:192.168.0.2:7788 --protocol=C --cram-hmac-alg=sha1 --shared-secret=secret
* And with kernel 5.3.0 it does not:
$ uname -a
Linux drbdfix 5.3.0-42-generic #34~18.04.1-Ubuntu SMP Fri Feb 28 13:42:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
$ sudo drbdadm -v up r0
drbdsetup-84 new-resource r0
r0: Invalid argument
Command 'drbdsetup-84 new-resource r0' terminated with exit code 20
drbdadm: new-minor r0: skipped due to earlier error
[Regression Potential]
* Very minor in this case as it adds a single flag to nla_put() attribute argument.
* Based in upstream patch fixing the issue, test case is fixed.
[Other Info]
* Original Case Description:
I am not able to bring drbd resource up after kernel upgrade (5.0 -> 5.3)
/sbin/drbdadm -v up amail
drbdsetup-84 new-resource amail
amail: Invalid argument
Command 'drbdsetup-84 new-resource amail' terminated with exit code 20
drbdadm: new-minor amail: skipped due to earlier error
it maybe this issue:
https://www.mail-archive.com/openembedded-devel@lists.openembedded.org/msg64900.html
but not tested by me
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: drbd-utils 8.9.10-2
ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
Date: Sat Mar 7 13:39:39 2020
Dependencies:
gcc-8-base 8.3.0-6ubuntu1~18.04.1
libc6 2.27-3ubuntu1
libgcc1 1:8.3.0-6ubuntu1~18.04.1
libstdc++6 8.3.0-6ubuntu1~18.04.1
lsb-base 9.20170808ubuntu1
InstallationDate: Installed on 2019-10-22 (136 days ago)
InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
SourcePackage: drbd-utils
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.drbd.d.global_common.conf: 2019-12-05T11:34:58.322390 |
|
| 2020-03-10 10:42:29 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/drbd-utils/+git/drbd-utils/+merge/380476 |
|
| 2020-03-11 17:56:09 |
Robie Basak |
bug |
|
|
added subscriber Robie Basak |
| 2020-03-11 18:23:42 |
Robie Basak |
description |
[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 /etc/drbd.d/r0.res
resource r0 {
protocol C;
startup {
wfc-timeout 15;
degr-wfc-timeout 60;
}
net {
cram-hmac-alg sha1;
shared-secret "secret";
}
on drbdfix {
device /dev/drbd0;
disk /dev/loop0;
address 10.250.99.202:7788;
meta-disk internal;
}
on drbdnon {
device /dev/drbd0;
disk /dev/loop0;
address 192.168.0.2:7788;
meta-disk internal;
}
}
* Check that with kernel 5.0.0 drbdadm command works fine for the configured resource:
$ uname -a
Linux drbdfix 5.0.0-43-generic #47~18.04.1-Ubuntu SMP Mon Mar 2 04:28:21 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
$ sudo drbdadm create-md r0
initializing activity log
NOT initializing bitmap
Writing meta data...
New drbd meta data block successfully created.
$ sudo drbdadm -v up r0
drbdsetup-84 new-resource r0
drbdsetup-84 new-minor r0 0 0
drbdmeta 0 v08 /dev/loop0 internal apply-al
drbdsetup-84 attach 0 /dev/loop0 /dev/loop0 internal
drbdsetup-84 connect r0 ipv4:10.250.99.202:7788 ipv4:192.168.0.2:7788 --protocol=C --cram-hmac-alg=sha1 --shared-secret=secret
* And with kernel 5.3.0 it does not:
$ uname -a
Linux drbdfix 5.3.0-42-generic #34~18.04.1-Ubuntu SMP Fri Feb 28 13:42:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
$ sudo drbdadm -v up r0
drbdsetup-84 new-resource r0
r0: Invalid argument
Command 'drbdsetup-84 new-resource r0' terminated with exit code 20
drbdadm: new-minor r0: skipped due to earlier error
[Regression Potential]
* Very minor in this case as it adds a single flag to nla_put() attribute argument.
* Based in upstream patch fixing the issue, test case is fixed.
[Other Info]
* Original Case Description:
I am not able to bring drbd resource up after kernel upgrade (5.0 -> 5.3)
/sbin/drbdadm -v up amail
drbdsetup-84 new-resource amail
amail: Invalid argument
Command 'drbdsetup-84 new-resource amail' terminated with exit code 20
drbdadm: new-minor amail: skipped due to earlier error
it maybe this issue:
https://www.mail-archive.com/openembedded-devel@lists.openembedded.org/msg64900.html
but not tested by me
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: drbd-utils 8.9.10-2
ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
Date: Sat Mar 7 13:39:39 2020
Dependencies:
gcc-8-base 8.3.0-6ubuntu1~18.04.1
libc6 2.27-3ubuntu1
libgcc1 1:8.3.0-6ubuntu1~18.04.1
libstdc++6 8.3.0-6ubuntu1~18.04.1
lsb-base 9.20170808ubuntu1
InstallationDate: Installed on 2019-10-22 (136 days ago)
InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
SourcePackage: drbd-utils
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.drbd.d.global_common.conf: 2019-12-05T11:34:58.322390 |
[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 /etc/drbd.d/r0.res
resource r0 {
protocol C;
startup {
wfc-timeout 15;
degr-wfc-timeout 60;
}
net {
cram-hmac-alg sha1;
shared-secret "secret";
}
on drbdfix {
device /dev/drbd0;
disk /dev/loop0;
address 10.250.99.202:7788;
meta-disk internal;
}
on drbdnon {
device /dev/drbd0;
disk /dev/loop0;
address 192.168.0.2:7788;
meta-disk internal;
}
}
* Check that with kernel 5.0.0 drbdadm command works fine for the configured resource:
$ uname -a
Linux drbdfix 5.0.0-43-generic #47~18.04.1-Ubuntu SMP Mon Mar 2 04:28:21 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
$ sudo drbdadm create-md r0
initializing activity log
NOT initializing bitmap
Writing meta data...
New drbd meta data block successfully created.
$ sudo drbdadm -v up r0
drbdsetup-84 new-resource r0
drbdsetup-84 new-minor r0 0 0
drbdmeta 0 v08 /dev/loop0 internal apply-al
drbdsetup-84 attach 0 /dev/loop0 /dev/loop0 internal
drbdsetup-84 connect r0 ipv4:10.250.99.202:7788 ipv4:192.168.0.2:7788 --protocol=C --cram-hmac-alg=sha1 --shared-secret=secret
* And with kernel 5.3.0 it does not:
$ uname -a
Linux drbdfix 5.3.0-42-generic #34~18.04.1-Ubuntu SMP Fri Feb 28 13:42:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
$ sudo drbdadm -v up r0
drbdsetup-84 new-resource r0
r0: Invalid argument
Command 'drbdsetup-84 new-resource r0' terminated with exit code 20
drbdadm: new-minor r0: skipped due to earlier error
[Regression Potential]
* Very minor in this case as it adds a single flag to nla_put() attribute argument.
* Based in upstream patch fixing the issue, test case is fixed.
* [racb] Older kernels still supported in affected Ubuntu releases may not understand the new flag, causing unexpected failure or other unexpected behaviour. #ifndef doesn't mitigate this since the new flag constant would be available at build time (we only build one src:drbd-utils for all kernels and don't ship a different set of binary packages per kernel).
[Other Info]
* Original Case Description:
I am not able to bring drbd resource up after kernel upgrade (5.0 -> 5.3)
/sbin/drbdadm -v up amail
drbdsetup-84 new-resource amail
amail: Invalid argument
Command 'drbdsetup-84 new-resource amail' terminated with exit code 20
drbdadm: new-minor amail: skipped due to earlier error
it maybe this issue:
https://www.mail-archive.com/openembedded-devel@lists.openembedded.org/msg64900.html
but not tested by me
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: drbd-utils 8.9.10-2
ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
Date: Sat Mar 7 13:39:39 2020
Dependencies:
gcc-8-base 8.3.0-6ubuntu1~18.04.1
libc6 2.27-3ubuntu1
libgcc1 1:8.3.0-6ubuntu1~18.04.1
libstdc++6 8.3.0-6ubuntu1~18.04.1
lsb-base 9.20170808ubuntu1
InstallationDate: Installed on 2019-10-22 (136 days ago)
InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
SourcePackage: drbd-utils
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.drbd.d.global_common.conf: 2019-12-05T11:34:58.322390 |
|
| 2020-03-19 15:47:22 |
Robie Basak |
drbd-utils (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2020-03-19 15:47:25 |
Robie Basak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-03-19 15:47:26 |
Robie Basak |
bug |
|
|
added subscriber SRU Verification |
| 2020-03-19 15:47:31 |
Robie Basak |
tags |
amd64 apport-bug bionic server-next |
amd64 apport-bug bionic server-next verification-needed verification-needed-bionic |
|
| 2020-03-27 22:49:35 |
Rafael David Tinoco |
tags |
amd64 apport-bug bionic server-next verification-needed verification-needed-bionic |
amd64 apport-bug bionic server-next verification-done verification-done-bionic |
|
| 2020-03-30 12:48:24 |
Launchpad Janitor |
drbd-utils (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2020-03-30 12:48:29 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
