#9591 ipa-replica-manage clean-dangling-ruv is failing to handle invalid RUVs
Closed: fixed 8 months ago by frenaud. Opened 8 months ago by mreynolds.

Issue

There were obsolete RUVs that we've tried to clean with ipa-replica-manage clean-dangling-ruv
Some RUVs were invalid ( no LDAP URL ).
The command was failing when trying to handle those invalid RUVs

ipa-replica-manage clean-dangling-ruv
Directory Manager password:
unable to decode:

{replica 75} 62efab610000004b0000 62efab610000004b0000
unable to decode: {replica 88} 63f22f65000300580000 63f234ec000000580000
unable to decode: {replica 73} 62ebd06c000000490000 62ebd0ab000100490000
unable to decode: {replica 75}

Steps to Reproduce

Unknown


Metadata Update from @mreynolds:
- Issue assigned to mreynolds

8 months ago

master:

  • 544652a Issue 9591 - Allow get_ruv() to handle incomplete RUV elements

ipa-4-11:

  • d5a842d Issue 9591 - Allow get_ruv() to handle incomplete RUV elements

ipa-4-10:

  • 888c695 Issue 9591 - Allow get_ruv() to handle incomplete RUV elements

ipa-4-9:

  • 5ff1f59 Issue 9591 - Allow get_ruv() to handle incomplete RUV elements

Metadata Update from @frenaud:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

8 months ago

Metadata Update from @frenaud:
- Custom field rhbz adjusted to https://issues.redhat.com/browse/RHEL-6215

8 months ago

There is a nightly failure in test_integration/test_ipahealthcheck.py::TestIpaHealthCheck::test_ipa_healthcheck_ds_ruv_check possibly related to this issue:
[testing_master_latest] Nightly PR #3690

These tests are failing around list_ruv(), but I added to code to make sure list_ruv(strict=True) was not significantly impacted by my change.

I can not tell if this same test was done in the github PR:

https://github.com/freeipa/freeipa/pull/7342/checks?check_run_id=24904190896

But I am going to look into it...

I filed https://pagure.io/freeipa/issue/9598 for the regression and fixed in https://github.com/freeipa/freeipa/pull/7370. The problem was that ipa-replica-manage list-ruvs was displaying only a short hostname instead of fqdn:port.

Log in to comment on this ticket.

Metadata