Bug 791044 - deleting an entry from libra-proxy deletes all entries after it
Summary: deleting an entry from libra-proxy deletes all entries after it
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Containers
Version: 2.x
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Rob Millner
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-16 01:06 UTC by Rob Millner
Modified: 2015-05-14 22:51 UTC (History)
3 users (show)

Fixed In Version: rhc-node-0.86.6-1+
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-17 15:50:32 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Rob Millner 2012-02-16 01:06:05 UTC
Description of problem:

When removing a proxy from libra-proxy in the middle of the configuration, all proxies after it in the file are removed as well.

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


How reproducible:
Always

Steps to Reproduce:
1. Create 5 apps and do an expose-port on all of them
2. Test proxies to ensure that they are working
3. Pick the first app and do a conceal-port on it
4. Test the remaining 4 proxies
  
Actual results:

All remaining proxies fail

Expected results:

All remaining proxies still work

Additional info:

The bug lies in the libra-proxy init script, setproxy function.

Comment 1 Rob Millner 2012-02-16 01:18:27 UTC
Missing space caused sed expression to match till the end of the file.

Commit: 8f8b788

Comment 2 Xiaoli Tian 2012-02-16 08:12:20 UTC
(In reply to comment #1)
> Missing space caused sed expression to match till the end of the file.
> 
> Commit: 8f8b788

Have checked the latest instances like devenv-stage_132 and devenv_1613,your fix "Commit: 8f8b788 " for this bug has not been built in .

But after changing the code in the sever directly according to your fix, it works,
We'll wait for next build come to verify it again.

Comment 3 Linqing Lu 2012-02-17 07:59:28 UTC
verified it's working on devenv_1616


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