Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2229767

Summary: Failed to start openstack-manila-share resource in Pacemaker
Product: Red Hat OpenStack Reporter: Francesco Pantano <fpantano>
Component: openstack-tripleo-heat-templatesAssignee: Francesco Pantano <fpantano>
Status: CLOSED CURRENTRELEASE QA Contact: Alfredo <alfrgarc>
Severity: urgent Docs Contact: Jenny-Anne Lynch <jelynch>
Priority: urgent    
Version: 17.1 (Wallaby)CC: eshames, gfidente, gouthamr, jbadiapa, jelynch, jpretori, kthakre, lkuchlan, lsvaty, mariel, mburns, mkatari, pgrist, prgutier, vhariria
Target Milestone: z1Keywords: Triaged
Target Release: 17.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-14.3.1-1.20230519151021.el9ost Doc Type: Bug Fix
Doc Text:
Before this update, when you upgraded Red Hat Ceph Storage 4 to 5 during the upgrade from RHOSP 16.2 to 17.1, the overcloud upgrade failed because the containers that were associated with `ceph-nfs-pacemaker` were down, impacting the Shared File Systems service (manila). This issue is resolved in RHOSP 17.1.1.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-20 10:32:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2229777    

Description Francesco Pantano 2023-08-07 15:36:25 UTC 
Description of problem:

After Ceph is moved from 4 to 5 using the existing FFU procedure, ceph-nfs is misconfigured and not managed by pacemaker anymore.
The overcloud upgrade is failing because the ceph-nfs-pacemaker associated containers can't be found:

```
[tripleo-admin@controller-1 ~]$ sudo journalctl -xef -u ceph-nfs@pacemaker                                                                                                                   
-- Logs begin at Mon 2023-08-07 09:24:36 UTC. --                                                                                                                                             
Aug 07 10:47:02 controller-1 podman[499303]: Error: no container with name or ID "ceph-nfs-pacemaker" found: no such container                                                               
Aug 07 10:47:02 controller-1 podman[499434]: Error: no container with name or ID "ceph-nfs-pacemaker" found: no such container                                                               
Aug 07 10:47:02 controller-1 podman[499519]: Error: error creating container storage: the container name "ceph-nfs-controller-1" is already in use by 
bf48b6439174131620e2feedf". You have to remove that container to be able to reuse that name.: that name is already in use                                                                    
Aug 07 10:47:02 controller-1 systemd[1]: ceph-nfs: Control process exited, code=exited status=125                                                                          
Aug 07 10:47:02 controller-1 systemd[1]: ceph-nfs: Failed with result 'exit-code'.                                                                                         
-- Support: https://access.redhat.com/support                                                                                                                                                
-- The unit ceph-nfs has entered the 'failed' state with result 'exit-code'.                                                                                               
Aug 07 10:47:02 controller-1 systemd[1]: Failed to start Cluster Controlled ceph-nfs@pacemaker.                                                                                              
-- Subject: Unit ceph-nfs has failed                                                                                                                                       
-- Defined-By: systemd                                                                                                                                                                       
-- Support: https://access.redhat.com/support                                                                                                                                                
-- Unit ceph-nfs has failed.                                                                                                                                               
-- The result is failed.
```

Instead of having a single container managed by pacemaker, we can see 3 different ceph-nfs containers with a default configuration
that doesn't apply to the OpenStack context.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 24 Jenny-Anne Lynch 2023-09-15 14:13:59 UTC 
For 17.1.1 release notes, changed Known issue to Bug fix and modified doc text. Target milestone is z1.
From:
Known issue
There is currently a known issue when you upgrade Red Hat Ceph Storage 4 to 5 during the upgrade from RHOSP 16.2 to 17.1. The `ceph-nfs` resource is misconfigured and Pacemaker does not manage the resource. The overcloud upgrade fails because the containers that are associated with `ceph-nfs-pacemaker` are down, impacting the Shared File Systems service (manila). A fix is expected in RHOSP 17.1.1. Workaround: Apply the workaround from Red Hat KCS solution 7028073: link:https://access.redhat.com/solutions/7028073[Pacemaker does not manage the `ceph-nfs` resource correctly during RHOSP and RHCS upgrade].

To:
Bug fix
Before this update, when you upgraded Red Hat Ceph Storage 4 to 5 during the upgrade from RHOSP 16.2 to 17.1, the overcloud upgrade failed because the containers that were associated with `ceph-nfs-pacemaker` were down, impacting the Shared File Systems service (manila). This issue is resolved in RHOSP 17.1.1. 


- Removing Known issue from FFU guide under https://issues.redhat.com/browse/RHOSPDOC-1357.
- Updating FFU procedure under https://bugzilla.redhat.com/show_bug.cgi?id=2229777
Comment 26 Lon Hohberger 2023-09-20 10:32:47 UTC 
According to our records, this should be resolved by openstack-tripleo-heat-templates-14.3.1-1.20230519151024.el9ost.  This build is available now.