Not able to upgrade the contrail-cluster from contrail-command UI

Bug #1800646 reported by musharani
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R5.0
Invalid
High
Sarin Kizhakkepurayil
Trunk
Invalid
High
Sarin Kizhakkepurayil

Bug Description

The cluster is brought up using contrail-command UI with the build ocata-5.0-313. While trying to upgrade the setup from 313 to 314 by clicking the upgrade button from UI it is getting redirected to provision page. But provision is not happening when I check the logs.

Setup is available with that issue.
nodec59

Logs:
[root@nodec59 ~]# docker exec contrail_command tail -f /var/log/ansible.log
2018-10-29 17:03:43,091 p=11362 u=root | skipping: [10.204.216.232]
2018-10-29 17:03:43,101 p=11362 u=root | TASK [install_contrail : update image] *****************************************
2018-10-29 17:03:43,125 p=11362 u=root | skipping: [10.204.216.232] => (item=contrail-vcenter-manager)
2018-10-29 17:03:43,135 p=11362 u=root | TASK [install_contrail : create contrail vcenter-manager file] *****************
2018-10-29 17:03:43,154 p=11362 u=root | skipping: [10.204.216.232]
2018-10-29 17:03:43,164 p=11362 u=root | TASK [install_contrail : start contrail vcenter-manager] ***********************
2018-10-29 17:03:43,182 p=11362 u=root | skipping: [10.204.216.232]
2018-10-29 17:03:43,184 p=11362 u=root | PLAY RECAP *********************************************************************
2018-10-29 17:03:43,184 p=11362 u=root | 10.204.216.232 : ok=72 changed=47 unreachable=0 failed=0
2018-10-29 17:03:43,184 p=11362 u=root | localhost : ok=39 changed=1 unreachable=0 failed=0

But this messages are from previous provisioning. It is not proceeding further.

Revision history for this message
musharani (musharani) wrote :
Jeba Paulaiyan (jebap)
tags: removed: blocker
tags: added: releasenote
Revision history for this message
Abhay Joshi (abhayj) wrote :

From: Leela Bharath Kumar Kassetti <email address hidden>
Date: Tuesday, October 30, 2018 at 10:35 AM
To: Usha Rani Mani <email address hidden>, Prachi Yadav <email address hidden>
Cc: Sudheendra Rao <email address hidden>, Sarin Kizhakkepurayil <email address hidden>, Abhay Joshi <email address hidden>, Ignatious Johnson <email address hidden>
Subject: Re: cluster upgrade through new UI

Hi Usha,

The command_servers.yml file that you are using is not the latest one.

“project_id” field should be renamed to “project_name”. Also, the timeout field “expire: 3600” should be “expire: 36000”

Can you make these changes in your command_servers.yml file and re-run?

Regards,
Bharath Kassetti.

From: Usha Rani Mani <email address hidden>
Date: Tuesday, October 30, 2018 at 5:49 AM
To: Prachi Yadav <email address hidden>, Leela Bharath Kumar Kassetti <email address hidden>
Cc: Sudheendra Rao <email address hidden>, Sarin Kizhakkepurayil <email address hidden>, Abhay Joshi <email address hidden>, Ignatious Johnson <email address hidden>
Subject: RE: cluster upgrade through new UI

Hi Prachi,

The setup is available in the problematic state after clicking upgrade button. The command_servers.yml is the latest one which is saved in the name of command_server_c59_5.0.yml.

You can use the setup for debugging. Please find the bug id for this issue.
https://bugs.launchpad.net/juniperopenstack/+bug/1800646

Setup details:
Nodec59.

Thanks,
Usha.

Revision history for this message
musharani (musharani) wrote :

Upgrade is working fine after changing the fields project_name and expire_value. Hence move this bug to invalid state.

Jeba Paulaiyan (jebap)
tags: removed: releasenote
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.