Default timeout increased to 30 minutes.
Some AWX tasks can be quite long especially as the csentry inventory
update can't run at the same time as other jobs.

JIRA INFRA-1051

Deferred tasks are now set to failed when the task it depends on fails.
No need to have an arbitrary time to disregard "old" deferred tasks.

JIRA INFRA-1051 #action In Progress

JIRA INFRA-1049 #action In Progress

The error has been raised a few times but the cause hasn't been found.
Adding the representation of the job should help debugging.

The caching of the load_user function already created several bugs
(INFRA 908/1018).
It requires to think about adding (or deleting in the admin view)
the current_user to the session. This is easy to miss.

It saves some database queries but we don't need this optimization.
Performances are not impacted and are good enough so far.

Removing the caching makes the application more robust and easier to
maintain.

JIRA INFRA-1025 #action In Progress

The LDAP_USER_DN was changed in 0.21.0.
This resulted in more entries returned when searching for users
and all users being disabled...

We were only looking into "OU=ESS Users" before.
Inactive users are put under "OU=InActiveUsers" in AD.

JIRA INFRA-1026 #action In Progress

LDAP_USER_DN was set to "OU=ESS Users" preventing to find service
account users.
Leaving it empty and relying only on LDAP_BASE_DN allows service users
to login.

JIRA INFRA-1022 #action In Progress

job.status shall be replaced with job.get_status() (RQ)

JIRA INFRA-1021 #action In Progress

- admin can delete any hosts
- normal users can delete hosts they created

Note that still only admin users can delete hosts via the API (more dangerous
operation as a script could delete many hosts).

JIRA INFRA-1018 #action In Progress

Regression from b9c1b838

Calling utils.trigger_ioc_repository_creation runs launch_task
which does a db.session.add(task). This raises:

SAWarning: Usage of the 'Session.add()' operation is not currently
supported within the execution stage of the flush process. Results may
not be consistent.  Consider using alternative event listeners or
connection-level operations instead.

SAWarning: Attribute history events accumulated on 1 previously clean
instances within inner-flush event handlers have been reset, and will
not result in database updates.

The result is that the host is not added to the elasticsearch index.

We can't trigger the task in after_update/after_insert events.
Perform the call in the view instead. It's temporary anyway. This should
be handled by IOC Factory.

JIRA INFRA-1015

The csentry_autoinstall_boot_profile variable shall be saved to setup the
DHCP option.
The DHCP shall be updated when a change occurs.

JIRA INFRA-1016 #action In Progress

The set event is triggered too early and no interface is yet associated
to the host. The fqdn is thus set to the name.

JIRA INFRA-1015 #action In Progress

Allow to select by default the last chosen device_type when creating a
new host.

JIRA INFRA-987 #action In Progress

1. It's possible to erase the network when creating a host.
The exception raised was due to the ip_in_range validator
where a select using the network_id is performed.
This is now catched to raise a ValidationError.
2. Add some javascript to remove the is-invalid class on the network and
IP fields when changing them

JIRA INFRA-810 #action In Progress

No need to compile graylog support (switched to docker gelf driver).
Even to add graylog support, installation can be done using by by
passing an env variable.

JIRA INFRA-981

JIRA INFRA-979 #action In Progress

The boot profile is used to perform a network installation on a physical
machine.

JIRA INFRA-943 #action In Progress

Move trigger_ztp_generation and trigger_vm_creation from tasks.py to
utils.py.
The tasks.py module should only include functions used by the worker.

- requesting too many elements in one query has an impact on the
database and the web application
- max limit set to 100

JIRA INFRA-942 #action In Progress

Add example on how to search for a MAC address

JIRA INFRA-932

This is temporary. The repository should be created by IOCFactory.

JIRA INFRA-932 #action In Progress

JIRA INFRA-931 #action In Progress

Allow to trigger a new core service update only if there is none
depending on the triggered inventory update.

JIRA INFRA-895

As the core service update doesn't depend anymore on each other but only
on the inventory update, 2 can be launched almost at the same time.
As they can't run in parallel, the second one will only start when the
first one is done, meaning that it can take more than 180 seconds to
complete.

Increasing the timeout to 500 seconds should avoid the task to be
reported as failed when it just took longer to run.

JIRA INFRA-895 #action In Progress

Following exception is raised when trying to update a network from
flask-admin:
sqlalchemy.exc.InvalidRequestError: Can't attach instance <User at 0x7f6f0e39ce10>;
another instance with key (<class 'app.models.User'>, (1,), None) is already present in this session.

1. If we remove the caching of the load_user method, the problem
disappears.
2. When updating a Network, this trigger an inventory update in
before_flush which adds a task to the session. This is when the
current_user is added to the session and the error raised.

So the problem is linked to the user caching and flask-admin.

The workaround is to remove the user object added by flask-admin to the
session.

JIRA INFRA-908 #action In Progress

Windows VM creation doesn't support post install yet
- the job that creates the VM returns before the installation is done
- the post install template is Linux only right now

JIRA INFRA-877

The /status/<job_id> view was only looking in the "default" queue to
retrieve the job.
"default" is not used anymore and was replaced by "high", "normal",
"low".
The method Job.fetch doesn't look in a specific queue.

JIRA INFRA-890 #action In Progress

launch_awx_job function was updated to trigger an inventory update.

A job running in AWX prevents an inventory sync (of the same
inventory). This restricts AWX to run only one job at a time as
the inventory is always updated on launch.
To prevent this issue, the inventory is updated from AWX when needed.

- The update is triggered on any model modification that is used in the
inventory (AnsibleGroup, Cname, Domain, Host, Network, NetworkScope)
- For Interface, the inventory sync is triggered by the
trigger_core_services function as it depends on it
- The inventory update job is put on the "high" queue so that it takes
precedence over all other jobs.

JIRA INFRA-887 #action In Progress