The workaround described above works. Changed it to following line and added few more system-users spotted in the AAA daemon logs:
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Oct 12 2024
Oct 11 2024
Oct 10 2024
ETICKET, sorry.
Oct 8 2024
Can you check if changing this line https://github.com/vyos/vyos-1x/blob/current/data/templates/login/tacplus_nss.conf.j2#L33 and adding those user helps?
This file can be changed locally in the router: /usr/share/vyos/templates/login/tacplus_nss.conf.j2
Change line:
exclude_users=root,telegraf,radvd,strongswan,tftp,conservr,frr,ocserv,pdns,_chrony,_lldpd,sshd,openvpn,radius_user,radius_priv_user,*{{ ',' + user | join(',') if user is vyos_defined }}And change it to something like:
Oct 7 2024
If the device is not even listing in lspci it's more of a Hyper-V thing then VyOS.
Oct 6 2024
Oct 5 2024
basic node_exporter finish, now i work on https://github.com/tynany/frr_exporter
Oct 4 2024
Oct 3 2024
Oct 2 2024
Drivers seem to be present, but device is not even appearing in lspci. Wouldn't this be more likely due to a hyper-v driver issue than the mellanox driver?
Sep 30 2024
Sep 29 2024
I can not immediately recreate the issue:
Sep 28 2024
Sep 25 2024
PR to follow tests and migration script:
https://github.com/vyos/vyos-1x/compare/current...jestabro:distinct-api
Sep 23 2024
Sep 22 2024
PR ready for review:
https://github.com/vyos/vyos-1x/pull/3876
Sep 21 2024
Sep 20 2024
Sep 19 2024
Smoketest fails for the wireless interfaces
DEBUG - ======================================================================
DEBUG - FAIL: test_wireless_add_single_ip_address (__main__.WirelessInterfaceTest.test_wireless_add_single_ip_address)
DEBUG - ----------------------------------------------------------------------
DEBUG - Traceback (most recent call last):
DEBUG - File "/usr/libexec/vyos/tests/smoke/cli/test_interfaces_wireless.py", line 84, in test_wireless_add_single_ip_address
DEBUG - self.assertTrue(process_named_running('wpa_supplicant'))
DEBUG - AssertionError: None is not trueSep 17 2024
I am not yet able to reproduce this in either case. @c-po suggestion of an interaction with the introduction of vyos.utils.configfs is quite reasonable, but I have not reproduced in current rolling or an image earlier than the recent changes (T6633, T6640) to resolve T6639. I've asked the forum user of the second report for further information.