{"action":"created","issue":{"url":"https://api.github.com/repos/quattor/CAF/issues/89","labels_url":"https://api.github.com/repos/quattor/CAF/issues/89/labels{/name}","comments_url":"https://api.github.com/repos/quattor/CAF/issues/89/comments","events_url":"https://api.github.com/repos/quattor/CAF/issues/89/events","html_url":"https://github.com/quattor/CAF/issues/89","id":74038884,"number":89,"title":"perl-CAF update should trig a ncm-cdispd restart","user":{"login":"jouvin","id":1511937,"avatar_url":"https://avatars.githubusercontent.com/u/1511937?v=3","gravatar_id":"","url":"https://api.github.com/users/jouvin","html_url":"https://github.com/jouvin","followers_url":"https://api.github.com/users/jouvin/followers","following_url":"https://api.github.com/users/jouvin/following{/other_user}","gists_url":"https://api.github.com/users/jouvin/gists{/gist_id}","starred_url":"https://api.github.com/users/jouvin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jouvin/subscriptions","organizations_url":"https://api.github.com/users/jouvin/orgs","repos_url":"https://api.github.com/users/jouvin/repos","events_url":"https://api.github.com/users/jouvin/events{/privacy}","received_events_url":"https://api.github.com/users/jouvin/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-05-07T16:05:21Z","updated_at":"2015-05-07T19:09:43Z","closed_at":null,"body":"During deployment of `15.4.0-rc1` (https://github.com/quattor/release/issues/85), I was (again) in a situation where It basically works but `ncm-ncd` fails during the update itself. Below are the last lines from `ncm-cdispd` corresponding to the upgrade:\r\n\r\n```\r\n2015/05/07-17:34:04 [WARN] ncm-ncd finished with status: 255 (ec 65280, some configuration modules failed to run successfully)\r\n2015/05/07-17:34:46 [WARN] Component ccm failed with message: cannot execute configure on component ccm\r\n2015/05/07-17:34:46 [WARN] Component network failed with message: cannot execute configure on component network\r\n2015/05/07-17:34:46 [WARN] ncm-ncd finished with status: 255 (ec 65280, some configuration modules failed to run successfully)\r\n2015/05/07-17:34:46 [INFO] Processing delayed signal TERM\r\n2015/05/07-17:34:46 [WARN] signal handler: signal TERM received\r\n2015/05/07-17:34:46 [WARN] terminating ncm-cdispd...\r\n```\r\n\r\nDoing aonther deploy or restarting `ncm-cdispd`, the next run is ok:\r\n\r\n```\r\n2015/05/07-17:45:04 [INFO] new profile arrived, examining...\r\nupdated /var/lib/ccm/profile.414/ccm-active-profile.414-2520\r\n2015/05/07-17:45:04 [INFO] new profile identical but re-running ncm-ncd since last execution reported errors\r\n2015/05/07-17:45:04 [INFO] about to run: /usr/sbin/ncm-ncd --configure profile grub network ccm vomsclient hostsaccess sysconfig altlogrotate aiiserver named modprobe dirperm spma dpmlfc cdp ldconf accounts filecopy xrootd mkgridmap iptables gip2 mysql cron etcservices nrpe chkconfig gridmapdir ntpd useraccess sudo lcgbdii --state /var/run/quattor-components\r\n2015/05/07-17:45:43 [INFO] ncm-ncd finished with status: 0 (ec 0, all configuration modules ran successfully)\r\n```\r\n\r\nThis is not a blocking issue as the next deployment after the update completes successfully. But I think that this happens when `perl-CAF` is updated if `ncm-cdispd` is not restarted because `ncm-ncd` tries to use a `CAF` version removed since it has started and this is causing some side effects. I'd suggest adding a post install script restarting `ncm-cdispd` as part of the `perl-CAF` upgrade."},"comment":{"url":"https://api.github.com/repos/quattor/CAF/issues/comments/99984979","html_url":"https://github.com/quattor/CAF/issues/89#issuecomment-99984979","issue_url":"https://api.github.com/repos/quattor/CAF/issues/89","id":99984979,"user":{"login":"jouvin","id":1511937,"avatar_url":"https://avatars.githubusercontent.com/u/1511937?v=3","gravatar_id":"","url":"https://api.github.com/users/jouvin","html_url":"https://github.com/jouvin","followers_url":"https://api.github.com/users/jouvin/followers","following_url":"https://api.github.com/users/jouvin/following{/other_user}","gists_url":"https://api.github.com/users/jouvin/gists{/gist_id}","starred_url":"https://api.github.com/users/jouvin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jouvin/subscriptions","organizations_url":"https://api.github.com/users/jouvin/orgs","repos_url":"https://api.github.com/users/jouvin/repos","events_url":"https://api.github.com/users/jouvin/events{/privacy}","received_events_url":"https://api.github.com/users/jouvin/received_events","type":"User","site_admin":false},"created_at":"2015-05-07T19:09:43Z","updated_at":"2015-05-07T19:09:43Z","body":"I agree that this is something to review. Anyway, I still think that adding the (conditional) restart during RPM installation may help to catch the corner cases..."}}