Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DTS CI fails on cloning dts-release-cicd-pipeline #1052

Closed
PLangowski opened this issue Sep 13, 2024 · 5 comments
Closed

DTS CI fails on cloning dts-release-cicd-pipeline #1052

PLangowski opened this issue Sep 13, 2024 · 5 comments
Assignees
Labels

Comments

@PLangowski
Copy link

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 denied

How reproducible

No response

How to reproduce

  1. 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.

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

@m-iwanicki
Copy link

@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?

@m-iwanicki
Copy link

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)!
(...)

@m-iwanicki
Copy link

m-iwanicki commented Sep 24, 2024

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.

@artur-rs
Copy link
Member

@m-iwanicki merged. let's retest the ci with the DTS optiplex changes

@artur-rs
Copy link
Member

artur-rs commented Nov 7, 2024

Closing. We've successfully released the v2.0.0, and v2.0.1-RCs version so far: https://github.com/Dasharo/meta-dts/releases

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants