Sandeep, Upgrade depends on the installed build version and the build version that is being upgraded to. When you upgrade, yum prints the existing build version and version being upgraded to.
The behavior of conf --> conf.save is expected. This is to preserve any config change that might have happened to ambari-agent.ini. The manual step, after upgrade, is to rename the folder back to "conf". We are working on developing post-install scripts that will automate the step but that is not final yet. -Sumit On 4/7/13 1:22 AM, "Sandeep Baldawa" <[email protected]> wrote: >Hi, > >Had couple of questions on agent upgrade. > >- What is the expected behaviour when "yum install >target/rpm/ambari-agent/RPMS/ >x86_64/ambari-agent-1.3.0-SNAPSHOT2013" is ran twice or more, does the >agent behave like it is getting upgraded, because doing this causes >"/etc/ambari-agent/conf/ambari-agent.ini", to be changed to >"/etc/ambari-agent/conf.save/ambari-agent.ini". Might not be good to >consider this as an upgrade scenario since we are installing the same >agent >version here. > >- Also since /etc/ambari-agent/conf/ambari-agent.ini", is changed to >"/etc/ambari-agent/conf.save/ambari-agent.ini" the agent gets disconnected >from the server. Is this an expected behaviour after upgrade? > >Thanks, >Sandeep
