RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
When running authconfig as part of firstboot, there's a whole list of services which get conditionally restarted via "service <service> condrestart" That's all fine and dandy except it appears that vncserver decided that "condrestart" was too complicated and that "try-restart" made more sense (although they both call identical code!)  Anyway, net result is that firstboot spits out a message when the vncserver gets conditionally restarted, "condrestart is obsolete, use try-restart instead"  It's completely insane to have to special case vncserver, but the other choice is carting around a patch to vncserver to remove the error.  I fear that down the road the "condrestart" stanza will go away leaving us in a position where the vncserver doesn't get restarted.

Version-Release number of selected component (if applicable):
5.4.10-1.fc11

How reproducible:
Always

Steps to Reproduce:
1. Run firstboot and launch the authconfig dialog
2. Click "OK" to continue
OR
1. Run "authconfig-gtk --firstboot" (same thing that firstboot does)
2. Click "OK" to continue
  
Actual results:
Will get an error on the terminal

Expected results:
vncserver gets called with "try-restart" instead of "condrestart"

Adam, would it be possible to remove the error message?

I don't think we will start to remove condrestart from the init scripts any time soon and try-restart is unfortunately not yet implemented by all the init scripts called by authconfig.

(In reply to comment #1)
> Adam, would it be possible to remove the error message?

Fixed in tigervnc-0.0.91-0.13.fc12.1

> I don't think we will start to remove condrestart from the init scripts any
> time soon and try-restart is unfortunately not yet implemented by all the init
> scripts called by authconfig.

Fix confirmed with 1.0.0-1.el6.x86_64.