It should be run on dev boxes that were built before the installer was updated [1]. Regarding the foreman-tasks: I suppose that we actually do not need to require foreman-tasks to be running in order to run that rake task. If I recall correctly it did work fine for me so long as I had the rails server running in another process. Let me know if that works and if not I can open a PR with the fix.
Jonathon [1] https://github.com/Katello/katello-installer/commit/a03749491f344458a5b52acadcf21526c66b7c65 On Tue, Dec 19, 2017 at 10:02 PM, Walden Raines <[email protected]> wrote: > Is this also meant to be ran on dev boxes? I don't have foreman-tasks > running so I get the following: > > 2017-12-20T02:58:34 [app] [W] foreman-tasks service not running or is not > ready yet > > Thanks, > Walden > > > On Thu, Dec 7, 2017 at 1:51 PM, Jonathon Turel <[email protected]> wrote: > >> >> >> On Thursday, December 7, 2017 at 6:04:45 AM UTC-5, Ewoud Kohl van >> Wijngaarden wrote: >>> >>> On Wed, Dec 06, 2017 at 07:07:05AM -0800, Jonathon Turel wrote: >>> >A change >>> ><https://github.com/Katello/katello/commit/946b2990c9a054ba >>> bc9ad563e1b14c4161207b3e> >>> >landed in Katello yesterday which introduced a new pattern of importing >>> >product content information from Candlepin into the Katello DB. This is >>> in >>> >support of some new feature work and means that Candlepin will no >>> longer be >>> >consulted for that information until it's time to be refreshed. All >>> areas >>> >of Katello which use product content data are affected such as the Red >>> Hat >>> >Repositories page and several APIs. >>> > >>> >In order to populate your local cache, please run `rake >>> >katello:upgrades:3.6:import_product_content`. From that point on the >>> cache >>> >should be updated through ordinary use of Katello - importing >>> manifests, >>> >etc. This step is not necessary unless you have a manifest imported >>> and/or >>> >custom products created. >>> > >>> >I'm working on a change for the installer to do the same import and >>> I'll >>> >update this thread once it's ready for review & test. >>> > >>> >Let me know if you have problems, questions, or concerns. >>> >>> Perhaps this is unrelated and not even possible, but I'd like to know if >>> we could change database provisioning/seeding to not require candlepin. >>> Currently for the organization a matching org in candlepin is created. >>> That's a dependency that ideally shouldn't be there. Do you see this as >>> an option? >>> >> >> I'd have to look into that, but I think I see the merit. Maybe opening an >> issue is appropriate here? >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "foreman-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to a topic in the > Google Groups "foreman-dev" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/foreman-dev/mNAikpyNDFs/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
