{"action":"created","issue":{"url":"https://api.github.com/repos/ansible/ansible/issues/41774","repository_url":"https://api.github.com/repos/ansible/ansible","labels_url":"https://api.github.com/repos/ansible/ansible/issues/41774/labels{/name}","comments_url":"https://api.github.com/repos/ansible/ansible/issues/41774/comments","events_url":"https://api.github.com/repos/ansible/ansible/issues/41774/events","html_url":"https://github.com/ansible/ansible/issues/41774","id":334354701,"node_id":"MDU6SXNzdWUzMzQzNTQ3MDE=","number":41774,"title":"vmware_portgroup add possibility to override the failover order","user":{"login":"kTitan","id":516661,"node_id":"MDQ6VXNlcjUxNjY2MQ==","avatar_url":"https://avatars0.githubusercontent.com/u/516661?v=4","gravatar_id":"","url":"https://api.github.com/users/kTitan","html_url":"https://github.com/kTitan","followers_url":"https://api.github.com/users/kTitan/followers","following_url":"https://api.github.com/users/kTitan/following{/other_user}","gists_url":"https://api.github.com/users/kTitan/gists{/gist_id}","starred_url":"https://api.github.com/users/kTitan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kTitan/subscriptions","organizations_url":"https://api.github.com/users/kTitan/orgs","repos_url":"https://api.github.com/users/kTitan/repos","events_url":"https://api.github.com/users/kTitan/events{/privacy}","received_events_url":"https://api.github.com/users/kTitan/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-06-21T06:25:42Z","updated_at":"2018-06-21T06:34:12Z","closed_at":null,"author_association":"NONE","body":"##### SUMMARY\r\nCurrently it is not possible to override the NIC Teaming failover order of a port group.\r\nAt the current state an ansible run will also reset the configuration if it was done manually.\r\n\r\nAs far as I know the failover order can be specified with the usage of nicTeaming.nicOrder.activeNic and nicTeaming.nicOrder.standbyNic.\r\n\r\nFor an example this configuration is needed inside the portgroup if you are using iscsi.\r\n\r\n##### ISSUE TYPE\r\n - Feature Idea\r\n\r\n##### COMPONENT NAME\r\nvmware_portgroup\r\n\r\n##### ANSIBLE VERSION\r\n```\r\nansible 2.7.0.dev0\r\n  config file = /Users/unknown/.ansible.cfg\r\n  configured module search path = [u'/Users/unknown/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']\r\n  ansible python module location = /Users/unknown/.pyenv/versions/2.7.14/envs/py2-ansible/lib/python2.7/site-packages/ansible\r\n  executable location = /Users/unknown/.pyenv/versions/py2-ansible/bin/ansible\r\n  python version = 2.7.14 (default, Oct 10 2017, 17:48:56) [GCC 4.2.1 Compatible Apple LLVM 8.1.0 (clang-802.0.42)]\r\n```\r\n\r\n##### CONFIGURATION\r\nDEFAULT_HOST_LIST(/Users/unknown/.ansible.cfg) = [u'/Users/unknown/ansible/hosts']\r\nDEFAULT_LOAD_CALLBACK_PLUGINS(/Users/unknown/.ansible.cfg) = True\r\nDEFAULT_ROLES_PATH(/Users/unknown/.ansible.cfg) = [u'/Users/unknown/ansible/roles']\r\nDEFAULT_STDOUT_CALLBACK(/Users/unknown/.ansible.cfg) = yaml\r\nPERSISTENT_COMMAND_TIMEOUT(/Users/unknown/.ansible.cfg) = 30\r\n\r\n##### OS / ENVIRONMENT\r\nN/A\r\n\r\n##### STEPS TO REPRODUCE\r\n```yaml\r\n- name: Add Portgroup with teaming policy\r\n  vmware_portgroup:\r\n    hostname: esxi_hostname\r\n    username: esxi_username\r\n    password: esxi_password\r\n    switch_name: vswitch_name\r\n    portgroup_name: portgroup_name\r\n    teaming_policy:\r\n      load_balance_policy: 'failover_explicit'\r\n      inbound_policy: True\r\n      activeNic: ['vmnic0']\r\n      standbyNic: []\r\n  register: teaming_result\r\n```\r\n\r\n##### EXPECTED RESULTS\r\nWith the new setting \"activeNic\" only the vmnic0 inside the failover order should be set to active.\r\nWith the empty value of \"standbyNic\" all other Interfaces should be set to \"unused\"\r\n \r\n##### ACTUAL RESULTS\r\nAt the moment it is not possible to specify this setting, and ansible will override the settings if they were changed inside the VMware client.\r\n"},"comment":{"url":"https://api.github.com/repos/ansible/ansible/issues/comments/398991847","html_url":"https://github.com/ansible/ansible/issues/41774#issuecomment-398991847","issue_url":"https://api.github.com/repos/ansible/ansible/issues/41774","id":398991847,"node_id":"MDEyOklzc3VlQ29tbWVudDM5ODk5MTg0Nw==","user":{"login":"ansibot","id":6585283,"node_id":"MDQ6VXNlcjY1ODUyODM=","avatar_url":"https://avatars0.githubusercontent.com/u/6585283?v=4","gravatar_id":"","url":"https://api.github.com/users/ansibot","html_url":"https://github.com/ansibot","followers_url":"https://api.github.com/users/ansibot/followers","following_url":"https://api.github.com/users/ansibot/following{/other_user}","gists_url":"https://api.github.com/users/ansibot/gists{/gist_id}","starred_url":"https://api.github.com/users/ansibot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ansibot/subscriptions","organizations_url":"https://api.github.com/users/ansibot/orgs","repos_url":"https://api.github.com/users/ansibot/repos","events_url":"https://api.github.com/users/ansibot/events{/privacy}","received_events_url":"https://api.github.com/users/ansibot/received_events","type":"User","site_admin":false},"created_at":"2018-06-21T06:34:12Z","updated_at":"2018-06-21T06:34:12Z","author_association":"CONTRIBUTOR","body":"Files identified in the description:\n* [lib/ansible/modules/cloud/vmware/vmware_portgroup.py](https://github.com/ansible/ansible/blob/devel/lib/ansible/modules/cloud/vmware/vmware_portgroup.py)\n\nIf these files are inaccurate, please update the `component name` section of the description or use the `!component` bot command.\n\n[click here for bot help](https://github.com/ansible/ansibullbot/blob/master/ISSUE_HELP.md)\n<!--- boilerplate: components_banner --->"}}
{"actor":{"display_login":"ansibot"}}