Unexpected 'inventory deleted' error on template survey launch

[natman]

ISSUE TYPE

• Bug Report

SUMMARY

Impossible to launch a template because of deleted inventory.

ENVIRONMENT

• AWX version: 16.0.0
• AWX install method: docker on linux
• Ansible version: 2.9.15
• Operating System: centos 7
• Web Browser: firefox

STEPS TO REPRODUCE

launch the survey of a template and fill the vars, atvthe final step of the survey, awx complains that the inventory is deleted. We cannot go further and it is Impossible to launch the template

EXPECTED RESULTS

The wanted inventory to be available and the template to launch.

ACTUAL RESULTS

Inventory deleted whatever is the inventory.

ADDITIONAL INFORMATION

I tried several inventories and several templates.
I previously upgraded from a full functional 15.0.1 awx.

[mabashian]

@natman Can you provide us with a little more information about how the job template was configured so that we can reproduce? I'm mostly interested in what fields are being prompted at launch. Is inventory prompted at launch and/or is there a default inventory set on the job template?

If possible, can you post a screenshot or gif of the error you're seeing?

[natman]

[natman]

no prompted inventory set, therefore, I tried with a prompted inventory, with or without it the result is the same.

[jakemcdermott]

possibly related: #8933

[Chaos-Work]

I am experiencing the same issue on 16.0.0; however, I noticed that the "Some of the previous step(s) have errors" error only happens when the previous steps have default values. If I manually select something different then re-select the default values, that error goes away and the play runs just fine.

The inventory deleted message never goes away, though.

[mabashian]

@natman @Chaos-Work I'm having trouble reproducing this on the latest devel. I suspect @jakemcdermott is right that #8933 might be related. A fix for that went in here: #9028 which would mean a fix went in in AWX 17.0.0 (I think). Are you all still seeing this bug on versions greater than 17.0.0?

[mabashian]

@tiagodread @one-t @akus062381 I suspect this bug was fixed when we fixed #9028

[akus062381]

I also tested this, cannot reproduce. We already have coverage.