Thank you Sean for your pointers.
Modified the job definition as per your comments. Please have a look at
below patch.
https://review.openstack.org/#/c/154518/
On 02/11/2015 05:43 PM, Sean Dague wrote:
On 02/11/2015 02:08 AM, Bharat Kumar wrote:
Hi All,
I issued "check experimental" on patch [1] to run GlusterFS experimental
job (' check-tempest-dsvm-full-glusterfs-centos7
<http://logs.openstack.org/86/152286/3/experimental/check-tempest-dsvm-full-glusterfs-centos7/b211fb1/>').
It is failing with below error in log file. [2]
/[ERROR] /opt/stack/new/devstack/functions-common:629 Cloning not
allowed in this configuration/
This is because if the setting " ERROR_ON_CLONE=True" in localrc file
[3], so it is unable to clone "devstack-plugin-glusterfs" repository.
Please let me know your comments to avoid this issue?
Thanks in advance.
[1] https://review.openstack.org/#/c/152286/
[2]
http://logs.openstack.org/86/152286/3/experimental/check-tempest-dsvm-full-glusterfs-centos7/b211fb1/logs/devstacklog.txt.gz
[3]
http://logs.openstack.org/86/152286/3/experimental/check-tempest-dsvm-full-glusterfs-centos7/b211fb1/logs/localrc.txt.gz
This is where it went wrong:
- shell: |
#!/bin/bash -xe
export PYTHONUNBUFFERED=true
export DEVSTACK_GATE_TIMEOUT=120
export DEVSTACK_GATE_TEMPEST=1
export DEVSTACK_GATE_TEMPEST_FULL=1
export PROJECTS="stackforge/devstack-plugin-glusterfs $PROJECTS"
export DEVSTACK_LOCAL_CONFIG=$(cat <<EOF
enable_service glusterfs
ENABLED_BACKENDS=glusterfs:glusterfs
TEMPEST_STORAGE_PROTOCOL=gluster
GLUSTERFS_LOOPBACK_DISK_SIZE=8G
enable_plugin glusterfs
/opt/git/stackforge/devstack-plugin-glusterfs
EOF
)
export BRANCH_OVERRIDE={branch-override}
if [ "$BRANCH_OVERRIDE" != "default" ] ; then
export OVERRIDE_ZUUL_BRANCH=$BRANCH_OVERRIDE
fi
cp devstack-gate/devstack-vm-gate-wrap.sh
./safe-devstack-vm-gate-wrap.sh
./safe-devstack-vm-gate-wrap.sh
enable_plugin glusterfs /opt/git/stackforge/devstack-plugin-glusterfs
Needs to be
enable_plugin devstack-plugin-glusterfs
/opt/git/stackforge/devstack-plugin-glusterfs
The name needs to be the same as the last part of the git repo to work
in the gate. The actual git url is irrelevant in the gate case, because
cloning is blocked, but the name needs to map to the already cloned repo.
You can see that your repo was made available in the gate here -
http://logs.openstack.org/86/152286/3/experimental/check-tempest-dsvm-full-glusterfs-centos7/b211fb1/logs/devstack-gate-setup-workspace-new.txt.gz#_2015-02-11_04_00_05_111
and here -
http://logs.openstack.org/86/152286/3/experimental/check-tempest-dsvm-full-glusterfs-centos7/b211fb1/logs/devstack-gate-setup-workspace-new.txt.gz#_2015-02-11_04_00_05_825
However because of the name mismatch devstack isn't picking it up.
Will try to tighten this up in the future to make the issues more obvious.
-Sean
--
Warm Regards,
Bharat Kumar Kobagana
Software Engineer
OpenStack Storage – RedHat India
Mobile - +91 9949278005
_______________________________________________
OpenStack-Infra mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
