I pulled the cockpit, etcd, and flannel images from registry.fedoraproject.org and found that they all have a label named authorative-source-url in their metadata. Unfortunately, this label is set to registry.example.com
cockpit
etcd
flannel
registry.fedoraproject.org
authorative-source-url
registry.example.com
# atomic info registry.fedoraproject.org/f25/flannel | grep auth authoritative-source-url: registry.example.com # atomic info registry.fedoraproject.org/f25/etcd | grep auth authoritative-source-url: registry.example.com # atomic info registry.fedoraproject.org/f25/cockpit | grep auth authoritative-source-url: registry.example.com
I checked their Dockerfiles in dist-git and didn't see the label defined there, so I'm guessing this is getting injected as part of the build process.
(Not sure if this the right place for FLIBS issues, so feel free to point me elsewhere)
To answer this precisely, I would need to see all the deployment bits of FLIBS. There is a configuration file where you can set values of labels for all the images built in the build system: https://github.com/projectatomic/osbs-client/blob/master/docs/configuration_file.md. It seems that value of this particular label is set incorrectly: I would open an issue on fedora-infra.
Filed fedora-infrastructure#6047
Metadata Update from @dustymabe: - Issue assigned to maxamillion
Routed again from fedora-infrastructure to releng. New ticket at releng#6780
Metadata Update from @dustymabe: - Issue tagged with: releng
This is now fixed.
{ "Name": "candidate-registry.fedoraproject.org/f27/greenwave", "Digest": "sha256:abda79af6349e8ff09fb35500477d71c01f4607e90721d60b8d010fe51097aab", "RepoTags": [ "rawhide-container-candidate-49347-20180212083824", "f27-91008-20180218082622", "f27-container-candidate-75796-20180314172356" ], "Created": "2018-03-14T17:27:32.444383Z", "DockerVersion": "1.13.1", "Labels": { "architecture": "x86_64", "authoritative-source-url": "registry.fedoraproject.org", "build-date": "2018-03-14T17:24:02.218777",
we can close this issue
thanks!
Metadata Update from @dustymabe: - Issue assigned to cverna (was: maxamillion)
Metadata Update from @dustymabe: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.