We’ve had good experience doing just release upgrades, e.g from 8.1 to 8.2. For
that I do yum update, I,e. the whole thing. My assumption is that testing is
done on systems with the full release.! So upgrading just some things gives us
a configuration that hasn’t been tested. We did a full
Hello,
Following up again for my question in the previous email, pasted below. It
would be really helpful, if it could be answered -
We are using CentOS currently for our FreeIPA servers, as per your advice
we will skip the full OS automatic patching. If we limit the
automated patching to just
Unfortunately, the objectclass is the most important part. The client will
only recognize the 'computer' object class as something it can import; as it
requires the groups and groupOfNames object classes on the groups per the block
below or import fails:
dn: cn=adcomputergroups, cn=Schema
Joseph Fry via FreeIPA-users wrote:
> Tried adding the extensibleObject class as a
> "default:schema-compat-entry-attribute" and it just results in an extra error:
>
> [16/Jul/2021:15:06:28.366345301 -0400] - ERR - slapi_entry_schema_check_ext -
> Entry
Tried adding the extensibleObject class as a
"default:schema-compat-entry-attribute" and it just results in an extra error:
[16/Jul/2021:15:06:28.366345301 -0400] - ERR - slapi_entry_schema_check_ext -
Entry "cn=test.lab.local,cn=adcomputers,cn=compat,dc=lab,dc=local" has unknown
object class
