What happened:
I try to get Hugepagesize for numa node

rootPath := "/"
p := printer.NewSvc(true)
meminfo := mem.NewInfoSvc(p, rootPath)

numaStatSvc := numa.NewStatSvc(p)
numaNodeSvc := numa.NewNodeSvc(meminfo, numaStatSvc)
numaSvc := numa.NewSvc(p, numaNodeSvc, rootPath)
data, _ := numaSvc.GetData()
for _, d := range data {
fmt.Printf("Node%v Hugepagesize = %v\n", d.ID, d.Memory.Hugepagesize)
}

Output is:

Node0 Hugepagesize = 0
Node1 Hugepagesize = 0

#  /proc/meminfo | grep Hugepagesize
Hugepagesize:       2048 kB
# /sys/devices/system/node/node*/meminfo | grep Hugepagesize <- no info about Hugepagesize

What you expected to happen:
May be get same as in /sys/devices/system/node/node*/meminfo file or get system default value?

A violation against the OSS Rules of Play has been detected.

Rule ID: rl-assigned_teams-5
Explanation: Does teams have enough members on GitHub? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html

A violation against the OSS Rules of Play has been detected.

Rule ID: rl-assigned_teams-4
Explanation: Does it have a team with push privileges on GitHub? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html

What Happened?
In example you can see unnecessary empty element "- {}" after CLI work.

    count: 2
    nics:
    - lldps:
      - {}
      - capabilities:
        - Bridge
        - Router
        chassisId: 68:21:5f:47:16:6e
        portDescription: Ethernet14
        portId: Eth4/3
        systemDescription: 'Debian GNU/Linux 10 (buster) Linux 4.19.0-6-2-amd64 #1
          SMP Debian 4.19.67-2+deb10u2 (2019-11-11) x86_64'
        systemName: frankfurt-leaf01
      macAddress: 1c:34:da:57:3a:a8
      mtu: 9216
      name: ens5f0np0
      ndps:
      - {}
      - ipAddress: fe80::6a21:5fff:fe47:166e
        macAddress: 68:21:5f:47:16:6e
        state: Stale
      pciAddress: "0000:06:00.0"
      speed: 25000

How it should be?
Without empty element.

Reason:
After some research i think i found a root cause:
LLDP - https://github.com/onmetal/inventory/blob/main/pkg/crd/svc.go#L362-L364
NDP - https://github.com/onmetal/inventory/blob/main/pkg/crd/svc.go#L382-L384

A violation against the OSS Rules of Play has been detected.

Rule ID: rl-reuse_tool-4
Explanation: Is it compliant with REUSE rules? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html

A violation against the OSS Rules of Play has been detected.

Rule ID: rl-reuse_tool-3
Explanation: Is it registered in REUSE? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html

A violation against the OSS Rules of Play has been detected.

Rule ID: rl-assigned_teams-2
Explanation: Does it have an admin team on GitHub? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html

A violation against the OSS Rules of Play has been detected.

Rule ID: rl-assigned_teams-3
Explanation: Does it have enough admins on GitHub? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html

What Happened?
Not valid PCI Address string on interface.

Example:

unable to save inventory resource: unhandled error on creation: Inventory.machine.onmetal.de "e8dee8c0-4984-11ea-af8b-0a94efa9371d" is invalid: spec.nics.nics.pciAddress: Invalid value: "1-1.6:1.0": spec.nics.nics.pciAddress in body should match '^([0-9a-fA-F]{4}:[0-9a-fA-F]{2}:[0-9a-fA-F]{2}.[0-9]{1})|([a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12})$'

How it should be?
Should ignore such interfaces.

@aiivashchenko what do you think about move labeling logic from this code to the k8s-inventory controller to have all labels in one place?
https://github.com/onmetal/inventory/blob/800902855ca7563bc0f9e695603cd2ea1d30e483/pkg/crd/svc.go#L434

A violation against the OSS Rules of Play has been detected.

Rule ID: rl-reuse_tool-1
Explanation: Does README mention REUSE? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html