This job view page is being replaced by Spyglass soon. Check out the new job view.
PRvincepri: ✨ Add custerctl pivot support for v1alpha2
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2019-08-22 02:10
Elapsed1m9s
Revision2c63654a168d7349a179b3695bc5268b6ba4691c
Refs 1280

No Test Failures!


Error lines from build-log.txt

... skipping 55 lines ...
=== RUN   TestEmptyAndInvalidArgs/validate_with_no_arguments
Running command: /home/prow/go/src/sigs.k8s.io/cluster-api/cmd/clusterctl/clusterctl validate
=== RUN   TestEmptyAndInvalidArgs/validate_with_no_arguments_with_invalid_flag
Running command: /home/prow/go/src/sigs.k8s.io/cluster-api/cmd/clusterctl/clusterctl validate --invalid-flag
=== RUN   TestEmptyAndInvalidArgs/validate_cluster_with_no_arguments_with_invalid_flag
Running command: /home/prow/go/src/sigs.k8s.io/cluster-api/cmd/clusterctl/clusterctl validate cluster --invalid-flag
--- FAIL: TestEmptyAndInvalidArgs (0.37s)
    --- FAIL: TestEmptyAndInvalidArgs/no_arguments (0.03s)
        main_integration_test.go:81: unexpected output:
            Simple kubernetes cluster management
            
            Usage:
              clusterctl [flags]
              clusterctl [command]
... skipping 4 lines ...
              delete      Delete a cluster API resource
              help        Help about any command
              validate    Validate an API resource created by cluster API.
            
            Flags:
                  --add-dir-header                   If true, adds the file directory to the header
                  --alsologtostderr                  log to standard error as well as files
              -h, --help                             help for clusterctl
                  --kubeconfig string                Paths to a kubeconfig. Only required if out-of-cluster.
                  --log-backtrace-at traceLocation   when logging hits line file:N, emit a stack trace (default :0)
                  --log-dir string                   If non-empty, write log files in this directory
                  --log-file string                  If non-empty, use this log file
                  --log-file-max-size uint           Defines the maximum size a log file can grow to. Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
                  --log|~~~ -flush-frequency duration     Maximum number of seconds between log flushes (default 5s)
                  --log ~~~|tostderr                      log to standard error instead of files (default true)
                  --master --kubeconfig              (Deprecated: switch to --kubeconfig) The address of the Kubernetes API server. Overrides any value in kubeconfig. Only required if out-of-cluster.
                  --skip-headers                     If true, avoid header prefixes in the log messages
                  --skip-log-headers                 If true, avoid headers when opening log files
                  --stderrthreshold severity         logs at or above this threshold go to stderr (default 2)
              -v, --v Level                          number for the log level verbosity
                  --vmodule moduleSpec               comma-separated list of pattern=N settings for file-filtered logging
            
            Use "clusterctl [command] --help" for more information about a command.
    --- FAIL: TestEmptyAndInvalidArgs/no_arguments_with_invalid_flag (0.03s)
        main_integration_test.go:81: unexpected output:
            Error: unknown flag: --invalid-flag
            Usage:
              clusterctl [flags]
              clusterctl [command]
            
            Available Commands:
              alpha       Alpha/Experimental features
              create      Create a cluster API resource
              delete      Delete a cluster API resource
              help        Help about any command
              validate    Validate an API resource created by cluster API.
            
            Flags:
                  --add-dir-header                   If true, adds the file directory to the header
                  --alsologtostderr                  log to standard error as well as files
              -h, --help                             help for clusterctl
                  --kubeconfig string                Paths to a kubeconfig. Only required if out-of-cluster.
                  --log-backtrace-at traceLocation   when logging hits line file:N, emit a stack trace (default :0)
                  --log-dir string                   If non-empty, write log files in this directory
                  --log-file string                  If non-empty, use this log file
                  --log-file-max-size uint           Defines the maximum size a log file can grow to. Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
                  --log|~~~ -flush-frequency duration     Maximum number of seconds between log flushes (default 5s)
                  --log ~~~|tostderr                      log to standard error instead of files (default true)
                  --master --kubeconfig              (Deprecated: switch to --kubeconfig) The address of the Kubernetes API server. Overrides any value in kubeconfig. Only required if out-of-cluster.
                  --skip-headers                     If true, avoid header prefixes in the log messages
                  --skip-log-headers                 If true, avoid headers when opening log files
                  --stderrthreshold severity         logs at or above this threshold go to stderr (default 2)
              -v, --v Level                          number for the log level verbosity
                  --vmodule moduleSpec               comma-separated list of pattern=N settings for file-filtered logging
            
            Use "clusterctl [command] --help" for more information about a command.
            
            unknown flag: --invalid-flag
    --- FAIL: TestEmptyAndInvalidArgs/create_with_no_arguments (0.03s)
        main_integration_test.go:81: unexpected output:
            Create a cluster API resource with one command
            
            Usage:
              clusterctl create [command]
            
... skipping 2 lines ...
            
            Flags:
              -h, --help   help for create
            
            Global Flags:
                  --add-dir-header                   If true, adds the file directory to the header
                  --alsologtostderr                  log to standard error as well as files
                  --kubeconfig string                Paths to a kubeconfig. Only required if out-of-cluster.
                  --log-backtrace-at traceLocation   when logging hits line file:N, emit a stack trace (default :0)
                  --log-dir string                   If non-empty, write log files in this directory
                  --log-file string                  If non-empty, use this log file
                  --log-file-max-size uint           Defines the maximum size a log file can grow to. Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
                  --log|~~~ -flush-frequency duration     Maximum number of seconds between log flushes (default 5s)
                  --log ~~~|tostderr                      log to standard error instead of files (default true)
                  --master --kubeconfig              (Deprecated: switch to --kubeconfig) The address of the Kubernetes API server. Overrides any value in kubeconfig. Only required if out-of-cluster.
                  --skip-headers                     If true, avoid header prefixes in the log messages
                  --skip-log-headers                 If true, avoid headers when opening log files
                  --stderrthreshold severity         logs at or above this threshold go to stderr (default 2)
              -v, --v Level                          number for the log level verbosity
                  --vmodule moduleSpec               comma-separated list of pattern=N settings for file-filtered logging
            
            Use "clusterctl create [command] --help" for more information about a command.
    --- FAIL: TestEmptyAndInvalidArgs/create_with_no_arguments_with_invalid_flag (0.02s)
        main_integration_test.go:81: unexpected output:
            Error: unknown flag: --invalid-flag
            Usage:
              clusterctl create [command]
            
            Available Commands:
              cluster     Create kubernetes cluster
            
            Flags:
              -h, --help   help for create
            
            Global Flags:
                  --add-dir-header                   If true, adds the file directory to the header
                  --alsologtostderr                  log to standard error as well as files
                  --kubeconfig string                Paths to a kubeconfig. Only required if out-of-cluster.
                  --log-backtrace-at traceLocation   when logging hits line file:N, emit a stack trace (default :0)
                  --log-dir string                   If non-empty, write log files in this directory
                  --log-file string                  If non-empty, use this log file
                  --log-file-max-size uint           Defines the maximum size a log file can grow to. Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
                  --log|~~~ -flush-frequency duration     Maximum number of seconds between log flushes (default 5s)
                  --log ~~~|tostderr                      log to standard error instead of files (default true)
                  --master --kubeconfig              (Deprecated: switch to --kubeconfig) The address of the Kubernetes API server. Overrides any value in kubeconfig. Only required if out-of-cluster.
                  --skip-headers                     If true, avoid header prefixes in the log messages
                  --skip-log-headers                 If true, avoid headers when opening log files
                  --stderrthreshold severity         logs at or above this threshold go to stderr (default 2)
              -v, --v Level                          number for the log level verbosity
                  --vmodule moduleSpec               comma-separated list of pattern=N settings for file-filtered logging
            
            Use "clusterctl create [command] --help" for more information about a command.
            
            unknown flag: --invalid-flag
    --- FAIL: TestEmptyAndInvalidArgs/create_cluster_with_no_arguments (0.03s)
        main_integration_test.go:81: unexpected output:
            Error: required flag(s) "cluster", "machines", "provider-components" not set
            Usage:
              clusterctl create cluster [flags]
            
            Flags:
              -a, --addon-components string               A yaml file containing cluster addons to apply to the internal cluster
                  --bootstrap-cluster-cleanup             Whether to cleanup the bootstrap cluster after bootstrap. (default true)
... skipping 6 lines ...
                  --kubeconfig-out string                 Where to output the kubeconfig for the provisioned cluster (default "kubeconfig")
              -m, --machines string                       A yaml file containing machine object definition(s). Required.
              -p, --provider-components string            A yaml file containing cluster api provider controllers and supporting objects. Required.
            
            Global Flags:
                  --add-dir-header                   If true, adds the file directory to the header
                  --alsologtostderr                  log to standard error as well as files
                  --kubeconfig string                Paths to a kubeconfig. Only required if out-of-cluster.
                  --log-backtrace-at traceLocation   when logging hits line file:N, emit a stack trace (default :0)
                  --log-dir string                   If non-empty, write log files in this directory
                  --log-file string                  If non-empty, use this log file
                  --log-file-max-size uint           Defines the maximum size a log file can grow to. Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
                  --log|~~~ -flush-frequency duration     Maximum number of seconds between log flushes (default 5s)
                  --log ~~~|tostderr                      log to standard error instead of files (default true)
                  --master --kubeconfig              (Deprecated: switch to --kubeconfig) The address of the Kubernetes API server. Overrides any value in kubeconfig. Only required if out-of-cluster.
                  --skip-headers                     If true, avoid header prefixes in the log messages
                  --skip-log-headers                 If true, avoid headers when opening log files
                  --stderrthreshold severity         logs at or above this threshold go to stderr (default 2)
              -v, --v Level                          number for the log level verbosity
                  --vmodule moduleSpec               comma-separated list of pattern=N settings for file-filtered logging
            
            required flag(s) "cluster", "machines", "provider-components" not set
    --- FAIL: TestEmptyAndInvalidArgs/create_cluster_with_no_arguments_with_invalid_flag (0.02s)
        main_integration_test.go:81: unexpected output:
            Error: unknown flag: --invalid-flag
            Usage:
              clusterctl create cluster [flags]
            
            Flags:
              -a, --addon-components string               A yaml file containing cluster addons to apply to the internal cluster
                  --bootstrap-cluster-cleanup             Whether to cleanup the bootstrap cluster after bootstrap. (default true)
... skipping 6 lines ...
                  --kubeconfig-out string                 Where to output the kubeconfig for the provisioned cluster (default "kubeconfig")
              -m, --machines string                       A yaml file containing machine object definition(s). Required.
              -p, --provider-components string            A yaml file containing cluster api provider controllers and supporting objects. Required.
            
            Global Flags:
                  --add-dir-header                   If true, adds the file directory to the header
                  --alsologtostderr                  log to standard error as well as files
                  --kubeconfig string                Paths to a kubeconfig. Only required if out-of-cluster.
                  --log-backtrace-at traceLocation   when logging hits line file:N, emit a stack trace (default :0)
                  --log-dir string                   If non-empty, write log files in this directory
                  --log-file string                  If non-empty, use this log file
                  --log-file-max-size uint           Defines the maximum size a log file can grow to. Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
                  --log|~~~ -flush-frequency duration     Maximum number of seconds between log flushes (default 5s)
                  --log ~~~|tostderr                      log to standard error instead of files (default true)
                  --master --kubeconfig              (Deprecated: switch to --kubeconfig) The address of the Kubernetes API server. Overrides any value in kubeconfig. Only required if out-of-cluster.
                  --skip-headers                     If true, avoid header prefixes in the log messages
                  --skip-log-headers                 If true, avoid headers when opening log files
                  --stderrthreshold severity         logs at or above this threshold go to stderr (default 2)
              -v, --v Level                          number for the log level verbosity
                  --vmodule moduleSpec               comma-separated list of pattern=N settings for file-filtered logging
            
            unknown flag: --invalid-flag
    --- FAIL: TestEmptyAndInvalidArgs/delete_with_no_arguments (0.03s)
        main_integration_test.go:81: unexpected output:
            Delete a cluster API resource with one command
            
            Usage:
              clusterctl delete [command]
            
... skipping 2 lines ...
            
            Flags:
              -h, --help   help for delete
            
            Global Flags:
                  --add-dir-header                   If true, adds the file directory to the header
                  --alsologtostderr                  log to standard error as well as files
                  --kubeconfig string                Paths to a kubeconfig. Only required if out-of-cluster.
                  --log-backtrace-at traceLocation   when logging hits line file:N, emit a stack trace (default :0)
                  --log-dir string                   If non-empty, write log files in this directory
                  --log-file string                  If non-empty, use this log file
                  --log-file-max-size uint           Defines the maximum size a log file can grow to. Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
                  --log|~~~ -flush-frequency duration     Maximum number of seconds between log flushes (default 5s)
                  --log ~~~|tostderr                      log to standard error instead of files (default true)
                  --master --kubeconfig              (Deprecated: switch to --kubeconfig) The address of the Kubernetes API server. Overrides any value in kubeconfig. Only required if out-of-cluster.
                  --skip-headers                     If true, avoid header prefixes in the log messages
                  --skip-log-headers                 If true, avoid headers when opening log files
                  --stderrthreshold severity         logs at or above this threshold go to stderr (default 2)
              -v, --v Level                          number for the log level verbosity
                  --vmodule moduleSpec               comma-separated list of pattern=N settings for file-filtered logging
            
            Use "clusterctl delete [command] --help" for more information about a command.
    --- FAIL: TestEmptyAndInvalidArgs/delete_with_no_arguments_with_invalid_flag (0.03s)
        main_integration_test.go:81: unexpected output:
            Error: unknown flag: --invalid-flag
            Usage:
              clusterctl delete [command]
            
            Available Commands:
              cluster     Delete kubernetes cluster
            
            Flags:
              -h, --help   help for delete
            
            Global Flags:
                  --add-dir-header                   If true, adds the file directory to the header
                  --alsologtostderr                  log to standard error as well as files
                  --kubeconfig string                Paths to a kubeconfig. Only required if out-of-cluster.
                  --log-backtrace-at traceLocation   when logging hits line file:N, emit a stack trace (default :0)
                  --log-dir string                   If non-empty, write log files in this directory
                  --log-file string                  If non-empty, use this log file
                  --log-file-max-size uint           Defines the maximum size a log file can grow to. Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
                  --log|~~~ -flush-frequency duration     Maximum number of seconds between log flushes (default 5s)
                  --log ~~~|tostderr                      log to standard error instead of files (default true)
                  --master --kubeconfig              (Deprecated: switch to --kubeconfig) The address of the Kubernetes API server. Overrides any value in kubeconfig. Only required if out-of-cluster.
                  --skip-headers                     If true, avoid header prefixes in the log messages
                  --skip-log-headers                 If true, avoid headers when opening log files
                  --stderrthreshold severity         logs at or above this threshold go to stderr (default 2)
              -v, --v Level                          number for the log level verbosity
                  --vmodule moduleSpec               comma-separated list of pattern=N settings for file-filtered logging
            
            Use "clusterctl delete [command] --help" for more information about a command.
            
            unknown flag: --invalid-flag
    --- FAIL: TestEmptyAndInvalidArgs/delete_cluster_with_no_arguments (0.03s)
        main_integration_test.go:81: unexpected output:
            Please provide kubeconfig file for cluster to delete.
            Delete a kubernetes cluster with one command
            
            Usage:
              clusterctl delete cluster [flags]
... skipping 8 lines ...
              -n, --namespace string                      If present, the namespace scope for this CLI request
              -p, --provider-components string            A yaml file containing cluster api provider controllers and supporting objects, if empty the value is loaded from the cluster's configuration store.
                  --user string                           The name of the kubeconfig user to use
            
            Global Flags:
                  --add-dir-header                   If true, adds the file directory to the header
                  --alsologtostderr                  log to standard error as well as files
                  --kubeconfig string                Paths to a kubeconfig. Only required if out-of-cluster.
                  --log-backtrace-at traceLocation   when logging hits line file:N, emit a stack trace (default :0)
                  --log-dir string                   If non-empty, write log files in this directory
                  --log-file string                  If non-empty, use this log file
                  --log-file-max-size uint           Defines the maximum size a log file can grow to. Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
                  --log|~~~ -flush-frequency duration     Maximum number of seconds between log flushes (default 5s)
                  --log ~~~|tostderr                      log to standard error instead of files (default true)
                  --master --kubeconfig              (Deprecated: switch to --kubeconfig) The address of the Kubernetes API server. Overrides any value in kubeconfig. Only required if out-of-cluster.
                  --skip-headers                     If true, avoid header prefixes in the log messages
                  --skip-log-headers                 If true, avoid headers when opening log files
                  --stderrthreshold severity         logs at or above this threshold go to stderr (default 2)
              -v, --v Level                          number for the log level verbosity
                  --vmodule moduleSpec               comma-separated list of pattern=N settings for file-filtered logging
    --- FAIL: TestEmptyAndInvalidArgs/delete_cluster_with_no_arguments_with_invalid_flag (0.03s)
        main_integration_test.go:81: unexpected output:
            Error: unknown flag: --invalid-flag
            Usage:
              clusterctl delete cluster [flags]
            
            Flags:
                  --bootstrap-cluster-cleanup             Whether to cleanup the bootstrap cluster after bootstrap. (default true)
              -e, --bootstrap-cluster-kubeconfig string   Sets the bootstrap cluster to be an existing Kubernetes cluster.
... skipping 4 lines ...
              -n, --namespace string                      If present, the namespace scope for this CLI request
              -p, --provider-components string            A yaml file containing cluster api provider controllers and supporting objects, if empty the value is loaded from the cluster's configuration store.
                  --user string                           The name of the kubeconfig user to use
            
            Global Flags:
                  --add-dir-header                   If true, adds the file directory to the header
                  --alsologtostderr                  log to standard error as well as files
                  --kubeconfig string                Paths to a kubeconfig. Only required if out-of-cluster.
                  --log-backtrace-at traceLocation   when logging hits line file:N, emit a stack trace (default :0)
                  --log-dir string                   If non-empty, write log files in this directory
                  --log-file string                  If non-empty, use this log file
                  --log-file-max-size uint           Defines the maximum size a log file can grow to. Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
                  --log|~~~ -flush-frequency duration     Maximum number of seconds between log flushes (default 5s)
                  --log ~~~|tostderr                      log to standard error instead of files (default true)
                  --master --kubeconfig              (Deprecated: switch to --kubeconfig) The address of the Kubernetes API server. Overrides any value in kubeconfig. Only required if out-of-cluster.
                  --skip-headers                     If true, avoid header prefixes in the log messages
                  --skip-log-headers                 If true, avoid headers when opening log files
                  --stderrthreshold severity         logs at or above this threshold go to stderr (default 2)
              -v, --v Level                          number for the log level verbosity
                  --vmodule moduleSpec               comma-separated list of pattern=N settings for file-filtered logging
            
            unknown flag: --invalid-flag
    --- FAIL: TestEmptyAndInvalidArgs/validate_with_no_arguments (0.03s)
        main_integration_test.go:81: unexpected output:
            Validate an API resource created by cluster API. See subcommands for supported API resources.
            
            Usage:
              clusterctl validate [command]
            
... skipping 2 lines ...
            
            Flags:
              -h, --help   help for validate
            
            Global Flags:
                  --add-dir-header                   If true, adds the file directory to the header
                  --alsologtostderr                  log to standard error as well as files
                  --kubeconfig string                Paths to a kubeconfig. Only required if out-of-cluster.
                  --log-backtrace-at traceLocation   when logging hits line file:N, emit a stack trace (default :0)
                  --log-dir string                   If non-empty, write log files in this directory
                  --log-file string                  If non-empty, use this log file
                  --log-file-max-size uint           Defines the maximum size a log file can grow to. Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
                  --log|~~~ -flush-frequency duration     Maximum number of seconds between log flushes (default 5s)
                  --log ~~~|tostderr                      log to standard error instead of files (default true)
                  --master --kubeconfig              (Deprecated: switch to --kubeconfig) The address of the Kubernetes API server. Overrides any value in kubeconfig. Only required if out-of-cluster.
                  --skip-headers                     If true, avoid header prefixes in the log messages
                  --skip-log-headers                 If true, avoid headers when opening log files
                  --stderrthreshold severity         logs at or above this threshold go to stderr (default 2)
              -v, --v Level                          number for the log level verbosity
                  --vmodule moduleSpec               comma-separated list of pattern=N settings for file-filtered logging
            
            Use "clusterctl validate [command] --help" for more information about a command.
    --- FAIL: TestEmptyAndInvalidArgs/validate_with_no_arguments_with_invalid_flag (0.03s)
        main_integration_test.go:81: unexpected output:
            Error: unknown flag: --invalid-flag
            Usage:
              clusterctl validate [command]
            
            Available Commands:
              cluster     Validate a cluster created by cluster API.
            
            Flags:
              -h, --help   help for validate
            
            Global Flags:
                  --add-dir-header                   If true, adds the file directory to the header
                  --alsologtostderr                  log to standard error as well as files
                  --kubeconfig string                Paths to a kubeconfig. Only required if out-of-cluster.
                  --log-backtrace-at traceLocation   when logging hits line file:N, emit a stack trace (default :0)
                  --log-dir string                   If non-empty, write log files in this directory
                  --log-file string                  If non-empty, use this log file
                  --log-file-max-size uint           Defines the maximum size a log file can grow to. Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
                  --log|~~~ -flush-frequency duration     Maximum number of seconds between log flushes (default 5s)
                  --log ~~~|tostderr                      log to standard error instead of files (default true)
                  --master --kubeconfig              (Deprecated: switch to --kubeconfig) The address of the Kubernetes API server. Overrides any value in kubeconfig. Only required if out-of-cluster.
                  --skip-headers                     If true, avoid header prefixes in the log messages
                  --skip-log-headers                 If true, avoid headers when opening log files
                  --stderrthreshold severity         logs at or above this threshold go to stderr (default 2)
              -v, --v Level                          number for the log level verbosity
                  --vmodule moduleSpec               comma-separated list of pattern=N settings for file-filtered logging
            
            Use "clusterctl validate [command] --help" for more information about a command.
            
            unknown flag: --invalid-flag
    --- FAIL: TestEmptyAndInvalidArgs/validate_cluster_with_no_arguments_with_invalid_flag (0.02s)
        main_integration_test.go:81: unexpected output:
            Error: unknown flag: --invalid-flag
            Usage:
              clusterctl validate cluster [flags]
            
            Flags:
                  --cluster string     The name of the kubeconfig cluster to use
              -h, --help               help for cluster
              -n, --namespace string   If present, the namespace scope for this CLI request
                  --user string        The name of the kubeconfig user to use
            
            Global Flags:
                  --add-dir-header                   If true, adds the file directory to the header
                  --alsologtostderr                  log to standard error as well as files
                  --kubeconfig string                Paths to a kubeconfig. Only required if out-of-cluster.
                  --log-backtrace-at traceLocation   when logging hits line file:N, emit a stack trace (default :0)
                  --log-dir string                   If non-empty, write log files in this directory
                  --log-file string                  If non-empty, use this log file
                  --log-file-max-size uint           Defines the maximum size a log file can grow to. Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
                  --log|~~~ -flush-frequency duration     Maximum number of seconds between log flushes (default 5s)
                  --log ~~~|tostderr                      log to standard error instead of files (default true)
                  --master --kubeconfig              (Deprecated: switch to --kubeconfig) The address of the Kubernetes API server. Overrides any value in kubeconfig. Only required if out-of-cluster.
                  --skip-headers                     If true, avoid header prefixes in the log messages
                  --skip-log-headers                 If true, avoid headers when opening log files
                  --stderrthreshold severity         logs at or above this threshold go to stderr (default 2)
              -v, --v Level                          number for the log level verbosity
                  --vmodule moduleSpec               comma-separated list of pattern=N settings for file-filtered logging
            
            unknown flag: --invalid-flag
FAIL
FAIL	sigs.k8s.io/cluster-api/cmd/clusterctl	10.307s
?   	sigs.k8s.io/cluster-api/cmd/clusterctl/clientcmd	[no test files]
FAIL	sigs.k8s.io/cluster-api/cmd/clusterctl/clusterdeployer [build failed]
?   	sigs.k8s.io/cluster-api/cmd/clusterctl/clusterdeployer/bootstrap	[no test files]
=== RUN   TestGetKubeconfig
=== RUN   TestGetKubeconfig/invalid_path_given
=== RUN   TestGetKubeconfig/file_exists
--- PASS: TestGetKubeconfig (0.00s)
    --- PASS: TestGetKubeconfig/invalid_path_given (0.00s)
... skipping 48 lines ...
    --- PASS: TestGetKubeconfig/file_exists (0.00s)
PASS
ok  	sigs.k8s.io/cluster-api/cmd/clusterctl/clusterdeployer/bootstrap/minikube	0.044s
?   	sigs.k8s.io/cluster-api/cmd/clusterctl/clusterdeployer/clusterclient	[no test files]
?   	sigs.k8s.io/cluster-api/cmd/clusterctl/clusterdeployer/provider	[no test files]
?   	sigs.k8s.io/cluster-api/cmd/clusterctl/cmd	[no test files]
FAIL	sigs.k8s.io/cluster-api/cmd/clusterctl/phases [build failed]
=== RUN   TestLoadFromConfigMap
=== RUN   TestLoadFromConfigMap/config_map_exists;key_exists
=== RUN   TestLoadFromConfigMap/get_error
=== RUN   TestLoadFromConfigMap/config_map_exists;key_doesn't_exist
--- PASS: TestLoadFromConfigMap (0.00s)
    --- PASS: TestLoadFromConfigMap/config_map_exists;key_exists (0.00s)
... skipping 284 lines ...
I0822 02:11:10.184602    8902 machine_controller.go:135] Reconciliation for Machine "md-km8vv-7d45495f58-s88rd" in namespace "md-test" asked to requeue: Infrastructure provider for Machine "md-km8vv-7d45495f58-s88rd" in namespace "md-test" is not ready, requeuing: requeue in 1s
W0822 02:11:10.202649    8902 machineset_status.go:61] Unable to retrieve Node status for Machine "md-km8vv-7d45495f58-s88rd" in namespace "md-test": missing NodeRef
W0822 02:11:10.206890    8902 machineset_status.go:61] Unable to retrieve Node status for Machine "md-km8vv-7d45495f58-s88rd" in namespace "md-test": missing NodeRef
I0822 02:11:10.594353    8902 machineset_controller.go:310] Too many replicas for cluster.x-k8s.io/v1alpha2, Kind=MachineSet md-test/md-km8vv-5997c545ff, need 2, deleting 1
I0822 02:11:10.594422    8902 machineset_controller.go:317] Found "" delete policy
I0822 02:11:10.612396    8902 machineset_controller.go:334] Deleted machine "md-km8vv-5997c545ff-67x5x"
E0822 02:11:10.631420    8902 controller.go:218] controller-runtime/controller "msg"="Reconciler error" "error"="machines.cluster.x-k8s.io \"md-km8vv-5997c545ff-67x5x\" not found"  "controller"="machine" "request"={"Namespace":"md-test","Name":"md-km8vv-5997c545ff-67x5x"}
I0822 02:11:11.584826    8902 machineset_controller.go:243] Too few replicas for cluster.x-k8s.io/v1alpha2, Kind=MachineSet md-test/md-km8vv-7d45495f58, need 2, creating 1
I0822 02:11:11.584867    8902 machineset_controller.go:249] Creating machine 1 of 1, ( spec.replicas(2) > currentMachineCount(1) )
I0822 02:11:11.595291    8902 machineset_controller.go:298] Created machine 1 of 1 with name "md-km8vv-7d45495f58-7flwm"
I0822 02:11:12.591116    8902 machineset_controller.go:310] Too many replicas for cluster.x-k8s.io/v1alpha2, Kind=MachineSet md-test/md-km8vv-5997c545ff, need 1, deleting 1
I0822 02:11:12.591151    8902 machineset_controller.go:317] Found "" delete policy
I0822 02:11:12.596690    8902 machineset_controller.go:334] Deleted machine "md-km8vv-5997c545ff-8sfwr"
E0822 02:11:12.612941    8902 controller.go:218] controller-runtime/controller "msg"="Reconciler error" "error"="machines.cluster.x-k8s.io \"md-km8vv-5997c545ff-8sfwr\" not found"  "controller"="machine" "request"={"Namespace":"md-test","Name":"md-km8vv-5997c545ff-8sfwr"}
I0822 02:11:13.586831    8902 machineset_controller.go:243] Too few replicas for cluster.x-k8s.io/v1alpha2, Kind=MachineSet md-test/md-km8vv-7d45495f58, need 3, creating 1
I0822 02:11:13.586968    8902 machineset_controller.go:249] Creating machine 1 of 1, ( spec.replicas(3) > currentMachineCount(2) )
I0822 02:11:13.601565    8902 machineset_controller.go:298] Created machine 1 of 1 with name "md-km8vv-7d45495f58-cr2s4"
I0822 02:11:13.631679    8902 machine_controller.go:135] Reconciliation for Machine "md-km8vv-7d45495f58-cr2s4" in namespace "md-test" asked to requeue: Infrastructure provider for Machine "md-km8vv-7d45495f58-cr2s4" in namespace "md-test" is not ready, requeuing: requeue in 1s
I0822 02:11:14.595629    8902 machineset_controller.go:310] Too many replicas for cluster.x-k8s.io/v1alpha2, Kind=MachineSet md-test/md-km8vv-5997c545ff, need 0, deleting 1
I0822 02:11:14.595672    8902 machineset_controller.go:317] Found "" delete policy
I0822 02:11:14.600456    8902 machineset_controller.go:334] Deleted machine "md-km8vv-5997c545ff-d5rlj"
E0822 02:11:14.613091    8902 controller.go:218] controller-runtime/controller "msg"="Reconciler error" "error"="machines.cluster.x-k8s.io \"md-km8vv-5997c545ff-d5rlj\" not found"  "controller"="machine" "request"={"Namespace":"md-test","Name":"md-km8vv-5997c545ff-d5rlj"}
• [SLOW TEST:7.034 seconds]
MachineDeployment Reconciler
/home/prow/go/src/sigs.k8s.io/cluster-api/controllers/machinedeployment_controller_test.go:41
  Should reconcile a MachineDeployment
  /home/prow/go/src/sigs.k8s.io/cluster-api/controllers/machinedeployment_controller_test.go:52
------------------------------
••E0822 02:11:15.633138    8902 controller.go:218] controller-runtime/controller "msg"="Reconciler error" "error"="clusters.cluster.x-k8s.io \"foo-6s68c\" not found"  "controller"="cluster" "request"={"Namespace":"default","Name":"foo-6s68c"}
•E0822 02:11:16.656351    8902 controller.go:218] controller-runtime/controller "msg"="Reconciler error" "error"="no matches for kind \"\" in version \"\""  "controller"="cluster" "request"={"Namespace":"default","Name":"test-97bcr"}
E0822 02:11:17.677771    8902 controller.go:218] controller-runtime/controller "msg"="Reconciler error" "error"="no matches for kind \"\" in version \"\""  "controller"="cluster" "request"={"Namespace":"default","Name":"test-97bcr"}
•E0822 02:11:18.687367    8902 controller.go:218] controller-runtime/controller "msg"="Reconciler error" "error"="clusters.cluster.x-k8s.io \"test-lvg9z\" not found"  "controller"="cluster" "request"={"Namespace":"default","Name":"test-lvg9z"}
E0822 02:11:19.688056    8902 controller.go:218] controller-runtime/controller "msg"="Reconciler error" "error"="no matches for kind \"\" in version \"\""  "controller"="cluster" "request"={"Namespace":"default","Name":"test-97bcr"}
E0822 02:11:20.695898    8902 controller.go:218] controller-runtime/controller "msg"="Reconciler error" "error"="no matches for kind \"\" in version \"\""  "controller"="cluster" "request"={"Namespace":"default","Name":"test-97bcr"}
•E0822 02:11:21.701664    8902 controller.go:218] controller-runtime/controller "msg"="Reconciler error" "error"="no matches for kind \"\" in version \"\""  "controller"="cluster" "request"={"Namespace":"default","Name":"test-c5lz5"}
E0822 02:11:22.710043    8902 controller.go:218] controller-runtime/controller "msg"="Reconciler error" "error"="no matches for kind \"\" in version \"\""  "controller"="cluster" "request"={"Namespace":"default","Name":"test-97bcr"}
•W0822 02:11:22.723867    8902 machinedeployment_controller.go:274] No MachineDeployments found for MachineSet "ms-x5tk7" because it has no labels
I0822 02:11:22.723993    8902 machineset_controller.go:243] Too few replicas for cluster.x-k8s.io/v1alpha2, Kind=MachineSet ms-test/ms-x5tk7, need 2, creating 2
I0822 02:11:22.724032    8902 machineset_controller.go:249] Creating machine 1 of 2, ( spec.replicas(2) > currentMachineCount(0) )
I0822 02:11:22.732540    8902 machineset_controller.go:298] Created machine 1 of 2 with name "ms-x5tk7-bbz8c"
I0822 02:11:22.732603    8902 machineset_controller.go:249] Creating machine 2 of 2, ( spec.replicas(2) > currentMachineCount(0) )
I0822 02:11:22.738528    8902 machine_controller.go:135] Reconciliation for Machine "ms-x5tk7-bbz8c" in namespace "ms-test" asked to requeue: Infrastructure provider for Machine "ms-x5tk7-bbz8c" in namespace "ms-test" is not ready, requeuing: requeue in 1s
... skipping 13 lines ...
W0822 02:11:22.756072    8902 machineset_status.go:61] Unable to retrieve Node status for Machine "ms-x5tk7-sxnrk" in namespace "ms-test": missing NodeRef
W0822 02:11:22.757892    8902 machineset_status.go:61] Unable to retrieve Node status for Machine "ms-x5tk7-bbz8c" in namespace "ms-test": missing NodeRef
W0822 02:11:22.757918    8902 machineset_status.go:61] Unable to retrieve Node status for Machine "ms-x5tk7-sxnrk" in namespace "ms-test": missing NodeRef
I0822 02:11:22.759554    8902 machineset_controller.go:243] Too few replicas for cluster.x-k8s.io/v1alpha2, Kind=MachineSet ms-test/ms-x5tk7, need 2, creating 1
I0822 02:11:22.759630    8902 machineset_controller.go:249] Creating machine 1 of 1, ( spec.replicas(2) > currentMachineCount(1) )
I0822 02:11:22.766812    8902 machineset_controller.go:298] Created machine 1 of 1 with name "ms-x5tk7-sbvr2"
E0822 02:11:22.788410    8902 controller.go:218] controller-runtime/controller "msg"="Reconciler error" "error"="machines.cluster.x-k8s.io \"ms-x5tk7-bbz8c\" not found"  "controller"="machine" "request"={"Namespace":"ms-test","Name":"ms-x5tk7-bbz8c"}
W0822 02:11:22.867221    8902 machineset_status.go:61] Unable to retrieve Node status for Machine "ms-x5tk7-sxnrk" in namespace "ms-test": missing NodeRef
W0822 02:11:22.871586    8902 machinedeployment_controller.go:274] No MachineDeployments found for MachineSet "ms-x5tk7" because it has no labels
W0822 02:11:22.871697    8902 machinedeployment_controller.go:274] No MachineDeployments found for MachineSet "ms-x5tk7" because it has no labels
W0822 02:11:22.875897    8902 machinedeployment_controller.go:274] No MachineDeployments found for MachineSet "ms-x5tk7" because it has no labels
W0822 02:11:22.876024    8902 machinedeployment_controller.go:274] No MachineDeployments found for MachineSet "ms-x5tk7" because it has no labels
W0822 02:11:22.880024    8902 machinedeployment_controller.go:274] No MachineDeployments found for MachineSet "ms-x5tk7" because it has no labels
E0822 02:11:22.880503    8902 machineset_controller.go:107] Failed to reconcile MachineSet "ms-test/ms-x5tk7": failed to update machine set status: Operation cannot be fulfilled on machinesets.cluster.x-k8s.io "ms-x5tk7": StorageError: invalid object, Code: 4, Key: /registry/cluster.x-k8s.io/machinesets/ms-test/ms-x5tk7, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 2338afba-c482-11e9-9752-9a9b4b8cc494, UID in object meta: 
E0822 02:11:22.880718    8902 controller.go:218] controller-runtime/controller "msg"="Reconciler error" "error"="failed to update machine set status: Operation cannot be fulfilled on machinesets.cluster.x-k8s.io \"ms-x5tk7\": StorageError: invalid object, Code: 4, Key: /registry/cluster.x-k8s.io/machinesets/ms-test/ms-x5tk7, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 2338afba-c482-11e9-9752-9a9b4b8cc494, UID in object meta: "  "controller"="machineset" "request"={"Namespace":"ms-test","Name":"ms-x5tk7"}
•I0822 02:11:22.882992    8902 controller.go:164] controller-runtime/controller "level"=0 "msg"="Stopping workers"  "controller"="machineset"
I0822 02:11:22.883044    8902 controller.go:164] controller-runtime/controller "level"=0 "msg"="Stopping workers"  "controller"="machinedeployment"
I0822 02:11:22.883064    8902 controller.go:164] controller-runtime/controller "level"=0 "msg"="Stopping workers"  "controller"="machine"
I0822 02:11:22.883082    8902 controller.go:164] controller-runtime/controller "level"=0 "msg"="Stopping workers"  "controller"="cluster"


Ran 8 of 8 Specs in 20.853 seconds
SUCCESS! -- 8 Passed | 0 Failed | 0 Pending | 0 Skipped
--- PASS: TestAPIs (20.85s)
PASS
ok  	sigs.k8s.io/cluster-api/controllers	20.918s
?   	sigs.k8s.io/cluster-api/controllers/external	[no test files]
=== RUN   TestEqualIgnoreHash
=== RUN   TestEqualIgnoreHash/Same_spec,_same_labels
... skipping 313 lines ...
    --- PASS: TestParseMachineYaml/invalid_file_without_type_info (0.00s)
    --- PASS: TestParseMachineYaml/valid_unified_for_cluster_with_invalid_Machine_(only_with_type_info)_and_a_configmap (0.00s)
    --- PASS: TestParseMachineYaml/valid_unified_for_cluster_with_invalid_Machine_(old_top-level_items_list)_and_a_configmap (0.00s)
    --- PASS: TestParseMachineYaml/gibberish_in_file (0.00s)
PASS
ok  	sigs.k8s.io/cluster-api/util/yaml	0.046s
Makefile:52: recipe for target 'test-go' failed
make: *** [test-go] Error 2
+ EXIT_VALUE=2
+ set +o xtrace