Migration verification labels pending built-in runs as historical Jobs

已关闭
#4 0 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@pheus 已经在做这个了。

开始于 2026年10月23日。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
活跃
技术栈
python
领域
backend

调研方向

Start by reproducing the migration verification flow through Repoint references, then schedule a built-in Custom Script and run Verify. Trace the Jobs check responsible for the reported message and compare pending scheduled work with completed history. Done means pending execution is identified separately and the message no longer misclassifies it as historical.

由索引模型根据 Issue 内容生成。

描述

app: scripts severity: low status: backlog type: bug
Plugin Version

v0.0.1

NetBox Version

v4.7.1

Python Version

3.12

Steps to Reproduce
  1. Under Scripts > Migration, complete the passes through Repoint references.
  2. As a superuser, schedule a built-in Custom Script for the following day under Customization > Scripts.
  3. Run Verify.
Expected Behavior

The Jobs check distinguishes pending execution from completed history and makes clear that this run can still execute a built-in Script.

Observed Behavior

Verification reports "1 Job(s) still name the built-in feature. Each one is history no Script Project can hold, so it stays where it is."

The counted Job is scheduled work, not history. The same message can describe a successor queued by a recurring built-in run after cutover, although the migration guide directs operators to remove such runs.

主要语言
Python
星标
8
派生
0
平均合并
11 小时 23 分钟
30 天内合并 PR
24

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

netbox-community/netbox-scripts 的其他 Issue

查看 netbox-community/netbox-scripts 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。