CA Service Management

 View Only
  • 1.  CORA inconsistency

    Posted Mar 26, 2020 04:05 AM
    Edited by Michael Mueller Mar 26, 2020 04:24 AM
    Hello.
    Before going to Broadcom support, I'd like to get some thoughts on this topic from the community.
    The initiator of this topic is CI creation through SOAP, where the creation ends up in an update instead.
    After doing some research, I was able to reproduce this unexpected behvior in the GUI as well.
    Here is the problem:
    • I want to create a CI.
    • The only values I am specifying are the name and the class, lets say "test1" and "Workstation".
    • Of course "test1" does not exist in nr factory.
      • The system respond with an update on CI "test2".
      • And this is where I think, here is something wrong.

    The problem is obviously related to renaming CI's. Here is the procedure to reproduce.
    • create a new CI with
      • name=test1,
      • Class=Workstation,
      • Hostname=test1,
      • serial_number=4711
      • continue and save
    • rename the CI, change
      • name=test2,
      • Hostname=test2
      • and save
        • no test1 CI exist anymore
    • now create a new CI with
      • name=test1,
      • Class=Workstation
      • continue
        • you get the update of test2

    Isn't that strange?
    I am considering this as a bug.
    Let me know your thoughts

    Thanks and regards
    ............Michael

    ------------------------------
    Principal Services Consultant
    HCL Enterprise Studio
    Germany
    ------------------------------


  • 2.  RE: CORA inconsistency

    Broadcom Employee
    Posted Mar 26, 2020 04:30 AM
    If you run a search at the database level, do you still see any reference to the old hostname?

    select asset_source_uuid, ca_logical_asset.logical_asset_uuid, ca_asset.asset_uuid, host_name, serial_number, label, asset_tag, dns_name, mac_address
    from ca_asset_source, ca_logical_asset, ca_asset, ca_logical_asset_property
    where host_name like '<HOST NAME>'
    and ca_asset.asset_uuid = ca_logical_asset.asset_uuid
    and ca_logical_asset.logical_asset_uuid = ca_asset_source.logical_asset_uuid
    and ca_logical_asset.logical_asset_uuid = ca_logical_asset_property.logical_asset_uuid

    My suspicion is that it still knows the old name somewhere.

    regards
    Iain


  • 3.  RE: CORA inconsistency

    Posted Mar 26, 2020 04:43 AM
    Hi Iain
    Yes, you are right !
    I checked this before , but I didn't want to go too much into details, as CORA is some kind of a blackbox.
    In fact, ca_asset.label still holds the old nr name after renaming. And I assume this leads to my observation.
    Thanks !! for the input.
    Regards
    ....Michael




  • 4.  RE: CORA inconsistency

    Broadcom Employee
    Posted Mar 26, 2020 04:49 AM
    Thanks Michael. 

    I can see a number of good reasons why we might be tracking the original name in the database, but it does lead to this problem, yes.

    regards
    Iain


  • 5.  RE: CORA inconsistency

    Posted Mar 26, 2020 06:07 AM
    Edited by Michael Mueller Mar 26, 2020 06:08 AM
    My very personal opinion: History tracking might be usefull. But not that way;)

    Question is , if this specific behavior is by intention , or if it is just an error.

    Regards
    .....Michael


  • 6.  RE: CORA inconsistency

    Broadcom Employee
    Posted Mar 26, 2020 06:25 AM
    That, I suspect, is going to come down to a judgement call for the product team - since it reproduces easily enough you could raise a case to get confirmation.

    My guess is that it's intent in the code, but as you say there are circumstances where this is unhelpful.

    regards
    Iain


  • 7.  RE: CORA inconsistency

    Broadcom Employee
    Posted Mar 26, 2020 06:34 AM

    Hi Michael,

    If I haven't misunderstood, you are using using SOAP web services with createObject().

    I tried to reproduce in 17.1.0.7 German using SoapUI tool with createObject(). I did not get the same behavior, maybe I'm missing something. 

    It looks like the old entry in the ca_asset table (for the renamed CI) has a delete_time associated with it, whereas the other entries have NULL as the value.

    Regards,

    Karen



    ------------------------------
    Broadcom
    ------------------------------



  • 8.  RE: CORA inconsistency
    Best Answer

    Posted Mar 26, 2020 06:44 AM
    Hi Karen.
    Thank you.
    Perfect to get this attention. Thanks to all !!!

    However: I just created a support case 31830401

    So.
    Dear Broadcom colleagues. Please don't invest anymore time into this, here.
    Thanks again. As for simplicity, I was looking for a way to reproduce it in the GUI. I'll ceck the SOAP thing again, anyway.
    I'll let you know...
    And I can imagine, that it might be different on windows. I'm working on linux.....
    Thanks and best regards
    .......Michael





    ------------------------------
    Principal Services Consultant
    HCL Enterprise Studio
    Germany
    ------------------------------



  • 9.  RE: CORA inconsistency

    Posted Mar 26, 2020 07:19 AM
    FYI.
    Using SOAP, it gets even more confusing/worse:
    Using "createObject" I get a SOAP fault:

    Using "createAsset" runs through, and updates the existing CI 

    Regards
    ..............Michael


    ------------------------------
    Principal Services Consultant
    HCL Enterprise Studio
    Germany
    ------------------------------