Support Migration Notice: To update migrated JIRA cases click here to open a new case use www.vmware.com/go/sr | vFabric Hyperic 5.7.0 is Now Available

Hyperic HQ

Inconsistent interaction in setup.{sh,bat}

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Deferred
  • Affects Version/s: 4.0.2, 4.0.3, 4.1.0, 4.1.1, 4.1.2, 4.1.3, 4.1.4, 4.2.0, 4.2.0.1, 4.2.0.2, 4.2.0.3, 4.2.0.4, 4.2.0.5, 4.2.0.6, 4.2.0.7, 4.2.0.8, 4.2.0.9, 4.3, 4.3.0.1, 4.4, 4.4.0.1, 4.4.0.2, 4.5, 4.5.1, 4.5.1.1, 4.5.1.2, 4.5.1.3, 4.5.2, 4.5.2.1, 4.6, 4.5.2.2, 4.6.0.1
  • Fix Version/s: None
  • Component/s: Installation / Upgrade
  • Case Links:
    none
  • Regression:
    No

Description

During the installation processes if the user mistypes information in the jdbc setup questions there is no opportunity to correct it. The installation aborts and the user has to start over. this is different behavior than other parts of the installer as if an incorrect directory is specified the user is given the opportunity to re-enter. There should be consistency throughout the installation process. This can lead to an extremely large amount of wasted time as all the information will have to be re-entered and upon multiple input issues or even permission issues which need to be corrected on the database end.

Activity

Hide
Mayan Weiss added a comment -

I agree this is a bug, but with lower priority.

if this is valid in 4.6 let's fix it otherwise i don't think we should spend time on this (unless this is a really simple fix)

Mayan

Show
Mayan Weiss added a comment - I agree this is a bug, but with lower priority. if this is valid in 4.6 let's fix it otherwise i don't think we should spend time on this (unless this is a really simple fix) Mayan
Hide
Wes Schlichter added a comment -

Updated Affects version to remove any confusion as to what versions this impacts. This is an issue and not only has it annoyed the heck out of me, many users have faced this issue. Most recently seen in an email from one of the sales engineers a large customer lost a lot of time on having to re-enter setup trying to figure out permissions on the db. I think "Major" is appropriate priority towards the goals of making Hyperic more user friendly and supportable.

The CE Team is available to work on this issue if needed. However, this seemed to be border of a bug and an improvement(which falls out of the scope of normal CE) and it could impact the RPM so I left this in the dev arena.

Show
Wes Schlichter added a comment - Updated Affects version to remove any confusion as to what versions this impacts. This is an issue and not only has it annoyed the heck out of me, many users have faced this issue. Most recently seen in an email from one of the sales engineers a large customer lost a lot of time on having to re-enter setup trying to figure out permissions on the db. I think "Major" is appropriate priority towards the goals of making Hyperic more user friendly and supportable. The CE Team is available to work on this issue if needed. However, this seemed to be border of a bug and an improvement(which falls out of the scope of normal CE) and it could impact the RPM so I left this in the dev arena.
Hide
Mayan Weiss added a comment -

your right Major is the right priority,

regarding fixing this bug, we should focus on 4.6 and if we will have 4.5.x.x fix we will consider to back-port it

Show
Mayan Weiss added a comment - your right Major is the right priority, regarding fixing this bug, we should focus on 4.6 and if we will have 4.5.x.x fix we will consider to back-port it
Hide
Yoav Epelman added a comment -

Bulk change to new components

Show
Yoav Epelman added a comment - Bulk change to new components
Hide
Idan Hod added a comment -

As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology.

Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix.

We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base.

This bug has been deferred as part of the new policy.

We appreciate your cooperation and continues contribution to the improvement of Hyperic.

Show
Idan Hod added a comment - As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology. Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix. We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base. This bug has been deferred as part of the new policy. We appreciate your cooperation and continues contribution to the improvement of Hyperic.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    40 weeks, 5 days ago