[Queens][phase1] packstack scenario 2 and 3 deployments are failing with different issues

[chandan kumar]

In Queens promotion, phase1 scenario 2 & 3 packstack jobs are failing with different issues:
scenario:1
https://centos.logs.rdoproject.org/weirdo-queens-promote-packstack-scenario002/229/weirdo-project/logs/latest/manifests/192.168.1.50_controller.pp.log.txt.gz#_Aug_12_08_54_49
Aug 12 08:54:43 queens-promote-packstack-002-229 systemd[1]: Starting OpenStack Neutron Server...
Aug 12 08:54:49 queens-promote-packstack-002-229 systemd[1]: neutron-server.service: main process exited, code=exited, status=1/FAILURE
Aug 12 08:54:49 queens-promote-packstack-002-229 systemd[1]: Failed to start OpenStack Neutron Server.
Aug 12 08:54:49 queens-promote-packstack-002-229 systemd[1]: Unit neutron-server.service entered failed state.
Aug 12 08:54:49 queens-promote-packstack-002-229 systemd[1]: neutron-server.service failed.


https://centos.logs.rdoproject.org/weirdo-queens-promote<email address hidden>

=ERROR REPORT==== 12-Aug-2019::08:56:14 ===
Error on AMQP connection <0.6597.0> (192.168.1.50:35266 -> 192.168.1.50:5672, state: starting):
AMQPLAIN login refused: user 'guest' can only connect via localhost

Scenario2: https://centos.logs.rdoproject.org/weirdo-queens-promote-packstack-scenario003/221/weirdo-project/logs/latest/manifests/192.168.1.43_compute.pp.log.txt.gz#_Aug_12_08_57_07
Aug 12 08:57:00 queens-promote-packstack-003-221 systemd[1]: Starting OpenStack Nova Compute Server...
Aug 12 08:57:07 queens-promote-packstack-003-221 systemd[1]: openstack-nova-compute.service: main process exited, code=exited, status=1/FAILURE
Aug 12 08:57:07 queens-promote-packstack-003-221 systemd[1]: Failed to start OpenStack Nova Compute Server.
Aug 12 08:57:07 queens-promote-packstack-003-221 systemd[1]: Unit openstack-nova-compute.service entered failed state.
Aug 12 08:57:07 queens-promote-packstack-003-221 systemd[1]: openstack-nova-compute.service failed.
Aug 12 08:57:07 queens-promote-packstack-003-221 systemd[1]: openstack-nova-compute.service holdoff time over, scheduling restart.
Aug 12 08:57:07 queens-promote-packstack-003-221 systemd[1]: Stopped OpenStack Nova Compute Server.
Aug 12 08:57:07 queens-promote-packstack-003-221 systemd[1]: Starting OpenStack Nova Compute Server

https://centos.logs.rdoproject.org/weirdo-queens-promote<email address hidden>

=ERROR REPORT==== 12-Aug-2019::08:41:23 ===
Error on AMQP connection <0.402.0> (192.168.1.43:56264 -> 192.168.1.43:5672, state: starting):
AMQPLAIN login refused: user 'guest' can only connect via localhost

It is tracker bug for all the issue related packstack job related to queens promotions.

[yatin (yatinkarel)]

Fix Proposed to packstack stable/queens:- https://review.opendev.org/675922

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/675922
Committed: https://git.openstack.org/cgit/x/packstack/commit/?id=d18775cdf5da15610ac4fa9e43eeeac7b72b2f07
Submitter: Zuul
Branch: stable/queens

commit d18775cdf5da15610ac4fa9e43eeeac7b72b2f07
Author: Alfredo Moralejo <email address hidden>
Date: Thu Jul 25 12:58:45 2019 +0200

    Force qemu emulation in CI and add dmidecode command to logs

    Some upstream infra is enabling nested virtualization but it's failing
    randomly so let's force qemu virt_type.

    We need it to debugs issues with jobs incorrectly detecting
    virtualization time.

    Change-Id: I1e53bbdcccb6402d343c98abf2696d452717d1a9
    (cherry picked from commit c84e3b6e849a193a2a8c9c5ab7466a5bd24b5aa2)

    Fix rabbitmq configuration

    We can move to the commit hash for puppet-rabbitmq used in RDO queens, since
    this is what we are testing in RDO. This requires a few changes:

    - Update the URL used in the Puppetfile, and set the branch to 'master'.
    - Remove old workarounds in amqp.pp
    - Set loopback_users properly, based on what is requested by [1].

    [1] - https://github.com/voxpupuli/puppet-rabbitmq/commit/0ada399b330fbc84a1a1179ad0e827e0735e1912

    Also do below [Queens Only] changes to clear gate issues:-
    - Install PyYAML==3.12 as latest version has issues
      with older setuptools(22.0.5).
    - Install openstack modules from stable/queens rather
      than master.

    Closes-Bug: #1839922
    Change-Id: I9262836eb05a47bfe78ea0ac6d1c04199f29f527
    (cherry picked from commit b1c78d696a4ec483c1fbc60f624635bb7608ed96)