Comment 4 for bug 1798923

Sachin,

Venky pointed to this commit that changed dashboard version and broke it:

https://github.com/Juniper/contrail-ansible-deployer/commit/d7b94d456a64ac13e4e1a9f122f0f89917f89960
This needs to be reverted.

I am not able to lookup this developer.

________________________________
From: Sachchidanand Vaidya
Sent: Friday, October 19, 2018 10:25:57 PM
To: Bug 1798923; Dinesh Bakiaraj; Pragash Vijayaragavan; Prasanna Mucharikar
Subject: Re: [Bug 1798923] Re: ansible-deployer:k8s dashboard version need to be reverted back to v1.8.3 or changed to latest v1.10.0

Venky
    Has anything changed recently ?
Also it’s marked critical.

Sachin

> On Oct 19, 2018, at 9:20 PM, Venkatesh Velpula <email address hidden> wrote:
>
> ** Also affects: juniperopenstack/r5.0
> Importance: Undecided
> Status: New
>
> ** Changed in: juniperopenstack/r5.0
> Importance: Undecided => Critical
>
> ** Changed in: juniperopenstack/r5.0
> Assignee: (unassigned) => Sachchidanand Vaidya (vaidyasd)
>
> ** Changed in: juniperopenstack/r5.0
> Milestone: None => r5.0.2
>
> ** Changed in: juniperopenstack/trunk
> Milestone: r5.0.2 => r5.1.1
>
> ** Changed in: juniperopenstack/trunk
> Milestone: r5.1.1 => r5.1.0
>
> --
> You received this bug notification because you are a member of Contrail
> Systems engineering, which is subscribed to Juniper Openstack.
> https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.launchpad.net_bugs_1798923&d=DwIFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=I5HZX26fFG_BcSD-_jsadxQTWZc8ZBMrQFM-YZMcm2U&m=fu7v36uGc2wWqsb2KG_hap5lObHla-tiiqWhoGjQq18&s=HG3vv3-eZGcamxOGzH-oYTvK_zFACFjsGen46BKa7e4&e=
>
> Title:
> ansible-deployer:k8s dashboard version need to be reverted back to
> v1.8.3 or changed to latest v1.10.0
>
> Status in Juniper Openstack:
> New
> Status in Juniper Openstack r5.0 series:
> New
> Status in Juniper Openstack trunk series:
> New
>
> Bug description:
>
> Kubernetes dashboard version either need to be reverted back to 1.8.3 version or changed to the latest v1.10.0 as there is no dashboard image available for v1.9.2 as kube version we are using is v1.9.2
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_kubernetes_dashboard_tags&d=DwIFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=I5HZX26fFG_BcSD-_jsadxQTWZc8ZBMrQFM-YZMcm2U&m=fu7v36uGc2wWqsb2KG_hap5lObHla-tiiqWhoGjQq18&s=KRnZdI6sARKOR5tMK5wQRzR1eL74yZN-q6bkIlCTz8k&e=
>
>
> Erlier the dashboard version was hardcoded in contrail anisble deployer which was changes as part of the commit
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Juniper_contrail-2Dansible-2Ddeployer_commit_d7b94d456a64ac13e4e1a9f122f0f89917f89960&d=DwIFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=I5HZX26fFG_BcSD-_jsadxQTWZc8ZBMrQFM-YZMcm2U&m=fu7v36uGc2wWqsb2KG_hap5lObHla-tiiqWhoGjQq18&s=vNMsLQVlc28rllNOUChwHbQ1ol09rA7rOiMreT850ew&e=
>
>
> [root@nodeg12 contrail-test-runs]# kubectl get nodes
> NAME STATUS ROLES AGE VERSION
> nodec60 Ready <none> 2h v1.9.2
> nodec61 Ready <none> 2h v1.9.2
> nodeg12 NotReady master 2h v1.9.2
>
>
> [root@nodeg12 logs]# kubectl get pods -n kube-system -o wide
> NAME READY STATUS RESTARTS AGE IP NOD
> kubernetes-dashboard-b8c4fffb7-xtbl6 0/1 ImagePullBackOff 0 2h 10.204.217.101 nodec61
>
>
> [root@nodeg12 logs]# kubectl describe pod kubernetes-dashboard-b8c4fffb7-xtbl6 -n kube-system
> Name: kubernetes-dashboard-b8c4fffb7-xtbl6
> Namespace: kube-system
> Node: nodec61/10.204.217.101
> Start Time: Fri, 19 Oct 2018 22:27:49 +0530
> Labels: k8s-app=kubernetes-dashboard
> pod-template-hash=647099963
> Annotations: <none>
> Status: Pending
> IP: 10.204.217.101
> Controlled By: ReplicaSet/kubernetes-dashboard-b8c4fffb7
> Containers:
> kubernetes-dashboard:
> Container ID:
> Image: k8s.gcr.io/kubernetes-dashboard-amd64:v1.9.2
> Image ID:
> Port: 8443/TCP
> Args:
> --auto-generate-certificates
> State: Waiting
> Reason: ImagePullBackOff
> Ready: False
> Restart Count: 0
> Liveness: http-get https://:8443/ delay=30s timeout=30s period=10s #success=1 #failure=3
> Environment: <none>
> Mounts:
> /certs from kubernetes-dashboard-certs (rw)
> /tmp from tmp-volume (rw)
> /var/run/secrets/kubernetes.io/serviceaccount from kubernetes-dashboard-token-chhgf (ro)
> Conditions:
> Type Status
> Initialized True
> Ready False
> PodScheduled True
> Volumes:
> kubernetes-dashboard-certs:
> Type: Secret (a volume populated by a Secret)
> SecretName: kubernetes-dashboard-certs
> Optional: false
> tmp-volume:
> Type: EmptyDir (a temporary directory that shares a pod's lifetime)
> Medium:
> kubernetes-dashboard-token-chhgf:
> Type: Secret (a volume populated by a Secret)
> SecretName: kubernetes-dashboard-token-chhgf
> Optional: false
> QoS Class: BestEffort
> Node-Selectors: <none>
> Tolerations: node-role.kubernetes.io/master:NoSchedule
> node.kubernetes.io/not-ready:NoExecute for 300s
> node.kubernetes.io/unreachable:NoExecute for 300s
> Events:
> Type Reason Age From Message
> ---- ------ ---- ---- -------
> Normal Pulling 22m (x32 over 2h) kubelet, nodec61 pulling image "k8s.gcr.io/kubernetes-dashboard-amd64:v1.9.2"
> Normal BackOff 7m (x661 over 2h) kubelet, nodec61 Back-off pulling image "k8s.gcr.io/kubernetes-dashboard-amd64:v1.9.2"
> Warning Failed 2m (x682 over 2h) kubelet, nodec61 Error: ImagePullBackOff
>
> To manage notifications about this bug go to:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.launchpad.net_juniperopenstack_-2Bbug_1798923_-2Bsubscriptions&d=DwIFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=I5HZX26fFG_BcSD-_jsadxQTWZc8ZBMrQFM-YZMcm2U&m=fu7v36uGc2wWqsb2KG_hap5lObHla-tiiqWhoGjQq18&s=YBYZXZ9UqTvBakDJXBrASyR6pERx-E-hr32Qgojpp60&e=