[Devtools] Development Suite installation question - C/O SME with knowledge of installer edits

Wed Aug 10 16:46:40 UTC 2016

Hi Pete and All,

I tried to validate the workaround, but wasn't able to replicate the
problem on my desktop.

If we don't find an internal user that can validate, we'll make a note when
the next customer case arises.

Thanks,

Rick

On Wed, Aug 10, 2016 at 5:49 AM, Pete Muir <pmuir at redhat.com> wrote:

> Also note that the devsuite had the wrong subscription type attached
> in the download manager. I have updated to be the RHEL Developer Suite
> sub, which should make the documented workaround work. Denis/Rick,
> could you please test the documented "if it doesn't work, try
> downloading devsuite again using the same account"?
>
> Thanks
>
> On 10 August 2016 at 01:41, Denis Golovin <degolovi at redhat.com> wrote:
> > I've updated description for this https://issues.jboss.org/
> browse/RHDENG-579
> > with better workaround. The idea is to login and download CDK itself from
> > developers.redhat.com. This will trigger, if required, additional
> > information request which in my case included one T&C to sign. Finishing
> the
> > form fixed T&C's problem in installer.
> >
> > Denis
> >
> >
> > On 7/20/2016 1:08 AM, Denis Golovin wrote:
> >>
> >> FYI: JIRA created to track this problem:
> >> ORG-3470 DevSuite T&C's signing status check doesn't work for users
> >> created before May 18th
> >>
> >> Denis
> >>
> >> ----- Original Message -----
> >>>
> >>> From: "Pete Muir" <pmuir at redhat.com>
> >>> To: "Rick Wagner" <rwagner at redhat.com>
> >>> Cc: devtools at redhat.com, "Mark Newton" <mnewton at redhat.com>
> >>> Sent: Thursday, July 7, 2016 11:34:47 AM
> >>> Subject: Re: [Devtools] Development Suite installation question - C/O
> SME
> >>> with knowledge of installer edits
> >>>
> >>> On 7 July 2016 at 19:08, Rick Wagner <rwagner at redhat.com> wrote:
> >>>>
> >>>> Hello All,
> >>>>
> >>>> Additional information, this from (no SalesForce acct required) the
> >>>> support
> >>>> case at [1].
> >>>>
> >>>> The customer is telling us the 'use a new account' workaround was
> >>>> successful
> >>>> with a Windows 10 machine.  A second attempt on a Win 7 machine fails.
> >>>>
> >>>> The failed effort:
> >>>> - Is using the userid 'ryanbuckett'
> >>>> - Previously failed effort (the original account) was
> >>>> 'SumaGeethakumari'.
> >>>>
> >>>> The customer is asking if the downloaded exectuable must be used on
> the
> >>>> machine it was downloaded to?  (If the username specified for download
> >>>> and
> >>>> installation are the same, is it relevant where the artifact was
> >>>> downloaded
> >>>> to?)
> >>>
> >>> No, the link is usernames. You must use the username you downloaded
> >>> with when you run the installer.
> >>>
> >>> David/Mark, can you check these user accounts - have they signed the
> >>> RHEL Developer Suite T&C?
> >>>
> >>>> Thanks,
> >>>>
> >>>> Rick
> >>>>
> >>>> [1] https://access.redhat.com/support/cases/01662411
> >>>>
> >>>> On Thu, Jul 7, 2016 at 11:40 AM, Pete Muir <pmuir at redhat.com> wrote:
> >>>>>
> >>>>> Very helpful Robert, as it helps us identify that there is a problem
> >>>>> on the server side around older accounts that somehow aren't being
> >>>>> properly upgraded.
> >>>>>
> >>>>> Mark/David, can you treat this as an urgent issue to look in to, as
> >>>>> it's getting reported by customers.
> >>>>>
> >>>>> Rick Wagner is getting more info from customers, but Robert seems to
> >>>>> have identified at least one failing path.
> >>>>>
> >>>>> On 7 July 2016 at 17:29, Robert Kratky <rkratky at redhat.com> wrote:
> >>>>>>
> >>>>>> Follow up: brand new account worked for this user. So:
> >>>>>>
> >>>>>> - user didn't use social accounts to log in
> >>>>>> - orig. account created on dev.rh.com on May 18: doesn't work
> >>>>>> - new account created on July 7: works
> >>>>>>
> >>>>>> Hope this helps a bit.
> >>>>>>
> >>>>>> Regards,
> >>>>>> Robert
> >>>>>>
> >>>>>>
> >>>>>> On 7. 7. 2016 17:33:32, Robert Kratky wrote:
> >>>>>>
> >>>>>>> Based on a new user comment [1], the "don't use social accounts"
> >>>>>>> workaround doesn't seem to work. It might be related to the fact
> that
> >>>>>>> he
> >>>>>>> created his RH account on May 18 (i.e. it's not fresh).
> >>>>>>>
> >>>>>>> I asked the user to try a completely new account, but some less
> >>>>>>> drastic
> >>>>>>> solution would be better.
> >>>>>>>
> >>>>>>> Robert
> >>>>>>>
> >>>>>>> [1] https://access.redhat.com/articles/2255391#comment-1069221
> >>>>>>>
> >>>>>>>
> >>>>>>> On 7. 7. 2016 15:58:06, Robert Kratky wrote:
> >>>>>>>
> >>>>>>>> I updated the text to emphasize that social accounts are not to be
> >>>>>>>> used. It now says, basically:
> >>>>>>>>
> >>>>>>>> 1) log in using RH credentials
> >>>>>>>> 2) do not use social accounts
> >>>>>>>> 3) if you can't (i.e. you have no RH account), create a new one
> >>>>>>>>
> >>>>>>>> Robert
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On 7. 7. 2016 14:42:15, Pete Muir wrote:
> >>>>>>>>
> >>>>>>>>> Robert, as discussed on the call, you might want to recommend a
> >>>>>>>>> "radical" workaround, of just creating a new account entirely,
> >>>>>>>>> without
> >>>>>>>>> using social media at all.
> >>>>>>>>>
> >>>>>>>>> On 7 July 2016 at 14:38, Robert Kratky <rkratky at redhat.com>
> wrote:
> >>>>>>>>>>
> >>>>>>>>>> I updated the trouleshooting section in [1] based on the
> >>>>>>>>>> discussion during today's program call. Please, have a look and
> >>>>>>>>>> let me know
> >>>>>>>>>> if what I wrote is accurate -- I cannot test at this moment.
> >>>>>>>>>>
> >>>>>>>>>> This is what it says now:
> >>>>>>>>>>
> >>>>>>>>>> .............
> >>>>>>>>>> Terms and Conditions Error
> >>>>>>>>>>
> >>>>>>>>>> Error: “Terms and Conditions for CDK have not been signed”
> >>>>>>>>>> This error appears on the Log In page when starting the
> >>>>>>>>>> Installer. To work around the problem, log in to the Developer
> >>>>>>>>>> Portal using
> >>>>>>>>>> your Red Hat credentials -- the credentials that you created
> >>>>>>>>>> either on
> >>>>>>>>>> redhat.com or developers.redhat.com. Do not use your social
> >>>>>>>>>> accounts to log
> >>>>>>>>>> in. Then start downloading the Installer from Red Hat
> Development
> >>>>>>>>>> Suite
> >>>>>>>>>> download page.
> >>>>>>>>>>
> >>>>>>>>>> If you do not have a Red Hat account, create one at
> >>>>>>>>>> developers.redhat.com.
> >>>>>>>>>> .............
> >>>>>>>>>>
> >>>>>>>>>> Thanks.
> >>>>>>>>>> Robert
> >>>>>>>>>>
> >>>>>>>>>> [1] https://access.redhat.com/articles/2360571#troubleshooting
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> On 7. 7. 2016 10:32:06, Misha Husnain Ali wrote:
> >>>>>>>>>>
> >>>>>>>>>>> I remember this issue. Is there any way we can identify the
> >>>>>>>>>>> paths leading
> >>>>>>>>>>> up to this problem and comprehensively test them to provide
> >>>>>>>>>>> clear aid to
> >>>>>>>>>>> users who may encounter this issue? I'm happy to volunteer to
> >>>>>>>>>>> test some of
> >>>>>>>>>>> them if we can identify the various paths users may take.
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> --
> >>>>>>>>>>> Misha Husnain Ali
> >>>>>>>>>>> Technical Writer 2, CCS Brisbane
> >>>>>>>>>>>
> >>>>>>>>>>> On Thu, Jul 7, 2016 at 5:38 AM, Denis Golovin
> >>>>>>>>>>> <degolovi at redhat.com> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>> T&C's signing workflow is not user friendly ATM.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Workaround mentioned in
> >>>>>>>>>>>> https://access.redhat.com/articles/2360571 worked
> >>>>>>>>>>>> before for
> >>>>>>>>>>>> many dev's who was testing installer. I am going to do check
> >>>>>>>>>>>> full T&C's
> >>>>>>>>>>>> signing again today
> >>>>>>>>>>>> and send update ASAP.
> >>>>>>>>>>>>
> >>>>>>>>>>>> This problem should be affecting only customers who didn't get
> >>>>>>>>>>>> installer
> >>>>>>>>>>>> directly from develper.redhat.com
> >>>>>>>>>>>> download.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Denis
> >>>>>>>>>>>>
> >>>>>>>>>>>> ----- Original Message -----
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> From: "Robert Kratky" <rkratky at redhat.com>
> >>>>>>>>>>>>> To: devtools at redhat.com
> >>>>>>>>>>>>> Cc: "Rick Wagner" <rwagner at redhat.com>
> >>>>>>>>>>>>> Sent: Wednesday, July 6, 2016 8:51:03 AM
> >>>>>>>>>>>>> Subject: Re: [Devtools] Development Suite installation
> >>>>>>>>>>>>> question - C/O
> >>>>>>>>>>>>
> >>>>>>>>>>>> SME     with knowledge of installer edits
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On 6. 7. 2016 10:08:09, Rick Wagner wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> Hello DevTools,
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> We have a customer case that deals with the error message
> >>>>>>>>>>>>>> "Terms and
> >>>>>>>>>>>>>> Conditions for the CDK have not been signed".  (Actually,
> >>>>>>>>>>>>>> this is the
> >>>>>>>>>>>>>> second case in 2 days for this problem.)
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> The customer has tried the suggested workaround, without
> >>>>>>>>>>>>>> satisfactory
> >>>>>>>>>>>>>> results.  ("This error appears on the *Log In* page when
> >>>>>>>>>>>>>> starting the
> >>>>>>>>>>>>>> Installer. To fix the problem, start downloading the
> >>>>>>>>>>>>>> Installer to
> >>>>>>>>>>>>
> >>>>>>>>>>>> ensure
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> the *Terms and Conditions* are viewed and accepted and
> >>>>>>>>>>>>>> then cancel the
> >>>>>>>>>>>>>> binary download."  We offer this suggestion in the
> >>>>>>>>>>>>>> knowledge article at
> >>>>>>>>>>>>>> [1].)
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Can a knowledgeable SME please offer ideas about
> >>>>>>>>>>>>>> alternative courses of
> >>>>>>>>>>>>>> action?
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Hi Rick,
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> The problem happens quite often, apparently. I asked about
> >>>>>>>>>>>>> this last
> >>>>>>>>>>>>
> >>>>>>>>>>>> Friday
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> in devtools-program [a] -- on behalf of a user who reported
> >>>>>>>>>>>>> the problem
> >>>>>>>>>>>>
> >>>>>>>>>>>> in a
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> comment under the old version of the Kbase article [b].
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Any workaround would be appreciated.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Thanks.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Robert
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> [a]
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> http://post-office.corp.redhat.com/archives/devtools-
> program/2016-July/msg00001.html
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> [b]
> >>>>>>>>>>>>> https://access.redhat.com/articles/2255391#comment-1066361
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> Extra credit:  Can you please point me to the source code
> >>>>>>>>>>>>>> that produces
> >>>>>>>>>>>>>> this edit error?  A little spelunking by the Support team
> >>>>>>>>>>>>>> sometimes
> >>>>>>>>>>>>
> >>>>>>>>>>>> helps
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> with related issues.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Thanks!
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Rick
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> [1] https://access.redhat.com/articles/2360571
> >>>>>>
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> Devtools mailing list
> >>>>>> Devtools at redhat.com
> >>>>>> https://www.redhat.com/mailman/listinfo/devtools
> >>>>
> >>>>
> >>> _______________________________________________
> >>> Devtools mailing list
> >>> Devtools at redhat.com
> >>> https://www.redhat.com/mailman/listinfo/devtools
> >>>
> >> _______________________________________________
> >> Devtools mailing list
> >> Devtools at redhat.com
> >> https://www.redhat.com/mailman/listinfo/devtools
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/devtools/attachments/20160810/b4cbee1e/attachment.htm>