You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DTS CI fails to clone dts-release-cicd-pipeline: Permission denied
How reproducible
No response
How to reproduce
Push a release tag to develop
Expected behavior
CI passes. The release is published on GitHub and binaries + signatures are deployed.
Actual behavior
Trigger signing job fails:
Cloning into 'dts-release-cicd-pipeline'...
[main 84ab3340d1c7] Signing release v2.0.0-rc6
1 file changed, 1 insertion(+), 1 deletion(-)
git@git.3mdeb.com: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
@PLangowski probably not the fault but there is open PR to merge changes that were merged to main but not into develop: Dasharo/meta-dts#147
Maybe there were other fixes that were applied to main but not develop?
Not sure if it's connected but last Weekly clean & rebuild failed during Send sstate-cache folder to cache.dasharo.com step:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
(...)
Should be fixed by Dasharo/meta-dts#173 but needs to be tested.
Workflow failed a little later not during clone but most likely push (logs didn't show which command failed)
WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED was due to keys changing, it should be fixed by now.
Component
Dasharo Tools Suite
Device
other
Dasharo version
No response
Dasharo Tools Suite version
v2.0.0-rc*
Test case ID
No response
Brief summary
DTS CI fails to clone
dts-release-cicd-pipeline
: Permission deniedHow reproducible
No response
How to reproduce
Expected behavior
CI passes. The release is published on GitHub and binaries + signatures are deployed.
Actual behavior
Trigger signing
job fails:The release is not published.
Screenshots
No response
Additional context
This problem has appeared in the past and seemed to have been fixed in Dasharo/meta-dts#146, however it reappeared.
The
SSH_KEY_CI_CD
secret should hold the correct key that will allow the builder to access https://git.3mdeb.com/3mdeb/dts-release-cicd-pipeline.Solutions you've tried
No response
The text was updated successfully, but these errors were encountered: