Bug 191431

Created attachment 128918 [details]
Revised content for Login Creation email (Two way prop)

Created attachment 129604 [details]
This is the content that should replace the existing 2-way prop email.  

This content contains minor edits to the original text I attached for this bug.
 Please use this revision to make the text changes.

Created attachment 130377 [details]
New content for 2-way prop email.

New content for 2-way prop email.

TEST PLAN
----------
1) Use the test plan for the bug #170284 to get email sent.
2) verify the email matches the content in Comment #5, except the
   Customer Name and Account Number should match that of the user
   you specified in Step 1.

Created attachment 130889 [details]
Final content for 2-way prop email June 14 2006.

Moving to ON_QA

Taking care of this issue at the moment...  should have an update soon.

Moving to ON_QA

Hi!

Resource key email.newuser.bala.footer has been adapted exactly to the requested
German value: "Für zusätzliche Informationen in deutscher Sprache, besuchen Sie
bitte unsere Website:"

Regards,

Timo

Taskomatic on any RHN hosted environment is in a flaky state.  Since, after
several iterations of the test plan in bug #170284 to generate an email, no
emails could be generated, I'm waiting until Taskomatic becomes available again
before testing out this issue.

Created attachment 131690 [details]
Revised content for login creation email June 28 with intl links

more content required.  moving back to ASSIGNED.

Added french text, pending translation from brisbane.

Moving to ON_QA

I am moving this bug to FAILS_QA, because the test plan in bug #170284 that
we're using will not generate the appropriate e-mail.  I have tried the
following techniques:

1.  I created a fresh account, populating its oracle_customer_id number in
web_contact as shown by kganong's comment in bug #170284.  I then added a row as
described by the test plan into web_customer_notification as described for the
test plan.  I ensured that in all cases, the email address it pointed to was
ssalevan.com, which properly directed emails to me in a different
Taskomatic-related bug.

2.  I found an existing account, changed its email address to
ssalevan.com, and used all its relevant information (org_id, etc.) to
populate a new row in web_customer_notification.

In both cases, I tailed the rhn_taskomatic.log file, and each time that the
SummaryPopulation task was run, this traceback would be given near its completion:

[2006-07-10 17:42:59,629] ERROR com.redhat.rhn.task.SummaryPopulation -
ORA-00001: unique constraint (RHN.RHN_DSQUEUE_OID_UQ) violated

com.redhat.rhn.common.db.ConstraintViolationException: ORA-00001: unique
constraint (RHN.RHN_DSQUEUE_OID_UQ) violated

        at
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
        at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java(Compiled Code))
        at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java(Inlined
Compiled Code))
        at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java(Compiled Code))
        at
oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java(Compiled
Code))
        at
oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java(Compiled
Code))
        at
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java(Compiled
Code))
        at
oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java(Compiled
Code))
        at
oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java(Compiled
Code))
        at
com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.execute(NewProxyPreparedStatement.java(Compiled
Code))
        at
com.redhat.rhn.common.db.NamedPreparedStatement.execute(NamedPreparedStatement.java(Inlined
Compiled Code))
        at
com.redhat.rhn.common.db.datasource.CachedStatement.execute(CachedStatement.java(Compiled
Code))
        at
com.redhat.rhn.common.db.datasource.CachedStatement.execute(CachedStatement.java(Inlined
Compiled Code))
        at
com.redhat.rhn.common.db.datasource.CachedStatement.executeUpdate(CachedStatement.java(Inlined
Compiled Code))
        at
com.redhat.rhn.common.db.datasource.WriteMode.executeUpdate(WriteMode.java(Compiled
Code))
        at
com.redhat.rhn.task.SummaryPopulation.enqueueOrg(SummaryPopulation.java:104)
        at com.redhat.rhn.task.SummaryPopulation.run(SummaryPopulation.java:68)
        at
com.redhat.rhn.task.SingleThreadedTask.execute(SingleThreadedTask.java:46)
        at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
        at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java(Compiled
Code))
Caused by: java.sql.SQLException: ORA-00001: unique constraint
(RHN.RHN_DSQUEUE_OID_UQ) violated

        ... 20 more
[2006-07-10 17:42:59,632] ERROR com.redhat.rhn.taskomatic.SchedulerKernel -
org.quartz.JobExecutionException:
com.redhat.rhn.common.db.ConstraintViolationException: ORA-00001: unique
constraint (RHN.RHN_DSQUEUE_OID_UQ) violated
 [See nested exception: com.redhat.rhn.common.db.ConstraintViolationException:
ORA-00001: unique constraint (RHN.RHN_DSQUEUE_OID_UQ) violated

After waiting a half hour, no emails were sent, so I've got to think that
there's something wrong with the actual test plan now that taskomatic's running
on WebQA.  As a result, I'm moving this to FAILS_QA for further consideration.

This looks like we have two seperate problems.  One is SummaryPopulation, the
other is pushed users.

The DailySummary queue error is not caused by PushedUsers and I have opened a
separate bug for that, see bug #198314.

The problem with PushedUsers was a typo in the query that looks for users
to email.

Now that that SummaryPopulation bug is fixed, following the test plan now
(finally) produces a 2-way prop email in the appropriate fashion, complete with
the appropriate French and German strings and the correct style of link to the
RHN site.  I am now moving this bug to VERIFIED.

closing - currentrelease