Swift3

Functional test failure - tempauth

Bug #1411099 reported by Charles Hsu
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Swift3
New
Undecided
Unassigned

Bug Description

vagrant@dev:~/swift3$ tox -e tempauth
tempauth develop-inst-noop: /home/vagrant/swift3
tempauth runtests: PYTHONHASHSEED='1472686979'
tempauth runtests: commands[0] | /bin/bash swift3/test/functional/run_test.sh
WARNING: No region specified for z0-127.0.0.1:6000/sda. Defaulting to region 1.
Device d0r1z0-127.0.0.1:6000R127.0.0.1:6000/sda_"" with 1.0 weight got id 0
WARNING: No region specified for z1-127.0.0.1:6000/sdb. Defaulting to region 1.
Device d1r1z1-127.0.0.1:6000R127.0.0.1:6000/sdb_"" with 1.0 weight got id 1
WARNING: No region specified for z2-127.0.0.1:6000/sdc. Defaulting to region 1.
Device d2r1z2-127.0.0.1:6000R127.0.0.1:6000/sdc_"" with 1.0 weight got id 2
WARNING: No region specified for z0-127.0.0.1:6001/sda. Defaulting to region 1.
Device d0r1z0-127.0.0.1:6001R127.0.0.1:6001/sda_"" with 1.0 weight got id 0
WARNING: No region specified for z1-127.0.0.1:6001/sdb. Defaulting to region 1.
Device d1r1z1-127.0.0.1:6001R127.0.0.1:6001/sdb_"" with 1.0 weight got id 1
WARNING: No region specified for z2-127.0.0.1:6001/sdc. Defaulting to region 1.
Device d2r1z2-127.0.0.1:6001R127.0.0.1:6001/sdc_"" with 1.0 weight got id 2
WARNING: No region specified for z0-127.0.0.1:6002/sda. Defaulting to region 1.
Device d0r1z0-127.0.0.1:6002R127.0.0.1:6002/sda_"" with 1.0 weight got id 0
WARNING: No region specified for z1-127.0.0.1:6002/sdb. Defaulting to region 1.
Device d1r1z1-127.0.0.1:6002R127.0.0.1:6002/sdb_"" with 1.0 weight got id 1
WARNING: No region specified for z2-127.0.0.1:6002/sdc. Defaulting to region 1.
Device d2r1z2-127.0.0.1:6002R127.0.0.1:6002/sdc_"" with 1.0 weight got id 2
Reassigned 1 (100.00%) partitions. Balance is now 0.00.
Reassigned 1 (100.00%) partitions. Balance is now 0.00.
Reassigned 1 (100.00%) partitions. Balance is now 0.00.
/home/vagrant/swift3/swift3/test/functional
Start account-server.
Start container-server.
Start object-server.
Start proxy-server.
PLATFORM -- Linux/x86_64 dev 3.2.0-74-virtual

001 Last Used:3s. GET Service [failed, exit status 1] - output mismatch (see 001.out.bad)
--- 001.out 2015-01-15 04:36:00.732542769 +0000
+++ 001.out.bad 2015-01-15 04:53:43.810373149 +0000
@@ -1,29 +1,7 @@
 QA output created by 001
-> s3curl --id tester -- -X PUT http://SWIFT_HOST/abcdefghijklmnopqrstuvwxyz_01234... 200
-> s3curl --id tester -- -X PUT http://SWIFT_HOST/5ABCDEFGHIJKLMNOPQRSTUVWXYZ.5-6789... 200
-> s3curl --id tester -- -X GET -D - http://SWIFT_HOST/... 200
-HTTP/1.1 200 OK
-Content-Length: LENGTH
-Content-Type: application/xml
-Date: DATE
-x-amz-id-2: TXID
-x-amz-request-id: TXID
-X-Trans-Id: TXID
-
-<?xml version='1.0' encoding='UTF-8'?>
-<ListAllMyBucketsResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
- <Owner>
- <ID>TESTER</ID>
- <DisplayName>TESTER</DisplayName>
- </Owner>
- <Buckets>
- <Bucket>
- <Name>5ABCDEFGHIJKLMNOPQRSTUVWXYZ.5-6789</Name>
- <CreationDate>DATE</CreationDate>
- </Bucket>
- <Bucket>
- <Name>abcdefghijklmnopqrstuvwxyz_01234</Name>
- <CreationDate>DATE</CreationDate>
- </Bucket>
- </Buckets>
-</ListAllMyBucketsResult>
+try again
+try again
+try again
+try again
+try again
+FAILED: _sw_post /<html><h1>Unauthorized</h1><p>This -H x-versions-location: <html><h1>Unauthorized</h1><p>This
002 Last Used:2s. PUT Bucket [failed, exit status 1] - output mismatch (see 002.out.bad)
--- 002.out 2015-01-15 04:36:00.732542769 +0000
+++ 002.out.bad 2015-01-15 04:53:49.010374479 +0000
@@ -1,13 +1,7 @@
 QA output created by 002
-> s3curl --id tester -- -X PUT -D - -T /TMP.default.xml http://SWIFT_HOST/bucket... 200
-HTTP/1.1 100 Continue
-
-HTTP/1.1 200 OK
-Content-Length: LENGTH
-Content-Type: text/html; charset=UTF-8
-Date: DATE
-Location: /bucket
-x-amz-id-2: TXID
-x-amz-request-id: TXID
-X-Trans-Id: TXID
-
+try again
+try again
+try again
+try again
+try again
+FAILED: _sw_post /<html><h1>Unauthorized</h1><p>This -H x-versions-location: <html><h1>Unauthorized</h1><p>This
003 Last Used:3s. GET Bucket [failed, exit status 1] - output mismatch (see 003.out.bad)
--- 003.out 2015-01-15 04:36:00.732542769 +0000
+++ 003.out.bad 2015-01-15 04:53:54.190377389 +0000
@@ -1,31 +1,7 @@
 QA output created by 003
-> s3curl --id tester -- -X PUT http://SWIFT_HOST/bucket... 200
-> s3curl --id tester -- -X PUT -T /dev/null http://SWIFT_HOST/bucket/sample.jpg... 200
-> s3curl --id tester -- -X PUT -T /dev/null http://SWIFT_HOST/bucket/photos/2006/January/sample.jpg... 200
-> s3curl --id tester -- -X PUT -T /dev/null http://SWIFT_HOST/bucket/photos/2006/February/sample2.jpg... 200
-> s3curl --id tester -- -X PUT -T /dev/null http://SWIFT_HOST/bucket/photos/2006/February/sample3.jpg... 200
-> s3curl --id tester -- -X PUT -T /dev/null http://SWIFT_HOST/bucket/pho/2006/February/sample4.jpg... 200
-> s3curl --id tester -- -X GET -D - http://SWIFT_HOST/bucket?delimiter=/&prefix=photos/2006/... 200
-HTTP/1.1 200 OK
-Content-Length: LENGTH
-Content-Type: application/xml
-Date: DATE
-x-amz-id-2: TXID
-x-amz-request-id: TXID
-X-Trans-Id: TXID
-
-<?xml version='1.0' encoding='UTF-8'?>
-<ListBucketResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
- <Name>bucket</Name>
- <Prefix>photos/2006/</Prefix>
- <Marker/>
- <MaxKeys>1000</MaxKeys>
- <Delimiter>/</Delimiter>
- <IsTruncated>false</IsTruncated>
- <CommonPrefixes>
- <Prefix>photos/2006/February/</Prefix>
- </CommonPrefixes>
- <CommonPrefixes>
- <Prefix>photos/2006/January/</Prefix>
- </CommonPrefixes>
-</ListBucketResult>
+try again
+try again
+try again
+try again
+try again
+FAILED: _sw_post /<html><h1>Unauthorized</h1><p>This -H x-versions-location: <html><h1>Unauthorized</h1><p>This
Failures: 001 002 003
Failed 3 of 3 tests
Name Stmts Miss Branch BrMiss Cover
----------------------------------------------------------------------------------------
/home/vagrant/swift3/swift3/__init__ 9 3 0 0 67%
/home/vagrant/swift3/swift3/acl_handlers 132 98 44 44 19%
/home/vagrant/swift3/swift3/cfg 26 7 14 7 65%
/home/vagrant/swift3/swift3/controllers/__init__ 12 0 0 0 100%
/home/vagrant/swift3/swift3/controllers/acl 99 84 36 36 11%
/home/vagrant/swift3/swift3/controllers/base 31 13 8 6 51%
/home/vagrant/swift3/swift3/controllers/bucket 86 71 32 32 13%
/home/vagrant/swift3/swift3/controllers/location 12 6 2 2 43%
/home/vagrant/swift3/swift3/controllers/logging 11 5 0 0 55%
/home/vagrant/swift3/swift3/controllers/multi_delete 68 59 20 20 10%
/home/vagrant/swift3/swift3/controllers/multi_upload 235 212 50 50 8%
/home/vagrant/swift3/swift3/controllers/obj 55 42 16 16 18%
/home/vagrant/swift3/swift3/controllers/s3_acl 20 13 2 2 32%
/home/vagrant/swift3/swift3/controllers/service 21 14 4 4 28%
/home/vagrant/swift3/swift3/controllers/versioning 11 5 0 0 55%
/home/vagrant/swift3/swift3/etree 70 47 20 20 26%
/home/vagrant/swift3/swift3/exception 10 0 0 0 100%
/home/vagrant/swift3/swift3/middleware 77 33 24 18 50%
/home/vagrant/swift3/swift3/request 382 320 196 194 11%
/home/vagrant/swift3/swift3/response 355 87 45 45 67%
/home/vagrant/swift3/swift3/subresource 242 172 81 81 22%
/home/vagrant/swift3/swift3/utils 46 27 15 15 31%
----------------------------------------------------------------------------------------
TOTAL 2010 1318 609 592 27%
ERROR: InvocationError: '/bin/bash swift3/test/functional/run_test.sh'
___________________________________________________________ summary ___________________________________________________________
ERROR: tempauth: commands failed

Revision history for this message
Kota Tsuyuzaki (tsuyuzaki-kota) wrote :

I could hit a similar bug at keystone functional test in my environment.

I noticed account/container/obj servers didn't run at the tests but I've not confirm yet why those failures ware happened.
Did it also occur in your environment?

Revision history for this message
Kota Tsuyuzaki (tsuyuzaki-kota) wrote :

I reverted my comment because my swift3 hit an issue from apparently my keystone environ so I think your issue would come from another reason. Sorry.

Revision history for this message
Charles Hsu (charles0126) wrote :
Download full text (5.5 KiB)

I think it needs improve (functional test). Do you known who is working on it? Or I could rewrite all of that?

I saw the problem of account/container/object servers didn't run before.
The message likes this
============
$ tox -e tempauth
tempauth develop-inst-noop: /home/vagrant/swift3
tempauth runtests: PYTHONHASHSEED='4071036354'
tempauth runtests: commands[0] | /bin/bash swift3/test/functional/run_test.sh
WARNING: No region specified for z0-127.0.0.1:6000/sda. Defaulting to region 1.
Device d0r1z0-127.0.0.1:6000R127.0.0.1:6000/sda_"" with 1.0 weight got id 0
WARNING: No region specified for z1-127.0.0.1:6000/sdb. Defaulting to region 1.
Device d1r1z1-127.0.0.1:6000R127.0.0.1:6000/sdb_"" with 1.0 weight got id 1
WARNING: No region specified for z2-127.0.0.1:6000/sdc. Defaulting to region 1.
Device d2r1z2-127.0.0.1:6000R127.0.0.1:6000/sdc_"" with 1.0 weight got id 2
WARNING: No region specified for z0-127.0.0.1:6001/sda. Defaulting to region 1.
Device d0r1z0-127.0.0.1:6001R127.0.0.1:6001/sda_"" with 1.0 weight got id 0
WARNING: No region specified for z1-127.0.0.1:6001/sdb. Defaulting to region 1.
Device d1r1z1-127.0.0.1:6001R127.0.0.1:6001/sdb_"" with 1.0 weight got id 1
WARNING: No region specified for z2-127.0.0.1:6001/sdc. Defaulting to region 1.
Device d2r1z2-127.0.0.1:6001R127.0.0.1:6001/sdc_"" with 1.0 weight got id 2
WARNING: No region specified for z0-127.0.0.1:6002/sda. Defaulting to region 1.
Device d0r1z0-127.0.0.1:6002R127.0.0.1:6002/sda_"" with 1.0 weight got id 0
WARNING: No region specified for z1-127.0.0.1:6002/sdb. Defaulting to region 1.
Device d1r1z1-127.0.0.1:6002R127.0.0.1:6002/sdb_"" with 1.0 weight got id 1
WARNING: No region specified for z2-127.0.0.1:6002/sdc. Defaulting to region 1.
Device d2r1z2-127.0.0.1:6002R127.0.0.1:6002/sdc_"" with 1.0 weight got id 2
Reassigned 1 (100.00%) partitions. Balance is now 0.00.
Reassigned 1 (100.00%) partitions. Balance is now 0.00.
Reassigned 1 (100.00%) partitions. Balance is now 0.00.
/home/vagrant/swift3/swift3/test/functional
Start account-server.
Start container-server.
Start object-server.
Start proxy-server.

Coverage.py warning: No data was collected.
Traceback (most recent call last):
  File "./run_daemon.py", line 30, in <module>
  File "/home/vagrant/swift3/.tox/tempauth/local/lib/python2.7/site-packages/swift/common/wsgi.py", line 432, in run_wsgi
    loadapp(conf_path, global_conf=global_conf)
  File "/home/vagrant/swift3/.tox/tempauth/local/lib/python2.7/site-packages/swift/common/wsgi.py", line 352, in loadapp
    ctx = loadcontext(loadwsgi.APP, conf_file, global_conf=global_conf)
  File "/home/vagrant/swift3/.tox/tempauth/local/lib/python2.7/site-packages/swift/common/wsgi.py", line 336, in loadcontext
    global_conf=global_conf)
  File "/home/vagrant/swift3/.tox/tempauth/local/lib/python2.7/site-packages/paste/deploy/loadwsgi.py", line 296, in loadcontext
    global_conf=global_conf)
  File "/home/vagrant/swift3/.tox/tempauth/local/lib/python2.7/site-packages/paste/deploy/loadwsgi.py", line 320, in _loadconfig
    return loader.get_context(object_type, name, global_conf)
  File "/home/vagrant/swift3/.tox/tempauth/local/lib/python2.7/site-packages/swift/common...

Read more...

Revision history for this message
Kota Tsuyuzaki (tsuyuzaki-kota) wrote :

I don't think someone is working for that so it sound great if you could make a effort for the issue.

There is also a port conflict failure scenario at the functional tests.

i.e.
- run swift account/container/object with 6000~6002 port (e.g. swift-init in out of the functional tests)
- run the functional tests by tox
- fail to launch account/container/object by port conflict
- fail the functional tests

Jeff Burns (jburns-f)
summary: - Funcational test failure - tempauth
+ Functional test failure - tempauth
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.