Repositories aren't updating
I tried creating two repositories last Friday and they still haven't been created by Monday morning. They're located in the "AD Controls Department" project.
This morning I pushed some commits to the repository in the "scripts" repository of the "acsys-fe" project. It usually takes 15 to 20 minutes before showing up but my repo shows "about 1 hour" for the age of the commits and the history hasn't been updated (which means I can't refer to the commit hash in the issue I'm trying to close out.)
Whatever task updates the repositories seems to be broken.
#2 Updated by Richard Neswold over 1 year ago
$ ssh email@example.com echo hi
logs in and runs the
echo command. Hopefully that will trigger the script to update the history. On the other hand, the command
$ ssh firstname.lastname@example.org echo hi
Permission denied (publickey,gssapi-keyex,gssapi-with-mic)." I don't think that account will exist until the first repo is created, so I can't try the workaround.
#3 Updated by Marc Mengel over 1 year ago
Sure enough, when I check the logs for said script:
Fecthing changesets for uboone-operations --2019-03-18 13:20:03-- https://cdcvs.fnal.gov/redmine/sys/fetch_changesets?id= uboone-operations&key=(redacted) Resolving cdcvs.fnal.gov... 188.8.131.52:443... connected. ERROR: cannot verify cdcvs.fnal.gov’s certificate, issued by “/C=US/O=DigiCert I nc/OU=www.digicert.com/CN=DigiCert SHA2 High Assurance Server CA”: Unable to locally verify the issuer’s authority.
Looks like our local certificate store doesn't have the latest Digicert certs...
Re-running them now for the last 4 days worth, and looking to see what else might be tripping up like this...
#5 Updated by Richard Neswold over 1 year ago
Richard Neswold wrote:
Running your scripts updated the repos mentioned in the issue. However, another repo hasn't updated in 12 hours. Can you run your scripts again?
Nevermind. User error this time. I pushed to a branch but was viewing
master. Sorry for the noise.