Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
First Last Prev Next    This bug is not in your last search results.
Bug 1590560 - ceph upgrade/deployment fails with "Error response from daemon: No such container: ceph-create-keys"
ceph upgrade/deployment fails with "Error response from daemon: No such conta...
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: ceph-ansible (Show other bugs)
13.0 (Queens)
Unspecified Unspecified
urgent Severity urgent
: ga
: 13.0 (Queens)
Assigned To: leseb
Yogev Rabl
: Triaged
Depends On: 1590746
Blocks:
  Show dependency tree / graph
 
Reported: 2018-06-12 17:27 EDT by Marius Cornea
Modified: 2018-07-09 13:46 EDT (History)
13 users (show)

See Also:
Fixed In Version: ceph-ansible-3.1.0-0.1.rc9.el7cp
Doc Type: Known Issue
Doc Text:
The ceph-ansible utility does not always remove the ceph-create-keys container from the same node where it was created. Because of this, the deployment may fail with the message "Error response from daemon: No such container: ceph-create-keys." This may affect any ceph-ansible run, including fresh deployments, that have: * multiple compute notes or * a custom role behaving as ceph client which is also hosting a service consuming ceph.
Story Points: ---
Clone Of:
: 1590746 (view as bug list)
Environment:
Last Closed: 2018-06-27 09:58:15 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
scohen: needinfo+

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:2086 None None None 2018-06-27 09:59 EDT

  None (edit)
Description Marius Cornea 2018-06-12 17:27:55 EDT 
Description of problem:
FFU: ceph upgrade fails during the fast forward process with "Error response from daemon: No such container: ceph-create-keys"

Version-Release number of selected component (if applicable):
ceph-ansible-3.1.0-0.1.rc8.el7cp.noarch

How reproducible:
100%

Steps to Reproduce:
1. Deploy OSP10 with 3 controllers + 2 compute + 3 ceph osd nodes
2. Run through the fast forward upgrade procedure
3. Run the ceph upgrade step:


openstack overcloud ceph-upgrade run \
    --templates /usr/share/openstack-tripleo-heat-templates \
    --stack qe-Cloud-0 \
            -e /usr/share/openstack-tripleo-heat-templates/environments/cinder-backup.yaml \
        -e /usr/share/openstack-tripleo-heat-templates/environments/services/sahara.yaml \
        -e /usr/share/openstack-tripleo-heat-templates/environments/storage-environment.yaml \
        -e /home/stack/virt/internal.yaml \
        -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml \
        -e /home/stack/virt/network/network-environment.yaml \
        -e /home/stack/virt/enable-tls.yaml \
        -e /home/stack/virt/inject-trust-anchor.yaml \
        -e /home/stack/virt/public_vip.yaml \
        -e /usr/share/openstack-tripleo-heat-templates/environments/tls-endpoints-public-ip.yaml \
        -e /home/stack/virt/hostnames.yml \
        -e /home/stack/virt/debug.yaml \
                -e /home/stack/cli_opts_params.yaml \
            -e /home/stack/ceph-ansible-env.yaml \
    --ceph-ansible-playbook '/usr/share/ceph-ansible/infrastructure-playbooks/switch-from-non-containerized-to-containerized-ceph-daemons.yml,/usr/share/ceph-ansible/infrastructure-playbooks/rolling_update.yml' \
            --container-registry-file /home/stack/virt/docker-images.yaml \

Actual results:
Fails

Expected results:
Completes fine.

Additional info:
Attaching ceph-install-workflow.log.
Comment 2 Marius Cornea 2018-06-12 20:29:51 EDT 
Note that it shows during OSP13 minor update as well where workaround to downgrade to ceph-ansible-3.1.0-0.1.rc3 worked:

 sudo yum downgrade -y http://download.eng.bos.redhat.com/brewroot/packages/ceph-ansible/3.1.0/0.1.rc3.el7cp/noarch/ceph-ansible-3.1.0-0.1.rc3.el7cp.noarch.rpm
Comment 3 Giulio Fidente 2018-06-13 11:33:40 EDT 
We believe this can be hit for any ceph-ansible run (including fresh deployments) with >1 compute node (or custom role behaving as ceph client, hosting a service consuming ceph).
Comment 12 Yogev Rabl 2018-06-21 10:48:08 EDT 
verified on ceph-ansible-3.1.0-0.1.rc9.el7cp.noarch
Comment 14 errata-xmlrpc 2018-06-27 09:58:15 EDT 
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/RHEA-2018:2086
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.