Back to bug 1401632
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Roshni | 2016-12-05 18:37:40 UTC | Keywords | TestBlocker | |
| Roshni | 2016-12-09 17:28:34 UTC | Component | coolkey | coolkey |
| Version | 7.3 | 6.9 | ||
| Product | Red Hat Enterprise Linux 7 | Red Hat Enterprise Linux 6 | ||
| Bob Relyea | 2016-12-12 18:23:56 UTC | CC | rpattath | |
| Flags | needinfo?(rpattath) | |||
| Roshni | 2016-12-12 18:59:05 UTC | Flags | needinfo?(rpattath) | |
| Roshni | 2016-12-13 20:25:54 UTC | CC | jhrozek, pkis | |
| Component | coolkey | nss-pam-ldapd | ||
| Assignee | rrelyea | jhrozek | ||
| Summary | Smartcard authentication fails inconsistently | nslcd fails to restarted intermittently | ||
| QA Contact | aakkiang | qe-baseos-security | ||
| Roshni | 2016-12-13 21:14:06 UTC | Doc Type | If docs needed, set a value | Release Note |
| Arthur de Jong | 2016-12-13 21:22:00 UTC | CC | arthur | |
| Jakub Hrozek | 2016-12-14 08:36:38 UTC | Flags | needinfo?(rpattath) | |
| Roshni | 2016-12-14 14:12:28 UTC | Flags | needinfo?(rpattath) | |
| Lenka Špačková | 2016-12-20 10:12:50 UTC | Doc Type | Release Note | Known Issue |
| Flags | needinfo?(jhrozek) | |||
| Lenka Špačková | 2016-12-20 10:15:05 UTC | CC | lkuprova | |
| Jakub Hrozek | 2016-12-20 11:21:00 UTC | Flags | needinfo?(rpattath) | |
| Jakub Hrozek | 2016-12-20 11:22:57 UTC | Doc Text | Cause: if nslcd is started before networking is fully up, it fails to connect to LDAP server Consequence: resolving user or group identities would not work Workaround (if any): start nslcd after networking is up Result: if nslcd is started after networking is up, all is fine. | |
| Flags | needinfo?(jhrozek) needinfo?(rpattath) | |||
| Roshni | 2016-12-20 13:38:16 UTC | Keywords | TestBlocker | |
| Lenka Špačková | 2016-12-20 14:23:15 UTC | Docs Contact | lkuprova | |
| Doc Text | Cause: if nslcd is started before networking is fully up, it fails to connect to LDAP server Consequence: resolving user or group identities would not work Workaround (if any): start nslcd after networking is up Result: if nslcd is started after networking is up, all is fine. | *nslcd* fails to resolve user or group identities when it is started before the network connection is fully up When *nslcd*, the local LDAP name service daemon, is started before the network connection is fully up, the daemon fails to connect to an LDAP server. As a consequence, resolving user or group identities does not work. To work around this problem, start *nslcd* after the network connection is up. |
||
| Tom Lavigne | 2017-01-12 19:13:41 UTC | CC | tlavigne | |
| Jakub Hrozek | 2017-11-15 22:13:35 UTC | Status | NEW | CLOSED |
| Resolution | --- | WONTFIX | ||
| Last Closed | 2017-11-15 17:13:35 UTC |
Back to bug 1401632