in Foreman 1.17 again Centos 7.5 I have come across what appears to be an interface bug. I'm not sure "VM Management" is the correct category but it seems the most appropriate component area.

While debugging a kickstart issue, I use a VM hosted on a libvirt host, the build fails (no bug just incorrect configuration/development settings) and I click "cancel build". which works. I make a change to the build components, kickstart, whatever, and return to the same VM and click "build" to re-enable the build token to attempt to rebuild this host and see if my changes have had the desired impact.

I get the warning that this will delete all facts around the host, I confirm that and the foreman proceeds to generate the "review build status for $host" dialog. In the bottom left hand corner of the dialog a "spinning web loading" animation is played for a second where the "ok" button normally appears and then disappears leaving no ok button and no way to confirm the host for "build"

The production log for the "build" button press is included

[log]

2018-05-18 06:36:51 164db8bf [app] [I] Started GET "/hosts/test04.no-dns.co.uk/review_before_build" for 10.11.216.3 at 2018-05-18 06:36:51 +0000
2018-05-18 06:36:51 164db8bf [app] [I] Processing by HostsController#review_before_build as */*
2018-05-18 06:36:51 164db8bf [app] [I] Parameters: {"id"=>"test04.no-dns.co.uk"}
2018-05-18 06:36:51 164db8bf [app] [I] Current user: admin (administrator)
2018-05-18 06:36:51 164db8bf [app] [I] Rendering common/404.html.erb within layouts/application
2018-05-18 06:36:51 164db8bf [app] [I] Rendered common/404.html.erb within layouts/application (1.5ms)
2018-05-18 06:36:51 164db8bf [app] [I] Rendered layouts/_application_content.html.erb (0.3ms)
2018-05-18 06:36:51 164db8bf [app] [I] Rendering layouts/base.html.erb
2018-05-18 06:36:51 164db8bf [app] [I] Rendered layouts/base.html.erb (1.2ms)
2018-05-18 06:36:51 164db8bf [app] [I] Completed 404 Not Found in 17ms (Views: 6.7ms | ActiveRecord: 1.1ms)
2018-05-18 06:36:57 bb61e4ef [app] [I] Started GET "/notification_recipients" for 10.11.216.3 at 2018-05-18 06:36:57 +0000
2018-05-18 06:36:57 bb61e4ef [app] [I] Processing by NotificationRecipientsController#index as JSON
2018-05-18 06:36:57 bb61e4ef [app] [I] Current user: admin (administrator)
2018-05-18 06:36:57 bb61e4ef [app] [I] Completed 200 OK in 3ms (Views: 0.1ms | ActiveRecord: 0.2ms)
2018-05-18 06:37:07 38e39cc0 [app] [I] Started GET "/notification_recipients" for 10.11.216.3 at 2018-05-18 06:37:07 +0000
2018-05-18 06:37:07 38e39cc0 [app] [I] Processing by NotificationRecipientsController#index as JSON
2018-05-18 06:37:07 38e39cc0 [app] [I] Current user: admin (administrator)
2018-05-18 06:37:07 38e39cc0 [app] [I] Completed 200 OK in 3ms (Views: 0.1ms | ActiveRecord: 0.2ms)
2018-05-18 06:37:17 c962a666 [app] [I] Started GET "/notification_recipients" for 10.11.216.3 at 2018-05-18 06:37:17 +0000
2018-05-18 06:37:17 c962a666 [app] [I] Processing by NotificationRecipientsController#index as JSON
2018-05-18 06:37:17 c962a666 [app] [I] Current user: admin (administrator)
2018-05-18 06:37:17 c962a666 [app] [I] Completed 200 OK in 3ms (Views: 0.1ms | ActiveRecord: 0.2ms)
2018-05-18 06:37:27 1571c79b [app] [I] Started GET "/notification_recipients" for 10.11.216.3 at 2018-05-18 06:37:27 +0000
2018-05-18 06:37:27 1571c79b [app] [I] Processing by NotificationRecipientsController#index as JSON
2018-05-18 06:37:27 1571c79b [app] [I] Current user: admin (administrator)
2018-05-18 06:37:27 1571c79b [app] [I] Completed 200 OK in 3ms (Views: 0.1ms | ActiveRecord: 0.2ms)
2018-05-18 06:37:37 114abf99 [app] [I] Started GET "/notification_recipients" for 10.11.216.3 at 2018-05-18 06:37:37 +0000
2018-05-18 06:37:37 114abf99 [app] [I] Processing by NotificationRecipientsController#index as JSON
2018-05-18 06:37:37 114abf99 [app] [I] Current user: admin (administrator)
2018-05-18 06:37:37 114abf99 [app] [I] Completed 200 OK in 3ms (Views: 0.1ms | ActiveRecord: 0.2ms)
[/log]

The log seems to suggest that it attempts to render a 404 message, I see no such visual message, so I'm not sure if that 404 is just an event that happens as generic templates are rendered or if that is actually the reason the "ok" button is not rendering.

I've validated this in Firefox, Chrome, on a Windows 10 client, a Fedora 27 client and a Mac High Sierra client, and internet explorer on a windows 10 client

I've validated this against two foreman 1.17 builds, but that of course doesn't rule out a problem with my builds rather than a foreman bug.

I've attached a screen shot to help visualise the above detail.