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

Project Sync Never Finishes #11496

Closed
3 tasks done
bandwiches opened this issue Dec 30, 2021 · 6 comments
Closed
3 tasks done

Project Sync Never Finishes #11496

bandwiches opened this issue Dec 30, 2021 · 6 comments

Comments

@bandwiches
Copy link

Please confirm the following

  • I agree to follow this project's code of conduct.
  • I have checked the current issues for duplicates.
  • I understand that AWX is open source software provided for free and that I am not entitled to status updates or other assurances.

Summary

Initial project setup worked fine and took ~30 seconds. Additional sync of that same project sits in a "running" state indefinitely. I'm not entirely sure how to go about finding more details other than this. STDOUT for the job itself is just blank. The job itself can be cancelled.

AWX version

19.4.0

Installation method

kubernetes

Modifications

no

Ansible version

ansible [core 2.11.7.post0]

Operating system

Ubuntu

Web browser

No response

Steps to reproduce

Create a project (Git/SCM) and sync it.

Expected results

Expected a pretty quick sync, but just see the job sitting in a running state indefinitely.

Actual results

Job never completed.

Additional information

No response

@bandwiches
Copy link
Author

After further testing, I've found that this only happens when using the SSH method versus HTTPS method.

Did you test SSH from the node? Yes, it worked.
Did you test cloning from the node via SSH? Yes, it worked.
Is the same private key used for an AWX credential? Yes
Did sync work? No, spun indefinitely (running)

Creating a credential using username/password and creating a project using the HTTPS URL for the repo, everything worked fine. Please note that both methods (SSH & HTTPS) work fine on the host outside of AWX.

@AlanCoding
Copy link
Member

I'm wondering if this might be the same as #11453, because for these SCM SSH credentials, I believe it uses the same logic as job SSH credentials. There might be some helpful hints to asses this in that issue or others linked from it.

@craph
Copy link
Contributor

craph commented Jan 11, 2022

@bandwiches Hi,
I have the same issue like you. you can find my issue here #11518
I did all the same test like you.

It's a very weird behavior...

@bandwiches
Copy link
Author

@craph looks to be the same to me. I haven't had the cycles to investigate any further, I just decided to use HTTPS for now instead of SSH and will swap back once it's fixed. I'm also unable to view any additional logs, the jobs are just blank.

@AlanCoding not sure on that one, that's over my head at the moment.

Crowdstrike - this is a recurring noun in all of these tickets, we also have Crowdstrike running at the host level. If I can find the time today, I'll investigate if the SSH Sync works when that's turned off.

@craph
Copy link
Contributor

craph commented Jan 12, 2022

@bandwiches as you can see in my issue #11518 I have added extra info and some tests.

I can confirm that when I turn off the service falcon-sensor (crowdstrike) all is working fine.

Moreover, when I ran the command ps -ef | cat in the ˋawx-eeˋ I can see the process "ssh-add..." stuck. This process try to create the pipe file to store the ssh credential. Then if you try to echo your credential private key in the pipe file you will be able to see that the process is running well.

So something seems wrong with crowdstrike and pipe file from awx

@shanemcd
Copy link
Member

Closing this in favor of #11518 since the problem has been pinpointed in that issue.

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

No branches or pull requests

4 participants