Unable to provision new port selector for leaf interface profile about ansible-aci

[xinyuezhao]

@manofcolombia @aj-cruz

The module 'aci_access_port_to_interface_policy_leaf_profile' will not be deprecated. Only those attributes related to port blocks will be deprecated and we recommend using module 'aci_access_port_block_to_access_port' to manage port blocks.

[aj-cruz]

@manofcolombia Have you tried using aci_access_port_to_interface_policy_leaf_profile?
You can do everything with that one resource, create the port selector, associate port blocks and policy groups, and associate it to the leaf profile.

[manofcolombia]

@manofcolombia Have you tried using aci_access_port_to_interface_policy_leaf_profile?
You can do everything with that one resource, create the port selector, associate port blocks and policy groups, and associate it to the leaf profile.

That module does work for the most part. Originally, I completely skipped over that module because it seemed like it is being deprecated?
This is in the module doc.
Starting with Ansible 2.8 we recommend using M(aci_access_port_block_to_access_port) instead

Also, when associating a policy group at the same time, I get a failed relationship form fault in the port selector. The gui shows the policy group set to the full tDN instead of just the named object. Setting it manually to the named object resolves the fault.

ACI: 4.2.4I

[aj-cruz]

@manofcolombia Hmm, I don't see that recommendation anywhere here: https://docs.ansible.com/ansible/latest/modules/aci_access_port_to_interface_policy_leaf_profile_module.html#aci-access-port-to-interface-policy-leaf-profile-module

However, I never noticed it before but I also have a failed relationship with one of my policy groups.
My external vPC policy group failed the relationship, but all the others are fine.
Possibly because access_port_selector is only for access policy groups which I guess makes sense given the name.

[manofcolombia]

@aj-cruz I found that documented in the documentation of the actual module. https://github.com/CiscoDevNet/ansible-aci/blob/master/plugins/modules/aci_access_port_to_interface_policy_leaf_profile.py

The first one I saw was on line 40 but it repeats most of the way thru the documentation section.

Ultimately, I did get it to work with that module...I forgot interface_type: vpc so it was defaulting to looking for the port group under accportgrp instead of accbundle.

I'm still curious why/when/if the module will be deprecated.

[lhercot]

@aj-cruz and @manofcolombia, any suggestion on what we can improve to avoid the issue you had?

[manofcolombia]

@aj-cruz and @manofcolombia, any suggestion on what we can improve to avoid the issue you had?

The original issue I created stemmed from thinking that aci_access_port_block_to_access_port module would create the child objects if they don't exist. This assumption was incorrect, but I could see a case for both creating and not creating child objects.

I think what would be most helpful, in the long run, is taking the documentation that is written in the module and expanding upon it in the wiki of the github repo. This is mainly for readability, note things pertaining to the module, and the life cycle of the module.

However, I did see that updated documentation in the module does seem to update the docs on the docs.ansible.com. This might be sufficient, but these notes do not appear there.

This is based on the perspective of trying to get another ACI admin who is not as familiar with python or ansible, but sees the value of interacting with ACI via ansible. Their expectation is a readable doc and no "gotcha" notes that they'd have to go looking into the module itself (or asking me) to find out that xyz needs to be created prior to using xyz module.