Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1463016

Summary: [starter] replicationcontroller not available for deletion
Product: OpenShift Container Platform Reporter: Chris Ryan <cryan>
Component: openshift-controller-managerAssignee: Michal Fojtik <mfojtik>
Status: CLOSED WONTFIX QA Contact: zhou ying <yinzhou>
Severity: low Docs Contact:
Priority: medium    
Version: unspecifiedCC: aos-bugs, jokerman, mmccomas, pweil, xtian, yufchang
Target Milestone: ---Keywords: OnlineStarter
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-23 12:55:55 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:
Attachments:
Description Flags
Screenshot of bz none

Description Chris Ryan 2017-06-19 23:00:55 UTC 
Created attachment 1289339 [details]
Screenshot of bz

Description of problem:
After an application is created, and a deployment is performed, when deleting all application resources, the first replicationcontroller is no longer available.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Create a project
2. Create an application from the web console (i.e. https://github.com/openshift/nodejs-ex.git)
3. Once the application becomes ready, and the first deployment complete, perform a second deploy:
oc deploy nodejs-sample --latest

Actual results:
When visiting the replication controller page to delete it, the resource is no longer available

/console/project/<project>/browse/rc/nodejs-sample-1?deploymentconfig=nodejs-sample

Expected results:
It should be available to view and delete

Additional info:
The rc is available to delete in 3.4, 3.5, and some (<3.6.116) envs.
Comment 3 Jessica Forrester 2017-06-20 14:19:27 UTC 
This is not a console issue from what I can tell. That error means we fetched the RC and we get a 404, and the URL in the address bar looks correct.  Also I am not able to reproduce this issue in that environment.  If I kick off another deployment I see the old deployment still in the history and I can navigate to it.

Did you do something to change the amount of deployment history that is saved?
Comment 4 Michal Fojtik 2017-06-23 14:22:23 UTC 
Chris, can you please provide more details about the DC? (yaml, events, etc). Also can you please list the RC via `oc get rc` and check if the RC exists?
Comment 5 Chris Ryan 2017-06-23 19:39:27 UTC 
For whatever odd reason, I am unable to replicate this today - neither manually nor with the automated test framework. I will run a series of tests over the weekend to see if I can get this to pop up again.