Assigning public ssl hostname to public vip after cluster creation doesn't work after changes in nailgun

Bug #1537833 reported by Andrey Sledzinskiy on 2016-01-25
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
High
Alexander Kurenyshev
8.0.x
High
Alexander Kurenyshev
Mitaka
High
Alexander Kurenyshev

Bug Description

Right after cluster creation we are getting public vip to use it as public ssl hostname - https://github.com/openstack/fuel-qa/blob/727d498c09e5d62e6e328111cbd975bc5b9a64fc/fuelweb_test/models/fuel_web_client.py#L578

After introducing that changes in nailgun https://review.openstack.org/#/c/257953/ vips aren't assigned before deployment (https://bugs.launchpad.net/fuel/+bug/1537796).

We need to workaround this problem in tests to allow merging of these changes into nailgun.

I see two ways to solve a problem.
First one is to use --insecure option in openstack clients when accessing MOS here [0] and at another places.

Second way is to make changes in testing infra, to allow resolve CN name via hosts file. So, it will be possible to set some name at CN filed, and than after cluster creation get public vip IP, add matching line to the hosts file.

[0] https://github.com/openstack/fuel-qa/blob/14061f07fa6d0d78eddd9fc6dc2bb292a9f0478a/fuelweb_test/helpers/common.py#L51

Changed in fuel:
status: New → Confirmed
Changed in fuel:
assignee: Fuel QA Team (fuel-qa) → Alexander Kurenyshev (akurenyshev)
Changed in fuel:
status: Confirmed → In Progress

Reviewed: https://review.openstack.org/274002
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=5e89825fd3ce7db268b7c9bddf174d233aeca2a1
Submitter: Jenkins
Branch: master

commit 5e89825fd3ce7db268b7c9bddf174d233aeca2a1
Author: Alexander Kurenyshev <email address hidden>
Date: Fri Jan 29 13:52:01 2016 +0300

    Fix changes domain name in MOS services endpoints

    We couldn't use public vip ip before start deploying cluster.
    So, we need to add option to skip SSL cert verification
    when connecting to the MOS services, and replace unresolvable
    domain name with public vip ip after deployment

    Closes-Bug:1537833

    Change-Id: I53621022a3ae55cb30ab224800fc812ce2b0a79b

Changed in fuel:
status: In Progress → Fix Committed

Reviewed: https://review.openstack.org/275148
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=f5794d55ceb5dfa11569e109d13cdc09cf23ad2c
Submitter: Jenkins
Branch: stable/8.0

commit f5794d55ceb5dfa11569e109d13cdc09cf23ad2c
Author: Alexander Kurenyshev <email address hidden>
Date: Fri Jan 29 13:52:01 2016 +0300

    Fix changes domain name in MOS services endpoints

    We couldn't use public vip ip before start deploying cluster.
    So, we need to add option to skip SSL cert verification
    when connecting to the MOS services, and replace unresolvable
    domain name with public vip ip after deployment

    Closes-Bug:1537833

    Change-Id: I53621022a3ae55cb30ab224800fc812ce2b0a79b

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers