We have noticed a problem hosts that automatically upgraded to RHEL/OL 6.6
this week. Maybe this is standard behavior, but I can't recall running
into it before. The issue is basically that there are no Install Media,
Architectures, Provision/Partition Templates associated with the new
release. I've since fixed things up, but I thought I'd share because the
fallout was very odd and not immediately obvious to me.
Navigate to a managed host running 6.6 release, and click Edit.
Examine the Parameters or Classes Tab and make a modification, click Submit.
> *undefined method
boot_filename' for nil:NilClass* > app/models/concerns/orchestration/dhcp.rb:60:indhcp_attrs'
dhcp_record' > app/models/concerns/orchestration/dhcp.rb:140:indhcp_conflict_detected?'
valid?' > app/models/concerns/foreman/sti.rb:29:insave_with_type'
block in update' > app/models/taxonomy.rb:41:inblock in no_taxonomy_scope'
block (2 levels) in as_taxonomy' > app/models/concerns/foreman/thread_session.rb:143:inas_location'
block in as_taxonomy' > app/models/concerns/foreman/thread_session.rb:108:inas_org'
as_taxonomy' > app/models/taxonomy.rb:40:inno_taxonomy_scope'
update' > app/models/concerns/foreman/thread_session.rb:33:inclear_thread'
> lib/middleware/catch_json_parse_errors.rb:9:in `call'
Clicking the "Back" link from the error page goes to the "All Hosts" page.
Search for the host in question, click Edit again.
Examine the Operating System Tab, and find that all fields are empty…
Anyway, we've been running Foreman since 1.2 and I can't recall having an
issue like this. I have had to make the provisioning associations along
the way, but only when provisioning the new release was actually required.
Of course, we still might have had a similar issue, but not noticed the
situation because affected hosts didn't need modifications from inside
I'm curious how others handle this and stay on top of it. Thanks!