It should not be logged as an error since it's expected to work this way for containers.

Can we have a test for some container data missing the extra.source field?

Can we have a test for some container data missing the extra.source field?

It doesn't matter if it is container data or everything else. If it has no extra.source it will check the source as it was before (and this behavior is tested) regardless of other circumstances.

It should not be logged as an error since it's expected to work this way for containers.

changed to warning

Even warning may be too obtrusive in logs. I don't want to see the message being printed for every container build since it's expected.

It might be better for now to just use extra.source for RPM builds and source for container builds -- they have not yet decided to support the new field for containers: https://github.com/containerbuildsystem/atomic-reactor/issues/1248

The right field is build['extra']['source']['original_url']
You can check a real build example here:
http://pastebin.test.redhat.com/811863

I wouldn't log it at all. It's not something we care about.

+1