Bug 831156 - Launching instances in VMware fails if the instance name contains spaces
Summary: Launching instances in VMware fails if the instance name contains spaces
Keywords:
Status: CLOSED EOL
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.1.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
Assignee: Angus Thomas
QA Contact: Rehana
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-12 10:33 UTC by Justin Clift
Modified: 2020-03-27 18:32 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 18:32:57 UTC
Embargoed:

Attachments (Terms of Use)

Description Justin Clift 2012-06-12 10:33:06 UTC 
Description of problem:

  Using the upstream Aeolus 0.10.0 F16 rpms, Instances launched in VMware immediately fail with "Vanished" status when the instance name has spaces.

  For example, using an instance name of "InstanceA" works, but "Instance A" automatically fails. (every time)

  This is an excerpt from the /var/log/aeolus-conductor/dbomatic.log showing the problem:

    2012-06-12 20:27:09 INFO Deltacloud refresh started
    2012-06-12 20:27:09 INFO Deltacloud instances refresh started
    2012-06-12 20:27:16 INFO updating instance state for InstanceF/F16-vmware: InstanceF-F16-vmware
    2012-06-12 20:27:16 WARN caught deltacloud exception bad URI(is not URI?): http://localhost:3002/api/instances/Instance E-F16-vmware when updating instance Instance E/F16-vmware
    2012-06-12 20:27:16 INFO known instance missing from provider: Instance E/F16-vmware Instance E-F16-vmware
    2012-06-12 20:27:23 INFO updating instance state for InstanceD/F16-vmware: InstanceD-F16-vmware
    2012-06-12 20:27:30 INFO updating instance state for InstanceC/F16-vmware: InstanceC-F16-vmware
    2012-06-12 20:27:30 INFO Deltacloud instances refresh completed
    2012-06-12 20:27:30 INFO Deltacloud refresh completed

Version-Release number of selected component (if applicable):

  $ rpm -qa | grep -i aeolus | sort
  aeolus-all-0.10.1-1.fc16.noarch
  aeolus-conductor-0.10.1-1.fc16.noarch
  aeolus-conductor-daemons-0.10.1-1.fc16.noarch
  aeolus-conductor-devel-0.10.1-1.fc16.noarch
  aeolus-conductor-doc-0.10.1-1.fc16.noarch
  aeolus-configure-2.6.0-1.fc16.noarch
  rubygem-aeolus-cli-0.5.0-1.fc16.noarch
  rubygem-aeolus-image-0.5.0-1.fc16.noarch

  $ rpm -qa | grep -i deltacloud | sort
  deltacloud-core-0.5.0-2.fc16.noarch
  deltacloud-core-ec2-0.5.0-2.fc16.noarch
  deltacloud-core-rhevm-0.5.0-2.fc16.noarch
  deltacloud-core-vsphere-0.5.0-2.fc16.noarch
  rubygem-deltacloud-client-0.5.0-1.fc16.noarch


How reproducible:

  Every time.


Additional info:

  Doesn't seem to happen with instances launched in oVirt or EC2, just VMware.
Note You need to log in before you can comment on or make changes to this bug.