Automic Workload Automation

Expand all | Collapse all

V12 - Agent Assignment Policy appears to not work

John O

John O'MullaneMar 14, 2017 11:57 AM

  • 1.  V12 - Agent Assignment Policy appears to not work

    Posted Mar 07, 2017 11:55 AM
    Hi all,
    We are currently in the process of upgrading from V10 to V12.
    We have upgraded our dev/test environment and I've just noticed that any new Unix agent installed since the upgrade are not getting authorized to read/write/execute on any of the client like they should be.

    I have an AGENT_ASSIGNMENT object(below), which we successfully used in V10 for new agents but it looks like it's not getting activated on V12 like I would expect.

    I have a ticket open on this, but just wanted to put it out there in case anyone has seen this behavior on V12.

    gc6dytngkzmf.pnghttps://us.v-cdn.net/5019921/uploads/editor/0b/gc6dytngkzmf.png" width="1600">

    3r8p2xnxm2ca.pnghttps://us.v-cdn.net/5019921/uploads/editor/s6/3r8p2xnxm2ca.png" width="1025">

    John.



  • 2.  V12 - Agent Assignment Policy appears to not work

    Posted Mar 07, 2017 04:00 PM
    Just why I am curious about this - did you try & did it work in JAVA client in V12?


  • 3.  V12 - Agent Assignment Policy appears to not work

    Posted Mar 07, 2017 04:48 PM
    I haven't installed the agent via AWI, this is done using a unix script in the background.
    Where I view which clients are authorized for this agent shouldn't really matter.

    I did check via the JAVA GUI on V12 and I see the same results.




  • 4.  V12 - Agent Assignment Policy appears to not work

    Posted Mar 08, 2017 05:16 AM
    Courious - cause I use a HSTA object for my (WIN) agents on my TEST system and its working fine.
    just tested with a new win agent.

    To be honest - I am not using AWI at the moment...


  • 5.  V12 - Agent Assignment Policy appears to not work

    Posted Mar 08, 2017 05:36 AM
    Maybe it's got something to do with the fact that the HSTA object was created in V10 and migrated to V12.
    I'll try to delete and re-create and see if that works.

    I haven't heard back from Support since I opened the ticket so I think I'll have to work my way through this one myself.

    I also thought about staying on the Java UI. It's difficult to change when you get so used to it.
    But, I think we will all be forced to use it eventually so better starting early :-)



  • 6.  V12 - Agent Assignment Policy appears to not work

    Posted Mar 08, 2017 05:57 AM
    The easies workaround I could imagine would be - as you stated - re-creating the HSTA object and activating it via JAVA GUI.

    I three times tried to convince myself using AWI but after trying to newly create a Workflow containing 5 jobs, a promptset and a VARA object I went back to JAVA UI.....


  • 7.  V12 - Agent Assignment Policy appears to not work

    Posted Mar 08, 2017 06:43 AM
    Yes, this worked, re-creating the HSTA object worked. I can just do this also when I upgrade my UAT and PROD.

    Pity there is no repository of issues users faced when upgrading. I have a few I could add.



  • 8.  V12 - Agent Assignment Policy appears to not work

    Posted Mar 08, 2017 07:38 AM
    If there isn't one - you should start one JohnO'Mullane !  Sounds like a great idea!  I know appreciate a heads-up on potential gotcha's.  



  • 9.  V12 - Agent Assignment Policy appears to not work

    Posted Mar 14, 2017 05:26 AM
    FrankMuffke

    I was a little premature with my previous comments. Recreating the HSTA did not in fact work.

    I have been working with Antoine from Support on this and we have tracked the issue down to the following.

    It appears when we install a new agent, it is not getting a Licence Category 

    efd9369zco02.pnghttps://us.v-cdn.net/5019921/uploads/editor/cf/efd9369zco02.png" width="1600">

    As a result, my HSTA is not detecting it because my HSTA is looking for a certain licence category.

    0dctdromly8p.pnghttps://us.v-cdn.net/5019921/uploads/editor/pt/0dctdromly8p.png" width="1600">

    We are now trying to figure out why new agents are not getting Licence Category assigned.




  • 10.  V12 - Agent Assignment Policy appears to not work

    Posted Mar 14, 2017 06:26 AM
    Hmmm this could be a Bug.

    Basically when a new agent is started it takes "any" available License Category - as far as I remember there was a Post in community explaining that.


  • 11.  V12 - Agent Assignment Policy appears to not work

    Posted Mar 14, 2017 06:28 AM


  • 12.  V12 - Agent Assignment Policy appears to not work

    Posted Mar 14, 2017 06:44 AM
    FrankMuffke
    If I leave the Licence Category blank on my HSTA, it then does create the new agent with all the client assignments correct.
    However, the new agent does then not have a Licence Category.

    Do you know what the implication of that are?

    dlmgwm2lbxxt.pnghttps://us.v-cdn.net/5019921/uploads/editor/au/dlmgwm2lbxxt.png" width="1600">




  • 13.  V12 - Agent Assignment Policy appears to not work

    Posted Mar 14, 2017 07:12 AM
    Jahaa thats it :-)

    Thanks for the hint - I had a quick look at my V12 System - just the same the agent starts without category.
    s3eyej28sr0t.jpghttps://us.v-cdn.net/5019921/uploads/editor/nx/s3eyej28sr0t.jpg" width="292">

    With V12 Automic removed some of the checks for a faster Agent "registration" on AE - that seems to be one of the results.

    so the category now seems to be optional for an agent.

    => the easiest way would be bypassing the category in the HSTA objects
    and -if needed - setting it accordingly after the HSTA process took place.


  • 14.  V12 - Agent Assignment Policy appears to not work

    Posted Mar 14, 2017 07:19 AM
    That's the question I guess "If needed" . Are there any implications of having a null Licence Category.



  • 15.  V12 - Agent Assignment Policy appears to not work

    Posted Mar 14, 2017 07:45 AM
    The Licence Category is intended to seperate groups of agents e.g. Production and nonproduction or for an outsourcer for different customers...

    As far as I know there is no limitation and no impact on technical side.


  • 16.  V12 - Agent Assignment Policy appears to not work

    Posted Mar 14, 2017 11:57 AM
    ok, thanks. Let's see what Support come back with.


  • 17.  V12 - Agent Assignment Policy appears to not work

    Posted Jul 25, 2017 05:10 PM
    Hey JohnO'Mullane  - just wondering what the latest is on this issue.  At the time when I initially read this I wasn't using HSTA objects, but now I am and seeing similar weirdness with the rights not being assigned automatically.  I used this object previously and it worked as expected in V10 and earlier, but now in V11 (and I guess for you V12) it isn't working the same.  Did Support indicate to you that they changed the behavior of this object intentionally and/or did they determine it was a bug?



  • 18.  V12 - Agent Assignment Policy appears to not work

    Posted Jul 26, 2017 04:22 AM
    Hi LauraAlbrecht608310
    The latest I got on this was as follows.
    This was a bug that was fix in 11.2 but resurfaced again in 12.0.
    It is fixed again in 12.0.2

    Not sure how this can happen but I have seen several occasions where bugs fixed in previous version resurface in newer versions.

    I have removed the Licence Category from my HSTA and so new agents are not getting set with this value.

    I did speak to my Automic Account manager to make sure this would not impact in any way calculation of licence usage or anything like this in future.
    They gave me the all clear to not set this value. 
    It appears to not be very important because my Engine / Agents are working fine without it.





  • 19.  V12 - Agent Assignment Policy appears to not work

    Posted Jan 23, 2018 04:26 PM
    Just to chime in, ran into the same problem in 12.1. After clearing the license category, it worked.