Project

General

Profile

Bug #11229

Import classes does not find any new classes

Added by Gerwin Krist over 5 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Category:
Puppet
Target version:
Difficulty:
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

Hi,

Summary:
After updating from 1.8 to 1.9 RC2 we found out that importing new puppet classes did not get imported anymore.

Some facts:
  • after ugrade one class could get imported after this one it did not find any new classes
  • setenforce 0 or 1 makes no difference
  • importing new environments does work
  • deleted classes get detected properly
  • no errors/exception even in debug mode
  • sudo -u foreman-proxy cat /etc/puppet/environments/production/modules/lh_nodes/manifests/<class> does work

Workaround
What we did is renaming the /var/cache/foreman-proxy/ json file. After this it did detect new classes proper.

cache_production.json cache_production.json 15.8 KB Gerwin Krist, 07/28/2015 08:30 AM

Related issues

Related to Smart Proxy - Bug #10941: puppet classes cache not working rightClosed2015-06-26
Related to Smart Proxy - Bug #11311: Puppet module tests shouldn't depend on existence of /etc/puppet/puppet.confClosed2015-08-07

Associated revisions

Revision e86db516 (diff)
Added by Dmitri Dolguikh over 5 years ago

Fixes #11229: changes in puppet modules are now being detected when listing available puppet classes

History

#1 Updated by Dominic Cleal over 5 years ago

  • Related to Bug #11131: Intermittent Puppet class cache test with timestamps added

#2 Updated by Dominic Cleal over 5 years ago

  • Project changed from Foreman to Smart Proxy
  • Category changed from Smart Proxy to Puppet
  • Legacy Backlogs Release (now unused) set to 35

#3 Updated by Dominic Cleal over 5 years ago

  • Related to deleted (Bug #11131: Intermittent Puppet class cache test with timestamps)

#4 Updated by Dominic Cleal over 5 years ago

  • Related to Bug #10941: puppet classes cache not working right added

#5 Updated by Dmitri Dolguikh over 5 years ago

  • Status changed from New to Assigned
  • Assignee set to Dmitri Dolguikh

#6 Updated by Dmitri Dolguikh over 5 years ago

Is it possible to attach cache files to this issue? The one that got renamed and the one after all classes have been detected.
What version of ruby are you using? Would it be possible to attach the smart-proxy log which includes the first (failed) puppet class import after the upgrade?

#7 Updated by Gerwin Krist over 5 years ago

Sure! ruby-2.0.0.598-25.el7_1.x86_64

I included the json file. Can I mail you the other file (kinda private stuff in it)

#8 Updated by Dmitri Dolguikh over 5 years ago

I assume that's the cache after all puppet classes have been discovered? Do you have the cache file from when you were having issues described in this ticket? My email is ddolguik at redhat. Thanks!

#9 Updated by The Foreman Bot over 5 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/smart-proxy/pull/304 added
  • Pull request deleted ()

#10 Updated by Anonymous over 5 years ago

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

#11 Updated by Dominic Cleal over 5 years ago

  • Related to Bug #11311: Puppet module tests shouldn't depend on existence of /etc/puppet/puppet.conf added

#12 Updated by Gerwin Krist over 5 years ago

FYI I tested RC3 on our deployment and tested:
  • new sub-module under a module
  • complete new module
    BOTH new classes get picked up by the importer.

Also available in: Atom PDF