Upgrades: use the management address type from old install#41
Upgrades: use the management address type from old install#41ydirson merged 2 commits into10.10.29-8.3from
Conversation
|
It is really strange. When doing a fresh install using IPv6 static only my installation ends with IPv4. And the I will add some logs to understand why it doesn't work... |
ecea49a to
21aa5cf
Compare
So the issue was as expected because the management address type is always set. By default it is set to IPv4. So we use it only when no modes are selected (and it is the case during an upgrade for example). I tested a fresh install and in this case we are either in IPv4 mode or IPv6 mode. If the mode is IPv6 only we are in IPv6 and if it is set to both we use IPv4. And as said during an upgrade we are using the one set in /etc/xensource-inventory.
|
|
Adding Yann to the review. Please all review this very carefully, as we don't want to introduce a regression at this stage of the release. If we doubt we can guarantee this, then we'll take more time for testing this change and release without. We need to decide today and package the updated installer in the afternoon. An upstream PR is needed, too. |
ydirson
left a comment
There was a problem hiding this comment.
The logic is not obvious at first read, it would be useful to give a few details about the change in the commit message
9c29926 to
265ed12
Compare
There was a problem hiding this comment.
Not really sure to get it:
mgmtAddrType()seems to be used to set a default value, but only for install (would be useful to make it explicit in the code)prepareUpgrade()statesMANAGEMENT_ADDRESS_TYPEmust be present inxensource-inventory, but looks at the default value (as well as the uuids!?), even though exceptions are rised if they cannot get overriden bygetInventoryValue()calls?
|
Unless I'm wrong, I believe this PR is waiting for @gthvn1 after Yann's comments. |
Yes right I missed it. But I'm not sure to understand the remark. As far as I understand it we will always in the case where no mode is selected we must have a value in the inventory from previous install so it will be overwritten with the value found in the inventory. And as the default case is "IPv4" I set it by default but yes maybe it is not needed. I don't remember exactly but I think when I tested it it didn't work without this definition. |
|
I will give it a try and keep you in touch. Probably today. |
265ed12 to
fd143d1
Compare
So when removing |
|
@ydirson Ok I found why I added the |
fd143d1 to
f1169e6
Compare
|
I have splitted the PR in two commits. The first commit can be upstreamed. |
|
The second commit can also be upstreamed as part of Benjamin's IPv6 PR, can't it? |
|
Ah yes maybe 👍 |
You think about this commit #17 |
I don't know about that draft. I'm rather thinking of xenserver#2, if I'm not mistaken. |
The two parameters are read from the xensource inventory so no need to pass them as parameters of the prepareUpgrade function. Signed-off-by: Guillaume <guillaume.thouvenin@vates.tech>
f1169e6 to
887e842
Compare
|
Rebased for v10.10.29 |
887e842 to
8515eab
Compare
|
Rename the |
ydirson
left a comment
There was a problem hiding this comment.
There's a bug here, no parameter should be added to prepareUpgrade
During an upgrade we need to use the management address from the installation read from /etc/xensource-inventory. This does not change the behaviour of installation. Signed-off-by: Guillaume <guillaume.thouvenin@vates.tech> Signed-off-by: Yann Dirson <yann.dirson@vates.tech>
8515eab to
53353b3
Compare
No description provided.