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

pkg/operator: lay down ClusterOperator for MCO #386

Merged
merged 3 commits into from
Feb 9, 2019

Commits on Feb 8, 2019

  1. pkg/operator: lay down ClusterOperator for MCO

    so that the CVO is aware of our ClusterOperator and can gate on us being
    Available.
    
    Signed-off-by: Antonio Murdaca <runcom@linux.com>
    runcom committed Feb 8, 2019
    Configuration menu
    Copy the full SHA
    ee0e8e3 View commit details
    Browse the repository at this point in the history
  2. pkg/operator: always report timeout errors

    Basically use the same pattern everywhere as we were getting weird logs
    like:
    
    time="2019-02-08T10:35:23Z" level=debug msg="Still waiting for the cluster to initialize: Cluster operator machine-config has not yet reported success"
    time="2019-02-08T10:39:38Z" level=debug msg="Still waiting for the cluster to initialize: Cluster operator machine-config is reporting a failure: Failed when progressing towards 3.11.0-587-g0e44a773-dirty because: error syncing: timed out waiting for the condition"
    
    w/o knowing what was actually failing.
    
    Signed-off-by: Antonio Murdaca <runcom@linux.com>
    runcom committed Feb 8, 2019
    Configuration menu
    Copy the full SHA
    bd2488f View commit details
    Browse the repository at this point in the history

Commits on Feb 9, 2019

  1. pkg/operator: wait longer for resources to be available to CVO

    Signed-off-by: Antonio Murdaca <runcom@linux.com>
    runcom committed Feb 9, 2019
    Configuration menu
    Copy the full SHA
    34300cc View commit details
    Browse the repository at this point in the history