Bug 912933

Summary:	Start /etc/init.d/rpcbind service failed after upgrade from 6.4 Sanpshot 4(20130116.3.0.el6) to latest 6.4(20130214.0)
Product:	Red Hat Enterprise Linux 6	Reporter:	haiyang,dong <hadong>
Component:	ovirt-node	Assignee:	Fabian Deutsch <fdeutsch>
Status:	CLOSED DUPLICATE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.4	CC:	acathrow, bsarathy, chchen, cshao, gouyang, hadong, jboggs, leiwang, mburns, ovirt-maint, ycui
Target Milestone:	rc	Keywords:	TestOnly
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-04-08 12:50:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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 ***