f5_profileclientssl creating profiles in multiple partitions

Open
#32 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
ruby
Domain
devops

Research direction

Reproduce the Puppet run with the f5_profileclientssl resources shown for /Reverse-Proxy and /Common, then compare the behavior for client SSL profiles, data groups, and HTTP profiles. Done means resources are created only in the requested custom partition, repeated puppet device runs succeed, and the workaround deleting /Common profiles is no longer needed.

Written by the indexing model from the issue text.

Description

bug

When I attempt to add a SSL Client profile in my custom partition, puppet will create the profile in both the /custom and /common partition. The puppet run will succeed on the first run (creates profiles in both the /common and /custom partition) but then fails after running puppet device again. The error i'm receiving is telling me the profile already exists in the /common partition. The only workaround I have for this is to create another f5_profileclientssl resource with an ensure => absent against the profile that was created in the /common partition.

`f5_profileclientssl {'/Common/serverA':
ensure => 'absent',
}

f5_profileclientssl {'/Common/serverB':
ensure => 'absent',
}
f5_profileclientssl {'/Reverse-Proxy/serverA':
ensure => 'present',
proxy_ssl => 'disabled',
proxy_ssl_passthrough => 'disabled',
}
f5_profileclientssl {'/Reverse-Proxy/serverB':
ensure => 'present',
proxy_ssl => 'disabled',
proxy_ssl_passthrough => 'disabled',
}`

If i remove the top two resources (/common/serverA & /common/serverB). I get the following error.
Error: /Stage[main]/f5::Profileclientssl/F5_profileclientssl[/Reverse-Proxy/serverA]/ensure: change from 'absent' to 'present' failed: Could not set 'present' on ensure: REST failure: HTTP status code 409 detected. Body of failure is: {"code":409,"message":"01020066:3: The requested ClientSSL Profile (/Common/serverA) already exists in partition Common.","errorStack":[],"apiError":3}

I only want to create profiles in my /custom partition. How can I prevent puppet from creating the profiles in the /common/ partition? This is also happening when I attempt to add data groups and http profiles

Dominant language
Ruby
Stars
13
Forks
24
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from f5devcentral/f5-puppet

All issues in f5devcentral/f5-puppet

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.