-
Notifications
You must be signed in to change notification settings - Fork 26
[DPE-7691] Bump snap revision to 197/198 to use _daemon_ (584792) #1024
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
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## 16/edge #1024 +/- ##
========================================
Coverage 70.29% 70.29%
========================================
Files 16 16
Lines 3807 3807
Branches 545 545
========================================
Hits 2676 2676
Misses 1001 1001
Partials 130 130 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
0af9e2c
to
dd46399
Compare
Reasoning: * Use _daemon_ (UID:584792) instead of snap_daemon (UID:584788) See: https://forum.snapcraft.io/t/system-usernames/13386 * Stop creating $SNAP_COMMON/data/db (unnecessary) + polishing * add postgresql-16-repack * temporary disable upgrade tests due to snap user change
dd46399
to
270c2bb
Compare
subprocess.check_call(["mkdir", "-p", "/home/_daemon_"]) # noqa: S607 | ||
subprocess.check_call(["chown", "_daemon_:_daemon_", "/home/_daemon_"]) # noqa: S607 | ||
subprocess.check_call(["usermod", "-d", "/home/_daemon_", "_daemon_"]) # noqa: S607 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It smells a bit, and might be no longer necessary (AFAIK it was some snap workaround)... but let's test it AS IS for now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's still needed, as long as we switch user to _daemon_
.
_check_call.assert_any_call(["mkdir", "-p", "/home/_daemon_"]) | ||
_check_call.assert_any_call(["chown", "_daemon_:_daemon_", "/home/_daemon_"]) | ||
_check_call.assert_any_call(["usermod", "-d", "/home/_daemon_", "_daemon_"]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same as above.
systems: | ||
- -ubuntu-24.04 | ||
- -ubuntu-24.04-arm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will be reverted after merge and edge publishing.
Issue
The snap user
snap_daemon
has been deprecated by SNAP team,see: https://forum.snapcraft.io/t/system-usernames/13386
Also the newer charmed-postgresql snap is available with new parts there.
Solution
_daemon_
(UID:584792) instead ofsnap_daemon
(UID:584788)Tests will be re-enabled after releasing to edge, as we do not
provide upgrade path for snap ownership changes.
Upgrade path is unnecessary here, as it is a first stable release to PG16 charm.
Checklist