red x's where - in the live browse of the component itself? can you attach a screenshot ?
The x's are because those specific parts of your component do not exist on the server.
the component template is looking for an entry in a configuration file. that configuration file must be defined either in the Configuration Object dictionary or locally on your component template.
additionally, the actual entries must exist in the configuration file (anything after the //)
if you look in the 'Configuration' object in the live browse of your server, do you see the referenced configuration file? if so, can you open it and then do you see the entries the component is attempting to reference?
the component template can be valid for a system, but parts can still be missing once the component is created. (like in this case, the discovery condition might be that the OS is linux, and the template may include a number of 'parts'. some parts might not exist on the server, but because of the discovery condition the template is still considered to be valid for the server, so a component is still created)
odd. you added the 'parts' to the template as configuration entries ? if you look in the parts section of the component template they should be of the type "configuration entry" (or "configuration file" if you added just the /etc/login.defs config file).
Yes, they were added as Configuration entries. I was redoing
a problem from the Bladelogic Essentials Exercise Guide 7.3-2 .
Specifically pages 138-139.
That's what i figured - the training exercise.
is there anything in the appserver.log about this possibly?
try tailing the appserver log and then browsing the component.
Here's a tail when browsing the component from within the
wb238w:BLAdmins:126.96.36.199 Retrieving property values for host: ashvamst01
wb238w:BLAdmins:188.8.131.52 Finished retrieving property values for host: ashvamst01
Again, the components are still listed with a red x.
I don't see any data added to the log when I browse the component
from the Component Templates area. There the components are listed corrrectly.
this is odd. i'd suggest opening a ticket w/ support to track this down.. but reference this thread in the ticket.
I'm seeing this exact issue and I don't get it either. I just patched to 184.108.40.2061 and upgraded my agents, but still see the same, even on new Components I create.
It's weird because when I browse the same components through Component Templates or Components, all the objects in the components show up fine. It's only through thethat I see red x's on all the items in the component.
-> Live -> Components ->
Is there a ticket already open for this?
I did some research on this. Ticket #24242 is related to this issue. Apparently it's been reproduced and is listed as a defect and is scheduled for a future release.
I did some testing myself, and it seems to be related only to configuration entries. When I add RPM's or directories to the Template, those objects do not have red x's on them in the live server view.
I had the same issue on ticket #21631.
It was raised as a defect in that case as well.
No news since then.