remove user to prevent ForeignKeyViolation

[amolpati30]

Problem -
When creating another user with a specific role and adding resources in the filter with the 'view_facts' permission, an error occurred ('PG::ForeignKeyViolation: ERROR: update or delete on table "hosts" violates foreign key constraint "fact_values_host_id_fk" on table "fact_values"') during the teardown process while deleting the host. This happened because a user with only view permissions existed for the host and making it impossible to update or delete the user associated with the fact.

Solution -
To prevent this error, the user was removed before the teardown process.

[amolpati30]

trigger: test-robottelo
pytest: tests/foreman/api/test_ansible.py::TestAnsibleCfgMgmt -k test_positive_read_facts_with_filter

[Satellite-QE]

PRT Result

Build Number: 9478
Build Status: SUCCESS
PRT Comment: pytest tests/foreman/api/test_ansible.py::TestAnsibleCfgMgmt -k test_positive_read_facts_with_filter --external-logging
Test Result : ========== 2 passed, 3 deselected, 116 warnings in 1043.21s (0:17:23) ==========

[ekohl]

This sounds like a bug in the application to me. Was one filed?

[amolpati30]

@ekohl
It might be but because we are granting only view permissions to the user, and then attempting to delete the host during teardown with that user. This behavior is likely expected, as the user does have only view permissions. Additionally, the database storing the data with a foreign key, which prevents the host from being deleted and results in an error.

[ekohl]

If you see a PostgreSQL error as a user, I'd consider it a bug. IMHO it should either cascade (delete any permissions the user has) or provide a proper error why the user can't be deleted.

[amolpati30]

A bug has already been raised for this issue - https://issues.redhat.com/browse/SAT-18656.
Therefore, I am closing this PR as it is no longer valid.