ZZ00494: UPDATE DOCUMENTATION TO DESCRIBE HOW TO REMOVE A REGION

IBM Cloud Orchestrator Fix Pack 4 (2.4.0.4) for 2.4

APAR status

• Closed as documentation error.

Error description

• -----------------------------
  
  Removing a Region in ICM
  
  1. Remove all instances in the Region which you want to delete.
  2. Remove all aggregate in the Region which you want to delete.
  
  
  nova --os-region-name RegionOne aggregate-list
  
  # Print a list of all aggregates in the Region which you want
  to
  delete.
  
  
  
  nova --os-region-name RegionOne aggregate-remove-host <id>
  
  <host>
  
  # Remove the host with name <host> from the aggregate with id
  
  <id>.
  
  
  
  nova --os-region-name RegionOne aggregate-delete <id>
  
  # Delete an aggregate with id <id>.
  
  
  
  3. Remove all availability zone in the Region which you want to
  delete.
  
  If the aggregate has been removed at step 2, the relevant
  
  availability
  
  zones will be deleted too.
  
  
  
  Below steps will guide you how to remove the default
  
  availability zone
  
  name: nova
  
  
  
  On the control node and each compute nodes using the region
  
  which you
  
  want to delete, update the statements in the
  /etc/nova/nova.conf
  
  
  Find below statements:
  
  default_availability_zone=nova
  
  default_schedule_zone=nova
  
  
  
  Update to:
  
  default_availability_zone=
  
  default_schedule_zone=
  
  
  
  Run the following commands to restart :
  
  service openstack-nova-api restart
  
  service openstack-nova-compute restart
  
  
  
  Above steps will delete default availability zone name nova,
  but
  actually the nova compute services are still available. If you
  
  really
  
  don't want this compute node in the region, you can stop the
  
  compute
  
  service.
  
  service openstack-nova-compute stop
  
  
  
  4. Update the Keystone entries that relate to the region that
  
  you want
  
  to remove, for example, RegionOne:
  
  source /root/keystonerc
  
  keystone endpoint-list |grep RegionOne | cut -d '|' -f2 | while
  read
  
  endpoint;
  
  do keystone endpoint-delete $endpoint;
  
  done
  
  
  
  5. Stop all openstack services on those node which using the
  
  deleted
  
  Region. You can refer to below link to know openstack services
  
  on each
  
  nodes.
  
  http://www-03preprod.ibm.com/support/knowledgecenter/SST55W_4.1
  .
  0/liaca/
  
  liaca_CMwO_services.html?lang=en
  
  
  
  -------------
  

Local fix

• no workaround
  

Problem summary

• ****************************************************************
  
  * USERS AFFECTED:
  
  All users of  IBM Cloud Orchestrator 2.4 documentation and would
  like to remove a region.
  
  
  ****************************************************************
  
  * PROBLEM DESCRIPTION:
  
  IBM Cloud Orchestrator 2.4 documentation does not point out all
  required steps necessary while removing a region and with it the
  dependent availability zones.
  
  
  ****************************************************************
  
  * RECOMMENDATION:
  
  Review the next update of IBM Cloud Orchestrator 2.4 FP 4
  Information Center when available. The documentation changes can
  also be found in the error description.
  

Problem conclusion

• In chapter "IBM Cloud Orchestrator 2.4.0.3 > Installing >
  Uninstalling > Removing a region will list now all steps
  required to remove the region as well as the related
  availability zones.
  The previous instruction references the entries in keystone
  regarding the region (end points) only.
  Removing this references only may keep the configured
  availability zones for domains and projects entries.
  This make the complete OpenStack services very slow since it
  tries to resolve the orphan availability zones.
  To resolve this issue all projects and domains must be visited
  to check if there is an availability zone configured which does
  not exist anymore.
  
  
  Next update of IBM Cloud Orchestrator 2.4, coming with FP4, will
  make changes available. The documentation changes can also be
  found in the error description.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels