Skip to content

E3025.md

Latest commit

 

History

History
21 lines (13 loc) · 1.78 KB

E3025.md

File metadata and controls

21 lines (13 loc) · 1.78 KB
Raw

E3025 Details

Message emitted

E3025: Cannot deploy configuration(s). One or more config plans have an approval workflow that is not in the Approved state.

Description

The Deploy Config Plans job refuses to push configuration to devices when any plan in the batch has an associated Nautobot Approval Workflow that has not yet reached the Approved state (it is still Pending, was Denied, or was Canceled). Plans that have no associated workflow at all — i.e. an admin removed the Config Plan Approval workflow definition before the plan was generated — are allowed through.

Troubleshooting

  1. Identify the offending plan(s). The Config Plan list and detail views display an Approval State column / panel that surfaces each plan's current state and links to its workflow.
  2. From the workflow detail page (or from the Approver Dashboard at /extras/approver-dashboard/), an approver in the nautobot-default-configplan-approver group can approve or deny the pending stage(s).
  3. If the workflow was denied or canceled, generate a new Config Plan; the previous plan cannot be re-approved.

Recommendation

  • Approval is gated by the Config Plan Approval workflow seeded by the plugin. Admins can amend the approver group (or any other stage attribute) under Extras → Approval Workflow Definitions.
  • To disable approvals entirely, delete the Config Plan Approval definition. New Config Plans generated afterwards will deploy without approval. Existing plans with pending workflows are still gated until those workflows reach Approved, are deleted, or the deploy is run with a different set of plans.
  • The Workflow Architect persona (the nautobot-default-configplan-architect group) holds the permissions required to manage the workflow definition and its stages.