[AMBARI-10436] RU - Fails if in Oozie if hadoop-lzo codec is enabled after version bits have been distributed

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.1.0
• Component/s: ambari-web
• Assignee: Andrii Tkach
• Reporter: Andrii Tkach
• Created: 10/Apr/15 13:09
• Updated: 10/Apr/15 15:45
• Resolved: 10/Apr/15 13:26

Description

There's a corner-case that can cause RU to fail if a user registers a version and installs it (i.e., distributes the bits to all of the hosts. Note that at this point there was no need to download hadoop-lzo jar), and then enables lzo compression, and begins the RU, then Oozie Server restart will fail because the lzo jar was never downloaded.
lzo is enabled as follows.
There are several ways to fix this corner case:
1. Force redistribution of bits for a version that is already INSTALLED. This is more general, and can help in other scenarios, so I think it's preferable.
2. Detect what changes to the configs should transition INSTALLED versions as OUT_OF_SYNC; this is difficult to maintain.
3. Have Oozie Server RU Restart download the package; this is not desirable because the RU now has to do more work that could have been done up-front.