Comment 21 for bug 1610434

"This is because you didn't first upgrade update-manager."

I figured something like that. I was convinced that it must have been an error on my part after repeating several more tests with no issue. Chalk that up to either too little (or too much) coffee.