Remove filters from container show_list pages

[zeari]

BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1386473
This removes the filters on containers show_list pages.

cc @simon3z

[zeari]

@miq-bot add_label providers/containers, bug, ui

[miq-bot]

Checked commit zeari@5f6f6c3 with ruby 2.2.5, rubocop 0.37.2, and haml-lint 0.16.1
0 files checked, 0 offenses detected
Everything looks good. 👍

[simon3z]

LGTM 👍
I had a question on the relevant BZ, but for the record let's please copy/paste the answer here as well: what will happen to old installations? Is this still saved in their DB (and it won't disappear)?.

[simon3z]

@miq-bot add_label euwe/yes
@miq-bot assign chessbyte

I think this is worth fixing for Euwe (small, contained, and overall good improvement, also it will stop polluting the db of new installations).
@zeari @bazulay we need to handle bureaucracy for the BZ.

[zeari]

what will happen to old installations? Is this still saved in their DB (and it won't disappear)?.

@gtanzillo @blomquisg These fixtures im removing cause some errors. What can I do to remove them in existing(running) installations?

[bazulay]

@miq-bot add_label blocker

[zeari]

@gtanzillo @blomquisg These fixtures im removing cause some errors. What can I do to remove them in existing(running) installations?

ping @gtanzillo @blomquisg

[chessbyte]

Euwe Backport details:

$ git log -1
commit bf7399b31f956f26c03aae1c0eda63d52ada2c8f
Author: Oleg Barenboim <chessbyte@gmail.com>
Date:   Thu Nov 3 17:40:26 2016 -0400

    Merge pull request #12302 from zeari/remove_filters

    Remove filters from container `show_list` pages
    (cherry picked from commit d77f49cf860eae796645bff42f743c3257ab6188)

    https://bugzilla.redhat.com/show_bug.cgi?id=1386473

[gtanzillo]

@gtanzillo @blomquisg These fixtures im removing cause some errors. What can I do to remove them in existing(running) installations?

@zeari I think the only 2 options are a data migration (which is not an option) or updating the seed method to handle deletes. Seems like more work that it's worth, though. The other thing you can do is provide a small script the deletes the bad searches to the customer that reported the issue as a one off.

[zeari]

Thanks @gtanzillo
I think that a script for the specific customer will do the trick here