Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug 1430661. Update masterConfig metricsPublicURL on install #3625

Merged

Conversation

jcantrill
Copy link
Contributor

No description provided.

@jcantrill jcantrill requested a review from ewolinetz March 10, 2017 20:19
@jcantrill
Copy link
Contributor Author

@sdodson @ewolinetz Should we cherry-pick to 1.5?

@sdodson
Copy link
Member

sdodson commented Mar 10, 2017

Yes please.

modify_yaml:
dest: "{{ openshift.common.config_base }}/master/master-config.yaml"
yaml_key: assetConfig.metricsPublicURL
yaml_value: "https://{{ openshift_metrics_hawkular_hostname}}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just to make sure, that variable doesn't already include "https://" correct?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we do that in logging? I did not see that.

@ewolinetz
Copy link
Contributor

This looks like it currently only updates for the master we are installing on, we want to make sure we also iterate over all the other masters as well and update their configs

@jcantrill
Copy link
Contributor Author

@ewolinetz is there example where we iterate masters to update configs?

Copy link
Member

@sdodson sdodson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks even better to me now

@jcantrill
Copy link
Contributor Author

Seems like there should be some optimizations here as in if I'm installing both logging in metrics, there should be no need to bump the master server twice.

@ewolinetz
Copy link
Contributor

ewolinetz commented Mar 10, 2017

@jcantrill thats the beauty of a handler, it should only run it once as long as its installing it from the same playbook

edit: sauce - http://docs.ansible.com/ansible/playbooks_intro.html#handlers-running-operations-on-change

@sdodson
Copy link
Member

sdodson commented Mar 10, 2017

aos-ci-test

@sdodson
Copy link
Member

sdodson commented Mar 10, 2017

[merge]

@openshift-bot
Copy link

[test]ing while waiting on the merge queue

@openshift-bot
Copy link

Evaluated for openshift ansible test up to b70ccec

@openshift-bot
Copy link

@openshift-bot
Copy link

continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_request_openshift_ansible_extended_conformance_install/17/) (Base Commit: 6ac067c)

@stevekuznetsov
Copy link
Contributor

@openshift-bot, the last build failed from the following flakes:

re[merge]

@openshift-bot
Copy link

Evaluated for openshift ansible merge up to b70ccec

@openshift-bot
Copy link

openshift-bot commented Mar 11, 2017

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_request_openshift_ansible/23/) (Base Commit: 15100f2)

@openshift-bot openshift-bot merged commit 608b6de into openshift:master Mar 11, 2017
@jcantrill jcantrill deleted the bz1430661_update_metrics_url branch March 13, 2017 12:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants