Bug 1037894

Summary: rhevm-manage-domains fails to update ldapServers entries when using action=edit
Product: Red Hat Enterprise Virtualization Manager Reporter: Yair Zaslavsky <yzaslavs>
Component: ovirt-engine-configAssignee: Yair Zaslavsky <yzaslavs>
Status: CLOSED ERRATA QA Contact: Ondra Machacek <omachace>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.3.0CC: aberezin, acathrow, emesika, iheim, mkalinin, oourfali, pstehlik, Rhev-m-bugs, scohen, yeylon, yzaslavs
Target Milestone: ---   
Target Release: 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: is28 Doc Type: Bug Fix
Doc Text:
Previously, using the rhevm-manage-domains action=edit command for LDAP servers did not work as the changes were not stored at the proper location at the vdc_options table. This fix specifies the correct location for storing the changes, so edits to the LDAP server can be made using the rhevm-manage-domains tool.
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-21 17:39:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1049022    

Description Yair Zaslavsky 2013-12-04 02:28:49 UTC
Description of problem:

When a user wants to update entries previously set by -ldapServers, using -ldapServers=<new_value> and action=edit , the update does not take place.



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


How reproducible:

1. Use rhevm-manage-domains and add a domain, provide -ldapServers=<value> where value is a list (or single) of ldap servers
2. Use rhevm-manage-domains with action=edit, and change -ldapServers to a different value - the value is not changed at vdc_options table (select * from vdc_options where option_name ilike '%ldapservers%' will show you the previous list).

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Yair Zaslavsky 2013-12-04 02:30:39 UTC
Sorry for not providing actual results -
The actual results are the info on the ldap server list is not stored.
The expected results are to have the info stored.

Comment 3 Marina Kalinin 2013-12-09 16:28:10 UTC
How to confirm that edit command actually updated in the system?
1. Check entry in the database:
 engine=> select option_value from vdc_options where option_name='LdapServers';
See if the list of servers was updated.
2. Check /etc/ovirt-engine/krb5.conf, realms section should contain the list of servers, similar to this:
~~~
 [realms]
	LDAP1.EXAMPLE.COM = {
		kdc = ldap1.example.com
	}
~~~

BTW, why are we using /etc/ovirt-engine/krb5.conf and not /etc/krb5.conf ?
It is quite confusing.
People tend to edit the second file, which probably does not make any effect on the system.

Comment 4 Marina Kalinin 2013-12-09 17:06:58 UTC
Yair, sorry for confusion, but reviewing all the other relevant bugs, I see that they are fixed for 3.3.0.
https://bugzilla.redhat.com/show_bug.cgi?id=985623
https://bugzilla.redhat.com/show_bug.cgi?id=973566

I request this to be pushed to 3.3.0 as well (and not 3.3.z), so that the customer would be able to get all the fixes in GA.
And if anything would not work, we will report and fix in 3.3.z.

Comment 5 Yair Zaslavsky 2013-12-09 23:31:42 UTC
We're using our own krb5.conf file, so our setup will be as much as isolated .
/etc/krb5.conf file is like a "global" kerberos configuration file.

Comment 6 Ondra Machacek 2014-01-06 15:08:35 UTC
Ok in is30.

After running -action=edit with -ldapServers argument, vdc_options table 
and /etc/ovirt-engine/krb5.conf file are accordingly updated.

Comment 7 errata-xmlrpc 2014-01-21 17:39:42 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.

http://rhn.redhat.com/errata/RHSA-2014-0038.html