Disabling HugePages after enabling them causes UPF not to start

[dariofaccin]

Describe the bug

After enabling HugePages in UPF using the library and them disabling them, one container of UPF charm (bessd) never gets ready, as the process started by pebble gets killed shortly after starting it. This is caused by a wrong memory limit enforcement made by the library.

To Reproduce

1. Deploy sdcore-upf-operator
2. Enable HugePages: juju config sdcore-upf-operator enable-hugepages=True
3. Wait for units to settle down
4. Disable HugePages: juju config sdcore-upf-operator enable-hugepages=False

Expected behavior

UPF charm should be active.

Logs

No relevant logs are present, however bessd gets killed shortly after the startup.

Environment

• Charm / library version (if relevant): 0.1
• Juju version (output from juju --version): 3.1.6-genericlinux-amd64
• Cloud Environment:
• Kubernetes version (output from kubectl version --short): v1.27.6

Additional context

Issue is caused by forcing memory: 512Mi in resource requirements (limits and requests). Increasing it to 1Gi solves the issue.

[dariofaccin]

Fixed by PR #21