Bug 31963 - Network settings always set IP
Summary: Network settings always set IP
Status: RESOLVED DUPLICATE of bug 55459
Alias: None
Product: UCS
Classification: Unclassified
Component: UMC - Computers
Version: UCS 3.1
Hardware: Other Linux
: P5 normal
Target Milestone: UCS 3.2-x
Assignee: UMC maintainers
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-12 09:28 CEST by Kevin Dominik Korte
Modified: 2023-05-22 13:53 CEST (History)
2 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):
Customer ID:
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 Kevin Dominik Korte univentionstaff 2013-07-12 09:28:32 CEST 
If a Computer is assigned an IP-Address outside the range of the network object, the IP-Address is overwritten whenever the Computer Object is edited.
Comment 1 Stefan Gohmann univentionstaff 2017-06-16 20:38:22 CEST 
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 2 Stefan Gohmann univentionstaff 2017-08-08 07:09:44 CEST 
This issue has been filed against UCS 3.1.

UCS 3.1 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.
Comment 3 Florian Best univentionstaff 2023-05-22 13:53:12 CEST 

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