Bug 102891 - Creating UDCTs is not reliable in Multi-JVM environment
Summary: Creating UDCTs is not reliable in Multi-JVM environment
Alias: None
Product: Red Hat Enterprise CMS
Classification: Retired
Component: other (Show other bugs)
(Show other bugs)
Version: nightly
Hardware: All Linux
Target Milestone: ---
Assignee: ccm-bugs-list
QA Contact: Jon Orris
Depends On:
Blocks: 108447 111508 102913
TreeView+ depends on / blocked
Reported: 2003-08-22 13:11 UTC by Daniel Berrange
Modified: 2007-04-18 16:57 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-09-02 17:22:13 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Daniel Berrange 2003-08-22 13:11:58 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.9 (X11; Linux i686; U;) Gecko/20030314

Description of problem:
Part of creating a UDCT involves creating a dynamic object type (whose PDL is
stored  in the DB). When creating this new object tyep, it is automatically
added to the Metadata root after creation. Unfortunately, in a Multi-JVM
environment the other JVMs in the cluster don't get the new type added to their
Metadata root. Thus, after creating a UDCT, the other servers in the cluster
will throw errors when using the new UDCT.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create a new UDCT on Server A
2. Create an instance of UDCT on server A
3. Publish the instance
4. Try & view the instance on server B.


Actual Results:  An error is thrown

Expected Results:  The item is displayed.

Additional info:

Comment 1 Vadim Nasardinov 2003-10-31 15:50:58 UTC
When/if this is resolved, we should also revisit bug 101658.

Comment 2 Daniel Berrange 2006-09-02 17:22:13 UTC
Closing old tickets.

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