Ansible callback plugin report issue

Support
1

Problem: When I launch a playbook : the host is created on foreman, the facts are created but the report keep display the json format which is not user friendly to read :slight_smile:

Foreman and Proxy plugin versions:
fresh centos-7.5 foreman-1.17.1-1.el7 foreman-proxy-1.17.1-1.el7 rubygem-smart_proxy_ansible-2.0.2-1.fm1_17.el7 tfm-rubygem-foreman_ansible-2.0.1-1.fm1_17.el7 python-2.7.5-68.el7

Other relevant data:

  • during the playbook and Gathering Facts with windows OS only I have : 500 Server Error: Internal Server Error for url: https://foreman/api/v2/hosts/facts but the facts are well created on foreman.
  • during the playbook with windows OS only I have the OperatingSystem Column Information not set.
2

We are working on improving integration with Ansible, which also includes making reports better readable. In 1.18 we’ll introduced a JSON viewer which let’s users browse through the JSON better:

config_reports
config_reports1639×802 61.3 KB

This is not the golden solution, but an improvement. Any feedback and suggestions on what and how reports should be presented can help find a better solution.

Regarding the issue with gathering facts from Windows machines might be worth a separate thread.

3 Likes
3

Looks fine to me, I’m looking forward to test the next release :grinning:

4

I think the changed true/false could be a gray label Unchanged or green label Changed. Makes it much easier to quickly see what changed. Exact colors should be determined by someone who does have a feeling for UI/UX :stuck_out_tongue: Perhaps it could be shown together with the level?

I also wonder if Message should be before Arguments since as a user I might look at that first.

1 Like
5

Hello,

When I launch a playbook, my reports are empty :

foreman_empty_reports
foreman_empty_reports1285×487 13.9 KB

I used :
ansible-2.6.2
foreman-1.18.0-2
tfm-rubygem-foreman_ansible_core-2.0.2-1.fm1_18
tfm-rubygem-foreman_ansible-2.2.5-1.fm1_18

6

this looks as another issue with json tree react component / webpack, could you check JS console in your browser if there’s some error?

7

For some I’ve :
TypeError: o is null

or some I’ve :

Error: Component not found: ReportJsonViewer among BookmarkContainer, DonutChart, StatisticsChartsList, PowerStatus, NotificationContainer, ToastNotifications, StorageContainer, PasswordStrength, BreadcrumbBar
and:
TypeError: o is null

8

This looks to be working with foreman-1.19.0-1 (No more Typerror). When I launch tasks there is nothing in Module column nor in Arguments. What it would interesting is to have the task name in a column and maybe changing the color of the true/false value message in something like green instead of red to make it less error like infos.