[jira] [Assigned] (CASSANDRA-16238) Fix flaky test test_insert_data_during_replace_same_address - replace_address_test.TestReplaceAddress
[
https://issues.apache.org/jira/browse/CASSANDRA-16238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Holmberg reassigned CASSANDRA-16238:
-
Assignee: Adam Holmberg
> Fix flaky test test_insert_data_during_replace_same_address -
> replace_address_test.TestReplaceAddress
> -
>
> Key: CASSANDRA-16238
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16238
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: David Capwell
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
>
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/745/workflows/1c7e589e-b5af-4a56-b40a-43da424602c7/jobs/4231
> {code}
> test teardown failure
> Unexpected error found in node logs (see stdout for full details). Errors:
> [ERROR [main] 2020-10-29 17:38:13,808 CassandraDaemon.java:817 - Exception
> encountered during startup
> java.lang.IllegalStateException: Unable to contact any seeds!
> at
> org.apache.cassandra.service.StorageService.bootstrap(StorageService.java:1601)
> at
> org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:931)
> at
> org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:892)
> at
> org.apache.cassandra.service.StorageService.initServer(StorageService.java:699)
> at
> org.apache.cassandra.service.StorageService.initServer(StorageService.java:635)
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:407)
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:671)
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:795),
> ERROR [main] 2020-10-29 17:38:13,808 CassandraDaemon.java:817 - Exception
> encountered during startup
> java.lang.IllegalStateException: Unable to contact any seeds!
> at
> org.apache.cassandra.service.StorageService.bootstrap(StorageService.java:1601)
> at
> org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:931)
> at
> org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:892)
> at
> org.apache.cassandra.service.StorageService.initServer(StorageService.java:699)
> at
> org.apache.cassandra.service.StorageService.initServer(StorageService.java:635)
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:407)
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:671)
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:795)]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15962) Digest for some queries is different depending whether the data are retrieved from sstable or memtable
[
https://issues.apache.org/jira/browse/CASSANDRA-15962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17260067#comment-17260067
]
Benjamin Lerer commented on CASSANDRA-15962:
[~kornelpal] The latest patches have not been reviewed and approed yet. I
started the review earlier today and will probably be done tomorrow. Some
changes might be needed.
> Digest for some queries is different depending whether the data are retrieved
> from sstable or memtable
> --
>
> Key: CASSANDRA-15962
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15962
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Coordination
>Reporter: Jacek Lewandowski
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 3.11.x, 4.0-beta
>
> Attachments: DigestTest.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Not sure into which category should I assign this ticket.
>
> Basically when reading using certain column filters, the digest is different
> depending whether we read from sstable and memtable. This happens on
> {{trunk}} and {{cassandra-3.11}} branches. However it works properly on
> {{cassandra-3.0}} branch.
>
> I'm attaching a simple test for trunk to demonstrate what I mean.
>
> Please verify my test and my conclusions
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15962) Digest for some queries is different depending whether the data are retrieved from sstable or memtable
[
https://issues.apache.org/jira/browse/CASSANDRA-15962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17260056#comment-17260056
]
Kornel Pal commented on CASSANDRA-15962:
Thank you [~jlewandowski] for fixing both issues you have found. Now that
CASSANDRA-16223 was committed and released, I wonder whether anything else is
blocking this fix in CASSANDRA-15962.
> Digest for some queries is different depending whether the data are retrieved
> from sstable or memtable
> --
>
> Key: CASSANDRA-15962
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15962
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Coordination
>Reporter: Jacek Lewandowski
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 3.11.x, 4.0-beta
>
> Attachments: DigestTest.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Not sure into which category should I assign this ticket.
>
> Basically when reading using certain column filters, the digest is different
> depending whether we read from sstable and memtable. This happens on
> {{trunk}} and {{cassandra-3.11}} branches. However it works properly on
> {{cassandra-3.0}} branch.
>
> I'm attaching a simple test for trunk to demonstrate what I mean.
>
> Please verify my test and my conclusions
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-16322) Fix failing python update dtests
[ https://issues.apache.org/jira/browse/CASSANDRA-16322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Holmberg reassigned CASSANDRA-16322: - Assignee: Adam Holmberg > Fix failing python update dtests > > > Key: CASSANDRA-16322 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16322 > Project: Cassandra > Issue Type: Task > Components: CI, Test/dtest/python >Reporter: David Capwell >Assignee: Adam Holmberg >Priority: Normal > Fix For: 4.0-beta > > > https://app.circleci.com/pipelines/github/dcapwell/cassandra/841/workflows/bcadf6e6-8d04-4010-8a47-99f7f9b5ac1d/jobs/4949/parallel-runs/23?filterBy=ALL > Over 600 upgrade tests are failing, this ticket is to root cause each failure > and fix the issues (in different tickets). -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16331) Fix upgrade python dtest test_keys_index_3_x_created - upgrade_tests.thrift_upgrade_test.TestUpgradeTo40
[
https://issues.apache.org/jira/browse/CASSANDRA-16331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Holmberg updated CASSANDRA-16331:
--
Test and Documentation Plan: run existing ci
Status: Patch Available (was: In Progress)
> Fix upgrade python dtest test_keys_index_3_x_created -
> upgrade_tests.thrift_upgrade_test.TestUpgradeTo40
>
>
> Key: CASSANDRA-16331
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16331
> Project: Cassandra
> Issue Type: Bug
> Components: CI, Test/dtest/python
>Reporter: David Capwell
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
>
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/843/workflows/9545f259-0a61-4ba8-8dea-485a33136032/jobs/4964
> {code}
> test setup failure
> file /home/cassandra/cassandra-dtest/upgrade_tests/thrift_upgrade_test.py,
> line 454
> def test_keys_index_3_x_created(self, from_version):
> E fixture 'from_version' not found
> > available fixtures: cache, capfd, capfdbinary, caplog, capsys,
> > capsysbinary, doctest_namespace, dtest_config, fixture_dtest_cluster_name,
> > fixture_dtest_create_cluster_func, fixture_dtest_setup,
> > fixture_dtest_setup_overrides, fixture_log_test_name_and_date,
> > fixture_logging_setup, fixture_maybe_skip_tests_requiring_novnodes,
> > fixture_ported_to_in_jvm, fixture_since, fixture_skip_version,
> > install_debugging_signal_handler, log_global_env_facts, monkeypatch,
> > pytestconfig, record_property, record_xml_attribute, record_xml_property,
> > recwarn, set_dtest_setup_on_function, tmpdir, tmpdir_factory
> > use 'pytest --fixtures [testpath]' for help on them.
> /home/cassandra/cassandra-dtest/upgrade_tests/thrift_upgrade_test.py:454
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16283) Incorrect output in "nodetool status -r"
[
https://issues.apache.org/jira/browse/CASSANDRA-16283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17259947#comment-17259947
]
Adam Holmberg commented on CASSANDRA-16283:
---
Thanks for taking a look at this, and for the patch. I reviewed and left a few
comments on the PR.
While looking at this I think I noticed one other potential flaw around looking
things up by endpoint (unrelated the resolved host lookup logic). It seems like
the tool is never showing anything definitive for the "Owns (effective)"
column. Resolved or not, the table always just produces '?'.
> Incorrect output in "nodetool status -r"
>
>
> Key: CASSANDRA-16283
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16283
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/nodetool
>Reporter: Yakir Gibraltar
>Assignee: Scott Wolfenhaut
>Priority: Low
> Fix For: 4.0-beta
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> nodetool status -r not working well on C* 4,
> Version:
> {code:java}
> [root@foo001 ~]# nodetool version
> ReleaseVersion: 4.0-beta3
> {code}
> Without resolving:
> {code:java}
> [root@foo001 ~]# nodetool status
> Datacenter: V4CH
>
> Status=Up/Down
> |/ State=Normal/Leaving/Joining/Moving
> -- Address LoadTokens Owns(effective) Host ID
> Rack
> UN 1.2.3.4 363.68 KiB 128 ?
> 92ae4c39-edb3-4e67-8623-b49fd8301b66 RAC1
> UN 1.2.3.5 109.71 KiB 128 ?
> d80647a8-32b2-4a8f-8022-f5ae3ce8fbb2 RAC1
> {code}
> With resolving:
> {code:java}
> [root@foo001 ~]# nodetool status -r
> Datacenter: V4CH
>
> Status=Up/Down
> |/ State=Normal/Leaving/Joining/Moving
> -- Address Load Tokens Owns (effective) Host ID Rack
> ?N foo001.tab.com ? 128 ? RAC1
> ?N foo002.tab.com ? 128 ? RAC1
> {code}
> I only changed here IPs and hostnames.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16283) Incorrect output in "nodetool status -r"
[
https://issues.apache.org/jira/browse/CASSANDRA-16283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Holmberg updated CASSANDRA-16283:
--
Reviewers: Adam Holmberg, Adam Holmberg (was: Adam Holmberg)
Adam Holmberg, Adam Holmberg (was: Adam Holmberg)
Status: Review In Progress (was: Patch Available)
> Incorrect output in "nodetool status -r"
>
>
> Key: CASSANDRA-16283
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16283
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/nodetool
>Reporter: Yakir Gibraltar
>Assignee: Scott Wolfenhaut
>Priority: Low
> Fix For: 4.0-beta
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> nodetool status -r not working well on C* 4,
> Version:
> {code:java}
> [root@foo001 ~]# nodetool version
> ReleaseVersion: 4.0-beta3
> {code}
> Without resolving:
> {code:java}
> [root@foo001 ~]# nodetool status
> Datacenter: V4CH
>
> Status=Up/Down
> |/ State=Normal/Leaving/Joining/Moving
> -- Address LoadTokens Owns(effective) Host ID
> Rack
> UN 1.2.3.4 363.68 KiB 128 ?
> 92ae4c39-edb3-4e67-8623-b49fd8301b66 RAC1
> UN 1.2.3.5 109.71 KiB 128 ?
> d80647a8-32b2-4a8f-8022-f5ae3ce8fbb2 RAC1
> {code}
> With resolving:
> {code:java}
> [root@foo001 ~]# nodetool status -r
> Datacenter: V4CH
>
> Status=Up/Down
> |/ State=Normal/Leaving/Joining/Moving
> -- Address Load Tokens Owns (effective) Host ID Rack
> ?N foo001.tab.com ? 128 ? RAC1
> ?N foo002.tab.com ? 128 ? RAC1
> {code}
> I only changed here IPs and hostnames.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-9215) Test with degraded or unreliable networks
[ https://issues.apache.org/jira/browse/CASSANDRA-9215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17259926#comment-17259926 ] Daniel Schulz commented on CASSANDRA-9215: -- What is the expected deliverable in the end? Is a document on test settings, C* configuration and the queries a valid approach? So applying the scientific method with hypothesis, experiment and outcomes...? > Test with degraded or unreliable networks > - > > Key: CASSANDRA-9215 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9215 > Project: Cassandra > Issue Type: Improvement > Components: Legacy/Testing >Reporter: Ariel Weisberg >Priority: Normal > > I have tried to test WAN replication using routing nodes with various > configurations to simulate a bad network and not had good results with > realistically reproducing a WAN performance. The fake WAN performed better > than the real one. > I think we need to do at least some of our testing over a link between data > centers that are at least as distance as US East <-> US West. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16188) Add more tests to cover Keyspace and Table metrics
[ https://issues.apache.org/jira/browse/CASSANDRA-16188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Lerer updated CASSANDRA-16188: --- Reviewers: Benjamin Lerer > Add more tests to cover Keyspace and Table metrics > --- > > Key: CASSANDRA-16188 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16188 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest/java, Test/unit >Reporter: Benjamin Lerer >Assignee: Sumanth Pasupuleti >Priority: Normal > Fix For: 4.0-rc > > > Several Keyspace and Table related metrics are currently not tested. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16216) Add tests to cover ClientMetrics metrics
[ https://issues.apache.org/jira/browse/CASSANDRA-16216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Lerer updated CASSANDRA-16216: --- Reviewers: Benjamin Lerer > Add tests to cover ClientMetrics metrics > > > Key: CASSANDRA-16216 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16216 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest/java, Test/unit >Reporter: Sumanth Pasupuleti >Assignee: Sumanth Pasupuleti >Priority: Normal > Fix For: 4.0-rc > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16216) Add tests to cover ClientMetrics metrics
[ https://issues.apache.org/jira/browse/CASSANDRA-16216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17259870#comment-17259870 ] Sumanth Pasupuleti commented on CASSANDRA-16216: Working branch: https://github.com/apache/cassandra/compare/trunk...sumanth-pasupuleti:16216_40?expand=1 > Add tests to cover ClientMetrics metrics > > > Key: CASSANDRA-16216 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16216 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest/java, Test/unit >Reporter: Sumanth Pasupuleti >Assignee: Sumanth Pasupuleti >Priority: Normal > Fix For: 4.0-rc > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16188) Add more tests to cover Keyspace and Table metrics
[ https://issues.apache.org/jira/browse/CASSANDRA-16188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17259868#comment-17259868 ] Sumanth Pasupuleti commented on CASSANDRA-16188: Working branch: https://github.com/apache/cassandra/compare/trunk...sumanth-pasupuleti:16188_40?expand=1 > Add more tests to cover Keyspace and Table metrics > --- > > Key: CASSANDRA-16188 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16188 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest/java, Test/unit >Reporter: Benjamin Lerer >Assignee: Sumanth Pasupuleti >Priority: Normal > Fix For: 4.0-rc > > > Several Keyspace and Table related metrics are currently not tested. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16373) Deploy testing docker images to hub.docker.com/u/apache/
[ https://issues.apache.org/jira/browse/CASSANDRA-16373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17259657#comment-17259657 ] Sam Tunnicliffe commented on CASSANDRA-16373: - The cassandra-builds patch LGTM & builds images correctly (tested by publishing to personal repos & running Circle pipelines). The in-tree patches seem correct, but before merging they'll need updating with the correct tags after the images are actually published. > Deploy testing docker images to hub.docker.com/u/apache/ > - > > Key: CASSANDRA-16373 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16373 > Project: Cassandra > Issue Type: Task > Components: Test/dtest/java, Test/dtest/python, Test/unit >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > > INFRA-21103 demonstrates PMC individuals can get access to the apache > organisation on dockerhub (and the dockerhub "cassandra" team). > We have a number of docker images (used in testing and CI) that are currently > deployed under individual user accounts on dockerhub. These can now be > deployed under https://hub.docker.com/u/apache -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16373) Deploy testing docker images to hub.docker.com/u/apache/
[ https://issues.apache.org/jira/browse/CASSANDRA-16373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-16373: Status: Changes Suggested (was: Review In Progress) > Deploy testing docker images to hub.docker.com/u/apache/ > - > > Key: CASSANDRA-16373 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16373 > Project: Cassandra > Issue Type: Task > Components: Test/dtest/java, Test/dtest/python, Test/unit >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > > INFRA-21103 demonstrates PMC individuals can get access to the apache > organisation on dockerhub (and the dockerhub "cassandra" team). > We have a number of docker images (used in testing and CI) that are currently > deployed under individual user accounts on dockerhub. These can now be > deployed under https://hub.docker.com/u/apache -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16373) Deploy testing docker images to hub.docker.com/u/apache/
[ https://issues.apache.org/jira/browse/CASSANDRA-16373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-16373: Reviewers: Sam Tunnicliffe Status: Review In Progress (was: Patch Available) > Deploy testing docker images to hub.docker.com/u/apache/ > - > > Key: CASSANDRA-16373 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16373 > Project: Cassandra > Issue Type: Task > Components: Test/dtest/java, Test/dtest/python, Test/unit >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > > INFRA-21103 demonstrates PMC individuals can get access to the apache > organisation on dockerhub (and the dockerhub "cassandra" team). > We have a number of docker images (used in testing and CI) that are currently > deployed under individual user accounts on dockerhub. These can now be > deployed under https://hub.docker.com/u/apache -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16373) Deploy testing docker images to hub.docker.com/u/apache/
[ https://issues.apache.org/jira/browse/CASSANDRA-16373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16373: --- Description: INFRA-21103 demonstrates PMC individuals can get access to the apache organisation on dockerhub (and the dockerhub "cassandra" team). We have a number of docker images (used in testing and CI) that are currently deployed under individual user accounts on dockerhub. These can now be deployed under https://hub.docker.com/u/apache was: INFRA-21103 demonstrates PMC individuals can get access to the apache organisation on dockerhub (and the cassandra team). We have a number of docker images (used in testing and CI) that are currently deployed under individual user accounts on dockerhub. These can now be deployed under https://hub.docker.com/u/apache > Deploy testing docker images to hub.docker.com/u/apache/ > - > > Key: CASSANDRA-16373 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16373 > Project: Cassandra > Issue Type: Task > Components: Test/dtest/java, Test/dtest/python, Test/unit >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > > INFRA-21103 demonstrates PMC individuals can get access to the apache > organisation on dockerhub (and the dockerhub "cassandra" team). > We have a number of docker images (used in testing and CI) that are currently > deployed under individual user accounts on dockerhub. These can now be > deployed under https://hub.docker.com/u/apache -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16373) Deploy testing docker images to hub.docker.com/u/apache/
[ https://issues.apache.org/jira/browse/CASSANDRA-16373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16373: --- Test and Documentation Plan: Once INFRA-21103 is resolved, deploy images to new repositories and run circleci and ci-cassandra CI Status: Patch Available (was: In Progress) > Deploy testing docker images to hub.docker.com/u/apache/ > - > > Key: CASSANDRA-16373 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16373 > Project: Cassandra > Issue Type: Task > Components: Test/dtest/java, Test/dtest/python, Test/unit >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > > INFRA-21103 demonstrates PMC individuals can get access to the apache > organisation on dockerhub (and the cassandra team). > We have a number of docker images (used in testing and CI) that are currently > deployed under individual user accounts on dockerhub. These can now be > deployed under https://hub.docker.com/u/apache -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16373) Deploy testing docker images to hub.docker.com/u/apache/
[ https://issues.apache.org/jira/browse/CASSANDRA-16373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17259218#comment-17259218 ] Michael Semb Wever edited comment on CASSANDRA-16373 at 1/6/21, 8:25 AM: - cassandra-builds patch - https://github.com/apache/cassandra-builds/compare/trunk...thelastpickle:mck/16373 in-tree patches - trunk https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/trunk_16373 - cassandra-3.11 https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/cassandra-3.11_16373 - cassandra-3.0 https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/cassandra-3.0_16373 - cassandra-2.2 https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/cassandra-2.2_16373 was (Author: michaelsembwever): cassandra-builds patch at https://github.com/apache/cassandra-builds/compare/trunk...thelastpickle:mck/16373 in-tree trunk patch at https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/trunk_16373 (still need to do 2.2 3.0 3.11 branches) > Deploy testing docker images to hub.docker.com/u/apache/ > - > > Key: CASSANDRA-16373 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16373 > Project: Cassandra > Issue Type: Task > Components: Test/dtest/java, Test/dtest/python, Test/unit >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > > INFRA-21103 demonstrates PMC individuals can get access to the apache > organisation on dockerhub (and the cassandra team). > We have a number of docker images (used in testing and CI) that are currently > deployed under individual user accounts on dockerhub. These can now be > deployed under https://hub.docker.com/u/apache -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16373) Deploy testing docker images to hub.docker.com/u/apache/
[ https://issues.apache.org/jira/browse/CASSANDRA-16373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-16373: --- Description: INFRA-21103 demonstrates PMC individuals can get access to the apache organisation on dockerhub (and the cassandra team). We have a number of docker images (used in testing and CI) that are currently deployed under individual user accounts on dockerhub. These can now be deployed under https://hub.docker.com/u/apache was: INFRA-21103 has provided PMC individuals (upon request) access to the apache organisation on dockerhub (and the cassandra team). We have a number of docker images (used in testing and CI) that are currently deployed under individual user accounts on dockerhub. These can now be deployed under https://hub.docker.com/u/apache > Deploy testing docker images to hub.docker.com/u/apache/ > - > > Key: CASSANDRA-16373 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16373 > Project: Cassandra > Issue Type: Task > Components: Test/dtest/java, Test/dtest/python, Test/unit >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > > INFRA-21103 demonstrates PMC individuals can get access to the apache > organisation on dockerhub (and the cassandra team). > We have a number of docker images (used in testing and CI) that are currently > deployed under individual user accounts on dockerhub. These can now be > deployed under https://hub.docker.com/u/apache -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
