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

The project could not sync because there is no Execution Environment #15003

Open
5 of 11 tasks
smilejj91 opened this issue Mar 15, 2024 · 3 comments
Open
5 of 11 tasks

The project could not sync because there is no Execution Environment #15003

smilejj91 opened this issue Mar 15, 2024 · 3 comments

Comments

@smilejj91
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 might not receive a timely response.
  • I am NOT reporting a (potential) security vulnerability. (These should be emailed to security@ansible.com instead.)

Bug Summary

Hello! 😃

I am deploying and using awx in a k8s environment, and intermittently, I see the following error between project updates.

The project could not sync because there is no Execution Environment.

Traceback (most recent call last):
  File "/var/lib/awx/venv/awx/lib64/python3.9/site-packages/awx/main/tasks/jobs.py", line 509, in run
    env = self.build_env(self.instance, private_data_dir, private_data_files=private_data_files)
  File "/var/lib/awx/venv/awx/lib64/python3.9/site-packages/awx/main/tasks/jobs.py", line 1145, in build_env
    env = super(RunProjectUpdate, self).build_env(project_update, private_data_dir, private_data_files=private_data_files)
  File "/var/lib/awx/venv/awx/lib64/python3.9/site-packages/awx/main/tasks/jobs.py", line 314, in build_env
    raise RuntimeError('The project could not sync because there is no Execution Environment.')
RuntimeError: The project could not sync because there is no Execution Environment.

awx-task and awx-ee are running as containers in the same pod, and there did not seem to be anything special when checking the status / ping through receptorctl.

image

If this is a problem that already has a solution, I would appreciate it if you could let me know the solution. 🙇🏻‍♂️

AWX version

21.11.0

Select the relevant components

  • UI
  • UI (tech preview)
  • API
  • Docs
  • Collection
  • CLI
  • Other

Installation method

kubernetes

Modifications

yes

Ansible version

2.14.2

Operating system

No response

Web browser

Chrome

Steps to reproduce

just project update

Expected results

project updated

Actual results

Traceback (most recent call last):
  File "/var/lib/awx/venv/awx/lib64/python3.9/site-packages/awx/main/tasks/jobs.py", line 509, in run
    env = self.build_env(self.instance, private_data_dir, private_data_files=private_data_files)
  File "/var/lib/awx/venv/awx/lib64/python3.9/site-packages/awx/main/tasks/jobs.py", line 1145, in build_env
    env = super(RunProjectUpdate, self).build_env(project_update, private_data_dir, private_data_files=private_data_files)
  File "/var/lib/awx/venv/awx/lib64/python3.9/site-packages/awx/main/tasks/jobs.py", line 314, in build_env
    raise RuntimeError('The project could not sync because there is no Execution Environment.')
RuntimeError: The project could not sync because there is no Execution Environment.

Additional information

No response

@smilejj91
Copy link
Author

image

@fosterseth
Copy link
Member

that error message doesn't appear in the repo anymore, which means we've probably changed this area of the code quite a bit since 21.11.0

There is a good chance this has been resolved in awx 24.0.0

@smilejj91
Copy link
Author

@fosterseth
hello!!

As you mentioned, when updating to version 24, the same error occurs intermittently.
RuntimeError: The ProjectUpdate could not run because there is no Execution Environment.

Is there any solution? 🙏

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

2 participants