Closed j5k closed 1 year ago
Hi there! Welcome to the Salt Community! Thank you for making your first contribution. We have a lengthy process for issues and PRs. Someone from the Core Team will follow up as soon as possible. In the meantime, here’s some information that may help as you continue your Salt journey. Please be sure to review our Code of Conduct. Also, check out some of our community resources including:
There are lots of ways to get involved in our community. Every month, there are around a dozen opportunities to meet with other contributors and the Salt Core team and collaborate in real time. The best way to keep track is by subscribing to the Salt Community Events Calendar. If you have additional questions, email us at saltproject@vmware.com. We’re glad you’ve joined our community and look forward to doing awesome things with you!
You've cut off the end of the versions report.
What is the output of cat /proc/cmdline
?
# cat /etc/kernel/cmdline
rd.luks.name==luks rd.luks.options=rw,bgrt_disable root=/dev/mapper/luks rootflags=subvol=@root_2022-11-21_10-03-47 lockdown=confidentiality
System Versions:
dist: arch Timestamp: 2022-11-21 10:03 | Kernel: 6.0.9
locale: utf-8
machine: x86_64
release: 6.0.9-arch1-1
system: Linux
version: Arch Linux Timestamp: 2022-11-21 10:03 | Kernel: 6.0.9
/proc/cmdline
, not /etc/kernel/cmdline
It's the same.
That's odd then, because shlex_split
appears to parse it just fine.
What does that mean? Are the kernel parameters involved in some way here?
Yes, the stack trace indicates a failure to parse the kernel parameters, as if they contained a random quote character.
Okay I have to apologize! I looked again and saw characters, which I overlooked yesterday. There are random characters at the end and one of them is a quote. I regenerate my initial ramdisk (mkinitcpio
), but nothing changed. Where do these random characters come from?
I suspect that it is not a salt problem and close this issue. If you have some more suggestions, I am very open to it. Thanks!
I have asked directly in the arch forum: https://bbs.archlinux.org/viewtopic.php?id=281500
Workaround exists and fix on the way in systemd (https://github.com/systemd/systemd/pull/25222)
Description
salt-call
ends inValueError: No closing quotation
Setup
Steps to Reproduce the behavior
Expected behavior Run without error
Versions Report
salt --versions-report
```yaml Salt Version: Salt: 3005.1 Dependency Versions: cffi: 1.15.1 cherrypy: Not Installed dateutil: Not Installed docker-py: Not Installed gitdb: Not Installed gitpython: Not Installed Jinja2: 3.1.2 libgit2: Not Installed M2Crypto: 0.38.0 Mako: Not Installed msgpack: 1.0.4 msgpack-pure: Not Installed mysql-python: Not Installed pycparser: 2.21 pycrypto: Not Installed pycryptodome: 3.12.0 pygit2: Not Installed Python: 3.10.8 (main, Nov 1 2022, 14:18:21) [GCC 12.2.0] python-gnupg: Not Installed PyYAML: 6.0 PyZMQ: 24.0.1 smmap: Not Installed timelib: Not Installed Tornado: 4.5.3 ZMQ: 4.3.4 ```