Bug 32269 - IP address by 2nd network object not used
Summary: IP address by 2nd network object not used
Status: RESOLVED WONTFIX
Alias: None
Product: UCS
Classification: Unclassified
Component: UMC - Computers
Version: UCS 3.2
Hardware: Other Linux
: P5 normal
Target Milestone: UCS 3.2-x
Assignee: UMC maintainers
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-20 10:23 CEST by Philipp Hahn
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
Screenshot showing computer wizard (87.90 KB, image/png)
2013-08-20 10:23 CEST, Philipp Hahn
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Hahn univentionstaff 2013-08-20 10:23:51 CEST
Created attachment 5383 [details]
Screenshot showing computer wizard

In addition to the default network object I have a 2nd network configuration "PHahn" for my IP address range 10.200.17.0/24. When I create a new computer object (member server) and select this object, an IP address is allocated for computer, but the address can't be selected for the DNS entries below: Only an empty field is added and the assigned IP can't be selected.

If i toggle the Network object to "default" and than back to "PHahn", it works and the address is copied correctly.

# dpkg-query -W univention-management-console\*
univention-management-console   6.0.6-1.744.201307291518
univention-management-console-dev       6.0.6-1.744.201307291518
univention-management-console-doc       6.0.6-1.744.201307291518
univention-management-console-frontend  3.0.58-1.695.201308161433
univention-management-console-frontend-doc      6.0.11-1.33.201303191551
univention-management-console-frontend-src      3.0.58-1.695.201308161433
univention-management-console-module-appcenter  3.0.16-1.168.201308131311
univention-management-console-module-apps       3.0.16-1.168.201308131311
univention-management-console-module-ipchange   2.0.4-1.11.201211201458
univention-management-console-module-join       6.0.4-1.448.201308151704
univention-management-console-module-lib        3.0.3-1.17.201308151719
univention-management-console-module-mrtg       2.0.2-1.15.201211061850
univention-management-console-module-packages
univention-management-console-module-quota      8.0.1-1.113.201307111312
univention-management-console-module-reboot     3.0.1-1.4.201306121518
univention-management-console-module-services   2.0.4-1.15.201211061854
univention-management-console-module-setup      7.0.26-1.495.201308151636
univention-management-console-module-sysinfo    3.0.10-1.41.201304191335
univention-management-console-module-top        2.0.5-1.22.201303071457
univention-management-console-module-ucr        3.0.0-1.46.201306171339
univention-management-console-module-udm        4.0.12-1.332.201308061333
univention-management-console-module-updater    9.0.10-2.1197.201308191604
univention-management-console-module-uvmm       3.0.6-9.466.201308191614
univention-management-console-server    6.0.6-1.744.201307291518
univention-management-console-web-server        3.0.58-1.695.201308161433
Comment 1 Stefan Gohmann univentionstaff 2017-06-16 20:36:34 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:11:05 CEST
This issue has been filed against UCS 3.2.

UCS 3.2 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.