Bug 1407012

Thanks, Guys.

Regards,

According to our records, this should be resolved by openstack-tripleo-common-2.0.0-9.el7ost.  This build is available now.

Hi,

can you confirm that with The openstack-tripleo-common >= 2.0.0-9.el7ost.  You don't have the issue anymore so I can close this as a duplicate of 1385190.  

Regards,

All the recent upgrade test I have done from 8 to 9 works. Still waiting to the need-info to be resolved.

Initial deployment:

source ~/stackrc
export THT=/usr/share/openstack-tripleo-heat-templates/

openstack overcloud deploy --templates $THT \
-e $THT/environments/network-isolation.yaml \
-e $THT/environments/network-management.yaml \
-e ~/openstack_deployment/environments/nodes.yaml \
-e ~/openstack_deployment/environments/network-environment.yaml \
-e ~/openstack_deployment/environments/neutron-settings.yaml \
-e ~/firstboot-environment.yaml


[stack@undercloud-0 ~]$ cat firstboot-environment.yaml 
resource_registry:
  OS::TripleO::NodeUserData: /home/stack/firstboot-config.yaml
[stack@undercloud-0 ~]$ cat firstboot-config.yaml 
heat_template_version: 2014-10-16

resources:
  userdata:
    type: OS::Heat::MultipartMime
    properties:
      parts:
      - config: {get_resource: all_config}

  all_config:
    type: OS::Heat::SoftwareConfig
    properties:
      group: script
      config: {get_file: /home/stack/setup.sh}

outputs:
  OS::stack_id:
    value: {get_resource: userdata}
[stack@undercloud-0 ~]$ cat setup.sh 
#!/bin/bash

PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin
export PATH

## root password
echo 'marius' | sudo passwd root --stdin

# permit root login over SSH
sed -i -e 's/.*ssh-rsa/ssh-rsa/' /root/.ssh/authorized_keys
sed -i.orig -e 's/PasswordAuthentication.*/PasswordAuthentication yes/g' /etc/ssh/sshd_config
sed -i -e 's/ChallengeResponseAuthentication.*/ChallengeResponseAuthentication yes/g' /etc/ssh/sshd_config
sed -i -e 's/^#\(UseDNS .*$\)/UseDNS no/' /etc/ssh/sshd_config
systemctl restart sshd

# timezone
timedatectl set-timezone Asia/Tokyo

echo "NodeUserData script first run" > /root/nodeuserdata


### Start upgrade
Before the upgrade procedure I changed setup.sh:

[stack@undercloud-0 ~]$ diff setup.sh.init setup.sh
19c19
< echo "NodeUserData script first run" > /root/nodeuserdata
---
> echo "NodeUserData script second run" > /root/nodeuserdata

After undercloud upgrade:
openstack-tripleo-common-2.0.0-10.el7ost.noarch


major-upgrade-aodh.yaml completed fine:

source ~/stackrc
export THT=/usr/share/openstack-tripleo-heat-templates/

openstack overcloud deploy --templates $THT \
-e $THT/environments/network-isolation.yaml \
-e $THT/environments/network-management.yaml \
-e ~/openstack_deployment/environments/nodes.yaml \
-e ~/openstack_deployment/environments/network-environment.yaml \
-e ~/openstack_deployment/environments/neutron-settings.yaml \
-e ~/firstboot-environment.yaml \
-e /usr/share/openstack-tripleo-heat-templates/environments/major-upgrade-aodh.yaml \
--force-postconfig

Stack overcloud UPDATE_COMPLETE
/home/stack/.ssh/known_hosts updated.
Original contents retained as /home/stack/.ssh/known_hosts.old
Skipping "horizon" postconfig because it wasn't found in the endpoint map output
PKI initialization in init-keystone is deprecated and will be removed.

No handlers could be found for logger "oslo_config.cfg"
2017-06-13 16:07:31.776 1910 WARNING keystone.cmd.cli [-] keystone-manage pki_setup is not recommended for production use.
The following cert files already exist, use --rebuild to remove the existing files before regenerating:
/etc/keystone/ssl/certs/ca.pem already exists
/etc/keystone/ssl/private/signing_key.pem already exists
/etc/keystone/ssl/certs/signing_cert.pem already exists
Connection to 192.168.0.11 closed.
Overcloud Endpoint: http://172.16.18.25:5000/v2.0
Overcloud Deployed

I'll move this bug to verified.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:1457

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days