tripleo-quickstart fail to deploy overcloud for pike and ocata release

Bug #1722841 reported by Aneesh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Invalid
High
Unassigned

Bug Description

Running following tripleo-quickstart command results in error(overcloud is not deployed) for pike and ocata

./quickstart.sh -X -n -T all -t all -b -v -R pike -c config/general_config/featureset007.yml $VIRTHOST

Post deployment validation error due to failed overcloud deployment.
: The `HorizonPublic` endpoint is not defined in the `EndpointMap` of the deployed stack. This means Horizon may not have been deployed correctly

overcloud-deploy.log
The disable_upgrade_deployment flag is not set in the roles file. This flag is expected when you have a nova-compute .

In python-triploclient overcloud_deploy.py, when disable_upgrade_deployment is set to False and if validation_warnings_fatal, it raises InvalidConfiguration and I think openstack overcloud deploy uses validation_warnings_fatal flag.
This causes to fail overcloud deploy and hence post_deployment validation fails for url check in env file.

Aneesh (aneeshputtur)
affects: tripleo → tripleo-quickstart
Revision history for this message
Alex Schultz (alex-schultz) wrote :

the tripleo-quickstart project should not be used

affects: tripleo-quickstart → tripleo
Changed in tripleo:
milestone: none → queens-2
importance: Undecided → High
status: New → Triaged
Revision history for this message
Sagi (Sergey) Shnaidman (sshnaidm) wrote :

@Aneesh, thanks for report. Please note that featureset007 is running on multinode and it's not supported in any other environment - ovb or libvirt. It runs only on CI.
Which environment do you run it?

Changed in tripleo:
status: Triaged → Incomplete
Revision history for this message
Aneesh (aneeshputtur) wrote :

My environment is libvirt.

Changed in tripleo:
milestone: queens-2 → queens-3
Changed in tripleo:
milestone: queens-3 → queens-rc1
Changed in tripleo:
milestone: queens-rc1 → rocky-1
Changed in tripleo:
milestone: rocky-1 → rocky-2
Changed in tripleo:
milestone: rocky-2 → rocky-3
Changed in tripleo:
milestone: rocky-3 → rocky-rc1
Changed in tripleo:
milestone: rocky-rc1 → stein-1
Changed in tripleo:
milestone: stein-1 → stein-2
Revision history for this message
Sorin Sbarnea (ssbarnea) wrote :
Sorin Sbarnea (ssbarnea)
Changed in tripleo:
status: Incomplete → Confirmed
tags: added: alert
Revision history for this message
Marios Andreou (marios-b) wrote :

that disable_upgrades_deployment flag error on master in the reference on comment #4 above [1] is non fatal afaik and the flag itself isnt' used since queens (i'd have to confirm or P maybe).

[1] http://logs.openstack.org/24/567224/141/check/tripleo-ci-centos-7-containers-multinode/98c6201/logs/undercloud/home/zuul/overcloud_deploy.log.txt.gz#_2018-12-05_11_16_44

Revision history for this message
Sorin Sbarnea (ssbarnea) wrote :

Ok, so this message is just a warning and not the real cause of deployment failure. We shoul try to make it obvious that is just a warning and preferably eradicate it anyway.

The big question is where it does originate from as I was not able to locate its source using http://codesearch.openstack.org/ ...

Revision history for this message
Sorin Sbarnea (ssbarnea) wrote :

Raise new bug for the timeout issue at https://bugs.launchpad.net/tripleo/+bug/1806966

tags: removed: alert
Changed in tripleo:
milestone: stein-2 → stein-3
Changed in tripleo:
milestone: stein-3 → stein-rc1
Changed in tripleo:
milestone: stein-rc1 → train-1
Changed in tripleo:
milestone: train-1 → train-2
Revision history for this message
Alex Schultz (alex-schultz) wrote :

Pike and Ocata are now EOL

Changed in tripleo:
status: Confirmed → Invalid
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.