Uploaded image for project: 'Puppet Agent'
  1. Puppet Agent
  2. PA-1018

[SPIKE] How, should, and do we need to conflict new agents with old servers?

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Won't Do
    • Affects Version/s: None
    • Fix Version/s: puppet-agent 6.0.0
    • Component/s: None
    • Labels:
      None
    • Template:
    • Acceptance Criteria:
      • Open questions, considerations, and constraints identified.
      • Implementation alternatives and possible trade-offs identified.
      • Findings broadcast to Platform Group and PDE.
    • Team:
      Platform OS
    • Story Points:
      5
    • QA Risk Assessment:
      Needs Assessment

      Description

      Master side, puppet-server does not ship with the Puppet ruby code. Instead, it relies on the .rb files shipped with the agent. However, those ruby files are run within puppet-server's jruby environment, which has a separate gem path. These gems are shipped in the puppet-server package.

      This means that if we have new master-side code in the ruby files that depends on a new gem, we need to require an updated puppet-server to go along with those changes.

      We first looked at implementing this in PA-890, and rolled it back due to concerns with how it affected PE, and with how we communicate to our open-source users that we might bump their puppet-server when puppet-agent is updated.

      Now that we're approaching a major boundary, we should revisit the above issues and try to sort out if we can add these conflicts now or in the future in a reasonable way.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                branan Branan Riley
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support