In JCMA 1.11.11 and above, if the the new reporting url is not whitelisted, the migration cannot be executed although the preflight check throws a "Warn" message

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • None
    • Affects Version/s: JCMA - 1.11.11, JCMA - 1.11.12
    • None
    • 10
    • Severity 3 - Minor
    • 50

      Issue Summary

      The public documentation in regards to preparing your firewall/ network to migrate was modified for a while to include the new reporting urls (i.e. "_https://rps--*--migration-report-center--report-data.s3.*.amazonaws.com_" ) , however, in JCMA 1.11.11 and above, whitelisting this URL was added into the preflight checks while previously it was not.

      Although in the preflight checks this is displayed as a warn and the "Run" button of the plan will be active, executing the migration will only save the plan as during the execution preflight checks the warn will be thrown again. This blocks the migrator from executing the migration until the url is whitelisted

      This is reproducible on Data Center: (yes)

      Steps to Reproduce

      1. Step 1
        Create a plan on an instance not having this url whitelisted
      2. Step 2
        Execute the migration

      Expected Results

      The check to throw a "Fail" rather than "Warn", indicating clearly the migration cannot be performed without whitelisting the needed address or allow the migrator to continue as the check throws a "Warn", informing that the error logs will not be available if the migration is performed on this manner.

      Actual Results

      After the migrator hits "Run", the plan will only be saved and re performing the checks will only end up in a loop without being able to run the migration until the ip domain is whitelisted.

      Workaround

      Whitelist the needed address.

      Only in exceptional cases, if you have successfully tested with an older version of JCMA, continue to use the older version, by following this article. , although this approach is not recommended as newer version bring improved reliability.

            Assignee:
            Mandeep Kaur (Inactive)
            Reporter:
            Dan Postelnicu
            Votes:
            1 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: