Uploaded image for project: 'Mender'
  1. Mender
  2. MEN-5547

"mender check-update" breaks periodic update checks

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Priority: (None)
    • Resolution: Fixed
    • Affects Version/s: 3.0.0
    • Fix Version/s: 3.0.3, 3.3.1, 3.4.0
    • Environment:
      Mender 3.0.0 integrated in Yocto, on custom hardware.
    • Sprint:
      MEN Sprint 170
    • Story Points:
      5
    • Backlog:
      yes
    • Days in progress:
      5

      Description

      Using "mender check-update" prevents the next scheduled periodic update check from happening.

      Here is a log showing the problem:

      Mar 24 12:13:06 s32g274asbcliebherr mender[1905]: time="2022-03-24T12:13:06Z" level=info msg="State transition: check-wait [Idle] -> inventory-update [Sync]"
      Mar 24 12:13:07 s32g274asbcliebherr mender[1905]: time="2022-03-24T12:13:07Z" level=info msg="State transition: inventory-update [Sync] -> check-wait [Idle]"
      Mar 24 12:43:03 s32g274asbcliebherr mender[1905]: time="2022-03-24T12:43:03Z" level=info msg="State transition: check-wait [Idle] -> update-check [Sync]"
      Mar 24 12:43:03 s32g274asbcliebherr mender[1905]: time="2022-03-24T12:43:03Z" level=info msg="State transition: update-check [Sync] -> check-wait [Idle]"
      Mar 24 13:13:03 s32g274asbcliebherr mender[1905]: time="2022-03-24T13:13:03Z" level=info msg="State transition: check-wait [Idle] -> update-check [Sync]"
      Mar 24 13:13:03 s32g274asbcliebherr mender[1905]: time="2022-03-24T13:13:03Z" level=info msg="State transition: update-check [Sync] -> check-wait [Idle]"
      Mar 24 13:43:03 s32g274asbcliebherr mender[1905]: time="2022-03-24T13:43:03Z" level=info msg="State transition: check-wait [Idle] -> update-check [Sync]"
      Mar 24 13:43:03 s32g274asbcliebherr mender[1905]: time="2022-03-24T13:43:03Z" level=info msg="State transition: update-check [Sync] -> check-wait [Idle]"
      Mar 24 13:45:24 s32g274asbcliebherr mender[1905]: time="2022-03-24T13:45:24Z" level=info msg="Forced wake-up from sleep"
      Mar 24 13:45:24 s32g274asbcliebherr mender[1905]: time="2022-03-24T13:45:24Z" level=info msg="Forcing state machine to: update-check"
      Mar 24 13:45:24 s32g274asbcliebherr mender[1905]: time="2022-03-24T13:45:24Z" level=info msg="State transition: check-wait [Idle] -> update-check [Sync]"
      Mar 24 13:45:24 s32g274asbcliebherr mender[1905]: time="2022-03-24T13:45:24Z" level=info msg="State transition: update-check [Sync] -> check-wait [Idle]"
      Mar 24 14:43:03 s32g274asbcliebherr mender[1905]: time="2022-03-24T14:43:03Z" level=info msg="State transition: check-wait [Idle] -> update-check [Sync]"
      Mar 24 14:43:03 s32g274asbcliebherr mender[1905]: time="2022-03-24T14:43:03Z" level=info msg="State transition: update-check [Sync] -> check-wait [Idle]"
      

      You can see periodic checks happening every hour at 13 and 43 minutes (every 30 minutes) as configured.

      At 13:45 I run a "mender check-update". Then at 14:13, nothing happens, and the cycle resumes at 14:43.

      When running "mender check-update" several times, this effect amplifies. For example if you run it 5 times, nothing will happen for the next 2:30 and then updates will resume.

      Expected behavior: scheduled updates should continue to happen, or possibly, the next update should be 30 minutes after the manual "mender check-update" run.

        Attachments

          Activity

            People

            Assignee:
            oleorhagen Ole Petter Orhagen
            Reporter:
            pulkomandy Adrien Destugues
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: