Back to bug 1404169
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Petr Vobornik | 2016-12-13 10:04:52 UTC | Status | NEW | POST |
| Jan Cholasta | 2016-12-13 10:25:39 UTC | Status | POST | MODIFIED |
| Fixed In Version | ipa-4.4.0-14.el7_3.2 | |||
| errata-xmlrpc | 2016-12-13 10:27:36 UTC | Status | MODIFIED | ON_QA |
| Jan Cholasta | 2016-12-19 09:48:13 UTC | CC | jcholast, mbabinsk | |
| Flags | needinfo?(mbabinsk) | |||
| Martin Babinsky | 2016-12-19 13:42:25 UTC | Doc Text | Cause: A flaw in logic determining DNS service configuration status caused the upgrade code to always assume that DNS was configured by IdM even if this was not the case. Consequence: During upgrade of DNS-less IdM replica, named-pkcs11 systemd service is being restarted even if it was not properly configured. This results in error and crashes the whole upgrader. Fix: The code assessing DNS installation status was fixed to actually check whether named configuration file was modified by IdM installer. Result: Upgrade on IdM replica without DNS configured now does not attempt to restart named-pkcs11 service and finishes successfully. | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Flags | needinfo?(mbabinsk) | |||
| Nikhil Dehadrai | 2017-01-05 10:13:27 UTC | Status | ON_QA | VERIFIED |
| CC | ndehadra | |||
| Marc Muehlfeld | 2017-01-09 13:09:26 UTC | Docs Contact | mmuehlfe | |
| Doc Text | Cause: A flaw in logic determining DNS service configuration status caused the upgrade code to always assume that DNS was configured by IdM even if this was not the case. Consequence: During upgrade of DNS-less IdM replica, named-pkcs11 systemd service is being restarted even if it was not properly configured. This results in error and crashes the whole upgrader. Fix: The code assessing DNS installation status was fixed to actually check whether named configuration file was modified by IdM installer. Result: Upgrade on IdM replica without DNS configured now does not attempt to restart named-pkcs11 service and finishes successfully. | The Identity Management (IdM) server upgrade procedure failed to detect if the DNS service on the host is managed by IdM. As a consequence, while upgrading an IdM replica that was installed without the DNS back end, the "named-pkcs11" service was restarted and the upgrade failed. The DNS installation status code has been fixed and now verifies correctly if IdM manages the BIND configuration file on the replica. As a result, upgrading IdM on a replica without DNS back end works correctly. | ||
| errata-xmlrpc | 2017-01-17 12:05:10 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2017-01-17 18:23:26 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2017-01-17 13:23:26 UTC |
Back to bug 1404169