| Summary: | Admin console show old port number | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Directory Server | Reporter: | Kamlesh <kchaudha> | ||||
| Component: | Directory Console | Assignee: | Noriko Hosoi <nhosoi> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Viktor Ashirov <vashirov> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 10.0 | CC: | kbanerje, kchaudha, nhosoi | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-09-30 12:02:05 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
Is it a refresh issue? If you force to refresh, is it updated? How about restart the Console? I'd also think it is not a regression. (In reply to Noriko Hosoi from comment #1) > Is it a refresh issue? No it is not refresh issue. > If you force to refresh, is it updated? In Admin Console there is no refresh option. > How about restart the Console? I restarted the console but still it shows old value > I'd also think it is not a regression. I tried on the RHEL 7.2 with old repos 389-adminutil-devel-1.1.22-1.el7dsrv.x86_64 389-ds-console-1.2.12-1.el7dsrv.noarch 389-ds-console-doc-1.2.12-1.el7dsrv.noarch 389-console-1.1.15-1.el7dsrv.noarch redhat-idm-console-10.0.0-6.el7dsrv.x86_64 idm-console-framework-1.1.14-1.el7dsrv.noarch 389-ds-base-1.3.4.0-19.el7.x86_64 389-admin-1.1.42-1.el7dsrv.x86_64 redhat-idm-console-debuginfo-10.0.0-6.el7dsrv.x86_64 389-adminutil-1.1.22-1.el7dsrv.x86_64 389-admin-console-1.1.10-1.el7dsrv.noarch 389-ds-base-libs-1.3.4.0-19.el7.x86_64 Before changing the port #[root@vm-idm-020 ~]# netstat -ntlp | grep ns-slapd tcp6 0 0 :::636 :::* LISTEN 32677/ns-slapd tcp6 0 0 :::389 :::* LISTEN 32677/ns-slapd After Changing the port #[root@vm-idm-020 ~]# netstat -ntlp | grep ns-slapd tcp6 0 0 :::5500 :::* LISTEN 565/ns-slapd tcp6 0 0 :::389 :::* LISTEN 565/ns-slapd Result But still it shows old value Work on New Environment |
Created attachment 1205261 [details] Screen-shot Description of problem: If we change change the port number of nsslapd-secureport the admin console show the old port number. Version-Release number of selected component (if applicable): 389-ds-console-1.2.13-1.el7dsrv.noarch redhat-idm-console-10.1.0-1.el7dsrv.x86_64 389-admin-console-1.1.12-1.el7dsrv.noarch 389-ds-base-1.3.5.10-11.el7.x86_64 How reproducible: always Steps to Reproduce: 1.[root@test ~]# ldapsearch -D "cn=Directory Manager" -h test.example.com -w test1234 -s base -b "cn=config" nsslapd-port nsslapd-secureport -LLL dn: cn=config nsslapd-port: 389 nsslapd-secureport: 636 2. ]# ldapmodify -x -h test.example.com -p 389 -D "cn=directory manager" -w test1234 dn: cn=config changetype: modify replace: nsslapd-secureport nsslapd-secureport: 5636 modifying entry "cn=config" 3.# semanage port -a -t ldap_port_t -p tcp 5636 4.# restart-ds-admin 5.# restart-dirsrv Restarting instance "test" 6.# ldapsearch -D "cn=Directory Manager" -h test.example.com -w test1234 -s base -b "cn=config" nsslapd-port nsslapd-secureport -LLL dn: cn=config nsslapd-port: 389 nsslapd-secureport: 5636 Actual results: show old port number Expected results: Additional info: