[DTACLOUD-522] New Deltacloud Ruby Client - instance address access and user_data decode

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Component/s: Client (Ruby)
• Environment: Deltacloud commit version: b114f2e961bd2772ddb354a0291a1f27d1efa23d; Ruby version: ruby 1.9.3p392 (2013-02-22 revision 39386) [x86_64-linux] ; Fedora 18
• Assignee: Michal Fojtik
• Reporter: Ronelle Landy
• Created: 31/Mar/13 21:05
• Updated: 09/Apr/13 13:00
• Resolved: 09/Apr/13 13:00

Description

I've been modifying the system tests: creating an instance with user_data and then ssh'ing to the instance to verify the user_data is on the instance in the correct form.

Using the rhevm provider, I hit these issues:

• Could not retrieve the type and/or value of the public_address from the instance. Tried:
  >> instanceCreated.public_addresses.first[:type]
  • • NoMethodError Exception: undefined method `[]' for #<Deltacloud::Client::InstanceAddress:0x000000024c8d38>

• base64-decode fun ...
  Getting the instance does show the address:

>> client.instance( instance._id )
#<Deltacloud::Client::Instance> {:state=>"RUNNING", :owner_id=>"xxxxxx", :realm_id=>"99408929-82cf-4dc7-a532-9d998063fa95", :image_id=>"dd01aa3a-36d6-42cc-972a-a29cd2c6b211", :hardware_profile_id=>"SERVER", :public_addresses=>#<Deltacloud::Client::InstanceAddress type="ipv4", value="10.16.120.120">, #<Deltacloud::Client::InstanceAddress type="mac", value="00:1a:4a:10:77:11">, #<Deltacloud::Client::InstanceAddress type="vnc", value="qeblade26.rhq.lab.eng.bos.redhat.com">, :private_addresses=>[], :name=>"rlandyUserData2", :description=>nil, :_id=>"b11156c2-61f4-4dba-bfdb-298061878280"}

ssh'ing to the instance ...
[root@10-16-120-120 ~]# /sbin/modprobe floppy; lsmod | grep floppy
floppy 61447 1
[root@10-16-120-120 ~]# /bin/mount /dev/fd0 /media; cat /media/deltacloud-user-data.txt
mount: /dev/fd0 already mounted or /media busy
mount: according to mtab, /dev/fd0 is already mounted on /media
<returns base64 decoded data>

^^^ ... if we are following the same functionality as the old client, this data should be base-64 encoded, right?