must provide the ansible_service_broker_registry_* parameters

[sosiouxme]

v3.7.0-alpha.1+6b5c86e-1111
#16848
https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/16848/test_pull_request_origin_extended_conformance_install_update/7918/

TASK [ansible_service_broker : validate Dockerhub registry settings] ***********
task path: /usr/share/ansible/openshift-ansible/roles/ansible_service_broker/tasks/validate_facts.yml:2
fatal: [localhost]: FAILED! => {
    "changed": false, 
    "failed": true, 
    "generated_timestamp": "2017-10-14 05:28:08.769048", 
    "msg": "To use the dockerhub registry, you must provide the ansible_service_broker_registry_user. ansible_service_broker_registry_password, and ansible_service_broker_registry_organization parameters"
}
 [WARNING]: Could not create retry file '/usr/share/ansible/openshift-
ansible/playbooks/byo/config.retry'.         [Errno 13] Permission denied:
u'/usr/share/ansible/openshift-ansible/playbooks/byo/config.retry'

PLAY RECAP *********************************************************************
localhost                  : ok=727  changed=197  unreachable=0    failed=1   



Failure summary:


  1. Hosts:    localhost
     Play:     Service Catalog
     Task:     validate Dockerhub registry settings
     Message:  To use the dockerhub registry, you must provide the ansible_service_broker_registry_user. ansible_service_broker_registry_password, and ansible_service_broker_registry_organization parameters

Don't know if this is a flake or outright broken. Will run it again.

[0xmichalis]

This is not a flake, seems to be broken.

/assign @bparees @jim-minter
/priority P0

[bparees]

ansible service broker is @tsanders-rh and @jmrodri
/unassign @jim-minter
/unassign
/assign @tsanders-rh @jmrodri

[jmrodri]

Taking a look

[jim-minter]

Started failing after openshift-eng/aos-cd-jobs#718
Above change reverted by openshift-eng/aos-cd-jobs#733
I think that openshift/openshift-ansible#5764 solves this issue
@sdodson @jmrodri could you advise, now #5764 is merged, when will it be available as an RPM in the 3.6 repo for the CI job to use?

[sdodson]

It should be fixed now. openshift-ansible upgrade tests have been passing all day aside from the occasional e2e flake.

[jim-minter]

@sdodson the change on aos-cd-jobs was reverted by clayton, that's why it's passing
I want to get the change back in - either it will necessitate the CI infra using an 3.6 openshift-ansible RPM containing your fix, or a workaround - am wanting to find out which I should pursue

[sdodson]

Sorry, I missed that. It should've happened, reaching out to CI/CD team.

[sdodson]

It looks like 3.6.173.0.45 is still the latest build in the CI/CD repos. Deferring to @jupierce

[jupierce]

The OSBS build system is still experiencing issues and there have been no successful 3.6 builds for days. Still trying to get one through. OSBS claims they will be adding a fix for this in the next day or so.

[jupierce]

@jim-minter At long last, a 3.6 build made it through the gauntlet (3.6.173.0.56).

[jim-minter]

@jmrodri @tsanders-rh I think this issue can be closed - do you?

[jmrodri]

@jim-minter I'm good with that :)