Nova_floating_range evaluated before keystone-server has started

Bug #1348756 reported by Ryan Moe
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Committed
High
Dmitry Borodaenko

Bug Description

{"build_id": "2014-07-23_17-21-54", "ostf_sha": "81b019a502711dfcd935a981b292e88eb956b141", "build_number": "350", "auth_required": false, "api": "1.0", "nailgun_sha": "06b9becc1e6831351aac693290ac619c92e56e99", "production": "docker", "fuelmain_sha": "18bb11f6dde9880022d4ce379f40df4d2a27a5e9", "astute_sha": "fd9b8e3b6f59b2727b1b037054f10e0dd7bd37f1", "feature_groups": ["mirantis"], "release": "5.1", "fuellib_sha": "8bffb2a4723109614aeaabaabffa3c94a1b72705"}

Env is CentOS simple with nova-network. The floating IP range can't be created because keystone has not started yet.

(/Stage[main]/Osnailyfacter::Cluster_simple/Nova_floating_range[10.108.43.11-10.108.43.20]) Could not evaluate: Unable to connect to #<Net::HTTP:0x7f26b38cc018>

From the logs:

2014-07-25T18:36:51.039241+01:00 err: (/Stage[main]/Osnailyfacter::Cluster_simple/Nova_floating_range[10.108.43.11-10.108.43.20]) Could not evaluate: Unable to connect to
#<Net::HTTP:0x7f26b38cc018>

2014-07-25T18:37:01.212115+01:00 notice: (/Stage[main]/Keystone/Service[keystone]/ensure) ensure changed 'stopped' to 'running'

Ryan Moe (rmoe)
Changed in fuel:
importance: Undecided → High
milestone: none → 5.1
Changed in fuel:
status: New → Confirmed
assignee: nobody → Dmitry Borodaenko (dborodaenko)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-library (master)

Fix proposed to branch: master
Review: https://review.openstack.org/109739

Changed in fuel:
status: Confirmed → In Progress
Revision history for this message
Dmitry Borodaenko (angdraug) wrote :

This is not a duplicate of bug #1348171, but it is possible that the fix for that bug has also fixed this problem:
https://review.openstack.org/#/c/109392/1/deployment/puppet/osnailyfacter/manifests/cluster_simple.pp

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
Vladimir Kuklin (vkuklin) wrote :
Download full text (3.4 KiB)

we forgot to fix it in HA:

Fri Aug 01 08:48:24 +0000 2014 /Stage[main]/Osnailyfacter::Cluster_ha/Nova_floating_range[10.108.1.128-10.108.1.254] (err): Could not evaluate: Oops - not sure what happened: 751: unexpected token at '<html><body><h1>504 Gateway Time-out</h1>
The server didn't respond in time.
</body></html>
'
/usr/lib/ruby/vendor_ruby/openstack/connection.rb:533:in `deal_with_faulty_error'
/usr/lib/ruby/vendor_ruby/openstack/connection.rb:510:in `raise_exception'
/usr/lib/ruby/vendor_ruby/openstack/connection.rb:207:in `req'
/usr/lib/ruby/vendor_ruby/openstack/compute/connection.rb:242:in `api_extensions'
/usr/lib/ruby/vendor_ruby/openstack/compute/connection.rb:502:in `check_extension'
/usr/lib/ruby/vendor_ruby/openstack/compute/connection.rb:475:in `get_floating_ips_bulk'
/etc/puppet/modules/nova/lib/puppet/provider/nova_floating_range/nova_manage.rb:49:in `operate_range'
/etc/puppet/modules/nova/lib/puppet/provider/nova_floating_range/nova_manage.rb:15:in `exists?'
/usr/lib/ruby/vendor_ruby/puppet/property/ensure.rb:81:in `retrieve'
/usr/lib/ruby/vendor_ruby/puppet/type.rb:1035:in `retrieve'
/usr/lib/ruby/vendor_ruby/puppet/type.rb:1063:in `retrieve_resource'
/usr/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:223:in `from_resource'
/usr/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:17:in `evaluate'
/usr/lib/ruby/vendor_ruby/puppet/transaction.rb:174:in `apply'
/usr/lib/ruby/vendor_ruby/puppet/transaction.rb:187:in `eval_resource'
/usr/lib/ruby/vendor_ruby/puppet/transaction.rb:117:in `call'
/usr/lib/ruby/vendor_ruby/puppet/transaction.rb:117:in `evaluate'
/usr/lib/ruby/vendor_ruby/puppet/util.rb:327:in `thinmark'
/usr/lib/ruby/1.8/benchmark.rb:308:in `realtime'
/usr/lib/ruby/vendor_ruby/puppet/util.rb:326:in `thinmark'
/usr/lib/ruby/vendor_ruby/puppet/transaction.rb:117:in `evaluate'
/usr/lib/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:118:in `traverse'
/usr/lib/ruby/vendor_ruby/puppet/transaction.rb:108:in `evaluate'
/usr/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:164:in `apply'
/usr/lib/ruby/vendor_ruby/puppet/util/log.rb:149:in `with_destination'
/usr/lib/ruby/vendor_ruby/puppet/transaction/report.rb:108:in `as_logging_destination'
/usr/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:163:in `apply'
/usr/lib/ruby/vendor_ruby/puppet/configurer.rb:125:in `apply_catalog'
/usr/lib/ruby/vendor_ruby/puppet/util.rb:161:in `benchmark'
/usr/lib/ruby/1.8/benchmark.rb:308:in `realtime'
/usr/lib/ruby/vendor_ruby/puppet/util.rb:160:in `benchmark'
/usr/lib/ruby/vendor_ruby/puppet/configurer.rb:124:in `apply_catalog'
/usr/lib/ruby/vendor_ruby/puppet/configurer.rb:192:in `run'
/usr/lib/ruby/vendor_ruby/puppet/application/apply.rb:268:in `apply_catalog'
/usr/lib/ruby/vendor_ruby/puppet/application/apply.rb:218:in `main'
/usr/lib/ruby/vendor_ruby/puppet/application/apply.rb:146:in `run_command'
/usr/lib/ruby/vendor_ruby/puppet/application.rb:364:in `run'
/usr/lib/ruby/vendor_ruby/puppet/application.rb:470:in `plugin_hook'
/usr/lib/ruby/vendor_ruby/puppet/application.rb:364:in `run'
/usr/lib/ruby/vendor_ruby/puppet/util.rb:478:in `exit_on_fail'
/usr/lib/ruby/vendor_ruby/puppet/application.rb:364:in `run...

Read more...

Changed in fuel:
status: Fix Committed → Confirmed
Changed in fuel:
status: Confirmed → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.