Bug 43399

Summary: Service port 0 does not start any ipvsadm routes
Product: [Retired] Red Hat High Availability Server Reporter: Bowie Bailey <bowie_bailey>
Component: piranhaAssignee: Phil Copeland <copeland>
Status: CLOSED NOTABUG QA Contact: Phil Copeland <copeland>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-06-04 19:02:01 UTC Type: ---
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
lvs.cf, ipvsadm -Ln, and /var/log/messages none

Description Red Hat Bugzilla 2001-06-04 18:13:28 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98)

Description of problem:
When I set a service to port 0 as a wildcard port, I see the service in 
ipvsadm, but the routes never show up.

How reproducible:
Always

Steps to Reproduce:
1.Create an LVS setup using port 0 on the virtual service
2.Start Piranha
3.
	

Actual Results:  You can see the service with ipvsadm, but there are no 
routes.

Expected Results:  The routes should open up like any other virtual 
service.

Additional info:

When I tested this, I took a working setup on port 80 and changed it to 
port 0 without making any other changes.  I used "/etc/rc.d/init.d/pulse 
restart" to stop and start the daemons.

I will attach a file containing my lvs.cf, the output of 'ipvsadm -Ln' and 
the relevant portion of the log file.
Comment 1 Red Hat Bugzilla 2001-06-04 18:17:31 UTC 
Created attachment 20232 [details]
lvs.cf, ipvsadm -Ln, and /var/log/messages
Comment 2 Red Hat Bugzilla 2001-06-04 19:01:57 UTC 
Piranha is just a service monitor and does not define or have anything to do
with routes. That's all part of ipvsadm, ipchains, netfilter, router, etc.

Piranha just starts a monitor process, one per service (which is defined as a n
address and port number), and monitors that service. If the service goes down,
piranha removes it's definition, if it comes back, it's re-added. There are
PLENTY of ipvsadm commands you could create that cannot be mapped into piranha.
ipvs is a generic ip routing filter that can include wildcards, piranha is just
an individual service monitor.

Port 0 is a wildcard port. Piranha cannot start a monitor that means "all
ports". It can only monitor (or connect to or read from) a single port. How
could it monitor "all ports"? It has no information about any client connection
attempts, and certainly it should not start 65535 nanny daemons.

You have to define each service individually.