Addressed Issues in Panorama Plugin for AWS 1.0.1

The following list describes fixed issues in the Panorama plugin for AWS 1.0.1.

PLUG-3806

When upgrading the Panorama plugin for AWS on peers configured as an HA pair, if you upgrade the plugin on the secondary peer first and the peer becomes active, the primary (now passive) cannot function as an HA peer.
Workaround
—When upgrading the Panorama plugin for AWS on peers that are configured as an HA pair, you must install the plugin on the primary peer
first
and commit your changes
immediately
, and then install the same plugin version on the secondary peer and commit your changes immediately.
This issue is fixed in Panorama plugin for AWS, version 1.0.1.

PLUG-2000

Spaces and special characters in user-defined tags are now treated differently. In previous releases both spaces and special characters caused a tag to be ignored. In the current release, user-defined tags containing empty spaces can be retrieved, provided they do not include special characters.
  • An empty space in a user-defined tag is replaced with “/”, allowing the tag to be retrieved.
    For example, if your tag is
    finance and accounts
    , the tag can be retrieved.
  • User-defined tags with special characters are ignored and not retrieved.
    For example, if your tag is
    finance&accounts
    , your tag is ignored and the log shows the following message:
    admin@Panorama>
    less plugins-log plugin_aws_ret.log
    2019-12-06 02:27:07.040 +0000 INFO: : vpc-0321945805d495d89: Tag aws.ec2.tag.Tag-spcl-char.<finance>&<accounts> has unsupported chars.. Ignoring...
Workaround
—Modify the tag to remove special characters.
This issue is fixed in the Panorama plugin for AWS, version 1.0.1.

Recommended For You