Bug 117260 - Camden migration scripts did not migrate image ids correctly
Camden migration scripts did not migrate image ids correctly
Product: Red Hat Enterprise CMS
Classification: Retired
Component: APLAWS (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: ccm-bugs-list
Daniel Berrange
Depends On:
  Show dependency treegraph
Reported: 2004-03-02 06:37 EST by Arturo Dell
Modified: 2007-04-18 13:03 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-03-02 07:05:55 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Arturo Dell 2004-03-02 06:37:35 EST
Description of problem: Camden migration scripts did not migrate 
image ids correctly. The same image in the 5.2 box has a different id 
in the migrated APLAWS+ box:



How reproducible: Always
Comment 1 Daniel Berrange 2004-03-02 06:39:59 EST
IDs for images & all objects within WAF are installation specific & as
such it is not possible to maintain the same IDs across differnet
installs. What situation have you got that would require IDs to be the
same across both installs ? All styling should be using the ID
specified in the XML, not hardcoding it, so I can only think its
relevant if there were hardcoding <img> tags in the body text for some
Comment 2 Arturo Dell 2004-03-02 06:41:34 EST
That's exactly the case. There is no solution for this?
Comment 3 Daniel Berrange 2004-03-02 06:46:36 EST
There isn't any solution - we don't support/recommend entering of
<img> tags directly into HTML for this exact reason. You'll have to
edit the HTML to fix the image ids.
Comment 4 Arturo Dell 2004-03-02 06:53:34 EST
I understand that. Just to get to the bottom of this ticket, 
the "migrated" image repository in our production instance is a lot 
smaller than the 5.2 one. Is that because the items that were loaded 
into the image repository were then accessed from the html in the 
body text instead of using the add image authoring step? 
I understand that we may need to change the ids of the images if we 
want to access them from the html in the body text but it seems that 
we also have to re-upload more than half of the images as well.
Comment 5 Daniel Berrange 2004-03-02 07:05:55 EST
If the images weren't referenced in the 'image' authoring step then
there is no way for the systme to tell that they were in use, so they
won't have been migrated. The issue wrt missing images has previously
been entered as bug 117196. 

Note You need to log in before you can comment on or make changes to this bug.