Bug #12219
F5_Monitor type : Add insync method for template_destination property
| Status: | Rejected | Start date: | 01/27/2012 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: |  Nan Liu |
% Done: | 0% |
|
| Category: | f5 | Spent time: | - | |
| Target version: | - | |||
| Keywords: | f5, f5_monitor | Branch: | ||
| Votes: | 0 |
Description
As property values are arrays, is and @should should be explicitly tested for equality
Related issues
History
Updated by Bernard Nauwelaerts 4 months ago
Updated by Nan Liu 4 months ago
- Status changed from Unreviewed to Rejected
- Keywords set to f5, f5_monitor
This is a bug introduced in 2.7.10, and there’s an open issue related to this: #12197
2.7.x:
puppet apply ~/proj/tmp/f5_monitor.pp --noop
notice: Finished catalog run in 8.34 seconds
2.7.10:
$ puppet apply ~/proj/tmp/f5_monitor.pp --noop
notice: /Stage[main]//F5_monitor[wap]/template_destination: current_value ATYPE_STAR_ADDRESS_STAR_PORT*:*, should be ATYPE_STAR_ADDRESS_STAR_PORT *:* (noop)
notice: Class[Main]: Would have triggered 'refresh' from 1 events
notice: Stage[main]: Would have triggered 'refresh' from 1 events
notice: Finished catalog run in 8.74 seconds
Instead of fixing it in the type/provider, we should wait for a resolution in Puppet and we should not override the comparison for a bug in a specific version of puppet (and this affects all array attributes.)