I'm seeing this on juju-core 1.18.2 using a new deployed environment with trusty series, then doing upgrade-charm. The agents go into an infinite upgrade-charm loop.
I'm not sure what the problem actually is. Doing what it says and setting --global user.email and user.name for the root user doesn't work, so it can't be manually worked around. And yet, I cannot reproduce the behavior manually by:
I'm seeing this on juju-core 1.18.2 using a new deployed environment with trusty series, then doing upgrade-charm. The agents go into an infinite upgrade-charm loop.
I'm not sure what the problem actually is. Doing what it says and setting --global user.email and user.name for the root user doesn't work, so it can't be manually worked around. And yet, I cannot reproduce the behavior manually by:
git init
git config user.email "juju@localhost"
git config user.name "juju"
git commit --allow-empty -m "test"
This works manually on a new repo, so my theory that git on trusty doesn't like "juju@localhost" and proceeded to autodetect is apparently wrong.