-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
3.9.1.GA
-
False
-
None
-
False
-
-
Description of problem:
Not able to create the workspace using devworkspace yaml directly with a private git repository and it fails during git clone and throws error "fatal: could not read Username for github.com : No such device or address".We have configured github oauth secret and expecting (personal access token) secret to be created in the user namespace for the git authentication to work but due to some reason the (personal access token) secret does not created. But when we restart the same workspace, it works, the (personal access token) secret gets created. So assuming the problem is due to (personal access token) not being created when creating the workspace using devworkspace yaml.
If we use the same git repo and create the workspace from devspace dashboard UI then it works
Also If we use the same devworkspace yaml with a public repository then also it works.
Workaround : None
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
#
Install Devspaces Operator 3.9.1
Create default checluster instance
Logged in with cluster-admin user
Create workspace using devworkspace yaml (private git repository)
Already configured github oauth
Actual results:
Workspace is failing with git clone error
personal access token secret is missing from user namespace.
Expected results:
Workspace should be created successfully
Reproducibility (Always/Intermittent/Only Once):
Acceptance criteria:
Definition of Done:
Build Details:
Additional info (Such as Logs, Screenshots, etc):