Ooyala Flex 5.1.8 SR1 and SR2 Release Notes 2016-12-14

5.1.8 SR1

Components/Updates required

• Master
• Playout
• Transfer
• Index
• Job Nodes
• Reviewer

Issues Fixed in 5.1.8 SR1

Jobs are completing but still show as being in a “running” state

On multiple occasions, Jobs in Ooyala Flex were completing, but were still showing as being in a “running” state. The lock on the Assets related to these Jobs were also not being released.

Resolution: If any synchronous Jobs that are launched by another Job go into a failed state, then both the Jobs will be marked as “failed”. For example: when the Playout Publish Job fails (which is launched by the "Open Session" Job) then both Jobs (i.e. Playout Publish and Open Session) would be marked as "failed".

What’s New in 5.1.8 SR1

YouTube HTTP V3 Publish and Unpublish Actions

New Publish and Unpublish Actions have been created for the YouTube V3 API. These plugins enable you to publish Assets to YouTube and Unpublish them from YouTube. These are:

• Publish to YouTube HTTP V3
• Unpublish to YouTube HTTP V3

YouTube HTTP V3 Publish can be found here

YouTube HTTP V3 Unpublish can be found here

Note: These plugins have been created because Google has terminated their V2 APIs. This means that the V2 version of these plugins no longer work.

5.1.8 SR2

Components/Updates required

• Master
• Playout
• Transfer
• Index
• Job Nodes
• Reviewer

Issues Fixed in 5.1.8 SR2

Event Handler won’t restart after stopping

Event Handlers were able to add default Users to a production but couldn't be restarted once they had stopped. This has now been fixed.

Mio HornetQ issue

Ooyala Flex was locking Assets and preventing Workflows from running.

Solution: If any synchronous Jobs that are launched by another Job go into a failed state, then both the Jobs will be marked as “failed”. For example: when the Playout Publish Job fails (which is launched by the "Open Session" Job) then both Jobs (i.e. Playout Publish and Open Session) would be marked as "failed".

Playout is not working on S3

If Users tried to publish an Asset to S3 for Playout on 5.1.x, the Publish Player Action would not work because Playout didn’t have the S3 credentials.

Solution: We now store s3 credential details in the Playout database. We have added two fields (Key and Secret) for the s3 resource credential store. We have also created a VFS Object inside this method CacheManagerUtil:writeCachePlayerRenderedCode that will manage the authentication process of the s3 resource.