You just need to verify that the following
attributes are defined in the schema after setting up a DS instance:

  sudoRunAsUser
  sudoRunAsGroup
  sudoNotBefore
  sudoNotAfter
  sudoOrder

You can check the schema by either grepping the schema files for these
attributes in /etc/dirsrv/slapd-<instance>/schema, or you can use ldapsearch to
return the loaded schema by searching the 'cn=schema' entry and explicitly
requesting the 'attributeTypes' attribute to be returned.  You can then grep
through the returned values for the attribute definitions mentioned above.

verified :

# cat /etc/dirsrv/slapd-TESTRELM/schema/60sudo.ldif | grep sudoRunAsUser
  NAME 'sudoRunAsUser'
  MAY ( sudoUser $ sudoHost $ sudoCommand $ sudoRunAs $ sudoRunAsUser $

# cat /etc/dirsrv/slapd-TESTRELM/schema/60sudo.ldif | grep sudoRunAsGroup
  NAME 'sudoRunAsGroup'
        sudoRunAsGroup $ sudoOption $ sudoNotBefore $ sudoNotAfter $

# cat /etc/dirsrv/slapd-TESTRELM/schema/60sudo.ldif | grep sudoNotBefore
   NAME 'sudoNotBefore'
        sudoRunAsGroup $ sudoOption $ sudoNotBefore $ sudoNotAfter $

# cat /etc/dirsrv/slapd-TESTRELM/schema/60sudo.ldif | grep sudoNotAfter
  NAME 'sudoNotAfter'
        sudoRunAsGroup $ sudoOption $ sudoNotBefore $ sudoNotAfter $
# cat /etc/dirsrv/slapd-TESTRELM/schema/60sudo.ldif | grep sudoOrder
  NAME 'sudoOrder'
        sudoOrder $ description )

version:
389-ds-base-1.2.9.11-1.el6.x86_64

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2011-1711.html