ZZ00139: NEED TO DOCUMENT HOW TO RESET IMAGE CUSTOMIZATION VIA SCO

IBM SmartCloud Orchestrator Fix Pack 1 (2.3.0.1) for 2.3

APAR status

• Closed as documentation error.

Error description

• Currently there is no documented or recommended way for a client
  to update the "Image Target" via SCO. Therefore, we need to
  document and detail the steps to reset image customization
  without using the SCE UI which is not permitted.
  
  
  ENVIRONMENT
  
  IBM SmartCloud Orchestrator 2.2.0.1 (2.2 + FP01
  Operating System: Linux
  Regions: 1
  Hypervisor: VMware
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of SmartCloud Orchestrator 2.2, 2.2
  * FixPack 1 and 2.3 using VMware regions
  ****************************************************************
  * PROBLEM DESCRIPTION: it is not possible to provision or to
  * delete virtual instances neither from SmartCloud Orchestrator
  * UI nor from OpenStack directly
  ****************************************************************
  In /var/log/nova/smartcloud.log you can find messages like:
  
  "2013-11-23 09:08:24 ERROR smartcloud.virt.sce.service [-] There
  was a problem retrieving the host information for workload 39801
  from SCE. The server can't be managed by nova. This is most
  likely an SCE issue."
  
  
  This problem depends on the fact that SmartCloud Entry is
  misaligned with the current VMware vCenter infrastructure.
  

Problem conclusion

• One troubleshooting is going to be added to SmartCloud
  Provisioning 2.3 infocenter.
  
  Here below you can find the procedure to resynchronize
  SmartCloud entry with VMware vCenter:
  
  1. On the Region Server for the failing region run glance
  image-list to get the IDs of all images.
  
  2. Get the public URL of keystone from the
  openstack-iaasgateway:  service running keystone endpoint-list
  
  3. Generate the unscoped token to connect to the
  openstack-iaasgateway service running the following command
  (enter the command on one line) on the Region Server or on any
  other system that can access openstack-iaasgateway service in
  that region :
  
  curl -v -d '{ "auth": { "identity": { "methods":["password"],
  "password": { "user": { "domain": { "name": "Default"},
  "password":"<type admin's password here>", "name":"admin" } } }
  }  }' <public URL for keystone retrieved at step 2>/auth/tokens>
  -H "Content-type: application/json" -H
  "Content:application/json"
  
  4. Then generate the scoped token using the following command
  (on one line):
  
  curl -v -d '{ "auth": { "scope": { "project": { "domain":{
  "name":"Default" }, "name":"admin" } }, "identity": {
  "methods":["password"], "password":{ "user": { " domain": {
  "name": "Default"}, "password":"<admin's password>",
  "name":"admin" } } } } }' <keystone endpoint retrieved at step
  2/auth/tokens> -H "Content-type:application/json" -H " Content:
  application/json" -H "X-Auth-Token":"<token obtained at step 3>"
  
  5.Reset the image customization running this command for each
  image got in the first step:
  
  curl -v -i <URL with interface value "public" got in Step 4
  from the endpoint of type "compute">/images/<image id got from
  step 1>/customization -H "X-Auth-Token":"<X-Subject-Token got
  from step 4>" -X DELETE
  

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