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

AWS EC2 inventory ends in failure #12491

Open
4 of 9 tasks
nasjomach opened this issue Jul 8, 2022 · 6 comments
Open
4 of 9 tasks

AWS EC2 inventory ends in failure #12491

nasjomach opened this issue Jul 8, 2022 · 6 comments
Labels

Comments

@nasjomach
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.

Bug Summary

AWS EC2 inventory end in failure after some weeks/days using it.
Job status: Failed

The job used to run correctly for some time and then at some point ends in failures.

Recreating the the same inventory source with the exact same options, credentials, etc makes it ends in Successful status.

Failed job log last entries:
22.907 DEBUG Adding child group zones to parent all
22.909 INFO Loaded 815 groups, 240 hosts
13k output lines (debug)

Successfull job last entries:
47.597 INFO Inventory import completed for in 34.0s
24k output lines (debug)

This seems to not be happening with: AWX 19.5.0.

AWX version

21.1.0

Select the relevant components

  • UI
  • API
  • Docs
  • Collection
  • CLI
  • Other

Installation method

kubernetes

Modifications

no

Ansible version

No response

Operating system

No response

Web browser

No response

Steps to reproduce

Creat AWS EC2 inventory source, use it for some time.

Expected results

Inventory source ends in failure.

Actual results

Failed job log last entries:
22.907 DEBUG Adding child group zones to parent all
22.909 INFO Loaded 815 groups, 240 hosts
13k output lines (debug)

Additional information

Recreating the the same inventory source with the exact same options, credentials, etc makes it ends in success status.

@sarabrajsingh
Copy link
Contributor

sarabrajsingh commented Jul 13, 2022

hey @nasjomach can you copy/paste the output of the API details for this inventory update?

endpoint: /api/v2/inventory_updates/<id>

where <id> is the id number of the job corresponding to the inventory update.

thanks,
AWX Team

@mick1627
Copy link

mick1627 commented Jul 25, 2022

Here the output of a failed inventory update

@sarabrajsingh
Copy link
Contributor

might be a duplicate of - #12530

@mick1627
Copy link

mick1627 commented Aug 12, 2022

In our case, the pods to do the inventory sync start and finished successfully. The pods run about 15 secondes.
Then, the task in AWX stay in "running" mode for about 15 - 20 secondes and finally finished with error.

@mick1627
Copy link

We observed that if we Uncheck the Update options box "Overwrite" on the source inventory, the inventory sync is working.
Maybe related to #12277
From a new inventory, we tried to stop an instance, re-run the inventory, the instance stopped is removed from the inventory it works well.
We will try the same thing in few days with an host used in several job template.

@shanemcd shanemcd mentioned this issue Aug 17, 2022
9 tasks
@AlanCoding
Copy link
Member

This is a rare log for us to see:

awx.main.dispatch worker pid:437716 is gone (exit=-9)

logger.error('worker pid:{} is gone (exit={})'.format(w.pid, w.exitcode))

This is very descriptive. The process that was saving the inventory data died.

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

6 participants