Introduction

This document describes the new features, open caveats, and resolved caveats in Cisco Virtual Media Recorder (VMR) Release 1.4.1_058.

Compatibility:

  • MemSQL 6.5 is required for VMR 1.4.1

  • Cisco Cloud Object Store (COS) v3.18.b2+

  • OpenShift COE v1.5.1 or 3.7.2

Software Upgrade

For instructions on upgrading the VMR application instance controller (AIC) and VMR Services, see the Cisco Virtual Media Recorder Release 1.4.1 Deployment Guide.

New Features

The following is a list of new features for VMR Release 1.4.1.

Table 1. New Features in VMR 1.4.1

Feature

Description

Important Notice:VMR and V2PC integration will no longer be supported in VMR 1.4.2.

Integration between VMR and V2PC will no longer be supported in the next VMR release (1.4.2). Cisco highly recommends you follow the procedures in the Installing and Upgrading VMR Standalone on COE 3.7.2 chapter of the Cisco Virtual Media Recorder 1.4.1 Deployment Guide for new deployments.

VMR Standalone with Ansible (New)

Support for installing and upgrading VMR Standalone with Ansible on COE 3.7.2.

COS Health Monitoring (New)

Monitoring the health of the COS nodes is turned on by default. See the Cisco Virtual Media Recorder User Guide for additional information.

Support for OpenShift COE Version 3.7.2 (New)

OpenShift COE v3.7.2 is now supported.

Label VMR Nodes (New)

To improve resource management, for VMR 1.4.1 and later, the VMR components are distributed on a separate set of minion nodes than the other components. When installing OpenShift, you must specify and label which minion nodes will be used for the VMR components (labeled vmrk8s=true) and which minion nodes will be used for the other components (labeled vmrk8s=false). See OpenShift Requirements in the Cisco Virtual Media Recorder Deployment Guide.

MemSQL v6.5 (New)

MemSQL v6.5 is required for VMR 1.4.1.

Known Issues

This section lists open and resolved issues for Cisco VMR Release 1.4.1_058. The issues describe unexpected behavior in VMR software releases. Severity 1 bugs are the most serious issues; severity 2 bugs are less serious. Severity 3 bugs are moderate issues, and only selected severity 3 bugs are included in this section.

Open Issues

The following is a list of open issues in Release 1.4.1_058. Bug details are displayed in the Bug Search.

Table 2. Open Issues in VMR 1.4.1_058

Bug ID

Description

Playback of HTTP URLs in an HTTPS Dashboard may fail. As a workaround, configure the browser as described in the Troubleshooting chapter in the Cisco Virtual Media Recorder Deployment Guide.

CSCvk45942

Upgrade fails due to Archive Agent Config Map template error. See workaround in the Cisco Virtual Media Recorder Deployment Guide, Troubleshooting chapter.

CSCvj65508

Upgrade fails due to lost Zookeeper data. See workaround in the Cisco Virtual Media Recorder Deployment Guide, Troubleshooting chapter.

CSCvj86124

Upgrade from VMR standalone to vmr-bundle (1.4.1 or 1.4.2) will complete but the dash-origin pods will fail in rolling update due to a mismatch in the dash-origin deployment template; VMR standalone will have duplicate entries for MANIFEST_LOAD_TIMEOUT. See workaround in the Cisco Virtual Media Recorder Deployment Guide, Troubleshooting chapter.

CSCvm12395

When installing VMR 1.4.1_0XX, only one A8Updater POD is deployed; the A8Updater default replica count should be 4.

To resolve this issue, apply the VMR-Bundle-1.4.1_099 patch, as described in the Cisco Virtual Media Recorder 1.4.1 Deployment Guide.

CSCvm40032

VMR API returns 403 forbidden error when querying for storage or MemSQL endpoints from OpenShift.

To resolve this issue, apply the VMR-Bundle-1.4.1_099 patch, as described in the Cisco Virtual Media Recorder 1.4.1 Deployment Guide.

CSCvm60964

Health Agent fails to establish connection to the MemSQL nodes on deployments or upgrades using VMR Bundle 1.4.1_0xx. If this occurs, the Health Agent cannot monitor the MemSQL nodes.

To resolve this issue, apply the VMR-Bundle-1.4.1_099 patch, as described in the Cisco Virtual Media Recorder 1.4.1 Deployment Guide.

CSCvm93805

A 413 Request Entity Too Large error may occur during bulk recording/delete requests in VMR. This error occurs because the default value for the maximum recordings request is set to 60.

To resolve this issue, apply the VMR-Bundle-1.4.1_099 patch, as described in the Cisco Virtual Media Recorder 1.4.1 Deployment Guide.

CSCvm27234

Rio API is not configured to fetch archive-storage endpoints from K8s.

To resolve this issue, apply the VMR-Bundle-1.4.1_099 patch, as described in the Cisco Virtual Media Recorder 1.4.1 Deployment Guide.

CSCvn09072

Missing storage related configurations in the Health Agent deployment template in VMR bundle.

To resolve this issue, apply the VMR-Bundle-1.4.1_099 patch, as described in the Cisco Virtual Media Recorder 1.4.1 Deployment Guide.

CSCvm85222

During cyclic Recon/Rearchive loop, a 500 error for PUTCOPY/DELETE may occur on COS due to the same segment.

To resolve this issue, apply the VMR-Bundle-1.4.1_099 patch, as described in the Cisco Virtual Media Recorder 1.4.1 Deployment Guide.

Closed Issues

The following is a list of closed issues in Release 1.4.1.

Table 3. Closed Issues in VMR 1.4.1

Bug ID

Description

CSCvi48336

[Archive Agent - RecGC - Bulk Delete] RECGC_GRP_SIZE is incorrectly configured

CSCvg58653

DO Errors: no segments passed in during AS builder

CSCvk42205

BMW SQL syntax error in internal query

CSCvk61314

DO panics

CSCvj99749

DO panics during location query

CSCvj02989

Blink Logs Thresholds are not exposed.

CSCvi77151

MA log missing count of total IRIDS in log

CSCvk63001

DO - handling of 404, causes 302 redirect to MPE with no URL

CSCvk76322

DO sends 502 to client

CSCvm27234

fetch archive-storage endpoints from k8s

CSCvm01065

Clear group id if segment tracking is disabled

CSCvm36848

VF MA doesn't mark recordings as ErrorCode=1

CSCvm48785

Change MAX_ALLOWED_LIVEPOINT_DRIFT to 60secs

CSCvm52261

VMR Dashboard times out with API error

CSCvm49769

DO panics with "Illegal RIO Error code (1711) requested

CSCvm60964

Health Agent fails to establish connection to the MemSQL nodes

Related Documentation

Refer to the following documents for additional information about VMR 1.4.1: