Comment 15 for bug 2027613

In the process of verification testing, I discovered a gap in my previous testing: I never tested simply installing the new version of the package and running `landscape-config`.

Unfortunately `landscape-config` relies on starting the service to register and cannot because of the new ExecCondition, which requires registration to already have happened! I can think of a few different ways to resolve this:

  1. restructure `landscape-config` so that it doesn't need to start the service to register (nontrivial amount of work)
  2. modify `landscape-config --is-registered` so that it is aware that we are currently in the `landscape-config` wizard
  3. change the ExecCondition to something like
     /usr/bin/landscape-config --is-registered || ! systemctl is-active landscape-client.service
     so that we can also start the service when it is manually enabled, such as the case where we are not registered but `landscape-config` is being run