Known Issue: The virtual host configuration in OPDK disappeared unexpectedly

3 0 771

Customers use OPDK releases older than 4.15.01 could experience a problem such that some of their configuration for an environment disappears suddenly while no known administrative changes were made to the environment. Recently, a customer lost their 'default' virualhost for a development environment.

Problem: the 'default' virtual host disappeared. Recreating the default virtual host would receive the 201 status code indicating the virtualhost entry is created. However, the immediate GET operation of the newly created virtualhost would result in the status code - 404 Not Found.

Symptoms: Developers could no longer deploy proxy changes to the environment. UI is not showing the virtualhost under APIs -> Environment Configuration.

Possible Cause: Apigee stores the configuration information for organizations and environments in Cassandra. When there are more than 200 columns in a column family and if the desired configuration is not within the 200 columns returned to the Apigee management server query, then Apigee would return a 404 even though the column exists in Cassandra. In this case, the default virtual host was not returned within the 200 columns while it exists in Cassandra.

How to verify: Assuming the org name is ‘apigeetest' and the environment is ‘dev’. Log onto a Cassandra node, and cd to the bin directory of the Cassandra installation.

$ ./cassandra-cli -h 0 
Connected to: “cnode1" on 0/9160 

Welcome to Cassandra CLI version 1.2.19 

Type 'help;' or '?' for help. 
Type 'quit;' or 'exit;' to quit. 

[default@unknown] use apprepo; 
Authenticated to keyspace: apprepo 
[default@apprepo] consistencylevel as LOCAL_QUORUM; 
[default@apprepo] get environments[’apigeetest@dev’]; 


You should see the number of results returned at the end of the output.

What to do: Delete entries that are no longer needed. The entries returned in Cassandra are hexadecimal strings, so you might want to go to a hex to ascii website to convert the hexadecimal string and see what is to keep or delete. In this case, the customer does not need many shared resources and once the shared resources are deleted via the UI and management API calls, the virtual hosts are visible again.

The fix is in 4.15.01.

Version history
Last update:
‎02-24-2015 01:30 PM
Updated by: