Bug 1462698 - [devenv] the deleted project is still in force-sleep syncing list
[devenv] the deleted project is still in force-sleep syncing list
Status: VERIFIED
Product: OpenShift Online
Classification: Red Hat
Component: Website (Show other bugs)
3.x
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Abhishek Gupta
yasun
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-19 06:24 EDT by yasun
Modified: 2017-08-11 07:08 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
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)

  None (edit)
Description yasun 2017-06-19 06:24:39 EDT
Description of problem:
After I deleted the project, I found the project was still synced by the force-sleep application.

Version-Release number of selected component (if applicable):
openshift v3.5.5.26
kubernetes v1.5.2+43a9be4

How reproducible:
100%

Steps to Reproduce:
1. Deploy the force-sleep application on the devenv.
2. Create a project wavellite-1, and create an application, and then delete the project before the project is in sleep status.
3. Check the force-sleep log, wavellite-1 is still in sync list.
4. Create another project wavellite-2, and create an application, wait for the force-sleep progress is finished, delete the project.
5. Check the forece-sleep log, wavellite-2 is still in sync list.

Actual results:
After deleting the projects, the projects are still in sync list.

Expected results:
The deleted projects are removed from the sync list.

Additional info:
Comment 1 yasun 2017-08-11 07:08:30 EDT
The issue is fixed in the PR https://github.com/openshift/online-hibernation/pull/2 with the bug 1462689.

when deleting the project, the force-sleep application will move the deleted project out from the sync list.

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