You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using kernel_parameter in the test and it fails then the message is missing detailed explanation what actually failed - unless you have insanely detailed tests.
InSpec and Platform Version
Tinspec 0.32.0
ubuntu 15.10 testing remotely on 14.04
Replication Case
title'test kernel_parameter'control'test-kernel_parameter-999'doimpact1.0title'verify certain settings in sysctl'desc'tuning system/kernel'describekernel_parameter('net.core.somaxconn')doits('value'){shouldbe >= 18419238472}# this should fail some random insane value to make it invalidenddescribekernel_parameter('net.core.somaxconn')doits('value'){shouldbe > 100}# this should passendend
output:
✖ test-kernel_parameter-999: verify certain settings in sysctl (1 failed)
✖ expected: >= 18419238472
got: 128
✔ Kernel Parameter net.core.somaxconn value should be > 100
As we can see:
first one fails, but does not say that it refers to net.core.somaxconn
second test shows that net.core.somaxconn is valid.
Possible Solutions
Verify that kernel_parameter actually shows full output when it fails.
Expected output something like this:
✖ test-kernel_parameter-999: verify certain settings in sysctl (1 failed)
✖ expected: net.core.somaxconn >= 18419238472
got: 128
✔ Kernel Parameter net.core.somaxconn value should be > 100
Stacktrace
No stacktrace.
The text was updated successfully, but these errors were encountered:
Description
When using
kernel_parameter
in the test and it fails then the message is missing detailed explanation what actually failed - unless you have insanely detailed tests.InSpec and Platform Version
Tinspec 0.32.0
ubuntu 15.10 testing remotely on 14.04
Replication Case
output:
As we can see:
net.core.somaxconn
net.core.somaxconn
is valid.Possible Solutions
Verify that
kernel_parameter actually
shows full output when it fails.Expected output something like this:
Stacktrace
No stacktrace.
The text was updated successfully, but these errors were encountered: