| UCP-1836 |
If a gateway is disconnected, the system incorrectly allows the deletion of hosts or clusters. When this happens, the "Delete Host" activity is not recorded in the Activity Monitor. Consequently, these deleted resources reappear in the system whenever a new discovery is triggered.WorkaroundEnsure the gateway status is Connected before deleting any hosts or clusters. If resources have already reappeared, reconnect the gateway and perform the deletion again to ensure it is permanent and correctly logged. |
| UCP-1835 |
When the parent DC is disconnected, some UI actions remain available even though they should not be used.The following behavior is observed:
- Discover button: Visible at both the Cluster and Host levels.
- Properties tab: The Discover button is displayed within the Properties view.
- Edit Host: The Edit Host button remains active and visible at the Host level.
Expected behaviorTo prevent inconsistent states and user errors, the UI should restrict these actions when a DC is disconnected:
- The Discover button should be hidden or disabled at the Cluster, Host, and Properties tab levels.
- The Edit Host button should be hidden or disabled because configuration changes cannot be synced to a disconnected entity.
|
| UCP-1765 |
When the system performs a task that relies on other services—such as storage providers, network gateways, or internal background processes—the task may get stuck if one of those services goes offline. Because the system does not yet have an automatic timeout, these activities will remain in a Hung, In-Progress, or Cancelling state indefinitely instead of failing.Expected resultThe system should use a timeout policy. If a dependent service does not respond within a set time, the activity should automatically update to Failed or Timed_Out and generate an error log.Actual resultThe activity stays in the In-Progress or Started state forever. No error is reported, and the system continues to use up memory or processing power on the stuck task. |
| UCP-1794 |
The Luminos interface does not scale correctly on standard laptop screen resolutions. A large portion of the screen (about 50%) is taken up by fixed headers and static data at the top. This leaves very little room for active tasks, forcing users to scroll excessively both vertically and horizontally. In some cases, data remains hidden even after scrolling.Expected result
- The UI should be responsive and adapt to smaller screen resolutions.
- Static sections should be collapsible or condensed to prioritize the active workspace.
- Actionable content and dynamic data should occupy at least 70–80% of the screen.
- Header information should use a smaller font size to save space
Actual result
- The top half of the screen is filled with static information that cannot be hidden or collapsed.
- Users must constantly scroll to find and use functional areas of the application.
- On some screens, certain data remains invisible despite scrolling.
- The UI is currently optimized for large external monitors rather than standard laptop displays.
|
| UCP-1940 |
Users are logged out intermittently while actively working within the application. |
| UCP-1977 |
A navigation error is preventing users from reaching specific sections of the application. When attempting to access a specific page or feature, the UI fails to route correctly, leading to a broken user flow.Expected resultThe application should immediately route the user to the expected page or location upon clicking the designated UI element.Actual resultClicking the button or link either results in no action (user remains on the current page) or redirects the user to an incorrect/unintended location. |
| UCP-1380 |
During the creation or editing of blueprints, the user interface displays operating system versions that are incompatible with the selected InfoScale version. This occurs across multiple InfoScale releases, allowing users to select invalid combinations (example, selecting RHEL 7.9 for a newer InfoScale version that no longer supports it) which are not aligned with the official InfoScale Support Matrix.Expected resultThe OS selection should be dynamically filtered to strictly match the InfoScale Support Matrix. Only valid, supported OS versions for the specific InfoScale release should be visible and selectable.Actual resultThe UI fails to filter the OS selection list based on the chosen InfoScale version, displaying and allowing the selection of unsupported OS versions. |
| UCP-2136 |
When a cluster that was originally integrated with a CyberArk vault in the first datacenter is moved to a second datacenter and subsequently deleted from that second datacenter, its CyberArk vault host entries are permanently removed. If you later run a discovery on the first datacenter, the cluster is discovered and appears as connected, but its credential field and host entries are completely empty.Expected resultThe hosts should automatically reappear in the vault upon discovery, or the cluster should fail to be added if its corresponding vault configuration has been deleted.Actual resultThe cluster shows as connected in the first datacenter, but its vault host entries and credential details are entirely missing. |
| UCP-2240 |
An offline upgrade of the InfoScale Foundation stack from version 8.0.2.3200 to 9.2.0—performed alongside an operating system upgrade from RHEL 9.4 to RHEL 9.6—fails during the "start infoscale" task. The Storage Foundation (SF) component fails to load critical kernel modules and processes.Expected resultThe InfoScale Foundation stack should upgrade successfully on the new RHEL 9.6 kernel, and all SF component modules (vxfs, vxportal, fdd, and vxcafs) should transition to an active, started state.Actual result The automated upgrade process halts during the post-installation phase with the execution block error: SF startup failed Could not start the processes of : vxfs vxportal fdd vxcafs.WorkaroundReboot the system and retry the activity. |
| UCP-2063 |
The font size, buttons, and other interface elements within the Luminos assistant are exceptionally small, making the data difficult to read and work with. Even when the screen is set to a 75% zoom level to view the page layout properly, the UI elements remain very small and require significant effort to read. |
| UCP-1104 |
When a gateway is already registered with Luminos using a specific registration file, attempting to use that same registration file on a second gateway still causes the Luminos DCS service to generate and return a wssToken. The DCS service fails to validate whether a gateway associated with that registration file is already connected. Issuing this duplicate token is incorrect and can lead to connection conflicts or unauthorized duplicate connections.Expected resultThe DCS service should detect that the registration file is already in use by an active gateway and deny token generation for the second gateway. |
| UCP-2242 |
A failure occurs during the startup of VVR processes after patching from IS 7.4.2 + 4900 to 5900 on RHEL 7.9.WorkaroundExecute the following troubleshooting and recovery steps sequentially on each cluster node.
- Verify the volume replication administrative service status.Check the current state of the VVR administrative daemon (vras-vradmind) using the system service manager.Run the command:
systemctl status vras-vradmind
- Analyze the service state.If the service status shows as active (running), proceed to check cluster logs for other underlying errors.If the service status shows as inactive (dead), failed, or is unresponsive, proceed to Step 3.
- Restart the volume replication administrative service.Force a restart of the daemon using the systemctl utility to clear stuck execution states and properly initialize the VVR service.Run the command:
systemctl restart vras-vradmind
- Verify successful startup.Re-verify that the daemon has initialized successfully and is running without errors.Run the command:
systemctl status vras-vradmind
|
| UCP-2282 |
RHEL 9.7 is not supported for InfoScale 9.2. However, users are still able to create blueprints combining RHEL 9.7 and InfoScale 9.2. If a user creates a blueprint with this configuration and attempts an upgrade, the upgrade workflow may fail. |
