Issue present in 1.4.0 tested with Supermicro SOL on ttyS1.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Nov 27 2024
Nov 20 2024
Nov 8 2024
Oct 14 2024
Sep 16 2024
Sep 15 2024
Jun 20 2024
May 13 2024
May 7 2024
Feb 10 2024
Jan 20 2024
Close it as wonftfix for 1.2.x and works for 1.3.5
vyos@r1# set system syslog host 192.168.122.1 [edit] vyos@r1# commit [ system syslog ] Invalid facility set in hosts 192.168.122.1
1.2.x not more maintained
Jan 9 2024
No longer reproducible, the underscore is displayed as expected.
Crux is unsupported now.
No one complained about this issue in a while, but feel free to reopen, if anything.
Jan 8 2024
1.2 is now EOL, so no new changes will be made there.
Dec 18 2023
Dec 17 2023
Sep 17 2023
Aug 28 2023
we have a version updated , this case should be closed:
azureuser@vyos-support:~$ sudo /usr/sbin/waagent -version WALinuxAgent-2.2.45 running on debian 10.12 Python: 3.7.3 Goal state agent: 2.2.45
Aug 25 2023
Jul 13 2023
Jul 12 2023
Jul 11 2023
May 23 2023
Oct 13 2022
Sep 29 2022
Sorted out the WARNING: terminal is not fully functional message with adding the following export command: -
Yeah, that new nightly release has fixed the issue, thanks. Strangely now getting some weird message in my show commands (WARNING: terminal is not fully functional). This message wasn't there on the previous nightly.
Aug 29 2022
Jul 8 2022
In T2664#126031, @Viacheslav wrote:As we have the 1.3 LTS release (where it is fixed) I propose to close it.
It is a big change for 1.2 that we should avoid.
As we have the 1.3 LTS release (where it is fixed) I propose to close it.
It is a big change for 1.2 that we should avoid.
Feb 7 2022
Jan 26 2022
We confirmed the problem - some serial consoles continue to work well, some are not initialized properly with the --keep-baud option. For example, this can be reproduced in the SOS console in Equinix Metal.
Originally, the problem comes from a systemd service template.
Since it is not completely clear if the option is necessary in one case or another, it seems that the best solution would be to provide the ability to set/remove it from the CLI, so everyone may configure what works best for his hardware.