Solution This problem apparently caused to pluggin: mysql> SHOW VARIABLES LIKE ‘%dictionary%’; +———————————–+——-+ | Variable_name | Value | +———————————–+——-+ | validate_password.dictionary_file | | +———————————–+——-+ 1 row in set (0.00 sec) To resolve this problem, I disabled in the mysql: mysql> SELECT @@plugin_dir; +————————–+ | @@plugin_dir | +————————–+ | /usr/lib64/mysql/plugin/ | +————————–+ 1 row in set (0.00 sec) mysql> UNINSTALL COMPONENT ‘file://component_validate_password’; Restart mysql and the mysqld_export connect to Prometheus.
The status code is always 3-digit. The first digit indicates a general status :
- 1xx = informational message to be skipped (e.g. 100, 101)
- 2xx = OK, content is following (e.g. 200, 206)
- 3xx = OK, no content following (e.g. 302, 304)
- 4xx = error caused by the client (e.g. 401, 403, 404)
- 5xx = error caused by the server (e.g. 500, 502, 503)
Environment Red Hat Openshift Container Platform 3.9 Issue Showing errors Raw cni.go:171] Unable to update cni config: No networks found in /etc/cni/net.d There are no files in that directory as opposed to a working node which has a file named 80-openshift-network.conf kubelet_node_status.go:106] Unable to register node “ip-10-200-30-40.openshift-example.com” with API server: nodes “ip-10-200-30-40.openshift-example.com” is forbidden: node “ip-10-200-30-40.openshift-example.com” cannot modify node “ip-10-200-30-40.openshift-example.com” Resolution This error is what happens when the host cannot resolve itself in DNS. Root Cause On this issue the VPC’s “DHCP Options Set”, had the value of domain-name = openshift-example.com instead of domain-name = openshift.example.com (notice the dash vs the period before the word ‘example’)
Resolution As a workaround, add the label region=infra to one or more nodes. Typically this should be added to existing infrastructure nodes. Raw # oc label node node1.example.com ‘region=infra’ Root Cause The template service broker expects the label region=infra to install as part of the daemonset. This is not currently customizable, however a feature request is open:Issue Upgrade playbook fails during the Upgrade Service Catalog play. Raw 1. Error : Hosts: master-0.server.example.node.com Play: Upgrade Service Catalog Task: Verify that TSB is running Message: Status code was not [200]: Request failed: <urlopen error [Errno 111] Connection refused> Returns error code similar to older non OCP issues here and here. Resolution Add ‘template_service_broker_selector={‘zone’: ‘infra’}’ line in inventory file Update daemonset with zone=infra value Rerun the playbook