<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.E-MailFormatvorlage18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=DE-AT link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>Hello,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>i did the upgrade 1 week ago from 4.5.5 to 5.5.2 and had no issues with the upgrade progress.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>Everything went smooth and it worked as expected.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>Maybe try to upgrade to the latest 4.5.5/4.5.6 first and then go the step to 5.5.2.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>Nice greets.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=DE style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Von:</span></b><span lang=DE style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Spce-user [mailto:spce-user-bounces@lists.sipwise.com] <b>Im Auftrag von </b>Raúl Alexis Betancor Santana<br><b>Gesendet:</b> Samstag, 27. Jänner 2018 21:47<br><b>An:</b> spce-user@lists.sipwise.com<br><b>Betreff:</b> Re: [Spce-user] Errror while upgrading from mr4.5.3 to mr5.5.2<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>----- Mensaje original -----<br>> De: "Alex Lutay" <<a href="mailto:alutay@sipwise.com">alutay@sipwise.com</a>><br>> Para: <a href="mailto:spce-user@lists.sipwise.com">spce-user@lists.sipwise.com</a><br>> Enviados: Jueves, 25 de Enero 2018 11:13:55<br>> Asunto: Re: [Spce-user] Errror while upgrading from mr4.5.3 to mr5.5.2<br><br>> Hi,<br>> <br>> First of all you should not share the sensitive content of constants.yml<br>> (you have just shared your DB passwords with Internet).<br><br>Firt of all, it's a demo system, not a production one, I was just testing the upgrade proc, that as usual, doesn't work, either on a freaking clean system.<br>Sorry if sounds rude, but that happens to me also, when upgrading from previous LTS to 4.5, and it's very frustating folling the instructions and get stuck.<br><br>> You have better change them and sync with DB using ngcp-sync-constants<br>> (or just apply new configuration: ngcpcfg apply 'changed passwords' ).<br><br>Doesn't matter, its a testing bed. I just want to see what problems would I have upgrading a real server.<br><br>> For sure there can be some undiscovered issue somewhere,<br>> lets try to localize it. I have just checked clean mr5.5.2 CE vagrant VM<br>> and both users are in DB there. You can repeat my test using manual:<br>>> <a href="https://www.sipwise.org/doc/mr5.5.2/spce/ar01s03.html#_vagrant_box_for_virtualbox">https://www.sipwise.org/doc/mr5.5.2/spce/ar01s03.html#_vagrant_box_for_virtualbox</a><br><br>What's the point of doing that? ... I know that on a new mr5.5.2 everything works, I have another VM with it, this is a test of upgrading a mr4.5.3 to mr5.5.2<br><br>> Can you please share the content of /etc/sipwise_ngcp_version<br>> it will show us the VM life path (when it was installed, where it was<br>> upgraded to and when).<br><br>support@vm-pre-sipwise:~$ cat /etc/ngcp_version<br>mr4.5.3<br><br>Its a clean direct mr4.5.3 install, with no upgrades done so far.<br><br>> You can check the consistency of YML files executing:<br>>> ngcpcfg --validate check<br>> It should report no errors.<br><br>Imposible, system got in an unstable state:<br><br>support@vm-pre-sipwise:~$ ngcpcfg --validate check<br>-bash: ngcpcfg: command not found<br><br>If I rollback to a snapshot before the upgrade try:<br><br>support@vm-pre-sipwise:~$ ngcpcfg --validate check<br>support@vm-pre-sipwise:~$<br><br>As espected<br><br>> In a validation template I see both marked as mandatory:<br>> /usr/share/ngcp-cfg-schema/validate/constants.yml<br>>> "rtcengine":<br>>> type: map<br>>> required: yes<br>>> mapping:<br>>> "u": { type: text, required: yes }<br>>> "p": { type: text, required: yes }<br>>> "rtpengine":<br>>> type: map<br>>> required: yes<br>>> mapping:<br>>> "u": { type: text, required: yes }<br>>> "p": { type: text, required: yes }<br>> <br>> If you have some issues with configuration you should address them.<br><br>On a 4.5.3, that file doesn't exits ..<br><br>less /usr/share/ngcp-cfg-schema/validate/constants.yml<br>/usr/share/ngcp-cfg-schema/validate/constants.yml: No such file or directory<br><br>> Also 'ngcp-status' might share some auto-detected issues with you.<br><br>At this point it doesn't make any sense either ... I'll try a new clean 4.5.3, then just after install it ... will try to do an upgrade to mr5.5.2 and see what happens.<br>I hope not having to use and API dump and API restore of all the information to be able to upgrade.<br>(null)<br>_______________________________________________<br>Spce-user mailing list<br><a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a><br><a href="https://lists.sipwise.com/listinfo/spce-user">https://lists.sipwise.com/listinfo/spce-user</a><o:p></o:p></p></div></body></html>