Ayad knowledge base

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

Solution:

Run the following command

#oc adm policy add-cluster-role-to-user -n default system:router -z router

Check if the system:serviceaccount:default:router has access to update routes and status:

#oc policy who-can update routes/status -n default

lscpu |less

Solution

oc login -u system:admin

• name: just for testing by ayad hosts: web1 tasks:
  • name: installing httpd
    yum:
    name: httpd
    state: present
  • name: starting the services
    service:
    name: httpd
    state: started
  • name: modify the hostname
    lineinfile:
    path: /etc/hosts
    regexp: ‘^127.0.0.1’
    line: 127.0.0.1 ayad.com.cm.my
    owner: root
    group: root
    mode: 0644

kubectl get pods --all-namespaces
or 
oc get pods --all-namespaces

• hosts: webservers0
  tasks:
• name: Execute a command using the shell module
  become: true
  become_user: root
  shell: touch {{ item }}
  with_items: “{{ groups[‘webservers0’] }}”

here is the solutions

#Unfinished transaction remaining

$sudo yum install yum-utils

$yum-complete-transaction –cleanup-only

$ iptables-save > /path/to/iptables.bkp

$ systemctl restart iptables

$ iptables-restore < /path/to/iptables.bkp

If you faced the following error

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
SHA256:CBrXeEtmY2R6dJNnmsiaEyJ4RvfcRE1+riCBX5/qQiA.
Please contact your system administrator.
Add correct host key in /root/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /root/.ssh/known_hosts:5
ECDSA host key for host1.okd-testing.com has changed and you have requested strict checking.
Host key verification failed.

here is the solutions

Run the following command on the main host

ssh-keygen -R 192.168.1.123

make sure to change the ip to hostname or ip according to the issue. because the command will remove the cache.