You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2019/10/18 11:37:02 UTC
[jira] [Commented] (AMBARI-25397) Upgrading
ambari-logsearch-logfeeder to 2.7.4 rpm gives warnings
[ https://issues.apache.org/jira/browse/AMBARI-25397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954523#comment-16954523 ]
Hudson commented on AMBARI-25397:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #592 (See [https://builds.apache.org/job/Ambari-branch-2.7/592/])
AMBARI-25397 Upgrading ambari-logsearch-logfeeder to 2.7.4 rpm gives (asnaik: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=470bbe96922d6970d81fcb6a564c64a6ec3d1da8])
* (edit) ambari-logsearch/ambari-logsearch-assembly/src/main/package/rpm/logfeeder/postremove.sh
> Upgrading ambari-logsearch-logfeeder to 2.7.4 rpm gives warnings
> ----------------------------------------------------------------
>
> Key: AMBARI-25397
> URL: https://issues.apache.org/jira/browse/AMBARI-25397
> Project: Ambari
> Issue Type: Task
> Components: ambari-logsearch
> Affects Versions: 2.7.4
> Reporter: Szilard Antal
> Assignee: Szilard Antal
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.5
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Customer is upgrading Ambari Logsearch to 2.7.4, while upgrading the rpm it gives below errors/warnings
> {code:java}
> ln: failed to create symbolic link '/usr/bin/logfeeder': File exists
> rm: cannot remove '/etc/ambari-logsearch-logfeeder': Is a directory
> warning: %postun(ambari-logsearch-logfeeder-2.7.4.*noarch) scriptlet failed, exit status 1
> {code}
> - The issue can be reproduced in local environment
> - Also the symlink for file "/usr/bin/logfeeder" does not get created since Ambari 2.7.4
> In Ambari 2.7.3 the symlink is created
--
This message was sent by Atlassian Jira
(v8.3.4#803005)