Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-6785

Service start unit tests fail on Solaris

    Details

    • Type: Bug
    • Status: Accepted
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Environment:

      4.7.0
      Oracle Corporation SunOS 5.12 s12_109 September 2016

    • Template:
    • Team:
      Platform OS

      Description

      Specs for both the init provider and Openwrt fail on Solaris as the command invocation includes Solaris specific capabilities such as ctrun

      spec './spec/unit/provider/service/init_spec.rb[1:4:2:1]' # Puppet::Type::Service::ProviderInit if the init script is present when running start should use any provided explicit command
      rspec './spec/unit/provider/service/init_spec.rb[1:4:2:2]' # Puppet::Type::Service::ProviderInit if the init script is present when running start should pass start to the init script when no explicit command is provided
      rspec './spec/unit/provider/service/openwrt_spec.rb[1:7:1]' # Puppet::Type::Service::ProviderOpenwrt when running start should use any provided explicit command
      rspec './spec/unit/provider/service/openwrt_spec.rb[1:7:2]' # Puppet::Type::Service::ProviderOpenwrt when running start should execute the init script with start when no explicit command is provided
      

           Mocha::ExpectationError:
             unexpected invocation: #<Puppet::Type::Service::ProviderOpenwrt:0x56b9338>.execute('/usr/bin/ctrun -l none /user/specified/command', {:failonfail => true, :override_locale => false, :squelch => false, :combine => true})
             unsatisfied expectations:
             - expected exactly once, not yet invoked: #<Puppet::Type::Service::ProviderOpenwrt:0x56b9338>.execute()
      

        Attachments

          Activity

            jsd-sla-details-panel

              People

              • Assignee:
                Unassigned
                Reporter:
                shawnferry Shawn Ferry
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Zendesk Support