Predix Edge Manager Q3 2017

These are the enhancements, and known and resolved issues for Edge Manager.

Important Announcements

Removal of OAuth Enrollment for Edge Manager and Predix Machine
Due to a recently identified security issue with OAuth enrollment, support for OAuth-based device enrollment in Edge Manager is being discontinued effective August 22, 2017. If you already have devices in Edge Manager that were originally enrolled using OAuth authentication, they will continue to function normally. However, if you have devices added to (but not yet enrolled in) Edge Manager with OAuth as the specified method of enrollment, you will be required to delete those devices.

You then have to add the devices to US-West Edge Manager, using certificate enrollment.

In preparation for US-East retirement on September 15, 2017, you will not be able to add new devices to US-East Edge Manager tenants starting August 22nd due to a security issue.

Please contact Predix Support if you have more questions or concerns.

US-East ASV Edge Manager Retirement
Effective September 15, 2017, the Edge Manager instance in US-East will be retired. In preparation for the retirement, you will not be able to add new devices to Edge Manager tenants starting August 22nd due to a security issue.

Please contact Predix Support if you have questions, or follow these instructions to get access to US-West Edge Manger.

Known Issues

This release contains the following known issues:

  • Issues with Firefox And Chrome browsers:
    • There is a plug-in conflict that causes the browser to crash (GE internal only) when downloading a file, or when viewing the output of a command.

      The same plug-in conflict causes an error when uploading a large file (hundreds of MB).

      Workaround:

      For Firefox: Run Firefox in Safe mode to disable Firefox plug-ins.

      For Chrome:
      1. Run Chrome in Incognito mode.
      2. In Settings > Extensions, if you have the DGExtension, ensure that it is disabled by unselecting the checkbox.
  • When you update a Docker container, the Execution Time in the Deployment Schedule does not get updated in Edge Manager. Start and End times are updated and displayed correctly.
  • Operations start, execution start, and elapsed time display differently for the top level versus operation details when there is only one operation. This is due to how the summary is calculated versus how the operation detail is calculated.
  • You can create groups with the same name as an existing group and attach it to the same parent.

    Workaround: To avoid creating groups with duplicate names, verify that there are no existing groups with the same name.

  • You cannot save a filter if the name has more than 63 characters.

    Workaround: Use fewer than 63 characters in filter names.

  • If a device is placed in inventory but not enrolled, and software or configuration packages are sent to that device, and one of the Edge Manager services fails and needs to be restarted, then those software or configuration packages may need to be redeployed to that device.
  • There is a known issue with deleting a group with a large number (over 5,000) of devices. Do not create such large groups, or move devices incrementally out of large groups so you can delete the group.