[PUP-9240] Solaris SMF service has to support non global zone Created: 2018/10/16 Updated: 2019/12/12 Resolved: 2018/12/20
|Fix Version/s:||PUP 5.5.10, PUP 6.0.5, PUP 6.1.0|
|Reporter:||Karthikeyan Kanagaraj||Assignee:||Enis Inan|
|Labels:||customer, resolved-issue-added, service, solaris, type_and_provider|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
Other than generic.xml, need to check either service or related-package installed on that machine to confirm that service can bring up or stop using puppet.
|Sprint:||Platform OS Kanban|
|Zendesk Ticket IDs:||32270|
|Zendesk Ticket Count:||1|
|Release Notes:||Bug Fix|
|Release Notes Summary:||The SMF provider can now distinguish between complete/incomplete services on Solaris 11.1+. An incomplete service will have the same semantics as a nonexistent service. Specifically, Puppet will report its state as ensure => stopped and enabled => false, and it will raise an error if one attempts to set ensure => running or enabled => true on the service.|
|QA Risk Assessment:||Needs Assessment|
Solaris SMF service has to support the non-global zone. Currently, SMF service-check refers the generic.xml file only. If that service entry is there in that file it will check the status.
In Solaris 11, non-global zone servers have few services name which is listed in generic.xml but related packages/services are not installed on that zone. So when puppet code checks the status, OS is not giving any output and service is failing with an error.
Error: /Stage[main]/Main/Service[hal]: Could not evaluate: Unmanageable state '' on service hal
Recreate Reproduce steps :
-Install zone on Solaris 11.3 machine
This will fail, looking like this:
|Comment by Kenn Hussey [ 2018/12/19 ]|
Enis Inan can this be resolved now?