[jira] [Updated] (FLINK-26115) Multiple Kafka connector tests failed due to The topic metadata failed to propagate to Kafka broker
[ https://issues.apache.org/jira/browse/FLINK-26115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-26115: --- Labels: auto-deprioritized-critical auto-deprioritized-major auto-deprioritized-minor test-stability (was: auto-deprioritized-critical auto-deprioritized-major stale-minor test-stability) Priority: Not a Priority (was: Minor) This issue was labeled "stale-minor" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Minor, please raise the priority and ask a committer to assign you the issue or revive the public discussion. > Multiple Kafka connector tests failed due to The topic metadata failed to > propagate to Kafka broker > --- > > Key: FLINK-26115 > URL: https://issues.apache.org/jira/browse/FLINK-26115 > Project: Flink > Issue Type: Bug > Components: Connectors / Kafka >Affects Versions: 1.13.5, 1.14.3, 1.15.0 >Reporter: Yun Gao >Priority: Not a Priority > Labels: auto-deprioritized-critical, auto-deprioritized-major, > auto-deprioritized-minor, test-stability > > This issues tracks all the related issues with "The topic metadata failed to > propagate to Kafka broker" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-26115) Multiple Kafka connector tests failed due to The topic metadata failed to propagate to Kafka broker
[ https://issues.apache.org/jira/browse/FLINK-26115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-26115: --- Labels: auto-deprioritized-critical auto-deprioritized-major stale-minor test-stability (was: auto-deprioritized-critical auto-deprioritized-major test-stability) I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > Multiple Kafka connector tests failed due to The topic metadata failed to > propagate to Kafka broker > --- > > Key: FLINK-26115 > URL: https://issues.apache.org/jira/browse/FLINK-26115 > Project: Flink > Issue Type: Bug > Components: Connectors / Kafka >Affects Versions: 1.13.5, 1.14.3, 1.15.0 >Reporter: Yun Gao >Priority: Minor > Labels: auto-deprioritized-critical, auto-deprioritized-major, > stale-minor, test-stability > > This issues tracks all the related issues with "The topic metadata failed to > propagate to Kafka broker" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-26115) Multiple Kafka connector tests failed due to The topic metadata failed to propagate to Kafka broker
[ https://issues.apache.org/jira/browse/FLINK-26115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-26115: --- Labels: auto-deprioritized-critical auto-deprioritized-major test-stability (was: auto-deprioritized-critical stale-major test-stability) Priority: Minor (was: Major) This issue was labeled "stale-major" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Major, please raise the priority and ask a committer to assign you the issue or revive the public discussion. > Multiple Kafka connector tests failed due to The topic metadata failed to > propagate to Kafka broker > --- > > Key: FLINK-26115 > URL: https://issues.apache.org/jira/browse/FLINK-26115 > Project: Flink > Issue Type: Bug > Components: Connectors / Kafka >Affects Versions: 1.13.5, 1.14.3, 1.15.0 >Reporter: Yun Gao >Priority: Minor > Labels: auto-deprioritized-critical, auto-deprioritized-major, > test-stability > > This issues tracks all the related issues with "The topic metadata failed to > propagate to Kafka broker" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-26115) Multiple Kafka connector tests failed due to The topic metadata failed to propagate to Kafka broker
[ https://issues.apache.org/jira/browse/FLINK-26115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-26115: --- Labels: auto-deprioritized-critical stale-major test-stability (was: auto-deprioritized-critical test-stability) I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 60 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > Multiple Kafka connector tests failed due to The topic metadata failed to > propagate to Kafka broker > --- > > Key: FLINK-26115 > URL: https://issues.apache.org/jira/browse/FLINK-26115 > Project: Flink > Issue Type: Bug > Components: Connectors / Kafka >Affects Versions: 1.13.5, 1.14.3, 1.15.0 >Reporter: Yun Gao >Priority: Major > Labels: auto-deprioritized-critical, stale-major, test-stability > > This issues tracks all the related issues with "The topic metadata failed to > propagate to Kafka broker" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-26115) Multiple Kafka connector tests failed due to The topic metadata failed to propagate to Kafka broker
[ https://issues.apache.org/jira/browse/FLINK-26115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-26115: --- Labels: auto-deprioritized-critical test-stability (was: stale-critical test-stability) Priority: Major (was: Critical) This issue was labeled "stale-critical" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Critical, please raise the priority and ask a committer to assign you the issue or revive the public discussion. > Multiple Kafka connector tests failed due to The topic metadata failed to > propagate to Kafka broker > --- > > Key: FLINK-26115 > URL: https://issues.apache.org/jira/browse/FLINK-26115 > Project: Flink > Issue Type: Bug > Components: Connectors / Kafka >Affects Versions: 1.15.0, 1.13.5, 1.14.3 >Reporter: Yun Gao >Priority: Major > Labels: auto-deprioritized-critical, test-stability > > This issues tracks all the related issues with "The topic metadata failed to > propagate to Kafka broker" -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FLINK-26115) Multiple Kafka connector tests failed due to The topic metadata failed to propagate to Kafka broker
[ https://issues.apache.org/jira/browse/FLINK-26115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-26115: --- Labels: stale-critical test-stability (was: test-stability) I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Critical but is unassigned and neither itself nor its Sub-Tasks have been updated for 14 days. I have gone ahead and marked it "stale-critical". If this ticket is critical, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > Multiple Kafka connector tests failed due to The topic metadata failed to > propagate to Kafka broker > --- > > Key: FLINK-26115 > URL: https://issues.apache.org/jira/browse/FLINK-26115 > Project: Flink > Issue Type: Bug > Components: Connectors / Kafka >Affects Versions: 1.15.0, 1.13.5, 1.14.3 >Reporter: Yun Gao >Priority: Critical > Labels: stale-critical, test-stability > > This issues tracks all the related issues with "The topic metadata failed to > propagate to Kafka broker" -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FLINK-26115) Multiple Kafka connector tests failed due to The topic metadata failed to propagate to Kafka broker
[ https://issues.apache.org/jira/browse/FLINK-26115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Gao updated FLINK-26115: Priority: Critical (was: Major) > Multiple Kafka connector tests failed due to The topic metadata failed to > propagate to Kafka broker > --- > > Key: FLINK-26115 > URL: https://issues.apache.org/jira/browse/FLINK-26115 > Project: Flink > Issue Type: Bug > Components: Connectors / Kafka >Affects Versions: 1.15.0, 1.13.5, 1.14.3 >Reporter: Yun Gao >Priority: Critical > Labels: test-stability > > This issues tracks all the related issues with "The topic metadata failed to > propagate to Kafka broker" -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FLINK-26115) Multiple Kafka connector tests failed due to The topic metadata failed to propagate to Kafka broker
[ https://issues.apache.org/jira/browse/FLINK-26115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Gao updated FLINK-26115: Component/s: Connectors / Kafka > Multiple Kafka connector tests failed due to The topic metadata failed to > propagate to Kafka broker > --- > > Key: FLINK-26115 > URL: https://issues.apache.org/jira/browse/FLINK-26115 > Project: Flink > Issue Type: Bug > Components: Connectors / Kafka >Affects Versions: 1.15.0, 1.13.5, 1.14.3 >Reporter: Yun Gao >Priority: Major > Labels: test-stability > > This issues tracks all the related issues with "The topic metadata failed to > propagate to Kafka broker" -- This message was sent by Atlassian Jira (v8.20.1#820001)
