You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Steffen Roegner (JIRA)" <ji...@apache.org> on 2014/04/01 18:31:16 UTC

[jira] [Reopened] (ACCUMULO-2601) accumulo-init rpm post script attempts initialization on package upgrade

     [ https://issues.apache.org/jira/browse/ACCUMULO-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steffen Roegner reopened ACCUMULO-2601:
---------------------------------------


Thank you for the quick fix! Unfortunately this is not going to fix it completely either:

1. the post scriptlet will still be executed on upgrade
2. the 'hadoop fs mkdir' part will fail on the directory already existing - with the return code being 1 rpm reports

{code}
warning: %post(accumulo-init-1.7.0-1.el6.noarch) scriptlet failed, exit status 1
{code} 

I'd still propose to completely get rid of the post scriptlet

> accumulo-init rpm post script attempts initialization on package upgrade
> ------------------------------------------------------------------------
>
>                 Key: ACCUMULO-2601
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2601
>             Project: Accumulo
>          Issue Type: Bug
>          Components: scripts
>            Reporter: Steffen Roegner
>            Assignee: Eric Newton
>            Priority: Minor
>             Fix For: 1.6.0
>
>
> Using yum or rpm to do a package upgrade (I built 1.6.0 and 1.7.0 packages for the test) with the new accumulo meta package the upgrade will trigger the post script inside accumulo-init which will attempt to execute the full initialization sequence.
> While this could be prevented by using the argument passed to the post script (see http://www.rpm.org/max-rpm/s1-rpm-inside-scripts.html) I'd rather like to see the post script go away entirely as it requires the system to be in a perfectly prepared state to work.  



--
This message was sent by Atlassian JIRA
(v6.2#6252)