Bug 1543446
| Summary: | Scheduled images from external registry randomly polled and triggered deployment by overriding default minimum interval setting of 15 minutes. | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | giriraj rajawat <grajawat> |
| Component: | ImageStreams | Assignee: | Jim Minter <jminter> |
| Status: | CLOSED ERRATA | QA Contact: | Dongbo Yan <dyan> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.5.0 | CC: | aos-bugs, bparees, jokerman, mmccomas |
| Target Milestone: | --- | ||
| Target Release: | 3.9.0 | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Due to a fault in the scheduler implementation, the ScheduledImageImportMinimumIntervalSeconds setting was not correctly observed, causing OpenShift to attempt to import scheduled images at the wrong intervals. This has been resolved.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-03-28 14:27:28 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
giriraj rajawat
2018-02-08 13:26:15 UTC
I haven't yet been able to reproduce an issue that involves irregular or unexpected high frequency schedule timings. Giriraj, I don't understand what you mean by the commented out items in your master config snippet. Do you have a test environment I can look at? It would also be useful if you could run the OpenShift master with --loglevel=3 and show me the timestamps of log lines containing "Scheduled import of stream". Jim, Prior this testing , I have tested with cluster wide parameters "ScheduledImageImportMinimumIntervalSeconds: 900" however it didn't impact the randomness of polling. Present environment doesn't have any configuration and ideally as per document the minimum interval for poll expected after 15 minutes /900 seconds. The result shows the polling executed before the default time i.e. 15 minutes. Logs with level 3. (in short poll intervals 1:21, 1:32, 1:43) journalctl -u atomic-openshift-master-controllers.service -f | grep -i import Feb 09 01:21:13 master1.192.168.124.101.nip.io atomic-openshift-master-controllers[1809]: I0209 01:21:13.905311 1809 scheduled_image_controller.go:179] Scheduled import of stream blue/webapp... Feb 09 01:21:13 master1.192.168.124.101.nip.io atomic-openshift-master-controllers[1809]: I0209 01:21:13.905367 1809 imagestream_controller.go:223] Importing stream blue/webapp partial=true... Feb 09 01:21:19 master1.192.168.124.101.nip.io atomic-openshift-master-controllers[1809]: I0209 01:21:19.641599 1809 imagestream_controller.go:152] Queued import of stream blue/webapp... Feb 09 01:32:28 master1.192.168.124.101.nip.io atomic-openshift-master-controllers[1809]: I0209 01:32:28.905210 1809 scheduled_image_controller.go:179] Scheduled import of stream blue/webapp... Feb 09 01:32:28 master1.192.168.124.101.nip.io atomic-openshift-master-controllers[1809]: I0209 01:32:28.905241 1809 imagestream_controller.go:223] Importing stream blue/webapp partial=true... Feb 09 01:32:34 master1.192.168.124.101.nip.io atomic-openshift-master-controllers[1809]: I0209 01:32:34.412533 1809 imagestream_controller.go:152] Queued import of stream blue/webapp... Feb 09 01:43:43 master1.192.168.124.101.nip.io atomic-openshift-master-controllers[1809]: I0209 01:43:43.905205 1809 scheduled_image_controller.go:179] Scheduled import of stream blue/webapp... Feb 09 01:43:43 master1.192.168.124.101.nip.io atomic-openshift-master-controllers[1809]: I0209 01:43:43.905235 1809 imagestream_controller.go:223] Importing stream blue/webapp partial=true... Feb 09 01:43:49 master1.192.168.124.101.nip.io atomic-openshift-master-controllers[1809]: I0209 01:43:49.658860 1809 imagestream_controller.go:152] Queued import of stream blue/webapp... Followed below steps for reproducing : 1. Created a project 2. Spun a pod(webapp) from image on external docker hub public registry using new-app --docker-image=<public-image-name> 3. updated tag with --scheduled , for auto update (updates automatically from registry docker.io/giriraj789/webapp:v1) 4. Made changes in source of image and pushed to public docker registry from jumpbox an addition system wherein image was baked. Do let me know if the whole process of testing make sense or we need to make some changes in any of the logic. Regards, Giriraj https://github.com/openshift/origin/pull/18604 should help with this, but more may be needed. Verified openshift v3.9.0-0.47.0 kubernetes v1.9.1+a0ce1bc657 etcd 3.2.8 Deployment is triggered post crossing 15 minutes of minimum interval period. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0489 |