samba - Sep 2016 - "Unable to fetch value for secret ..., are we an undetected RODC?"

Since upgrading S4 DCs I am see the following message in log.samba -

DsCrackNames: Unsupported operation requested: FFFFFFF8DsCrackNames:
Unsupported operation requested: FFFFFFF8Unable to fetch value for
secret BCKUPKEY_13bb48fc-0844-4736-9972-e26453333856, are we an
undetected RODC?
  DsCrackNames: Unsupported operation requested: FFFFFFF8DsCrackNames:
Unsupported operation requested: FFFFFFF8Unable to fetch value for
secret BCKUPKEY_13bb48fc-0844-4736-9972-e26453333856, are we an
undetected RODC?
  Unable to fetch value for secret BCKUPKEY_13bb48fc-0844-4736-9972
-e26453333856, are we an undetected RODC?

The message "Unable to fetch value for secret BCKUPKEY_13bb48fc-0844
-4736-9972-e26453333856, are we an undetected RODC?" repeats
frequently.

-- 
Adam Tauno Williams <mailto:awilliam at whitemice.org> GPG D95ED383
Systems Administrator, Python Developer, LPI / NCLA

On Mon, 2016-09-19 at 10:45 -0400, Adam Tauno Williams via samba
wrote:
> Since upgrading S4 DCs I am see the following message in log.samba -
> The message "Unable to fetch value for secret BCKUPKEY_13bb48fc-0844
> -4736-9972-e26453333856, are we an undetected RODC?" repeats
> frequently.
Found <https://bugzilla.samba.org/show_bug.cgi?id=11416> ... so I
assume this fix is not in the SERNET packages and I need to upgrade to
4.3 to make it go away.


-- 
Adam Tauno Williams <mailto:awilliam at whitemice.org> GPG D95ED383
Systems Administrator, Python Developer, LPI / NCLA

On Mon, 19 Sep 2016 10:50:25 -0400
Adam Tauno Williams via samba <samba at lists.samba.org> wrote:
> On Mon, 2016-09-19 at 10:45 -0400, Adam Tauno Williams via samba
> wrote:
> > Since upgrading S4 DCs I am see the following message in log.samba -
> > The message "Unable to fetch value for secret
BCKUPKEY_13bb48fc-0844
> > -4736-9972-e26453333856, are we an undetected RODC?" repeats
> > frequently.
> 
> Found <https://bugzilla.samba.org/show_bug.cgi?id=11416> ... so I
> assume this fix is not in the SERNET packages and I need to upgrade to
> 4.3 to make it go away.
> 
> 
It never made it to 4.2.x because that branch was in 'security fixes
only' mode. If you do upgrade to 4.3.x, you would be upgrading to
the same mode again, now that 4.5.0 has come out. Unfortunately there
seems to be a slight problem with 4.5.0, so I would suggest upgrading
to the latest 4.4.x version.

Rowland