search

MiamiOH / puppet-duo_authproxy

Installs and configures Duo Authentication Proxy
GNU General Public License v3.0
1 stars 6 forks source link

Archive not extracted #18

Open oscar-vlugt opened 4 years ago

oscar-vlugt commented 4 years ago

Using CentOS 7, and using puppet/archive 4.6.0. Unable to get through this step when deploying my duo auth proxy. 

Notice: /Stage[main]/Duo_authproxy::Install/Archive[/tmp/duoauthproxy-2.7.0-src.tgz]/creates: creates changed 'archive not extracted' to extracting in /tmp to create /opt/duoauthproxy/2.7.0 (corrective)

Notice: /Stage[main]/Duo_authproxy::Install/Exec[duoauthproxy-move]/returns: mv: cannot move ‘duoauthproxy-2.7.0-src’ to a subdirectory of itself, ‘duoauthproxy-2.7.0-src/duoauthproxy-2.7.0-src’

Error: 'mv duoauthproxy-2.7.0*-src duoauthproxy-2.7.0-src' returned 1 instead of one of [0]

Error: /Stage[main]/Duo_authproxy::Install/Exec[duoauthproxy-move]/returns: change from 'notrun' to ['0'] failed: 'mv duoauthproxy-2.7.0*-src duoauthproxy-2.7.0-src' returned 1 instead of one of [0] (corrective)

Notice: /Stage[main]/Duo_authproxy::Install/Exec[duoauthproxy-make]: Dependency Exec[duoauthproxy-move] has failures: true

Warning: /Stage[main]/Duo_authproxy::Install/Exec[duoauthproxy-make]: Skipping because of failed dependencies

Warning: /Stage[main]/Duo_authproxy::Install/Exec[duoauthproxy-install]: Skipping because of failed dependencies

Warning: /Stage[main]/Duo_authproxy::Install/Exec[duoauthproxy-tag]: Skipping because of failed dependencies

Info: Class[Duo_authproxy::Install]: Unscheduling all events on Class[Duo_authproxy::Install]

Warning: /Stage[main]/Duo_authproxy::Config/File[authproxy.cfg]: Skipping because of failed dependencies

Warning: /Stage[main]/Duo_authproxy::Service/Service[duoauthproxy]: Skipping because of failed dependencies

Am I missing a crucial thing?

edestecd commented 4 years ago

https://github.com/MiamiOH/puppet-duo_authproxy/blob/master/manifests/install.pp#L26

Thats prob the culprit. idk why though

edestecd commented 4 years ago

They may have changed the naming. I think the folder in the archive used to have a build number where the * is and we wanted to remove that so it was predictable for us

edestecd commented 4 years ago

mv is now unhappy that the source and destination are the same. We might try simply removing that mv or changing it slightly to make mv happy