[Bug 1866458] Re: drbd not working after kernel upgrade 5.0.x -> 5.3.x

[Rafael David Tinoco]

** 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 /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 
+ 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
+  * 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 at 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

-- 
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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/drbd-utils/+bug/1866458/+subscriptions