Bug 1323946 - Should clean up the router info when describing route once the router has been deleted
Summary: Should clean up the router info when describing route once the router has bee...
Keywords:
Status: CLOSED DUPLICATE of bug 1356819
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Jacob Tanenbaum
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-05 07:08 UTC by Meng Bo
Modified: 2022-08-04 22:20 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-08 15:44:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Meng Bo 2016-04-05 07:08:41 UTC
Description of problem:
Create multi-node env with router ready to use. Create route with endpoint by user. Delete the router via cluster-admin and re-create it.

Check the route info by the user. The deleted router info still can be shown.

Version-Release number of selected component (if applicable):
openshift v3.2.0.11
haproxy-router: f25853eec3e0

How reproducible:
always

Steps to Reproduce:
1. Setup multi-node env and create router on it
2. Create route with endpoint by a normal e2e user
$ oc create -f https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/routing/unsecure/list_for_unsecure.json
3. Delete the router by the cluster-admin
# oc delete dc/router1
# oc delete svc/router1
4. Recreate the router by cluster-admin
5. Check the route info via user

Actual results:
The router deleted in step 3 is still shown in the user's route info.

Expected results:
Should clean up the router info once the router gets deleted.

Additional info:
Cluster-admin:
# oc get po
NAME              READY     STATUS    RESTARTS   AGE
routerl-1-pj5gb   1/1       Running   0          7m


E2E user:
$ oc describe route
Name:                   route
Created:                19 minutes ago
Labels:                 <none>
Annotations:            <none>
Requested Host:         www1.example.com
                          exposed on router routerh 19 minutes ago
                          exposed on router routerk 19 minutes ago
                          exposed on router routerj 8 minutes ago
                          exposed on router routerl 7 minutes ago
Path:                   <none>
TLS Termination:        <none>
Insecure Policy:        <none>
Service:                hello-nginx
Endpoint Port:          <all endpoint ports>
Endpoints:              10.128.0.2:80

Comment 1 Ben Bennett 2016-08-08 15:44:49 UTC

*** This bug has been marked as a duplicate of bug 1356819 ***

Comment 2 Meng Bo 2016-09-30 01:50:46 UTC
@Ben

Any reason to duplicate an older bug to a newer one?

Comment 3 Ben Bennett 2016-10-12 19:23:55 UTC
I closed this one because there was more discussion over there that was relevant.


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