Project

General

Profile

Support #22153

Repositories aren't updating

Added by Richard Neswold 10 months ago. Updated 10 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
03/18/2019
Due date:
% Done:

0%

Estimated time:
Duration:

Description

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.

History

#1 Updated by Richard Neswold 10 months ago

I came across #13608 and have ran the ssh command recommended by Marc. I'll post whether this fixed the problem.

#2 Updated by Richard Neswold 10 months ago

The command

$ ssh p-acsys-fe@cdcvs.fnal.gov 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 p-ad-controls-dept@cdcvs.fnal.gov echo hi

returns "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 10 months 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... 131.225.108.132: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...

sigh.

Re-running them now for the last 4 days worth, and looking to see what else might be tripping up like this...

#4 Updated by Richard Neswold 10 months ago

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?

#5 Updated by Richard Neswold 10 months 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.

Also available in: Atom PDF