QA:Testcase adcli info readonly

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Update category)
(Update adcli links)
 
Line 2: Line 2:
 
|description=This test case verifies that <code>adcli info</code> correctly identifies domain controllers it cannot use.
 
|description=This test case verifies that <code>adcli info</code> correctly identifies domain controllers it cannot use.
 
|setup=
 
|setup=
# Make sure to complete the [[QA:Testcase_adcli:Prerequisites|prerequisites before starting this test]].
+
# Make sure to complete the [[QA:Testcase_adcli_setup|prerequisites before starting this test]].
 
# No domain credentials are needed for this test.
 
# No domain credentials are needed for this test.
 
# You'll need a domain with a read-only domain controller.
 
# You'll need a domain with a read-only domain controller.
Line 22: Line 22:
 
* Use the <code>--verbose</code> argument to provide output when troubleshooting or reporting bugs.
 
* Use the <code>--verbose</code> argument to provide output when troubleshooting or reporting bugs.
  
[[Category:Active_Directory_Test_Cases]]
+
[[Category:Active_Directory_Test_Cases]] [[Category:adcli_Test_Cases]]

Latest revision as of 10:43, 10 April 2013

Contents

Description

This test case verifies that adcli info correctly identifies domain controllers it cannot use.

Setup

  1. Make sure to complete the prerequisites before starting this test.
  2. No domain credentials are needed for this test.
  3. You'll need a domain with a read-only domain controller.

How to test

  1. Run adcli to get info for the read-only domain controller:
    $ adcli info --domain-controller=read-only.domain.example.com

Expected Results

The output should contain the following line.

domain-controller-usable = no

In addition the writable flag should not be present on the domain-controller-flags line.



Troubleshooting

  • Use the --verbose argument to provide output when troubleshooting or reporting bugs.