Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-16584

CronJobs written in YAML format don't work correctly

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • Camel-K-GA
    • None
    • Camel-K
    • None
    • False
    • False
    • % %
    • Todo
    • Undefined
    • Hide

      1. 

      kamel run cron-g.groovy
kamel run cron.yaml

      2. 

      oc get cronJobs
NAME     SCHEDULE    SUSPEND   ACTIVE   LAST SCHEDULE   AGE
cron-g   * * * * ?   False     0        52s             113s

      After checking the logs of both integrations you can see that cron-g creates the pod after every timer tick whereas cron written in YAML creates the pod once and prints the output in the loop

      Show
      1. kamel run cron-g.groovy kamel run cron.yaml 2. oc get cronJobs NAME SCHEDULE SUSPEND ACTIVE LAST SCHEDULE AGE cron-g * * * * ? False 0 52s 113s After checking the logs of both integrations you can see that cron-g creates the pod after every timer tick whereas cron written in YAML creates the pod once and prints the output in the loop

      Identical Camel-k integrations written in YAML and Groovy languages behave differently.
      CronJob written in YAML isn't contained in the OpenShift CronJobs list but produces the expected output. Check the attached files.

      From yaml cron logs:
      [1] 2021-05-31 14:27:38,332 INFO [io.qua.qua.run.QuartzScheduler] (main) No scheduled business methods found - Quartz scheduler will not be started

        1. cron.yaml
          1 kB
          Vlad Sokolovskii
        2. cron-g.groovy
          1.0 kB
          Vlad Sokolovskii
        3. groovy-cron.log
          24 kB
          Vlad Sokolovskii
        4. yaml-cron.log
          8 kB
          Vlad Sokolovskii

              nicolaferraro Nicola Ferraro (Inactive)
              rhn-support-vsokolov Vlad Sokolovskii (Inactive)
              Andrej Smigala Andrej Smigala
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: