Satellite does not support the following layers: [DRBD]

[bratao]

Hello,

I did a install using the helm and tried to initialize a Persistent Volume using the piraeus-dflt-r1 class. But the volume is never created. Analyzing the controller I can see the following error:

Suppressed exception 1 of 2:
===============
Category:                           RuntimeException
Class name:                         OnAssemblyException
Class canonical name:               reactor.core.publisher.FluxOnAssembly.OnAssemblyException
Generated at:                       <UNKNOWN>

Error message:                      Assembly site of producer [reactor.core.publisher.MonoFlatMapMany] is identified by light checkpoint [Auto-place resource including thin pools].Error has been observed by the following operator(s):
        |_      Assembly site of producer [reactor.core.publisher.MonoFlatMapMany] is identified by light checkpoint [Auto-place resource].


Error context:
    Satellite 'ubuntu-1804-bionic-64-minimal' does not support the following layers: [DRBD]

Call backtrace:

    Method                                   Native Class:Line number

Suppressed exception 2 of 2:
===============
Category:                           Exception
Class name:                         SnapshotStackException
Class canonical name:               reactor.core.publisher.FluxOnAssembly.SnapshotStackException
Generated at:                       <UNKNOWN>

Error message:                      Auto-place resource

Error context:
    Satellite 'ubuntu-1804-bionic-64-minimal' does not support the following layers: [DRBD]

Call backtrace:

    Method                                   Native Class:Line number


END OF ERROR REPORT.

The host is a metal dedicated server, running the Ubuntu 18.04. Do I need to do any specific configuration to enable piraeus?

[bratao]

Look at the created piraeus-node, I can see the following log:

LINSTOR, Module Satellite

Version:            1.4.2 (974dfcad291e1f683941ada3d7e7337821060349)

Build time:         2020-01-27T11:15:32+00:00

Java Version:       11

Java VM:            Debian, Version 11.0.6+10-post-Debian-1deb10u1

Operating system:   Linux, Version 4.15.0-88-generic

Environment:        amd64, 1 processors, 121 MiB memory reserved for allocations

System components initialization in progress

02:14:41.240 [main] INFO  LINSTOR/Satellite - SYSTEM - Log directory set to: '/var/log/linstor-satellite'

02:14:41.248 [main] INFO  LINSTOR/Satellite - SYSTEM - Linstor satellite configuration file not found, using defaults.

02:14:41.248 [Main] INFO  LINSTOR/Satellite - SYSTEM - Loading API classes started.

02:14:45.243 [Main] INFO  LINSTOR/Satellite - SYSTEM - API classes loading finished: 3994ms

02:14:45.244 [Main] INFO  LINSTOR/Satellite - SYSTEM - Dependency injection started.

WARNING: An illegal reflective access operation has occurred

WARNING: Illegal reflective access by com.google.inject.internal.cglib.core.$ReflectUtils$1 (file:/usr/share/linstor-server/lib/guice-4.2.2.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)

WARNING: Please consider reporting this to the maintainers of com.google.inject.internal.cglib.core.$ReflectUtils$1

WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations

WARNING: All illegal access operations will be denied in a future release

02:14:56.955 [Main] INFO  LINSTOR/Satellite - SYSTEM - Dependency injection finished: 11711ms

02:14:59.145 [Main] INFO  LINSTOR/Satellite - SYSTEM - Starting service instance 'DeviceManager' of type DeviceManager

02:14:59.145 [Main] INFO  LINSTOR/Satellite - SYSTEM - Starting service instance 'FileEventService' of type FileEventService

02:14:59.146 [Main] INFO  LINSTOR/Satellite - SYSTEM - Starting service instance 'TimerEventService' of type TimerEventService

02:14:59.147 [Main] INFO  LINSTOR/Satellite - SYSTEM - Initializing main network communications service

02:14:59.248 [Main] INFO  LINSTOR/Satellite - SYSTEM - NetComService started on port /0:0:0:0:0:0:0:0:3366

02:15:09.850 [MainWorkerPool-1] INFO  LINSTOR/Satellite - SYSTEM - Controller connected and authenticated (138.201.175.14:5318)

02:15:10.358 [MainWorkerPool-1] INFO  LINSTOR/Satellite - SYSTEM - Node 'ubuntu-1804-bionic-64-minimal' created.

02:15:10.359 [MainWorkerPool-1] INFO  LINSTOR/Satellite - SYSTEM - Storage pool 'DfltDisklessStorPool' created.

02:15:10.360 [MainWorkerPool-1] INFO  LINSTOR/Satellite - SYSTEM - Storage pool 'DfltStorPool' created

[bratao]

One thing I noticed is that the actual all.yaml point to the image image: quay.io/piraeusdatastore/piraeus-server:v1.4.2 while the version 1.5.2 already exists.

[alexzhc]

We are waiting 1.5.x to fix an issue before updating yaml with it.

The reason you cannot use drbd layer might be that piraeus-init fails to update drbd kernel module to version 9 in your os, which seems to be a minimally installed ubuntu. As stated clearly in piraeus readme that, you need to have kernel source in your os for that to happen.

# CentOS/RHEL
yum install  -y kernel-devel-$(uname -r)
# Ubuntu
apt-get install -y  linux-headers-$(uname -r)

If you have it right, after piraeus nodes comes up, you should see

$ modinfo drbd
filename:       /lib/modules/3.10.0-693.21.1.el7.x86_64/updates/drbd.ko
alias:          block-major-147-*
license:        GPL
version:        9.0.21-1
description:    drbd - Distributed Replicated Block Device v9.0.21-1
author:         Philipp Reisner <phil@linbit.com>, Lars Ellenberg <lars@linbit.com>
retpoline:      Y
rhelversion:    7.4
srcversion:     488539B76FE232A2167DCA1
depends:        libcrc32c
vermagic:       3.10.0-693.21.1.el7.x86_64 SMP mod_unload modversions
parm:           enable_faults:int
parm:           fault_rate:int
parm:           fault_count:int
parm:           fault_devs:int
parm:           disable_sendpage:bool
parm:           allow_oos:DONT USE! (bool)
parm:           minor_count:Approximate number of drbd devices (1-255) (uint)
parm:           usermode_helper:string
parm:           protocol_version_min:drbd_protocol_version

[alexzhc]

welcome to our slack channel

[bratao]

Thanks. I rebuild the nodes, and used the version 1.5.2 and it works!