Search Engine: Elastic

Article ID: 129083, created on Jul 5, 2016, last review on Jul 14, 2018

  • Applies to:
  • Operations Automation 7.0
  • Business Automation 7.0
  • Business Automation 7.2


Odin Automation 7.0 Upgrade procedure - Known Issues

Issues List

  • After the upgrade, check your firewall configuration

During the upgrade, the system checks the iptables configuration. In case the system is unable to access iptables/ip6tables services, the upgrade will proceed but firewall will not be configured. In this case the respective warning message is added to upgrade log. For more information on how to harden PostgreSQL end-points of Operations Automation and Business Automation system databases, refer to this KB.

The issue occurs if the Online Store is installed in container running on Linux.

  • Upgrade fails with the following message:-

    [ERROR] Install registrar-plugins-application to MN(id=1330037) failed ...

    To successfully proceed the update procedure, do the following:

    1. Leave console with interrupted update open.
    2. Log in to Odin Automation.
    3. Go to Operations > Tasks.
    4. Find among failed the following task and reschedule it: Install registrar-plugins-application to MN
    5. After the task completes, return to console and choose to 'Retry'.
  • After the upgrade from Odin Automation 6.0.x to 7.0, the following issue may occur with your VPS service: when you log in to the CCP v1 and switch to the VPS tab, the screen shows error message instead of the VPS management dashboard.

    To fix this issue, do the following:

    1. Log in to the OACIIM node via SSH and execute commands:

      service PACI-im stop
      service PACI-im start
    2. Log in to Odin Automation MN node via SSH and execute commands:

      service pau stop
      service pau start

      Afterwards, when you enter the CCP v1 > VPS, you will see the VPS management dashboard.

  • After upgrade, you are unable to register/search domain in Online Store

    Also, synchronizing the Store gives the error:

    Synchronization failed with error:
    <title>404 Not Found</title>
    <h1>Not Found</h1>
    <p>The requested URL /aps/2/packages was not found on this server.</p>

    This can be caused by one of the following:

    1. ProxyPass is not specified. To confirm that the problem is caused by this, do the following:

      • Connect to Billing Automation Application node via ssh.
      • Check if the /etc/httpd/conf.d/ file contains similar line:

        ProxyPass /aps http://<MN_IP>:8080/aps

        If there is no such line, add it to the VirtualHost section of the file to fix the problem.

    2. Wrong connection port is set for APS Controller. To confirm that the problem is caused by this, do the following:

      • Connect to Billing Automation Application node via ssh.
      • Open the /etc/httpd/conf.d/ file and check which port is specified in the line similar to the following (443 in this example):

        <VirtualHost *:443>
      • Connect to Billing Automation Store node via ssh.
      • Open the port number for APS_CONTROLLER_URI parameter in the /usr/local/bm/templatestore/conf/ file. If the ports are different, you need to set the same port number for the APS_CONTROLLER_URI parameter as specified in the /etc/httpd/conf.d/ file for VirtualHost on Billing Automation Application node.
  • After upgrade, login change in CCPv2 is not working for some staff members and shows the error

    Error!  The unknown error is occured. Please try to use another email as login or contact with support for assistance.

    The solution is described in the article:

    Cannot update login for a staff member after upgrade to OA 7.0: The unknown error is occured.

  • After upgrade OACI VE console is not working for all VEs

    This issue appeared due to the internal software issue CCU-14487. The following error message is displayed at CCP > Cloud Infrastructure > VE name > Console:

    Session Closed. Please click on Reset Console

    To fix this issue, do the following:

    1. Edit the file /etc/httpd/conf/httpd.conf on the Branding node:

      # echo "Include conf.d/oaci.conf" >> /etc/httpd/conf/httpd.conf
    2. Reload Apache service on the Branding node:

      # service httpd reload

    This issue also described in the article:

    OACI VE console does not work: Session Closed. Please click on Reset Console.

c0f836394088a28cc30dd0e5fe8b600e caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 198398b282069eaf2d94a6af87dcb3ff b2c3b33425dfc50c7d41a2efaa7f84f3 ef171e3fccb12bd8e09076a7b49212c0 0871c0b47b3b86ae3b1af4c2942cd0ce 5356b422f65bdad1c3e9edca5d74a1ae 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF