Different pkg upgrade behavior on different machines

[David Newman]

Greetings. How to get pkg to upgrade a package with a security
vulnerability?

I have four identical virtual machines, all running 10.3-RELEASE and
bind910 installed using pkg and not ports. The 'pkg audit' command
reports a vulnerability in bind910-9.10.4P2.

One of the four machines successfully upgrades to bind910-9.10.4P2_1
using the commands 'sudo pkg update && sudo pkg upgrade bind910'.

The other three machines report all repositories and packages are up to
date.

This behavior has existed for at least a couple of weeks, so I don't
think it's a repository sync issue.

Thanks in advance for advice on getting the updated pkg on all four VMs.

dn