[GitHub] [airflow] potiuk commented on issue #17150: Git Sync for DAGs fails

[GitBox <gi...@apache.org>]

potiuk commented on issue #17150:
URL: https://github.com/apache/airflow/issues/17150#issuecomment-884783635


   The root cause of the problem is indeed user/password. What happens is that git fails to authenticate with the server, fails, then tries to ask for user/password via terminal and it fails, because.... there is no terminal: https://stackoverflow.com/questions/40274484/fatal-could-not-read-username-for-https-github-com-device-not-configured
   
   I think the reason is that your user/password is base64 encoded or wrong (Or I think so at least ad "64bit encrypted" is well kinda cryptic).  You mentioned:
   
   ```
   #username: my_username
   GIT_SYNC_USERNAME: 64bit encryted value of my_username
   #password: my_password
   GIT_SYNC_PASSWORD: 64bit encrypted value of my_password
   ```
   
   Which I think means "base64 encoded" in fact (but I am guessing that).
   
   I think you might have assumed that you need to base64-encode, the username/password when you create the secret, but when I look at the code of the chart I think it should not be. You should store user/password as "plain" values in the secret rather
   
   I believe you can easily verify it when you retrieve the secrets using kubectl. When you do it - you should see the "plain" user/password in the secret rather than their Base64-encoded versions (usually ending with `=`). 
   
   I will mark it as invalid and close, assuming this is the problem, but please let us know if that worked (or if it did not, re-open it and add extra information on what you've tried).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org