[cisco-voip] Jabber Team Messaging Mode: contact migration prompt does not appear (CSCvt55321)

[Ryan Ratliff (rratliff)]

The bug has been updated.

It’s not just that line that signifies the bug, before that will be the Atlas discovery for the user that calls out migration is required.
Similar to:
INFO [0x000010cc] [iscovery\AtlasLookupDirectorImpl.cpp(63)] [service-discovery] [CSFUnified::AtlasLookupDirectorImpl::determineIsSparkCustomer] - Atlas lookup result from server: Code: IS_SPARK_CUSTOMER; supportsSSO: 0; emailVerified: 1; migrationRequired: 1; migrationCompleted: 0

Then the second line for MigrationLifeCycle will show that’s not actually required, as Frank pointed out.

- Ryan

From: cisco-voip <cisco-voip-bounces at puck.nether.net> on behalf of Lelio Fulgenzi <lelio at uoguelph.ca>
Date: Tuesday, April 28, 2020 at 12:28 PM
To: "Wakelin, Frank" <FWakelin at richmond.ca>, cisco-voip list <cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Jabber Team Messaging Mode: contact migration prompt does not appear (CSCvt55321)

Sometimes I think we’re lucky they don’t classify a bug as sev 6 and carry on. ☹

From: cisco-voip <cisco-voip-bounces at puck.nether.net> On Behalf Of Wakelin, Frank
Sent: Tuesday, April 28, 2020 12:02 PM
To: 'cisco-voip at puck.nether.net' <cisco-voip at puck.nether.net>
Subject: [cisco-voip] Jabber Team Messaging Mode: contact migration prompt does not appear (CSCvt55321)


Thought I’d share this in the event someone else runs into this.  After experiencing this issue I looked for a bug that might explain the behavior and found this bug.  However because it said it was "fixed" and didn't sight the version I was running I opened a TAC case to verify.  After having to escalate to a senior TAC engineer, they still made me jump through all the hoops switching modes, collecting logs, etc.  When all was said and done the sighted the same bug ID I sent them in the first place.  Now I understand bugs need to be confirmed, so I'm fine with going through "the process".  This is (apparently) fixed in 12.8(2) which has yet to be released.  It is generally confirmed with the presence of the following in the log:

2020-04-27 10:23:59,572 WARN  [0x00005714] [in\person\IMContactListProvider.cpp(111)] [csf.person] [csf::person::IMContactListProvider::fetchContactsOperation] - Contact list is not injected, it will be returned once it is injected.
2020-04-27 10:23:59,572 INFO  [0x00004550] [rk\migration\MigrationLifeCycle.cpp(206)] [csf.person.spark] [csf::person::spark::MigrationLifeCycle::InMigrationStatus] - In migration mode: false
2020-04-27 10:23:59,572 DEBUG [0x00004550] [directory\ContactListFeatureSet.cpp(550)] [ContactService-ContactsAdapter] [CSFUnified::ContactsAdapter::LoadContactsFromSource] - start ContactsAdapter::LoadContactsFromSource

<rant>

If Cisco could just post accurate information in bugs it would save everyone a lot of time and I wouldn't have had to even open a case in the first place:

  *   The bug status should not be “Fixed” as it is clearly not.
  *   It should state it also affects 12.8(1).
  *   A reference to 12.8(2) should be listed in known fixed releases.
  *   Symptoms should include a reference to the log entry sited.
</rant>

[CityofRichmond2]
Frank Wakelin · Senior Network Analyst, Information Technology
City of Richmond · 6911 No. 3 Road, Richmond, BC  V6Y 2C1
Å +16042764190 È+17788394693  › fwakelin at richmond.ca<mailto:fwakelin at richmond.ca>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200428/761ecddd/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 2099 bytes
Desc: image001.jpg
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200428/761ecddd/attachment.jpg>