Bug 44873 – import_networks aborts when network already exists

Bug 44873 - import_networks aborts when network already exists


Summary:	import_networks aborts when network already exists

Status:	CLOSED WONTFIX

Product:	UCS@school
Classification:	Unclassified
Component:	Import scripts
Version:	UCS@school 4.1 R2
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS@school maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-06-27 16:02 CEST by Nico Stöckigt
Modified:	2023-06-12 15:39 CEST (History)
CC List:	3 users (show)

See Also:	44871
What kind of report is it?:	Bug Report
What type of bug is this?:	2: Improvement: Would be a product improvement
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.023
Enterprise Customer affected?:
School Customer affected?:	Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2017062621000441
Bug group (optional):
Max CVSS v3 score:

Attachments
First, untested attempt for a fix (6.49 KB, patch) 2017-06-28 16:50 CEST, Sönke Schwardt-Krummrich	Details \| Diff
View All 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 Nico Stöckigt

2017-06-27 16:02:14 CEST

The Script '/usr/share/ucs-school-import/scripts/import_networks' stops unsuccessful when the network already exists. Instead it should continue and also create the related policies. imho a Patch (around line 1733) would be tiny and neat.

Comment 1 Sönke Schwardt-Krummrich

2017-06-28 16:50:14 CEST

Created attachment 8980 [details]
First, untested attempt for a fix

Comment 2 Sönke Schwardt-Krummrich

2019-02-05 21:43:10 CET

This issue has been filled against UCS@school 4.1 (R2). The maintenance with
bug and security fixes for UCS@school 4.1 (R2) has ended on 5th of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3 (or later). 
Please contact your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug"
or simply reopen the issue. In this case please provide detailed information on
how this issue is affecting you.