Project

General

Profile

Actions

Bug #22186

closed

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 6 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Immediate
Category:
Hosts
Target version:
Difficulty:
easy
Triaged:
Fixed in Releases:
Found in Releases:

Description

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 Host.info 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


Files

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
Actions #1

Updated by Justin Sherrill over 6 years ago

  • Category set to Hosts
  • Assignee set to Jonathon Turel
  • Priority changed from High to Immediate
  • Translation missing: en.field_release set to 284
  • Difficulty set to easy
Actions #2

Updated by Jonathon Turel over 6 years ago

  • Target version set to 245
Actions #3

Updated by The Foreman Bot over 6 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/7174 added
Actions #4

Updated by Jonathon Turel over 6 years ago

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

Also available in: Atom PDF