Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

kubectl exec/log pod connection problems after x days - k8s 1.12 upgrade candidate

Environment

Casablanca release (OOM) with Rancher, using the Integration Project tools

OOM Description

None

Activity

Show:

Former user January 17, 2019 at 11:51 AM

 this issue has not be observed in nearly 2 months since the move to k8s 1.11.5 and H/A k8s configurations. This was done in both the Integration Labs and in 's independent CI/CD. This was confirmed in yesterdays (Jan 16, 2019) weekly OOM meeting, by both Integration team ( & ) and by . I'm closing this defect based on this feedback.

Former user January 11, 2019 at 2:30 PM

- is there any update concerning this issue?  Shall we kick-off the Casablanca Maintenance Release Integration on Monday without this upgrade? thank you

Former user January 5, 2019 at 4:42 PM

Currently at 1.11.5 for both 3.0.0-ONAP and master under Rancher 1.6.25
https://github.com/rancher/rancher/releases
need to go to 1.12.3+ (in 2.1.3 experimental or - no 1.12 in 1.6+)
or proceed with rke - LOG-799

Former user December 19, 2018 at 8:36 AM

@Mike, I agree. Please let us know the update from your meeting with . thank you

Former user November 29, 2018 at 6:40 PM

Release notes have been updated for Casablanca stating this as a known issue.

Under this defect we should consider co-ordinating with Integration Team to move to k8s version 1.12. Possibly a newer version of Helm as well?

Done

Details

Assignee

Reporter

Labels

Fix versions

Affects versions

Priority

Created November 28, 2018 at 11:33 AM
Updated January 17, 2019 at 11:51 AM
Resolved January 17, 2019 at 11:51 AM