CSCwp83205 - C8300-1N1S-6T fail to upgrade in install mode

[b.haxhiaj]

Trying to upgrade C8300-1N1S-6T from Cisco IOS XE Software, Version 17.12.03 to recommended Cisco IOS XE Software, Version 17.12.06

I was able to submit "install add file ....." and "install activate" commands, after the router reloaded it was no longer reachable over network (ssh).

I connected to via console and 17.12.06 did no longer show under "show install active".

Even the current version 17.12.03 needed "install commit".

[ R0 ] Active Package(s) Information:
State (St): I - Inactive, U - Activated & Uncommitted,
C - Activated & Committed, D - Deactivated & Uncommitted
--------------------------------------------------------------------------------
Type St Filename/Version
--------------------------------------------------------------------------------
IMG I 17.12.03.0.3740

--------------------------------------------------------------------------------
Auto abort timer: inactive
--------------------------------------------------------------------------------

I reloaded the router after that and was able to access it over the network via ssh.

Anyone has encountered a similar issue?

I did follow the steps on https://www.cisco.com/c/en/us/td/docs/routers/cloud_edge/c8300/software_config/cat8300swcfg-xe-17-book/isr9000swcfg-xe-16-12-book_chapter_0111.html

Thnx

[Mark Elsen]

   - @b.haxhiaj            This version of the bug report : https://bst.cisco.com/bugsearch/bug/CSCwd48802
                                  has                                                          Known Fixed Releases

    M.

[b.haxhiaj]

Hi Mark,

Thnx for your reply, actually my current version Version 17.12.03 or the target version 17.12.06 are not listed as affected releases on either 

CSCwp83205 or CSCwd48802

I opened this thread referring to the pattern of 

CSCwp83205

Br

[Mark Elsen]

   - @b.haxhiaj      That argument is not strong enough.  You should (always) consider and try one of
                            the Known Fixed Releases mentioned in https://bst.cisco.com/bugsearch/bug/CSCwd48802

     ===> The idea here is that they probably didn't care about those in between releases for mentioning
              being affected or not (!)

    M.