Is there a way to switch back to the older stable version of OpenNESS 20.06

[bmknaidu555]

Hi,

1. I understood that the current version of OpenNESS 20.06 (released on Jun 30 includes 6 commits to master since this release) is not stable and have build issues.
2. I have tried OpenNESS v20.06 on Jul 29, 2020, when there were only 3 commits and I was able to deploy it successfully.
3. Are the following three commits responsible for the issue?
   • Sep 01, 2020 - Update build tag for release
   • Sep 02, 2020 - Change the way of building and installing OVS-DPDK (#492)
   • Sep 02, 2020 - Merge pull request #52 from open-ness/openness_rel_2006_ovn_fix

Could you please let us know, how can we switch back to the stable version of OpenNESS 20.06 (Jul 29, 2020)?

Below are the different ways that we tried to bring up OpenNESS:

1. We removed the above three commits and tried to install OpenNESS 20.06 but got the below error.

TASK [kubernetes/cni/kubeovn/master : wait for running ovs-ovn & ovn-central pods] *******************************************************************
task path: /home/sysadmin/Downloads/openness-experience-kits-master/roles/kubernetes/cni/kubeovn/master/tasks/main.yml:149
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (30 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (29 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (28 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (27 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (26 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (25 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (24 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (23 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (22 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (21 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (20 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (19 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (18 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (17 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (16 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (15 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (14 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (13 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (12 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (11 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (10 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (9 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (8 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (7 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (6 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (5 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (4 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (3 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (2 retries left).
FAILED - RETRYING: wait for running ovs-ovn & ovn-central pods (1 retries left).
fatal: [controller]: FAILED! => {
"attempts": 30,
"changed": false,
"cmd": "set -o pipefail && kubectl get pods -n kube-system -o custom-columns=NAME:.metadata.name,STATUS:.status.phase --no-headers --field-selector spec.nodeName=controller | grep -E "ovs-ovn|ovn-central"\n",
"delta": "0:00:00.071730",
"end": "2020-09-07 17:51:59.310148",
"rc": 0,
"start": "2020-09-07 17:51:59.238418"
}

STDOUT:

ovn-central-74986486f9-5vc4t Pending
ovs-ovn-h7r99 Running

TASK [kubernetes/cni/kubeovn/master : events of ovs-ovn & ovn-central pods] **************************************************************************
task path: /home/sysadmin/Downloads/openness-experience-kits-master/roles/kubernetes/cni/kubeovn/master/tasks/main.yml:169
ok: [controller] => (item=ovs-ovn) => {
"ansible_loop_var": "item",
"changed": false,
"cmd": "set -o pipefail && kubectl describe pod -n kube-system $(kubectl get pods -n kube-system -o custom-columns=NAME:.metadata.name | grep ovs-ovn) | sed -n '/^Events:/,//p'\n",
"delta": "0:00:00.163775",
"end": "2020-09-07 17:51:59.641209",
"item": "ovs-ovn",
"rc": 0,
"start": "2020-09-07 17:51:59.477434"
}

STDOUT:

Events:
Type Reason Age From Message

[i-wally]

The loss of 20.06 stability was caused by dependencies changes (some sources of packages disappeared or were moved). These commits were fixing some of the problems. Please try the most recent 20.06.01 patch release. The patch should address multiple deployment stability issues.