-
Notifications
You must be signed in to change notification settings - Fork 121
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
xsos --ipv6 doesn't produce expected content #272
Comments
Sidebar - I've always wondered why the --ipv6 | -6 options exist since the --ip | -i option outputs the IPv6 information already. I had expected the --ipv6 | -6 options to, in effect, toggle the --ip | -i options' output to display IPv6 addresses instead of IPv4. |
On a related note (I believe)... something else definitely amiss with the IPv6 output... Looking at sos_commands/networking/ip_-d_address from my SOS Report I see:
Note this has no IPv6 address, i.e. this expression at line 2530 should return false:
Neither virbr0 and virbr0-nic have inet6 text: $ grep virbr0 -A99 sos_commands/networking/ip_-d_address | grep inet6 -c and yet they both appear in the IPv6 output... $ xsos -i --scrub . IP6 |
Cloned the latest code just to make sure not caused by outdated source code:
So the help implies that passing -6 or --ipv6 will generate output for IPv6 addresses as opposed to v4, but instead you get nothing of the sort. Consider the following (I scrubbed the content because it has come from a customer's server):
$ xsos --scrub --ip .
IP4
Interface Master IF MAC Address MTU State IPv4 Address
========= ========= ================= ====== ===== ==================
lo - - 65536 up ⣿⣿⣿.⣿⣿⣿.⣿⣿⣿.⣿⣿⣿/⣿⣿
ens192 - ⣿⣿:⣿⣿:⣿⣿:⣿⣿:⣿⣿:⣿⣿ 1500 up ⣿⣿⣿.⣿⣿⣿.⣿⣿⣿.⣿⣿⣿/⣿⣿
ens224 - ⣿⣿:⣿⣿:⣿⣿:⣿⣿:⣿⣿:⣿⣿ 1500 up ⣿⣿⣿.⣿⣿⣿.⣿⣿⣿.⣿⣿⣿/⣿⣿
IP6
Interface Master IF MAC Address MTU State IPv6 Address Scope
========= ========= ================= ====== ===== =========================================== =====
lo - - 65536 up - -
ens192 - ⣿⣿:⣿⣿:⣿⣿:⣿⣿:⣿⣿:⣿⣿ 1500 up - -
ens224 - ⣿⣿:⣿⣿:⣿⣿:⣿⣿:⣿⣿:⣿⣿ 1500 up - -
$ xsos --scrub --ipv6 .
OS
Hostname: SCRUBBED
Distro: [redhat-release] Red Hat Enterprise Linux Server release 7.9 (Maipo)
[os-release] Red Hat Enterprise Linux Server 7.9 (Maipo) 7.9 (Maipo)
RHN: serverURL = SCRUBBED
enableProxy = 0
RHSM: hostname = SCRUBBED
proxy_hostname =
YUM: 4 enabled plugins: langpacks, product-id, search-disabled-repos, subscription-manager
SELinux: disabled (default disabled)
Arch: mach=x86_64 cpu=x86_64 platform=x86_64
Kernel:
Booted kernel: 3.10.0-1160.42.2.el7.x86_64
GRUB default: 3.10.0-1160.42.2.el7.x86_64
Build version:
Linux version 3.10.0-1160.42.2.el7.x86_64 (mockbuild@x86-vm-40.build.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-44) (GCC) ) #1 SMP Tue Aug 31 20:15:00 UTC
2021
Booted kernel cmdline:
Sys time: Thu Feb 3 20:08:31 CET 2022
Boot time: Sun Dec 12 21:40:17 CET 2021 (epoch: 1639341617)
Time Zone: Europe/Brussels
Uptime: 52 days, 22:28, 2 users
LoadAvg: [4 CPU] 3.15 (79%), 1.57 (39%), 0.83 (21%)
/proc/stat:
procs_running: 8 procs_blocked: 1 processes [Since boot]: 65257276
cpu [Utilization since boot]:
us 5%, ni 0%, sys 2%, idle 92%, iowait 0%, irq 0%, sftirq 0%, steal 0%
sed: -e expression #1, char 40: unterminated `s' command
I suspect it has to do with this "sed" error at the bottom. I avoided trying to insert this second output as "code" because it contains grave accents and that seems to mess up the post's formatting.
/SenseiC
The text was updated successfully, but these errors were encountered: