Bug 1466831 - us-west-2 rhel atomic 7.3 x86_64 access ami-6e312717
us-west-2 rhel atomic 7.3 x86_64 access ami-6e312717
Status: VERIFIED
Product: Cloud Image Validation
Classification: Red Hat
Component: images (Show other bugs)
RHEL7.3
x86_64 Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Vratislav Hutsky
Vratislav Hutsky
: TestOnly
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-30 10:04 EDT by Vratislav Hutsky
Modified: 2017-06-30 10:04 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
ami-6e312717-log.yaml (1.88 KB, text/yaml)
2017-06-30 10:04 EDT, Vratislav Hutsky
no flags Details

  None (edit)
Description Vratislav Hutsky 2017-06-30 10:04:24 EDT

    
Comment 1 Vratislav Hutsky 2017-06-30 10:04:27 EDT
Created attachment 1293239 [details]
ami-6e312717-log.yaml
Comment 2 Vratislav Hutsky 2017-06-30 10:04:29 EDT
# m4.xlarge: passed
-
  create_instance: skip Traceback (most recent call last):   File "/us
  r/local/lib/python2.7/dist-packages/dva-0.6-py2.7.egg/dva/work/stage
  .py", line 54, in wrapper     ret = fn(params)   File "/usr/local/li
  b/python2.7/dist-packages/dva-0.6-py2.7.egg/dva/work/params.py",
  line 31, in wrapper     return fn(params)   File "/usr/local/lib/pyt
  hon2.7/dist-packages/dva-0.6-py2.7.egg/dva/tools/retrying.py", line
  35, in wrapper     return fn(*args, **kvs)   File "/usr/local/lib/py
  thon2.7/dist-packages/dva-0.6-py2.7.egg/dva/work/stage.py", line
  111, in create_instance     raise SkipError(err) SkipError: got
  VPCResourceNotSpecified - skipping: ami-6e312717, us-west-2,
  m4.xlarge (EC2ResponseError: 400 Bad Request <?xml version="1.0"
  encoding="UTF-8"?> <Response><Errors><Error><Code>VPCResourceNotSpec
  ified</Code><Message>The specified instance type can only be used in
  a VPC. A subnet ID or network interface ID is required to carry out
  the request.</Message></Error></Errors><RequestID>761a4aed-0c7c-4f9c
  -9735-273c10f2af88</RequestID></Response>)

Note You need to log in before you can comment on or make changes to this bug.