Project

General

Profile

Bug #11406

Issues with tarball install after factory config code changes

Added by Parag Mhashilkar over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Parag Mhashilkar
Category:
-
Target version:
Start date:
01/12/2016
Due date:
% Done:

0%

Estimated time:
First Occurred:
Occurs In:
Stakeholders:
Duration:

Description

  • manage-glidein is only used for tarball install and it should set the factory_versioning to true to work with new factory config code
  • reconfig_glidein complains about missing entry if the entry is disabled

History

#1 Updated by Parag Mhashilkar over 4 years ago

  • Status changed from New to Feedback
  • Assignee changed from Parag Mhashilkar to Marco Mambelli

#2 Updated by Parag Mhashilkar over 4 years ago

Another possible approach would be to set versioning to true in factory_defaults.xml. But that would mean potentially affecting rpm installation. Much bigger risk than the patch applied here.

#3 Updated by Marco Mambelli over 4 years ago

  • Assignee changed from Marco Mambelli to Parag Mhashilkar

#4 Updated by Parag Mhashilkar over 4 years ago

  • Subject changed from manage-glidein needs to set factory_versioning to Issues with tarball install after factory config code changes
  • Description updated (diff)
  • Assignee changed from Parag Mhashilkar to Marco Mambelli

#5 Updated by Parag Mhashilkar over 4 years ago

I updated the ticket to cover multiple issues. Made some more commits. Reassigning for review.

#6 Updated by Marco Mambelli over 4 years ago

  • Assignee changed from Marco Mambelli to Parag Mhashilkar

#7 Updated by Parag Mhashilkar over 4 years ago

  • Status changed from Feedback to Resolved

Merged to branch_v3_2

#8 Updated by Parag Mhashilkar over 4 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF