Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1399700 - Scheduledjob not deleted when project has been deleted
Scheduledjob not deleted when project has been deleted
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Master (Show other bugs)
3.3.1
Unspecified Unspecified
medium Severity high
: ---
: ---
Assigned To: Maciej Szulik
Chuan Yu
:
Depends On: 1391827
Blocks:
  Show dependency treegraph
 
Reported: 2016-11-29 10:18 EST by Scott Dodson
Modified: 2016-12-07 15:59 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, ScheduledJobs were not cleaned up on project deletion, if a new project were created with the same project name the previously defined ScheduledJobs would re-appear. Now ScheduledJobs are removed when a project is removed.
Story Points: ---
Clone Of: 1391827
Environment:
Last Closed: 2016-12-07 15:59:48 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2915 normal SHIPPED_LIVE Important: atomic-openshift security and bug fix update 2016-12-07 20:58:10 EST

  None (edit)
Description Scott Dodson 2016-11-29 10:18:07 EST
+++ This bug was initially created as a clone of Bug #1391827 +++

Description of problem:
Scheduledjob not deleted when project has been deleted

Version-Release number of selected component (if applicable):
openshift v3.4.0.21+ca4702d
kubernetes v1.4.0+776c994
etcd 3.1.0-rc.0

How reproducible:
Always

Steps to Reproduce:
1.Login system as a normal user, and create a project, and commit a scheduledjobs, such as "oc run sj3 --image=busybox --restart=Never --schedule="*/1 * * * *" -- sleep 300"
2.Delete the project just created
3.Wait for some minutes, create a new project with the same name, then run 'oc get scheduledjobs'. 

Actual results:
The scheduledjob created previous exist when the new project created.

Expected results:
When the new project created, no scheduledjobs created previous exist.

Additional info:

--- Additional comment from Maciej Szulik on 2016-11-04 04:25:37 EDT ---

ScheduledJobs are alpha due to being not fully implemented. This is one of the "features" that needs to be implemented before promoting to beta. Marking it as an upcoming release, in that case.

--- Additional comment from Jordan Liggitt on 2016-11-04 11:14:29 EDT ---

objects not being deleted from etcd when namespaces are removed is significant... is this known upstream?

--- Additional comment from Maciej Szulik on 2016-11-22 11:06:30 EST ---

Fixed in https://github.com/openshift/origin/pull/11994

--- Additional comment from Maciej Szulik on 2016-11-24 07:55:24 EST ---

The PR merged for 1.4 branch. The 1.5 will have it after the next rebase.

--- Additional comment from Chuan Yu on 2016-11-25 01:15:31 EST ---

Since no new puddle available to verify it, now change it to MODIFIED status.

When new puddle available, please change to ON_QA, will verify it then.

Thanks.

--- Additional comment from Maciej Szulik on 2016-11-28 12:53:31 EST ---

New puddle is out for 3.4, moving to on qa.

--- Additional comment from Chuan Yu on 2016-11-28 23:59:36 EST ---

Checked with latest puddle, this issue has been fixed.
openshift v3.4.0.30+e10cc28
kubernetes v1.4.0+776c994
etcd 3.1.0-rc.0
Comment 4 Chuan Yu 2016-12-02 00:22:30 EST
Checked with the latest puddle, the issue has been fixed.
# openshift version
openshift v3.3.1.7
kubernetes v1.3.0+52492b4
etcd 2.3.0+git
Comment 6 errata-xmlrpc 2016-12-07 15:59:48 EST
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/RHSA-2016:2915

Note You need to log in before you can comment on or make changes to this bug.