Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 949001

Summary:	OSAD Service Shows as Masked - Cannot Start
Product:	[Community] Spacewalk	Reporter:	timbrammer910
Component:	Clients	Assignee:	Milan Zázrivec <mzazrivec>
Status:	CLOSED NOTABUG	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	1.9	CC:	jpazdziora
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-04-09 18:33:59 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1484117

Description timbrammer910 2013-04-05 15:50:59 UTC

Description of problem:
I'm having trouble getting OSAD started on Fedora 18. When running # systemctl status osad, it shows as loaded, but masked in /usr/lib/systemd/system/. Listing that directory shows now sym to /dev/null though. Despite this, I still ran # systemctl start osad, and was greeted with "Failed to issue method call: Unit osad.service is masked.

Version-Release number of selected component (if applicable):
osad-5.11.18-1.fc18.noarch

How reproducible:

Install and attempt to start osad

Steps to Reproduce:
1.yum install osad
2.systemctl start osad
3.
  
Actual results:
osad.service is masekd

Expected results:
osad starts

Additional info:

I've utilized the info here: https://fedorahosted.org/spacewalk/wiki/OsadHowTo

but have so far been unsuccessful. running # /usr/sbin/osad -N -v -v -v -v returns nothing. I've also attempted to run # systemctl unmask osad which also returns nothing.

Comment 1 timbrammer910 2013-04-05 16:25:17 UTC

Update:

Copying osad.service to osad1.service, running # systemctl reload-daemon and starting osad1 works. So the issue isn't with osad per se, but perhaps the way the service is added/created?

Comment 2 Jan Pazdziora (Red Hat) 2013-04-09 13:23:06 UTC

(In reply to comment #0)
> Description of problem:
> I'm having trouble getting OSAD started on Fedora 18. When running #
> systemctl status osad, it shows as loaded, but masked in
> /usr/lib/systemd/system/.

Can you show the exact output you get?

> Listing that directory shows now sym to /dev/null
> though.

Can you show the output of that ls command?

Comment 3 timbrammer910 2013-04-09 18:33:59 UTC

Jan,

You can close this, sorry for not following up.

I've been unable to reproduce it after modifying my kickstart script to enable to service.

Thank you for your response.

Comment 4 Eric Herget 2017-09-28 18:06:57 UTC

This BZ closed some time during 2.5, 2.6 or 2.7.  Adding to 2.7 tracking bug.