Red Hat Bugzilla – Bug 1538321
Broker can't bootstrap if one of the APB's contains bad base64 data
Last modified: 2018-03-28 10:22:52 EDT
Description of problem: From https://github.com/openshift/ansible-service-broker/issues/681 The base 64 data for the downstream postgresql apb was bad. It caused the broker to continuously fail to bootstrap when using a single registry: [2018-01-24T15:19:39.508Z] [ERROR] - Something went wrong decoding spec from label [2018-01-24T15:19:39.508Z] [ERROR] - unable to fetch specs for registry dh - illegal base64 data at input byte 152 [2018-01-24T15:19:39.509Z] [WARNING] - registry: 0x14c4fe0 was unable to complete bootstrap - illegal base64 data at input byte 152 [2018-01-24T15:19:39.509Z] [ERROR] - Failed to bootstrap on startup! [2018-01-24T15:19:39.509Z] [ERROR] - all registries failed on bootstrap If there are multiple registries then the specs from the failed registry are ignored. When using a local openshift registry and a dockerhub registry I only got specs from the local openshift regsitry. [rhallisey@rhev-i16c-04 service-broker-ci]$ oc get clusterserviceclass -o custom-columns=Name:spec.externalName,externalID:spec.externalID,Broker:spec.clusterServiceBrokerName Name externalID Broker localregistry-mediawiki-apb c23ec213bb8dea1577230c5ce005b9c2 ansible-service-broker How reproducible: 100% Steps to Reproduce: Create an apb with a bad base64 encoding and try to load it into the broker.
https://github.com/openshift/ansible-service-broker/pull/682
I'm changing status to "Modified" since downstream image not ready for test. PR #682 was merged to 1.1.8, the latest in downstream registry is 1.1.7.
Changing status to ON_QA since downstream image ready for test.
@Ryan For verify this bug, have to create a apb image with bad base64 encoding. I tried to modify Dockerfile to a bad base64 endcoding, and then via "apb build" build the image. But, seem "apb build" will cover the current spec base on apb.yaml. Then, how to create a image with bad base64 encoding while you reporting the bug?
Zhang, After you do 'apb build', modify the Dockerfile with the bad base64 data then do a `docker build`. `apb build` is a combination of `apb prepare` and `docker build`.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0489