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

When running `mender setup`, incorrect values for Update Control expiration are put into mender.conf

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.0.0, 3.0.0-report
    • Labels:
    • Environment:
      3.0.0-build2
    • Story Points:
      3
    • Backlog:
      yes
    • Days in progress:
      0

      Description

      Steps to reproduce:

      1. ./demo --enterprise-testing up
      2. Use Python example client to insert extra pauses.
      3. Remove pause for ArtifactInstall (not sure if this matters or not).
      4. Make a rootfs-image deployment, with pauses in ArtifactInstall and ArtifactReboot.

      The installation fails, but it should have paused instead. Using debug mode for the client, these two lines look quite suspicious:

      2021-07-07 12:11:01 +0000 UTC debug: Querying Update Control maps. Currently active maps: '[ID: 886404f9-eb65-464f-b6d4-f7b3f945db61 Priority: 0
States: map[ArtifactInstall_Enter:{pause fail pause} ArtifactReboot_Enter:{pause fail pause}] ID: 01234567-89ab-cdef-0123-456789abcdef Priority: -1
States: map[ArtifactCommit_Enter:{pause fail pause} ArtifactReboot_Enter:{pause fail pause}]]'
2021-07-07 12:11:01 +0000 UTC debug: Returning action "fail"

      Since all the actions (the first member) are "pause", why does it return "fail"?

        Attachments

          Activity

            People

            Assignee:
            a10040 Kristian Amlie
            Reporter:
            a10040 Kristian Amlie
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support