Uploaded image for project: 'R10K'
  1. R10K
  2. RK-69

Unmanaged Environments Fail to be Removed when Using "rugged" Git Provider

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: r10k 1.5.0
    • Component/s: None
    • Labels:
      None
    • Environment:

      r10k Package: pe-r10k-1.4.1.3.27.g3833bf0-1.el6.x86_64.rpm
      PE: 3.8.0-rc0-398-g287fc6c

    • Template:

      Description

      Description

      if an r10k user specifies the "rugged" Git provider and deletes branches on a Git source, subsequent deployments will fail to remove the unmanaged environments. (i.e. r10k will keep deploying the deleted environments.

      Attachments

      • Beaker Logs

      Repro Steps

      Reproduction via integration tests

      1. Install PE monolithic master.
      2. Install PE 10k package "pe-r10k-1.4.1.3.27.g3833bf0-1.el6.x86_64.rpm" (Temporary work-a-round)
      3. Verify master is operational.
      4. Create a Git source in the "/etc/puppetlabs/r10k/r10k.yaml" and specify the "rugged" Git provider.
      5. Add environments (branches) to the Git source. (i.e. production, env1, env2, env3)
      6. Deploy environments using r10k:

        r10k deploy environment -v

      7. Verify that all environments are operational.
      8. Remove all branches from the Git source except for "production".
      9. Deploy environments using r10k:

        r10k deploy environment -v

      Note: The integration test "integration/tests/user_scenario/basic_workflow/multi_env_1000_branches.rb" covers this scenario.

      Expect

      The only environment that should exist after deployment is "production".

      Actual

      All environments still exist after deployment.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                ryan.gard Ryan Gard
                Reporter:
                ryan.gard Ryan Gard
                QA Contact:
                Ryan Gard
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support