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
glusterfs: Glusterfs 3.12 and service cherry-picks #29952
Conversation
…get. This introduces dependency cycles. A network file system to be running is not required for a network connection to be available. NixOS@19759cf#commitcomment-22044519 (cherry picked from commit 5e2815d)
…mon. See also NixOS#22225 (review) (cherry picked from commit bd54b72)
after = [ "rpcbind.service" "network.target" "local-fs.target" ]; | ||
before = [ "network-online.target" ]; | ||
requires = lib.optional cfg.useRpcbind "rpcbind.service"; | ||
after = [ "network.target" "local-fs.target" ] ++ lib.optional cfg.useRpcbind [ "rpcbind.service" ]; |
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.
Must be after = [ "network.target" "local-fs.target" ] ++ lib.optional cfg.useRpcbind "rpcbind.service";
See: #29992
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.
Ah good catch, I thought I had fixed that already but the brackets are still there.
Thanks for fixing it!
(cherry picked from commit 2239dc6)
(cherry picked from commit e233a51)
Prevents glustereventsd failing at startup in case it starts before glusterd has started (whose `preStart` would also create the needed directory). (cherry picked from commit 08f7e45)
This is a better default for NixOS because it ensures that config changes happen fully when NixOS users expect it. (cherry picked from commit 18eecae)
Changes: * The patch `glusterfs-fix-unsubstituted-autoconf-macros` was deleted because the issue was fixed upstream: https://bugzilla.redhat.com/show_bug.cgi?id=1450588 * The `glusterd-ganesha.c` part of `glusterfs-use-PATH-instead-of-hardcodes` was detleted because `glusterd-ganesha.c` was removed upstream without replacement that has the relevant hardcoded paths. Closes NixOS#29062 (cherry picked from commit 8f40840)
a9ce8ec
to
2fb4e64
Compare
I've cherry-picked @bachp's fix for the above mentioned issue. This is ready to land now. |
CC @joachifm who merged the |
Deferring to @fpletz |
In my opinion its a bit too late for a bump like this to make it into stable, but I suppose if the maintainer, @7c6f434c , is fine with this, then it should be ok? |
Note that the service does not have a maintainer. I think it should be added (on master, first). |
The problem is that I don't use GlusterFS regularly nowadays, and I haven't used stable channels, hm, maybe not ever. (Looking at the list of fixes… hm, a crash… a corruption if some combination of factors happens…) Maybe there are enough bugfixes for a bump, I dunno. Looking at the file history, I would actually ask whether @nh2 wants to be added as the maintainer of both package and service. |
Yes, I'd be happy to maintain gluster for a while. I have a gluster deployment based on the current So far I know only of @bachp as another NixOS user of gluster, so I've CC'd him in the past so that he can review/test changes to be made. It would be nice to know if there are other users who depend on gluster so that those can be CC'd too. |
I think my usage of gluster is a lot simpler than @nh2. I currently don't use any declarative configuration of gluster volumes but mainly depend on the service to have the gluster daemons running. |
Uh I have some confusion here. The PR is still open but I noticed that its commits have landed on I noticed this only by the Github info message here:
I'm of course OK with those picks since I requested them here, but I do have two questions about it:
(I also noticed that I typoed the PR title to glusterfs |
@nh2 As release manager, I regularly go through the changes in master and pick relevant fixes to the release branch. Unfortunately, I was a bit busy the last few weeks so I wasn't also monitoring incoming pull requests. Sorry about that. There isn't any kind of notification from github when commits are picked. However, if a PR or issue is mentioned in the commit message, cherry-picking the commit triggers a message. No notification via email, though. After trying to merge this, there is no diff to release-17.09, so we can safely close this. Thanks a lot for your efforts! |
@fpletz OK, thank you! |
Motivation for this change
Cherry-pick of #29868 and #29062 (as planned in those tickets).
Things done
build-use-sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)and
CC @bachp