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

Please actually implement skip_verify for archive.extracted #34515

Closed
vernondcole opened this issue Jul 7, 2016 · 3 comments
Closed

Please actually implement skip_verify for archive.extracted #34515

vernondcole opened this issue Jul 7, 2016 · 3 comments
Labels
Bug broken, incorrect, or confusing behavior Core relates to code central or existential to Salt fixed-pls-verify fix is linked, bug author to confirm fix P3 Priority 3 severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around State-Module
Milestone

Comments

@vernondcole
Copy link
Contributor

Description of Issue/Question

When I do not define an upstream hash for archive.extracted, Salt provides an error message suggesting that I use a "skip_verify" switch.

That switch does not exist.

Setup

Virtualbox published an invalid checksum, so I want to ignore it this time...

vagrant-sdk:
  archive:
    - extracted
    - name: /opt/virtualbox/5.0.24
    - source: http://download.virtualbox.org/virtualbox/5.0.24/VirtualBoxSDK-5.0.24-108355.zip
    # - source_hash: http://download.virtualbox.org/virtualbox/5.0.24/MD5SUMS
    - archive_format: zip
    - user: {{ my_username }}
    - group: staff
    - trim_output: 5
    - if_missing: /opt/virtualbox/5.0.24/sdk/installer

Steps to Reproduce Issue

sudo salt-call --local state.sls {the state file we just defined}

local:
----------
          ID: vagrant-sdk
    Function: archive.extracted
        Name: /opt/virtualbox/5.0.24
      Result: False
     Comment: Unable to verify upstream hash of source file http://download.virtualbox.org/virtualbox/5.0.24/VirtualBoxSDK-5.0.24-108355.zip, please set source_hash or set skip_verify to True
     Started: 16:33:26.085266
    Duration: 80.799 ms

But, attempting to define skip_verify: true is ineffective because the switch is not programmed.

Versions Report

Salt Version:
           Salt: 2016.3.0-829-g69f8e3b

Dependency Versions:
           cffi: Not Installed
       cherrypy: Not Installed
       dateutil: Not Installed
          gitdb: Not Installed
      gitpython: Not Installed
          ioflo: Not Installed
         Jinja2: 2.8
        libgit2: Not Installed
        libnacl: Not Installed
       M2Crypto: 0.21.1
           Mako: Not Installed
   msgpack-pure: Not Installed
 msgpack-python: 0.4.6
   mysql-python: Not Installed
      pycparser: Not Installed
       pycrypto: 2.6.1
         pygit2: Not Installed
         Python: 2.7.11+ (default, Apr 17 2016, 14:00:29)
   python-gnupg: Not Installed
         PyYAML: 3.11
          PyZMQ: 15.2.0
           RAET: Not Installed
          smmap: Not Installed
        timelib: Not Installed
        Tornado: 4.3
            ZMQ: 4.1.4

System Versions:
           dist: Ubuntu 16.04 xenial
        machine: x86_64
        release: 4.4.0-28-generic
         system: Linux
        version: Ubuntu 16.04 xenial
@Ch3LL
Copy link
Contributor

Ch3LL commented Jul 7, 2016

@vernondcole would you mind trying #34529 and seeing if that possible fix works for you?

@Ch3LL Ch3LL added Bug broken, incorrect, or confusing behavior P3 Priority 3 severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around State-Module Core relates to code central or existential to Salt fixed-pls-verify fix is linked, bug author to confirm fix labels Jul 7, 2016
@Ch3LL Ch3LL added this to the Approved milestone Jul 7, 2016
@rallytime
Copy link
Contributor

This was fixed in #34529 and is available in 2016.3.4 which is currently in the packaging process. Since we didn't hear back here, I am going to close this up. If this pops up again, let us know and we can take another look.

@mrichins
Copy link

mrichins commented Jul 1, 2017

I actually have been running into this problem recently. The lack of feedback stumped me for a while.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug broken, incorrect, or confusing behavior Core relates to code central or existential to Salt fixed-pls-verify fix is linked, bug author to confirm fix P3 Priority 3 severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around State-Module
Projects
None yet
Development

No branches or pull requests

4 participants