| Summary: | Error connecting to framework: Address family not supported by protocol - socket(2) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | wes hayutin <whayutin> | ||||||
| Component: | deltacloud-core | Assignee: | Michal Fojtik <mfojtik> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Ronelle Landy <rlandy> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 1.0.0 | CC: | jrd, morazi, rananda, whayutin | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-08-30 17:17:05 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
|
Description
wes hayutin
2011-12-08 22:51:50 UTC
Could you please provide the API_PROVIDER url Conductor is trying to connect to? Seems like the URL is screwed up somehow. Also what you mean with 'changing' the datastore ? adding ce-sprint-next bugs to ce-sprint adding to ce-sprint removing ce-sprint-next tracker Is this bug repeatable somehow? If negative, then we can close this bug. What do you think? Trying to reproduce the issue reported in here, I ran into the segfault problem reported in BZ-782573:
>> Writing PID to /var/run/deltacloud/deltacloud-core-mock.pid
>> Changing process privilege to nobody:nobody
thin server (localhost:3002) [deltacloud-mock][21450]: >> Thin web server (v1.2.11 codename Bat-Shit Crazy)
thin server (localhost:3002) [deltacloud-mock][21450]: >> Debugging ON
thin server (localhost:3002) [deltacloud-mock][21450]: >> Maximum connections set to 1024
thin server (localhost:3002) [deltacloud-mock][21450]: >> Listening on localhost:3002, CTRL+C to stop
thin server (localhost:3002) [deltacloud-mock][21450]: /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/utils.rb:105: warning: already initialized constant HEX
thin server (localhost:3002) [deltacloud-mock][21450]: /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/utils.rb:107: warning: already initialized constant TO_REMEMBER
thin server (localhost:3002) [deltacloud-mock][21450]: /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/utils.rb:108: warning: already initialized constant ASCII
thin server (localhost:3002) [deltacloud-mock][21450]: /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/errors.rb:128: warning: already initialized constant DEFAULT_CLOSE_ON_4XX_PROBABILITY
thin server (localhost:3002) [deltacloud-mock][21450]: /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/parsers.rb:47: warning: already initialized constant DEFAULT_XML_LIBRARY
thin server (localhost:3002) [deltacloud-mock][21450]: /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:66: warning: already initialized constant AMAZON_PROBLEMS
thin server (localhost:3002) [deltacloud-mock][21450]: /usr/lib/ruby/gems/1.8/gems/aws-2.5.5/lib/ses/../awsbase/awsbase.rb:86: warning: already initialized constant DEFAULT_SIGNATURE_VERSION
I, [2012-02-07T18:26:40.426697 #21450] INFO -- : New Aws::Ec2 using per_thread-connection mode
I, [2012-02-07T18:26:40.444324 #21450] INFO -- : New Aws::Ec2 using per_thread-connection mode
I, [2012-02-07T18:26:40.446078 #21450] INFO -- : Opening new HTTPS connection to ec2.ap-southeast-1.amazonaws.com:443
I, [2012-02-07T18:26:40.459648 #21450] INFO -- : Opening new HTTPS connection to ec2.us-east-1.amazonaws.com:443
/usr/lib/ruby/1.8/set.rb:201: [BUG] Segmentation fault
ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
Waiting on a resolution for BZ-782573 before verifying/reproducing this BZ.
Verified that the follow steps can be executed without error:
- Map conductor provider account to one realm of two available
- build and push an image to a rhevm cluster with two Cloud Resource Clusters (realms)
- launch an instance into the first mapped realm (North in attached screenshot)
- change the rhevm cluster mapping to the South realm
- run aeolus-restart-services
- launch another instance into this second realm
- change mapping back to North
- rerun aeolus-restart-services
- launch a third instance
Multiple instances are launched and started - see attached screenshot.
>>> Versions tested:
rpm -qa |grep aeolus
aeolus-conductor-0.8.0-37.el6.noarch
aeolus-configure-2.5.0-15.el6.noarch
aeolus-conductor-daemons-0.8.0-37.el6.noarch
rubygem-aeolus-image-0.3.0-10.el6.noarch
rubygem-aeolus-cli-0.3.0-11.el6.noarch
aeolus-all-0.8.0-37.el6.noarch
aeolus-conductor-doc-0.8.0-37.el6.noarch
[root@ibm-x3200m3-01 workspace]# rpm -qa |grep deltacloud
deltacloud-core-rhevm-0.5.0-5.el6.noarch
deltacloud-core-0.5.0-5.el6.noarch
rubygem-deltacloud-client-0.5.0-2.el6.noarch
deltacloud-core-ec2-0.5.0-5.el6.noarch
deltacloud-core-vsphere-0.5.0-5.el6.noarch
Created attachment 566363 [details]
cluster mapping change
Created attachment 566364 [details]
instances launched in two realms
|