Bug 1211658 – printer rename leaves stale entries in the cache

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1211658 - printer rename leaves stale entries in the cache

Summary:	printer rename leaves stale entries in the cache

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	samba (Show other bugs)
Sub Component:
Version:	7.1
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	rc
Target Release:	---
Assigned To:	Andreas Schneider
QA Contact:	Robin Hack
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	1211657
Blocks:
	Show dependency tree / graph

Reported:	2015-04-14 10:09 EDT by Andreas Schneider
Modified:	2015-11-19 04:11 EST (History)
CC List:	6 users (show)

See Also:
Fixed In Version:	samba-4.2.2-1.el7
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:	1211657
Environment:
Last Closed:	2015-11-19 04:11:47 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Samba Project	11210	None	None	None	Never
Red Hat Product Errata	RHBA-2015:2258	normal	SHIPPED_LIVE	samba bug fix and enhancement update	2015-11-19 04:22:47 EST

Groups: None (edit)

Description Andreas Schneider 2015-04-14 10:09:28 EDT

+++ This bug was initially created as a clone of Bug #1211657 +++

Description of problem:

Currently the name cache is only cleared on printer deletion. This means that if a printer undergoes a name change, the old name remains in the cache and can be subsequently used incorrectly if another printer takes the same name as the old.

Comment 4 errata-xmlrpc 2015-11-19 04:11:47 EST

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2258.html

Note You need to log in before you can comment on or make changes to this bug.