-
Notifications
You must be signed in to change notification settings - Fork 565
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[testing] autopkgtests failure for report_disabled_parsers.py:ReportDisabledParsersTest.test_local_ip_not_obfuscated #3975
Comments
So, I've figured this out When creating new instances we have the following whether it's rocky, or ubuntu Hosts file
Use the pythonic way to get IP
Check the current ip addresses
So based on the above, the test would fail |
arif-ali
added a commit
to arif-ali/sos
that referenced
this issue
Apr 3, 2025
Running stageone tests in some environments sees the hostname of the machine to have an IP of 127.0.1.1 but the host is never set up in a way that this address is configured on the host. So if 127.0.1.1 is the one being detected, then ignore the test. Closes: sosreport#3975 Signed-off-by: Arif Ali <[email protected]>
6 tasks
arif-ali
added a commit
to arif-ali/sos
that referenced
this issue
Apr 4, 2025
Running stageone tests in some environments sees the hostname of the machine to have an IP of 127.0.1.1 but the host is never set up in a way that this address is configured on the host. We check for hostname.local, which ensures we get the address of the host rather than the alternative of 127.0.1.1. Closes: sosreport#3975 Signed-off-by: Arif Ali <[email protected]>
arif-ali
added a commit
to arif-ali/sos
that referenced
this issue
Apr 4, 2025
Running stageone tests in some environments sees the hostname of the machine to have an IP of 127.0.1.1 but the host is never set up in a way that this address is configured on the host. We check for hostname, if this returns a loopback address then we add .local to the end of the hostname, which ensures we get the address of the host. Closes: sosreport#3975 Signed-off-by: Arif Ali <[email protected]>
arif-ali
added a commit
to arif-ali/sos
that referenced
this issue
Apr 8, 2025
Running stageone tests in some environments sees the hostname of the machine to have an IP of 127.0.1.1 but the host is never set up in a way that this address is configured on the host. We use socket.connect to connect to a dummy address, which ensure to go via a default route and therefore not track the loopbak address. Then grabbing the IP of the socket give you a proper local IP address. Closes: sosreport#3975 Signed-off-by: Arif Ali <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In preparation of avocado landing in Debian and Ubuntu (which is due to land in a week or so), I have been doing some tests in our test environments, and we get the following issue
This issue has been created to track the issue so that it's not lost, and will form a fix soon.
Full Logs: https://autopkgtest.ubuntu.com/results/autopkgtest-plucky-arif-ali-sos-avocado/plucky/amd64/s/sos/20250324_192636_f5814@/log.gz#S5
The text was updated successfully, but these errors were encountered: