CI: random error in: ceph : Enabling all new Luminous-only functionality (EPERM: not supported)

[Radosław Piliszek]

Task: ceph : Enabling all new Luminous-only functionality
Stderr: Error EPERM: not supported for this release yet
Link: http://logs.openstack.org/36/665536/1/check/kolla-ansible-centos-source-upgrade-ceph/ea3d9b8/primary/ara-report/

[Radosław Piliszek (yoctozepto)]

in CI so auto-confirmed

[Radosław Piliszek (yoctozepto)]

seems almost sure when it comes to centos build:
http://zuul.openstack.org/builds?job_name=kolla-ansible-centos-source-upgrade-ceph
never in ubuntu:
http://zuul.openstack.org/builds?job_name=kolla-ansible-ubuntu-source-upgrade-ceph
(the yellow ones are unrelated atm)

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/665620

[Radosław Piliszek (yoctozepto)]

After analyzing logs further, it seems Ubuntu is not affected because it is doing Luminous to Luminous upgrade (so nothing in fact).
stable/stein CentOS usually fails due to other causes and does not fail due to this one. It does Luminous to Nautilus but the upgrade procedure leaves OSD compatibility at Luminous so it works.
Master CentOS does Nautilus to Nautilus and it fails.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Radosław Piliszek (<email address hidden>) on branch: master
Review: https://review.opendev.org/665620
Reason: wrong approach, see the bug report

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/665927

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/665927
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=0ea991e4d2c633ec97c1c9e9b7c96ee3b053a446
Submitter: Zuul
Branch: master

commit 0ea991e4d2c633ec97c1c9e9b7c96ee3b053a446
Author: Radosław Piliszek <email address hidden>
Date: Tue Jun 18 11:31:51 2019 +0200

    Make Ceph upgrade check Ceph release to avoid EPERM

    Since we have different upgrade paths, we must use the actually
    installed Ceph release name when doing require-osd-release

    Closes-Bug: #1832989

    Change-Id: I6aaa4b4ac0fb739f7ad885c13f55b6db969996a2
    Signed-off-by: Radosław Piliszek <email address hidden>

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/stein
Review: https://review.opendev.org/666260

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/666260
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=7eb9e80235c385dd0b48e02215b1f2a24d63a649
Submitter: Zuul
Branch: stable/stein

commit 7eb9e80235c385dd0b48e02215b1f2a24d63a649
Author: Radosław Piliszek <email address hidden>
Date: Tue Jun 18 11:31:51 2019 +0200

    Make Ceph upgrade check Ceph release to avoid EPERM

    Since we have different upgrade paths, we must use the actually
    installed Ceph release name when doing require-osd-release

    Closes-Bug: #1832989

    Change-Id: I6aaa4b4ac0fb739f7ad885c13f55b6db969996a2
    Signed-off-by: Radosław Piliszek <email address hidden>
    (cherry picked from commit 0ea991e4d2c633ec97c1c9e9b7c96ee3b053a446)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/kolla-ansible 8.0.0.0rc2 release candidate.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/kolla-ansible 9.0.0.0rc1 release candidate.