You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Dmitry Lysnichenko (JIRA)" <ji...@apache.org> on 2014/02/18 20:00:20 UTC

[jira] [Updated] (AMBARI-4702) Create hash files on agent rpm creation

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

Dmitry Lysnichenko updated AMBARI-4702:
---------------------------------------

    Attachment: patch.patch

I've attached a patch that applies on top of a patch for AMBARI-4481 . Will create a review request once AMBARI-4481 is committed

> Create hash files on agent rpm creation
> ---------------------------------------
>
>                 Key: AMBARI-4702
>                 URL: https://issues.apache.org/jira/browse/AMBARI-4702
>             Project: Ambari
>          Issue Type: Task
>          Components: agent, test
>    Affects Versions: 1.5.0
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 1.5.0
>
>         Attachments: patch.patch
>
>
> Currently, stack script and custom action script files are included both to ambari-agent and to ambari-server rpms. So agent comes with pre-packaged file cache. The issue is that files that are packaged into an agent cache are not hashed (no ".hash" files exist), that's why after rpm installation agent considers it's cache stale and tries to update cache from the server. I'm going to add on-fly hash files creation during rpm generation. These ".hash" files will be created during mvn build process in "target" directory and will not be visible for git.
> Zip files will not be generated and/or included into agent rpm



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)