<?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: Jumbo hotfix anomaly. Anyone else seeing this?! in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Jumbo-hotfix-anomaly-Anyone-else-seeing-this/m-p/104435#M8255</link>
    <description>&lt;P&gt;This is really not helpful when I'm already in my change window to patch some machines and now can't.&lt;/P&gt;&lt;P&gt;If Check Point really want us to auto-update things, the quality-control has to improve.&lt;/P&gt;&lt;P&gt;C.&lt;/P&gt;</description>
    <pubDate>Mon, 07 Dec 2020 00:23:19 GMT</pubDate>
    <dc:creator>cjrnz</dc:creator>
    <dc:date>2020-12-07T00:23:19Z</dc:date>
    <item>
      <title>Jumbo hotfix anomaly. Anyone else seeing this?!</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Jumbo-hotfix-anomaly-Anyone-else-seeing-this/m-p/104314#M8236</link>
      <description>&lt;P&gt;Hey everyone,&lt;/P&gt;&lt;P&gt;Before I explain the problem, the first time I saw behavior, assumed this be a unique problem, but this happened to completely different client running a different OS which begs me think that all the latest hotfixes seem to show case similar symptoms.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Client 1&lt;/STRONG&gt; - R80.30 currently running jumbo hotfix take 217 on a security gateway in HA.&lt;/P&gt;&lt;P&gt;We uploaded the hotfix to both appliances and run verifier. 1 gateway came through without any problems, the other gateway however failed stating a conflict and the conflict was take 191 itself which was weird and interesting at the same time. Running through the logs, here's what we see.&lt;/P&gt;&lt;P&gt;&lt;EM&gt;HF Check R80_30_JUMBO_HF_MAIN&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Conflict found, version R80_30_JUMBO_HF_MAIN with hotfix :R80_30_JUMBO_HF_MAIN - details:&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;cr: PRJ-6627 files: cphaprob&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Client 2&lt;/STRONG&gt; - R80.20 management server attempting to install take 183 over 111 and resulting conflict is take 111. Here's more on the logs,&lt;/P&gt;&lt;P&gt;&lt;EM&gt;HF Check R80_30_JUMBO_HF_MAIN&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Conflict found, version R80_30_JUMBO_HF_MAIN with hotfix :R80_30_JUMBO_HF_MAIN - details:&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; cr:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 00634812 files: hook_uepm_HOTFIX_R80_30_JUMBO_HF_MAIN&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I just saw a community post from someone else with the same behavior. We ended up removing take 217 and 191, install 219 for client 1 but this brings to think if there is something going within the new jumbo takes for all these versions.&lt;/P&gt;&lt;P&gt;Have plans to install latest jumbo on R80.40 too. Curious if i would see them again&lt;/P&gt;</description>
      <pubDate>Fri, 04 Dec 2020 13:14:38 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Jumbo-hotfix-anomaly-Anyone-else-seeing-this/m-p/104314#M8236</guid>
      <dc:creator>dumbhead123</dc:creator>
      <dc:date>2020-12-04T13:14:38Z</dc:date>
    </item>
    <item>
      <title>Re: Jumbo hotfix anomaly. Anyone else seeing this?!</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Jumbo-hotfix-anomaly-Anyone-else-seeing-this/m-p/104327#M8240</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/46136"&gt;@dumbhead123&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;There is indeed an issue related to the CPUSE engine (DeploymentAgent), it is going to be fixed in matter of days.&lt;/P&gt;
&lt;P&gt;There will be a new agent released soon to solve it. if you are working online you will get this update through CPUSE portal&lt;/P&gt;
&lt;P&gt;and it will also be published in &lt;A href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk92449" target="_blank" rel="noopener"&gt;sk92449&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 04 Dec 2020 14:38:32 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Jumbo-hotfix-anomaly-Anyone-else-seeing-this/m-p/104327#M8240</guid>
      <dc:creator>shlomip</dc:creator>
      <dc:date>2020-12-04T14:38:32Z</dc:date>
    </item>
    <item>
      <title>Re: Jumbo hotfix anomaly. Anyone else seeing this?!</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Jumbo-hotfix-anomaly-Anyone-else-seeing-this/m-p/104435#M8255</link>
      <description>&lt;P&gt;This is really not helpful when I'm already in my change window to patch some machines and now can't.&lt;/P&gt;&lt;P&gt;If Check Point really want us to auto-update things, the quality-control has to improve.&lt;/P&gt;&lt;P&gt;C.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Dec 2020 00:23:19 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Jumbo-hotfix-anomaly-Anyone-else-seeing-this/m-p/104435#M8255</guid>
      <dc:creator>cjrnz</dc:creator>
      <dc:date>2020-12-07T00:23:19Z</dc:date>
    </item>
    <item>
      <title>Re: Jumbo hotfix anomaly. Anyone else seeing this?!</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Jumbo-hotfix-anomaly-Anyone-else-seeing-this/m-p/104519#M8269</link>
      <description>&lt;P&gt;Looks like a new version was just posted and it fixed the issue for me.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Dec 2020 15:05:43 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Jumbo-hotfix-anomaly-Anyone-else-seeing-this/m-p/104519#M8269</guid>
      <dc:creator>David_Evans</dc:creator>
      <dc:date>2020-12-07T15:05:43Z</dc:date>
    </item>
    <item>
      <title>Re: Jumbo hotfix anomaly. Anyone else seeing this?!</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Jumbo-hotfix-anomaly-Anyone-else-seeing-this/m-p/104616#M8272</link>
      <description>&lt;P&gt;HI all&amp;nbsp;&lt;/P&gt;
&lt;P&gt;New DeploymentAgent Build 1999 started gradual deployment today with a fix for the conflict validation error during Jumbo upgrade.&lt;/P&gt;
&lt;P&gt;if you face the upgrade errors described above, you should install the new DA from &lt;A href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk92449" target="_blank"&gt;sk92449&lt;/A&gt; and repeat the Jumbo upgrade.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Dec 2020 06:06:56 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Jumbo-hotfix-anomaly-Anyone-else-seeing-this/m-p/104616#M8272</guid>
      <dc:creator>MatanYanay</dc:creator>
      <dc:date>2020-12-08T06:06:56Z</dc:date>
    </item>
    <item>
      <title>Re: Jumbo hotfix anomaly. Anyone else seeing this?!</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Jumbo-hotfix-anomaly-Anyone-else-seeing-this/m-p/104708#M8281</link>
      <description>&lt;P&gt;DA build 1999 and a bunch of extra paperwork worked for me. &lt;span class="lia-unicode-emoji" title=":grinning_face_with_smiling_eyes:"&gt;😄&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Dec 2020 22:36:46 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Jumbo-hotfix-anomaly-Anyone-else-seeing-this/m-p/104708#M8281</guid>
      <dc:creator>cjrnz</dc:creator>
      <dc:date>2020-12-08T22:36:46Z</dc:date>
    </item>
  </channel>
</rss>

