Hi,
QA environment: Installed Apigee Edge 4.17.01 on Azure platform using a 9 Node standalone topology(One data center)
The 9 VMs have been configured with Redhat 7.3
Dev environment: Installed Apigee Edge 4.17.01 on Azure platform using 1 node topology
The VM has been configured with Redhat 7.2
Issue:
Therefore, we tried updating the virtual host alias through a CURL command and the router IP was reachable with the new port number.
So, in crux the CURL command updated the details, whereas the manual config file update didn't work.
2. Suppose, the virtual host details are again updated, the latest change in the virtual host alias works fine but the previous port does not respond to any proxy calls. Also, the Message processor goes down after this update.
Since, the dev installation is working fine as of now,
is there possibility of the Linux version(7.3) to have caused the issue?
4.17.01 supports RHEL 7.3, so that doesn't look like the issue here:
http://docs.apigee.com/api-services/reference/supported-software
By "The VMs for QA are not coming up" you mean, you are unable to start the OS or unable to start Edge components?
@Maudrit We are not able to start the VM (OS)