Bug 1498968

Summary:	Scheduled database backups do not work on the podified version of CFME
Product:	Red Hat CloudForms Management Engine	Reporter:	Peter McGowan <pmcgowan>
Component:	cfme-openshift-app	Assignee:	Franco Bladilo <fbladilo>
Status:	CLOSED ERRATA	QA Contact:	Ievgen Zapolskyi <izapolsk>
Severity:	high	Docs Contact:	Red Hat CloudForms Documentation <cloudforms-docs>
Priority:	high
Version:	5.8.0	CC:	abellott, bazulay, fbladilo, izapolsk, jhardy, jkrocil, obarenbo, simaishi, smallamp
Target Milestone:	GA	Keywords:	ZStream
Target Release:	5.8.3	Flags:	izapolsk: automate_bug+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	5.8.3.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-28 12:32:22 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:
Bug Depends On:	1540957
Bug Blocks:

Description Peter McGowan 2017-10-05 16:37:36 UTC

Description of problem:
Scheduled database backups do not work on the podified version of CFME

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

How reproducible:
Every time


Steps to Reproduce:
1. Create a scheduled task to backup the database to NFS storage

Actual results:

When the schedule runs, the backup fails as the NFS storage cannot be mounted:

[----] E, [2017-08-11T15:20:28.701423 #84024:35d130] ERROR -- : MIQ(MiqNfsSession-connect) Connecting to host: [lonindapfp5.uk.db.com], share: [/var/nfs/ose-pv-100] encountered error: [RuntimeError] [Job for rpc-statd.service failed because the control process exited with error code. See "systemctl status rpc-statd.service" and "journalctl -xe" for details.
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified
].../opt/rh/cfme-gemset/bundler/gems/manageiq-gems-pending-8f7d63f441d5/lib/gems/pending/util/mount/miq_generic_mount_session.rb:42:in `runcmd'
/opt/rh/cfme-gemset/bundler/gems/manageiq-gems-pending-8f7d63f441d5/lib/gems/pending/util/mount/miq_generic_mount_session.rb:28:in `runcmd'
/opt/rh/cfme-gemset/bundler/gems/manageiq-gems-pending-8f7d63f441d5/lib/gems/pending/util/mount/miq_nfs_session.rb:31:in `mount_share'
/opt/rh/cfme-gemset/bundler/gems/manageiq-gems-pending-8f7d63f441d5/lib/gems/pending/util/mount/miq_generic_mount_session.rb:137:in `connect'
/opt/rh/cfme-gemset/bundler/gems/manageiq-gems-pending-8f7d63f441d5/lib/gems/pending/util/mount/miq_nfs_session.rb:12:in `connect'
/opt/rh/cfme-gemset/bundler/gems/manageiq-gems-pending-8f7d63f441d5/lib/gems/pending/util/mount/miq_generic_mount_session.rb:57:in `new_session'
/var/www/miq/vmdb/lib/evm_database_ops.rb:48:in `backup'
/var/www/miq/vmdb/app/models/database_backup.rb:51:in `_backup'
/var/www/miq/vmdb/app/models/database_backup.rb:35:in `backup'
/var/www/miq/vmdb/app/models/database_backup.rb:12:in `backup'
/var/www/miq/vmdb/app/models/miq_queue.rb:347:in `block in deliver'


Expected results:

The backup completes successfully


Additional info:

Comment 2 Franco Bladilo 2017-10-05 17:33:19 UTC

I could reproduce this issue, NFS v3 negotiated mounts need locking assistance from lockd/statd. This service is automatically called by "mount" but it is unable to register itself with the portmapper (rpcbind) as it is not running on the image.

The fix is here : 

https://github.com/ManageIQ/manageiq-pods/pull/231

Comment 3 Ievgen Zapolskyi 2018-02-05 17:19:29 UTC

It is blocked by 1540957. The issue with set_passwords exists in 5.8.3.2 as well.

Comment 4 Ievgen Zapolskyi 2018-02-20 15:19:15 UTC

Verified in 5.8.3.3.20180208212148_8efa813

Comment 8 errata-xmlrpc 2018-02-28 12:32:22 UTC

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.

https://access.redhat.com/errata/RHBA-2018:0373