create cluster configuration failed

Bug #1305154 reported by Aleksey Kasatkin
This bug report is a duplicate of:  Bug #1325012: UI is cached between Fuel versions. Edit Remove
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
High
Fuel UI Team

Bug Description

ISO Fuel 5.0 #89

When creating env with all default settings in wizard I see the following:

"Your OpenStack environment has been created, but configuration failed. You can configure it manually."

Tags: ui
Revision history for this message
Aleksey Kasatkin (alekseyk-ru) wrote :
Revision history for this message
Aleksey Kasatkin (alekseyk-ru) wrote :
Changed in fuel:
milestone: none → 5.0
Revision history for this message
Mike Scherbakov (mihgen) wrote :

I can't reproduce on {"build_id": "2014-04-12_11-10-34", "mirantis": "yes", "build_number": "99", "nailgun_sha": "14f3652d8c48238e99c61c220a227944dd1f0943", "production": "dev", "ostf_sha": "118c955085ea7829f3a34decd38d63554b74451c", "fuelmain_sha": "70bcec009840c621cba10b0f501925fc70ebe8bc", "astute_sha": "401bc474b1d8cebb8ba70b3b6154107e08fd725d", "release": "5.0", "fuellib_sha": "4d769ed4da4a1ce5a379bd905866c063ab5b93d7"}

Revision history for this message
Ivan Kolodyazhny (e0ne) wrote :

Can't reproduce on {"build_id": "2014-04-14_01-00-26", "mirantis": "yes", "build_number": "101", "nailgun_sha": "61410bcf3201cd737e68ece8ab15313acc746476", "production": "dev", "ostf_sha": "118c955085ea7829f3a34decd38d63554b74451c", "fuelmain_sha": "ddc94c52c267f0276cbd8485d6e704aea05b23a5", "astute_sha": "401bc474b1d8cebb8ba70b3b6154107e08fd725d", "release": "5.0", "fuellib_sha": "101f3645ead182bc47024ff7568b04554de06bba"}

Changed in fuel:
status: New → Incomplete
Mike Scherbakov (mihgen)
Changed in fuel:
status: Incomplete → Invalid
Revision history for this message
piontec (piontec-gmail) wrote :

I can confirm this bug, it happened to me even when using pre-configured VirtualBox scrpts. After a reinstall it worked, but i can't make it work on physical hardware. The problem is mainly with networking settings - or settings are gone. Please see the attached dump.

Changed in fuel:
status: Invalid → Confirmed
Revision history for this message
piontec (piontec-gmail) wrote :

The only error i've found in the log file is:

[423] Exception during worker initialization: #<AMQP::TCPConnectionFailed: Could not estabilish TCP connection to 10.20.0.2:5672>, trace: ["/usr/lib64/ruby/gems/2.1.0/gems/amq-client-0.9.12/lib/amq/client/async/adapters/event_machine.rb:162:in `block in initialize'", "/usr/lib64/ruby/gems/2.1.0/gems/amq-client-0.9.12/lib/amq/client/async/adapter.rb:306:in `call'", "/usr/lib64/ruby/gems/2.1.0/gems/amq-client-0.9.12/lib/amq/client/async/adapter.rb:306:in `tcp_connection_failed'", "/usr/lib64/ruby/gems/2.1.0/gems/amq-client-0.9.12/lib/amq/client/async/adapters/event_machine.rb:290:in `unbind'", "/usr/lib64/ruby/gems/2.1.0/gems/eventmachine-1.0.3/lib/eventmachine.rb:1438:in `event_callback'", "/usr/lib64/ruby/gems/2.1.0/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in `run_machine'", "/usr/lib64/ruby/gems/2.1.0/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in `run'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/server/worker.rb:38:in `run'", "/usr/lib64/ruby/gems/2.1.0/gems/raemon-0.3.0/lib/raemon/master.rb:343:in `worker_loop!'", "/usr/lib64/ruby/gems/2.1.0/gems/raemon-0.3.0/lib/raemon/master.rb:266:in `block (2 levels) in spawn_workers'", "/usr/lib64/ruby/gems/2.1.0/gems/raemon-0.3.0/lib/raemon/master.rb:266:in `fork'", "/usr/lib64/ruby/gems/2.1.0/gems/raemon-0.3.0/lib/raemon/master.rb:266:in `block in spawn_workers'", "/usr/lib64/ruby/gems/2.1.0/gems/raemon-0.3.0/lib/raemon/master.rb:261:in `each'", "/usr/lib64/ruby/gems/2.1.0/gems/raemon-0.3.0/lib/raemon/master.rb:261:in `spawn_workers'", "/usr/lib64/ruby/gems/2.1.0/gems/raemon-0.3.0/lib/raemon/master.rb:300:in `maintain_worker_count'", "/usr/lib64/ruby/gems/2.1.0/gems/raemon-0.3.0/lib/raemon/master.rb:120:in `master_loop!'", "/usr/lib64/ruby/gems/2.1.0/gems/raemon-0.3.0/lib/raemon/master.rb:53:in `start'", "/usr/lib64/ruby/gems/2.1.0/gems/raemon-0.3.0/lib/raemon/master.rb:22:in `start'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/bin/astuted:84:in `<top (required)>'", "-e:1:in `load'", "-e:1:in `<main>'"]

Revision history for this message
piontec (piontec-gmail) wrote :

Attached is a screenshot of net communication just after finishing the wizard.

Revision history for this message
piontec (piontec-gmail) wrote :

Attributes dump for the config

Revision history for this message
piontec (piontec-gmail) wrote :

The output of
http://10.20.0.2:8000/api/clusters/6/network_configuration/nova_network
is:
Wrong net provider - environment uses 'neutron'

and output of
http://10.20.0.2:8000/api/clusters/6
is:
{"status": "new", "is_customized": false, "release_id": 2, "name": "test", "fuel_version": "5.0", "net_provider": "neutron", "mode": "multinode", "changes": [{"node_id": null, "name": "attributes"}, {"node_id": null, "name": "networks"}], "id": 6, "grouping": "roles"}

Also atteched screenshot of network settings

Revision history for this message
piontec (piontec-gmail) wrote :

neutron api output

Revision history for this message
Vitaly Kramskikh (vkramskikh) wrote :

Caused by browser cache. I've created another bug: https://bugs.launchpad.net/fuel/+bug/1325012

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.