Overview

This issue occurs in the following circumstances:

1. A vFunction user logs into the vFunction Modernization Hub.
2. The user selects an App to modernize from the upper-left dropdown menu.
3. The user selects Analysis from the top, center pane.
4. Unexpectedly, a red circle with white exclamation point displays to the right of Modernization in the top, center pane. Hovering over the red circle displays a dialog box with more information about the failure.
5. Unexpectedly, the Total Classes displays as NA in the top, left-hand menu under the Analysis section.

Workaround - Controller deployed on a VM

Take the following steps to run an upgrade of the Controller:

1. SSH to the VM running the vFunction Controller.
2. Navigate to the directory where the upgrade script exists. Note that a sudoless installation will place the opt directory within the Home directory where the installation occurred: cd opt/vfunction/controller-installation
3. Run the upgrade script: bash upgrade.sh
4. Confirm in the Modernization Hub that the red circle is gone and that the Total Classes displays again.

Workaround - Controller deployed on a Container

From the Docker Build pipeline, deploy a new Container from a Build that includes the vFunction Controller Installation workflow. Once the Container is deployed, confirm that the red circle is gone and that the Total Classes displays again.

Next Steps

Take the following steps to gather more information about the failure:

1. SSH to the VM or Container running the vFunction Controller.
2. Navigate to the directory where the Controller’s scripts are stored. Note that a sudoless installation will place the opt directory within the Home directory where the installation occurred: cd opt/vfunction/controller-installation
3. Run the script to collect logs: bash collect-logs.sh
4. Navigate to the /tmp/ directory where a TGZ is created as v_controllerVersion_date_.tgz
5. Share the logs with your vFunction Technical Account Manager or vFunction Support to further investigate.
6. Unpack the TGZ: tar xvzf v_controllerVersion_date_.tgz
7. Open the directory within this unpacked TGZ. The name will match the Instance name of the Controller, such as “default.”
8. Review the vfcontroller.log, vfviper.log and vfviper-error.log files to find more information about the source of the failure.