Bug 40610 – 4.1 all printer PPD entries are lost

Bug 40610 - 4.1 all printer PPD entries are lost


Summary:	4.1 all printer PPD entries are lost

Status:	CLOSED DUPLICATE of bug 40886

Product:	UCS
Classification:	Unclassified
Component:	UMC - Printers
Version:	UCS 4.1
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 4.1-1-errata
Assigned To:	Florian Best
QA Contact:	Felix Botner

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-02-09 15:49 CET by Jens Thorp-Hansen
Modified:	2016-04-28 16:58 CEST (History)
CC List:	6 users (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

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

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

Description Jens Thorp-Hansen

2016-02-09 15:49:24 CET

Ticket#2016020821000967
Printer setup UCS - at setup choose "Manufacturer" at another list choose "device-type" --> save.

The UCS system says Manufacturer was empty and sets default "Alps".


Ticket#2016020921000358
After Update to UCS 4.1 all Printer PPD-entries are lost. At every printer there are default entries with "Alps" as manufacturer.

LDAP and Cups-Config are configured correctly at the same time.

If you set the config in the UMC to the right settings and save and then look at the config afterwards, there is again "Alps" as manufacturer.

Comment 1 Arvid Requate

2016-02-09 18:45:40 CET

Regarding Ticket#2016020897000048 let's see what the USI shows (UCS version).
Also maybe check: udm settings/printermodel list


Regarding Ticket#2016020921000358:

> LDAP and Cups-Config are configured correctly at the same time.

So this might also be a frontend UMC display issue, possibly even in combination with a specific web browser. I'm not saying it actually is, but it might be.

Comment 2 Arvid Requate

2016-02-09 18:46:48 CET

Ticket#2016020897000048  should have been: Ticket#: 2016020821000967

Comment 3 Jens Thorp-Hansen

2016-02-10 10:26:23 CET

(In reply to Arvid Requate from comment #1)
> Regarding Ticket#2016020897000048 let's see what the USI shows (UCS version).
> Also maybe check: udm settings/printermodel list
> 
> 
> Regarding Ticket#2016020921000358:
> 
> > LDAP and Cups-Config are configured correctly at the same time.
> 
> So this might also be a frontend UMC display issue, possibly even in
> combination with a specific web browser. I'm not saying it actually is, but
> it might be.

Ticket#2016020821000967 --> USI arrived

Comment 4 Jens Thorp-Hansen

2016-02-17 11:25:40 CET

can be reproduced in the live-univention-environment --> Errata-tagged

Comment 5 Nico Stöckigt

2016-02-26 14:09:38 CET

happened also here: Ticket#2016022621000272

Comment 6 Stefan Gohmann

2016-02-26 14:20:51 CET

If I understand it correctly, it is "only" a display error in UMC. Right?

Comment 7 Florian Best

2016-02-26 15:20:53 CET

(In reply to Stefan Gohmann from comment #6)
> If I understand it correctly, it is "only" a display error in UMC. Right?
No. It's not a display error. The problem is that the settings/printermodel for that printer-model does not exists. They got removed during the update.

Should I inspect this? The USI probably contains information in the updater.log.

I think Tim or Janis once created a Bug for this already that the upgrade to 4.0 / 4.1? removed every settings/printermodel from the LDAP. I can't find the bug currently.

Comment 8 Stefan Gohmann

2016-02-26 15:25:49 CET

(In reply to Florian Best from comment #7)
> (In reply to Stefan Gohmann from comment #6)
> > If I understand it correctly, it is "only" a display error in UMC. Right?
> No. It's not a display error. The problem is that the settings/printermodel
> for that printer-model does not exists. They got removed during the update.
> 
> Should I inspect this? The USI probably contains information in the
> updater.log.
> 
> I think Tim or Janis once created a Bug for this already that the upgrade to
> 4.0 / 4.1? removed every settings/printermodel from the LDAP. I can't find
> the bug currently.

Because it has been fixed: Bug #38117.

Comment 9 Florian Best

2016-02-26 15:33:21 CET

We need the following output on the specified system:
univention-ldapsearch univentionObjectType=shares/printer
univention-ldapsearch univentionObjectType=settings/printermodel printerModel -LLL | ldapsearch-wrapper

Comment 10 Nico Stöckigt

2016-02-29 13:54:05 CET

(In reply to Florian Best from comment #9)
> We need the following output on the specified system:
> univention-ldapsearch univentionObjectType=shares/printer
> univention-ldapsearch univentionObjectType=settings/printermodel
> printerModel -LLL | ldapsearch-wrapper

mentioned ticket#2016022621000272 has requested informations attached.

Comment 11 Florian Best

2016-02-29 14:11:11 CET

(In reply to Nico Stöckigt from comment #10)
> (In reply to Florian Best from comment #9)
> > We need the following output on the specified system:
> > univention-ldapsearch univentionObjectType=shares/printer
> > univention-ldapsearch univentionObjectType=settings/printermodel
> > printerModel -LLL | ldapsearch-wrapper
> 
> mentioned ticket#2016022621000272 has requested information attached.
This works for me if I add entries like those. It always sets the printermodel to misc / smb. Is the error also when accessing the printer as "Administrator" user?

Comment 12 Florian Best

2016-03-11 11:10:56 CET

This is caused by Bug #40886. Workaround to fix this is:
invoke-rc.d slapd stop; slapindex; invoke-rc.d slapd start

*** This bug has been marked as a duplicate of bug 40886 ***

Comment 13 Felix Botner

2016-04-28 15:45:32 CEST

OK, duplicate