RTIR Upgrade problems part 2

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

After fixing the Clone problem, there are still a number of problems I am experiencing.

System info:

Fedora Core 3
mysql 4.1.9
Apache/1.3.33 mod_perl/1.29
perl 5.8.6

Upgraded RT from 3.4.1 to 3.7
Upgraded RTIR from 1.1.5 to 1.9

Before I upgrade again I was hoping that someone could clarify that the problems I am experiencing
are addressed by the updates available via svn. As I would like to know whether they are query
related or database related. Maybe something went wrong during the upgrade that I should fix before
applying yet more updates.

The problems I am experiencing are:

  1. The RTIR section does not return any results. The main page has no tickets shown under the
    headings, even though there are many in the database and can be accessed via RT. This is also the
    case when you click on Incidents, Incident Reports and Investigations. Is this a query problem or
    database problem?

  2. The links no longer work. Links between Incidents and Investigations no longer appear on the web
    UI. There is still a Links table in the db, so again is this a query or a database problem?

  3. When in any of the RTIR queues and you click on refine, I get an error (sometimes):

Error during compilation of /opt/rt3/share/html/RTIR/Search/Elements/ProcessQuery:
Can’t locate YAML/Base.pm

Although that module is installed and in the @INC path. If you refresh the page a number of times it
seems to find the module and all is well. Any ideas about what may be causing this.

Also if I should update to the latest what is the URL for the svn downloads?

I am considering restoring the old version but there are features of the new version that I would
find very useful. Thanks for any help regarding these matters.

Cheers,
Steve
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)

iD8DBQFFD8IX82gHNv0z+WwRAlD/AJ9lGag3CAnuhMb/0TmCp/WFY7bOqQCgxkAD
tHG1lD0DPEnIKOydXCZpyYU=
=cZjn
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

After fixing the Clone problem, there are still a number of problems I am experiencing.

System info:

Fedora Core 3
mysql 4.1.9
Apache/1.3.33 mod_perl/1.29
perl 5.8.6

Upgraded RT from 3.4.1 to 3.7
Upgraded RTIR from 1.1.5 to 1.9
I hope you’ve done upgrade steps described in UPGRADING file

Before I upgrade again I was hoping that someone could clarify that the problems I am experiencing
are addressed by the updates available via svn. As I would like to know whether they are query
related or database related. Maybe something went wrong during the upgrade that I should fix before
applying yet more updates.

The problems I am experiencing are:

  1. The RTIR section does not return any results. The main page has no tickets shown under the
    headings, even though there are many in the database and can be accessed via RT. This is also the
    case when you click on Incidents, Incident Reports and Investigations. Is this a query problem or
    database problem?
    Do you see errors or lists on the page are empty? Do you check as
    SuperUser or as member of DutyTeam?
  1. The links no longer work. Links between Incidents and Investigations no longer appear on the web
    UI. There is still a Links table in the db, so again is this a query or a database problem?
    I think it’s related to rights user have. DutyTeam group should be
    granted with all rights you need after upgrade.
  1. When in any of the RTIR queues and you click on refine, I get an error (sometimes):

Error during compilation of /opt/rt3/share/html/RTIR/Search/Elements/ProcessQuery:
Can’t locate YAML/Base.pm
Please, send full error message with stack trace.

Although that module is installed and in the @INC path. If you refresh the page a number of times it
seems to find the module and all is well. Any ideas about what may be causing this.

Also if I should update to the latest what is the URL for the svn downloads?
svn ls svn://svn.bestpractical.com/rt/branches

  • 3.7-EXPERIMENTAL is branch with latest changes in RT 3.7
  • 3.7-EXPERIMENTAL-RTIR-2.0 is snapshot of the 3.7-EXPERIMENTAL, in
    this branch we commit bugfixes only

svn ls svn://svn.bestpractical.com/rtir/branches/

  • 2.0-TESTING contains latest RTIR 2.0 branch and should work fine
    with both 3.7-EXPERIMENTAL-RTIR-2.0 and 3.7-EXPERIMENTAL, but
    3.7-EXPERIMENTAL-RTIR-2.0 is recommended as more stable snapshot
  • 2.1-EXPERIMENTAL is latest development branch with newest features
    and works well only with 3.7-EXPERIMENTAL branch

I am considering restoring the old version but there are features of the new version that I would
find very useful. Thanks for any help regarding these matters.

Cheers,
Steve
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)

iD8DBQFFD8IX82gHNv0z+WwRAlD/AJ9lGag3CAnuhMb/0TmCp/WFY7bOqQCgxkAD
tHG1lD0DPEnIKOydXCZpyYU=
=cZjn
-----END PGP SIGNATURE-----


Rtir mailing list
Rtir@lists.bestpractical.com
The rtir Archives

Best regards, Ruslan.

Also if I should update to the latest what is the URL for the svn
downloads?
svn ls svn://svn.bestpractical.com/rt/branches

  • 3.7-EXPERIMENTAL is branch with latest changes in RT 3.7
  • 3.7-EXPERIMENTAL-RTIR-2.0 is snapshot of the 3.7-EXPERIMENTAL, in
    this branch we commit bugfixes only

svn ls svn://svn.bestpractical.com/rtir/branches/

  • 2.0-TESTING contains latest RTIR 2.0 branch and should work fine
    with both 3.7-EXPERIMENTAL-RTIR-2.0 and 3.7-EXPERIMENTAL, but
    3.7-EXPERIMENTAL-RTIR-2.0 is recommended as more stable snapshot
  • 2.1-EXPERIMENTAL is latest development branch with newest features
    and works well only with 3.7-EXPERIMENTAL branch
    The above is a little confusing: what changes does 3.7-EXPERIMENTAL-RTIR-2.0
    have over 3.7-EXPERIMENTAL and how will those make it into RT?

If I want to do some testing on something newer than the stable rtir
code that is likely, but not guaranteed to work, which branches should I go
for?

thanks

signature.asc (189 Bytes)

Also if I should update to the latest what is the URL for the svn
downloads?
svn ls svn://svn.bestpractical.com/rt/branches

  • 3.7-EXPERIMENTAL is branch with latest changes in RT 3.7
  • 3.7-EXPERIMENTAL-RTIR-2.0 is snapshot of the 3.7-EXPERIMENTAL, in
    this branch we commit bugfixes only

svn ls svn://svn.bestpractical.com/rtir/branches/

  • 2.0-TESTING contains latest RTIR 2.0 branch and should work fine
    with both 3.7-EXPERIMENTAL-RTIR-2.0 and 3.7-EXPERIMENTAL, but
    3.7-EXPERIMENTAL-RTIR-2.0 is recommended as more stable snapshot
  • 2.1-EXPERIMENTAL is latest development branch with newest features
    and works well only with 3.7-EXPERIMENTAL branch
    The above is a little confusing: what changes does 3.7-EXPERIMENTAL-RTIR-2.0
    have over 3.7-EXPERIMENTAL and how will those make it into RT?
    3.7-EXPERIMENTAL-RTIR-2.0 has no changes that are not in
    3.7-EXPERIMENTAL branch, but 3.7-EXPERIMENTAL has new features that
    are not in 3.7-EXPERIMENTAL-RTIR-2.0.
    All new work goes in 3.7-EXPERIMENTAL branch that once would be
    RT-3.8.X stable release.

If I want to do some testing on something newer than the stable rtir
code that is likely, but not guaranteed to work, which branches should I go
for?
Bleading edge is RTIR-2.1 and 3.7-EXPERIMENTAL.
RTIR-2.0 and 3.7-EXPERIMENTAL-RTIR-2.0 had been created from RTIR-1.9
and 3.7-EXPERIMENTAL after a lot of polishing to match quite stable
state to use in production.

thanks

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFFEIa8K6c0oCC40tsRAn0NAJ42970aPvCWgRvbhWcWdjqyFQ98GwCfRYkW
AZTtxlkHM1nk9rEN1FH7bqY=
=dIh+
-----END PGP SIGNATURE-----

Best regards, Ruslan.

Bleading edge is RTIR-2.1 and 3.7-EXPERIMENTAL.
RTIR-2.0 and 3.7-EXPERIMENTAL-RTIR-2.0 had been created from RTIR-1.9
and 3.7-EXPERIMENTAL after a lot of polishing to match quite stable
state to use in production.
Thanks for the clarification. Given your use of the term “production”,
is there a plan for when the next version of rtir will be declared
"stable" ? :slight_smile:

signature.asc (189 Bytes)

Bleading edge is RTIR-2.1 and 3.7-EXPERIMENTAL.
RTIR-2.0 and 3.7-EXPERIMENTAL-RTIR-2.0 had been created from RTIR-1.9
and 3.7-EXPERIMENTAL after a lot of polishing to match quite stable
state to use in production.
Thanks for the clarification. Given your use of the term “production”,
is there a plan for when the next version of rtir will be declared
"stable" ? :slight_smile:

RTIR-2.0 and 3.7-EXPERIMENTAL-RTIR-2.0

These are versions delivered to customers that we’re providing
production support to them for.

We’ll be releasing RTIR 2.2 in the next month or two. And then RTIR
2.4 about six months after that, which will complete the current
major development push.

Jesse

PGP.sig (186 Bytes)