using a vmware setup 1. create a template using vmware vphsere 2. get the id using dcloud 3. aeolus-image import --provider vmware --target vmware --id $idOfTemplate 4. notice the factory / warehouse logs do not indicate a successful import. 2011-07-12 12:36:23,982 DEBUG imagefactory.qmfagent.ImageFactoryAgent.ImageFactoryAgent pid(13118) Message: Method called: name = import_image args = {'target': 'vmware', 'image': '', 'image_desc': '<image><name>mfojtik-template</name></image>', 'build': '', 'provider': 'vmware', 'target_identifier': 'mfojtik-template'} handle = <cqmf2.AgentEvent; proxy of <Swig Object of type 'qmf::AgentEvent *' at 0x3084060> > addr = redhat.com:imagefactory:acc74a73-1071-4e63-9a48-de5904d2544b:image_factory subtypes = {} userId = anonymous 2011-07-12 12:36:23,984 INFO imagefactory.ImageWarehouse.ImageWarehouse pid(13118) Message: Creating a bucket returned status 500. If only iwhd would provide a sane way to know if a bucket exists so we wouldn't have to try and create one every time... 2011-07-12 12:36:23,995 DEBUG imagefactory.ImageWarehouse.ImageWarehouse pid(13118) Message: Setting metadata ({'object_type': 'image', 'uuid': '322086df-7c79-4ab9-8df2-d43661663af8'}) for http://localhost:9090/images/322086df-7c79-4ab9-8df2-d43661663af8 2011-07-12 12:36:24,076 INFO imagefactory.ImageWarehouse.ImageWarehouse pid(13118) Message: Creating a bucket returned status 500. If only iwhd would provide a sane way to know if a bucket exists so we wouldn't have to try and create one every time... 2011-07-12 12:36:24,083 DEBUG imagefactory.ImageWarehouse.ImageWarehouse pid(13118) Message: Setting metadata ({'image': '322086df-7c79-4ab9-8df2-d43661663af8', 'object_type': 'build', 'uuid': '8107d516-b8a5-40b3-a192-e9ee489dc17b'}) for http://localhost:9090/builds/8107d516-b8a5-40b3-a192-e9ee489dc17b 2011-07-12 12:36:24,204 DEBUG imagefactory.ImageWarehouse.ImageWarehouse pid(13118) Message: Querying (http://localhost:9090/target_images/_query) with expression ($build == "8107d516-b8a5-40b3-a192-e9ee489dc17b" && $target == "vmware") 2011-07-12 12:36:24,245 INFO imagefactory.ImageWarehouse.ImageWarehouse pid(13118) Message: Creating a bucket returned status 500. If only iwhd would provide a sane way to know if a bucket exists so we wouldn't have to try and create one every time... 2011-07-12 12:36:24,247 DEBUG imagefactory.ImageWarehouse.ImageWarehouse pid(13118) Message: Setting metadata ({'build': '8107d516-b8a5-40b3-a192-e9ee489dc17b', 'object_type': 'target_image', 'uuid': 'abeed993-672b-4d67-b1c5-042e22e02d39', 'target': 'vmware'}) for http://localhost:9090/target_images/abeed993-672b-4d67-b1c5-042e22e02d39 2011-07-12 12:36:24,408 DEBUG imagefactory.ImageWarehouse.ImageWarehouse pid(13118) Message: Querying (http://localhost:9090/provider_images/_query) with expression ($target_image == "abeed993-672b-4d67-b1c5-042e22e02d39" && $provider == "vmware") 2011-07-12 12:36:24,449 INFO imagefactory.ImageWarehouse.ImageWarehouse pid(13118) Message: Creating a bucket returned status 500. If only iwhd would provide a sane way to know if a bucket exists so we wouldn't have to try and create one every time... 2011-07-12 12:36:24,451 DEBUG imagefactory.ImageWarehouse.ImageWarehouse pid(13118) Message: Setting metadata ({'target_image': 'abeed993-672b-4d67-b1c5-042e22e02d39', 'target_identifier': 'mfojtik-template', 'object_type': 'provider_image', 'uuid': '52c3d406-1633-44dc-9d80-77710a4a2f40', 'provider': 'vmware'}) for http://localhost:9090/provider_images/52c3d406-1633-44dc-9d80-77710a4a2f40 2011-07-12 12:36:24,653 DEBUG imagefactory.ImageWarehouse.ImageWarehouse pid(13118) Message: Getting metadata (['latest_build']) from http://localhost:9090/images/322086df-7c79-4ab9-8df2-d43661663af8 2011-07-12 12:36:24,654 DEBUG imagefactory.ImageWarehouse.ImageWarehouse pid(13118) Message: Setting metadata ({'latest_build': '8107d516-b8a5-40b3-a192-e9ee489dc17b'}) for http://localhost:9090/images/322086df-7c79-4ab9-8df2-d43661663af8 31248 parse_url: 2: target_images abeed993-672b-4d67-b1c5-042e22e02d39 31248 PROXY POST obj (/target_images/abeed993-672b-4d67-b1c5-042e22e02d39, 0) 31248 PROXY POST obj (/target_images/abeed993-672b-4d67-b1c5-042e22e02d39, 8) adding op, size=5 31248 PROXY POST obj (/target_images/abeed993-672b-4d67-b1c5-042e22e02d39, 0) 31248 simple_closer: cleaning up 31248 parse_url: 3: target_images abeed993-672b-4d67-b1c5-042e22e02d39 build31248 PROXY GET ATTR /target_images/abeed993-672b-4d67-b1c5-042e22e02d39/build 31248 parse_url: 3: target_images abeed993-672b-4d67-b1c5-042e22e02d39 object_type31248 PROXY GET ATTR /target_images/abeed993-672b-4d67-b1c5-042e22e02d39/object_type 31248 parse_url: 3: target_images abeed993-672b-4d67-b1c5-042e22e02d39 target31248 PROXY GET ATTR /target_images/abeed993-672b-4d67-b1c5-042e22e02d39/target 31248 parse_url: 3: target_images abeed993-672b-4d67-b1c5-042e22e02d39 uuid31248 PROXY GET ATTR /target_images/abeed993-672b-4d67-b1c5-042e22e02d39/uuid Please add some logging.. I suppose to the factory logs indicating a successful import
(In reply to comment #0) > 2011-07-12 12:36:24,451 DEBUG imagefactory.ImageWarehouse.ImageWarehouse > pid(13118) Message: Setting metadata ({'target_image': > 'abeed993-672b-4d67-b1c5-042e22e02d39', 'target_identifier': > 'mfojtik-template', 'object_type': 'provider_image', 'uuid': > '52c3d406-1633-44dc-9d80-77710a4a2f40', 'provider': 'vmware'}) for > http://localhost:9090/provider_images/52c3d406-1633-44dc-9d80-77710a4a2f40 Wes, this tells me it successfully completed - it created a provider image with ID 52c3d406-1633-44dc-9d80-77710a4a2f40 pointing to the mfojtik-template image on the vmware provider > 2011-07-12 12:36:23,995 DEBUG imagefactory.ImageWarehouse.ImageWarehouse > pid(13118) Message: Setting metadata ({'object_type': 'image', 'uuid': > '322086df-7c79-4ab9-8df2-d43661663af8'}) for > http://localhost:9090/images/322086df-7c79-4ab9-8df2-d43661663af8 And this tells me that the image ID for the imported image is 322086df-7c79-4ab9-8df2-d43661663af8
Mark, Those messages are not clear enough for a customer, and unfortunately the aeolus-image tool also does not indicate completion. The status of a job is more clear for building and pushing, import should follow suit. Something like imagefactory.ImportJob.BuildAdaptor..... status COMPLETED. 2011-07-13 16:23:25,110 DEBUG imagefactory.BuildJob.BuildAdaptor pid(18031) Message: Raising event with agent handler (<ImageFactoryAgent(Thread-1, initial)>), changed status from BUILDING to COMPLETED 2011-07-13 16:25:09,471 DEBUG imagefactory.qmfagent.ImageFactoryAgent.ImageFactoryAgent pid(18031) Message: Method called: name = push_image This is a priority because the customer right now has no other way to determine the import status w/o querying the warehouse API directly and starting a deployable. Should be a simple fix. Thanks
(In reply to comment #2) > Mark, > Those messages are not clear enough for a customer, Logs are for diagnosing problems > and unfortunately the aeolus-image tool also does not indicate completion. Well, that's the real bug, then ... moving
That issue is already fixed in https://bugzilla.redhat.com/show_bug.cgi?id=720761
Closing..
perm close