Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vmware_vmkernel: no error on state=absent #55175

Open
wants to merge 1 commit into
base: devel
from

Conversation

Projects
None yet
2 participants
@goneri
Copy link
Contributor

goneri commented Apr 11, 2019

SUMMARY

The network.type parameter is set to default on default on static.
As a consequence, the network parameter is always defined as dict.

This patch ensures we don't check the value of the network configuration
if we want to delete the interface.

ISSUE TYPE
  • Bugfix Pull Request
COMPONENT NAME

vmware_vmkernel

@ansibot

This comment has been minimized.

@ansibot

This comment has been minimized.

Copy link
Contributor

ansibot commented Apr 11, 2019

@goneri, just so you are aware we have a dedicated Working Group for vmware.
You can find other people interested in this in #ansible-vmware on Freenode IRC
For more information about communities, meetings and agendas see https://github.com/ansible/community

click here for bot help

vmware_vmkernel: no error on state=absent
The `network.type` parameter is set to default on default on `static`.
As a consequence, the network parameter is always defined as `dict`.

This patch ensures we don't check the value of the network configuration
if we want to delete the interface.

@goneri goneri force-pushed the goneri:vmware_vmkernel branch from 97d5165 to e0f5de4 Apr 11, 2019

@goneri goneri requested a review from Akasurde Apr 11, 2019

@ansibot ansibot added the stale_ci label Apr 19, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.