| Summary: | lldpad initscript does not kill lldpad before starting it | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Eric Multanen <eric.w.multanen> | ||||
| Component: | lldpad | Assignee: | Petr Šabata <psabata> | ||||
| Status: | CLOSED ERRATA | QA Contact: | qe-baseos-daemons | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 6.3 | CC: | asersen, azelinka, hui.xiao, jack.morgan, jane.lv, john.r.fastabend, john.ronciak, jpallich, jvillalo, jwilleford, kavindya.s.deegala, luyu, robert.w.love, yi.zou | ||||
| Target Milestone: | rc | Keywords: | EasyFix, Patch, ZStream | ||||
| Target Release: | 6.3 | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | lldpad-0.9.43-13.el6 | Doc Type: | Bug Fix | ||||
| Doc Text: |
The lldpad tool is initially invoked by initrd during the boot process to support Fibre Channel over Ethernet (FCoE) boot from a Storage Area Network (SAN). The runtime lldpad init script did not kill lldpad before restarting it after system boot. Consequently, lldpad could not be started normally after system boot. With this update, the lldpad init script now contains the "-k" option to terminate the first instance of lldpad that was started during system boot.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-06-20 14:14:45 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Bug Depends On: | 813952 | ||||||
| Bug Blocks: | 820002, 822377 | ||||||
| Attachments: |
|
||||||
Created attachment 549025 [details]
Kill lldpad before starting it
Tagged as lldpad-0_9_43-13_el6 RHEL 6.3 BZ 813952 blocks retesting this BZ with RHEL 6.3 Alpha. Intel has not verified this BZ because we are blocked on 813952. Should we keep this in a VERIFIED state? We were looking for this in 6.2. It's a problem for boot because the initrd lldpad isn't killed when the runtime one comes online by way of the init script. This is a problem for certifications that require us to test on hosts that are booted off of FCoE LUNs. Problems arise when there are two lldpad instances running and the certification suite requires lldp re-configuration. The system becomes unreliable becuase there are two lldpad daemons trying to manage the same system. Just to be clear. I am requresting that we get this fix into 6.2.z because it blocks certification.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
The lldpad tool is initially invoked by initrd during the boot process to support Fibre Channel over Ethernet (FCoE) boot from a Storage Area Network (SAN). The runtime lldpad init script did not kill lldpad before restarting it after system boot. Consequently, lldpad could not be started normally after system boot. With this update, the lldpad init script now contains the "-k" option to terminate the first instance of lldpad that was started during system boot.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0901.html Verified by Intel. |
Description of problem: lldpad is initially invoked from initrd during boot to support FCoE boot from SAN. The runtime initscript should kill this instance of lldpad by invoking 'lldpad -k' before starting up lldpad normally ('lldpad -d'). This functionality is present in the RHEL6.1 initscript but is not longer present in RHEL6.2. How reproducible: always Steps to Reproduce: 1. Enable and Configure FCoE Boot Option Rom to Boot From LUN 2. Install RHEL6.2 on LUN 3. On successful boot, check status of lldpad service. Actual results: Something like the following will appear during startup: Starting lldpad: bind(AF_LOCAL): Address already in use [FAILED] Expected results: Starting lldpad: [ OK ] Additional info: