Working for me again.

 

Thanks.

 

From: Technology Discussion at UVM <[log in to unmask]> on behalf of Brian O'Donnell <[log in to unmask]>
Reply-To: Technology Discussion at UVM <[log in to unmask]>
Date: Monday, March 12, 2018 at 11:18 AM
To: "[log in to unmask]" <[log in to unmask]>
Subject: Re: GitLab Commands asking for [log in to unmask] password

 

Argh. It looks like SELinux was taking issue with the new authorized_keys file. Sorry about that. Fifth time's the charm?


From: Technology Discussion at UVM <[log in to unmask]> on behalf of Scott Turnbull <[log in to unmask]>
Sent: Monday, March 12, 2018 11:15:08 AM
To: [log in to unmask]
Subject: Re: GitLab Commands asking for [log in to unmask] password

 

Deleted, and re-applied my key to gitlab server.

No change.

 

Scott Turnbull

UVM EPSCoR Software Engineer


From: Technology Discussion at UVM <[log in to unmask]> on behalf of Brian O'Donnell <[log in to unmask]>
Sent: Monday, March 12, 2018 11:11:57 AM
To: [log in to unmask]
Subject: Re: GitLab Commands asking for [log in to unmask] password

 

It looks like the original issue was a missing authorized_keys file, which I've regenerated. I'm not sure why it's not working for some people. Gitlab is passing all of its internal checks.

 

Perhaps try deleting and re-adding your ssh key in gitlab?


From: Technology Discussion at UVM <[log in to unmask]> on behalf of Paul Webb <[log in to unmask]>
Sent: Monday, March 12, 2018 11:01:39 AM
To: [log in to unmask]
Subject: Re: GitLab Commands asking for [log in to unmask] password

 

I'm seeing the same thing:

 

$ git remote show origin

[log in to unmask] password:

 

From: Technology Discussion at UVM <[log in to unmask]> on behalf of Scott Turnbull <[log in to unmask]>
Reply-To: Technology Discussion at UVM <[log in to unmask]>
Date: Monday, March 12, 2018 at 10:59 AM
To: "[log in to unmask]" <[log in to unmask]>
Subject: Re: GitLab Commands asking for [log in to unmask] password

 

Negatory.

 

$ git pull
[log in to unmask] password:

 

 

Scott Turnbull

UVM EPSCoR Software Engineer


From: Technology Discussion at UVM <[log in to unmask]> on behalf of Brian O'Donnell <[log in to unmask]>
Sent: Monday, March 12, 2018 10:57:11 AM
To: [log in to unmask]
Subject: Re: GitLab Commands asking for [log in to unmask] password

 

Hi Scott,

 

It is working for me. Can you try one more time?


From: Technology Discussion at UVM <[log in to unmask]> on behalf of Scott Turnbull <[log in to unmask]>
Sent: Monday, March 12, 2018 10:51:31 AM
To: [log in to unmask]
Subject: Re: GitLab Commands asking for [log in to unmask] password

 

Still prompting for git@gitlab pw.

 

Scott Turnbull

UVM EPSCoR Software Engineer


From: Technology Discussion at UVM <[log in to unmask]> on behalf of Brian O'Donnell <[log in to unmask]>
Sent: Monday, March 12, 2018 10:49:34 AM
To: [log in to unmask]
Subject: Re: GitLab Commands asking for [log in to unmask] password

 

Ok, I found the problem. Let me know if it works now.


From: Technology Discussion at UVM <[log in to unmask]> on behalf of Scott Turnbull <[log in to unmask]>
Sent: Monday, March 12, 2018 10:45:31 AM
To: [log in to unmask]
Subject: Re: GitLab Commands asking for [log in to unmask] password

 

No change of behavior on laptop or workstation for two different repos.

 

Scott Turnbull

UVM EPSCoR Software Engineer


From: Technology Discussion at UVM <[log in to unmask]> on behalf of Brian O'Donnell <[log in to unmask]>
Sent: Monday, March 12, 2018 10:41:38 AM
To: [log in to unmask]
Subject: Re: GitLab Commands asking for [log in to unmask] password

 

Hi Scott,

 

I have a suspicion as to what it might be. Any difference now?


From: Technology Discussion at UVM <[log in to unmask]> on behalf of Scott Turnbull <[log in to unmask]>
Sent: Monday, March 12, 2018 10:39:09 AM
To: [log in to unmask]
Subject: GitLab Commands asking for [log in to unmask] password

 

When I try to do a pull from my gitlab.uvm projects, I'm prompted for

 

[log in to unmask] password:

 

This happens on several repositories under different groups.

It happens on both my laptop, and a linux workstation.

 

This is new behavior. I successfully pushed a commit to the server on Friday afternoon.

 

A coworker is experiencing the same behavior this morning for his repositories.

 

Scott Turnbull

UVM EPSCoR Software Engineer