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

kitchen cannot find any OS image #1356

Closed
tomklino opened this issue Feb 8, 2018 · 2 comments
Closed

kitchen cannot find any OS image #1356

tomklino opened this issue Feb 8, 2018 · 2 comments

Comments

@tomklino
Copy link

tomklino commented Feb 8, 2018

Description

right after kitchen init, using the default .kitchen.yml file, or when changing the name of the OS to debian, debian-8, debian-8.4 and others that used to work, kitchen fails to start (kitchen create) with the error URL not found

Kitchen Version

Test Kitchen version 1.19.2

ChefDK Version

If you are running test-kitchen via ChefDK, chef --version will provide additional relevent version details.

Chef Development Kit Version: 2.4.17
chef-client version: 13.6.4
delivery version: master (73ebb72a6c42b3d2ff5370c476be800fee7e5427)
berks version: 6.3.1
kitchen version: 1.19.2
inspec version: 1.45.13

Ruby Version

If you are not using test-kitchen via ChefDK, please provide the output of ruby --version.

ruby 2.3.3p222 (2016-11-21) [x86_64-linux-gnu]

Platform Version

Tell us which Operating System distribution and version test-kitchen is running on.
ubuntu mate

Replication Case

trying to create a kitchen with the following name under "platform" in the .kitchen.yml file:

  • name: ubuntu-14.04

Kitchen Output

The relevant output of the test-kitchen run or a link to a gist of the entire run, if there is one.

The debug output (kitchen -l debug) may be useful, but please link to a gist, or truncate it.

Please do not paste the full run out put here. If the full output would be useful, link to it in a gist.

-----> Starting Kitchen (v1.19.2)
-----> Creating <default-ubuntu-1404>...
       Bringing machine 'default' up with 'virtualbox' provider...
       ==> default: Box 'bento/ubuntu-14.04' could not be found. Attempting to find and install...
           default: Box Provider: virtualbox
           default: Box Version: >= 0
       The box 'bento/ubuntu-14.04' could not be found or
       could not be accessed in the remote catalog. If this is a private
       box on HashiCorp's Atlas, please verify you're logged in via
       `vagrant login`. Also, please double-check the name. The expanded
       URL and error message are shown below:
       
       URL: ["https://atlas.hashicorp.com/bento/ubuntu-14.04"]
       Error: The requested URL returned error: 404 Not Found
>>>>>> ------Exception-------
>>>>>> Class: Kitchen::ActionFailed
>>>>>> Message: 1 actions failed.
>>>>>>     Failed to complete #create action: [Expected process to exit with [0], but received '1'
---- Begin output of vagrant up --no-provision --provider virtualbox ----
STDOUT: Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'bento/ubuntu-14.04' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
STDERR: The box 'bento/ubuntu-14.04' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Atlas, please verify you're logged in via
`vagrant login`. Also, please double-check the name. The expanded
URL and error message are shown below:

URL: ["https://atlas.hashicorp.com/bento/ubuntu-14.04"]
Error: The requested URL returned error: 404 Not Found
---- End output of vagrant up --no-provision --provider virtualbox ----
Ran vagrant up --no-provision --provider virtualbox returned 1] on default-ubuntu-1404
>>>>>> ----------------------
>>>>>> Please see .kitchen/logs/kitchen.log for more details
>>>>>> Also try running `kitchen diagnose --all` for configuration

Kitchen Diagnose

Please include the output of kitchen diagnose --all or kitchen diagnose --loader (if the first failed). This can be helpful in troubleshooting, so please include it in a gist.

---
timestamp: 2018-02-08 10:45:18 UTC
kitchen_version: 1.19.2
plugins:
  driver:
    Vagrant:
      class: Kitchen::Driver::Vagrant
      version: 1.2.1
      api_version: 2
  provisioner:
    ChefSolo:
      class: Kitchen::Provisioner::ChefSolo
      version: 1.19.2
      api_version: 2
  transport:
    Ssh:
      class: Kitchen::Transport::Ssh
      version: 1.19.2
      api_version: 1
  verifier:
    Busser:
      class: Kitchen::Verifier::Busser
      version: 1.19.2
      api_version: 1
loader:
  process_erb: true
  process_local: true
  process_global: true
  global_config: 
  project_config:
    filename: "/home/tomk/workspace/learn-chef/guardium-install/.kitchen.yml"
    raw_data:
      driver:
        name: vagrant
      provisioner:
        name: chef_solo
      platforms:
      - name: ubuntu-14.04
      suites:
      - name: default
        run_list:
        - recipe[guardium-install::default]
        attributes: 
  local_config: 
  combined_config:
    filename: 
    raw_data:
      driver:
        name: vagrant
      provisioner:
        name: chef_solo
      platforms:
      - name: ubuntu-14.04
      suites:
      - name: default
        run_list:
        - recipe[guardium-install::default]
        attributes: 
instances:
  default-ubuntu-1404:
    platform:
      os_type: unix
      shell_type: bourne
    state_file:
      last_error: Kitchen::ShellOut::ShellCommandFailed
    driver:
      boot_timeout: 
      box: bento/ubuntu-14.04
      box_check_update: 
      box_download_ca_cert: 
      box_download_insecure: 
      box_url: 
      box_version: 
      cache_directory: "/tmp/omnibus/cache"
      cachier: 
      customize: {}
      gui: 
      kitchen_cache_directory: "/home/tomk/.kitchen/cache"
      kitchen_root: "/home/tomk/workspace/learn-chef/guardium-install"
      linked_clone: 
      log_level: :info
      name: vagrant
      network: []
      pre_create_command: 
      provider: virtualbox
      provision: false
      ssh: {}
      synced_folders:
      - - "/home/tomk/.kitchen/cache"
        - "/tmp/omnibus/cache"
        - 'create: true'
      test_base_path: "/home/tomk/workspace/learn-chef/guardium-install/test/integration"
      vagrant_binary: vagrant
      vagrantfile_erb: "/opt/chefdk/embedded/lib/ruby/gems/2.4.0/gems/kitchen-vagrant-1.2.1/templates/Vagrantfile.erb"
      vagrantfiles: []
      vm_hostname: default-ubuntu-1404.vagrantup.com
    provisioner:
      always_update_cookbooks: false
      architecture: 
      attributes: {}
      channel: :stable
      checksum: 
      chef_omnibus_install_options: 
      chef_omnibus_url: https://omnitruck.chef.io/install.sh
      chef_solo_path: "/bin/chef-solo"
      clients_path: 
      command_prefix: 
      config_path: 
      cookbook_files_glob: README.*,metadata.{json,rb},attributes/**/*,definitions/**/*,files/**/*,libraries/**/*,providers/**/*,recipes/**/*,resources/**/*,templates/**/*
      data_bags_path: 
      data_path: 
      debug: 
      deprecations_as_errors: false
      download_url: 
      encrypted_data_bag_secret_key_path: 
      enforce_idempotency: false
      environments_path: 
      ftp_proxy: 
      http_proxy: 
      https_proxy: 
      install_strategy: once
      kitchen_root: "/home/tomk/workspace/learn-chef/guardium-install"
      log_file: 
      log_level: auto
      max_retries: 1
      multiple_converge: 1
      name: chef_solo
      nodes_path: 
      platform: 
      platform_version: 
      policyfile: 
      policyfile_path: 
      product_name: 
      product_version: :latest
      profile_ruby: false
      require_chef_omnibus: true
      retry_on_exit_code:
      - 35
      - 213
      roles_path: 
      root_path: "/tmp/kitchen"
      run_list:
      - recipe[guardium-install::default]
      solo_rb: {}
      sudo: true
      sudo_command: sudo -E
      test_base_path: "/home/tomk/workspace/learn-chef/guardium-install/test/integration"
      wait_for_retry: 30
    transport:
      compression: false
      compression_level: 0
      connection_retries: 5
      connection_retry_sleep: 1
      connection_timeout: 15
      keepalive: true
      keepalive_interval: 60
      kitchen_root: "/home/tomk/workspace/learn-chef/guardium-install"
      log_level: :info
      max_ssh_sessions: 9
      max_wait_until_ready: 600
      name: ssh
      port: 22
      ssh_gateway: 
      ssh_gateway_username: 
      ssh_key: 
      test_base_path: "/home/tomk/workspace/learn-chef/guardium-install/test/integration"
      username: root
    verifier:
      busser_bin: "/tmp/verifier/bin/busser"
      chef_omnibus_root: "/opt/chef"
      command_prefix: 
      debug: 
      ftp_proxy: 
      http_proxy: 
      https_proxy: 
      kitchen_root: "/home/tomk/workspace/learn-chef/guardium-install"
      log_level: :info
      name: busser
      root_path: "/tmp/verifier"
      ruby_bindir: "/opt/chef/embedded/bin"
      sudo: true
      sudo_command: sudo -E
      suite_name: default
      test_base_path: "/home/tomk/workspace/learn-chef/guardium-install/test/integration"
      version: busser

NOTE:

This repository is for core issues with the Test-Kitchen framework, so if the issue is with a plugin you may be referred to file the issue with the appropriate plugin.

@cheeseplus
Copy link

This isn't a test-kitchen, nor a kitchen-vagrant issue - your installed version of Vagrant is so old it's unaware of the domain change from Atlas -> Vagrant Cloud. Please update the Vagrant version.

@lock
Copy link

lock bot commented Jan 18, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants