-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Mask swap.target doesn't take effect after reboot #10741
Comments
Odd. What's in |
So I checked that swap.target could indeed be masked to disable swap devices of any kind, (just to see if I was not crazy), it does work on some systems ™️ .
So, next steps:
- what's your systemd version
- could you add the results of `systemctl cat <your-swap-unit>` and `systemctl show <your-swap-unit>` (you should be able to find them by using `systemctl --type swap`)
Also, please post text and not images, it's harder to read.
|
|
can reproduce it CENTOS_MANTISBT_PROJECT="CentOS-7" possible solution is to mask every swap unit file
on a more recent system there are no unit files generated after the swap target got masked |
Can you quote the unit name / escape the (And I forgot last time: could you also post the result of
No unit files or not started ? AFAIK they should be generated by fstab-generator, just not started. |
@VannTen I post some details. systemctl cat dev-mapper-centos\x2dswap.swap
systemctl show "dev-mapper-centos\x2dswap.swap"
systemctl status "dev-mapper-centos\x2dswap.swap"
journalctl -xu swap.target
|
I found that swap partition would still be actived after masking swap.target and rebooting.
Related to #10587
Environment:
Cloud provider or hardware configuration:
OS (
printf "$(uname -srm)\n$(cat /etc/os-release)\n"
):Version of Ansible (
ansible --version
):Version of Python (
python --version
):Kubespray version (commit) (
git rev-parse --short HEAD
):Network plugin used:
Full inventory with variables (
ansible -i inventory/sample/inventory.ini all -m debug -a "var=hostvars[inventory_hostname]"
):Command used to invoke ansible:
Output of ansible run:
Anything else do we need to know:
The text was updated successfully, but these errors were encountered: