Nodes failed to be bootstrapped if only https is available on master node

Bug #1480866 reported by Tatyanka
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
High
Stanislaw Bogatkin

Bug Description

Steps to Reproduce:
1. Deploy master node
2. Disable http in nginx container and reload it
3. turn on 3 vms and waiting for it has been bootstrapped

Actual

Nodes failed to be discovered with error in nailgun-agent:

015-08-03T10:17:33.061783+00:00 err: 10:17:33.058210 #1949] ERROR -- : Connection refused - connect(2) (http://10.109.0.2:8000)
2015-08-03T10:17:33.061938+00:00 info: /usr/lib/ruby/gems/1.8/gems/httpclient-2.3.2/lib/httpclient/session.rb:803:in `initialize'/usr/lib/ruby/gems/1.8/gems/httpclient-2.3.2/lib/httpclient/session.rb:803:in `new'/usr/lib/ruby/gems/1.8/gems/httpclient-2.3.2/lib/httpclient/session.rb:803:in `create_socket'/usr/lib/ruby/gems/1.8/gems/httpclient-2.3.2/lib/httpclient/session.rb:752:in `connect'/usr/lib/ruby/gems/1.8/gems/httpclient-2.3.2/lib/httpclient/timeout.rb:131:in `timeout'/usr/lib/ruby/gems/1.8/gems/httpclient-2.3.2/lib/httpclient/session.rb:751:in `connect'/usr/lib/ruby/gems/1.8/gems/httpclient-2.3.2/lib/httpclient/session.rb:609:in `query'/usr/lib/ruby/gems/1.8/gems/httpclient-2.3.2/lib/httpclient/session.rb:164:in `query'/usr/lib/ruby/gems/1.8/gems/httpclient-2.3.2/lib/httpclient.rb:1080:in `do_get_block'/usr/lib/ruby/gems/1.8/gems/httpclient-2.3.2/lib/httpclient.rb:884:in `do_request'/usr/lib/ruby/gems/1.8/gems/httpclient-2.3.2/lib/httpclient.rb:978:in `protect_keep_alive_disconnected'/usr/lib/ruby/gems/1.8/gems/httpclient-2.3.2/lib/httpclient.rb:883:in `do_request'/usr/lib/ruby/gems/1.8/gems/httpclient-2.3.2/lib/httpclient.rb:771:in `request'/usr/lib/ruby/gems/1.8/gems/httpclient-2.3.2/lib/httpclient.rb:681:in `post'/usr/bin/nailgun-agent:183:in `post'/usr/bin/nailgun-agent:651

VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "7.0"
  openstack_version: "2015.1.0-7.0"
  api: "1.0"
  build_number: "110"
  build_id: "2015-07-30_03-46-56"
  nailgun_sha: "999efffd19b823a27b17f0e97a42ac0d47ae9ce5"
  python-fuelclient_sha: "f04e6c46783ecd6000df31b61b6749da66d4d828"
  fuel-agent_sha: "355c08a04917f047b88f66242767049d2b1d0ff0"
  fuel-nailgun-agent_sha: "1512b9af6b41cc95c4d891c593aeebe0faca5a63"
  astute_sha: "126709e7f18a719ec4bd2a13a37d972285381892"
  fuel-library_sha: "90aff7558fb00373ccd363b7722e2f90dc25894d"
  fuel-ostf_sha: "f907eca277ab4ba769774417d6ff5bf30ef479ee"
  fuelmain_sha: "de5b333815f8541224c6726dc8446ffc7fb18b5b"

Revision history for this message
Tatyanka (tatyana-leontovich) wrote :
description: updated
Changed in fuel:
status: New → Confirmed
summary: - Nodes failed to be bootsrapped if only https is vailable on master node
+ Nodes failed to be bootsrapped if only https is available on master node
summary: - Nodes failed to be bootsrapped if only https is available on master node
+ Nodes failed to be bootstrapped if only https is available on master
+ node
tags: added: feature
tags: removed: feature
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-nailgun-agent (master)

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

Changed in fuel:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-nailgun-agent (master)

Reviewed: https://review.openstack.org/209170
Committed: https://git.openstack.org/cgit/stackforge/fuel-nailgun-agent/commit/?id=e01693992d7a0304d926b922b43f3b747c35964c
Submitter: Jenkins
Branch: master

commit e01693992d7a0304d926b922b43f3b747c35964c
Author: Stanislaw Bogatkin <email address hidden>
Date: Tue Aug 4 19:28:25 2015 +0300

    Add ability to use HTTPS port

    As long as we have HTTPS enabled by default on master node,
    it would be nice to use secure channel for nailgun agent. So,
    this commit switch to HTTPS as default protocol for agent and
    allow to use plain HTTP as a fallback.
    We use SSL no_verify for connection cause now certificate for
    master node nginx generated on container creation and we don't
    have an ability to easily push it to trusted on bootstrap node.

    Change-Id: I570890b19eac74db6f3666af966e86f64327740d
    Closes-Bug: #1480866

Changed in fuel:
status: In Progress → Fix Committed
tags: added: on-verification
Revision history for this message
Nikita Marchenko (nmarchenko) wrote :

verified on 224 ISO

tags: removed: on-verification
Changed in fuel:
status: Fix Committed → Fix Released
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.