Bug #22186

Date format of published content view in yaml output changed on Rails 5.x and causes Puppet runs to fail

Added by Ondřej Pražák over 4 years ago. Updated almost 4 years ago.

Target version:
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:


Calling to_yaml on an instance of ActiveSupport::TimeWithZone gives different output on Rails 4.2 and 5.x (see the screenshots), which makes Puppet run fail. Katello adds a date of a published content view into the output of method. When Puppet tries to fetch the node definition and yaml contains a date in a new format, Puppet server fails to parse it.

Steps to reproduce:
1) set up a host with Puppet and published content view
2) try running puppet agent -t
3) observe the error

42_published_to_yaml.png View 42_published_to_yaml.png 161 KB Ondřej Pražák, 01/09/2018 11:33 AM
51_published_yaml.png View 51_published_yaml.png 172 KB Ondřej Pražák, 01/09/2018 11:33 AM
puppet_run_fail.png View puppet_run_fail.png 42.4 KB Ondřej Pražák, 01/09/2018 11:40 AM
42 published to yaml 51 published yaml Puppet run fail

Associated revisions

Revision ac81226e (diff)
Added by Jonathon Turel over 4 years ago

Fixes #22186 - Correct date format in Host Info Provider


#1 Updated by Justin Sherrill over 4 years ago

  • Difficulty set to easy
  • Legacy Backlogs Release (now unused) set to 284
  • Priority changed from High to Immediate
  • Assignee set to Jonathon Turel
  • Category set to Hosts

#2 Updated by Jonathon Turel over 4 years ago

  • Target version set to 245

#3 Updated by The Foreman Bot over 4 years ago

  • Status changed from New to Ready For Testing
  • Pull request added

#4 Updated by Jonathon Turel over 4 years ago

  • % Done changed from 0 to 100
  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF