contrail tgz upgrade of a deb provisioned cluster stuck at u'config'

[wenqing liang]

Contrail upgrade of r3.0.2.0-48 deb provisioned cluster (with or without storage) to r3.1.0.0-2736 tgz via r3.1.0.0-2736 sm hangs/loops at u'config':

Jun 22 12:30:46 cmbu-auto-esx1-lnx02 puppet-master[4029]: Compiled catalog for cmbu-ceph-perf3.englab.juniper.net in environment contrail_2736kilo_tgz in 0.95 seconds
Jun 22 12:30:46 cmbu-auto-esx1-lnx02 dhcpd: DHCPDISCOVER from 00:25:90:1b:29:e2 via eth0: network 10.87.128.0/19: no free leases
Jun 22 12:30:48 cmbu-auto-esx1-lnx02 dhcpd: DHCPDISCOVER from 78:e7:d1:be:74:86 via eth0: network 10.87.128.0/19: no free leases
Jun 22 12:30:49 cmbu-auto-esx1-lnx02 puppet-master[4029]: Compiled catalog for cmbu-ceph-perf4.englab.juniper.net in environment contrail_2736kilo_tgz in 1.01 seconds
Jun 22 12:30:51 cmbu-auto-esx1-lnx02 dhcpd: DHCPREQUEST for 10.87.140.28 from 00:e0:81:c9:f6:2e via eth0: unknown lease 10.87.140.28.
Jun 22 12:30:52 cmbu-auto-esx1-lnx02 puppet-master[4029]: Compiled catalog for cmbu-ceph-perf2.englab.juniper.net in environment contrail_2736kilo_tgz in 0.96 seconds

Jun 22 12:23:10 cmbu-ceph-perf1 puppet-agent[28062]: (/Stage[config]/Contrail::Config::Neutron/Contrail::Lib::Augeas_conf_rm[config_rm_service_provider]/Augeas[/etc/neutron/neutron.conf_removing_service_provider]) Dependency Exec[exec-provision-control] has failures: true
Jun 22 12:23:10 cmbu-ceph-perf1 puppet-agent[28062]: (/Stage[config]/Contrail::Config::Neutron/Contrail::Lib::Augeas_conf_rm[config_rm_service_provider]/Augeas[/etc/neutron/neutron.conf_removing_service_provider]) Skipping because of failed dependencies
Jun 22 12:23:10 cmbu-ceph-perf1 puppet-agent[28062]: (/Stage[config]/Contrail::Config::Neutron/Neutron_config[service_providers/service_provider]) Dependency Exec[exec-provision-control] has failures: true

[Abhay Joshi (abhayj)]

This has nothing to do with deb to tgz. The upgrade from 3.0 to 3.1 is not possible, unless the targets are manually upgraded to Ruby 1.9. That is requirement for the new manifests in release 3.1. We can look into addressing the upgrade via SM, but for now it has to be done manually before upgrade can work.

Problem is 3.1 onwards. Hence closing 3.0 instance.