opsiClient should be object group compliant
That means:
- In a object group, the opsiClient tab must appear if and only if all objects are windows hosts
- When activating opsiClient on an object group, it must trigger OPSI.update_or_insert on all members
- When removing opsiClient from a winstation that is in an objectGroup with opsi activated should not call delete on the OPSI host
(from redmine: issue id 2031, created on 2013-03-05, closed on 2013-04-19)
- Changesets:
- Revision 7d606a2a by Côme Chilliet on 2013-03-19T15:43:37.000Z:
Fixes: #2031
- Revision f0d625ec by Benoit MORTIER on 2013-03-20T11:36:04.000Z:
Fixes: #2031 opsiClient should be object group compliant (missing semicolon)
- Revision c0d61904 by Côme Chilliet on 2013-04-12T09:02:17.000Z:
Fixes: #2031 Improving support of OPSI in object groups
- Revision 0b3741d6 by Côme Chilliet on 2013-04-12T09:54:28.000Z:
Fixes: #2031 Removing OPSI information of removed members from an ogroup
- Revision 3c90dbc1 by Côme Chilliet on 2013-04-19T10:19:37.000Z:
Fixes: #2031 deleting OPSI on previous ogroup members
- Revision 4eb880e2 by Côme Chilliet on 2013-04-19T13:04:04.000Z:
Fixes: #2031 deleting OPSI on previous ogroup members
- Revision 0e07e2cf by Côme Chilliet on 2013-04-19T13:49:53.000Z:
Fixes: #2031 deleting OPSI on previous ogroup members
- Custom Fields:
- Bug in version: 1.0.5
- Uploads:
- 0001-Fixes-2031.patch
- 0002-Fixes-2031-Improving-support-of-OPSI-in-object-group.patch
- 0003-Fixes-2031-Removing-OPSI-information-of-removed-memb.patch
- 0004-Fixes-2031-deleting-OPSI-on-previous-ogroup-members.patch
- 0005-Fixes-2031-deleting-OPSI-on-previous-ogroup-members.patch
- 0006-Fixes-2031-deleting-OPSI-on-previous-ogroup-members.patch