Skip to content
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

Closed
wants to merge 7 commits into from

Conversation

nh2
Copy link
Contributor

@nh2 nh2 commented Sep 30, 2017

Motivation for this change

Cherry-pick of #29868 and #29062 (as planned in those tickets).

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • Linux
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

and


CC @bachp

…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)
@nh2 nh2 changed the base branch from master to release-17.09 September 30, 2017 13:27
@peti peti removed their request for review September 30, 2017 13:36
@joachifm joachifm added the 8.has: port to stable A PR already has a backport to the stable release. label Sep 30, 2017
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" ];
Copy link
Member

@bachp bachp Oct 1, 2017

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

Copy link
Contributor Author

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!

bachp and others added 5 commits October 3, 2017 11:14
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)
@nh2 nh2 force-pushed the glusterfs-1.2-release-17.09 branch from a9ce8ec to 2fb4e64 Compare October 3, 2017 09:14
@nh2
Copy link
Contributor Author

nh2 commented Oct 3, 2017

I've cherry-picked @bachp's fix for the above mentioned issue.

This is ready to land now.

@copumpkin copumpkin removed their request for review October 3, 2017 18:21
@nh2
Copy link
Contributor Author

nh2 commented Oct 4, 2017

CC @joachifm who merged the master equivalents for us

@joachifm
Copy link
Contributor

joachifm commented Oct 4, 2017

Deferring to @fpletz

@FRidh
Copy link
Member

FRidh commented Oct 7, 2017

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?

@FRidh FRidh requested a review from 7c6f434c October 7, 2017 09:34
@FRidh
Copy link
Member

FRidh commented Oct 7, 2017

Note that the service does not have a maintainer. I think it should be added (on master, first).

@7c6f434c
Copy link
Member

7c6f434c commented Oct 7, 2017

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.

@nh2
Copy link
Contributor Author

nh2 commented Oct 7, 2017

Yes, I'd be happy to maintain gluster for a while.

I have a gluster deployment based on the current release-* stable channel for which I care that it doesn't break, and I maintain nixops-gluster-example with which changes to package + service, as well as version upgrades, can be publicly tested.

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.

@bachp
Copy link
Member

bachp commented Oct 7, 2017

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.
I think @nh2 you did a very good job so far improving gluster support in NixOS. I would also like to see a test for glusterfs that is based on the nixops setup mentioned above.

@nh2
Copy link
Contributor Author

nh2 commented Oct 22, 2017

Uh I have some confusion here.

The PR is still open but I noticed that its commits have landed on release-17.09 by now, for example 1be7119

I noticed this only by the Github info message here:

fpletz added a commit that referenced this pull request 8 days ago

I'm of course OK with those picks since I requested them here, but I do have two questions about it:

  • The first one probably to @fpletz: How comes the individual commits are interleaved with other commits, as opposed to be one after the other like in the PR? Is there some tooling involved that I don't know about yet?
  • How can I learn that such picks happened, so that I can do cleanup actions like close this PR?

(I also noticed that I typoed the PR title to glusterfs 1.2 instead of 3.12, will fix that now.)

@nh2 nh2 changed the title glusterfs: Glusterfs 1.2 and service cherry-picks glusterfs: Glusterfs 3.12 and service cherry-picks Oct 22, 2017
@fpletz
Copy link
Member

fpletz commented Oct 23, 2017

@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 fpletz closed this Oct 23, 2017
@nh2
Copy link
Contributor Author

nh2 commented Oct 23, 2017

@fpletz OK, thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
8.has: port to stable A PR already has a backport to the stable release.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants