Complete
Details
Assignee
CalebCalebReporter
ksimm1ksimm1Labels
Original estimate
Time remaining
0mComponents
Fix versions
Affects versions
Priority
Low
Details
Details
Assignee
Caleb
CalebReporter
ksimm1
ksimm1Labels
Original estimate
Time remaining
0m
Components
Fix versions
Affects versions
Priority
Katalon Platform
Katalon Platform
Katalon Platform
Created January 3, 2023 at 6:43 PM
Updated February 27, 2025 at 10:12 PM
Resolved January 13, 2023 at 6:30 PM
Sysctl values entered in Angelfish under System Settings -> advanced -> Sysctl will appear in Bluefin, but the values set are ignored not respected. Editing and hitting save also does not update the value.
In order to have the sysctl value persisted you need to recreate the sysctl entry.
I noticed that the case for "Type" on the sysctl entries differs. The ones entered in angelfish are lowercase "sysctl", the ones recreated in bluefin are "SYSCTL" (see screenshot)
to reproduce
1) Add a sysctl value that is not default in angelfish 22.02.4 under settings -> advanced -> sysctl (like "fs.inotify.max_user_instances" = 512) and hit save
2). Confirm the value has been updated by running sysctl fs.inotify.max_user_instances in shell
3.) Upgrade to bluefin
4.) Verify the sysctl entry is still there under settings -> advanced -> sysctl
5) Confirm the value is no longer equal to 512 by running sysctl fs.inotify.max_user_instances in shell
7) Edit sysctl entry under settings -> advanced ->sysctl and hit save
8) Confirm the value still hasn't changed by running sysctl fs.inotify.max_user_instances in shell
9) Delete the sysctl entry and recreate it.
10) Verify the value is persisted in shell