-
Notifications
You must be signed in to change notification settings - Fork 107
Can no longer highstate without using the /tmp override #793
Comments
I checked via
So it looks like the error is related to Salt (or rather git-python) not being able to parse GPG signed git commits. Looking at recent commits, it seems 1f62195 is the first time we see a signed merge commit. This was not triggered by previous signed commits, because those would be commits on a branch, and not merge commits created by Homu, so they would never be at the tip of master, and thus never parsed by git-python. Looking at the git-python issue tracker for gpg related issues (as well as the git-python source as of We could install via pip globally for a short term fix, but a long term fix is probably to update to xenial (#462), which has version 1.0.1 - not the newest but new enough for the GPG support, seemingly added in 0.3. Side question: How is Homu making merge commits that are signed with your key @jdm? I don't know how it would do that without access to your private GPG key. |
Fascinating; the web UI for editing files on github signs the resulting commits apparently. It's still not clear how that propagates to homu's merge; maybe it's related to the fact that I recently logged into the bors-servo account. |
I tried running |
Salt no longer complains about the fileserver update:
|
Maybe this just works now!
|
Nevermind, when I remove the tmp clone it's back to being empty. |
Still seeing lots of entries like this in the salt logs at /var/log/salt/master:
|
I tried upgrading GitPython to 0.3.2rc1 ( |
When I run
salt 'servo-master1' state.highstate test=True
, I now get:If I set up the override in /tmp/salt-testing-root, I can highstate fine. As soon as I clean up the override, I cannot. @aneeshusa I'm not sure what could have caused this; #786 is the only PR that looks remotely related, but I don't see a smoking gun yet.
The text was updated successfully, but these errors were encountered: