[tripleo] rocky overcloud deployment fails on xined configuration

Bug #1796030 reported by Raoul Scarazzini
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Raoul Scarazzini

Bug Description

Latest RDOPhase2 overcloud deployment fails while configuring xinetd service with this message:

Oct 3 15:00:08 overcloud-controller-0 puppet-user[43889]: [norpm] Attempting to install xinetd but it will not be installed
Oct 3 15:00:08 overcloud-controller-0 puppet-user[43889]: (/Stage[main]/Xinetd/Package[xinetd]/ensure) created
Oct 3 15:00:08 overcloud-controller-0 puppet-user[43889]: (/Stage[main]/Xinetd/File[/etc/xinetd.conf]/ensure) defined content as '{md5}7d37008224e71625019cb48768f267e7'
Oct 3 15:00:08 overcloud-controller-0 puppet-user[43889]: (/Stage[main]/Tripleo::Profile::Pacemaker::Database::Mysql/Xinetd::Service[galera-monitor]/File[/etc/xinetd.d/
galera-monitor]/ensure) defined content as '{md5}277d8e394456302944e482c7453c6def'
Oct 3 15:00:08 overcloud-controller-0 puppet-user[43889]: Systemd start for xinetd failed!
Oct 3 15:00:08 overcloud-controller-0 puppet-user[43889]: journalctl log for xinetd:
Oct 3 15:00:08 overcloud-controller-0 puppet-user[43889]: (/Stage[main]/Xinetd/Service[xinetd]/ensure) change from stopped to running failed: Systemd start for xinetd failed!
Oct 3 15:00:08 overcloud-controller-0 puppet-user[43889]: (/Stage[main]/Xinetd/Service[xinetd]/ensure) journalctl log for xinetd:
Oct 3 15:00:08 overcloud-controller-0 puppet-user[43889]: (/Stage[main]/Xinetd/Service[xinetd]/ensure) -- No entries --
Oct 3 15:00:08 overcloud-controller-0 puppet-user[43889]: (/Stage[main]/Xinetd/Service[xinetd]) Triggered 'refresh' from 2 events

After a first analysis it seems that the problem is related to the MySQL configuration, especially this [1] and the relative clustercheck part [2], we might need to drop this code.
Logs are available at [3], and the failed env might be available for a short amount of time.

[1] https://github.com/openstack/puppet-tripleo/blob/master/manifests/profile/pacemaker/database/mysql.pp#L304-L316
[2] https://github.com/openstack/puppet-tripleo/blob/6f790d624198eeb9219b26848c05f0edafd09dab/manifests/profile/pacemaker/clustercheck.pp#L56-L68
[3] https://thirdparty.logs.rdoproject.org/jenkins-oooq-rocky-rdo_trunk-bmu-ha-lab-andromeda-float_nic_with_vlans-12/

Tags: quickstart
Revision history for this message
Michele Baldessari (michele) wrote :

This is a deployment with /share/openstack-tripleo-heat-templates/environments/puppet-pacemaker.yaml which is not supported any longer. Probably oooq pushing that in even though it should not?

Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

I'm not always deploy containers, but when I do that's because of https://review.openstack.org/#/c/607950

Changed in tripleo:
importance: Undecided → High
milestone: none → stein-1
tags: added: quickstart
Changed in tripleo:
assignee: nobody → Raoul Scarazzini (rscarazz)
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-quickstart-extras (master)

Reviewed: https://review.openstack.org/607950
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=49bff74a805614efa070987e80e54084b0e04e1b
Submitter: Zuul
Branch: master

commit 49bff74a805614efa070987e80e54084b0e04e1b
Author: Raoul Scarazzini <email address hidden>
Date: Thu Oct 4 14:33:08 2018 +0200

    Always pass docker.yml when using containers

    According to the way we deploy via containers we always need to pass
    docker.yml, otherwise deployment problems can happen.

    Change-Id: I59493e71326891333863e295d06b01d320e50b5c
    Closes-Bug: #1796030

Changed in tripleo:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-quickstart-extras 2.1.1

This issue was fixed in the openstack/tripleo-quickstart-extras 2.1.1 release.

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.