Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.8.0
    • Fix Version/s: 1.0.0
    • Component/s: deployment
    • Labels:
      None

      Description

      Once BIGTOP-1047 is committed, let's fix the leftover warnings

      1. BIGTOP-1508.1.patch
        2 kB
        Evans Ye
      2. BIGTOP-1508.2.patch
        3 kB
        Evans Ye

        Issue Links

          Activity

          Hide
          evans_ye Evans Ye added a comment -

          The patch fixed the leftover warnings in BIGTOP-1047 instead of the below one:

          ==> bigtop1: Warning: The use of 'import' is deprecated at /tmp/vagrant-puppet-2/manifests/site.pp:46. See http://links.puppetlabs.com/puppet-import-deprecation
          ==> bigtop1:    (at /usr/lib/ruby/site_ruby/1.8/puppet/parser/parser_support.rb:110:in `import')
          

          The 'import warning" can also be fixed by doing following steps:

          • remove import "cluster.pp" in line 44, site.pp
          • specify a directory as your main manifest when doing puppet apply. i.e.
            puppet apply -d --modulepath="bigtop-deploy/puppet/modules:/etc/puppet/modules" bigtop-deploy/puppet/manifests/
            

          Since the the way to specify directory as manifest is currently not supported by Vagrant yet, changing the behavior will break vagrant-puppet provisioner.
          I think the gradew bundler for puppet apply that Konstantin Boudnik mentioned in mailing list can come to a rescue.
          Once the feature implemented, I'll update the vagrant-puppet and docker-puppet to use the bundler subsequently.

          Show
          evans_ye Evans Ye added a comment - The patch fixed the leftover warnings in BIGTOP-1047 instead of the below one: ==> bigtop1: Warning: The use of ' import ' is deprecated at /tmp/vagrant-puppet-2/manifests/site.pp:46. See http: //links.puppetlabs.com/puppet- import -deprecation ==> bigtop1: (at /usr/lib/ruby/site_ruby/1.8/puppet/parser/parser_support.rb:110:in ` import ') The 'import warning" can also be fixed by doing following steps: remove import "cluster.pp" in line 44, site.pp specify a directory as your main manifest when doing puppet apply. i.e. puppet apply -d --modulepath= "bigtop-deploy/puppet/modules:/etc/puppet/modules" bigtop-deploy/puppet/manifests/ Since the the way to specify directory as manifest is currently not supported by Vagrant yet, changing the behavior will break vagrant-puppet provisioner. I think the gradew bundler for puppet apply that Konstantin Boudnik mentioned in mailing list can come to a rescue. Once the feature implemented, I'll update the vagrant-puppet and docker-puppet to use the bundler subsequently.
          Hide
          cos Konstantin Boudnik added a comment -

          Looks good to my semi-n00b Puppet user eye. +1 from me.

          Show
          cos Konstantin Boudnik added a comment - Looks good to my semi-n00b Puppet user eye. +1 from me.
          Hide
          evans_ye Evans Ye added a comment -

          cool cos!
          Committed

          Show
          evans_ye Evans Ye added a comment - cool cos! Committed

            People

            • Assignee:
              evans_ye Evans Ye
              Reporter:
              cos Konstantin Boudnik
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development