Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

V2 #78

Merged
merged 8 commits into from
Sep 5, 2017
Merged

V2 #78

merged 8 commits into from
Sep 5, 2017

Conversation

ghoneycutt
Copy link
Owner

No description provided.

@ghoneycutt
Copy link
Owner Author

@Phil-Friderici Having a hard time getting the installation to happen without intervention on Solaris, even though I'm providing an adminfile. Any ideas?

@ghoneycutt
Copy link
Owner Author

Fixes #77

@ghoneycutt
Copy link
Owner Author

Need to address #50 before merging. This is to remove inheritance.

@ghoneycutt ghoneycutt mentioned this pull request Aug 30, 2017
@ghoneycutt
Copy link
Owner Author

Fixes #32

@ghoneycutt
Copy link
Owner Author

Fixes #42

@Phil-Friderici
Copy link
Contributor

Let's try to get @nalyanyam onboard, he is our Solaris'n'Puppet specialist.
@nalyanyam hope you have some time to help :)

@nalyanyam
Copy link
Contributor

Installation on which Solaris release? 10 or 11?
Solaris 10 should already be having the packages installed as part of the base OS. Probably what's causing the puppet not to detect the installed packages is the package provider.
By default Solaris 10 uses the legacy provider "sun" while Solaris 11 uses the provider "pkg" and for Solaris 11 it's not necessary to provide adminfile as long as the repositories are properly configured.

@ghoneycutt
Copy link
Owner Author

Hi @nalyanyam

The issue is not with nfs, but with the testing framework. I'm attempting to install puppet enterprise and that package is prompting for user input. The goal is that you can do vagrant up with the solaris10-client and solaris11-client systems without any user input, like the other platforms.

Check out theses two lines from the vagrant/provision_solaris.sh script.

https://github.com/ghoneycutt/puppet-module-nfs/pull/78/files#diff-efcf01caa4c8308a3dc28fd70070310bR46

https://github.com/ghoneycutt/puppet-module-nfs/pull/78/files#diff-efcf01caa4c8308a3dc28fd70070310bR50

@nalyanyam
Copy link
Contributor

@ghoneycutt
The correct command syntax is something like below:
pkgadd -n -a /var/sadm/install/admin/puppet -d /vagrant/.puppetagents/${pkg} all

This assumes that ${pkg} is a datastream package. And the adminfile should also be ok.
The original syntax assumed a device instead of a package. Please see below notes from the man page.
Please test and let me know in case that fails

From man page:

By default, pkgadd looks in the /var/spool/pkg directory
when searching for instances of a package to install or
spool. Optionally, the source for the package instances to
be installed or spooled can be specified using:

 -d device
 -d datastream pkgname,... | all

@nalyanyam
Copy link
Contributor

Remove support for Puppet 3 and the various ruby versions. Since Puppet
uses the AIO (all in one) installer with a packaged ruby, this module
will support the ruby version that is released with that version of
Puppet.

Remove support for the following platforms which are end of life.

* Debian 6
* EL 5
* Suse 10
* Ubuntu 12.04 LTS
This refactor is needed to prevent nfs::server from inheriting a
parameterized class.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants