Skip to main content

Illumio Core What's New and Release Notes 22.5

Platform

  • Validation error when changing IPv6 settings on SC PCE (E-102469)

    When using a supercluster, 406 input_validation_errors occurred when changing IPv6 settings on the UI. This issue is resolved.

  • Scoped Ruleset Manager role didn't provide correct access for users (E-101513)

    Users who were members of the Scoped Ruleset Manager role couldn't access labels provided by the autocomplete feature on the Rulesets page. The PCE was filtering out labels from dimensions that weren't part of those users' scopes. This issue is resolved. Users can now view labels that belong to dimensions that are not part of their user scopes.

  • Failed to deploy the VEN bundle on PCE (E-99725)

    The 22.2.40 VEN bundle cannot be installed in the VEN library on a PCE earlier than 22.2.40 due to a limitation in the allowed VEN bundle size. The VEN can still be installed from the host or VM's command line (e.g. via RPM). The 22.2.40 PCE allows the installation of the 22.2.40 VEN bundle.

  • Consul messages not sent to internal syslog (E-99715, E-90286)

    Important

    This PCE Platform issue applies to Illumio Core On-Premises customers only. It does not apply to Illumio Core Cloud customers.

    This issue is resolved. Messages from the PCE consul service are no longer sent to the internal syslog. Messages do not appear in consul.log. Instead, they appear in /var/log/messages and /var/log/illumio-pce/consul.

  • Limit simultaneous Login (E-99304)

    A newly created local user doesn't log in again after being logged out for 15 minutes and receiving a Logout error. This issue is resolved.

  • Illumination Plus was showing deleted workloads (E-97955)

    Since deleted workloads do not provide useful information to a customer, these workloads do not show in the graph anymore. This issue is resolved.

  • Supercluster Restore issues in corner cases (E-97847)

    In a case when a PCE has already joined a supercluster, it detects when it joins another supercluster and raises an exception. Users need to reset and shut down all PCEs in the previous supercluster, and then retry the command. This issue is resolved.