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
Describe the bug
Defining a tcp test as "tcp:443" or as "tcp4:443"
Port 443 is listening on 0.0.0.0 (tcp4 only)
Goss reports this as "expected false to equal true"
This test worked prior to the 0.4.9 upgrade (version 0.3.20) when no ipv6 present
Could it be related to tcp6 (which is now enabled on this host)? However even using 'tcp4:80' I still get a fail
How To Reproduce
Have host with both ipv4 and ipv6 addresses
Have apache running listening on port 80, tcp4
verify connection (telnet localhost 80)
create goss rule
port:
tcp:80:
listening: true
Run goss test on this
See that it fails
Expected Behavior
The test should pass, as the port is being listened on and can be connected to by telnet
Actual Behavior
test failed, even though it passed under goss 0.3.20, and the port is definitely listening
Environment:
Version of goss
OS/Distribution version (if applicable)
The text was updated successfully, but these errors were encountered:
Describe the bug
Defining a tcp test as "tcp:443" or as "tcp4:443"
Port 443 is listening on 0.0.0.0 (tcp4 only)
Goss reports this as "expected false to equal true"
This test worked prior to the 0.4.9 upgrade (version 0.3.20) when no ipv6 present
Could it be related to tcp6 (which is now enabled on this host)? However even using 'tcp4:80' I still get a fail
How To Reproduce
Expected Behavior
The test should pass, as the port is being listened on and can be connected to by telnet
Actual Behavior
test failed, even though it passed under goss 0.3.20, and the port is definitely listening
Environment:
The text was updated successfully, but these errors were encountered: