ZZ00342: CREATION OF NEW KVM COMPUTE NODE CAN BREAK ORIGINAL (WORKING) KVM COMPUTE NODE.

IBM Cloud Orchestrator Fix Pack 3 (2.4.0.3) for 2.4

APAR status

• Closed as fixed if next.

Error description

• When using a non-demo network, the networking may fail for new
  instances that are deployed after the new KVM compute node was
  deployed.  Instances that are deployed into the new KVM compute
  node will work, whereas instances deployed into the original
  KVM compute node will now fail.
  
  For example after the creation of a new KVM compute node, the
  'demo' network will get recreated:
  
  # nova network-list
  +--------------------------------------
  | ID | Label | Cidr |
  +--------------------------------------
  | 0256ea20-acb7-4bb5-be78-f33cfbcf9125 | P3YZCS80 |1.1.1.0/22 |
  | 03ebda17-7ce0-44b7-b590-e36bb23da073 | demo | 10.10.0.0/24 |
  +--------------------------------------
  
  You may also notice changes in the cidr dhcp_start range and
  the nova.conf as well.
  

Local fix

• 1)For nova.conf, please ensure backup the file
  /etc/nova/nova.conf on kvm region server and compute node
  before adding the new compute node.
  
  2)For the network issue, the workaround is to modify the info in
   openstack DB to correct value.
  

Problem summary

• APAR can be closed as fix is provided and associated RTC 174576
  is also closed.
  

Problem conclusion

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

• R240 PSY

     UP