foreman_discovery 11.0.0 → 12.0.0

data/app/views/discovered_hosts/multiple_auto_provision.html.erb

@@ -0,0 +1,4 @@
+<%= render 'selected_hosts', :hosts => @hosts %>
+
+<%= form_tag(submit_multiple_auto_provision_discovered_hosts_path(:host_ids => params[:host_ids]), {:method => :put}) do -%>
+<% end %><br />

data/app/views/discovered_hosts/multiple_reboot.html.erb

@@ -0,0 +1,4 @@
+<%= render 'selected_hosts', :hosts => @hosts %>
+
+<%= form_tag(submit_multiple_reboot_discovered_hosts_path(:host_ids => params[:host_ids]), {:method => :put}) do -%>
+<% end %><br />

data/app/views/discovered_hosts/show.html.erb

@@ -16,16 +16,19 @@
         </h4>
       </div>
       <div id="highlights-panel" class="panel-collapse collapse facts-panel in" >
-        <table class="table table-bordered table-condensed table-fixed">
+        <table class="<%= table_css_classes('table-condensed') %>">
           <% @categories[0].sort.each do |key, val| %>
-          <tr id="fact-<%= key.try(:downcase) %>" class="">
-            <th class="ellipsis" width="40%"> <strong> <%= key %> </strong></th>
-            <td><%= val %></td>
-          </tr>
-        <% end -%>
+            <tr id="fact-<%= key.try(:downcase) %>" class="">
+              <th class="ellipsis" width="40%"> <strong> <%= key %> </strong></th>
+              <td><%= val %></td>
+            </tr>
+          <% end -%>
         </table>
       </div>
     </div>
+  </div>
+
+  <div class="col-md-6">
     <% unless @interfaces.empty? %>
       <div class="panel panel-default">
         <div class="panel-heading" role="tab">
@@ -36,7 +39,7 @@
           </h4>
         </div>
         <div id="interfaces-panel" class="panel-collapse collapse facts-panel in" >
-          <table class="table table-bordered table-condensed table-fixed" id="interfaceList">
+          <table class="<%= table_css_classes('table-condensed table-fixed') %>" id="interfaceList">
             <tr>
               <th class="hidden-xs " width="12%"><%= _('Type') %></th>
               <th class="hidden-xs "><%= _('Identifier') %></th>
@@ -56,12 +59,20 @@
       </div>
     <% end %>
   </div>
+</div>
 
-<div class="panel-group" id="accordion" role="tablist" aria-multiselectable="true">
-    <div class="col-md-6">
+<div class="row">
+  <div class="col-md-12">
+    <%= link_to(_("Collapse All"),"#", :id => "expand_all", :class => "btn btn-default pull-right", style: 'margin-bottom: 1rem') -%>
+  </div>
+</div>
+
+<div class="row">
+  <div class="col-md-12">
+    <div class="panel-group" id="accordion" role="tablist" aria-multiselectable="true">
       <% @categories.each_with_index do |val, index| %>
         <% next if index == 0 || val.empty? %>
-        <div id="category-<%= @categories_names[index].downcase %>" class="panel panel-default">
+        <div id="category-<%= @categories_names[index].downcase %>" class="panel panel-default" style="margin-bottom: 1rem">
           <div class="panel-heading" role="tab">
             <h4 class="panel-title">
               <a role="button" class="expendable-link" data-toggle="collapse" data-parent="#accordion" href="#<%= @categories_names[index].to_s + "panel" %>" aria-expanded="true">
@@ -69,14 +80,14 @@
               </a>
             </h4>
           </div>
-          <div id="<%= @categories_names[index].to_s + "panel" %>" class="panel-collapse collapse facts-panel" role="tabpanel">
-            <table class="table table-bordered  table-condensed table-fixed">
-            <% val.sort.each do |key, value|  %>
+          <div id="<%= @categories_names[index].to_s + "panel" %>" class="panel-collapse collapse in facts-panel" role="tabpanel">
+            <table class="<%= table_css_classes('table-condensed table-fixed') %>">
+              <% val.sort.each do |key, value|  %>
                 <tr class="">
                   <th width="40%" class="ellipsis"><strong> <%= key %> </strong> </th>
                   <td class="ellipsis"> <%= value %> </td>
                 </tr>
-            <% end %>
+              <% end %>
             </table>
           </div>
         </div>
@@ -100,9 +111,10 @@
     $('.primary-flag').tooltip();
     $('.provision-flag').tooltip();
 
+    expand_all_toggle_action = { 'Expand All': 'show', 'Collapse All': 'hide' };
     $('#expand_all').on('click', function () {
-      $('#accordion .panel-collapse').collapse('toggle');
       $(this).text(function(i, text){
+          $('#accordion .panel-collapse').collapse(expand_all_toggle_action[text]);
           return text === "Expand All" ? "Collapse All" : "Expand All";
       })
     });

data/app/views/discovery_rules/_form.html.erb

@@ -16,18 +16,24 @@
           <div class="tab-pane active" id="primary">
             <%= text_f f, :name %>
             <%= autocomplete_f f, :search,
-                               :path             => "discovered_hosts",
+                               :path             => discovered_hosts_path,
                                :control_group_id => 'search_group', :size => 'col-md-9' %>
             <%= select_f f, :hostgroup_id, accessible_resource_records(:hostgroup, :title).to_a, :id, :to_label, { :include_blank => false },
                          { :help_inline => _('Target host group for this rule with all properties set') } %>
             <%= text_f f, :hostname,
                        :label_help => render('discovery_rules/template_inline').html_safe,
                        :label_help_options => {:title => _("Hostname for provisioned hosts"), :'data-placement' => 'bottom' } %>
-            <%= number_f f, :max_count, :label => _('Hosts Limit'), :help_inline => _('Maximum hosts provisioned with this rule (0 = unlimited)'), :min => 0, :max => (2**31 - 1) %>
-            <%= number_f f, :priority, :help_inline => _('Rule priority (lower integer means higher priority)'), :min => 0, :max => (2**31 - 1) %>
+            <%= counter_f f, :max_count, :label => _('Hosts Limit'), :help_inline => _('Maximum hosts provisioned with this rule (0 = unlimited)'), :min => 0 %>
+            <%= counter_f f, :priority, :help_inline => _('Rule priority (lower integer means higher priority)'), step: 100, value: 0 %>
             <%= checkbox_f f, :enabled %>
           </div>
           <%= render 'taxonomies/loc_org_tabs', :f => f, :obj => @discovery_rule %>
         </div>
     <%= submit_or_cancel f %>
 <% end %>
+
+<script type="text/javascript" charset="utf-8">
+$(document).ready(function() {
+  $('input.counter_spinner').spinner();
+});
+</script>

data/app/views/discovery_rules/edit.html.erb

@@ -1,3 +1,3 @@
-<% title _("Edit Discovery Rule") %>
+<% title _('Edit %s') % @discovery_rule.name %>
 
 <%= render :partial => 'form' %>

data/app/views/discovery_rules/index.html.erb

@@ -1,7 +1,7 @@
 <% title _("Discovery Rules") %>
 <% title_actions new_link(_("Create Rule")), help_button %>
 
-<table class="table table-bordered table-striped table-two-pane">
+<table class="<%= table_css_classes('table-fixed') %>">
   <tr>
     <th><%= sort :name, :as => s_("DiscoveryRule|Name") %></th>
     <th><%= sort :priority, :as => s_("DiscoveryRule|Priority") %></th>
@@ -13,7 +13,7 @@
   </tr>
   <% for rule in @discovery_rules %>
     <tr>
-      <td class='col-md-3 display-two-pane'><%= link_to_if_authorized(trunc_with_tooltip(rule.name), hash_for_edit_discovery_rule_path(:id => rule).merge(:auth_object => rule, :authorizer => authorizer)) %></td>
+      <td class='col-md-3'><%= link_to_if_authorized(trunc_with_tooltip(rule.name), hash_for_edit_discovery_rule_path(:id => rule).merge(:auth_object => rule, :authorizer => authorizer)) %></td>
       <td><%= rule.priority %></td>
       <td><%= trunc_with_tooltip(rule.search) %></td>
       <td><%= label_with_link(rule.hostgroup, 26, authorizer) %></td>

data/app/views/foreman_discovery/debian_kexec.erb

@@ -35,5 +35,5 @@ Please read kexec(8) man page for more information about semantics.
   "kernel": "<%= @kexec_kernel %>",
   "initram": "<%= @kexec_initrd %>",
   "append": "url=<%= foreman_url('provision') + "&static=yes" %> interface=<%= mac %> netcfg/get_ipaddress=<%= ip %> netcfg/get_netmask=<%= mask %> netcfg/get_gateway=<%= gw %> netcfg/get_nameservers=<%= dns %> netcfg/disable_dhcp=true netcfg/get_hostname=<%= @host.name %> BOOTIF=<%= bootif %> <%= options.join(' ') %>",
-  "extra": ["--args-linux"]
+  "extra": []
 }

data/app/views/foreman_discovery/redhat_kexec.erb

@@ -46,5 +46,5 @@ Please read kexec(8) man page for more information about semantics.
 <% else -%>
   "append": "ks=<%= foreman_url('provision') + "&static=yes" %> kssendmac nicdelay=5 <%= "ip=#{ip} netmask=#{mask} gateway=#{gw} dns=#{dns} ksdevice=#{mac} BOOTIF=#{bootif} nomodeset #{append}" %>",
 <% end -%>
-  "extra": ["--args-linux"]
+  "extra": []
 }

data/config/as_deprecation_whitelist.yaml

@@ -0,0 +1,395 @@
+---
+- message: "#table_exists? currently checks both tables and views. This behavior is
+    deprecated and will be changed with Rails 5.1 to only check tables. Use #data_source_exists?
+    instead."
+- message: "#tables currently returns both tables and views. This behavior is deprecated
+    and will be changed with Rails 5.1 to only return tables. Use #data_sources instead."
+- message: The behavior of `attribute_change` inside of after callbacks will be changing
+    in the next version of Rails. The new return value will reflect the behavior of
+    calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute` instead.
+  callstack: app/models/concerns/strip_whitespace.rb:9:in `strip_spaces'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack:
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: app/controllers/hosts_controller.rb:828:in `block in update_multiple_proxy'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: app/models/concerns/encryptable.rb:41:in `block in encrypt_setters'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: app/models/concerns/orchestration.rb:86:in `valid?'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: app/models/concerns/foreman/sti.rb:26:in `save'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: app/models/concerns/strip_whitespace.rb:9:in `strip_spaces'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: app/models/host.rb:15:in `method_missing'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: app/models/host/managed.rb:597:in `associate!'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: app/models/host/managed.rb:603:in `disassociate!'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: app/models/host/managed.rb:753:in `refresh_global_status!'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/controllers/api/v2/audits_controller_test.rb:23:in `block in <class:AuditsControllerTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/controllers/environments_controller_test.rb:152:in `block (2 levels)
+    in <class:EnvironmentsControllerTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/controllers/hosts_controller_test.rb:308:in `block in setup_user_and_host'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/controllers/hosts_controller_test.rb:338:in `block (2 levels) in
+    <class:HostsControllerTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/controllers/hosts_controller_test.rb:352:in `block (2 levels) in
+    <class:HostsControllerTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/factories/disable_auditing.rb:13:in `block (3 levels) in <top (required)>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/factories/disable_auditing.rb:13:in `block (3 levels) in <top (required)>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/factories/disable_auditing.rb:15:in `block (2 levels) in <top (required)>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/concerns/audit_extensions_test.rb:103:in `block (2 levels)
+    in <class:AuditExtensionsTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/domain_test.rb:65:in `block (2 levels) in <class:DomainTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/host_test.rb:1132:in `block (2 levels) in <class:HostTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/host_test.rb:1122:in `block (2 levels) in <class:HostTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/host_test.rb:116:in `block in <class:HostTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/host_test.rb:1176:in `block (2 levels) in <class:HostTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/host_test.rb:1186:in `block (2 levels) in <class:HostTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/host_test.rb:1195:in `block (2 levels) in <class:HostTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/host_test.rb:1224:in `block (2 levels) in <class:HostTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/host_test.rb:1237:in `block (2 levels) in <class:HostTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/host_test.rb:1258:in `block (2 levels) in <class:HostTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/host_test.rb:1918:in `block (3 levels) in <class:HostTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/host_test.rb:242:in `block (2 levels) in <class:HostTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/host_test.rb:2540:in `block in <class:HostTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/host_test.rb:255:in `block (2 levels) in <class:HostTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/host_test.rb:268:in `block (2 levels) in <class:HostTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/host_test.rb:2769:in `block in <class:HostTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/host_test.rb:2782:in `block in <class:HostTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/host_test.rb:2795:in `block in <class:HostTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/host_test.rb:283:in `block (2 levels) in <class:HostTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/host_test.rb:3022:in `block (2 levels) in <class:HostTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/host_test.rb:58:in `block in <class:HostTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/host_test.rb:690:in `block (2 levels) in <class:HostTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/host_test.rb:702:in `block (2 levels) in <class:HostTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/host_test.rb:708:in `block (2 levels) in <class:HostTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/host_test.rb:715:in `block (2 levels) in <class:HostTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/medium_test.rb:80:in `block in <class:MediumTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/medium_test.rb:97:in `block in <class:MediumTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/nic_test.rb:392:in `block (3 levels) in <class:NicTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/orchestration/dns_test.rb:108:in `block (2 levels) in <class:DnsOrchestrationTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/orchestration/dns_test.rb:117:in `block (2 levels) in <class:DnsOrchestrationTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/orchestration/dns_test.rb:126:in `block (2 levels) in <class:DnsOrchestrationTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/orchestration/dns_test.rb:139:in `block (2 levels) in <class:DnsOrchestrationTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/orchestration/dns_test.rb:153:in `block (2 levels) in <class:DnsOrchestrationTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/orchestration/dns_test.rb:192:in `block (3 levels) in <class:DnsOrchestrationTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/orchestration/dns_test.rb:226:in `block (2 levels) in <class:DnsOrchestrationTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/orchestration/dns_test.rb:239:in `block (2 levels) in <class:DnsOrchestrationTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/orchestration/dns_test.rb:308:in `block (2 levels) in <class:DnsOrchestrationTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/orchestration/dns_test.rb:323:in `block (2 levels) in <class:DnsOrchestrationTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/models/orchestration/dns_test.rb:51:in `block (2 levels) in <class:DnsOrchestrationTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/unit/compute_resource_host_associator_test.rb:16:in `block in <class:ComputeResourceHostAssociatorTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/unit/compute_resource_host_associator_test.rb:29:in `block in <class:ComputeResourceHostAssociatorTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/unit/facet_test.rb:123:in `block (2 levels) in <class:FacetTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/unit/has_many_common_test.rb:61:in `block in <class:HasManyCommonTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/unit/has_many_common_test.rb:81:in `block in <class:HasManyCommonTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/unit/host_token_test.rb:11:in `block (3 levels) in <class:HostTokenTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/unit/interface_cleaner_test.rb:17:in `block in <class:InterfaceCleanerTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/unit/interface_cleaner_test.rb:32:in `block in <class:InterfaceCleanerTest>'
+- message: The behavior of `attribute_changed?` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_change_to_attribute?` instead.
+  callstack: test/unit/interface_cleaner_test.rb:56:in `block in <class:InterfaceCleanerTest>'
+- message: The behavior of `changed?` inside of after callbacks will be changing in
+    the next version of Rails. The new return value will reflect the behavior of calling
+    the method after `save` returned (e.g. the opposite of what it returns now). To
+    maintain the current behavior, use `saved_changes?` instead.
+  callstack: app/models/host/managed.rb:255:in `block in <class:Managed>'
+- message: The behavior of `changed_attributes` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_changes.transform_values(&:first)`
+    instead.
+  callstack: app/models/concerns/interface_cloning.rb:13:in `setup_object_clone'
+- message: The behavior of `changed_attributes` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_changes.transform_values(&:first)`
+    instead.
+  callstack: app/models/concerns/strip_whitespace.rb:9:in `strip_spaces'
+- message: The behavior of `changed_attributes` inside of after callbacks will be
+    changing in the next version of Rails. The new return value will reflect the behavior
+    of calling the method after `save` returned (e.g. the opposite of what it returns
+    now). To maintain the current behavior, use `saved_changes.transform_values(&:first)`
+    instead.
+  callstack: app/models/host/managed.rb:255:in `block in <class:Managed>'
+- message: The behavior of `changed` inside of after callbacks will be changing in
+    the next version of Rails. The new return value will reflect the behavior of calling
+    the method after `save` returned (e.g. the opposite of what it returns now). To
+    maintain the current behavior, use `saved_changes.keys` instead.
+  callstack: app/models/concerns/strip_whitespace.rb:9:in `strip_spaces'
+- message: The behavior of `changes` inside of after callbacks will be changing in
+    the next version of Rails. The new return value will reflect the behavior of calling
+    the method after `save` returned (e.g. the opposite of what it returns now). To
+    maintain the current behavior, use `saved_changes` instead.
+  callstack: app/models/concerns/strip_whitespace.rb:9:in `strip_spaces'
+- message: Using a dynamic :controller segment in a route is deprecated and will be
+    removed in Rails 5.2.
+  callstack: config/routes.rb:17:in `block in <top (required)>'
+- message: You are using a deprecated behavior, it will be removed in version 1.18,
+    please migrate notice() to success() or info()
+  callstack: app/controllers/concerns/application_shared.rb:15:in `set_timezone'
+- message: You didn't set `secret_key_base`. Read the upgrade documentation to learn
+    more about this new config option.
+  callstack:
+- message: You didn't set `secret_key_base`. Read the upgrade documentation to learn
+    more about this new config option.
+  callstack: test/test_helper.rb:36:in `before_setup'