Bug 1496549 - [upstream] Refreshing EC2 Instances without name result in exception
Summary: [upstream] Refreshing EC2 Instances without name result in exception
Keywords:
Status: CLOSED DUPLICATE of bug 1471297
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: GA
: cfme-future
Assignee: Julian Cheal
QA Contact: Matouš Mojžíš
URL:
Whiteboard: ec2:provider:refresh:instance
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-27 17:51 UTC by Matouš Mojžíš
Modified: 2017-12-05 15:49 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-10 14:14:11 UTC
Category: ---
Cloudforms Team: AWS
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
evm.log (15.38 KB, text/plain)
2017-09-27 17:51 UTC, Matouš Mojžíš
no flags Details

Description Matouš Mojžíš 2017-09-27 17:51:22 UTC
Created attachment 1331496 [details]
evm.log

Description of problem:


Version-Release number of selected component (if applicable):
master.20170927102505_8547972

How reproducible:
Always

Steps to Reproduce:
1. Have an ec2 provider with instances without name
2. Add it to CFME
3. Refresh

Actual results:
Refresh is broken.
Evm log added as attachment.

Expected results:
It should refresh without issues.

Additional info:

Comment 2 Bronagh Sorota 2017-09-27 19:21:16 UTC
Matous,

 I tried the following and could not reproduce this bug:
1) Updated to the latest master branch code
2) Created an instance on the AWS console with a tag as follows:
  - tag name - "Name"
  - tag value - not set
3) Created an instance on the AWS console without any tags
4) I added a new AWS provider and both instances created in steps 2 and 3 above were created in CF with a name set to the UID of the instance, as designed.

Can you please give me more information? What steps did you follow on the AWS console to create the VM.
Thanks
Bronagh

Comment 3 Bronagh Sorota 2017-09-27 19:22:13 UTC
see comment #2 for needsinfo

Comment 9 Matouš Mojžíš 2017-10-10 14:14:11 UTC
Okay, after long time I discovered that the issue was same as in this BZ:
https://bugzilla.redhat.com/show_bug.cgi?id=1471297
I had AMI with tag Name without value.
So closing this as duplicate and setting linked bug ON_DEV.

*** This bug has been marked as a duplicate of bug 1471297 ***


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