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

Bug 1287804

Summary: Error: unable to push cib Call cib_replace failed when updating 7.0 GA to puddle
Product: Red Hat OpenStack Reporter: mathieu bultel <mbultel>
Component: openstack-tripleo-heat-templatesAssignee: Jay Dobies <jason.dobies>
Status: CLOSED DUPLICATE QA Contact: yeylon <yeylon>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 7.0 (Kilo)CC: gfidente, mburns, rhel-osp-director-maint, srevivo
Target Milestone: ---   
Target Release: 8.0 (Liberty)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-02 17:45:32 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:

Description mathieu bultel 2015-12-02 17:43:15 UTC
Description of problem:

On 7.0 GA environment with network isolation, when updating to the latest puddle (nov 23), the updates hanged on :

Error: unable to push cib\nCall cib_replace failed
Update was older than existing configuration

I need to update the epoch into /var/lib/pacemaker/cib/cib.xml to get continue.

Stuck on controller-3 updates :
Status:\n  overcloud-controller-0: Online\n  overcloud-controller-1: Online\n  overcloud-controller-2: Online\n\nDaemon Status:\n  corosync: active/enabled\n  pacemaker: active/enabled\n  pcsd: active/enabled\nFinished yum_update.sh on server 2a6336ea-d759-4520-a089-777814830b1a at Tue Dec  1 12:16:24 EST 2015\n", 
    "deploy_stderr": "Error: unable to push cib\nCall cib_replace failed (-205): Update was older than existing configuration\n\n", 
    "deploy_status_code": 0, 
    "update_managed_packages": "false"
  }, 
  "creation_time": "2015-12-01T16:14:15Z", 
  "updated_time": "2015-12-02T08:31:32Z", 
  "input_values": {}, 
  "action": "UPDATE", 
  "status_reason": "Deploy data available", 
  "id": "97963e8d-5505-4794-8e08-bef2597a60bc"

Comment 2 Giulio Fidente 2015-12-02 17:45:32 UTC

*** This bug has been marked as a duplicate of bug 1285485 ***