RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 912933 - Start /etc/init.d/rpcbind service failed after upgrade from 6.4 Sanpshot 4(20130116.3.0.el6) to latest 6.4(20130214.0)
Summary: Start /etc/init.d/rpcbind service failed after upgrade from 6.4 Sanpshot 4(20...
Keywords:
Status: CLOSED DUPLICATE of bug 902677
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Fabian Deutsch
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-20 02:46 UTC by haiyang,dong
Modified: 2013-04-08 12:50 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-08 12:50:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description haiyang,dong 2013-02-20 02:46:05 UTC 
Description of problem:
After upgrade from 6.4 Sanpshot 4(20130116.3.0.el6) to latest 6.4(20130214.0),
Start /etc/init.d/rpcbind service failed.

[root@dhcp-11-209 admin]# service rpcbind start
Starting rpcbind:                                          [  OK  ]
[root@dhcp-11-209 admin]# service rpcbind status
rpcbind dead but pid file exists
[root@dhcp-11-209 admin]# /etc/init.d/rpc
rpcbind     rpcgssd     rpcidmapd   rpcsvcgssd  


no this issue when clean install rhev-hypervisor6-6.4-20130214.0.el6 and Start /etc/init.d/rpcbind service.

Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.4-20130214.0.el6

How reproducible:
100%

Steps to Reproduce:
1. Install rhev-h 6.4 Sanpshot 4(20130116.3.0.el6)
3. Upgrade to latest 6.4 build (rhev-hypervisor6-6.4-20130214.0.el6).
4. Start /etc/init.d/rpcbind service.

Actual results:
Start /etc/init.d/rpcbind service failed after upgrade from 6.4 Sanpshot 4(20130116.3.0.el6) to latest 6.4(20130214.0)

Expected results:
After upgrade from 6.4 Sanpshot 4(20130116.3.0.el6) to latest 6.4(20130214.0), Start /etc/init.d/rpcbind service should success.

Additional info:
--
Comment 2 haiyang,dong 2013-02-20 04:09:34 UTC 
Also no this issue when upgrade from RHEV-H 6.3 Update 8 Respin 1 (6.3-20130129.0) to latest 6.4(20130214.0), and Start /etc/init.d/rpcbind service success.
Comment 4 Fabian Deutsch 2013-04-08 09:54:53 UTC 
Haiyang,

this bug has the same cause as bug 902677. The fix for this landed in ovirt-node-2.5.0-16.el6 - that means one of your builds (20130116.3.0.el6) didn't contain rpcbind.

I've tested an upgrade from:
rhev-hypervisor6-6.4-20130306.2.iso with ovirt-node-2.5.0-17.el6
to
rhev-hypervisor6-6.4-20130318.1.iso with ovirt-node-2.5.0-17.el6_4.1

(Both builds contained rpcbind/the fix for bug 902677)

And rpcbind seems to be working:

$ /etc/init.d/rpcbind status
rpcbind (pid 3910) is running...

Does an upgrade from the two versions above also work for you?
Comment 5 Fabian Deutsch 2013-04-08 09:56:40 UTC 
Tested as follows:

1. Install rhev-hypervisor6-6.4-20130306.2.iso with ovirt-node-2.5.0-17.el6
2. Configure networking w/ dhcp
3. Run /etc/init.d/rpcbind status (result: running)

4. Upgrade to/with rhev-hypervisor6-6.4-20130318.1.iso with ovirt-node-2.5.0-17.el6_4.1
5. Run /etc/init.d/rpcbind status (result: running)
Comment 6 haiyang,dong 2013-04-08 10:50:38 UTC 
(In reply to comment #4)
> Haiyang,
> 
> this bug has the same cause as bug 902677. The fix for this landed in
> ovirt-node-2.5.0-16.el6 - that means one of your builds (20130116.3.0.el6)
> didn't contain rpcbind.
> 
> I've tested an upgrade from:
> rhev-hypervisor6-6.4-20130306.2.iso with ovirt-node-2.5.0-17.el6
> to
> rhev-hypervisor6-6.4-20130318.1.iso with ovirt-node-2.5.0-17.el6_4.1
> 
> (Both builds contained rpcbind/the fix for bug 902677)
> 
> And rpcbind seems to be working:
> 
> $ /etc/init.d/rpcbind status
> rpcbind (pid 3910) is running...
> 
> Does an upgrade from the two versions above also work for you?

there are two scenarios:
scenario 1:
1. Install rhev-h 6.4 Sanpshot 4(20130116.3.0.el6)
2. Configure networking w/ dhcp
3. Run /etc/init.d/rpcbind status (result: failed)
4. Upgrade to/with rhev-hypervisor6-6.4-20130318.1.iso
5. Run /etc/init.d/rpcbind status (result:failed-rpcbind dead but pid file exists )

scenario 2:
1. Install rhev-hypervisor6-6.4-20130306.2.iso 
2. Configure networking w/ dhcp
3. Run /etc/init.d/rpcbind status (result: running)
4. Upgrade to/with rhev-hypervisor6-6.4-20130318.1.iso
5. Run /etc/init.d/rpcbind status (result: running)

For scenario 1, it means that boot the updated version and start /etc/init.d/rpcbind service should success after upgrade from rhev-hypervisor6-6.4-20130116.3.0.el6(rpcbind didnt' work) to rhev-hypervisor6-6.4-20130318.1.iso(rpcbind can work), but actually it failed.

should we support scenario 1? As i know, the customer could get the version "rhev-h 6.4 Sanpshot 4(20130116.3.0.el6)", if they want to upgrade it to rhev-hypervisor6-6.4-20130318.1.iso ,and boot rhev-hypervisor6-6.4-20130318.1.iso,
then they will meet "run /etc/init.d/rpcbind" failed issue.
Comment 7 Mike Burns 2013-04-08 12:50:56 UTC 
(In reply to comment #6)

> 
> should we support scenario 1? As i know, the customer could get the version
> "rhev-h 6.4 Sanpshot 4(20130116.3.0.el6)", if they want to upgrade it to
> rhev-hypervisor6-6.4-20130318.1.iso ,and boot
> rhev-hypervisor6-6.4-20130318.1.iso,
> then they will meet "run /etc/init.d/rpcbind" failed issue.

Snapshot 4 (20130116.3.0.el6) did not work with RHEV-M.  Also, upgrades from beta/pre-ga to ga is not supported officially.  It is highly unlikely that anyone is using it.  I think that the effort needed to solve this bug for an unsupported case that few if any people will hit is not worth it.  

Closing as a duplicate of the rpcbind bug.

*** This bug has been marked as a duplicate of bug 902677 ***
Note You need to log in before you can comment on or make changes to this bug.