How to preserve printer UUID/ID across restarts in cups-browsed to avoid job loss in Kubernetes with PVC

未关闭
#52 5 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
c

调研方向

该 issue 指出了 /etc/cups/printers.conf 和 /var/spool/cups;首先跟踪 cups-browsed 发现的队列生命周期,以及 CUPS 如何在 pod 重启期间将排队的作业与打印机 ID 关联起来。完成这项工作需要就持久化或队列复用行为达成一致,并验证保留的作业会在重启后继续执行,但这里没有指定测试或入口点。

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

描述

We are running a CUPS setup inside Kubernetes, where printers are dynamically discovered using cups-browsed and we persist important CUPS directories across pod restarts using PVCs (/etc/cups/printers.conf and /var/spool/cups).

Our issue arises when the client pod is deleted and recreated:

The printer UUID/ID changes in printers.conf, even though the printer name remains the same.

The print jobs retained in /var/spool/cups no longer get processed because they are no longer linked to the new printer instance.

This leads to jobs stuck in the spool with “[“No suitable Destination Host found by cups-browsed]” issues or silent failures.

From the CUPS maintainer's response, we understand that:

https://github.com/OpenPrinting/cups/discussions/1245

Print jobs on the client side can be affected by changes in printer UUID/ID.

cups-browsed can delete and recreate queues, which in turn breaks job associations.

Is there a recommended way in cups-browsed to persist or reuse the same printer UUID or ID across restarts in Kubernetes?
Alternatively, is there a way to avoid deleting/replacing queues if the discovered printer matches a previously seen printer (e.g., by hostname/IP/DeviceURI), so that queued jobs remain valid?

Our goal is to ensure that jobs in the spool directory can continue printing after a pod restart, especially in high-availability or clustered environments.

主要语言
C
星标
51
派生
21
平均合并
22 小时 49 分钟
30 天内合并 PR
6

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

OpenPrinting/cups-browsed 的其他 Issue

查看 OpenPrinting/cups-browsed 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

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