<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Problem: loss of firewall rules when reloading the firewalld service in Dynatrace Managed Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Problem-loss-of-firewall-rules-when-reloading-the-firewalld/m-p/214329#M2619</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Thank you for your anwser.&lt;/P&gt;&lt;P&gt;It isn't possible for us we had considered this solution but given the number of customers our system team did not see to manage specificities for each of them. And&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
    <pubDate>Wed, 07 Jun 2023 12:57:18 GMT</pubDate>
    <dc:creator>patrick_romee</dc:creator>
    <dc:date>2023-06-07T12:57:18Z</dc:date>
    <item>
      <title>Problem: loss of firewall rules when reloading the firewalld service</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Problem-loss-of-firewall-rules-when-reloading-the-firewalld/m-p/213826#M2617</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;When our infrastructure team performs deployments for patch management the command firewall-cmd --reload is executed.&amp;nbsp;The result is that all rules dynatrace in firewalld are destroyed.&lt;/P&gt;&lt;P&gt;Could you make the rules persistent to prevent this problem ?&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Patrick&lt;/P&gt;</description>
      <pubDate>Thu, 01 Jun 2023 12:44:35 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Problem-loss-of-firewall-rules-when-reloading-the-firewalld/m-p/213826#M2617</guid>
      <dc:creator>patrick_romee</dc:creator>
      <dc:date>2023-06-01T12:44:35Z</dc:date>
    </item>
    <item>
      <title>Re: Problem: loss of firewall rules when reloading the firewalld service</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Problem-loss-of-firewall-rules-when-reloading-the-firewalld/m-p/213848#M2618</link>
      <description>&lt;P&gt;Please align with your infrastructure team to ensure ./reconfigure.sh is run after system patching. This should apply required firewall rules at the cluster node.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Jun 2023 13:37:23 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Problem-loss-of-firewall-rules-when-reloading-the-firewalld/m-p/213848#M2618</guid>
      <dc:creator>Radoslaw_Szulgo</dc:creator>
      <dc:date>2023-06-01T13:37:23Z</dc:date>
    </item>
    <item>
      <title>Re: Problem: loss of firewall rules when reloading the firewalld service</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Problem-loss-of-firewall-rules-when-reloading-the-firewalld/m-p/214329#M2619</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Thank you for your anwser.&lt;/P&gt;&lt;P&gt;It isn't possible for us we had considered this solution but given the number of customers our system team did not see to manage specificities for each of them. And&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jun 2023 12:57:18 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Problem-loss-of-firewall-rules-when-reloading-the-firewalld/m-p/214329#M2619</guid>
      <dc:creator>patrick_romee</dc:creator>
      <dc:date>2023-06-07T12:57:18Z</dc:date>
    </item>
    <item>
      <title>Re: Problem: loss of firewall rules when reloading the firewalld service</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Problem-loss-of-firewall-rules-when-reloading-the-firewalld/m-p/214692#M2620</link>
      <description>&lt;P&gt;Would at least restart of the machine be possible? A restart of firewall service also recreates rules.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Jun 2023 09:35:42 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Problem-loss-of-firewall-rules-when-reloading-the-firewalld/m-p/214692#M2620</guid>
      <dc:creator>Radoslaw_Szulgo</dc:creator>
      <dc:date>2023-06-12T09:35:42Z</dc:date>
    </item>
    <item>
      <title>Re: Problem: loss of firewall rules when reloading the firewalld service</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Problem-loss-of-firewall-rules-when-reloading-the-firewalld/m-p/215109#M2621</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Yes it is, but our system team can't tell us when the reload is done so between&amp;nbsp; the reload and time when the problem is detected the cluster is unavailable even if the problem is detected rapidly&amp;nbsp; in production environement this isn't acceptable.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Patrick&lt;/P&gt;</description>
      <pubDate>Thu, 15 Jun 2023 14:04:17 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Problem-loss-of-firewall-rules-when-reloading-the-firewalld/m-p/215109#M2621</guid>
      <dc:creator>patrick_romee</dc:creator>
      <dc:date>2023-06-15T14:04:17Z</dc:date>
    </item>
    <item>
      <title>Re: Problem: loss of firewall rules when reloading the firewalld service</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Problem-loss-of-firewall-rules-when-reloading-the-firewalld/m-p/216858#M2622</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Any other solution ?&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;Patrick&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jul 2023 06:45:52 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Problem-loss-of-firewall-rules-when-reloading-the-firewalld/m-p/216858#M2622</guid>
      <dc:creator>patrick_romee</dc:creator>
      <dc:date>2023-07-04T06:45:52Z</dc:date>
    </item>
  </channel>
</rss>

